-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[TXT Registry] Fix Records()
case handling
#3912
[TXT Registry] Fix Records()
case handling
#3912
Conversation
Hi @Sewci0. 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 Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions 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/test-infra repository. |
It's a fix to: #3724. @johngmyers / @szuecs can you please take a look? |
/ok-to-test |
/lgtm |
/assign @szuecs |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: johngmyers The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…case [TXT Registry] Fix `Records()` case handling
There's an issue in
Records()
function inTXT Registry
. When using templated affix,recordType
will be passed in lowercase in:external-dns/registry/txt.go
Lines 140 to 144 in 6a53959
This will then fail to match against the computed key with uppercase recordType in:
external-dns/registry/txt.go
Lines 159 to 175 in 6a53959
Surprisingly it wasn't caught by any of the existing tests. I've added few cases should capture that in the future.
Checklist