infobloxopen / migrate

52%

ib: 52%

LAST BUILD ON BRANCH dirty-state-down-steps-up

branch: dirty-state-down-steps-up

CHANGE BRANCH

x

Reset

Sync Branches

• dirty-state-down-steps-up
• alpine-master
• alpine-upgrade
• aws-sdk-v2
• hostname_pgx
• hotload
• ib
• image-scan
• jenkins-go
• master
• merge-upstream
• no-make-docker
• pgx-migrate-test
• pgx_hotload
• pgx_pg
• pgx_register
• refs/tags/v1.0.10
• refs/tags/v1.0.3
• refs/tags/v1.0.4
• refs/tags/v1.0.6
• refs/tags/v1.0.7
• refs/tags/v1.0.8
• refs/tags/v1.0.9
• reportImage
• specify-alpine-version
• storeMigratesInDB
• tdrpt-6373-reduce-CVEs
• tdrpt-6835-reduce-cves
• update-go
• update_aws_go_version_to_v2
• upgrade-otel-v1.42.0

Build # 23698473245

Build Type

Pull #57

github

Committed by daniel-garcia

Commit Message

Add dirty state handling to Down(), Steps(), and Up()

Previously only Migrate() supported dirty state recovery, file copying,
and cleanup. Down(), Steps(), and Up() would reject dirty state with
ErrDirty and had no file copy infrastructure for rollback support.

Now all three functions follow the same pattern as Migrate():
- Recover from dirty state via handleDirtyState() when enabled
- Copy migration files to dest volume via copyFiles()
- Clean up files above target version via cleanupFiles()
- handleMigrationFailure() already fires on error via runMigrations()

Backward compatible: without dirtyStateConf, ErrDirty behavior unchanged.

Pull Request Pull Request #57: Add dirty state handling to Down(), Steps(), and Up()

Coverage Stats

44 of 68 new or added lines in 1 file covered. (64.71%)

2 existing lines in 1 file now uncovered.

4384 of 8409 relevant lines covered (52.13%)

23.99 hits per line