Issue #16606 has been updated by Henrik Lindberg.
In #16659 (marked as a duplicate):
Nick Chappell wrote:
> If a resource is tagged with a custom tag that has multiple namespace
> segments ('tag::specific::more-specific'), individual parts of it are matched
> with the == operator when used in a <| |> resource collector.
>
> Apparently, the intentional behavior of the == operator in resource
> collectors where it matches individual namespace segments from a longer
> resource or class name also gets applied to custom tags that are added by the
> user.
>
> Just filing a bug report for evaluation by engineering whether this behavior
> will be changed.
----------------------------------------
Bug #16606: realizing virtual resources by tag with double colon :: in name
gives unexpected results
https://projects.puppetlabs.com/issues/16606#change-74753
Author: Eric Seynaeve
Status: Investigating
Priority: Normal
Assignee: Henrik Lindberg
Category:
Target version:
Affected Puppet version: 2.7.12
Keywords: virtual resource realize tag
Branch:
When I run a puppet apply on the following code, it gives unexpected results:
class ex1 {
include ex2
Notify <| tag == 'zz_tag_bla' |>
}
class ex2 {
@notify {"You're a winner":
tag => 'zz_tag_bla::yadda',
}
}
include ex1
I would expect that the notify would NOT be realized. However, it is.
>From my testing, it seems that the '::' in the tag name causing special
>interpretations. Nowhere in the documentation I can find why this is.
What's going on here ?
Eric
--
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.
