Issue #10676 has been updated by Brice Figureau. Branch set to https://github.com/masterzen/puppet/tree/tickets/2.7.x/10676
One of the reason we do it this way is that a report has no schema enforced. The last run summary is extracted from the current registered metrics, and those are registered depending on what happened during the run. I've sent a pull request containing a step in the correct direction, at least we'll now have all resources status defined. Check: https://github.com/puppetlabs/puppet/pull/212 ---------------------------------------- Bug #10676: last run summary is an inconsistent data structure https://projects.puppetlabs.com/issues/10676 Author: Nigel Kersten Status: Accepted Priority: High Assignee: Category: Target version: Telly Affected Puppet version: Keywords: Branch: https://github.com/masterzen/puppet/tree/tickets/2.7.x/10676 * If a run has a failed resource such that all the subsequent events don't fire, we don't write out 'events 0', we simply don't put in the events key. RI's real world use of this file led him to need to create a hash with the following data and merge it in. We should be consistent so this isn't needed. * failed * changed * total * restarted * out of sync We should just do something similar but with absolutely every top level item. Start with the base data structure, and merge into it, rather than building it up as it sounds like we're doing. -- 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.
