Issue #4560 has been updated by Cody Herriges.
Status changed from Needs more information to Investigating
I am going to write an acceptance test or two to document this. In the mean
time I would just suggest to make the following change to your initial define
example.
define mydef { @notify { $name: tag => mydef } }
mydef { 'foo': }
Notify<| tag == 'mydef' |>
----------------------------------------
Bug #4560: Virtual resources inside definitions not properly realized by tag
http://projects.puppetlabs.com/issues/4560
Author: Ian Ward Comfort
Status: Investigating
Priority: Normal
Assigned to:
Category:
Target version:
Affected version: 2.6.1rc2
Keywords: realize virtual resource definition tag
Branch:
This problem bit my production environment, running 0.25.5, but I can reproduce
the problem with 2.6.1rc2, so I'm filing against that.
Consider this sample manifest:
<pre>
define mydef { @notify { $name: } }
mydef { 'foo': }
Notify<| tag == 'mydef' |>
</pre>
Given the metaparameter documentation for 'tag', I would expect this manifest
to generate a real notify resource and a message at catalog-run time, but it
does not.
If the last line is change to `Notify<||>`, to realize all virtual notify
resources, the notification appears properly.
More curiously, if the definition is changed to `define mydef { @notify {
$name: tag => 'mydef' } }`, with an explicit tag of the definition name, the
notification *also* appears properly.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
