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

Request for Bluecat provider #1198

Closed
jbarnett1981 opened this issue Sep 17, 2019 · 19 comments
Closed

Request for Bluecat provider #1198

jbarnett1981 opened this issue Sep 17, 2019 · 19 comments
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. new-provider

Comments

@jbarnett1981
Copy link

Similar to other ipam products (like Infoblox), a provider for Bluecat would be very nice.

@njuettner njuettner added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. new-provider labels Sep 24, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 23, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 22, 2020
@jbarnett1981
Copy link
Author

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jan 23, 2020
@kvendingoldo
Copy link
Contributor

I started to implement bluecat provider for external-dns

@seanmalloy
Copy link
Member

seanmalloy commented Mar 12, 2020

@kvendingoldo and @jbarnett1981 do you want to use the standard XML API for BlueCat or the newer BlueCat API gateway(REST API)?

Here is the information about the BlueCat API Gateway ... https://www.bluecatnetworks.com/resources_doc/whitepaper/bluecat-gateway.pdf.

My team has some code for adding BlueCat support using the API Gateway here ... https://github.com/KohlsTechnology/external-dns/tree/timcurless-feature/provider. See bluecat.go in that folder. We were hoping on creating a pull request in the near-ish future. The code needs some more polishing and testing.

Also, here is a branch that adds DNS TXT record support to the BlueCat API Gateway product ... https://github.com/KohlsTechnology/gateway-workflows/tree/timcurless-feature. Hoping to submit a pull request for this soon too.

cc: @vinny-sabatini @sanbornick @linit01 @timcurless

@seanmalloy
Copy link
Member

@jbarnett1981 and @kvendingoldo I submitted work in progress PR #1506 to add a BlueCat provider that uses the BlueCat API Gateway(REST API). I'm hoping to be able to finish up this PR in the next few months.

@seanmalloy
Copy link
Member

/assign @seanmalloy

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 9, 2020
@seanmalloy
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 9, 2020
@seanmalloy
Copy link
Member

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 18, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 16, 2020
@seanmalloy
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 18, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 16, 2021
@sanbornick
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 16, 2021
@sjbodzo
Copy link

sjbodzo commented Mar 8, 2021

@seanmalloy

@jbarnett1981 and @kvendingoldo I submitted work in progress PR #1506 to add a BlueCat provider that uses the BlueCat API Gateway(REST API). I'm hoping to be able to finish up this PR in the next few months.

Any update on BlueCat support? The issue referenced in the PR looks like it closed in October of last year.

@seanmalloy
Copy link
Member

@seanmalloy

@jbarnett1981 and @kvendingoldo I submitted work in progress PR #1506 to add a BlueCat provider that uses the BlueCat API Gateway(REST API). I'm hoping to be able to finish up this PR in the next few months.

Any update on BlueCat support? The issue referenced in the PR looks like it closed in October of last year.

@sjbodzo I'm hoping to still finish the linked PR. The last time it was worked on we had everything working except for deleting DNS records. Beyond that the code is a bit messy and unit tests could use some improvement.

@seanmalloy
Copy link
Member

@sjbodzo I updated PR #1506 and will be soon be requesting a final review from the project maintainers. I think there might be hope that this will merge soon-ish. Cross your fingers.

@seanmalloy
Copy link
Member

PR #1506 for the initial BlueCat support has been merged.

/close

@k8s-ci-robot
Copy link
Contributor

@seanmalloy: Closing this issue.

In response to this:

PR #1506 for the initial BlueCat support has been merged.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. new-provider
Projects
None yet
Development

No branches or pull requests

8 participants