diff options
| author | Michael Stapelberg <michael@stapelberg.de> | 2025-01-12 09:57:38 +0100 |
|---|---|---|
| committer | Brad Fitzpatrick <brad@danga.com> | 2025-01-13 11:27:35 -0800 |
| commit | 64ab0ddff14cfcae55b66017ba104afd3640e422 (patch) | |
| tree | 19d3983a0668a674bea75f5a84deefa51e280eef /control/controlhttp/controlhttpserver/controlhttpserver.go | |
| parent | 6ccde369ffa0aa381fdaf6a735f3e3bbaba179b9 (diff) | |
| download | tailscale-64ab0ddff14cfcae55b66017ba104afd3640e422.tar.xz tailscale-64ab0ddff14cfcae55b66017ba104afd3640e422.zip | |
cmd/tailscale/cli: only exit silently if len(args) == 0
This amends commit b7e48058c8d243adf1ff687e3e92d3fb02b035ea.
That commit broke all documented ways of starting Tailscale on gokrazy:
https://gokrazy.org/packages/tailscale/ — both Option A (tailscale up)
and Option B (tailscale up --auth-key) rely on the tailscale CLI working.
I verified that the tailscale CLI just prints it help when started
without arguments, i.e. it does not stay running and is not restarted.
I verified that the tailscale CLI successfully exits when started with
tailscale up --auth-key, regardless of whether the node has joined
the tailnet yet or not.
I verified that the tailscale CLI successfully waits and exits when
started with tailscale up, as expected.
fixes https://github.com/gokrazy/gokrazy/issues/286
Signed-off-by: Michael Stapelberg <michael@stapelberg.de>
Diffstat (limited to 'control/controlhttp/controlhttpserver/controlhttpserver.go')
0 files changed, 0 insertions, 0 deletions