Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


auto-patch (2) Versions 0.1.10

Configures node for automatic patching.

cookbook 'auto-patch', '~> 0.1.10', :supermarket
cookbook 'auto-patch', '~> 0.1.10'
knife supermarket install auto-patch
knife supermarket download auto-patch
Quality 71%

chef-auto-patch Build Status


Chef Cookbook for automatically patching nodes on a specific schedule (weekday,
hour, and minute). Handles weekly or monthly patching routines with or without
node splay for large environments. Can automatically prepare node for true patch
window by cleaning and pre-downloading packages, which speeds up patch process
and can help guarantee meeting patching timeframes.

If you're looking for daily upgrades on Ubuntu, check out the
unattended-upgrades package
and a corresponding cookbook.
(/ht @hectcastro for this information).



  • RedHat 6.3 (Santiago)
  • Ubuntu 12.04 (Precise)


  • cron


  • node["auto-patch"]["disable"] - defaults to false
  • node["auto-patch"]["hour"] - defaults to 3
  • node["auto-patch"]["minute"] - defaults to 0
  • node["auto-patch"]["monthly"] - auto patching occurs once a month on the corresponding textual week number ("first","second",etc) and weekday ("monday","tuesday",etc), overridden by node["auto-patch"]["weekly"], defaults to "first sunday"
  • node["auto-patch"]["reboot"] - reboot automatically after patching, defaults to true
  • node["auto-patch"]["splay"] - seconds of random delay before beginning, defaults to 0
  • node["auto-patch"]["weekly"] - auto patching occurs once a week on the corresponding textual weekday ("monday","tuesday",etc), overrides node["auto-patch"]["monthly"], defaults to nil

Patch Preparation

  • node["auto-patch"]["prep"]["clean"] - cleans updater cache files, defaults to true
  • node["auto-patch"]["prep"]["disable"] - defaults to true
  • node["auto-patch"]["prep"]["hour"] - defaults to 2
  • node["auto-patch"]["prep"]["minute"] - defaults to 0
  • node["auto-patch"]["prep"]["monthly"] - auto patching prep occurs once a month on the corresponding textual week number ("first","second",etc) and weekday ("monday","tuesday",etc), overridden by node["auto-patch"]["prep"]["weekly"], defaults to "first sunday"
  • node["auto-patch"]["prep"]["splay"] - seconds of random delay before beginning, defaults to 1800
  • node["auto-patch"]["prep"]["weekly"] - auto patching prep occurs once a week on the corresponding textual weekday ("monday","tuesday",etc), overrides node["auto-patch"]["prep"]["monthly"], defaults to nil
  • node["auto-patch"]["prep"]["update_updater"] - updates apt or yum before actual patching occurs, defaults to true


  • recipe[auto-patch] configures automatic patching


  • Change any attributes to fit your patching cycle
  • If using auto patch preparation, ensure it starts before auto patch (remember any splay!)
  • Add recipe[auto-patch] to your node's run list

Weekly automatic patching

Just use the node["auto-patch"]["weekly"] attribute to override the monthly
setting. Don't forget to add appropriate node["auto-patch"]["prep"]["weekly"]
if you're using automatic patch preparation.

Automatic patching of large numbers of nodes

If you're auto patching many nodes at once, you have two attributes you can
optionally add to prevent denial of service against your network, update
server(s), and resources:
* Adding node["auto-patch"]["splay"]
* Setting node["auto-patch"]["prep"]["disable"] to false (along with setting
associated prep attributes to meet your patch cycle)

Using roles to specify auto patching groups

If you'd like to specify groups of nodes for auto patching, you can setup roles.

Say you want to auto patch some nodes at 8am and some at 10pm on your monthly
"patch day" of the fourth Wednesday every month.

If you have a base role (you do, right?), you can save duplicating attributes
and specify some base information first:

"auto-patch" => {
  "monthly" => "fourth wednesday",
  "prep" => {
    "disable" => false,
    "hour" => 7,
    "monthly" => "fourth wednesday"

Example role that then could be added to 8am nodes:

name "auto-patch-0800"
description "Role for automatically patching nodes at 8am on patch day."
  "auto-patch" => {
    "hour" => 8

Example role that then could be added to 10pm nodes:

name "auto-patch-2200"
description "Role for automatically patching nodes at 10pm on patch day."
  "auto-patch" => {
    "hour" => 22

Disabling automatic patching

  • Specify node["auto-patch"]["disable"] to true
  • If necessary, specify node["auto-patch"]["prep"]["disable"] to true
  • Run chef-client on your node

Testing and Development

Here's how you can quickly get testing or developing against the cookbook thanks to Vagrant and Berkshelf.

vagrant plugin install vagrant-berkshelf
vagrant plugin install vagrant-cachier
vagrant plugin install vagrant-omnibus
git clone git://
cd chef-auto-patch
vagrant up BOX # BOX being centos5, centos6, debian7, fedora18, fedora19, fedora20, freebsd9, ubuntu1204, ubuntu1210, ubuntu1304, or ubuntu1310

You can then SSH into the running VM using the vagrant ssh BOX # BOX being centos6 or ubuntu1204 command.
The VM can easily be stopped and deleted with the vagrant destroy
command. Please see the official Vagrant documentation
for a more in depth explanation of available commands.


Please use standard Github issues/pull requests.

License and Author

Author:: Brian Flad (

Copyright:: 2012-2013

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.


  • Bugfix: #2 check if constants are already defined


  • RHEL 5 support with correct package name


  • Fixed day of month logic for later week specifications


  • Removed cookbook attribute from cron_d resources since was fixed in cron@1.2.2


  • Fixed typo in default recipe for platform_family detection


  • Fixes in default recipe for WARN: Setting attributes without specifying a precedence is deprecated


  • Defaulted auto-patch splay to 0 since setting is only for large numbers of nodes


  • Refactored next_monthly_*_date functions into next_monthly_date


  • Convert unnecessary String attributes to Fixnum


  • Only install yum-plugin-downloadonly if auto-patch prep is enabled.


  • Initial release with tested Red Hat 6.3 support


  • Initial cookbook building and testing.

Collaborator Number Metric

0.1.10 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric

0.1.10 passed this metric

Foodcritic Metric

0.1.10 failed this metric

FC064: Ensure issues_url is set in metadata: auto-patch/metadata.rb:1
FC065: Ensure source_url is set in metadata: auto-patch/metadata.rb:1
FC066: Ensure chef_version is set in metadata: auto-patch/metadata.rb:1
FC069: Ensure standardized license defined in metadata: auto-patch/metadata.rb:1
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric

0.1.10 passed this metric

Supported Platforms Metric

0.1.10 passed this metric

Testing File Metric

0.1.10 passed this metric

Version Tag Metric

0.1.10 passed this metric