[BUG] - CLI requires non-empty VULTR_API_KEY for "help [..]" and "version" subcommands about vultr-cli HOT 4 CLOSED

@nifr Thanks for the report. This is something that has been on the todo list for a long time. I'll see about adding a patch for these commands at least.

from vultr-cli.

@optik-aper just came back here and I was amazed by your crazy response time.

Thank you so much for the quick response and for looking into this.

I discovered another important sub-command (completion) that fails if VULTR_API_KEY is unset.

source <(vultr-cli completion bash)

Errors out (obviously) as follows:

bash: api-key: command not found
bash: Please: command not found

Note: This also reveals that the error/warning message goes to stdout instead of stderr. Intended?

Current workaround for bash, zsh, [..] for anyone who ends up here until this issue resolved:

if command -v vultr-cli >/dev/null 2>&1; then
  source <(VULTR_API_KEY='workaround' vultr-cli completion "${SHELL##*/}")
fi

from vultr-cli.

I appreciate the additional info! I have a working fix on this, but I need to re-organize some of the code to make sure auth-required commands warn the user. Hopefully I'll have some time this week to wrap that part up.

from vultr-cli.

Note: This also reveals that the error/warning message goes to stdout instead of stderr. Intended?

I missed this in my first read, sorry. That is how it's currently intended/designed but could be changed. I'll have to think about whether that makes sense to change and try experiments.

from vultr-cli.