I explore that, thanks!
From: Tensibai [mailto:firstname.lastname@example.org]
Sent: Wednesday, March 11, 2015 1:09 PM
Subject: [chef] Re: RE: Re: Which cookbook version wins in this case?
You may use a report handler for this:
An example one with this use case is available on the doc site here: http://docs.chef.io/handlers.html#cookbook-versions-rb
Le 2015-03-11 17:39, Fouts, Chris a écrit :
Thanks. I’m testing this now. How do I show the cookbooks’ version that converged on the node? “knife node show” of course shows the run list, but not the cookbooks’ versions?
From: Taylor Price [mailto:email@example.com]
Sent: Tuesday, March 10, 2015 10:46 PM
Subject: [chef] Re: Which cookbook version wins in this case?
1.0.0 should win. It satisfies all requirements, where 1.2.0 does not.
On Mar 10, 2015, at 2:23 PM, Fouts, Chris <Chris.Fouts@Sensus.commailto:Chris.Fouts@Sensus.com> wrote:
Say I have a web_role cookbook, and its metadata.rb file looks like this
depends ‘apache’, '= 1.0.0’
depends ‘webapp’, '= 1.0.0’
depends ‘someapp’, ‘= 1.0.0’
…and my webapp cookbook’s metadata.rb files look like…
depends ‘apache’ # Not pinned to any version
On the server I have firstname.lastname@example.org:email@example.com and firstname.lastname@example.org:email@example.com versions of the apache cookbook
Now if I add my web_role cookbook to my node’s run list, which version of the apache cookbook will converge, 1.0.0 defined in the web_role’s metadata.rb file, or the 1.2.0, latest version on the chef server?