----- Original Message ----- > So, my essential point is that if that file did change – and it > genuinely did – we should report that back, and provide better tools > to filter it on the server side. The advantage of filtering on the > client rather than the server is minimal, given we compress the data > transmitted, so you are talking about a few bytes of network traffic, > total.
yes, the main concern isnt that it is or isnt in the report its that its being reported on, mailed out, shown as red on dashboard etc ditto for output on --test though that we can shut up generally with the loglevel meta parameter > > Would you be equally satisfied if we allowed you to annotate that the > resource was expected to change every time, and then alerted you only > if it *didn't* change on a given run? (...or just never displayed > that change to you?) I think there's a lot of files that changes frequently but not always and it would be worth excluding those so more flexibility would be useful -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
