On Dec 21, 3:07 pm, zoredache <franc...@gmail.com> wrote: > On Nov 17, 2:21 pm, jcbollinger > There is none. Variables declared > inside node definitions are not> accessible elsewhere except via > dynamic scoping. As a result, in 2.8> they will not be accesible > outside their node definitions at all. > > Which almost makes you wonder why there isn't didn't also include some > kind of warning when any variables are set in the node scope. It > sounds like when they are going to be almost completely pointless > after the 2.8 upgrade.
In 2.7, if you use node variables outside their node's definition then you will get a dynamic scope warning, just like you do with any other use of dynamic scoping. If you use node variables in a manner that does not involve dynamic scoping then it will continue to work in 2.8, and I don't see why any warning would be warranted for that. It is true that most of the usefulness of node variables is tied to dynamic scoping, and therefore that their usefulness will be small once dynamic scoping goes away. Although I make little use of node variables myself, I think this is a step backwards. John -- 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.
