driver / standard (pull_request) Successful in 25s
driver / lint (pull_request) Successful in 26s
driver / types (pull_request) Failing after 35s
driver / test (3.13) (pull_request) Failing after 18s
driver / test (3.12) (pull_request) Failing after 21s
driver / lowest (pull_request) Failing after 17s
driver / build (pull_request) Successful in 30s
driver / security (pull_request) Failing after 40s
CI / driver (pull_request) Failing after 1m25s
driver / publish (pull_request) Skipped
OPNsense keeps its cron jobs in its configuration and runs each as a configd action, so the POSIX implementation does not fit: the driver has no shell, and a job's command is not a shell line. The cron API reads and writes them instead. get_scheduled_jobs reads every job in one request (/api/cron/settings/get, which carries the selected action rather than its display text). A job another component registered is platform, one written by put_scheduled_job carries the napalm-scheduled-job marker in its description and is application, the rest admin. Every job can be enabled and disabled; only an application's job is edited or deleted. put_scheduled_job takes a configd action as command and refuses one configd does not offer; get_scheduled_job_commands lists them. Running a job now is refused: the API cannot run a configd action. Every write reads the job again and refuses one whose digest changed. Parameters are written one per line and only without blanks, quotes or backslashes: OPNsense up to 26.1 splits them as a shell would, 26.7 takes a line per argument, and only such arguments mean the same to both. Requires napalm-device-types 4.26.0. Closes #43