vagrant destroy exits with 0 if confirmation is declined #923

skade opened this Issue May 9, 2012 · 3 comments


None yet

3 participants

skade commented May 9, 2012

vagrant destroy returns 0 if confirmation is declined. Nothing big, but its a bit strange:

$ vagrant destroy && vagrant up
Are you sure you want to destroy the 'base' VM? [Y/N] N
The VM 'base' will not be destroyed, since the confirmation
was declined.
[base] VM already created. Booting if it's not already running...
[base] Clearing any previously set forwarded ports...

A related problem is that vagrant also exist with 0 if the command is not found--vagrant up will similarly execute if you do:

$ vagrant destroyp && vagrant

(I've made a pull request (#1336) to fix the "invalid command" problem, not quite sure where to start with the "confirmation not given" problem.)



@mitchellh mitchellh closed this Jul 11, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment