From 7699a0be0e7cea4212dd1deaeb558b44ec798e1e Mon Sep 17 00:00:00 2001 From: Tom Limoncelli Date: Mon, 10 Apr 2023 17:44:40 -0400 Subject: [PATCH] Update "provider request" docs (#2269) Co-authored-by: Tom Limoncelli --- documentation/bug-triage.md | 6 +----- documentation/providers.md | 20 ++++++++++++++++++++ 2 files changed, 21 insertions(+), 5 deletions(-) diff --git a/documentation/bug-triage.md b/documentation/bug-triage.md index ee6b6679a..4eae829cc 100644 --- a/documentation/bug-triage.md +++ b/documentation/bug-triage.md @@ -21,7 +21,6 @@ priority: # How to handle a provider request - 1. Change the subject to be "Provider request: name of the provider" 1. Set the label `provider-request` 1. Respond to the issue with the message below @@ -46,10 +45,7 @@ I will now close the issue. I know that's a bit confusing, but it will remain o If someone would like to volunteer to implement this, please re-open this issue and add the tag `has-pr`. -We encourage you to try adding this provider yourself. We've tried to -make the process as friendly as possible. Many people have reported -that adding a provider was their first experience writing Go. The -process is documented here: +We encourage you to try adding this provider yourself. We've tried to make the process as friendly as possible. Many people have reported that adding a provider was their first experience writing Go. The process is documented here: https://docs.dnscontrol.org/developer-info/writing-providers If you need assistance, please speak up in this issue and someone will get back to you ASAP. ``` diff --git a/documentation/providers.md b/documentation/providers.md index 1cc930da7..eb8867465 100644 --- a/documentation/providers.md +++ b/documentation/providers.md @@ -154,9 +154,29 @@ code to support this provider, we'd be glad to help in any way. * [CoreDNS](https://github.com/StackExchange/dnscontrol/issues/1284) (#1284) * [EU.ORG](https://github.com/StackExchange/dnscontrol/issues/1176) (#1176) * [EnCirca](https://github.com/StackExchange/dnscontrol/issues/1048) (#1048) +* [Imperva](https://github.com/StackExchange/dnscontrol/issues/1484) (#1484) * [Infoblox DNS](https://github.com/StackExchange/dnscontrol/issues/1077) (#1077) * [Joker.com](https://github.com/StackExchange/dnscontrol/issues/854) (#854) * [Plesk](https://github.com/StackExchange/dnscontrol/issues/2261) (#2261) * [RRPPRoxy](https://github.com/StackExchange/dnscontrol/issues/1656) (#1656) * [RcodeZero](https://github.com/StackExchange/dnscontrol/issues/884) (#884) * [SynergyWholesale](https://github.com/StackExchange/dnscontrol/issues/1605) (#1605) +* [UltraDNS by Neustar / CSCGlobal](https://github.com/StackExchange/dnscontrol/issues/1533) (#1533) + +#### Q: Why are the above Github issues marked "closed"? + +A: Following [the bug triage process](/developer-info/bug-triage), the request +is closed once it is added to this list. If someone chooses to implement the +provider, they re-open the issue. + +#### Q: Would someone write a provier for me? + +A: The maintainer of DNSControl does not write new providers. New providers +are contributed by the community. + +DNSControl tries to make writing a provider as easy as possible. DNSControl +does most of the work for you, you only have to write code to authenticate, +download DNS records, and perform create/modify/delete operations on those +records. Please read the directions for [Writing new DNS +providers](/developer-info/writing-providers). The DNS maintainers will gladly +coach you through the process.