Jira (PUP-1053) Resource defaults and automatic tags are applied after collectors are evaluated

[Charlie Sharpsteen (JIRA)]

Title: Message Title

Charlie Sharpsteen commented on an issue   Re: Resource defaults and automatic tags are applied after collectors are evaluated Summary from PUP-22 : Automatic tags and resource defaults are applied by the compiler during the finish stage which is executed after the evaluate_generators stage where collectors are evaluated. Additionally, the step that adds automatic_tags from parent scopes is not selective at all---it performs a wholesale copy of all tags. Therefore, a notify resource defined inside a class ends up tagged as both a class resource and a notify resource which is probably not the intended behavior as this makes it difficult to use tags to filter by resource type. Add Comment   Puppet / PUP-1053 Resource defaults and automatic tags are applied after collectors are evaluated Resources (and virtual resources) are not having their classes declared tags correctly applied. ("Add the specified tags to the containing class or definition. All contained objects will then acquire that tag, also." ref: http://docs.puppetlabs.com/references/latest/function.html#tag) <pre> class foo {     tag 'notworking'     notify { "I'm untagged... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.