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.

Sign up for GitHub

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

Jump to bottom

[BUG] - Config file isn't being used to authenticate #429

Closed
optik-aper opened this issue Mar 15, 2024 · 0 comments · Fixed by #430
Closed

[BUG] - Config file isn't being used to authenticate #429

optik-aper opened this issue Mar 15, 2024 · 0 comments · Fixed by #430
Assignees
@optik-aper
Labels
bug Something isn't working regression Something that worked doesn't work after changes

Comments

@optik-aper
Copy link
Member

Describe the bug
The default config file isn't being read in and used to authenticate.

To Reproduce
Steps to reproduce the behavior:

  1. Create the default config file ~/.vultr-cli.yaml and add the API key
  2. Try to use a command and you'll get oauth2: token expired and refresh token is not set
  3. But if you export it as an environment variable, it works.
  • Version 3.0.2
@optik-aper optik-aper added bug Something isn't working regression Something that worked doesn't work after changes labels Mar 15, 2024
@optik-aper optik-aper self-assigned this Mar 15, 2024
@optik-aper optik-aper mentioned this issue Mar 15, 2024
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@optik-aper optik-aper

Labels
bug Something isn't working regression Something that worked doesn't work after changes
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix oauth token when a config file is used optik-aper/vultr-cli
1 participant
@optik-aper