Allow to set chef-zero-host when using the Chef Zero provider #549
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.
This fix introduces a new configuration option chef_zero_host for the
Chef Zero provider. Using this option, you can bind the Chef Zero
server to another address than localhost.
Being able to set the host is nice when using test kitchen to test cookbooks that create docker containers or VMs which in turn use chef to configure themselves. This way the "nested" Chef clients inside the containers or VMs can access Test Kitchen's Chef Zero server, too.
Example kitchen.yml: