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


Chronological Thread 
  • From: Torben Knerr < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Nested node attributes not working as expected when using overrides?
  • Date: Wed, 24 Oct 2012 11:48:55 +0200



On Mon, Oct 22, 2012 at 9:11 PM, Daniel DeLeo < " target="_blank"> > wrote:
On Monday, October 22, 2012 at 10:36 AM, Torben Knerr wrote:
>
> Ah, thanks! CHEF-2936 is exactly what hits me. CHEF-1804 is weird as well,
> I'll try to keep that in the back of my head...
>
> As this behaviour is quite counter-intuitive, would you agree that a
> foodcritic rule would make sense here?
Yeah, a foodcritic rule would be nice. I was poking around in foodcritic recently and found that it doesn't detect some types of attribute access[0], so fixing that would be a good starting point. 

We intend to fix this for Chef 11, with the intention of allowing more logic (especially computed/derived attribute values and platform-specific attribute values) in attributes files so any foodcritic rule ought to branch on Chef version above/below 11.0.

FYI: added https://github.com/acrmp/foodcritic/issues/82 for the nested node attributes issue specifically
 




Archive powered by MHonArc 2.6.16.

§