The message for td apikey:set -f can be misleading if env vars TREASURE_DATA_API_KEY or TD_API_KEY are set

[kiyoto]

Env variables override "td apikey:set -f", i.e., whatever new apikey you set would not replace the one set by the env variable.

This behavior is intended, but the associated message is kind of misleading:

$ td apikey:set <new_apikey>

API key is set.
Use 'td db:create <db_name>' to create a database.

When, in reality, API key is not set to <new_apikey>.

[takkanm]

@kiyoto
Currently, td apikey:set -f will display an error message.

$ TD_API_KEY=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX td apikey:set -f
usage:
 $ td apikey:set <apikey>

description:
 Set Treasure Data API key

options:
 -f, --force                      overwrite current account setting

Is this, would be the behavior you want?

[kiyoto]

@takkanm At least it should have a warning. But wow, someone is working on an issue from 2.5 years ago!

[takkanm]

Settings from the environment variable can not be, what are you expected that the effect of the message appears as a warning?