[chef] Re: Testing New Cookbooks


Chronological Thread 
  • From: Денис Барышев < >
  • To:
  • Subject: [chef] Re: Testing New Cookbooks
  • Date: Mon, 27 Jun 2011 15:58:10 +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; b=nE25H/tgdEakQmHeDtYirPVU0P9qAvyXHJwb0U4HL3nWzDzeOnuqYvYQzjvooGgJpI e3Dgz5hmCmZ8qX3GaYH9JIrm0ONsmjI5zNsP0JBledQBQ5ptHgAvPWPPiKMHvTJECYJA TVs7SgyvbVOgW6ocbsxIe9Si9nqwufXtRd+aE=

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.

§