Cheflow

A command line tool for managing Chef Environments using Berkshelf and the Node Cookbook Pattern.

TLDR of the Node Cookbook Pattern; You have one top level cookbook that is locked to a Chef Environment. One node per Chef Environment. This Chef Environment is named node_{application_name}_{environment_name} (i.e. node_myface_dev).

Huge thanks go to Jamie Winsor who coined the Environment Cookbook pattern and created the excellent Berkflow gem that this Gem is based upon and inspired by.

For the full details, read COOKBOOKS.md.

• ChefDK >= 0.2.0

Install Cheflow into the ChefDK:

$ chef gem install cheflow

cheflow info|i

Displays useful information about the current cookbook, including the environments this cookbook is being used in, and the list of versions.

This is also the default command that will be executed if you run Cheflow without any command.

cheflow

cheflow bump|b

Bumps the version of the current cookbook. By default, this will be the dev version (patch). To bump the major or minor version, just pass that as the first argument:

cheflow bump minor

cheflow upload|up

Upload the current cookbook - the current cookbook being that which is in the current working directory. The current version of the cookbook will determine if this upload should be frozen or not. If it is a dev version (ie. a patch release), then the uploaded cookbook is not frozen.

cheflow apply|a

Apply the current Berksfile.lock file to the current Node cookbook's environment.

The Cheflow workflow is predominantly based on the current Cookbook version, which determines whether to apply version locks from Berksfile.lock to the production environment or not. Additionally, it will determine if the current cookbook is a node cookbook or not, and behave accordingly.

If the version's patch number is an odd one, ie. a dev release, then the environment should be specified. If no environment is specified, then it will default to development. Cheflow will not allow you to lock a development release to production, even if you specify it.

• Bump the dev version of the non-node cookbook. (eg. 1.0.0 to 1.0.1)
• Upload the cookbook without freezing: berks up COOKBOOK --no-freeze

Equivalent Cheflow command:

cheflow upload

• Bump the dev version. (eg. 1.0.0 to 1.0.1)
• Update Berkshelf: berks install.
• Upload new unfrozen version: berks upload COOKBOOK --no-freeze.
• Apply new version to the given Node environment: berks apply ENVIRONMENT

Equivalent Cheflow command:

cheflow up [ENVIRONMENT]

Default environment is development.

• Upload new unfrozen version: berks upload COOKBOOK --no-freeze.

Cheflow command:

cheflow up [ENVIRONMENT]

Default environment is development.

If the version's patch number is an even one. ie. a production release, then the environment is assumed to be production. You can specify any other environment.

• Upload new frozen version
• Apply frozen version

Cheflow command:

cheflow release [ENVIRONMENT]

Default environment is production.

$ cheflow help

1. Fork it ( https://github.com/joelmoss/cheflow/fork )
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 a new Pull Request