800336 - use /etc/cron.d, not Cron[..], and purge unused crons with puppet

Status: RESOLVED INCOMPLETE

(Infrastructure & Operations :: Infrastructure: Puppet, task)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

Puppet's built-in cron resource stinks.

/etc/cron.d is better, but we don't delete un-managed files from there.

It'd be awesome if we could create an /etc/cron.mozilla.d that we could manage recursively with purge => true.

If that's not possible, finding a way to manage /etc/cron.d/ in such a way that RPMs' crontasks *aren't* deleted would be the next best thing.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

09:03 <%jabba> could also get complicated, just manage one file /etc/cron.d/mozilla and use concat or augeas to purge and add entries to it
09:04 <%jabba> like say, make a /etc/cron.mozilla/ directory, set purge => true on it, then a resource to add individual cron files to it, then an exec statement to cat /etc/cron.mozilla/* > /etc/cron.d/mozilla
09:05 <%jabba> that's how I set up an ssh_authorized_keys module that I never ended up deploying, but it worked great

Comment 2

[Justin Dow [:jabba]]

Low priority, maybe something rtucker wants to take a stab at researching.

Comment 3

[Rob Tucker [:rtucker]]

This would be perfect with a custom type/provider

This is right up my alley.. WOOT WOOT

Comment 4

[:Atoll]

INCOMPLETE as it's low priority and we're not having trouble with Cron resources currently