Contact Details
No response
What happened?
Current: When a migration fails as part of a production deployment, the deployment is allowed to continue. This causes issues where application code is not properly synchronized with the underlying data model and schema represented in the database.
We also don't have any observability into migration failures in our Grafana dashboard. This container's runtime logging isn't currently displayed anywhere.
Requirement: Failed migrations fail deployments with actionable log output.
What is the version of refactor-platform-rs that you're seeing the problem on?
1.0.0-beta1
Any related code or configuration details to produce this issue as well as relevant log output.
Contact Details
No response
What happened?
Current: When a migration fails as part of a production deployment, the deployment is allowed to continue. This causes issues where application code is not properly synchronized with the underlying data model and schema represented in the database.
We also don't have any observability into migration failures in our Grafana dashboard. This container's runtime logging isn't currently displayed anywhere.
Requirement: Failed migrations fail deployments with actionable log output.
What is the version of refactor-platform-rs that you're seeing the problem on?
1.0.0-beta1
Any related code or configuration details to produce this issue as well as relevant log output.