The Monuments database ~/jobs.yml (scheduled cron jobs) is maintained by hand on the Toolforge, disconnected from the repo.

That meant an image bump in defaults.sh (TOOLFORGE_PYTHON_IMAGE) only propagated to the one-shot deploy jobs, while the scheduled update-monuments job kept running on the old image specified in ~/jobs.yml.

By maintaining a jobs.yml.template as the source of truth in the repository we can ensure it remains synced with TOOLFORGE_PYTHON_IMAGE in defaults.sh. If deploy recreates the jobs.yml file and loads it into the jobrunner then the changes should be picked up on the subsequent start of the job.

After deployment the old ~/jobs.yml should be removed to avoid confusion.