search

upbound / up

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

No warning when `up` isn't in the PATH #490

Closed RedbackThomson closed 2 months ago

RedbackThomson commented 2 months ago

What happened?

When navigating using up ctx into a cloud space, and up is not present in the user's PATH, the user will see the following error:

up: error: unexpected argument tokenrces: unable to retrieve the complete list of server APIs: v1: Get "https://upbound-gcp-us-west-1.space.mxe.upbound.io/api/v1": getting credentials: exec: executable up failed with exit code 1
up: error: unexpected argument token

Ideally we would warn the user that up is not in their PATH since it practically makes up unusable.

How can we reproduce it?

Remove up from PATH, run it separately, see error.

What environment did it happen in?