We've run into an interesting tangle between skipped resources and refreshes. There are presently several reasons a resource can be "skipped":
1) one of its dependencies failed (ticket #5876) 2) it doesn't match the tags being applied (ticket #3788) 3) its schedule dictates it should not be applied If a resource is "skipped", it will be marked as such in the generated report and will not be normally evaluated. However, 'refresh' events will still happen in all of these cases, in reponse to subscribe/notify. Of these cases, only #1 seems to patently be incorrect. So the purpose of this thread is to solicit opinions about the desired behavior of the other two cases. What are your thoughts on how subscribe/notify ought to interact with tags and schedules? How are you using subscribe/notify with tags and schedules? If this behavior changed, would your life be better, worse, or unaffected? -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
