Dmitrii Kovalkov 312a74f11f storcon: implement safekeeper_migrate_abort handler (#12705) ...

## Problem
Right now if we commit a joint configuration to DB, there is no way
back. The only way to get the clean mconf is to continue the migration.
The RFC also described an abort mechanism, which allows to abort current
migration and revert mconf change. It might be needed if the migration
is stuck and cannot have any progress, e.g. if the sk we are migrating
to went down during the migration. This PR implements this abort
algorithm.

- Closes: https://databricks.atlassian.net/browse/LKB-899
- Closes: https://github.com/neondatabase/neon/issues/12549

## Summary of changes
- Implement `safekeeper_migrate_abort` handler with the algorithm
described in RFC
- Add `timeline-safekeeper-migrate-abort` subcommand to `storcon_cli`
- Add test for the migration abort algorithm.

2025-07-31 12:40:32 +00:00

..

client

storcon + safekeeper + scrubber: propagate root CA certs everywhere (#11418)

2025-04-04 06:30:48 +00:00

migrations

storcon: finish safekeeper migration gracefully (#12528)

2025-07-22 14:58:20 +00:00

src

storcon: implement safekeeper_migrate_abort handler (#12705)

2025-07-31 12:40:32 +00:00

Cargo.toml

A few SC changes (#12615)

2025-07-17 13:14:36 +00:00