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

global triggers #13

Closed russroy closed 6 years ago

russroy commented 10 years ago

How difficult would it be to introduce the notion of a "global" trigger for use in multi-machine environments? That is, a trigger which would fire once for all machines rather than once for each machine. I'm thinking here of the use case of cluster-wide setup/cleanup operations.

Eg. In an aws ec2 env I'd like to dynamically allocate a subnet for my cluster as a "before" action upon 'vagrant up' and dealloc as an "after" action upon 'vagrant destroy' - one operation for all machines.

snowch commented 10 years ago

+1, I also need to perform an operation after all vm's have started.

Is there a workaround that can be used until this enhancement is in place?

AntonioMeireles commented 9 years ago

+1 too. would be very handy.

aprudnik commented 9 years ago

+1. I would like it too. otherwise I have to use --no-parallel tag to ensure all VMs are up and running, after I can start a script.

mcameron commented 9 years ago

+1

rolodato commented 9 years ago

+1

brianfgonzalez commented 8 years ago

+1

fabianvf commented 8 years ago

+1, have some networking changes I need to make after every VM is up, vagrant gets very unhappy if these changes happen before it tries to bring up a vm

stephenrlouie commented 8 years ago

+1

mbarretta commented 7 years ago

+1

ntrp commented 6 years ago

Any news about this?

rahulmishra commented 6 years ago

+1