Jira (PUP-2532) parameter lookup produces screwy result for default values

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: parameter lookup produces screwy result for default values No need to test further, the spec tests cover the cases that were wrong. The problem was that if no value was set, you would get the wrong default. Notify { message => 'wrong'} class testing { Notify { message => 'correct' } notify {hi: } } # This got the global 'wrong' default, because it looked up defaults from the scope where this source line is, not # the source line where the hi resource was created / contained... notify { hi_test: message => Notify[hi][message] } Hope that explains it better Add Comment   Puppet / PUP-2532 parameter lookup produces screwy result for default values When the future parser "lookup resource parameter" evaluates and there is no parameter value set by the evaluated manifest logic at that point, the evaluator then looks up the default value for that parameter. This unfortunately looks up the default value as seen from the perspective of the "lookup resource parameter" scope/context, and not the context... 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.