civo update fails with NoAPIKeySuppliedError if I don't have an API key

Question

civo update fails with NoAPIKeySuppliedError if I don't have an API key

Closed this issue a year ago · 4 comments

$ civo update
Creating the connection to Civo's API failed with NoAPIKeySuppliedError: no API Key supplied, this is requiredNoAPIKeySuppliedError: no API Key supplied, this is required

deleting $HOME/.civo.json fixed the issue for me

Answer 1 · 2023-08-17T12:24:52.000Z

mm, that is odd, the update doesn't use the ApiKey to update the binary, @haardikdharma10 can you check this

Answer 2 · 2023-08-29T20:03:57.000Z

I had the same issue when I deleted the tempKey as I was testing something with the API keys. The CLI should at least let you save a new API key, when there's none, and also check the help menu so you know how to do it. I'm on v1.0.61.

Answer 3 · 2023-08-30T08:06:42.000Z

I will check this

Answer 4 · 2023-08-30T09:40:29.000Z

@rberrelleza @fharper I just checked this and the cmd update doesn't use the API to update the binary. I will close this issue for now, If need to reopen please feel free to do it.