Skip to content
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

Destroy vagrant hosts only if Vagrantfile exists #77

Merged
merged 1 commit into from Nov 21, 2013

Conversation

hunner
Copy link
Member

@hunner hunner commented Nov 20, 2013

The new vagrant destroy --force run during the vagrant hypervisors provision method added in #48 seems to fail if no Vagrantfile has ever been created for a nodeset. This fixes that.

@anodelman
Copy link
Contributor

Please update spec tests.


it "destroys an existing set of hosts before provisioning" do
File.stub(:file?).and_return('/tmp/nodeset.yml')
vagrant.should_receive( :vagrant_cmd ).with( "destroy --force" ).once
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are using FakeFS for file functions in our spec tests. Can you do a quick re-write with that?

The new `vagrant destroy --force` run during the vagrant hypervisors
`provision` method added in voxpupuli#48 seems to fail if no `Vagrantfile` has
ever been created for a nodeset. This fixes that.
anodelman added a commit that referenced this pull request Nov 21, 2013
Destroy vagrant hosts only if Vagrantfile exists
@anodelman anodelman merged commit 9bc67be into voxpupuli:master Nov 21, 2013
@hunner hunner deleted the destroy_nothing branch November 21, 2013 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants