[chef] Re: http_proxy not work for recipe_url?

[Daniel DeLeo < >]

On Thursday, September 5, 2013 at 1:39 PM, Brian J. Murrell wrote:

I have a solo.rb file with the following in it:

json_attribs " /path/node.json">https://u: /path/node.json"

recipe_url " /path/cookbooks.tar.gz">https://u: /path/cookbooks.tar.gz"

http_proxy "http://proxy:3128"

https_proxy "http://proxy:3128"

# chef-solo

seems to be using the proxy to fetch the node.json file but it seems to

be trying to connect directly to "server" to fetch the cookbooks.tar.gz

file.

Is this a known issue/limitation of the proxy support in chef? I would

have thought it would be generic for all HTTP activities.

This feature is kinda hacked in to allow for simple bootstrapping cases, such as the old chef-server install via chef-solo. I'd consider it a bug.

Out of curiosity, why distribute cookbooks this way?

-- 

Daniel DeLeo