+1 for global defaults for resources!
From: Daniel DeLeo <email@example.com:firstname.lastname@example.org>
Reply-To: "email@example.com:firstname.lastname@example.org" <email@example.com:firstname.lastname@example.org>
Date: Wednesday, September 11, 2013 11:37 AM
To: "email@example.com:firstname.lastname@example.org" <email@example.com:firstname.lastname@example.org>
Subject: [chef] Re: rubygems source
On Wednesday, September 11, 2013 at 11:30 AM, Moser, Kevin wrote:
A little discussion point here. We run into an issue quite frequently with cookbooks from the community that assume access to rubygems.orghttp://rubygems.org, where we host an internal mirror and our servers don’t have access to rubygems.orghttp://rubygems.org.
We tend to create wrapper cookbooks and rewind a bunch of resources or add new recipes to the community cookbook just to let us specify new sources. Wanted to have some discussion around a more chef wide style override. Created a ticket for this and would be interested to have folks have some conversation on it and see what might be a good approach for everyone.
For the immediate term we’ve been handling stuff like this via Chef::Config options, so I think this could be okay for a future 11.x release. In the longer term (Chef 12ish, or maybe a “big” feature release of 11.x) we’d like to implement a means to configure global defaults for resource attributes.