[chef] Re: Re: Re: http_proxy not work for recipe_url?

[Daniel DeLeo < >]

On Friday, September 6, 2013 at 2:52 PM, Brian J. Murrell wrote:

On 13-09-06 03:28 PM, Daniel DeLeo wrote:

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.

So it was not extended to fetching the cookbooks also, just the .json file?

Yep. The json file gets fetched by Chef::REST so it picked up proxy support for free when that was added, whereas the recipe_url is opened by ruby's openuri, which doesn't support parodying (or relies on ENV vars for configuring them, I haven't looked).

If you're interested in patching, the one tricky bit to note is that openuri supports FTP, so you'd need to make sure that still worked. If you're super motivated, I think that part of the codebase could use some heavy refactoring, but a patch that just solves the problem at hand would be welcome, too.

 

Out of curiosity, why distribute cookbooks this way?

As opposed to what other way, assuming the cookbooks are sitting on an

HTTP server somewhere. Or maybe they are not. How else would you

suggest I distribute them if I don't want to go the whole chef-server route?

Honestly, I have no idea how chef-solo users distribute their cookbooks, I'd assumed most would use git and run chef-solo with some wrapper to fetch any updates before chef-solo starts.

Also, chef-server is pretty easy to install nowadays, what turns you off about it?

 

b.

-- 

Daniel DeLeo