Dmitrii Kovalkov e83f1d8ba5 tests: prepare test_historic_storage_formats for --timelines-onto-safekeepers (#12214) ...

## Problem
`test_historic_storage_formats` uses `/tenant_import` to import historic
data. Tenant import does not create timelines onto safekeepers, because
they might already exist on some safekeeper set. If it does, then we may
end up with two different quorums accepting WAL for the same timeline.

If the tenant import is used in a real deployment, the administrator is
responsible for looking for the proper safekeeper set and migrate
timelines into storcon-managed timelines.

- Relates to https://github.com/neondatabase/neon/pull/11712

## Summary of changes
- Create timelines onto safekeepers manually after tenant import in
`test_historic_storage_formats`
- Add a note to tenant import that timelines will be not storcon-managed
after the import.

2025-06-13 06:28:18 +00:00

..

client

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

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

migrations

storcon: Introduce deletion tombstones to support flaky node scenario (#12096)

2025-06-06 10:16:55 +00:00

src

tests: prepare test_historic_storage_formats for --timelines-onto-safekeepers (#12214)

2025-06-13 06:28:18 +00:00

Cargo.toml

storcon: add https API (#11239)

2025-03-20 08:22:02 +00:00