Jira (PUP-5935) Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module

[Thomas Hallgren (JIRA)]

Title: Message Title

Thomas Hallgren commented on PUP-5935   Re: Module specific hiera data should be available to a defined type, even if it is called from within another defined type in another module I think this might be a duplicate of PUP-5618 . When I test the attached modules (and again, thanks, it's so much easier with working examples) on our stable branch I get what I would have expected: # puppet apply -environment pup_5935 -e "test1::foo { 'TEST': }" Notice: Compiled catalog for test.example.com in environment pup_5935 in 0.21 seconds Notice: this_is_from_test1 Notice: /Stage[main]/Main/Test1::Foo[TEST]/Notify[this_is_from_test1]/message: defined 'message' as 'this_is_from_test1' Notice: this_is_from_test2 Notice: /Stage[main]/Main/Test1::Foo[TEST]/Test2::Foo2[blah]/Notify[this_is_from_test2]/message: defined 'message' as 'this_is_from_test2' Notice: Applied catalog in 0.08 seconds I believe that PE 2015.3.1 is based on Puppet 4.3.1. The PUP-5618 fix is in Puppet 4.3.2. Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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.