The ergonomics of "fastly auth" are worse than the deprecated "fastly profile token"

[joeshaw]

Version

Fastly CLI version v14.1.1 (548fb34)
Built with go version go1.25.8 darwin/arm64 (2026-03-23)
Viceroy version: viceroy 0.16.2

What happened

Prior to fastly profile token being deprecated (see also #1708), I used it often in shell substitution when I needed an auth token. For example, calling the API directly using curl:

curl -H "Fastly-Key: $(fastly profile token --quiet)" https://api.fastly.com/...

There's no equivalent fastly auth mode to display just the token for the given profile. You have to involve shell pipelines and external tools:

curl -H "Fastly-Key: $(fastly auth show --quiet --reveal | awk '/^Token:/ {print $2}' https://api.fastly.com/...

Please add a flag to display only the token!

[kpfleming]

This is in the works already in #1690.

In addition, I've been (slowly) working on a fastly run command which would be used like this:

fastly run curl -H "Fastly-Key: ${FASTLY_API_KEY}" https://api.fastly.com...

The command would obtain the current token (default or specified using --token), inject it into the environment in a child process, and then run the specified command in that process. The primary use case is for fastly run terraform plan/apply, but it could also be used for curl or any other command which can read the token from an environment variable.

Would this be useful for you?

[joeshaw]

Yeah, that could be nice. Shell escaping might be a pain though, ${FASTLY_API_KEY} would be resolved by the shell rather than by the fastly CLI, so you might need a different syntax for that.

[kpfleming]

Yes, I realized that a few minutes after posting... the original purpose of this was for Terraform, which reads the environment variable directly. A small curl wrapper script could do that too.