Capitalise 'DNS' in ACME DNS01 provider names
Signed-off-by: James Munnelly <james@munnelly.eu>
This commit is contained in:
parent
214b5e932b
commit
b57088a38c
@ -3055,7 +3055,7 @@ spec:
|
||||
by performing the DNS01 challenge flow.
|
||||
type: object
|
||||
properties:
|
||||
acmedns:
|
||||
acmeDNS:
|
||||
description: Use the 'ACME DNS' (https://github.com/joohoi/acme-dns)
|
||||
API to manage DNS01 challenge records.
|
||||
type: object
|
||||
@ -3145,7 +3145,7 @@ spec:
|
||||
type: string
|
||||
serviceConsumerDomain:
|
||||
type: string
|
||||
azuredns:
|
||||
azureDNS:
|
||||
description: Use the Microsoft Azure DNS API to manage DNS01
|
||||
challenge records.
|
||||
type: object
|
||||
@ -3190,7 +3190,7 @@ spec:
|
||||
description: when specifying ClientID and ClientSecret
|
||||
then this field is also needed
|
||||
type: string
|
||||
clouddns:
|
||||
cloudDNS:
|
||||
description: Use the Google Cloud DNS API to manage DNS01
|
||||
challenge records.
|
||||
type: object
|
||||
|
||||
@ -4021,7 +4021,7 @@ spec:
|
||||
authorizations by performing the DNS01 challenge flow.
|
||||
type: object
|
||||
properties:
|
||||
acmedns:
|
||||
acmeDNS:
|
||||
description: Use the 'ACME DNS' (https://github.com/joohoi/acme-dns)
|
||||
API to manage DNS01 challenge records.
|
||||
type: object
|
||||
@ -4115,7 +4115,7 @@ spec:
|
||||
type: string
|
||||
serviceConsumerDomain:
|
||||
type: string
|
||||
azuredns:
|
||||
azureDNS:
|
||||
description: Use the Microsoft Azure DNS API to manage
|
||||
DNS01 challenge records.
|
||||
type: object
|
||||
@ -4161,7 +4161,7 @@ spec:
|
||||
description: when specifying ClientID and ClientSecret
|
||||
then this field is also needed
|
||||
type: string
|
||||
clouddns:
|
||||
cloudDNS:
|
||||
description: Use the Google Cloud DNS API to manage
|
||||
DNS01 challenge records.
|
||||
type: object
|
||||
|
||||
@ -4018,7 +4018,7 @@ spec:
|
||||
authorizations by performing the DNS01 challenge flow.
|
||||
type: object
|
||||
properties:
|
||||
acmedns:
|
||||
acmeDNS:
|
||||
description: Use the 'ACME DNS' (https://github.com/joohoi/acme-dns)
|
||||
API to manage DNS01 challenge records.
|
||||
type: object
|
||||
@ -4112,7 +4112,7 @@ spec:
|
||||
type: string
|
||||
serviceConsumerDomain:
|
||||
type: string
|
||||
azuredns:
|
||||
azureDNS:
|
||||
description: Use the Microsoft Azure DNS API to manage
|
||||
DNS01 challenge records.
|
||||
type: object
|
||||
@ -4158,7 +4158,7 @@ spec:
|
||||
description: when specifying ClientID and ClientSecret
|
||||
then this field is also needed
|
||||
type: string
|
||||
clouddns:
|
||||
cloudDNS:
|
||||
description: Use the Google Cloud DNS API to manage
|
||||
DNS01 challenge records.
|
||||
type: object
|
||||
|
||||
@ -281,7 +281,7 @@ type ACMEChallengeSolverDNS01 struct {
|
||||
|
||||
// Use the Google Cloud DNS API to manage DNS01 challenge records.
|
||||
// +optional
|
||||
CloudDNS *ACMEIssuerDNS01ProviderCloudDNS `json:"clouddns,omitempty"`
|
||||
CloudDNS *ACMEIssuerDNS01ProviderCloudDNS `json:"cloudDNS,omitempty"`
|
||||
|
||||
// Use the Cloudflare API to manage DNS01 challenge records.
|
||||
// +optional
|
||||
@ -293,7 +293,7 @@ type ACMEChallengeSolverDNS01 struct {
|
||||
|
||||
// Use the Microsoft Azure DNS API to manage DNS01 challenge records.
|
||||
// +optional
|
||||
AzureDNS *ACMEIssuerDNS01ProviderAzureDNS `json:"azuredns,omitempty"`
|
||||
AzureDNS *ACMEIssuerDNS01ProviderAzureDNS `json:"azureDNS,omitempty"`
|
||||
|
||||
// Use the DigitalOcean DNS API to manage DNS01 challenge records.
|
||||
// +optional
|
||||
@ -302,7 +302,7 @@ type ACMEChallengeSolverDNS01 struct {
|
||||
// Use the 'ACME DNS' (https://github.com/joohoi/acme-dns) API to manage
|
||||
// DNS01 challenge records.
|
||||
// +optional
|
||||
AcmeDNS *ACMEIssuerDNS01ProviderAcmeDNS `json:"acmedns,omitempty"`
|
||||
AcmeDNS *ACMEIssuerDNS01ProviderAcmeDNS `json:"acmeDNS,omitempty"`
|
||||
|
||||
// Use RFC2136 ("Dynamic Updates in the Domain Name System") (https://datatracker.ietf.org/doc/rfc2136/)
|
||||
// to manage DNS01 challenge records.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user