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

Don't attempt to update machines that are not running during vagrant up #202

Merged

Conversation

austinlparker
Copy link
Contributor

Fixes #200

Currently, when running vagrant up after vagrant halt (or some other combination of steps that leaves you with powered off but provisioned vagrant machines), the hostmanager plugin will attempt to update the hostsfile on each machine. However, it does this by querying the vagrant environment for created machines. This PR changes the behavior to have hostmanager only attempt to update the hosts file on running vagrant machines during vagrant up.

austinlparker and others added 2 commits July 5, 2016 11:14
@austinlparker austinlparker changed the title Don't attempt to update machines that are not running during vagrant up Don't attempt to update machines that are not running during vagrant up Jul 5, 2016
@seth-reeser
Copy link
Member

Thank you for the pull request @austinlparker ! This has been low hanging fruit for quite some time - beat us to it! Looks good. I'm going to run through some QA and once passed will publish a new release.

@austinlparker
Copy link
Contributor Author

Hey Seth, any word on this?

@seth-reeser
Copy link
Member

Should be a day or two - stay tuned.

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