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

[BUG] CLI disregards --config and fails #490

Open
alexgmathews opened this issue Nov 18, 2024 · 0 comments
Open

[BUG] CLI disregards --config and fails #490

alexgmathews opened this issue Nov 18, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@alexgmathews
Copy link

Steps To Reproduce

  1. Operating System: Debian 12 x86_64
  2. Vultr-CLI Binary: vultr-cli_v3.4.0_linux_amd64 installed to /usr/local/sbin/vultr-cli with owner/group root:root and permissions 700
  3. Configuration file placed at /etc/vultr-cli.yaml with contents api-key: 123XYZ... with owner/group root:root and permissions 600
  4. Shell Environment: bash, root user (command executed directly as root / not prefixed by sudo)
  5. Command: $ vultr-cli account --config /etc/vultr-cli.yaml

Error Message

Error Reading in file: /root/.vultr-cli.yaml
Error:
Please export your VULTR API key as an environment variable or add 'api-key' to your config file, eg:
export VULTR_API_KEY='<api_key_from_vultr_account>'

Expected behavior
If the --config flag is defined...

  1. vultr-cli should use the defined path for configuration
  2. vultr-cli should not attempt reading $HOME/.vultr-cli.yaml
  3. the error message should give an example demonstrating add 'api-key' to your config file
@alexgmathews alexgmathews added the bug Something isn't working label Nov 18, 2024
@optik-aper optik-aper self-assigned this Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants