----- "Jeff McCune" <j...@puppetlabs.com> wrote: > I make the recommendation that classes should include the classes > they depend on, but this appears to be problematic if the class doing the > include sets resource defaults, particularity when setting a > relationship in a default like require, before, subscribe and notify. > This opens up the door for resource cycles.
recommendations are fine, but that is a lot of convention and best practice something that is very hard to pass on to new people, its hard to audit and its hard to predict. And ones established as a best practise that causes problems when ignored also lulls one into a false sense of safety. best avoided, it should do the right thing by default. > Perhaps it might be useful to set resource defaults only for the > local scope, and not for any classes which get included into this scope. > How do you feel about this change to the language? I've thought about this problem before and thought the fact that puppet did not behave in this way was a bug, so my vote is with this :) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
