flyctl - outdated documentation - `fly ssh estabilish` command doesn't exist

[kristoffn]

I was reading the documentation when I noticed that it may be outdated because the fly ssh estabilish command doesn’t exist anymore.

$ fly ssh estabilish
Use SSH to login to or run commands on VMs

Usage:
  flyctl ssh [command]

Available Commands:
  console     Connect to a running instance of the current app.
  issue       Issue a new SSH credential
  log         Log of all issued SSH certs
  sftp        Get or put files from a remote VM.

Flags:
  -h, --help   help for ssh

Global Flags:
  -t, --access-token string   Fly API Access Token
  -j, --json                  json output
      --verbose               verbose output

Use "flyctl ssh [command] --help" for more information about a command.

$ fly version
fly v0.0.442 darwin/arm64 Commit: e5a70d79 BuildDate: 2022-12-30T17:10:16Z

[Cuji]

@thomas

ssh establish and ssh issue actually don’t interact with WireGuard at all — they’re API-only commands. establish is a one-time command that sets up an SSH certificate for your organization — we should get rid of it and just manage that for you, but when SSH was introduced we thought it might be opt-in. issue just creates time-limited SSH user certificates to log in with.

Using establish and issue, you can use standard OpenSSH to log in directly to instances when you have a WireGuard tunnel established with your OS.

ssh console does something much more ambitious: it sets up a WireGuard tunnel on its own, using an agent process in flyctl. That tunnel is entirely in userland — your OS doesn’t know anything about it. Under the hood, it’s relying on the same certificates that establish and issue set up.

Unsure if this actually got removed since, I suspect not as that message is only a few weeks ago; I suppose someone at Fly may be able to shed some light on it.