This is a Knife plugin to help forking cookbook versions. This is particularly useful when you have different cookbook versions between dev and prod environments and you want them to be the same prior to a prod release.
You will need chef installed and a working knife config; development has been done on chef 11, but it should work with any version higher than 0.10.10
gem install knife-cookbook-taggerFor a list of commands:
knife cookbooktagger --helpCurrently there is only one command available:
knife cookbooktagger -o <original version> -t [<target version>]If you run the command without specifying the target version, then a new cookbook will be generated using the latest version (incrementing the minor version by 1).
Note: this is by no means production ready; I'm using it with success for my needs and hopefully you will find it useful too. Be sure to do a backup your chef server first.
- automatically cleanup old cookbook versions
- Source hosted at GitHub
- Report issues/questions/feature requests on GitHub Issues
Pull requests are very welcome! Ideally create a topic branch for every separate change you make. For example:
- Fork the repo
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Added some feature') - Push to the branch (
git push origin my-new-feature) - Create new Pull Request
Created by [David Gouveia] ([email protected])
Apache License, Version 2.0 (see LICENSE)