- From: Sean OMeara <
>
- To:
- Subject: [chef] Re: Re: Re: Testing New Cookbooks
- Date: Mon, 27 Jun 2011 11:04:18 -0400
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=tv3SvPYoRGdy8lUAZGNLxSUAi5f9LSTc73Tpb4HlGRnGQ3qmLpaE9DMIm5mTujbNpy GImjUM2NupD/O5HBkTqQkqQ1rN2mPP7/inyI+4az9l1waPRA2DqdbhJ9JgGoQAbKsM9j lcHXstaBvoFm2+kfzHQ2AvU5Wp2lbboSk3Ce8=
Hi.
Check out these links, they'll show you how to pin cookbook versions down.
http://www.opscode.com/blog/2011/04/21/chef-0-10-preview-environments/
http://wiki.opscode.com/display/chef/Environments
-s
On Mon, Jun 27, 2011 at 8:02 AM, Matthew Drobnak
<
>
wrote:
>
That's kind of what I figured. Thanks everyone.
>
Where is this set again? I know I saw it, but I can't remember where.
>
-Matt
>
On Jun 27, 2011, at 7:58 AM, Денис Барышев wrote:
>
>
You could use environments for this. For production hardcode versions of
>
cookbooks. And testing environment might use the latest versions.
>
>
On Jun 27, 2011 3:42 PM, "Matthew Drobnak"
>
<
>
>
wrote:
>
> Quick question - is there a way to test a new version of a cookbook with
>
> the same name, without breaking existing servers already provisioned?
>
>
>
> For example, say I have a tomcat cookbook that's working, but I wanted to
>
> try a different one...but I don't want to mess all the existing boxes up.
>
>
>
> Is this possible? I'm using Chef 0.10.
>
>
>
> Thanks.
>
>
>
> -Matt
>
>
Archive powered by MHonArc 2.6.16.