Issue #8174 has been updated by Russ Allbery.
Are these warnings safe to ignore, or is Puppet really going to break all use of facts without scoping in Puppet 2.8 as the warning seems to imply? Do we have to go through all of our manifests and change every use of, e.g., $operatingsystem to $::operatingsystem? The implications of that for templates look, so far as I can tell from Google, absolutely awful. I'm hoping that, since it was indicated above that this is a bug, facts will just stay global and the warning can just be ignored.... ---------------------------------------- Bug #8174: External Node Classifer makes puppet think Facter variables are dynamic lookup issues https://projects.puppetlabs.com/issues/8174#change-56790 Author: Chuck Schweizer Status: Accepted Priority: Normal Assignee: Nick Fagerlund Category: Target version: Affected Puppet version: 2.7.1 Keywords: Branch: I have found that if your class is part of the External Node Classifier definition puppet 2.7.1 thinks variables from Facter are dynamic lookups. EG. External config --- classes: - hadoop environment: production parameters: puppetmaster: puppet Dynamic lookup of $operatingsystem at /var/opt/puppet/environments/production/modules/hadoop/manifests/base.pp:53 is deprecated. Support will be removed in Puppet 2.8. Use a fully-qualified variable name (e.g., $classname::variable) or parameterized classes. $ facter operatingsystem RedHat -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
