[chef] Re: Versioned Environments

[Adam Jacob < >]

I've implemented this as a series of environments that get promoted into/out 
of. Basically take the environment policy and attributes from A and slam them 
into B.

Adam

On Oct 11, 2012, at 5:39 AM, Michael Leikind wrote:

> Hi Mike, 
> 
> Thanks for your reply, 
> Yes we use internal chef cookbook versions all the time, but this time we 
> want to use the similar for the environment.
> I know environments do not support it, and I wonder of there some "nice" 
> workaround for this ..
> 
> 
> On Oct 11, 2012, at 1:43 PM, Mike 
> <
 >
>  wrote:
> 
>> I guess I'd be curious to understand the "versioning" of an
>> environment - is the app code currently version1 on dev, and now you
>> want a version2 dev environment? Or is the versioning for
>> chef-specific code?
>> 
>> If it is for chef cookbooks and such, you can version your cookbooks
>> in metadata.rb, and have specific versions of your cookbook available
>> for a given environment.
>> 
>> i.e.:
>> "prod" => cookbook "myapplication", "= 0.1.0"
>> "dev" => cookbook "myapplication", "= 0.2.0"
>> 
>> So any changes to the cookbook code (as long as you increment the
>> version in metadata.rb) will not be applied to an environment that
>> does not match the version constraints.
>> 
>> (Read more on version constraints:
>> http://wiki.opscode.com/display/chef/Version+Constraints ;)
>> 
>> On Thu, Oct 11, 2012 at 7:27 AM, Michael Leikind 
>> <
 >
>>  wrote:
>>> Hi All,
>>> 
>>> I am looking for the best way for versioning the multiple environments.
>>> For instance, we have now 3 main environments (like dev, staging and
>>> production) Now we want to have multiple environment versions per each of
>>> these three (dev/ver1, production/ver2, etc.)
>>> Although I didn't find any Chef way to achieve that, I wonder if any of 
>>> you
>>> have done this and what is the logic.
>>> As a side note, we are using Git for source control.
>>> 
>>> thanks !
>>> 
>>> --
>>> 
>>> --
>>> Michael L.
>>> 
> 
>