[chef] Re: Re: Re: Re: Nested node attributes not working as expected when using overrides?

[Daniel DeLeo < >]

On Friday, October 19, 2012 at 8:11 AM, Bryan Baugher wrote:

I looked and didn't find anything. I have been using nested attributes for quite some time and haven't had any issues using them in recipes.

On Fri, Oct 19, 2012 at 9:53 AM, Torben Knerr < " target="_blank"> > wrote:

Waah, really? I hoped I did something wrong. Wouldn't that violate the principle of least surprise? Or is it just me who is "surprised" by that... 

Btw: I'm seeing this pattern in lots of recipes, guess this would be a surprise to some of the authors as well.

Is this documented anywhere in the Wiki?

Currently, precedence within an attribute level is implemented by order of application. This means that the only safe time to generate a computed value is in a recipe, since attributes from roles will not have been applied until later.

We recently fixed a different but related issue, CHEF-1804[0] with an eye towards making this issue (CHEF-2936[1]) easier to resolve; it should be fixed in master in the next couple of weeks. Note that these are potentially breaking changes so they will go in Chef 11.0 but not 10.x.

-- 

Daniel DeLeo

0. http://tickets.opscode.com/browse/CHEF-1804

1. http://tickets.opscode.com/browse/CHEF-2936