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.
Is an LWRP the best way to create a resource that is really a
collection of other resources?
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.
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
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!
Mark J. Reed firstname.lastname@example.org