Promote `validate` subcommand to GA about crossplane HOT 4 OPEN

We could think of splitting the caching mechanism to its separate command so that one could use its output to feed CRDs to kubectl validate directly instead. IIRC having two separate commands was actually one of the initial proposals 😅

My two cents: crossplane validate feels like a better UX to me than crossplane fetch && kubectl validate.

from crossplane.

We should also add support for missing types of schema errors, see discussion here. To be understood how much will be left after the PR from @ezgidemirel to add x-kubernetes-validations.

from crossplane.

I learned today that kubectl validate is a thing. Apparently it does a lot of what our validate command does, and is designed to be used a library that other tools can depend on. We might consider using it.

from crossplane.

Thanks @negz for pointing that out, definitely interesting, I gave it a quick shot and although it looks like we could plug it pretty easily, just keeping our schema caching logic and leaving everything else to their implementation, potentially with a few added benefits such as the ability to use CRDs from a running Cluster. There is still a risk due to the overlapping dependencies, e.g. right now we would have to downgrade a few things to be able to import sigs.k8s.io/kubectl-validate and I couldn't easily make it build. It could be worth rethinking about this once/if we move the crossplane cli to its own repo as per #4850.

We could think of splitting the caching mechanism to its separate command so that one could use its output to feed CRDs to kubectl validate directly instead. IIRC having two separate commands was actually one of the initial proposals 😅

from crossplane.