cron: wire bib refresh-iom for daily CMS IOM sync #343
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #304/#305/#306.
The
uv run stack bib refresh-iomcommand is idempotent and does ingest → watch-iom → attach → sync-zotero in one pass. It needs a scheduler so the library stays up-to-date without hand-triggering.Task:
uv run stack bib refresh-iomnightly.Acceptance: container fires automatically, log shows no human invocation, futurepdf CHANGED events auto-open an issue tagged
cms-update.Closing — shipped in
759d8d5.src/bib/iom_alert.py—file_iom_change_alert()opens acms-update-tagged Gitea issue whenwatch-iomreports a futurepdf.pdf SHA-256 change. Auto-creates the label if it doesn't exist.src/cli/bib.py:refresh-iom— added--file-issue/--no-file-issueflag (default True). Calls the alert when changed=True.tests/bib/test_iom_alert.py— 4 unit tests.bib-refresh-iom.{service,timer}armed for daily 03:30 EDT withPersistent=true(catches up if the box was off when scheduled). First run tonight at 03:30.Out of scope (per issue body):