Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7179 Type aliases defined across multiple levels of modules Change By: Eric Thompson QA Risk Assessment: Needs Assessment No Action 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7179 Type aliases defined across multiple levels of modules Change By: Eric Thompson QA Risk Assessment Reason: covered by unit tests 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Thomas Hallgren commented on PUP-7179 Re: Type aliases defined across multiple levels of modules Eric Thompson, I think its well covered by the unit tests. They create a proper directory structure with dependencies and all and then verifies that things resolve correctly. 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Eric Thompson commented on PUP-7179 Re: Type aliases defined across multiple levels of modules Henrik Lindberg, Thomas Hallgren, i can't tell from the unit tests in the PR if this needs acceptance tests or not. thoughts? 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7179 Type aliases defined across multiple levels of modules Change By: Henrik Lindberg Release Notes Summary: Fixes a A loader delegation problem has been fixed that caused problems when a Pcore Type A::A in a module 'a', referenced data type B::B in a dependent module 'b', that in turn referenced type C::C in a depended indirectly on data types not directly visible to the module 'c'. The fix ensures that , but being visible to the correct loader for the respective module is used when resolving involved types of an intermediate type . 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7179 Type aliases defined across multiple levels of modules Change By: Thomas Hallgren Release Notes Summary: Fixes a loader delegation problem that caused problems when a Pcore Type A::A in a module 'a', referenced type B::B in a dependent module 'b', that in turn referenced type C::C in a depended module 'c'. The fix ensures that the correct loader for the respective module is used when resolving involved types. Release Notes: Bug Fix 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Kenn Hussey commented on PUP-7179 Re: Type aliases defined across multiple levels of modules Thomas Hallgren or Henrik Lindberg please provide release notes for this issue. 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Thomas Hallgren assigned an issue to qa Puppet / PUP-7179 Type aliases defined across multiple levels of modules Change By: Thomas Hallgren Status: Ready for CI Test Assignee: qa 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Thomas Hallgren commented on PUP-7179 Re: Type aliases defined across multiple levels of modules Merged to stable at ea16755 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7179 Type aliases defined across multiple levels of modules Change By: Thomas Hallgren Assignee: Thomas Hallgren 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7179 Type aliases defined across multiple levels of modules Change By: Thomas Hallgren Assignee: Thomas Hallgren 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7179 Type aliases defined across multiple levels of modules Change By: Thomas Hallgren Story Points: 2 Team: Puppet Developer Experience Sprint: PDE 2017-02-08 Fix Version/s: PUP 4.9.2 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Thomas Hallgren commented on PUP-7179 Re: Type aliases defined across multiple levels of modules This looks like missing transitive dependencies to me. A's loader should definitely see C (through B). 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Henrik Lindberg commented on PUP-7179 Re: Type aliases defined across multiple levels of modules Yes you are right, the types used by B should be looked up from the perspective of B (not A). It must be passing on the wrong loading scope. 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title Henrik Lindberg commented on PUP-7179 Re: Type aliases defined across multiple levels of modules ping Thomas Hallgren, do you think there is a quick for this? If so, I am inclined to try to get this into 4.9.2. 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
Title: Message Title
Matt Dainty updated an issue
Puppet / PUP-7179
Type aliases defined across multiple levels of modules
Change By:
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:{noformat}Class[A]: parameter 'myparam' references an unresolved type 'C::MyType'{noformat} `myparam` is defined in the class of type 'B::SomeType'. 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.
Jira (PUP-7179) Type aliases defined across multiple levels of modules
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'
