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

Set proxy settings for chef-solo provisioning #6

Closed
laradji opened this issue Mar 20, 2013 · 1 comment
Closed

Set proxy settings for chef-solo provisioning #6

laradji opened this issue Mar 20, 2013 · 1 comment

Comments

@laradji
Copy link

laradji commented Mar 20, 2013

Hi,

I'am not sure if this his the good place to ask for this feature, but it will really help to speed up testing if we can set proxy_settings for the chef-solo to be run.

@fnichol
Copy link
Contributor

fnichol commented Jul 22, 2013

There is some support for this in Test Kitchen proper. If you set http_proxy and/or https_proxy in a driver_config: block, these environment variables will be in the remote SSH commands' environment. Usually this covers curl, wget, chef, apt, and a few others.

For example:

---
driver_plugin: vagrant
driver_config:
  http_proxy: http://10.0.0.1:8123
  https_proxy: https://10.0.0.1:8123

Note that you'd need to have an HTTP caching proxy server on that host and port. I've run a local polipo instance on my workstation and used the public IP address of it (stuck in a .kitchen.local.yml file to override defaults).

Hope this helps!

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

No branches or pull requests

2 participants