Jira (PUP-7276) templates in defined types in Puppet 4 (or 3.8 future parser) lost access to scope of calling class

[Zed Pobre (JIRA)]

Title: Message Title

Zed Pobre commented on PUP-7276   Re: templates in defined types in Puppet 4 (or 3.8 future parser) lost access to scope of calling class Thanks for the tip on {{ Scope#.to_hash }} (hunting that down led me to http://www.rubydoc.info/gems/puppet/Puppet/Parser/Scope), but I'm not seeing how to get calling scope, or indeed how to call that on an arbitrary named scope even if I knew the name in advance. Any other clues? I haven't had time yet to fully investigate this, but it looks like if I can get access to the title of the resource invoking them, functions can actually do everything defines used to be able to do, it's just that the interface to them is ... suboptimal. :/ They can create resources, and I think the resources they create are still in the original calling scope. The problem is that functions don't seem to support named parameters, so you can't reorder or skip a middle one, and they inherently go into the global namespace. The one thing I haven't been able to figure out so far to actually give it a solid test is how to find the name of the resource that invoked it as well as the class that resource was created inside. Do you have an example of that some place? In light of this, I would suggest that if the current behavior of defines is intended, it is an inherently flawed design and should be changed – I can't see any reason that: myclass::templatemacro { '/path/to/file:': module => 'special', feature => true' } is somehow philosophically different from: templatemacro('/path/to/file','special',true) except that the syntax in the latter is less convenient, forced into the global namespace, and has code that is more difficult to read and maintain. Forcing me to do the latter rather than the former does not seem in any way to be an improvement. Alternately, if it is possible to define the scope used in a function, perhaps it is possible to do: {{ templatefrom('class',<template paths>) }} where the scope can be specified as a parameter, and then create $caller_class_name that defines can see. Defines can then switch out all template(<files>) calls to templatefrom($caller_class_name,<files>). That would actually be pretty close to ideal as well. The issue here is that I have no idea how add $caller_class_name, or indeed how to switch the scope of a function. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.