Hello
I need to solve a big problem, generating the .vagrant folder without
stopping and restarting the VM's.
We are using github to store the Vagrant file and the provision scripts,
but not the .vagrant folder.
Every time you clone the repo in a different machine you do not know which
servers are up and running and which are not.
Let's say I deliver the project to a customer with some of the VM's running
and some stopped and the customer runs a 'vagrant status';
they don't see the running machines and if they try to run them, they will
run NEW instances
I need to dump (re-generate) the .vagrant/machines/{{machine}}/aws folder
and configurations.
There is anyway to do it? Probably tweaking with ruby inside the vagrant
file or maybe including the Vagrantfile inside a .rb file you can get that
info, but unfortunatelly I'm not ruby programmer.
Hope someone has a solution for that
Thanks in advance.
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/7fb8b6f0-c417-4b77-8f51-77aa04fb9d04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
