CLI Error with API Key

[Read Only] Questions and Answers
1

I am trying to limit access to some Qovery environments by using the Qovery API token when making CLI requests.

I created the API token by following the CLI command qovery token. I selected the Organization and Role and set the Token name and description.

After I have my new token, I set the API token to an ENV var like specified in the docs. export Q_CLI_ACCESS_TOKEN=

When I go to run my shell command qovery shell I get the error:

FATA[2024-03-04T14:28:12-05:00] error while creating websocket connectionwebsocket: bad handshake

2

Hello @jmilam-bluesky

Do you manage to connect by providing the full URL to the Qovery shell command? Or do you have the same issue?

For example:
qovery shell https://console.qovery.com/organization/xxxxx/project/xxxx/environment/xxxx/application/xxxx/general

3

@Pierre_Gerbelot same issue unfortunately with the entire url.

qovery shell https://console.qovery.com/organization/xxx/project/xxx/environment/xxxapplication/xxxx/general

4

Could you provide the url of the application?

5

I do not have that ability to give out the full url of the application on this forum. Can I ask why that is necessary? Is there a way to more securely divulge that information?

6

I might need this to investigate your issue. For now, I can reproduce the problem on my end without this information. I’ll contact you directly if needed

7

Indeed, the qovery shell command does not support the token authentication method. We will work on fixing that. Meanwhile, you can use the qovery auth method.
Thank you

8

Thanks for your help Pierre, and the clarity on the limitations of the token auth.

9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

10

Hi @jmilam-bluesky ,

we have released the support of the qovery token while using the qovery shell command :+1:

2 Likes