Jira (PUP-2273) Enable access to parameters of defined types

Henrik Lindberg (JIRA) Sun, 29 Jun 2014 17:40:26 -0700

Title: Message Title

Henrik Lindberg commented on an issue

You can do this in the future parser since 3.6 and it will become standard in Puppet 4.0. Note that the result of getting the value of an attribute of a resource is evaluation order dependent. Here is your example rewritten using the available syntax (Type[title][param], and it also does things in the correct evaluation order:

                                                    define foo ($bar) {
  $baz = "${bar}_qux"
}
define foo2 {
  notify { "${Foo[myfoo][bar]} ${Foo[myfoo][baz]}": } 
}
class example {
  foo { myfoo: bar => mybar }
  foo2 { trigger_notification: }
}

                                                

As pointed out, the evaluation order would make your original example not see the evaluated result of the instantiation of foo - it happens after the class is finished. In my example it will work because the second resource (foo2) is evaluated after the first (Foo[myfoo]).

Add Comment

Puppet /

PUP-2273

If I have the following define:

{noformat}
define foo ($bar) {
  $baz = "${bar}_qux"
}
{noformat}

I'd like to be able to do something like:

{noformat}
class foo2 {
  foo { 'myfoo':
    bar => 'mybar',
  }

  notify { "${Foo['myfoo']::bar} ${Foo['myfoo']::baz}": }
}
{noformat}

And have the notify message be "mybar mybar_qux"

This message was sent by Atlassian JIRA

--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2273) Enable access to parameters of defined types

Reply via email to