-
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
chore: graduate feature gate FillIDs to Beta and set to true by default #4746
Conversation
c99eafd
to
07bc694
Compare
E2E (targeted) tests with KIND-based clusters were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/6328663139 |
Pull request was converted to draft
07bc694
to
9e2846c
Compare
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4746 +/- ##
=======================================
- Coverage 67.9% 67.8% -0.1%
=======================================
Files 165 165
Lines 19291 19291
=======================================
- Hits 13102 13087 -15
- Misses 5420 5433 +13
- Partials 769 771 +2
☔ View full report in Codecov by Sentry. |
9e2846c
to
f5bcffa
Compare
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.
I just wonder why do we need the ids in golden test files 🤔
What this PR does / why we need it:
Graduate feature gate
FillIDs
to Beta and set totrue
by default. Adjust code, tests (regenerate golden tests tests cases), CI, etc. Mention it inCHANGELOG.MD
andFEATURE_GATES.md
.Which issue this PR fixes:
Closes #4739
Special notes for your reviewer:
Dereferencing any field in
KongConsumer
is risky, because each one is a pointer, thus when an error is returned (it was the case for envtests that don't care about it) panic occurred. UsingFriendlyName(...)
is always safePR 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