Jira (PUP-6950) scope.function_getparam does not work in ERB templates (future parser)

[Rowan Ruseler (JIRA)]

Title: Message Title

Rowan Ruseler commented on PUP-6950   Re: scope.function_getparam does not work in ERB templates (future parser) Henrik Lindberg, thanks once again. What I notice is when I create a scope.lookupvar('foo::server'), it does load the 'server_name'. Kinda confused then why the scope.function_ does not. Or it does, but the servers::information is not yet been evaluated? So I assume that this is what you wrote about 'order of evaluation'. do as little as possible class servers::information has more server(s) then one, so I am unable to do that (well, my knowledge stops here - I can not find any documentation on how to do that). Can I create something like $server_name = "$ {server_id} " within the ERB? That it looks up what specific 'server_id' - foo/foo2/etc and gets the correct value? server { 'foo':   ip_address => "127.0.0.1",   } server { 'foo2':   ip_address => "127.0.0.1",   } Apologies for the many questions, but I've been unable to find an 'relative' easy solution. Or I'll have to rewrite a module so that it does not use a parser = future function. But going to parser = future is a big step in the direction towards 4.x. 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.