Jira (PUP-4328) scope.lookupvar does not work in ERB templates (future parser)

[Eric Thompson (JIRA)]

Title: Message Title

Eric Thompson updated an issue   Puppet / PUP-4328 scope.lookupvar does not work in ERB templates (future parser) Change By: Eric Thompson ERB templates that directly use methods on {{scope}} to lookup variables instead of the {{@varname}} syntax fails to find variables unless they are in global scope. This is most likely caused by the 4.x evaluator only giving the 3.x function access to the global scope (since functions in general should not ever have access to the calling scope). This is a breaking change from 3.x that is not documented. Problem is probably solved by porting the template and inline_template functions to the 4.x function API and making sure that the calling scope is passed on. Part of me does not want to fix this since it is a source of subtle bugs and problems that scope is accessed directly (and has a very broad and undefined "API") - that was the reason all variables in scope are made available using the {{@varname}} syntax. Some projects have already changed their templates (like Foreman). Question is if we should fix this problem or not. ping [~eric.sorenson] risk assessment: high (test automation within one sprint) probability: high (see modules mentioned by henrik below) severity: medium (workarounds exist other than modules breaking) highest test layer: acceptance (high risk, touches several components, regression candidate) Add Comment   This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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.