Spell out the upload-destination precedence instead of chaining ">"

"MDM > --upload-bundle-url > account setting > management.json > NetBird"
reads both ways: it can mean "MDM is consulted first" or "MDM is overridden by
the next one". Replace it with a numbered list and say explicitly that the
client uses the first entry that is set.
This commit is contained in:
riccardom
2026-09-11 18:32:49 +02:00
parent ae138dde4b
commit c7720d7e7e
+8 -4
View File
@@ -41,11 +41,15 @@ A self-hosted deployment can set the destination for every account at once with
}
```
The account setting overrides that value when set. An MDM-managed client overrides both, through the `debugBundleUploadURL` policy key — see [MDM integration](/client/mdm-integration). So the order is:
Several places can name a destination. The client walks this list and uses **the first one that is set**, ignoring the rest:
```text
MDM policy > --upload-bundle-url (or a remote job's Upload URL) > account setting > management.json > NetBird's service
```
1. The `debugBundleUploadURL` MDM policy on the device — see [MDM integration](/client/mdm-integration).
2. A destination named for this one bundle: `--upload-bundle-url` on the CLI, or the `Upload URL` field of a remote job.
3. This account setting.
4. `DebugUpload.URL` in the management server's `management.json`.
5. The upload service NetBird runs.
So the device's own policy beats everything, a destination typed for a single bundle beats the account's, and the account setting beats the deployment-wide default. Whoever is further down only gets a say when nobody above them said anything.
`netbird debug bundle` without `-U` never uploads at all: it writes the bundle locally and prints the path.