- From: Adam Jacob <
>
- To:
- Subject: [chef] Re: LWRPs as containers
- Date: Tue, 19 Apr 2011 10:17:10 -0700
On Tue, Apr 19, 2011 at 8:13 AM, Mark J. Reed
<
>
wrote:
>
I have an LWRP that fundamentally just creates a bunch of other
>
resources dynamically. I had some issues getting notifies to work, so
>
I have some questions.
>
>
1. Is an LWRP the best way to create a resource that is really a
>
collection of other resources?
>
>
2. If not, what is? A define? A straight-up non-lightweight resource
>
definition? It's definitely not a recipe, as I need to be able to
>
call/include it multiple times with different parameters.
>
>
3. If it's at least a reasonable way to do it, where in the provider
>
does that logic belong? Creating more resources once you're already
>
running the action seems a bit late; I wind up having to call
>
run_action on them as I create them in order to get the behavior I
>
want.
>
>
4. As far as notifies go, is there a way from the provider to access
>
the set of notifications requested?
>
>
Any thoughts and recommendations appreciated. Thanks!
Can you give us some example code, and tell us what's happening with
the notifications?
Adam
--
Opscode, Inc.
Adam Jacob, Chief Product Officer
T: (206) 619-7151 E:
Archive powered by MHonArc 2.6.16.