Jira (PUP-11661) Preserve noop-ness when unchanged resources are omitted

[Josh Cooper (Jira)]

Title: Message Title

Josh Cooper created an issue   Puppet / PUP-11661 Preserve noop-ness when unchanged resources are omitted Issue Type: Task Assignee: Unassigned Created: 2022/10/20 10:48 AM Priority: Normal Reporter: Josh Cooper In PUP-11654, we're adding a setting to not send unchanged resource statuses. However, some fields in the report are derived from resource statuses and events. For example, the corrective_change and noop_pending instance variables are computed in the finalize_report method. If a report is deserialized using Report.from_data_report and then re-serialized using Report#to_data_hash, it's important that the original corrective_change and noop_pending data be preserved. I believe it will work that way, but it's something to check. Another complication is the puppetdb report processor determines if a report to be "noop" based on events. So we may need to include unchanged events that were explicitly marked as "noop". Add Comment   This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472736.1666288092000.50245.1666288140166%40Atlassian.JIRA.