That’s how I’ve been doing it.
Note that knife cookbook site install will do the branch, tag and merge for you.
There is a gotcha where if it downloads dependencies that you’ve
already updated then there will be no changes for git and the process
stops - however the cookbook you wanted will have worked.
I also use the git diff process to review every change that is made by
the updated cookbook.
Secondly, (although kind of firstly) I watch each cookbook on the
cookbooks site so that I know when they change.
On Mon, Oct 22, 2012 at 10:26 AM, email@example.com wrote:
I have installed a cookbook to my chef server using knife cookbook site install
, and I need to make some customizations to it. I’ve done that and
then pushed it up to my git repo where we’re storing all of our cookbooks.
What is the appropriate way to make sure I am receiving updates from the
opscode public repo? Do I just run knife cookbook site install again
and then merge the changes with my git repo? Or is there a better way to do