On Thursday, June 21, 2012 12:38:14 PM UTC-5, Guy Knights wrote:
What is the best way to ensure that when a node inherits another node, that > the inherited node's manifest runs first? Is there was a to ensure this > happens? > In principle, the leaf node can declare relationships between all the classes it declares and all those declared by the inherited node. In practice, you probably don't want that, because you'll end up with dependency cycles unless you're either very careful or very lucky. It's also hard to maintain. All that underscores the fact that you're thinking about the problem the wrong way. Whether one resource needs to be applied before another is a function only of those resources, not of which node declaration caused them to be added to the catalog. Set up appropriate relationships between your resources, and Puppet will find an agreeable order in which to apply them. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Z1aEid4PCYgJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
