[chef] Re: Re: Re: Re: Chef 11 Attribute Changes -- Computed Attributes Edition

[Jesse Campbell < >]

I'm curious about this... Phil, can you give a more concrete example?

On Tue, Nov 6, 2012 at 9:19 PM, Phil Dibowitz < " target="_blank"> > wrote:

On Tue, Nov 06, 2012 at 06:12:43PM -0800, Daniel DeLeo wrote:
> In what cases do you use this behavior?
>
> And, in the case of defaults, you can go to normal or override attributes if you must. Do you find yourself frequently overriding role overrides in recipes?

All over the place... roles request stuff we want, and in certain cases we
determine based on the runtime environment that we can't do that.

But I shouldn't have to use override. Obviously I *can*, but it defeats the
whole purpose of the predecence hierarchy within a given precedence level.

Plus, as Adam would say, you have no runway. We went from a 14-level runway,
to a 2-level runway. Someone goes "override" in a role and you're fucked.

I see no reason why recipes shouldn't win - we can accomplish everything
desired and still have the Attribute collapse such that recipes win.

Runtime data should *always* win over static data.

--
Phil Dibowitz                             ">
Open Source software and tech docs        Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"Be who you are and say what you feel, because those who mind don't matter
 and those who matter don't mind."
 - Dr. Seuss