-
Notifications
You must be signed in to change notification settings - Fork 9
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
SIMSBIOHUB-449: Upgrade to Postgres 17 #1428
Conversation
Openshift URLs for the PR Deployment: |
73c1ea7
to
b7f9472
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #1428 +/- ##
=======================================
Coverage 46.08% 46.08%
=======================================
Files 910 910
Lines 23752 23752
Branches 3500 3500
=======================================
Hits 10947 10947
Misses 12189 12189
Partials 616 616 ☔ View full report in Codecov by Sentry. |
18c823f
to
890817a
Compare
- Wrap most instances of "system_user" in double quotes, as it is not a reserved word in postgres. - Add migration to drop biohub_dapi_v1 schema - Disable static deploy db setup step
b6fdb71
to
0214854
Compare
Quality Gate passedIssues Measures |
Quality Gate passedIssues Measures |
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.
🕷️
Links to Jira Tickets
https://apps.nrs.gov.bc.ca/int/jira/browse/SIMSBIOHUB-449
Description of Changes
Upgrade local and remote Postgres versions from 12.5 to 17.
system_user
in double quotes (as it is a reserved word and using it unwrapped will fail in the database.system_user
when it is used in a knex query builder.Cleanup
Testing Notes
Database builds/deploys as usual.
API works as usual.
Note:
Migration Plan
I've included all of the steps in a comment in the Jira ticket.
The main thing to be aware of is that this PR disables the dev/test/prod database knex migration step, so that I can run it manually one time during this version upgrade (we can re-enable it afterwards).