Chef integration needs option to set 'http_proxy' and 'no_proxy' configurations in the nodes 'client.rb' before bootstrap

Josh P Schneider's Avatar

Josh P Schneider

21 Oct, 2015 11:22 PM

there is an issue when Scalr is used with chef, and the cloud nodes that scalr/chef is deploying to is behind proxies. In these cases chef will need to have 'http_proxy'/https_proxy/no_proxy configured so the runlist that is specified in the scalr setup can be run. So far it is not possible to deploy/add these configurations in the phase 'OnHostInit' as that /etc/chef/client.rb file does not exist. and the next phase BeforeHostUp scalr has already attempted to bootstrap/run the runlist. Is there a way/method that we can deploy these proxy configurations?

  1. Support Staff 1 Posted by Marat Komarov on 22 Oct, 2015 10:23 AM

    Marat Komarov's Avatar

    Currently it's not possible to specify custom options in client.rb. We understand the need in this feature, so added it into our roadmap.

  2. marc closed this discussion on 22 Jul, 2016 08:33 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac