Dmitrii Kovalkov ee7bb1a667 storcon: validate new_sk_set before starting safekeeper migration (#12546) ...

## Problem
We don't validate the validity of the `new_sk_set` before starting the
migration. It is validated later, so the migration to an invalid
safekeeper set will fail anyway. But at this point we might already
commited an invalid `new_sk_set` to the database and there is no `abort`
command yet (I ran into this issue in neon_local and ruined the timeline
:)

- Part of https://github.com/neondatabase/neon/issues/11669

## Summary of changes
- Add safekeeper count and safekeeper duplication checks before starting
the migration
- Test that we validate the `new_sk_set` before starting the migration
- Add `force` option to the `TimelineSafekeeperMigrateRequest` to
disable not-mandatory checks

2025-07-12 04:57:04 +00:00

..

client

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

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

migrations

Add new activating scheduling policy for safekeepers (#12441)

2025-07-03 16:27:43 +00:00

src

storcon: validate new_sk_set before starting safekeeper migration (#12546)

2025-07-12 04:57:04 +00:00

Cargo.toml

pageserver: add gRPC LSN lease support (#12384)

2025-06-30 12:44:17 +00:00