weiguoqiang/cert-manager
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity
8b7552cec1
cert-manager/deploy/crds
History
Richard Wall 8beeac1187 Rename Certificate.Spec.URISANs to URIs and EmailSANs to EmailAddresses 
For consistency with DNSNames and IPAddresses
And for consistency with https://golang.org/pkg/crypto/x509/#Certificate

Signed-off-by: Richard Wall <richard.wall@jetstack.io>
2020-08-14 17:02:53 +01:00
..
BUILD.bazel Fix up chart and bazel build rules 2020-04-01 18:22:35 +01:00
crd-certificaterequests.yaml Update CRDs 2020-08-13 21:43:36 +01:00
crd-certificates.yaml Rename Certificate.Spec.URISANs to URIs and EmailSANs to EmailAddresses 2020-08-14 17:02:53 +01:00
crd-challenges.yaml Update CRDs 2020-08-13 21:43:36 +01:00
crd-clusterissuers.yaml Update CRDs 2020-08-13 21:43:36 +01:00
crd-issuers.yaml Update CRDs 2020-08-13 21:43:36 +01:00
crd-orders.yaml Update CRDs 2020-08-13 21:43:36 +01:00
README.md Address review feedback 2020-04-07 10:15:05 +01:00

README.md

CRDs source directory

Warning

: if you are an end-user, you do NOT need to use the files in this directory. These files are for development purposes only.

This directory contains 'source code' used to build our CustomResourceDefinition resources in a way that can be consumed by all our different deployment methods.

This package exposes a number of different Bazel targets:

  • templates.regular: the Helm templates for the 'regular' CRD manifests
  • templates.legacy: the Helm templates for the 'legacy' CRD manifests
  • crds.regular: the templated 'regular' CRD manifests (after running helm template)
  • crds.legacy: the templated 'legacy' CRD manifests (after running helm template)
  • crd-<crd-name>.templated: for each CRD type, the one CRD after running helm template
  • templated_files: a filegroup containing all of the individual templated CRD files

Most users should never utilise the files in this directory directly. Instead, Bazel build targets in other packages (i.e. //deploy/manifests, //deploy/charts etc) will be configured to automatically consume the appropriate artifact listed above.