Jira (PUP-3190) "each" no longer supported in Puppet 3.7.0

[Andy Parker (JIRA)]

Title: Message Title

Andy Parker commented on an issue   Re: "each" no longer supported in Puppet 3.7.0 After a little bit of searching it looks like the new loader system for functions is looking in the wrong place for system functions: I installed 3.7.0 onto a centos6 vm and hacked up /usr/lib/ruby/site_ruby/1.8/puppet/pops/loader/module_loaders.rb to give me some info about what it is trying to load: [root@localhost ~]# puppet apply --parser future -e '[1,2].each |$x| { notice($x) }' indexing /usr/lib/ruby/site_ruby/1.8/puppet/pops/../../../lib/puppet/functions found [] Error: each() is only available when parser/evaluator future is in effect on node localhost.corp.puppetlabs.net Error: each() is only available when parser/evaluator future is in effect on node localhost.corp.puppetlabs.net Add Comment   Puppet / PUP-3190 "each" no longer supported in Puppet 3.7.0 After upgrading to Puppet 3.7.0, the puppetmaster no longer recognizes the "each" keyword. It prints this in the log: {noformat} Sep 5 19:22:56 minicfg2 puppet-master[11897]: each() is only available when parser/evaluator future is in effect on node buildhost1.lysator.liu.se {noformat} The /etc/puppet/puppet.conf on the puppetmaster host looks ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.