On Friday, July 3, 2015 at 10:30:59 AM UTC-5, R.I. Pienaar wrote:
What I really want is a way for resources to influence sorting only and not
> make
> dependencies.
>
Why?
A resource relationship expresses the idea that the resource at one end
must be configured before the one at the other end successfully and
correctly can be. If you indeed have such a situation, then you have a
genuine dependency that it is useless to ignore. If you do not have such a
situation, then by definition it does not matter in which order you manage
the (formally) unrelated resources.
The direction and even existence of relationships is often different for
tearing down a (sub)system than it is for building it up, which can be a
pain, but I'm not at all seeing what's useful about controlling order of
application absent dependencies.
>
> Manifest ordering does what I want - it orders one resource before another
> and does
> not add relationships. I want parameters for that kind of non relational
> ordering.
>
>
There are no such metaparameters in current Puppet.
> I am though require surprised by the behaviour of notify.
>
> exec{"false": notify => Exec["true"]}
> exec{"true": }
>
> Exec["true"] will never run because notify is a dependency.
>
Yes, this has been Puppet's behavior since at least since v0.24. The
"notify" and "subscribe" metaparameters have always implied "before" and
"require", respectively. It makes sense to me to some extent, but it is
not clear cut as the behavior non-signaling relationships.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/bba7bad0-7988-46c5-b94b-58a64d1aa2a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
