home/cert-manager
2
0
Fork 0
mirror of https://github.com/wahyd4/cert-manager.git synced 2026-08-09 05:06:38 +10:00
Code Issues Packages Projects Releases Wiki Activity

fix mistakenly changed CRDs for v1beta1 (#4352)

Browse Source 
Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
This commit is contained in:
Ashley Davis
2021-08-13 13:44:05 +01:00
parent 4f61d405a6
commit e0e5a50f31
4 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy/crds/crd-challenges.yaml
+3 -3
View File
@@ -2033,7 +2033,7 @@ spec:
description: Configures cert-manager to attempt to complete 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
required:
@@ -2101,7 +2101,7 @@ spec:
type: string
serviceConsumerDomain:
type: string
azuredns:
azureDNS:
description: Use the Microsoft Azure DNS API to manage DNS01 challenge records.
type: object
required:
@@ -2139,7 +2139,7 @@ spec:
tenantID:
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
required:
deploy/crds/crd-clusterissuers.yaml
+3 -3
View File
@@ -2492,7 +2492,7 @@ spec:
description: Configures cert-manager to attempt to complete 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
required:
@@ -2560,7 +2560,7 @@ spec:
type: string
serviceConsumerDomain:
type: string
azuredns:
azureDNS:
description: Use the Microsoft Azure DNS API to manage DNS01 challenge records.
type: object
required:
@@ -2598,7 +2598,7 @@ spec:
tenantID:
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
required:
deploy/crds/crd-issuers.yaml
+3 -3
View File
@@ -2492,7 +2492,7 @@ spec:
description: Configures cert-manager to attempt to complete 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
required:
@@ -2560,7 +2560,7 @@ spec:
type: string
serviceConsumerDomain:
type: string
azuredns:
azureDNS:
description: Use the Microsoft Azure DNS API to manage DNS01 challenge records.
type: object
required:
@@ -2598,7 +2598,7 @@ spec:
tenantID:
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
required:
pkg/apis/acme/v1beta1/types_issuer.go
+3 -3
View File
@@ -340,7 +340,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
@@ -352,7 +352,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
@@ -361,7 +361,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.