[Pkg-puppet-devel] reports retention policy

[Thomas Goirand]

On 8/28/24 16:54, Jérôme Charaoui wrote:
> If we really don't care about diverging from how upstream ships Puppet, 
> and we agree reports aren't useful, then why not just disable them by 
> default (report = false) ? [1]

That'd be better than letting the system disk getting full.

> Checking whether clients have applied their catalog can be done other 
> ways than checking the report timestamp, such as looking at 
> last_run_summary.yaml or PuppetDB (catalog_timestamp).

I cannot find such file in my server. Where is it supposed to be stored?

On 8/28/24 17:09, Antoine Beaupré wrote:
 > I think that's a major regression, and we should fix it. We have
 > shipped that regression in bookworm already, so our "current"
 > retention policy is *already* an undocumented change (from 30 days to
 > "infinity"). If we want to fix *that*, we need a stable update.

We could fix stable ...

 >> If we really don't care about diverging from how upstream ships
 >> Puppet, and we agree reports aren't useful, then why not just disable
 >> them by default (report = false) ? [1]
 >
 > I think that's a good idea.

Ok for Trixie, but for stable, I don't think we can just disable 
reports. A clean job (the same as in Bullseye?) sound more appropriate 
and acceptable by the stable release team.

On 8/28/24 17:09, Antoine Beaupré wrote:
 > It kind of blows my mind that this is enabled by default *and*
 > simultaneously not managed. That seems like a really Bad Idea.
 >
 > Let's just turn off reports and teach people how to use PuppetDB in
 > the NEWS file, possibly fixing this to stable after a period in
 > trixie?

Agreed.

Thanks for this very open discussion,
Cheers,

Thomas Goirand (zigo)