[chef] Re: Re: Re: Berksfile.lock commit in dev branches

[Xabier de Zuazo < >]

Hi tknerr,

On Fri, Feb 13, 2015 at 02:28:26PM +0100, Torben Knerr wrote:
> as you said, we are as well doing it only for the top-level cookbooks
> (think of environment cookbooks but using metadata.rb instead of
> environments to lock the dependency graph). Since we are using mostly
> chef  solo / zero having the Berksfile.lock checked in is enough.
> 
> I also experimented with generating / dynamically reading metadata.rb
> entries from the Berksfile.lock for chef client / server use, but it
> was just an experiment and YMMV:
> https://gist.github.com/tknerr/4e3236d00ceba917abea

We are currently using a similar solution to upload our "environment" 
cookbooks
to Chef Server and read the Berksfile.lock. Here is an example:

https://gist.github.com/zuazo/44308e89328ffb665ae1

But this kind of solutions are too tricky :-S

-- 
Xabier de Zuazo

Attachment: signature.asc
Description: Digital signature