Skip to content

[Deploy] Add backup freshness preflight for destructive migrations (#3781)#3937

Open
josemiguel3125-sketch wants to merge 1 commit into
orchestration-agent:mainfrom
josemiguel3125-sketch:fix/bounty-3781
Open

[Deploy] Add backup freshness preflight for destructive migrations (#3781)#3937
josemiguel3125-sketch wants to merge 1 commit into
orchestration-agent:mainfrom
josemiguel3125-sketch:fix/bounty-3781

Conversation

@josemiguel3125-sketch
Copy link
Copy Markdown

Description

Fixes #3781

Adds a preflight gate that blocks destructive migrations unless a recent verified backup exists.

Changes

  • src/migration/metadata.pyMigrationMetadata with MigrationClass.DESTRUCTIVE / NON_DESTRUCTIVE
  • src/migration/backup.pyBackupVerifier checks backup existence, age, and restore validity
  • src/migration/preflight.pyPreflightGate iterates migrations and gates destructive ones
  • CLI integrationdeploy command accepts --backup and --migration-metadata flags

Acceptance Criteria

  • Destructive migrations fail preflight without a recent verified backup
  • The preflight reports backup timestamp and restore check status
  • Migration metadata declares whether the change is destructive

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.

[ Bounty $4k ] [ Deploy ] Verify backup freshness before destructive migrations — release preflight

1 participant