Skip to content

fix(postgres): guard archived Sentry snapshot and restore tools - #27

Open
kaanyagci wants to merge 5 commits into
mainfrom
ops/sentry-database-separation
Open

kaanyagci wants to merge 5 commits into
mainfrom
ops/sentry-database-separation

Conversation

@kaanyagci

@kaanyagci kaanyagci commented Sep 16, 2026 •

Copy link
Copy Markdown
Member

Preserves the host-specific September Sentry storage migration tools and runbook without changing the shared PostgreSQL deployment. Generated resolved configurations remain host-local. Historical cutover observations in the runbook are not a claim of a new production deployment.

The restore tool now requires an exact manifest for every mapped archive, unique destination volumes, valid archive names, and matching sizes and SHA-256 checksums before creating any volume. Snapshotting rejects any running container using a source volume, even under a different Compose project. Existing destination volumes remain protected.

Validation: eight isolated tests cover valid restoration, missing/extra manifest entries, duplicate targets, wrong sizes/checksums, existing destinations, and a writer in another Compose project. The original scripts failed the regression suite; all eight tests pass after the guards. This suite is included in CI. No production snapshot, restore, or migration was executed.

Review update — 2026-10-13

Reconciled with current main. All eight archived Sentry snapshot/restore guard tests passed. These are archived migration utilities; no historical migration was executed against production.

Merge and deployment remain pending protected-branch approval and applicable production prerequisites.

@kaanyagci
kaanyagci added this pull request to stack #30 September 16, 2026 10:39
@kaanyagci
kaanyagci marked this pull request as ready for review October 11, 2026 10:25
@kaanyagci kaanyagci changed the title Record verified standalone Sentry storage migration fix(postgres): guard archived Sentry snapshot and restore tools Oct 11, 2026

This branch has not been deployed

No deployments
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.

1 participant