-
Notifications
You must be signed in to change notification settings - Fork 54
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
HTTP/HTTPS proxy support? #201
Comments
|
@wrightp if this is something that I can assist with, please let me know. I'd be happy to see this move along, as installing chef client behind a firewall has never really been easy and the value this feature would provide is beyond measure. |
@iancward I have some time this week to start a PR. Proxy support is a required feature for some work coinciding with Kitchen changes. I'll dig in and see the best way to approach this and I'll mention you on the PR. |
As described in the referenced chef_client_updater issue proxy support in the powershell script is broken in that it overrides any environment variable with blank if no value is provided in the options hash 😦 |
https://github.com/chef-cookbooks/chef_client_updater/blob/master/CHANGELOG.md#320-2018-01-22 claims that version 3.9.0 of this gem provides proxy support. Is that accurate? I don't see proxy support anywhere in this repository's changelog. |
@wrightp it looks like I accidentally un-assigned you or that my comment changed something with the assignment. |
@tas50 @lamont-granquist, It looks like proxy support is added in PR #242 . We may need to close this issue. |
Hello,
I support infrastructure that is behind a firewall which does not allow direct access to the internet. However, we do have HTTP proxies available, and I'm attempting to use Mixlib::Install via pry to make sure it actually works.
Unfortunately, it doesn't not appear to actually work.
My ultimate hope here is that this gem will support http/s proxy and that the chef_client_updater cookbook can be configured to use mixlib::install with a proxy. That way, we can avoid having to use a yum repository mirror of packages.chef.io and have our servers install chef (somewhat) directly via omnitruck.
The text was updated successfully, but these errors were encountered: