Describe the bug
When deploying users with this role (without setting cron_allow: true), an empty file /etc/cron.allow is created (except the ansible_managed header).
Quoting crontab(8):
If the /etc/cron.allow file exists, then you must be listed (one user per line) therein in order to be allowed to use this command.
This means that after using this role, no (other) user is allowed to run cron.
Expected behavior
It should be possible to disable the deployment of /etc/cron.allow. Maybe setting a variable like users_cron_allow: false could do the trick. The default could be true, but I am also fine with false.
Describe the bug When deploying users with this role (without setting
cron_allow: true
), an empty file/etc/cron.allow
is created (except theansible_managed
header).Quoting
crontab(8)
:This means that after using this role, no (other) user is allowed to run cron.
Expected behavior It should be possible to disable the deployment of
/etc/cron.allow
. Maybe setting a variable likeusers_cron_allow: false
could do the trick. The default could betrue
, but I am also fine withfalse
.Environment