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

New provider to support complicated multi-dns-provider setups #605

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

captncraig
Copy link
Contributor

This adds a "multi" provider that dynamically creates and selects dns providers to use on a domain-by-domain basis. I need this for our production setup because:

  1. We need a single certificate that spans many domains, including multiple wildcards.
  2. Most domains are hosted on multiple dns providers (google cloud and r53, both active all the time).
  3. Some domains are hosted on different providers from others.
  4. We even have multiple cloudflare accounts with different feature sets that have different domains on them.

Using the "multi" provider, you supply an addition json configuration that specifies which providers are available with their credentials, and which providers should be applied to which domains.

This can be a little complicated to specify, but it seems necessary if your setup is as convoluted as described above.

Godoc documentation should describe pretty well how to use it.

Tested working in some pretty complicated scenarios for production-level certs.

@ldez ldez self-requested a review July 24, 2018 22:18
@ldez
Copy link
Member

ldez commented Aug 1, 2018

@captncraig could you rebase?

@daegalus
Copy link

Any updates on this? it is becoming clear that I might need this in our platform too.

@captncraig
Copy link
Contributor Author

Sorry, I got sidetracked on this and we decided to use our existing dns tool for this as well. I think this feature is still an ok idea, but am reluctant to continue work on it as the config can be a bit tricky, and I can't commit to really offering support going forward. The code is there though. If somebody wants to take it up, rebase and get it merge-ready please do.

@ldez
Copy link
Member

ldez commented Feb 21, 2019

I already start to work on this, but for now I don't found a satisfying approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

3 participants