[client] Say in --upload-bundle-url's help that the default can be NetBird's service

The text described the empty flag as "the one the management server publishes"
and stopped there, so a reader had no way to know what happens when it publishes
none. Name the fallback, and scope the root requirement to a host other than
NetBird's rather than to setting the flag at all.

Reported by cubic on #7514.
This commit is contained in:
riccardom
2026-09-14 09:18:44 +02:00
parent 298ad3e69d
commit 2befe96c31
+5 -4
View File
@@ -27,11 +27,12 @@ const errCloseConnection = "Failed to close connection: %v"
// uploadBundleURLUsage documents that an empty flag is not "no upload" but
// "wherever this deployment says": the daemon takes the destination from the
// management server, and only falls back to the service NetBird runs for a peer
// enrolled with NetBird's cloud. Naming another one requires root, since the
// daemon fetches the URL and PUTs its own logs and state to whatever it returns.
// management server, falling back to the service NetBird runs when none is
// published. Naming another host requires root, since the daemon fetches the URL
// and PUTs its own logs and state to whatever it returns.
const uploadBundleURLUsage = "Upload service URL to get an upload URL from. " +
"Defaults to the one the management server publishes; requires root when set explicitly"
"Defaults to the one the management server publishes, or to NetBird's service when it publishes none; " +
"naming any host other than NetBird's requires root"
var (
logFileCount uint32