Skip to content
Some Chef cookbook/resource summary handlers
Ruby HTML Perl 6
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

summary-handlers Cookbook

This cookbook includes three report handlers.

Cookbook Summary

The cookbook summary is a list of cookbooks that have been pulled down as part of the run list (or dependencies).

Recipe Summary

The recipe summary is designed for situations for helping to see if a community cookbook has been added as a dependency but no longer required as it lists all recipes and marks those that have not been loaded.

Resource Summary

The resource summary is for larger cookbooks with a lot of resources to summerise the resources that have been loaded into the resource queue. The report has two modes, output the resources grouped by type or by cookbook recipe. There are two sorting options

  • By Type; the output is resource type followed by recipe name
  • By Cookbook; the output is recipe name followed by resources

The overall intention of the summary handlers is for development time using Test Kitchen, not production but it could be added as part of a regular run list.

Output is using puts rather than Chef::Log, if you fork and change the code to use Chef::Log and there is no output check your Log level!

If the cookbook proves to be popular I will distribute the core as a gem to make it even easier to install and use!


Tested with ChefDK 0.62



Key Type Description Default
['summary-handlers']['cookbook-summary-report'] boolean If default recipe called add cookbook-summary true
['summary-handlers']['recipe-summary-report'] boolean If default recipe called add recipe-summary true
['summary-handlers']['resource-summary-report'] boolean If default recipe called add resource-summary true


NB: Key is abbreviated, the key path starts with ['summary-handlers']['resource-summary'] Simple add below for full attribute name, i.e ['summary-handlers']['resource-summary']['report_type']

Key Type Description Default
['report_type'] Symbol :by_cookbook or :by_type :by_cookbook
['report_format'] Symbol :template, :json or :yaml :template
['updated_only'] boolean Show only updated resources false
['user_filter'] Proc Proc for user filter nil

The user_filter will allow you to filter resource summary to just the resources you are interested in, the filter can be any valid resouce property.

Example setting for default['summary-handlers']['resource-summary']['user_filter'] = proc {|resource| resource.method == user_criteria}

This setting will need to be done in your wrapper cookbook attributes or recipe file as it requires Ruby proc.


If using Test Kitchen and Berkshelf then add to your Berksfile, summary_handlers is available on Git or Public Chef Supermarket.


cookbook 'summary_handlers', git: ''

Public Supermarket

source ''


cookbook 'summary_handlers'

Change you test suite run list to include summary handlers (.kitchen.yml or .kitchen.local.yml)

- name: default
  run_list: ["recipe[summary_handlers]","recipe[my_cookbook]"]
  attributes: { ... }

Use the attributes section of the test suite to get the desired behavior.

Alternatively, you can add this cookbook as a dependency in your cookbook, to do that update your cookbooks metadata file

depends 'summary_handlers'

Then add an include_recipe in default.rb (or one of the recipes used by your cookbook)

include_recipe 'summary_handlers


Please see and read the

License and Authors

Please see LICENSE Authors: Chris Sullivan

You can’t perform that action at this time.