harvest deployment should fail on failed DB migration
Open
bug
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 200
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 5
Description
When an Alembic migration script changes, any database upgrade failure should cause the deployment to fail immediately. This prevents the deployment from progressing beyond the staging environment and avoids deploying the application to prod against an incompatible or partially migrated database.
## How to reproduce
We see [harvesting issues on prod](https://gsa-tts.slack.com/archives/C2N85536E/p1783345955660409) due to failed db migration.
Contributor guide
Assessment
This issue has not been assessed yet.