Issue #21508 has been updated by Henrik Lindberg. Status changed from Investigating to In Topic Branch Pending Review Keywords changed from future parser to future parser scope template variable Branch set to https://github.com/puppetlabs/puppet/pull/1735
The cause was that Scope#to_hash did not include the local variables. That function was used by the TemplateWrapper to configure the available instance variables. Ergo - they were missing. The fix includes the local variables, but skips all match (ephemeral) variables $0-$n just like the original implementation did. (i.e. it is backwards compatible). ---------------------------------------- Bug #21508: Can't access a lambda variable in a template (Future Parser) https://projects.puppetlabs.com/issues/21508#change-93815 * Author: Kit Plummer * Status: In Topic Branch Pending Review * Priority: Normal * Assignee: Henrik Lindberg * Category: * Target version: * Affected Puppet version: 3.2.2 * Keywords: future parser scope template variable * Branch: https://github.com/puppetlabs/puppet/pull/1735 ---------------------------------------- https://gist.github.com/kitplummer/5877926 Doesn't work: `<% @value %>` Does work: `<%= scope.lookupvar('value') %>` -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
