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

Refactor, cleanup Akamai provider #1870

Merged
merged 6 commits into from
Jan 13, 2021

Conversation

edglynes
Copy link
Contributor

Ref. #1846
Refactored provider to use Edge DNS API library. Updated library version to 1.0.0. Cleaned up the implementation by organizing into logical functions and removing un necessary logic. Updated test automation to align with logic changes. Added additional optional arguments for API authentication. Updated the tutorial name and content to reflect Akamai DNS product name change and validation.

/kind feature
/cc @Raffo @sheerun @tariq1890

refactor: remove dns api logic and use dns api library
enhancement: add additional args for auth credential retieval
cleanup: simplify, organize processing logic
test: update automation and validate
update README.md to include akamai provider changes
update CHANGEME.md to rename akamai-fastdns refs to akamai-edgedns
update Akamai tutorial name and content for updated functionality and tested scenarios.
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Nov 23, 2020
@k8s-ci-robot
Copy link
Contributor

Welcome @edglynes!

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/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Nov 23, 2020
@edglynes
Copy link
Contributor Author

/assign @njuettner

@edglynes
Copy link
Contributor Author

@njuettner @seanmalloy Hi. I had added prior contributors as reviewers as a courtesy. Don't think they are active. This PR is ready for submission. I've reviewed, ran make lint, make test, make build and make build.docker all successfully and tested. Can one of you review and approve? Else, what do you suggest? Thx.

@edglynes
Copy link
Contributor Author

edglynes commented Dec 2, 2020

/assign @njuettner @Raffo

@edglynes
Copy link
Contributor Author

edglynes commented Dec 2, 2020

@sheerun @tariq1890 - any interest in reviewing this PR given prior contributions? hx.

@sheerun
Copy link
Contributor

sheerun commented Dec 2, 2020

I don't use akamai, it needs an owner. Maybe send e-mail to akamai if they are willing to designate someone to support it

@edglynes
Copy link
Contributor Author

edglynes commented Dec 2, 2020

I don't use akamai, it needs an owner. Maybe send e-mail to akamai if they are willing to designate someone to support it

I work for Akamai and am quite willing to be the owner, however I can't review, nor approve, the PR I authored...

@sheerun
Copy link
Contributor

sheerun commented Dec 2, 2020

Then you need to find your way into https://github.com/kubernetes/org/blob/master/config/kubernetes-sigs/org.yaml which means you need to find 2 reviewers that are willing to be your sponsors (I know, pain, maybe it's best to ask around at slack channels like #sig-network or #external-dns). Right now I'm only member, not reviewer.

Then you'll probably be added to OWNERS file of akamai in this repository which means you would not need as comprehensive reviews from others and you could review and approve PRs for akamai as well

@sheerun
Copy link
Contributor

sheerun commented Dec 2, 2020

@sheerun
Copy link
Contributor

sheerun commented Dec 2, 2020

All I can do is approve this PR, which I will do because all tests are preserved and changes seems to be refactor-only

/approve

@sheerun
Copy link
Contributor

sheerun commented Dec 2, 2020

Also note that my approval doesn't mean much because I'm owner of cloudflare provider, not a reviewer of whole repository

provider/akamai/akamai.go Outdated Show resolved Hide resolved
provider/akamai/akamai.go Outdated Show resolved Hide resolved
provider/akamai/akamai.go Outdated Show resolved Hide resolved
provider/akamai/akamai.go Outdated Show resolved Hide resolved
provider/akamai/akamai.go Outdated Show resolved Hide resolved
provider/akamai/akamai.go Outdated Show resolved Hide resolved
provider/akamai/akamai.go Outdated Show resolved Hide resolved
Copy link
Member

@njuettner njuettner left a comment

Choose a reason for hiding this comment

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

I went trough the code a bit and saw some flaws. Could take another look at your code and review it again you might see some additional things which you want to optimize?

You can ping me again once you feel confident 🙂

- removed commented code
- removed unnecessary provider checks in GetRecords and AddChanges
- removed noisy debugf comments
- updated validation keys check
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 3, 2020
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 3, 2020
@edglynes
Copy link
Contributor Author

edglynes commented Dec 4, 2020

@njuettner Went thru all feedback and pushed update. Please reviewand approve. Thx.

Copy link
Member

@njuettner njuettner left a comment

Choose a reason for hiding this comment

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

one small nit since we already have released v0.7.4 🤞

docs/tutorials/akamai-edgedns.md Outdated Show resolved Hide resolved
docs/tutorials/akamai-edgedns.md Outdated Show resolved Hide resolved
docs/tutorials/akamai-edgedns.md Outdated Show resolved Hide resolved
@edglynes
Copy link
Contributor Author

Hi @njuettner. I made last changes you requested a few weeks ago. Can you approve this PR and merge? Thx.

@edglynes
Copy link
Contributor Author

edglynes commented Jan 4, 2021

@njuettner happy new year. I rebased today from master. All review comments addressed. Please approve and merge. Thank you.

@Raffo @seanmalloy @hjacobs @linki I've not heard back from Nick in over a month. This PR is/has been ready to go. All review comments addressed and recently rebased. Can any of you approve and merge or direct me to someone who can?

Thank you.

Ed

Copy link
Member

@njuettner njuettner left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: edglynes, njuettner, sheerun

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 Jan 13, 2021
@k8s-ci-robot k8s-ci-robot merged commit 7195323 into kubernetes-sigs:master Jan 13, 2021
@billinghamj
Copy link

It seems like this was published in v0.8.0, but now that release seems to have disappeared...? Any idea why? Bit confusing! 😂

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. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants