steve e0037f0026 restic: treat 'config file already exists' on init as soft success ...

Re-running restic init on a repo that's already initialised exits
non-zero with "Fatal: ... config file already exists". Semantically
that's a no-op, not a failure — the repo IS initialised, the
caller's intent is satisfied. Sniff stderr for the magic string
and swallow the exit code in that case, emitting an event line
so the operator-facing log says what happened.

Caught while smoke-testing P2-04.5: I'd init'd the repo manually
during a debug session, then the operator clicking the UI's
Init-repo button would hit this and the host's repo_initialised_at
would never flip.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-02 13:22:01 +01:00

..

runner.go

restic: treat 'config file already exists' on init as soft success

2026-05-02 13:22:01 +01:00

snapshots.go

P1-22: snapshot listing via restic snapshots --json

2026-05-01 11:20:57 +01:00

url_test.go

P1 polish: agent-as-root, init-repo flow, rest creds passthrough, UX fixes

2026-05-02 11:02:12 +01:00

url.go

P1 polish: agent-as-root, init-repo flow, rest creds passthrough, UX fixes

2026-05-02 11:02:12 +01:00