Issue #7555 has been updated by Daniel Pittman.
On Tue, Oct 4, 2011 at 10:16, Nigel Kersten <[email protected]> wrote: > As per: https://projects.puppetlabs.com/issues/7555 > it looks like we've got some use cases around excluding some resources from > being reported on to reduce noise. This feels like solving the problem on the wrong side to me. > Should we implement a metaparameter like this? Do the use cases justify > breaking the consistency of the model (report on everything) ? This is worse than that: it bakes in the assumption that the reports are *not* a graph, or that we can just discard structural elements in that graph, by allowing us to ditch what would otherwise be a vertex. One of the proposed enhancements to the report - which I think is hugely valuable - is that we return the augmented graph from the client side, where things like file recursion, or autorequires, can change the catalog we sent down. Excluding something from that may be a huge structural change, and it is certainly going to make correlation between that graph and the original catalog extremely difficult to discover. 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. ---------------------------------------- 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.
