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

Initial Acme-Dns plugin #4

Merged
merged 2 commits into from
Apr 30, 2018
Merged

Initial Acme-Dns plugin #4

merged 2 commits into from
Apr 30, 2018

Conversation

rmbolger
Copy link
Owner

Adds a AcmeDns plugin which addresses issue #1 and #2.

This is likely going to be a fairly unique plugin because of the intended acme-dns workflow. When a cert is first created, each name will have a new acme-dns "registration" which generates a unique subdomain on the acme-dns server. Those subdomains need to be manually registered as CNAMEs targets for their associated challenge records. So the plugin will display an interactive prompt informing the user of what records to add and pause waiting for the user to press a key.

After that, things proceed as normal. Renewals and new orders with the same names do not require user interaction because the CNAMEs have already been created and the credentials are saved to the account profile just like other plugin parameters.

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

Successfully merging this pull request may close these issues.

1 participant