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

[Aron Parsons (JIRA)]

Title: Message Title

Aron Parsons commented on an issue   Re: "each" no longer supported in Puppet 3.7.0 Something is definitely broken in 3.7 with the future parser. Even the example from the docs (https://docs.puppetlabs.com/puppet/latest/reference/experiments_lambdas.html#available-functions) is broken. Below is from the EL6 RPM and an unmodified puppet.conf. rpm -V puppet rpm -q puppet puppet-3.7.0-1.el6.noarch puppet apply --parser future -e '$a=[1,2,3] each($a) |$value| { notice $value } ' Error: each() is only available when parser/evaluator future is in effect on node host.example.com Error: each() is only available when parser/evaluator future is in effect on node host.example.com 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.