Project
Reverse Dependencies for chef
The projects listed here declare chef as a runtime or development dependency
0.0
Generates a Berksfile from JSON style Chef environment files. Also support extension to environment file with 'cookbook_locations'. Verifies the Berksfile is consistent (all dependencies met) and will upload updated cookbooks and env files to a chef server.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
bindle is a server and development environment provisioning tool. Using Chef, Vagrant, and Fog it organizes and simplifies the creation and management of your development environment and allows you to use the same provisioning tools on your production servers.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.0
Extras for Chef's knife command
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
Chef is a tool for managing server automation. A good butcher makes for a good chef.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.0
Chef handler for sending exceptions & updated resources to Campfire
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.0
Allows capistrano to use Chef data, roles and environments for deployment. Provides basics tasks to upgrade server with chef
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
Provides easy support for using Capistrano and Chef together
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.0
Some tools for dynamically creating clusters on top of OpenNebula. This project is a
playground and implementations will be most likely domain specific to my company
in early versions, although I try to abstract from that as much as possible.
This is WORK IN PROGRESS!
All versions <1.0.0 should be treated as development and unstable versions.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
A Chef Knife plugin that facilitates creating and configuring applications in Chef
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
Generates wiki documentation from Chef node attributes using ERB templates.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.0
A Chef analytics API client with minimal dependencies
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
Allows chef-client/solo to grab cookbooks on the fly using berkshelf
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.0
Skeleton for a testable Chef cookbook
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
# 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..._
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
chefdepartie uses chef-zero to provide a local, testing chef server
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
Executes a chef-client run with only the application's role and the application cookbook in the run list. For example, for the application "foo" the run list would be: role:foo application
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
Chef tool that can be used to do some helpful things.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
Sends chef-client errors via email. More detailed than a simple chef_handler.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
Activity
0.0
Commands useful for checking internet connectivity, VM presence etc.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.0
A tool for your left hand, to have a meal cooked by chef.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024