Separate git repo per cookbook - how will dependent cookbooks be reolved?


#1

Hi Chefs,

as I have read there is some effort in putting the Opscode cookbooks in
their own git repository each.

By doing that, did you already decide how to pull in the dependent
cookbooks?

Librarian or git submodules come to my mind. Or will it be something built
into Chef which resolves dependent cookbooks via metadata.rb?

Just curious…

Torben


#2

Librarian does work perfectly for this case.
On Mar 9, 2012 8:25 PM, “Torben Knerr” ukio@gmx.de wrote:

Hi Chefs,

as I have read there is some effort in putting the Opscode cookbooks in
their own git repository each.

By doing that, did you already decide how to pull in the dependent
cookbooks?

Librarian or git submodules come to my mind. Or will it be something built
into Chef which resolves dependent cookbooks via metadata.rb?

Just curious…

Torben


#3

On Fri, Mar 9, 2012 at 2:25 AM, Torben Knerr ukio@gmx.de wrote:

as I have read there is some effort in putting the Opscode cookbooks in
their own git repository each.

By doing that, did you already decide how to pull in the dependent
cookbooks?

Librarian or git submodules come to my mind. Or will it be something built
into Chef which resolves dependent cookbooks via metadata.rb?

The recommended workflow is still to use the community site as the
source for stable cookbooks and use git for cookbook development.
‘knife cookbook site install’ is happy to download cookbooks from the
community site for you.

People have strong feelings about tools. Some people hate git
submodules, others love them. Cookbook authoring is art, and we all
have our favorite brush. I think the number of cookbook users is going
to continue to grow over the number of public cookbook maintainers,
and there will be less development centric workflow patterns overall.
Discussion is still likely to be made by people who are authoring and
maintaining though.

Bryan