Vlad Lazar 3e4cbaed67 storcon: validate intent state before applying optimization (#12593) ...

## Problem

In the gap between picking an optimization and applying it, something
might insert a change to the intent state that makes it incompatible.
If the change is done via the `schedule()` method, we are covered by the
increased sequence number, but otherwise we can panic if we violate the
intent state invariants.

## Summary of Changes

Validate the optimization right before applying it. Since we hold the
service lock at that point, nothing else can sneak in.

Closes LKB-65

2025-07-16 14:37:40 +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 intent state before applying optimization (#12593)

2025-07-16 14:37:40 +00:00

Cargo.toml

pageserver: add gRPC LSN lease support (#12384)

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