Chefenv

Manages multiple chef server/organization environments

Add this line to your application's Gemfile:

gem 'chefenv'

And then execute:

$ bundle

Or install it yourself as:

$ gem install chefenv

Environments are stored under CHEFENV_DIR/environments. You can set the CHEFENV_DIR environment variable if you like. The default value is ~/.chefenv

Upgrade Note: This is different from version 0.1.0 - You should move your environment folders from ~/chef to ~/.chefenv/environments

Execute:

WARNING: If you have data stored under ~/.chef the init command will DELETE it!

$ chefenv init

This will setup CHEFENV_DIR/environments and clear the current environment.

Create a directory under CHEFENV_DIR/environments for each of your environments. Put your knife.rb, .pem and any other files you need for that organization under that folder. For example, for my hosted chef organization, I create ~/chef/hosted and put my knife.rb and .pem files in there. Additionally, this is a reasonable place to put secret key files.

Once you have at least one environment folder you can

$ chefenv list
$ chefenv use ENVNAME

1. Add tasks for creating/destroying organizations

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

Author:: Andrew Garson (andrew.garson@gmail.com)