Jira (PUP-7179) Type aliases defined across multiple levels of modules

[Matt Dainty (JIRA)]

Title: Message Title

Matt Dainty created an issue   Puppet / PUP-7179 Type aliases defined across multiple levels of modules Issue Type: Bug Affects Versions: PUP 4.9.0 Assignee: Unassigned Created: 2017/02/04 9:56 AM Priority: Normal Reporter: Matt Dainty I have three modules; A, B and C. Module C defines some type aliases. Module B lists module C in `metadata.json` and defines some type aliases in terms of the ones in C, (`Variant`, `Array`, etc.). Module A lists module B in `metadata.json` and uses the type aliases defined in B for parameter types. When I try and use module A I get errors similar to: Class[A]: parameter 'myparam' references an unresolved type 'C::MyType' The workaround is to also add module C to module A's `metadata.json` even though it is installed on the host by virtue of installing module B. I would argue it should just work without this as I'm not explicitly using any of C's resources; it's a dependency of B's and that module is free to change it's dependencies as it sees fit. 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.