0.3.210 regression with `--access-token`

[Jiralite]

Describe the bug
I've been a workflow to back up a database. However, it started failing, specifically here:

flyctl proxy 5432 --app $FLY_DB_APP --access-token $FLY_DATABASE_TOKEN

Error: https://github.com/Soulobby/Soulobby/actions/runs/19251087698/job/55038989095

It doesn't seem to find my access token?

It worked fine on versions prior to 0.3.210 as you can see from previous runs:

https://github.com/Soulobby/Soulobby/actions/runs/19217220203/job/54928569413#step:3:12

(Or look at the history yourself.)

Worth noting that I've been using this for like a year. The repository is new only because I migrated it.

I modified my workflow to use 0.3.209:

Soulobby/Soulobby@d1eb109

The workflow works again:

https://github.com/Soulobby/Soulobby/actions/runs/19252335221

Something is definitely wrong.

• Fly 0.3.210 (see the logs in the runner).

[Jiralite]

A naive look at recent commits makes me believe #4645 is the culprit, specifically here:

flyctl/internal/command/command.go

Line 571 in 5a396de

tokenFromEnv := env.First(config.AccessTokenEnvKey, config.APITokenEnvKey) != ""

It looks like it's only looking for this environment variable and disregarding --access-token. Is this intended behaviour?

[ethos-seth]

Thanks for posting this. 🙏 Pinning to 0.3.209 was an effective workaround for us too.

[jns-itminds]

A workaround for this seems to be setting the access token through an environment variable

FLY_ACCESS_TOKEN=$FLY_DATABASE_TOKEN flyctl proxy 5432 --app $FLY_DB_APP

[Jiralite]

I said that above already.

It's also an already-defined way of providing authentication–not a workaround. Have a read:
https://fly.io/docs/flyctl/integrating/#environment-variables