[chef] Re: Standard Practices

[Jay Pipes < >]

We use one chef-repo git repository that contains our roles,
non-encrypted data bags and a cookbooks directory that only contains git
submodules that reference separate cookbook repositories (both
upstream/community as well as internal).

We store encrypted data bags in a separate repo that is
encrypted/decrypted using some Python automation code we have.

Takes a little getting used to git submodules, but overall it works
quite well for us. Use source control for what it's good at: versioning
related software. Use Chef for what it's good at: configuration
management. My personal opinion is it is best not to mix the two things...

Best,
-jay

On 03/13/2013 11:22 AM, Mark Pimentel wrote:
> I just wanted to get a feeling for what standard practices people are
> following for managing chef cookbooks.
> 
> We will be moving to git internally and I would like to plan out the
> migration of our cookbooks to git.  What is the best practice for this
> layout?
> 
> One repo per cookbook? or all cookbooks in one repository?
> How about databags, roles, environments?
> 
> Any feedback would be greatly appreciated.
> 
> -- 
> Thanks,
> 
> Mark