- From: Ringo De Smet <
>
- To:
- Subject: [chef] Re: Re: release 0.9.12 does not include [CHEF-1423] - Support versions of recipes on the run list
- Date: Tue, 11 Jan 2011 10:33:43 +0100
- 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=JrTIRIchESVJyAHSYdFQVCDVt4Htcm8MB+EUJ3ozNupV26iVvg8/K8VtlZOm1vFIqY EVGBtvLHK0edbNiwsiOTnKwQI8lR13i5PB1a5bDHKQ98vWeD3O3lKQHA+E/wG/+vkwTv ShAfSo9kSkEiIKK2lxVKTrXoykXKCyNhNGw3Q=
Seth,
On 28 December 2010 20:21, Seth Falcon
<
>
wrote:
>
>
In the meantime, we have been working on integrating cookbook version
>
constraint logic into Chef and making the syntax for specifying
>
version constraints more consistent. What has been implemented on the
>
master branch is described here:
>
>
http://wiki.opscode.com/display/chef/Cookbook+Version+Constraints
Have you also been thinking of versioning roles? I think this would
come in handy to evolve your setups.
The role "webserver" today could be totally different tomorrow, so
being able to link
to <cookbooks>@1.0 and
to <cookbooks>@2.0 makes sense to me.
Ringo
- [chef] Re: Re: release 0.9.12 does not include [CHEF-1423] - Support versions of recipes on the run list, Ringo De Smet, 01/11/2011
Archive powered by MHonArc 2.6.16.