Fix feature gates string representation#4757
Conversation
|
Hi @immanuwell. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
zac-nixon
left a comment
There was a problem hiding this comment.
/approved
/lgtm
Thanks for the fix!
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: immanuwell, zac-nixon The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4757 +/- ##
==========================================
+ Coverage 56.09% 56.75% +0.65%
==========================================
Files 388 390 +2
Lines 30932 31139 +207
==========================================
+ Hits 17352 17673 +321
+ Misses 12566 12435 -131
- Partials 1014 1031 +17 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Issue
No related issue found.
Description
Tiny fix for
FeatureGates.String(). It was printing the wholeFeatureStatus, so values looked likeGlobalAcceleratorController={false true}instead ofGlobalAcceleratorController=false. That goes sideways when the string is parsed back askey=bool, and pflag can hit this path for flag/default rendering.Repro, before this change:
It fails with
invalid mapStringBool: GlobalAcceleratorController={false true}.Now the output is stable, sorted, and parseable. fwiw this is local CLI/config plumbing, no AWS quota or resource ceiling involved.
Checklist
Tests:
go test ./...also runs conformance/e2e locally and needs kube config plus cluster-name, so that one fails here for env setup only.