Set default proxy configuration for Chef provisioners #21
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
Set proxy settings for all Chef provisioners based on `config.proxy.http` etc. The provisioner specific configuration still takes precedence. Chef configuration wants the (optional) username and password in separate config keys, so we need to extract them from our URI.
|
@schlamar, here is the first attempt to implement #19. Could you give it a spin? Installation instructions (also found in the wiki): git clone https://github.com/tmatilai/vagrant-proxyconf.git
cd vagrant-proxyconf
git checkout chef-provisioners
bundle
bundle exec rake build
vagrant plugin install pkg/vagrant-proxyconf-*.gem |
|
Worked like a charm 👍 |
tmatilai
added a commit
that referenced
this pull request
Sep 10, 2013
Set default proxy configuration for Chef provisioners Fixes #19
|
Cool stuff! Like! 👍 |
Closed
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.
Set proxy settings for all Chef Solo and Chef Client provisioners based on
config.proxy.httpetc. The provisioner specific configuration still takes precedence.Chef configuration wants the (optional) username and password in separate config keys, so we need to extract them from our URI.
Fixes #19.