Clients should provide a direct interface to reports
|Affected Puppet version:||0.25.1
If software is calling Puppet, it is currently difficult for that software to figure out what has happened in a Puppet run.
It should be possible to have the report provided on stdout or some equivalent, in such a way that the caller can easily figure out exactly what happened.
For this to be any use, #2759 needs to also be included.
- Priority changed from Normal to High
- Assignee set to Luke Kanies
Anyone have any opinion on how this should be implemented?
I’m thinking some combination of a —show-report flag on the client, and/or storing the most recent report on the client.
Just the latter would be a good start, I think, but not quite there.
- Status changed from Accepted to Needs Decision
I think the proposed approach would work as a first cut.
- Priority changed from High to Normal
- Target version changed from 2.6.0 to 52
There should definitely be a way to store reports on the client!
- Status changed from Needs Decision to Accepted
- Assignee deleted (
- Target version changed from 52 to 2.7.x
I figure just starting by storing the latest report on the client is good enough.
- Target version changed from 2.7.x to 3.x
Any objections to always storing the most recent report on disk?
I think this would be useful for multiple purposes.
atm reports are already stored on the client disk but only when reporting is enabled
Where does the report get stored?
And now that reporting is enabled by default, this should be better, at least.
Where lastrunreport points to which is $statedir/last_run_report.yaml and also pretty awesome from quick feedback is last_run_summary.yaml which is always written and just have a summary – more or less the metrics in report, really nice for quickly figuring out what happens.
Also available in: Atom