upbound / up

The @upbound CLI
Apache License 2.0
49 stars 42 forks source link

`up version` doesn't fail gracefully #504

Closed RedbackThomson closed 1 month ago

RedbackThomson commented 1 month ago

What happened?

up version attempts to make a call to the current cluster to determine the crossplane and spaces versions. If the cluster is not reachable, it outputs a partial response and then fails with an error message. Ideally we would fail more gracefully. Perhaps:

Client Version: v0.29.0
Server Version: <unknown>
Spaces Controller Version: <unknown>

Maybe we still show the error message? Maybe we log errors to a stderr file?

How can we reproduce it?

Create a faulty kubeconfig and run up version

What environment did it happen in?