cookbook versions can address this. You can specify version of individual
cookbooks in their metadata. You can enforce every environment to use a
particular version (in absence of which, most upstream version will be
picked up). You can specify cookbook versions in individual node’s run list
In a typical cookbook development workflow you might consider having
multiple chef environments, say dev, test and production. Dev environment
wont have any cookbook version constrain, while in test you can freeze the
latest stable versions once they are tested in dev, and finally production
containing battle tested cookbooks in test environment.
On Fri, Jan 4, 2013 at 3:17 PM, Kirill Timofeev email@example.com wrote:
I have number of cookbooks on chef server depending on each other. I
wonder if I can override some of those cook books with local copies for
testing purposes. I want to make changes to cook book, run chef-client
which would use chef-server to fetch all cook books except changed one,
verify that my changes work as expected and only after that submit updated
cook book to chef server. Is it possible?