-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support --no-destroy-on-error for up() #122
Comments
Hi @eighthave, you basically got a PR all done already, want to submit one as well? :) |
sure I can do it, if it is something you'd want to merge
|
Sure thing, seems like an option that can come in handy. |
I just ran into this today, and it would be really helpful to still have. I was testing Talos with vagrant and using ansible to make API calls to it. When I got to build it in molecule, there is always a failure to log in because it doesn't support ssh. If I could just tell it to ignore the failure everything would work. As it is now (with libvirt) it deletes the VM and I can't get around it. |
vagrant up
has the option--no-destroy-on-error
which is very helpful for debugging. It would be nice if python-vagrant supported it, and it looks simple to add. I would just adddestroy_on_error=True
as an arg tovagrant.up()
then pass the right arg depending on that value, something like:Here's a reference:
The text was updated successfully, but these errors were encountered: