-
Notifications
You must be signed in to change notification settings - Fork 1.3k
feat: validate db schemas CI test #4094
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
Added a new CI workflow to validate database schemas against committed versions, helping prevent schema drift and inconsistencies.
- Added
.github/workflows/validate-db-schemas.yml
that triggers on PR events affectingbackend/src/db/**
, runs migrations and compares generated schemas with committed ones - Created automatic validation checks that fail CI if schema changes are not properly documented and committed
- Modified
.infisicalignore
to handle API keys in the new workflow configuration - Leverages existing Docker configurations from other workflows for consistent test environments
- Implements proper cleanup of test resources after schema validation
2 files reviewed, 1 comment
Edit PR Review Bot Settings | Greptile
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
…ical/infisical into daniel/validate-db-schemas
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few comments
Description 📣
This PR introduces a new CI test to verify that the database state matches the committed schemas.
Type ✨