Question about scheduling the first Saturday of January using Cron and date command

[CrypticCommit]

What are you trying to do?
I am trying to schedule a Cron job that runs specifically on the first Saturday of January at midnight. I noticed that the Cron expression 0 0 1 ? 1 SAT#1 * can achieve this, but according to the configuration reference it has not allowed special characters.
Likewise, I want to know if a similar approach using standard cron syntax and the date command is supported.

What is your current configuration?
Here is the Cron expression I am considering:

# run every Saturday in January at midnight, check if it's the first Saturday
BACKUP_CRON_EXPRESSION="0 0 * 1 6 [ "$(date +\%d)" -le 7 ]"

Log output
time=2025-04-05T17:35:13.058+02:00 level=ERROR msg="Fatal error running command: unexpected command substitution at 1:38" error="main.(*command).runInForeground: error scheduling: main.(*command).schedule: error sourcing configuration: main.sourceConfiguration: error loading config files: main.loadConfigsFromEnvFiles: error reading config file /etc/dockervolumebackup/conf.d/04yearly.conf: main.source: error expanding env: unexpected command substitution at 1:38"

Additional context
I would like to confirm if this approach is valid in your Cron implementation. If it is not supported, could you recommend an alternative method to schedule a job for the first Saturday of January? Any guidance or examples would be greatly appreciated.

[CrypticCommit]

As a workaround, I will be using the following Cron expression:
sudo vi /etc/cron.d/backup_nextcloud_cron
0 0 * 1 6 root [ "$(date +\%d)" -le 7 ] && podman exec podman_backup_nextcloud /bin/sh -c 'set -a; source /etc/dockervolumebackup/conf.d/04yearly.conf; set +a && backup'

[m90]

I am not sure how I would model this tbh. The package used is https://github.com/robfig/cron and the documentation is copied verbatim from there. Maybe the repo's issues have some helpful information that helps your uese case?

[CrypticCommit]

@m90 Thanks for the info.

It seems to be that robfig/cron is abandoned.
This fork clarkmcc/cron supports it (I think). The same issue is connected to 434 and 319.

[m90]

Wouldn't this fork only support L when your use case would need #?

[CrypticCommit]

Wouldn't this fork only support L when your use case would need #?

True, but in my use case I do not really care about first (SAT#1) or last one (L). 😄

[m90]

I think I'd be fine to switch to the fork sometime soon to enable this, but I have to admit I don't think it'd warrant cutting a new release. Are you able to work off a self-built image in the meantime?

[m90]

So I just tried swapping the dependency and unfortunately I found out that the clarkmcc fork is based off the v1 version of package cron, when the latest release of the upstream package is already at v3. I would think this happened inadvertently because of the strange ways in which Go modules handle major versions, but unfortunately it also means that swapping out the package isn't really an option as the code in this image relies on features provided by that v3.

I don't know how much work it would be to create yet another fork of package cron and backport the changes that allow providing Ls to the v3 branch, but until then, this change is unfortunately blocked.