[Pkg-puppet-devel] PROPOSAL: reports=none retention policy on the server side

[Antoine Beaupré]

So let's try to settle this thread.

It seems a simple solution would be to switch the server-side
configuration to "reports=none", only on the server, and remove the cron
job.

That way, the *clients* can still send reports, and operators can
*still* enable storing those on disk in YAML by tweaking that setting,
but by default we don't accumulate those.

We would make both changes (remove cron job and change setting) in sid,
then wait for trixie to pick it up, then send a proposed-update for
bookworm.

At this point, I'm not sure it warrants a NEWS file update, but if we do
that we should probably narrow it down to bookworm. Otherwise we could
also update the release notes, like we already did for that peculiar
upgrade. That might be simpler and more visible/useful for people that
might not already have upgraded.

(I would object to doing the NEWS update in sid, as that might confuse
people who *did* upgrade to bookworm correctly, when they upgrade to
trixie.)

If there are no objections to this, I propose we deploy start this
process on the coming Tuesday, September 3rd.

a.
-- 
Dans vos mensonges de pierre
Vous gaspillez le soleil
                        - Gilles Vigneault