On Monday, July 21, 2014 3:32:47 PM UTC-5, Nan Liu wrote:
>
> Similar to the discussion of collect resources realize + override, I wish
> the metaparameters weren't magically passed to the resources, and we could
> choose to use them and pass the behavior on as needed.
>
>
Sadly, it's not that easy. Some metaparameters already aren't (or
shouldn't) be forwarded, mainly 'alias'. On the other hand, many others
*must* be forwarded in order to be effective ('tag', 'noop', ...). The
relational metaparameters could technically swing either way, but the
overall semantics need to maintain containment.
Schedule and loglevel are the only two that I think are ambiguous, but more
loglevel than schedule. I'm not sure how it makes sense for a resource to
not inherit the schedule set on its container (if there is one), else it's
container's assigned schedule isn't fully honored. On the other hand, it
does make sense for a resource to have a different (lower) loglevel than
its container, especially if the container's is interpreted as an upper
bound rather than an exact log level for all messages.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/c3a1c76d-ab5b-41c4-9a6c-c922bb6e710d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
