We made a ticket (01380412) about a bug in

sce_linux::utils::packages::linux::auditd

but the response from support seems wrong. That class has an (undocumented) parameter

$manage_auditd_rulesd

which to me seems clearly intended to be used for enabling full management of the directory

/etc/audit/rules.d

, meaning that unmanaged files will be purged. That parameter defaults to

false

. The bug is that setting that parameter to

true

only sets

purge => true

on the

file

resource, and the

recurse

attribute is missing. From the docs,

purge

only makes sense when `recurse => true`: https://github.com/puppetlabs/puppet/blob/e227c27540975c25aa22d533a52424a9d2fc886a/references/types/file.md?plain=1#L492-L493 But the response from support was that this is intentional: "The

sce_linux

module is designed to manage only the files it creates and does not purge others to avoid accidentally removing any custom configurations you may have in the same directory. Our team has intentionally chosen not to remove unmanaged files to prevent potential issues." This response from support doesn't make sense because you can't accidentally remove custom configurations when the default value for the parameter is

false

, you have to intentionally set it to

true

. It is pretty clear that the parameter was intended to allow for purging unmanaged files, otherwise the parameter is useless. There is no other way to accomplish this, since the

file

resource in

sce_linux

is managing the directory, we can't also manage the directory in our own code. Can we get this ticket reevaluated?

I will raise this with the Support team for another look. However, from a quick skim of the case, the reasoning given was relayed from the engineering team that works on SCE.

Thanks.