On Apr 17, 2012, at 9:15 AM, R.I.Pienaar wrote: > I think having a node variable merge in with top scope variables might > be acceptable in most cases - its roughly how things used to be have - but > its magical and weird and just not clear whats going on. > > Having that magical behavior supports how people tend to use puppet but it > also tends to support the common pitfalls people have with puppet as it > encourages a bad design of code.
+1 Like ;-) > these are all hard non magical things, you know where your variables come > from. You know what they are and what can override them. Mix in the @facts > style syntax and this story becomes even clearer. > > If we were to expand this list to include: > - magical node variables that can override top scope vars in some cases > > Then it's quite clear to me which is the elephant in the room and shouldnt > be there. +1 Like -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
