-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
fix: Support conversion from/to simple to/from other routing policies for the AWS provider. #3159
fix: Support conversion from/to simple to/from other routing policies for the AWS provider. #3159
Conversation
… for the AWS provider.
|
Welcome @jessegonzalez! |
/easycla |
@szuecs could you please review this? I'd love to see route53 records converted from simple to weighted 🙏 |
/approve |
cc: @njuettner and cc: @seanmalloy please review when you get a chance. At the moment, our workaround is to clickops a simple routing record into a weighted record with the same set identifier as external-dns is trying to create in order to get it to resolve correctly. This change will prevent us from having to do the workaround. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jessegonzalez, nitrocode, szuecs 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 |
Thank you @szuecs ! Please let us know if there will be a patch release planned. We're very eager for the new version 😄 |
I never did a release, but @Raffo will likely do one as soon as the plugin provider is ready |
This broke CI. It's the second time this happens in the past 2 weeks. I'm gonna have to revert. |
Hmm. I see how the action failed ci. How come the ci didn't fail tests in this pr? Does ci only run on prs after merge and not as a pr check itself? The ci checks looks like they should run on pr. external-dns/.github/workflows/ci.yml Lines 3 to 7 in 0fcfb29
|
@nitrocode it was my fault, because I can merge but I had not yet the rights to run tests and missed to ask for test run. |
Description
This PR allows Route53 record updates to change the routing policy to/from simple from/to other routing policies. These record modifications do not support UPSERT, but instead, require DELETE/CREATE to succeed.
The AWS provider function
createUpdateChanges
has been updated with another conditional to test if one of the old/new set identifiers is the empty string and the other is not.The AWS Provider test
TestAWSApplyChanges
has been updated to validate the change.While examining what should be changed, I identified that the AWS provider function
UpdateRecords
is unused, and may be a candidate for removal. If desired I can address that here as well.Fixes #3141
Checklist