Re: [vagrant-up] My plugin isn't loading on Vagrant 1.6.0+

://github.com/mitchellh/vagrant/issues/3775 plugin on the Vagrantifle used to work, but wasn't meant to do it in that way. So when in 1.6 stopped to work, is not much that could be done to bring the functionality back. Alvaro On Fri, Jun 27, 2014 at 5:14 AM, Alexander Kahn alexan

Re: [vagrant-up] Can't vagrant provision (chef) due to sudo -E

Matilainen teemu.matilai...@iki.fiwrote: Hi Alex, You should be able to set GEM_HOME with `chef.binary_env` attribute, like this: https://gist.github.com/tmatilai/9376993 -- Teemu On Tue, May 6, 2014 at 11:44 PM, Alexander Kahn alexanderk...@gmail.comwrote: Hi everyone, I'm upgrading from

[vagrant-up] Can't vagrant provision (chef) due to sudo -E

Hi everyone, I'm upgrading from Vagrant 1.0.7 to 1.5.4. Things are mostly working except that this change[1], which makes sudo commands run with -E (preserve environment), causes chef-client to load a version of the Yajl gem from the vagrant user's gem path rather than from chef's embedded

[vagrant-up] Plugin hook into instance creation

Hi, I'm porting some code from Vagrant 1.0.x to 1.5.x. The code hooks into the `up` (new VM is created) and `start` (existing VM is booted) events. In Vagrant 1.5, I'm seeing machine_action_up, machine_action_halt and machine_action_provision, which I'm making use of. But I don't see a way to