On Tuesday, April 7, 2015 at 2:54:20 PM UTC-5, Neil - Puppet List wrote:
>
> Here is a similar example using notify
>
> ====== site.pp ======
> node default {
> include noticegroups::matches
> }
> ====== modules/noticegroups/manifests/matches.pp ======
> class noticegroups::matches {
> include notices
> Notices::Anotice <| tag == matches |>
> }
> ====== modules/notices/manifests/anotice.pp ======
> define notices::anotice {
> notify { $title: }
> }
> ====== modules/notices/manifests/data.pp ======
> class notices::data {
> @notices::anotice { 'meant to be made': tag=>['matches'], }
> @notices::anotice { 'NOT meant to be made': tag=>['doesnotmatch'], }
> }
> ====== modules/notices/manifests/init.pp ======
> class notices {
> include notices::data
> }
>
> with that I get the behaviour I expect in puppet 3.6 and broken in 3.7
>
> if I change class noticegroups::matches to noticegroups::iwantmatches then
> only the resource I want gets realized
>
> this just seems like 3.7 broke something to me
>
I agree. You should file a ticket.
Puppet automatically tags resources that are declared by a given class with
each segment of that class's name. Possibly it does similarly to resources
collected by classes (which would make sense), and I can imagine that a
regression might have crept in in that area. For instance, it may be that
P3.7 erroneously tags collected resources *before* filtering by tag (and
perhaps before filtering at all, which would be significantly worse).
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/d4db03ca-4b52-46c6-a3e6-4574c706755b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
