The $:: business is to force the variable look up to be in the top scope. It didn't fix have anything to do with the conditional, I just put it there for correctness.
In this case, you are using a variable that is set by facter, so it appears in the top scope. Variables that you set yourself can be in the top scope if you put them in site.pp, or in a class scope if you declare them inside of a class. There's also a node scope. While referring to variables with explicit scoping is not required in the current version of puppet, there are some major upcoming changes to how Puppet makes variables available to different parts of your code. You'll most likely get a compiler warning if you don't use it in the 2.7 series, and it just won't work in the next version of Puppet. This page on variable scope is worth reading: http://docs.puppetlabs.com/guides/scope_and_puppet.html Geoff Davis Scripps Institution of Oceanography gada...@ucsd.edu, (858) 822-5756 On Apr 17, 2012, at 12:31 PM, Forrie wrote: > Thank you, I appreciate it. Still learning all the interesting > nuances of this syntax. I'm not yet familiar 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-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. -- 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.
