History

James Munnelly 7978fbe081 Address review feedback and include truststore.jks with JKS mode enabled Signed-off-by: James Munnelly <james@munnelly.eu>		2020-04-22 15:20:49 +01:00
..
BUILD.bazel	Fix up chart and bazel build rules	2020-04-01 18:22:35 +01:00
crd-certificaterequests.yaml	Fix up chart and bazel build rules	2020-04-01 18:22:35 +01:00
crd-certificates.yaml	Address review feedback and include truststore.jks with JKS mode enabled	2020-04-22 15:20:49 +01:00
crd-challenges.yaml	Regenerate files	2020-04-21 10:07:13 +01:00
crd-clusterissuers.yaml	addressed all reviewes and added all validation tests	2020-04-10 08:48:56 +02:00
crd-issuers.yaml	addressed all reviewes and added all validation tests	2020-04-10 08:48:56 +02:00
crd-orders.yaml	Address review feedback	2020-04-07 10:15:05 +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.