This really all depends on the environment. Ill list of a few examples of what may happen.
1) If your bootstrap is part of the box I think it will only run when creating a new "machine". and so switching the bootstrap file will not have an effect unless someone runs "vagrant destroy -f && vagrant up" 2) If your bootstrap file is actuality a shell script provision and you are running vagrant less than version 1.4 it will run the full script each time a vagrant up is run. 3) If your bootstrap file is actuality a shell script provision and you are running vagrant greater than version 1.4 it will run the full script only on the first run on creating a vm ( vagrant provision will force a run ) 4) in vagrant 1.6 you will be able to add scripts to either run once or always. ( I am not sure of the implementation but ) you could just update the vagrant file with another shell script provision and have it only run once and so the differences will be applied on the next "vagrant up/reload/provision" command. In cases 2 and 3 the differences could be applied if the bootstrap file has the ability to figure out its last step and continue where it left off. Good Luck! On Wed, Apr 16, 2014 at 11:39 PM, Hendra Uzia <[email protected]> wrote: > I have an updated bootstrap file and about to distributed to all other > developers who's using it. Is there a mechanism in vagrant or other tools > in conjunction with vagrant so that developer can provision only a fraction > of updated bootstrap file rather than whole bootstrap file? Manually > running the changes is possible by seeing differences in the commit, but it > would be better if there's a mechanism that can support this task. > > I'm hoping it's analogous to database migration tools, which developer can > migrate changes to the database rather than recreate the database from > zero. I'm new to vagrant and this might be an rtfm question, so far I > haven't found solution to this issue, and I'm open to suggestions. Thanks. > > -- > 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]. For more options, visit https://groups.google.com/d/optout.
