[chef] Chef repo with submodules versus seperate cookbooks, ...

[Steven De Coeyer < >]

Hello

I was wondering how most of you manage your chef-repo.

Currently we use one chef repository with all our cookbooks in it and some 
community cookbooks added as submodules.
As we do not edit the community cookbooks directly, but rather wrap them, 
this is not much an issue. But now we’d like to opensource some of our own 
cookbooks, which probably means splitting them from our chef repository and 
adding them as submodules as well. 

Some problems I foresee with this, are: 
 * it’s not good practice to edit a submodule directly inside the repo (or is 
it?)
 * it’s not practical to not have all your cookbooks in one place (i.e. 
vagrant expects 1 cookbook path)
 * our chef developers have to take into account to constantly update all 
submodules instead of just one git pull (or we need to complicate git usage 
with git aliases such as ` git config alias.pullall '!git pull && git 
submodule update --init --recursive’ `)

Nothing big, nothing that’s not manageable. It just feels weird and as if I’m 
missing something.

How do you guys handle this?

Kr.
S

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail