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

RSS

chef-updater (8) Versions 2.0.0

Application cookbook which provides a custom resource for updating Chef Client.

Policyfile
Berkshelf
Knife
cookbook 'chef-updater', '= 2.0.0', :supermarket
cookbook 'chef-updater', '= 2.0.0'
knife supermarket install chef-updater
knife supermarket download chef-updater
README
Dependencies
Changelog
Quality 100%

chef-updater cookbook

Build Status
Code Quality
Test Coverage
Cookbook Version
License

Application cookbook which provides a simple recipe for updating
the Chef Client package on an instance.

This cookbook supports updating a minimum Chef version of 12.1.0 and
above
. The inspiration for this cookbook comes from the
Omnibus Updater cookbook which specifically targets the Omnitruck
API for obtaining Chef client artifacts. Unfortunately those of us in
the enterprise likely already have our own mechanisms for distributing
packages, and most of the time they integrate very well with the
operating system's package manager.

Platforms

This cookbook is tested and used in production on the following
platforms:

  • RHEL 5/6/7
  • CentOS 5/6/7
  • Ubuntu 12.04/14.04
  • Windows 2008r2/2012r2
  • AIX 7.1
  • Solaris 11.2

Basic Usage

Because of how this cookbook short-circuits the Chef convergence it
cannot be run at the compile phase of the run. It should be included
as early as possible in a node's expanded run-list in order to stop a
near-immediately when the client is upgraded.

Resource/Provider

The default recipe passes in some tuning attributes to the
resource/provider. These attributes should only be tweaked if you
understand what you're doing. It is important to note that by default
the package_source is nil. This means that the system package
provider will attempt to grab it from a potential package repository
(if configured).

Additionally, the package_version should be the semantic version of the
Chef Client that you would like the node to be upgraded to. In the background
a helper transforms this into the version necessary for the platform that
the provider is operating on (e.g. 12.4.0-1.el5).

Property Type Description Default
package_name String Name of package to be upgraded. 'chef'
package_version String Version of the package to be upgraded. '12.9.38'
package_source [String, NilClass] Remote URL of where package resides. nil

Dependent cookbooks

poise ~> 2.6
chef-sugar >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Change Log

Unreleased

Full Changelog

Merged pull requests:

  • Add windows provider for chef_updater resource. #6 (johnbellone)
  • Get the windows portion to correctly uninstall the old version #5 (jjustice6)

v1.1.2 (2016-02-03)

Full Changelog

Merged pull requests:

  • Check package version by using >= constraint #4 (sh9189)

v1.1.1 (2015-11-20)

Full Changelog

v1.1.0 (2015-11-20)

Full Changelog

v1.0.2 (2015-10-27)

Merged pull requests:

  • Set timeout and package_options correctly #2 (sh9189)
  • Support timeout,options #1 (sh9189)

* This Change Log was automatically generated by github_changelog_generator

Collaborator Number Metric
            

2.0.0 passed this metric

Foodcritic Metric
            

2.0.0 passed this metric