Automated O&M Tasks

Note (2026-07-23): This page covers automation for the legacy CKAN-based catalog-old.data.gov (running through fall 2026) and inventory.data.gov, which are still CKAN-based. For the current catalog.data.gov (Flask/OpenSearch) app's automated tasks (restart, sitemaps, Snyk, DB model drift check), see catalog.data.gov.

Routine Tasks

These repositories will automatically create failure tickets, so no need to check the Actions

• Inventory Restart Action
• Inventory deploy Action
• Catalog Restart Action
• Catalog Deploy Action
• All Automated Catalog CKAN Tasks have been consolidated into a single action. A few unique features of these actions
  • An error issue will be created if any of the tasks have a non-zero exit code.
  • https://github.com/GSA/catalog.data.gov/issues/848 is an always open informational issue that is updated each night with a link to the newest run. Inspect the link and update the comment on the issue with the number of datasets changed.
  • If the DB-Solr-Sync action takes more than 30 mins, it will automatically raise an Error Issue (similar to a non-zero exit code).
  • https://github.com/GSA/catalog.data.gov/issues/847 is an always open informational issue that is updated each night with a link to the newest run. Inspect the link and update the comment on the issue with the number of datasets changed.
  • If the Tracking-Update action takes more than 210 mins, it will automatically raise an Error Issue (similar to a non-zero exit code).

Snyk Scans

For Catalog and Inventory, snyk will create PR's if a dependency needs to be updated.

• Inventory Snyk Scan
• Catalog Snyk Scan

• If either of these actions failed and a PR was created, review and approve/triage it as needed
• If either of these actions failed and a PR was not created, an unfixable vulnerability was found, check the Snyk UI Console to triage the vulnerability.