Is your feature request related to a problem? Please describe.
<cron><item> on a real box is dominated by entries no playbook should own: base-system jobs (adjkerntz, bogons update, periodic, newsyslog) and package-generated ones (pfBlockerNG, acme). There is currently no module that can assert a single user cron entry (e.g. a nightly config-backup rsync) while leaving the generated siblings alone; the only options are the whole-subtree approach (which fights pfBlockerNG/acme every time they rewrite their items) or hand-written pfsense_phpshell.
Describe the solution you'd like
A pfsense_cron module keyed on command (plus optional who), managing one <item>:
- pfsensible.core.pfsense_cron:
minute: "0"
hour: "3"
mday: "*"
month: "*"
wday: "*"
who: root
command: /usr/local/bin/backup-config.sh
state: presentSemantics like the built-in ansible.builtin.cron: match on command (and who), create/update/delete only that item, then call configure_cron(). This mirrors how pfsense_dhcp_static manages one static map instead of the whole <staticmap> list.
Is your feature request related to a problem? Please describe.
<cron><item>on a real box is dominated by entries no playbook should own: base-system jobs (adjkerntz, bogons update,periodic,newsyslog) and package-generated ones (pfBlockerNG, acme). There is currently no module that can assert a single user cron entry (e.g. a nightly config-backup rsync) while leaving the generated siblings alone; the only options are the whole-subtree approach (which fights pfBlockerNG/acme every time they rewrite their items) or hand-writtenpfsense_phpshell.Describe the solution you'd like
A
pfsense_cronmodule keyed oncommand(plus optionalwho), managing one<item>:Semantics like the built-in
ansible.builtin.cron: match oncommand(andwho), create/update/delete only that item, then callconfigure_cron(). This mirrors howpfsense_dhcp_staticmanages one static map instead of the whole<staticmap>list.