Feature #2611

resource attribute access

Added by Jan Capek over 2 years ago. Updated 2 months ago.

Status:Accepted Start date:09/08/2009
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:language
Target version:3.X
Affected Puppet version:0.24.8 Branch:
Keywords:resource attribute access
Votes: 7

Description

Based on a post to the development mailing list, it may be useful to add attribute access to the language.

Use case scenario: – a resource has a certain attribute – the attribute needs to be accessed from else where (e.g. another resource, template etc.)

Sample code:

$cacert_path = Base::X509::Cert["cacert"].path

Where the Base::X509::Cert resource is a custom define instantiated e.g. as:

  base::x509::cert { "cacert":
    path => "/etc/ssl/$name",
    source => "puppet:///profiles/cacert.pem",
  } 

History

Updated by Luke Kanies over 2 years ago

  • Category set to language
  • Status changed from Unreviewed to Accepted
  • Priority changed from High to Normal
  • 3 changed from Easy to Medium

“Relatively easy”, not “easy”. :) I usually reserve the ‘easy’ tickets for people who can kind of walk in off the street and figure it out, which doesn’t usually qualify for language extensions.

Updated by Markus Roberts over 2 years ago

Should the target be 0.26 (as it’s a feature, not a bug)?

Updated by Jan Capek almost 2 years ago

  • Target version set to 2.6.0

Would this feature be acceptable for 0.26?

Updated by James Turnbull almost 2 years ago

  • Target version changed from 2.6.0 to 2.7.x

At this stage it’s not going to make it into 2.6.

Updated by Nigel Kersten about 1 year ago

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

Also available in: Atom PDF