docs: correct admin-credentials help text
CI / Test (rest) (pull_request) Successful in 1m42s
CI / Test (store) (pull_request) Successful in 1m45s
CI / Lint (pull_request) Successful in 28s
CI / Build (windows/amd64) (pull_request) Successful in 29s
CI / Test (server-http) (pull_request) Successful in 2m27s
CI / Build (linux/amd64) (pull_request) Successful in 30s
CI / Build (linux/arm64) (pull_request) Successful in 26s
e2e / Playwright vs docker-compose (pull_request) Successful in 1m30s
CI / Test (rest) (pull_request) Successful in 1m42s
CI / Test (store) (pull_request) Successful in 1m45s
CI / Lint (pull_request) Successful in 28s
CI / Build (windows/amd64) (pull_request) Successful in 29s
CI / Test (server-http) (pull_request) Successful in 2m27s
CI / Build (linux/amd64) (pull_request) Successful in 30s
CI / Build (linux/arm64) (pull_request) Successful in 26s
e2e / Playwright vs docker-compose (pull_request) Successful in 1m30s
Forget does not use admin credentials. Only JobPrune builds a runner against the admin slot (cmd/agent/main.go:622-645); JobForget runs on the everyday runner, as the comment at main.go:517-524 states. Also corrects the claim that leaving this blank lets everyday creds handle prune: maintenance_dispatch.go:52-56 skips prune entirely with 'prune skipped — no admin creds' on any backend, with no fallback. Refs #34
This commit is contained in:
@@ -83,9 +83,11 @@
|
|||||||
{{end}}
|
{{end}}
|
||||||
<p class="text-[12.5px] text-ink-mid leading-[1.6] mb-4 max-w-[640px]">
|
<p class="text-[12.5px] text-ink-mid leading-[1.6] mb-4 max-w-[640px]">
|
||||||
Only needed for rest-server repos that distinguish an append-only
|
Only needed for rest-server repos that distinguish an append-only
|
||||||
user (everyday backups) from a delete-capable user (prune /
|
user (everyday backups) from a delete-capable user (prune). Note
|
||||||
forget). For S3 / B2 / SFTP / local, leave this blank — the
|
that <strong>forget</strong> always runs with the everyday repo
|
||||||
everyday repo credentials handle prune too.
|
credentials, so those must have delete authority. For S3 / B2 /
|
||||||
|
SFTP / local, leave this blank — but note that <strong>prune is
|
||||||
|
skipped entirely when this is unset</strong>, on any backend.
|
||||||
</p>
|
</p>
|
||||||
<div class="grid grid-cols-2 gap-4">
|
<div class="grid grid-cols-2 gap-4">
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
Reference in New Issue
Block a user