search

emyl / vagrant-triggers

Allow the definition of arbitrary scripts that will run on the host before and/or after Vagrant commands.
MIT License
546 stars 35 forks source link

VAGRANT_NO_TRIGGERS seems to be ignored #50

Closed salzamt closed 9 years ago

salzamt commented 9 years ago

hi, it seems that no matter if the VAGRANT_NO_TRIGGERS env var is set or not, scripts are executed. cheers

emyl commented 9 years ago

Hi!

Just tried:

Cannonball:vagrant-triggers emyl$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Running triggers before up...
==> default: Executing command "uname -a"...
==> default: Darwin Cannonball.local 12.6.0 Darwin Kernel Version 12.6.0: Wed Mar 18 16:23:48 PDT 2015; root:xnu-2050.48.19~1/RELEASE_X86_64 x86_64
==> default: Command execution finished.
==> default: Checking if box 'puppetlabs/ubuntu-12.04-64-puppet' is up to date…
==> default: VirtualBox VM is already running.
Cannonball:vagrant-triggers emyl$ VAGRANT_NO_TRIGGERS=1 vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'puppetlabs/ubuntu-12.04-64-puppet' is up to date…
==> default: VirtualBox VM is already running.

Can you provide additional details or an example in order I can reproduce your error?

emyl commented 9 years ago

I'm closing this, feel free to reopen the issue if you can reproduce the error in some way.