[chef] Re: Re: Re: Re: community cookbooks updating


Chronological Thread 
  • From: Mat Davies < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: community cookbooks updating
  • Date: Tue, 29 Jan 2013 15:36:03 +0000

thanks guys I'll take a look at both librarian and berkshelf and see which works better for me.
I guess I should be using one of them for cookbook management anyway.
-Mat

On 29 January 2013 13:17, Jesse Campbell < " target="_blank"> > wrote:
I'm using librarian... it will tell me if cookbooks that are sourced from the community site are outdated against the community site.
but, it won't tell me if cookbooks that I've downloaded from the community site into my local repo are now outdated (we downloaded apache2, added one attribute to it, and now we're about 5 versions behind).

Does berkshelf check your own repo for cookbooks that are also on the community site?


On Tue, Jan 29, 2013 at 7:56 AM, Torben Knerr < " target="_blank"> > wrote:
And so can librarian:
$ librarian-chef outdated [--verbose]
Both are fantastic tools for cookbook dependency management you might want to check out if you haven't already.

Cheers, Torben


On Tue, Jan 29, 2013 at 1:00 PM, Brian Akins < " target="_blank"> > wrote:
On Tue, Jan 29, 2013 at 6:56 AM, Mat Davies < " target="_blank"> > wrote:
> Does anyone have a tool or script that will check your chef or chef repo to
> see if any of the community cookbooks are out of date with the current
> community version and give you a list of those that are?

Berkshelf can do that - although that feature is tagged as beta.






Archive powered by MHonArc 2.6.16.

§