- From: Andrea Campi <
>
- To:
- Subject: [chef] Re: Re: Re: Re: Re: Using data generated in a LWRP
- Date: Thu, 5 Apr 2012 10:59:14 +0200
On Thu, Apr 5, 2012 at 10:32 AM, Nick Peirson
<
>
wrote:
>
On 03/04/2012 15:40, Steven Danna wrote:
>
>
> I think that ultimately my strong opinion about this is to avoid using
>
> the node object to pass state around resources if it is possible.
>
> However, it is occasionally necessary, and in those cases I don't have
>
> a strong opinion about whether to store the information in a node
>
> attribute or the run_state.
>
>
I agree. I've ended up using node.run_state to pass state, but this is
>
implicit and not a convention I've seen documented. Anyone using my the LWRP
>
I've written will have to understand this before being able to use it to
>
find the state information.
>
>
Andrea's suggestion seemed to provide a good solution, what are everyone's
>
thoughts on it? If my ruby was stronger I'd try to hack together a pull
>
request to get the ball rolling but, as it's not, would raising a bug report
>
be a good starting point?
Indeed it would. Also, pestering^Wpinging people for feedback either
here or on IRC would help.
Ideally, it would be nice to have other use cases; for example,
existing cookbooks that could be simplified by this functionality.
If there is enough interest, I may sit down and implement it the next
time I get a time slot for working on Chef "core" functionality.
Or I may do it regardless, but no promise about that ;)
Andrea
Archive powered by MHonArc 2.6.16.