On Friday, October 18, 2013 8:07:32 PM UTC-5, Bryan Traywick wrote: > > This also brings up a third question that I thought of while formulating > my thoughts for this question: Why are dependency and ordering linked in > puppet? It seems to me that ideally there should be a way to specify that > command A is performed before command B without making command B depend on > command A. >
Puppet is not about commands, it is about resources and their state. An application-order dependency expresses the concept that correctly applying resource B depends on resource A being in its intended target state. Thus, it follows that resource A must be applied before resource B, *and* that if resource A is not applied successfully then resource B cannot be applied successfully, either. Exec resources fit a bit loosely into this model, but they do fit, with two states: "not run" and "run". On the other hand, if applying resource B successfully does not depend on the state of resource A, then the relative order in which they are applied does not matter. You can provide an ordering relationship anyway, but doing so asserts a false dependency, and you have no room for complaint when Puppet behaves as if it were a true one. 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
