A custom cookbook in support of mh-opsworks
Ubuntu 14.04 LTS, and more specifically amazon aws
| Key | Type | Description | Default |
|---|---|---|---|
| ['mh-opsworks-recipes']['bacon'] | Boolean | whether to include bacon | true |
Include mh-opsworks-recipes in your node's run_list:
{
"run_list": [
"recipe[mh-opsworks-recipes::default]"
]
}- Dan Collis-Puro - djcp
- Create a branch off the develop branch
- Edit your cluster config to use this branch in your development cluster
- Make your changes and push them to your recipe branch
- Update your cluster's chef recipes and redeploy to run them. If your recipe isn't run during the deploy lifecycle, then run it manually to test.
- Work on your feature until it's ready to be merged into the develop branch.
- Be sure to update the "To be released" section of the CHANGELOG.md file with a description of your change, and whether or not it requires a manual recipe invocation. If your change runs as part of the deploy lifecycle, it will be run the next time the main app is deployed to a cluster and therefore does not require a manual chef recipe invocation.
- Rebase against develop and submit a pull request off of develop.
- Update CHANGELOG.md to collapse all "To be released" changes under a new version, following semver.
- Rebase develop onto master (just to be sure).
- Cut an RC tag and link that into your staging cluster. Annotate the tag to reference the matterhorn tag this is meant to work with.
- QA. When QA passes,
- Merge the RC tag into master,
- Tag the release on master based on the RC tag
- Push the tag to the remote via
git push --tags - Make sure the release manager knows the correct tag to use in the cluster config.
This project is under an Apache 2.0 license. Please see LICENSE.txt for details.
2015 President and Fellows of Harvard College