Skip to content

feat(control-plane): require complete plan publication - #466

Merged
zzylol merged 2 commits into
mainfrom
feat/atomic-plan-publication
Sep 3, 2026
Merged

zzylol merged 2 commits into
mainfrom
feat/atomic-plan-publication

Conversation

@zzylol

@zzylol zzylol commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Summary

  • make BackendPlan a required member of each coupled publication generation
  • report per-document streaming/routing/plan status on desynchronization
  • refuse partial publication when BackendPlan emission fails
  • distinguish the uninitialized bootstrap plan from an installed active plan
  • keep legacy serving available only before the first real plan activation

Validation

  • cargo test -p control_plane emit::backend_push --lib (15 passed)
  • cargo test -p data_plane --test e2e_controller_plans_and_backend_serves controller_really_pushes_backend_plan_and_query_really_serves
  • git diff --check

Stack

Depends on #465.

@zzylol
zzylol changed the base branch from feat/backend-plan-sid-binding to main September 3, 2026 02:54
@zzylol
zzylol merged commit ca34fee into main Sep 3, 2026
1 check passed
@zzylol
zzylol deleted the feat/atomic-plan-publication branch September 12, 2026 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant