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

Feature #2284

Late binding definition names

Added by James Turnbull almost 5 years ago. Updated over 2 years ago.

Status:Needs More InformationStart date:05/19/2009
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:3.x
Affected Puppet version:0.24.8 Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the PUP project on JIRA using the button below:


Description

A thread on the mailing list (http://mail.madstop.com/pipermail/puppet-users/2007-March/002027.html) has brought up a specific way in which variables defined in the prototype, including the definition name, can be late-binding enough that they can be used for default values in definition prototypes. This would be a good idea, and would only add functionality without changing expected behaviour.

If this is done, it should be done in such a way that all variables in the definitions are late-binding, so that the variables are defined in the order in which they appear in the prototype.

History

#1 Updated by Luke Kanies almost 4 years ago

  • Status changed from Needs Decision to Accepted
  • Assignee changed from Luke Kanies to Markus Roberts
  • Target version changed from 4 to 2.7.x

#2 Updated by Nigel Kersten almost 3 years ago

  • Status changed from Accepted to Needs More Information

Markus, can you clarify the state of this in relation to the futures work? This isn’t the main bug is it?

#3 Updated by Nigel Kersten almost 3 years ago

  • Target version changed from 2.7.x to 3.x

#4 Updated by Joshua Lifton over 2 years ago

  • Assignee deleted (Markus Roberts)

This issue was assigned to a former Puppet Labs employee. Adding back to the pool of unreviewed issues.

#5 Updated by Joshua Lifton over 2 years ago

This issue was assigned to a former Puppet Labs employee. Adding back to the pool of unreviewed issues.

Also available in: Atom PDF