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

Propagate settings to chef? #19

Closed
schlamar opened this issue Sep 5, 2013 · 3 comments · Fixed by #21
Closed

Propagate settings to chef? #19

schlamar opened this issue Sep 5, 2013 · 3 comments · Fixed by #21

Comments

@schlamar
Copy link

schlamar commented Sep 5, 2013

Is it possible to propagate proxy settings to chef_solo and chef_client provisioners? See http://serverfault.com/a/536596/126460 on how you would set them manually.

@tmatilai
Copy link
Owner

tmatilai commented Sep 5, 2013

Hi Marc,

sure it should be possible. I was in the impression that Chef would honor the environment variables, but to be honest I haven't verified. And looks like I was wrong...

I'll take a look later today. Thanks for the feedback!

@schlamar
Copy link
Author

schlamar commented Sep 5, 2013

I was in the impression that Chef would honor the environment variables

Sadly not: https://tickets.opscode.com/browse/CHEF-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel

I'll take a look later today. Thanks for the feedback!

Great!

@tmatilai
Copy link
Owner

tmatilai commented Sep 5, 2013

I stand corrected. =)
Agreed, we should set also the Chef proxy settings when config.http is used. Thanks again for the idea and investigation!

tmatilai added a commit that referenced this issue Sep 10, 2013
Set default proxy configuration for Chef provisioners

Fixes #19
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 a pull request may close this issue.

2 participants