-
Notifications
You must be signed in to change notification settings - Fork 14
Open
Description
Feature Overview
- Support defining
acme_issuer
without name. There will be only 1 issuer in most configs, so there is no need to ask user for the name. The "default" issuer can be supported with following syntax:acme_certificate on | off | name;
oracme_certificate [off | name];
. We can even omit named issuers support entirely for the first release to check whether someone actually needs it. acme_certificate
should work athttp
scope, just likessl_certificate
, so that ACME can be enabled for all the servers. That also impliesoff
support, as shown above.- Split
acme_certificate
into 3 separate directives, as issuer selection, certificate identifier and key type are all orthogonal concerns. And for the first release I'd suggest to omit support for custom identifiers entirely and rely only onserver_name
to keep onlyacme_certificate on|off;
andacme_key ...;
. - Remove resolver config from
acme_issuer
for first release to check if that level of customization is actually needed.
Alternatives Considered
No response
Additional Context
No response
Metadata
Metadata
Assignees
Labels
No labels