Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Civo apikey issue #355

Closed
saiyam1814 opened this issue Jan 3, 2024 · 0 comments
Closed

Civo apikey issue #355

saiyam1814 opened this issue Jan 3, 2024 · 0 comments

Comments

@saiyam1814
Copy link
Contributor

Lets say you have a few apikeys on your system with below names

+---------+---------+
| Name    | Default |
+---------+---------+
| demo    |         |
+---------+---------+
| owner   |         |
+---------+---------+
| rancher |         |
+---------+---------+
| saiyam  |         |
+---------+---------+
| saiyam2 |         |
+---------+---------+
| sam3    | <=====  |
+---------+---------+

this shows that my current apikey is sam3

now I try to switch to saiyam

civo apikey use saiyam
Set the default API Key to be saiyam2

but instead of switching to saiyam it is switching to saiyam2 which is a different name.

Now if you try to delete saiyam2 it will creak and according to the system cli is using saiyam2 and it wont update the json and will remove saiyam2 and your civo cli will break

demo ~ civo apikey remove saiyam2
Warning: Are you sure you want to delete the saiyam2 api key (y/N) ? y
Removed the API Key saiyam2
demo ~ civo
Creating the connection to Civo's API failed with NoAPIKeySuppliedError: no API Key supplied, this is requiredNoAPIKeySuppliedError: no API Key supplied, this is required

alejandrojnm added a commit that referenced this issue Jan 4, 2024
…ey close Civo apikey issue #355

Signed-off-by: Alejandro J. Nuñez Madrazo <alejandrojnm@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants