Issue #7555 has been updated by R.I. Pienaar.
Daniel Pittman wrote: > So, no, I do not believe we should support this. Better, I think, to support > that feature in our reporting tools, or make it easier for people to build > that in their tools. well, I didnt really dictate an implimentation only the outcome. you can flag events as silent/ignorable and the report tool can choose to ignore it. that would also solve the problem from the point of an end user. ---------------------------------------- Feature #7555: should be able to exclude a resource from reporting https://projects.puppetlabs.com/issues/7555 Author: R.I. Pienaar Status: Needs More Information Priority: Normal Assignee: Nigel Kersten Category: Target version: Affected Puppet version: Keywords: mcollective Branch: There are many cases where you would want a resource to run always - like an exec that does an apt-get update for example - these will constantly spam the reports with changes and it would be good if there was a meta parameter that lets people choose to not have a resource be reported on. I realize its a bit controversial but it would make some peoples lives a lot better, by default everything should be reported though as it is today -- 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.
