feat: whoami: updated whoami to show the path to the config if that is what is being used

[kevkevinpal]

Summary

I wanted a way to know where my config/api keys were stored other than on login/logout. So I added a new output to whoami to show the config path if we are using a config.

Example

$ pnpm dev whoami --json

> resend-cli@1.4.1 dev /mnt/shared_drive/DEVDIR/resend-cli
> tsx src/cli.ts whoami --json

{
  "authenticated": true,
  "profile": "default",
  "api_key": "re_...JMBH",
  "source": "config",
  "config_path": "/home/kevkevin/.config/resend/credentials.json"
}

With no --json

$ pnpm dev whoami

> resend-cli@1.4.1 dev /mnt/shared_drive/DEVDIR/resend-cli
> tsx src/cli.ts whoami


  Profile: default
  API Key: re_...JMBH
  Source:  config file
  Config:  /home/kevkevin/.config/resend/credentials.json

---

Summary by cubic

Updated whoami to show the full path to the credentials file when the API key comes from config. This makes it easy to find where keys are stored.

• New Features
  • Adds config_path in JSON output and a "Config:" line in standard output when the source is config, showing the full path to credentials.json from getConfigDir.

^{Written for commit f8cacb2. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 2 files

[felipefreitag]

Thanks for this contribution!

Since this was opened, we've landed secure credential storage (#97), which stores API keys in the OS keychain (macOS Keychain, Linux secret-service, Windows Credential Manager) rather than in credentials.json. With that change, pointing users to the credentials file wouldn't be accurate for keychain users.
With that in mind, do you feel the need for the path to the file?

[kevkevinpal]

Since this was opened, we've landed secure credential storage (#97), which stores API keys in the OS keychain (macOS Keychain, Linux secret-service, Windows Credential Manager) rather than in credentials.json.

Awesome, that looks like a significant improvement.

With that change, pointing users to the credentials file wouldn't be accurate for keychain users. With that in mind, do you feel the need for the path to the file?

Is there a chance that it can be still saved to a credentials.json file? I think just in that case we should show it. If there is no chance of that happening then we can close this PR.

[felipefreitag]

Since this was opened, we've landed secure credential storage (#97), which stores API keys in the OS keychain (macOS Keychain, Linux secret-service, Windows Credential Manager) rather than in credentials.json.

Awesome, that looks like a significant improvement.

With that change, pointing users to the credentials file wouldn't be accurate for keychain users. With that in mind, do you feel the need for the path to the file?

Is there a chance that it can be still saved to a credentials.json file? I think just in that case we should show it. If there is no chance of that happening then we can close this PR.

We still use the config file for storing profiles, and it's possible for users to choose insecure storage manually

[kevkevinpal]

We still use the config file for storing profiles, and it's possible for users to choose insecure storage manually

I think it then makes sense to still display this in those cases where the config is used