I want a node to be able to print the recipes that were or were to be executed during a chef-client run, including recipes that come from “include_recipe” statements.
I can’t just use the run list because that is not fully expanded. I have seen various attempts at doing this, but none seem to work well or completely.
–
Stephen Corbesero, DevOps Engineer
Synchronoss - Mobile Innovation for a Connected World
stephen.corbesero@synchronoss.com | www.synchronoss.com
The minitest handler cookbook handles the "were executed" case like so:
https://github.com/btm/minitest-handler-cookbook/blob/master/libraries/test_loader.rb#L99-L104.
Not sure if this falls into one of the various attempts that falls short,
but passing it along in case it helps.
On Wed, Jun 18, 2014 at 8:47 AM, Stephen Corbesero <
Stephen.Corbesero@synchronoss.com> wrote:
I want a node to be able to print the recipes that were or were to be
executed during a chef-client run, including recipes that come from
“include_recipe” statements.I can’t just use the run list because that is not fully expanded. I have
seen various attempts at doing this, but none seem to work well or
completely.--
Stephen Corbesero, DevOps Engineer
Synchronoss - Mobile Innovation for a Connected World
In the latest chef-client, the recipes node attribute includes recipes executed via include_recipe. Of course, chef-client doesn’t know the future, so if you look at this while chef-client is compiling your recipes, there could be a recipe that will be loaded later but doesn’t appear in that attribute.
--
Daniel DeLeo
On Wednesday, June 18, 2014 at 5:53 AM, David Petzel wrote:
The minitest handler cookbook handles the "were executed" case like so: https://github.com/btm/minitest-handler-cookbook/blob/master/libraries/test_loader.rb#L99-L104. Not sure if this falls into one of the various attempts that falls short, but passing it along in case it helps.
On Wed, Jun 18, 2014 at 8:47 AM, Stephen Corbesero <Stephen.Corbesero@synchronoss.com (mailto:Stephen.Corbesero@synchronoss.com)> wrote:
I want a node to be able to print the recipes that were or were to be executed during a chef-client run, including recipes that come from “include_recipe” statements.
I can’t just use the run list because that is not fully expanded. I have seen various attempts at doing this, but none seem to work well or completely.
--
Stephen Corbesero, DevOps Engineer
Synchronoss - Mobile Innovation for a Connected World
stephen.corbesero@synchronoss.com (mailto:stephen.corbesero@synchronoss.com) | www.synchronoss.com (http://www.synchronoss.com)
On Wed, 18 Jun 2014 07:57:06 -0700 Daniel DeLeo dan@kallistec.com
wrote:
In the latest chef-client, the
recipesnode attribute includes
recipes executed viainclude_recipe. Of course, chef-client doesn’t
know the future, so if you look at this while chef-client is
compiling your recipes, there could be a recipe that will be loaded
later but doesn’t appear in that attribute.
But a recipe can fetch the resulting recipes-list from the last run with
a search for itself on the chef server. Doesn't work with chef-solo
though...