-
Notifications
You must be signed in to change notification settings - Fork 589
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
feat: all-in-one manifests migrations job improvement #4116
Conversation
E2E (targeted) tests were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/5135226233 |
96a5c25
to
b20ddd3
Compare
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #4116 +/- ##
=======================================
- Coverage 60.4% 55.5% -4.9%
=======================================
Files 150 146 -4
Lines 16745 16603 -142
=======================================
- Hits 10114 9224 -890
- Misses 6000 6861 +861
+ Partials 631 518 -113 ☔ View full report in Codecov by Sentry. |
What this PR does / why we need it:
kong migrations bootstrap
alone works fine when installing a fresh instance of KIC with DB-backed Kong. It doesn't work though when we'd like to upgrade and keep the DB state between the upgrades, because it only bootstraps a fresh database - when there is one already in existence, it just returns.This PR aims to solve this issue by adding additional commands to the migrations job:
kong migrations up && kong migrations finish
which will make the job detect new migrations that need to be run after the upgrade and finish them.Which issue this PR fixes:
It was discovered when writing E2E tests for #4025.
Special notes for your reviewer:
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR