From 3d9937513bc76cd9558de35851f8acc036c9ff73 Mon Sep 17 00:00:00 2001 From: Brad Fitzpatrick Date: Thu, 2 Dec 2021 14:01:57 -0800 Subject: [PATCH] cmd/tailscale: clarify which prefless flags don't need revert protection Fixes #3482 Change-Id: Icb51476b0d78d3758cb04df3b565e372b8289a46 Signed-off-by: Brad Fitzpatrick (cherry picked from commit a8f60cf6e8786ead724b790427b0731010786f26) --- cmd/tailscale/cli/up.go | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/cmd/tailscale/cli/up.go b/cmd/tailscale/cli/up.go index 5d2916f27..e7586690e 100644 --- a/cmd/tailscale/cli/up.go +++ b/cmd/tailscale/cli/up.go @@ -46,8 +46,10 @@ If flags are specified, the flags must be the complete set of desired settings. An error is returned if any setting would be changed as a -result of an unspecified flag's default value, unless the --reset -flag is also used. +result of an unspecified flag's default value, unless the --reset flag +is also used. (The flags --authkey, --force-reauth, and --qr are not +considered settings that need to be re-specified when modifying +settings.) `), FlagSet: upFlagSet, Exec: runUp,