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

Remove PropertyValuesEqual method from Provider interface #3702

Merged
merged 3 commits into from
Aug 11, 2023

Conversation

johngmyers
Copy link
Contributor

Description

This is prep work for the webhook provider. Removes the frequently-called PropertyValuesEqual method from the Provider and Registry interfaces, requiring providers to normalize provider-specific properties in their AdjustEndpoints method.

Checklist

  • Unit tests updated
  • End user documentation updated

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jun 17, 2023
@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jun 17, 2023
@johngmyers johngmyers force-pushed the provider-specific-2 branch 2 times, most recently from d2cfcbc to c4eae81 Compare June 18, 2023 23:46
@johngmyers johngmyers mentioned this pull request Jun 19, 2023
Copy link
Contributor

@Raffo Raffo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@johngmyers In general this looks good to me. One question I have is how can we make sure that we spot any regressions with this change. Do you have access to some of the providers impacted, for example cloudflare?

plan/plan_test.go Show resolved Hide resolved
@johngmyers
Copy link
Contributor Author

I do not have access to Cloudflare.

To spot AWS regressions I added to the AWS tests assertions that AdjustEndpoints is idempotent over the test data and that the Records expected data is already normalized (modulo records added by normalization, after my AAAA alias PR).

The Cloudflare unit tests do not make assertions about the content of returned records, just their expected number. So I did not attempt to adjust those tests.

Copy link
Contributor

@Raffo Raffo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@johngmyers a couple more comments, then we're good to go.

plan/plan_test.go Show resolved Hide resolved
plan/plan_test.go Show resolved Hide resolved
provider/designate/designate.go Show resolved Hide resolved
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 20, 2023
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 21, 2023
@Raffo
Copy link
Contributor

Raffo commented Aug 11, 2023

/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 Aug 11, 2023
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johngmyers, mloiseleur, Raffo

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 Aug 11, 2023
@johngmyers
Copy link
Contributor Author

/retest

@k8s-ci-robot k8s-ci-robot merged commit 8623a2a into kubernetes-sigs:master Aug 11, 2023
14 checks passed
@johngmyers johngmyers deleted the provider-specific-2 branch August 11, 2023 17:43
@johngmyers johngmyers mentioned this pull request Sep 13, 2023
2 tasks
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/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants