The ergonomics of "fastly auth" are worse than the deprecated "fastly profile token"
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go
- Domain
- authentication, cli
Research direction
Start at the fastly auth show command and compare its --quiet and --reveal output with the deprecated fastly profile token --quiet behavior. Add the requested token-only mode for the selected profile, then verify that its output can be used directly in shell substitution for the curl example.
Written by the indexing model from the issue text.
Description
Version
Fastly CLI version v14.1.1 (548fb34e)
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!
- Dominant language
- Go
- Stars
- 164
- Forks
- 80
- Avg merge
- 14h 22m
- Merged PRs (30d)
- 17
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fastly/cli
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·