How do projects manage chef cookbooks when multiple teams manage multiple sets of cookbooks?
Posted
by
strife25
on Server Fault
See other posts from Server Fault
or by strife25
Published on 2012-12-07T21:02:38Z
Indexed on
2012/12/08
5:09 UTC
Read the original article
Hit count: 475
I am wondering how projects that have multiple component teams manage their sets of cookbooks?
We are trying to figure out how we can have an ops team provide a set of "common component" cookbooks that can be re-used by other teams that will also write their own cookbooks. For example, the ops team should own the Java cookbook, while a component manages their cookbooks written for their component or build engines.
From my little experience with chef server, this kind of workflow seems to not be well supported since the server stores and manages all cookbooks - so there is a potential to overwrite a cookbook written by another team.
How do other projects deal with this type of problem?
© Server Fault or respective owner