Prevent wiping of addresses of other providers #169
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add information that the usual sudo group on Fedora/Red Hat systems is named 'wheel'. Generalize instructions to make them distribution-agnostic. Add step on adding yourself to the administrator group.
Hostmanager can only deal with one provider at a time. If you `vagrant up` a virtualbox vm, then an aws, all information of your virtulabox vm will be removed from /etc/hosts on the host. By adding the provider type in the header/footer of the hostmanager section of /etc/hosts, we can have one section per provider and thus keep all machines, no matter the provider.
|
This is only a partial solution - please expand. |
|
Hi, Would you mind expanding on why this is only partial? :) My understanding is that vagrant-hostmanager when updating a host file basically recreates its block from scratch every time. As Vagrant cannot manage more than one provider per run, this means that if I am dealing with a say virtualbox VM and hostmanager wipe outs all vagrant entries, there is no way to find again VMs backed up by another provider, AWS for instance. My patch creates one block per provider, meaning that they all are independent and can be managed individually, fully recreated as required without impacting the other blocks. Cheers, |
…-sudo Improve README.md for Passwordless sudo.
…permissions-on-etc-hosts Ensure permissions on /etc/hosts stay intact
…nage-guest-flag Fix for issue devopsgroup-io#108, add a flag to manage guest hosts file.
Hostmanager can only deal with one provider at a time. If you `vagrant up` a virtualbox vm, then an aws, all information of your virtulabox vm will be removed from /etc/hosts on the host. By adding the provider type in the header/footer of the hostmanager section of /etc/hosts, we can have one section per provider and thus keep all machines, no matter the provider.
…tion make separating aliases into multiple lines optional Conflicts: test/Vagrantfile
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hostmanager can only deal with one provider at a time.
If you
vagrant upa virtualbox vm, then an aws, all informationof your virtualbox vm will be removed from /etc/hosts on the host.
By adding the provider type in the header/footer of the hostmanager
section of /etc/hosts, we can have one section per provider and
thus keep all machines no matter the provider.