[chef] Re: Re: Understanding node attributes set from 'role' cookbooks

[Lewis Thompson < >]

On 14 March 2014 16:44, Noah Kantrowitz 
<
 >
 wrote:
> Move that logic into recipe or resource code so it can be lazily evaluated. 
> The problem is that attribute files are run once at the start a run so 
> having any logic based on values that might change later (either due to 
> overrides or anything else) doesn't change the outcome of that execution 
> (since it already happened).

Hi Noah

Thanks for your reply.  Am I correct in understanding that you mean
the attributes file logic should be moved into a recipe for lazy
evaluation?

I can understand how this would change the behaviour but in this
instance I am wrapping a third-party cookbook.  Adjusting that
cookbook would make tracking upstream changes difficult.

Are there any other tricks that I can do to force my wrapping
cookbook's recipe to be evaluated before that of the cookbook with
attribute logic?

thanks, Lewis