Align control-path bootstrap with TF-SDK for Release 2.0.0

Konstantinos Togiasrequested to merge
fix/single-bootstrap-control-paths into develop

Align control-path bootstrap with TF-SDK for Release 2.0.0

Target: refactor/tf-sdk-srm-bug-fixes

Based on 2c083de, with the published SDK through 1b778a3.

Builds topology discovery and the execution registry from one SDK-loaded bootstrap. The registry key supplies each adapter's control_path_ref; the SDK checks incoming requests against that identity before backend work.

Replaces independent CONTROL_PATH_SETTINGS__ENTRIES input with the complete file selected by BOOTSTRAP_TOPOLOGY_PATH. Adds duplicate/conflicting identity checks and reuses existing SDK error mapping. Empty health startup and create-missing topology seeding remain available. Placement, database schema and termination use cases retain their existing behavior.

Requires TF-SDK 2.0.0rc3 and the matching deployment configuration: explicit kubeconfig/context/namespace or explicit in-cluster mode, protected credential mounts and a writable SDK runtime directory. Remove the chart's old controlPaths list. Upgrade or roll back the compatible component set together.

Local validation in a fresh locked environment with the registry-published SDK wheel:

  • Full SRM suite, including PostgreSQL/NATS integration: 535 passed.
  • Full mypy, Ruff lint/format and both import-boundary contracts passed.
  • New cases cover one bootstrap load, wrong-instance rejection, concurrent routes and invalid configuration. Observation and termination semantics remain unchanged.
  • Registry wheel and sdist match the tested tag-build hashes. The lock uses their actual published URLs; other package versions remain unchanged.
  • Live OEG/two-cluster acceptance remains separate.

Run MR CI with the locked dependencies before merge. Integrate the matching SDK/SRM/chart/configuration migration together.

Merge request reports