[chef] Re: Re: Berksfile and metadata.rb


Chronological Thread 
  • From: "Julian C. Dunn" < >
  • To: " " < >
  • Subject: [chef] Re: Re: Berksfile and metadata.rb
  • Date: Fri, 16 May 2014 09:44:48 -0500

Right, and in case that example wasn't clear, you can mix-and-match fixture cookbooks and regular cookbooks in that :integration clause.

https://github.com/juliandunn/oracle-xe/blob/master/Berksfile

- Julian


On Fri, May 16, 2014 at 7:39 AM, Stewart, Curtis < " target="_blank"> > wrote:
If it’s something your cookbooks are dependent on, not just for tests, then always add it to your metadata.

Otherwise, you can add an :integration group to your Berksfile (and leave the cookbook out of the metadata) and test kitchen will always pickup that group.  Granted they’re local cookbooks, you can see the jenkins cookbook (https://github.com/opscode-cookbooks/jenkins/blob/master/Berksfile) for an example.


Curtis Stewart
Consultant
Skype cstewart8710

 




Cloud Migration - Architecture - DevOps - Big Data - App Dev


Hi!

If I add

cookbook 'apt'

to the Berksfile, do I have to add

depends 'apt'

to the metadata.rb?

If I understand it correctly, sometimes I may want to add cookbooks to the
Berksfile (for example, local ones) for the run list in .kitchen.yml, but I may
not want to add them to the metadata.rb file. I'm a bit confused...

Thanks,

David Gil
Agència Estatal de Meteorologia a Catalunya




--
[ Julian C. Dunn < " target="_blank"> >          * Sorry, I'm    ]
[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ]
[ gopher://sdf.org/1/users/keymaker/           * compliant!    ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]



Archive powered by MHonArc 2.6.16.

§