The dependency warning may be overstated a bit, in your situation you're
not likely to cause that issue by accident.
Another view might be that systems should be built from scratch when
significant changes are made. Regardless of your CM tool, that's generally
a better idea these days - even upgrades generally benefit from standing up
a fresh system to replace the older system.
Also, order of removal of files does seem odd, if neither is required. Was
that a contrived example or an actual example? If the latter, that seems
like a really badly behaved application, from the outside.
On Wednesday, September 21, 2016, Peter Faller <pgfal...@gmail.com> wrote:
> Thanks Craig - that does work, but what it says in the documentation is
> "Note: Chained collectors can potentially cause huge dependency cycles
> should be used carefully."
> This approach works fine for 'leaf' resources; but when the dependencies
> get more complicated it is very easy to create dependency cycles. It's
> beginning to look to me that Puppet is best suited to cases where resources
> once added, remain in place.
> 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/
> For more options, visit https://groups.google.com/d/optout.
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 view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.