Jira (PUP-1973) futurepaser doesn't bind variables in templates correctly

[Daniele Sluijters (JIRA)]

Title: Message Title

Daniele Sluijters commented on an issue   Re: futurepaser doesn't bind variables in templates correctly I've come to understand that this is intended behaviour, dynamic scoping is explicitly turned 'off' in future evaluator. However, there's puppetlabs modules that (ab)use this feature right now. Add Comment   Puppet / PUP-1973 futurepaser doesn't bind variables in templates correctly If you run the puppetlabs-ntp module with parser=future on 3.5.0-rc1 it will break complaining that it can't call {{flatten{{ on {{nil:NilClass{{ in the ntp.conf template. This happens because for some reason {{@restrict{{ and every other variable in the template isn't bound, ergo nil. If I explicitly add a {{$restricted = $::ntp::restricted}} to co... 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.