provide parameter for privately hosted chef package

[someara]

because ENTERPRISE (pew pew pew)

[schisamo]

Have some more details on how you would like this to work? What should the config look like? How do we select the correct package in a multi-vm Vagrantfile?

[James-Snow]

I have a need for this as well.

Presumably one has a specific Chef package in mind for each Vagrant box, so perhaps being able to point at an installer per box? Something like:

Vagrant::Config.run do |config|
  config.vm.define :web do |web_config|
    web_config.vm.box = "web"
    web_config.vm.forward_port 80, 8080
    web_config.vm.chef_version = "/path/to/chef_11.6.0-1.ubuntu.12.04_i386.deb"
  end

  config.vm.define :db do |db_config|
    db_config.vm.box = "db"
    db_config.vm.forward_port 3306, 3306
    db_config.vm.chef_version = "/path/to/chef_11.6.0-1.ubuntu.12.04_amd64.deb"
  end
end

[schisamo]

@someara @James-Snow Could you workaround this by using an alternate install.sh via the OMNIBUS_INSTALL_URL environment variable?

This was added as part of @petecheslock's work in #10

[someara]

That solves it, but it'd be nice as a config parameter instead of an environment.
At minimum is should appear in the readme

[James-Snow]

My goal was offline development - i.e, no Internet connectivity. The environment variable method works in that it lets me point at a self-extracting shell script.

[schisamo]

Trying to consolidate things here, closing this as it's the same as #46.