Skip to content

Initialize new backup repositories before use - #122

Merged
martinohansen merged 3 commits into
release-1.28from
martin/repo-init
Sep 28, 2026
Merged

martinohansen merged 3 commits into
release-1.28from
martin/repo-init

Conversation

@martinohansen

Copy link
Copy Markdown

A bucket or repository path change can retain the stanza name. The
manager then mistakes initialization of the old repository for readiness
of the new one. Backups only poll for stanza metadata and can time out
before WAL archiving triggers recovery.

Initialization must follow configuration changes and remain pending
after failure, even when the next reconcile finds the file unchanged.
Replicas and suspended clusters must defer initialization until they
become eligible.

A bucket or repository path change can retain the stanza name. The
manager then mistakes initialization of the old repository for readiness
of the new one. Backups only poll for stanza metadata and can time out
before WAL archiving triggers recovery.

Initialization must follow configuration changes and remain pending
after failure, even when the next reconcile finds the file unchanged.
Replicas and suspended clusters must defer initialization until they
become eligible.
The fake pgBackRest command must be executable, and its output is read
from a test-owned temporary directory. Document these narrow gosec
exceptions so CI accepts the fixture without disabling security checks
for other code. Keep imports in the configured gci groups.
@martinohansen martinohansen added preview Preview changes and removed preview Preview changes labels Sep 24, 2026
@martinohansen
martinohansen merged commit 228b764 into release-1.28 Sep 28, 2026
37 checks passed
@martinohansen
martinohansen deleted the martin/repo-init branch September 28, 2026 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants