Bypass install.sh entirely

[lamont-granquist]

For testing I'd like to be able to set an env var to point to a deb or rpm on my system and just copy that into the guest and install it. No need for the O/S detection and version discovery in install.sh I just want to get a package onto the system. For bonus points the env var could be a URL and if its not file:// then the vagrant pure-ruby downloader could suck it down from S3 or wherever and install it...

[tmatilai]

Sounds like the same as #16. :)

[lamont-granquist]

sorta, mostly i'd like to use this for testing pre-rc version of chef-client where i don't really want to mark up my Vagrantfile at all -- i want a local override of install.sh, and its not a dependency that i want to check in to version control and share, so i want the env var approach.

[tmatilai]

I'm big fan of env vars myself. There is no reason why both couldn't be supported. But I guess the best way to get this moving would be to make a PR. ;)

[lamont-granquist]

i actually tend to think env vars are horrible, but for this use case it is precisely what i want...

i think you also want the ability to be able to set a url in the vagrantfile and install the chef client directly from there. you probably don't want to check in a file:// uri in that case since that leads down the road of checking chef client packages in with your repo which is terrible... (although there's no reason to go out of our way to prevent this use case, if people want to be terrible they should go right ahead...)

and, yeah, thinking about a PR...

[fletchowns]

It would be awesome if we had a way to control where it grabs the install package from