----- Original Message ----- > From: "Michal Růžička" <michal.ruzi...@puppetlabs.com> > To: "puppet-dev" <puppet-dev@googlegroups.com> > Sent: Tuesday, 22 March, 2016 13:42:29 > Subject: [Puppet-dev] Re: Overriding lastrunreport for certain puppet runs?
> All, > In pxp-module-puppet we need a reliable way of reading the last run > reports written by puppet agent runs triggered by the pxp-module-puppet. > In a proposed PR <https://github.com/puppetlabs/pxp-agent/pull/368> we > achieve that by passing unique file names via to the --lastrunreport > option to those puppet runs. The drawback is that those runs obviously > don't write their run reports to the default last run report location. > Which therefore may contain outdated information. > Is this something to be concerned about? I'd say yes, these files are effectively public APIs, users would build tools on them and would expect them to be current - tools including mcollective fwiw -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/2132019388.145945.1458651017438.JavaMail.zimbra%40devco.net. For more options, visit https://groups.google.com/d/optout.
