[chef] Re: Re: Re: Re: Re: Re: delayed evaluation?

["John E. Vincent (lusis)" < >]

I see a couple of more "flexible" options. I think node.run_state would work here but I'm not positive without testing it.

Another option that I've always found interesting is creating/using a databag as part of a recipe. It's a bit risky in that the databag is just out there without a commensurate copy in your repo though.

Really this feels like the job of an LWRP. There's a lot of logic you're describing that would really muddy a recipe.

On Tue, Dec 17, 2013 at 1:03 PM, John Alberts < " target="_blank"> > wrote:

On Tue, Dec 17, 2013 at 9:37 AM, Rilindo Foster < " target="_blank"> > wrote:

Slightly off-topic, but where are you modifying It may be a style or philosophy thing, but I personally wouldn't try to modify an attribute once I declare it. I rather that I set my conditions up front in attributes file and maybe override them as necessary within the environment role. Changing them within the recipe strikes me as adding a significant amount of complexity to the code maintenance, as you now have to look at the recipes AND attributes when you modify the cookbook.

Yes, I agree.  Here's the actual scenario that I'm dealing with.  I'm creating some new EBS volumes, once they are created, I store those new device entries in an attribute.  Later in the code, I need to use those new devices to either format, create a raid, etc.  So, I need to save those device values somewhere during the Chef run and be able to use them later in the code.

--
John Alberts