On Thu, Jun 23, 2011 at 6:01 AM, jcbollinger <john.bollin...@stjude.org>wrote:
> > While I'm on my soapbox, this is one reason why I don't like > interclass dependencies very much, and why run stages (which magnify > this problem) need to be approached with caution. There is certainly > something to be said for the layer of abstraction achieved by relying > on interclass dependencies instead of on finer-grained inter-resource > dependencies, but you can't do it halfway. > I agree with the halfway bit :) but generally I feel that class-to-class relationships are much easier to maintain than resource-to-resource relationships that cross class boundaries. It allows you to change the internal relationships and behavior of classes without worrying so much about external consumers of your class. Encapsulation is a good thing. Your modules are significantly less reusable if you need to document required individual resource relationships. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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.
