Skip to content
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

Conversation

jessegonzalez
Copy link
Contributor

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

  • Unit tests updated
  • End user documentation updated

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Nov 15, 2022

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: jessegonzalez / name: Jesse Gonzalez (606ce34)

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Nov 15, 2022
@k8s-ci-robot
Copy link
Contributor

Welcome @jessegonzalez!

It looks like this is your first PR to kubernetes-sigs/external-dns 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/external-dns has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Nov 15, 2022
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Nov 15, 2022
@jessegonzalez
Copy link
Contributor Author

/easycla

@nitrocode
Copy link
Contributor

@szuecs could you please review this? I'd love to see route53 records converted from simple to weighted 🙏

@nitrocode
Copy link
Contributor

/approve

@nitrocode
Copy link
Contributor

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.

@szuecs
Copy link
Contributor

szuecs commented Dec 2, 2022

/approve
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 2, 2022
@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 2, 2022
@k8s-ci-robot k8s-ci-robot merged commit d03b9fb into kubernetes-sigs:master Dec 2, 2022
@nitrocode
Copy link
Contributor

Thank you @szuecs ! Please let us know if there will be a patch release planned. We're very eager for the new version 😄

@szuecs
Copy link
Contributor

szuecs commented Dec 2, 2022

I never did a release, but @Raffo will likely do one as soon as the plugin provider is ready

@Raffo
Copy link
Contributor

Raffo commented Dec 3, 2022

This broke CI. It's the second time this happens in the past 2 weeks. I'm gonna have to revert.

@nitrocode
Copy link
Contributor

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.

on:
push:
branches: [ master ]
pull_request:
branches: [ master ]

@szuecs
Copy link
Contributor

szuecs commented Jan 4, 2023

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Errors thrown when converting Route53 CNAME record from simple routing policy to weighted
5 participants