Generate README.md docs from Chef cookbook attributes files

Self-contained, easy-setup, fast-start in-memory Chef Community Site for testing.

A small collection of Chef hacks and workarounds.

Basic datadog integration

# Chef Data Region ## Description Chef Data Region extends the `Chef::DSL::DataQuery` module's `data_bag_item` method with the ability to dynamically expand the data bag name in a configurable, environment-specific manner. ## Motivation This gem exists to address the following scenario: An organization maintains data in Chef data bag items. The data is deployed to several data center environments and is stored in data bags whose names reference the environments. The organization wants to write environment-agnostic recipes that access the data bags without explicitly referencing the data bags by their environment names. As a concrete example, imagine the organization maintains encrypted data for three deployment environments: development, staging, and production. It maintains this data in three data bags, one for each environment, with data for services named `gadget` and `widget` in items: | Environment | Bag | Item | |-------------+----------------+--------| | Development | secure-dev | gadget | | Development | secure-dev | widget | | Production | secure-prod | gadget | | Production | secure-prod | widget | | Staging | secure-staging | gadget | | Staging | secure-staging | widget | The items are encrypted with a key unique to that environment to maximize security. Now consider how a recipe would access these bags. When then recipe is running, it needs to know the data center environment in order to construct the bag name. The organization would most likely assign the enviroment name to a node attribute. In a naive implementation, each recipe would include logic that examined the attribute's value to determine which bag to load. This would obviously duplicate code. Imagine instead that the organization wants to reference the bag by the name `secure` and rely on an _abstraction_ to translate `secure` into the environment-specific bag name. This gem provides that abstraction. ## Features This gem overrides the `data_bag_item` method with configurable logic that dynamically decides which bag to load. It retains API compatibility with `Chef::DSL::DataQuery#data_bag_item`, so existing recipes that call `data_bag_item` work without modification. The gem imposes no constraints on data bag item structure. ## Configuration Assign the region name to a node attribute that varies by environment: node.default['local'][region'] = 'staging' Add the following configuration to Chef Client's `client.rb` file. * Require the gem: require 'chef/data_region' * Configure the gem with a hash that maps a bag name to an expansion pattern: Chef::DataRegion.add( 'secure', { attribute: %w(local region), pattern: 'secure-%<attribute>s' } ) ## Bag name expansion The gem expands bag names using Ruby's `format` method. _More pending..._

chefdepartie uses chef-zero to provide a local, testing chef server

Ease collaboration on your Chef kitchen's secrets by storing the data online, for example in private Gists.

chef-gen-flavor-base is a base class to make it easy to create 'flavors' for use with [chef-gen-flavors](https://github.com/jf647/chef-gen-flavors). chef-gen-flavors plugs into the 'chef generate' command provided by ChefDK to let you provide an alternate template for cookbooks and other chef components. This gem simply provides a class your flavor can derive from; templates are provided by separate gems, which you can host privately for use within your organization or publicly for the Chef community to use. An example flavor that demonstrates how to use this gem is distributed separately: [chef-gen-flavor-example](https://github.com/jf647/chef-gen-flavor-example) At present this is focused primarily on providing templates for generation of cookbooks, as this is where most organization-specific customization takes place. Support for the other artifacts that ChefDK can generate may work, but is not the focus of early releases.

An example plugin for [chef-gen-flavors](https://rubygems.org/gems/chef-gen-flavors). This plugin makes use of all the snippets provided by chef-gen-flavor-base, is meant as a reference implementation than for actual use. It demonstrates how to create a flavor with tests and serves as a good example of how to get started writing your own flavors for distribution. There are two flavors in this gem: * example: includes all the snippets in their default form * example2: inherits from example but removes ExampleFile and ExampleTemplate from the list of snippets to use

chef-gen-flavors is a framework for creating custom templates for the 'chef generate' command provided by ChefDK. This gem simply provides a framework; templates are provided by separate gems, which you can host privately for use within your organization or publicly for the Chef community to use. [chef-gen-flavor-base](https://github.com/jf647/chef-gen-flavor-base) is a base class that makes it easy to compose a flavor from reusable snippets of functionality, and using it is highly recommended. Using chef-gen-flavors on its own is only suitable if you already have a template which is a copy of the skeleton provided by ChefDK. At present this is focused primarily on providing templates for generation of cookbooks, as this is where most organization-specific customization takes place. Support for the other artifacts that ChefDK can generate may work, but is not the focus of early releases.

This Handler will report the events and metrics for a chef-client run to Datadog.

Push reporting stats to Librato metrics

This Handler will collect logs from a chef-client run to LogDNA.

Chef report handler for sending run detail information to Opsmatic

Send serf events from chef run on resource updates

send chef notifications to slnky

Chef status notifier handler

This gem provides a set of helper methods to use in chef recipies. Currently, the only implemented method is `#encrypt_password`, which takes a plain-text password and generates a shadow hash for use by the Chef User resource.

This contains a script to lock Chef runs.

Provisioner for creating vSphere VM instances in Chef Metal.