Issue with the "Integrating flyctl" doc

[colinmollenhour]

I found an issue with this document.

Title: Integrating flyctl
Location: https://fly.io/docs/flyctl/integrating/
Source: https://github.com/superfly/docs/blob/main/flyctl/integrating.html.md

Describe the issue

It seems the -t or --access-token flag no longer works.. I'm trying to use flyctl deploy ....

On CI it says:

$ flyctl deploy --config fly.staging.toml --remote-only -t "$FLY_API_TOKEN_STAGING"
Error: No access token available. Please login with 'flyctl auth login'

And on local terminal it says:

Welcome back!
Your session has expired, please log in to continue using flyctl.

But if I use the same token passing it to the FLY_ACCESS_TOKEN environment variable it works as expected.

This broke my CI pipeline so I'll change it to use the environment variable, but this CLI flag should either be fixed or removed from the docs.

[kcmartin]

I tested the -t flag with flyctl v0.3.231 and it works correctly for flyctl deploy.

Testing steps:

flyctl tokens create deploy -a my-fly-app
flyctl deploy -t "$TOKEN"

The deploy completed successfully with no authentication errors.

@colinmollenhour - What version of flyctl are you running? This might have been fixed in a recent version. You can check with flyctl version and update with flyctl version update (or reinstall via your package manager).

[colinmollenhour]

@kcmartin I'm using this workflow in GitLab CI:

# Install Fly.io CLI
.install-flyctl: &install-flyctl
  - curl -sSL https://fly.io/install.sh | sh
  - export FLYCTL_INSTALL="/root/.fly"
  - export PATH="$FLYCTL_INSTALL/bin:$PATH"

I'll add flyctl --version so I have that in the logs in the future, but based on that it should have been the latest at the time I opened the issue.

EDIT:
On my local machine I had 0.3.229 before updating

[kcmartin]

Thanks -- let us know if you're still seeing the issue after updating.