[chef] Re: Re: conflict between using environments to manage cookbook releases and to manage application environments

[Bryan Berry < >]

I would like to see chef_environments renamed to something like "zones" and only manage cook versions and no other attributes, and then see environments as a place to hold values specific to your application_environments

On Tue, May 1, 2012 at 11:06 AM, Nikolay Sturm < " target="_blank"> > wrote:

* Bryan Berry [2012-05-01]:

> Some cookbooks, such as the haproxy cookbook, treat chef_environments
> like application_environments
>
> I would love to treat chef_environments like application_environments
> but that would completely break my workflow. How are others dealing w/
> the issues I have brought up here?

I hate this mixup of chef and application environments, maybe I just
haven't seen the light yet. Anyways, we use the opscode platform and
introduced a second organization for cookbook tests. Big PITA and I
would really love to see a clean solution.

cheers,

Nikolay

--
"It's all part of my Can't-Do approach to life." Wally