The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #11462

Composite namevars are poorly documented, apparently untested

Added by Anonymous almost 3 years ago. Updated about 1 year ago.

Status:ClosedStart date:12/16/2011
Priority:NormalDue date:
Assignee:Nick Fagerlund% Done:

0%

Category:-
Target version:-
Keywords: Affected URL:
Branch:

We've Moved!

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.


Description

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.


Related issues

Related to Puppet - Bug #15264: Custom title patterns can fail cryptically Closed 06/27/2012

History

#1 Updated by Anonymous almost 3 years ago

  • Status changed from Unreviewed to Accepted
  • Assignee set to Anonymous

#2 Updated by Anonymous almost 3 years ago

This specifically came up when investigating #10109, which needs a test case involving a real resource with a composite namevar (and not just some sketchy stubbing).

#3 Updated by Anonymous over 2 years ago

I think the testing has been much better covered by the work done on #15264, but there is probably still more to do. There is also still no documentation that I can find for them.

#4 Updated by Anonymous about 2 years ago

  • Project changed from Puppet to Puppet Documentation
  • Assignee changed from Anonymous to Nigel Kersten

#5 Updated by Nigel Kersten about 2 years ago

  • Assignee changed from Nigel Kersten to Nick Fagerlund

Nick, lets make sure we get this into the prioritization list.

#6 Updated by Nick Fagerlund about 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.

#7 Updated by Nigel Kersten about 1 year ago

  • Status changed from Accepted to Closed

Also available in: Atom PDF