Thanks for the reply Alvaro. I did as you suggested and I got the result I was looking for (i.e. shell/salt provisioners only run once per "up" and "destroy").
Follow-up question... can you explain _why_ Vagrant called each four times the way I had it configured originally? What if I wanted to enhance my Vagrantfile and have it spin up several AWS instances, each running different shell/salt provisioners? What would the syntax look like then? Hopefully the question makes sense. If not, I will post another question once I make the planned expansion to my Vagrantfile. Thanks again for your help. Steve. On Monday, April 14, 2014 9:07:29 PM UTC-7, Alvaro Miranda Aguilera wrote: > > hello, I have no expiernce with AWS, but you need the provisioner block to > be included in the provider? > > if I had to do the same in virtualbox, I will put an end after those > override, > > > if you have time, move the end from line 53 to line 41. > > > On Tue, Apr 15, 2014 at 10:44 AM, Steve Kirkpatrick > <[email protected]<javascript:> > > wrote: > >> Thanks for the quick response Mitchell. >> >> Here's a link to the Vagrantfile: >> https://gist.github.com/stepkirk/10687914 >> >> >> On Monday, April 14, 2014 3:20:24 PM UTC-7, Mitchell Hashimoto wrote: >> >>> Please share your Vagrantfile >>> >>> On Mon, Apr 14, 2014 at 3:16 PM, Steve Kirkpatrick <[email protected]> >>> wrote: >>> > Hello, >>> > >>> > Trying to figure out why Vagrant (tried 1.5.1, 1.5.2 and 1.5.3) would >>> run >>> > the same provisioners multiple times on "up" and "destroy". >>> > >>> > Here is the output from a "destroy": >>> > >>> > $ vagrant destroy --force >>> > WARNING: Nokogiri was built against LibXML version 2.8.0, but has >>> > dynamically loaded 2.9.1 >>> > ==> default: Terminating the instance... >>> > ==> default: Running cleanup tasks for 'shell' provisioner... >>> > ==> default: Running cleanup tasks for 'shell' provisioner... >>> > ==> default: Running cleanup tasks for 'salt' provisioner... >>> > ==> default: Running cleanup tasks for 'shell' provisioner... >>> > ==> default: Running cleanup tasks for 'shell' provisioner... >>> > ==> default: Running cleanup tasks for 'salt' provisioner... >>> > ==> default: Running cleanup tasks for 'shell' provisioner... >>> > ==> default: Running cleanup tasks for 'shell' provisioner... >>> > ==> default: Running cleanup tasks for 'salt' provisioner... >>> > ==> default: Running cleanup tasks for 'shell' provisioner... >>> > ==> default: Running cleanup tasks for 'shell' provisioner... >>> > ==> default: Running cleanup tasks for 'salt' provisioner... >>> > >>> > I have two shell provisioners and one salt. You can see it is running >>> them >>> > four times. >>> > My guess I I have a problem with my Vagrantfile? >>> > >>> > Any ideas on what to look for? Would a copy of my Vagrantfile help? >>> > >>> > FWIW, I am using AWS as the provider. >>> > >>> > Thanks, >>> > Steve. >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups >>> > "Vagrant" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> an >>> > email to [email protected]. >>> > For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
