Regenerate CRDs to fix broken name pattern

redhat-cop / vault-config-operator

An operator to support Haschicorp Vault configuration workflows from within Kubernetes

Apache License 2.0

112 stars 49 forks source link

Regenerate CRDs to fix broken name pattern #210

Closed tbalzer closed 12 months ago

tbalzer commented 12 months ago

During #202 (specifically cc426f8b94869fc4ce4e8e1dff6d7382752b3b70) the quoting of the validation patterns for the new name field was fixed, but it was missed to regenerate the CRDs, which I have done with this PR. Currently the validation does not work correctly when applying as-is from e.g. helm because of this.

tbalzer commented 12 months ago

@raffaelespazzoli @Vikaspogu @sabre1041 Would be nice to get this fixed soon, as it's pretty trivial but breaks our deployments when trying to use CRDs from the helm release.