[chef] Re: Re: Re: Re: Re: Re: Re: Chef Client 12.1.0 Released

[Lamont Granquist < >]

For a chef specific piece of code like that which is only designed to mangle the chef resource collection, there's zero benefit to rubygems because there's no utility outside of chef, so distribution via libraries in cookbooks is a much better solution (using the tool for the job).  For gems like nokogiri it obviously makes sense to have those as gems, but in those use cases you're much more likely to be able to wrap the use of that gem in a provider.

On 3/3/15 6:45 PM, Peter Burkholder wrote:

" type="cite">

Why is depending upon a cookbook preferable to compile-time chef_gem installation?

I completely understand that we don't want a build-essentials race occurring before our Chef run can even get off the ground, but isolating useful code into Cookbooks instead of the larger Ruby ecosystem doesn't seem to the way forward either.

On Tue, Mar 3, 2015 at 7:10 PM, Lamont Granquist < " target="_blank"> > wrote:

Yeah, since you want to use the gem at compile time in recipe code by design its one use case where forcing compile time is actually what you want.  At the same time its trivial to do chef-rewind without the chef-rewind gem which can avoid that problem entirely:

# override the redis.conf template from the redis cookbook with my wrapper cookbook
resources(template: "#{node['redis']['conf_dir']}/redis.conf").cookbook(cookbook_name)

You can also drop the chef-rewind code into a cookbook library file and include it that way and avoid the gem require, which is a much better pattern for distributing library code to be used in chef recipes.

On 3/3/15 3:28 PM, Morgan Blackthorne wrote:

I think that chef-rewind is a bit of a corner case, and there are certainly some people that think it's an anti-pattern, and others who use it liberally.

--

~*~ StormeRider ~*~

"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS

On Tue, Mar 3, 2015 at 3:24 PM, Nathan Williams < " target="_blank"> > wrote:

> requiring gems in recipe code was bad practice

is there any background reading on this? i find we use chef_gem for chef-rewind and `require 'chef/rewind'` quite often, but this would seem to indicate there's a better practice. if so, i'd love to hear more about it as this is the first time it's crossed my radar.

On Tue, Mar 3, 2015 at 1:43 PM, Jeff Byrnes < " target="_blank"> > wrote:

A potential solution might be to wrap those sorts of things in backticks, to avoid triggering the italicizing behavior (which I suspect is Markdown of some sort), and preserve these programmy things.

-- 

Jeff Byrnes
@thejeffbyrnes

Lead DevOps Engineer

EverTrue

704.516.4628

On March 3, 2015 at 2:57:03 PM, Morgan Blackthorne ( " target="_blank"> ) wrote:

I think that the blog interpreting underscores as italics is a bit wonky when so many chef things are blah_blah2. I'm not sure if it just needs to be edited to syntax-highlight/format those keywords, or if you're better off disabling that auto-italic feature, but the text as stands is definitely confusing visually, even if I can intuit what is meant.

--

~*~ StormeRider ~*~

"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS

On Tue, Mar 3, 2015 at 10:43 AM, Jay Mundrawala < " target="_blank"> > wrote:

Hi Chefs,

We've just released Chef 12.1.0. You can read more about it at https://www.chef.io/blog/2015/03/03/chef-12-1-0-released/.

Thanks,

Jay

--

Peter Burkholder — Customer Success Engineer

Unavailability: Travel March 2-3; Vacation March 16-20; ChefConf March 30-April 3

301-204-5767 –  " target="_blank">  – my: Linkedin  Twitter  Calendar

CHEF CHEF.IO

TM

chef.io   Blog   Facebook   Twitter   Youtube