Also delete the YAML for the jobs that were already marked ensure: absent, so that it's easier to see what's going on. This way, the remaining ensure: absent jobs are just those which have been recently replaced.
The MySQL and MongoDB/DocDB jobs remain for now; they don't have replacement jobs yet.
content-publisher, email-alert-api, publishing-api also don't have replacements yet in staging/integration (but they do in prod). These are the Postgres databases where we transform data between staging and integration rather than just doing a straight dump/restore.
These have been replaced by Kubernetes cronjobs in https://github.com/alphagov/govuk-helm-charts/pull/1346.
Also delete the YAML for the jobs that were already marked
ensure: absent, so that it's easier to see what's going on. This way, the remainingensure: absentjobs are just those which have been recently replaced.The MySQL and MongoDB/DocDB jobs remain for now; they don't have replacement jobs yet.
content-publisher, email-alert-api, publishing-api also don't have replacements yet in staging/integration (but they do in prod). These are the Postgres databases where we transform data between staging and integration rather than just doing a straight dump/restore.
https://trello.com/c/JjTHY62V