The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
Composite namevars are poorly documented, apparently untested
|Assignee:||Nick Fagerlund||% Done:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.
Composite namevars don’t have much documentation to speak of, and the only tests that touch on having multiple key_attributes don’t deal with actual types with composite namevars, instead stubbing key_attributes and/or title_patterns (see: spec/unit/type_spec.rb:504, spec/unit/resource_spec.rb:794). This makes it very difficult to know how to proceed when writing code relating to composite namevars.
#6 Updated by Nick Fagerlund over 2 years ago
OK… this is a feature of the type and provider “API” (<— not actually an API, void where prohibited), which means it belongs in the Puppet reference manual.
Expanding the PRM is currently behind MCollective rework, Hiera docs, and updating what IS in the PRM for Telly. So this’ll take a bit.