This is what I originally posted on the #vagrantup Freenode IRC channel: BogdanS heya! a quick question: I am using vagrant with the aws plugin (for aws as provider). If I want to keep the instance around for a long time (or forever), after being spawned with vagrant up --provider=aws, how could I instruct vagrant to just forget about the instance - so that a subsequent vagrant up would create a new one and any vagrant destroy (or anything else) in between would not do anything (pretty much acting like it's not tracking any instance) is rm -Rf .vagrant (removing the .vagrant folder) enough? or is there a more elegant approach? → favetelinguis has joined BogdanS and if rm -Rf .vagrant is the solution, is there something else that needs removing/changing, besides that folder?
Let me know if what I wrote is explicit enough or it requires more explanations. I have a feeling that the answer is not vagrant-aws-specific, that's why I posted it here. -- 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/7e4069c3-7d6d-432a-8d42-8b2a5a4ac233%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
