Knife cookbook site install workflow question


#1

Hello, I’m currently working on a test implementation of chef and have
started to run up against some problems with workflow. The main problem
I’ve hit is associated with ‘knife cookbook site install’.

This quickly breaks down in a team environment since it relies on local
branches to maintain changes that you’ve made to cookbooks that you’ve
imported that you then want to upgrade.

I’m curious if others are using this plugin in a team environment and if
so, how do you handle the local/remote branching problem?

If others are able to install cookbooks in a similar way while allowing to
make local changes and upgrade (and merge) to later versions of the remote
cookbook, please let me know how you’re accomplishing this.

Thanks in advance for any suggestions!

-Eli