[chef] Re: Re: Cookbook workflows

[Torben Knerr < >]

Great idea! I would also be interested in collecting best practices, especially concerning the cookbook development workflows. So far I did not find any valuable information except on this mailing list :-)

We had some discussions about the topic recently on this list:

http://lists.opscode.com/sympa/arc/chef/2012-01/msg00046.html
http://lists.opscode.com/sympa/arc/chef/2012-01/msg00090.html

Don't know if that fits for every situation, but currently I would consider this as a "best practice":
- cookbooks should be versioned independently, thus they need their own git repositories. 
- for pulling together a sound baseline of independently versioned cookbooks you can use either git submodules or librarian.

- a concept of explicit SNAPSHOT versions (as in maven) would be useful during development. As there are no explicit SNAPSHOT versions, you can still agree on a convention, e.g. each X.Y.Z version with an odd Z number is considered a "SNAPSHOT"


Cheers,
Torben

On Tue, Jan 31, 2012 at 3:23 PM, Kevin Harvey < "> > wrote:

This looks really great. The more 'best practices' documentation out there the better. I'd love to know of any more out there. Thanks Anthony!
--
Kevin Harvey
Web Developer
" target="_blank">

On Tue, Jan 31, 2012 at 9:08 AM, Anthony Goddard < " target="_blank"> > wrote:

Hi all,

I just remembered adding this wiki page a little while back, but not padding it out yet, http://wiki.opscode.com/display/chef/Cookbook+Workflows. I thought it would be a good place to list all of the different cookbook workflows, maybe use cases, pros/cons. Am I duplicating something that already exists in a place that glaringly obvious to everyone but me? :/ If not, would love the addition of other workflows I haven't listed yet. I'm hoping to get a chance to pad out the others soon.

---
Anthony Goddard
Woods Hole Marine Biological Laboratory