Jira (PUP-916) Document report format changes for improved agent reporting

[Kylo Ginsberg (JIRA)]

Title: Message Title

Kylo Ginsberg commented on an issue   Re: Document report format changes for improved agent reporting Jason Antman yeah this makes me sad too. The hold-up is just there being too few hours in the day. Wrt PE, rest assured I totally agree that they're just one more consumer of the report format, and in fact are mostly an interested stakeholder rather than a definer of the details. E.g. the current breakdown of tasks in the linked epic (PUP-283) was motivated in part by conversations in IRC a few months ago. If you have additional error scenarios or additional comments on what report changes you'd like to see (or patches :>), please add them to either this ticket or the parent epic. Add Comment   Puppet / PUP-916 Document report format changes for improved agent reporting This should allow the report reader to determine: * if a cached catalog was used * if so, whether it was due to preference or an error during the agent run * if an error, at what step in the agent run * if during catalog compilation, any error messages the server makes available This proposal should be run by the PE / PuppetDB folks since they will... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.