kienan
/
vagrant-hostmanager
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

update README describing new running order on 'vagrant up' 

as discussed on #73.
This commit is contained in:
Paulo Bittencourt 2014-05-30 12:52:45 -04:00
parent 8948648cbc
commit a9e059e52b
1 changed files with 26 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
README.md
View File

@ -6,7 +6,16 @@ resolution of multi-machine environments deployed with a cloud provider
where IP addresses are not known in advance. where IP addresses are not known in advance.
*NOTE:* Version 1.1 of the plugin prematurely introduced a feature to hook into *NOTE:* Version 1.1 of the plugin prematurely introduced a feature to hook into
commands other than `vagrant up` and `vagrant destroy`. Version 1.1 broke support for some providers. Version 1.2 reverts this feature until a suitable implementation supporting all providers is available. commands other than `vagrant up` and `vagrant destroy`. Version 1.1 broke support
for some providers. Version 1.2 reverts this feature until a suitable implementation
supporting all providers is available.
***Potentially breaking change in v1.5.0:*** the running order on `vagrant up` has changed
so that hostmanager runs before provisioning takes place. This ensures all hostnames are
available to the guest when it is being provisioned
(see [#73](https://github.com/smdahlen/vagrant-hostmanager/issues/73)).
Previously, hostmanager would run as the very last action. If you depend on the old behavior,
see the [provisioner](#provisioner) section.
Installation Installation
------------ ------------
@ -61,15 +70,26 @@ Vagrant.configure("2") do |config|
end end
``` ```
As a last option, you can use hostmanager as a provisioner. ### Provisioner
This allows you to use the provisioning order to ensure that hostmanager
runs before or after provisioning. The provisioner will collect hosts from
boxes with the same provider as the running box.
Use: Starting at version 1.5.0, hostmanager runs before any provisioning occurs. If you
would like hostmanager to run after or during your provisioning stage,
you can use hostmanager as a provisioner. This allows you to use the provisioning
order to ensure that hostmanager runs when desired. The provisioner will collect
hosts from boxes with the same provider as the running box.
Example:
```ruby ```ruby
# Disable the default hostmanager behavior
config.hostmanager.enabled = false
# ... possible provisioner config before hostmanager ...
# hostmanager provisioner
config.vm.provision :hostmanager config.vm.provision :hostmanager
# ... possible provisioning config after hostmanager ...
``` ```
Custom IP resolver Custom IP resolver