> This works exactly as it appears, and is a reasonable approach, though > in my example scenario the scope is limited ; i would harbour concerns > about tracking this though many levels of scope (as you have) without > proper internal documentation. :)
That's the good thing about the way we do it - there's only one level of scope: basezone. Every variable we define in all the classes along the way is visible at that level, so we don't have to remember class names of all the stuff in the middle. Your version makes things more complex, because you have to remember that your domain variable is in getsite. Also, I don't think you'd be able to include getsite more than once - I think you'd get a variable redefinition error. And we do try and use puppetdoc to explain class internals as much as possible, so the new guys know what classes they need to include. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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.
