Skip to content

Cell configuration and org placement share fenced control - #776

Draft
zlareb1 wants to merge 210 commits into
mainfrom
feat/cell-update
Draft

zlareb1 wants to merge 210 commits into
mainfrom
feat/cell-update

Conversation

@zlareb1

@zlareb1 zlareb1 commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Related: #735, #782, #795

Changelog category

  • New Feature

Changelog entry

loom cell update reserves configuration changes before rollout and finishes or reverts them after participant turnover. loom cell place uses the same fenced directory control to place an org without changing an existing placement.

Why

A cell must reserve new issuers and orgs before accepting a configuration, then keep both reservations until old participants can no longer serve it. Configuration updates and explicit org placement share directory identity checks, generation fencing, immutable placement winners and synchronous durability, so they belong to one control protocol.

The SCIM provisioning prerequisite is merged. This PR targets main and retains its update-specific target-policy check. Fresh independent review of all 67 paths on this repaired head found no source findings or nits. The preceding head finished with three failed unit shards, two failed native authority jobs and failed Cell acceptance. Those failures remain recorded. Hosted CI on the repaired source has two failed unit shards: another translation-check worker loss, and three placement HTTP deadline/cancellation failures. Both native authority jobs pass. Cell acceptance has also failed, leaving three failed checks. No merge is qualified.

Scope and risk

The CLI coordinates directory reservations, local Postgres acceptance, complete ClickHouse participant censuses and verified address refresh. Directory changes place configured orgs in the same transaction as reservations and enforce cell closure and quota. Finish and revert narrow local acceptance before releasing the other directory reservation; captured processes must permanently retire or have an exact death proof, and a replacement must serve the selected configuration.

Shared fingerprint checks cover configured orgs, end-user org patterns and issuer reservations. Settings validation and code-repository configuration parsing accept an explicit candidate without changing the running process's settings. The operator coordinator verifies paired stores without joining the participant census it must drain, and preserves an operation's first failure if client cleanup also fails. Placement bounds the complete directory exchange through its owner, separately from local database phases; secondary HTTP cleanup failures preserve the original request failure or cancellation.

Participant validation rejects conflicting state or birth evidence at any equal version, independent of replica row order. A newer winner cannot hide an older conflict.

The main risks are interrupted cross-store operations, concurrent controllers, incomplete participant proof and stale router address caches. Tests cover fencing, interrupted recovery, placement durability, refusal paths and cleanup. A SCIM-on target runs the shared fresh provisioning census before the directory generation claim, after local durability and after participant turnover before reservation release. The CLI must have the target cell's valid SCIM credentials, OIDC login and required authentication. Cached admission permits do not establish this precondition; reverting to SCIM-off current performs no provisioning read.

Compatibility, rollout and rollback

  • Wire: adds operator-authenticated POST /cells/v1/operator/cells/{cell}/place with org, deployment id and fingerprint; GET and POST .../addresses; POST .../configuration/placements; and POST .../configuration. Update writes carry the claimed control generation and exact observed fingerprint pair. Address writes carry store nonces and proposed upstream/probe URLs; configuration writes carry action, target fingerprint, root-secret fingerprint and store nonces. No existing operation or field is removed, and no setting or default is added.
  • Operator steps: use the paired cell stores and router operator credential. Provision every live identity for a SCIM-on target or explicitly pass --revoke-unprovisioned with config, finish or revert. This uses the existing subject leases and SCIM cutoffs; each accepted cutoff is reported immediately and remains if a later check fails. The flag is refused for address refresh. The versioned, nonsecret settings file overlays the CLI's effective settings; the command does not install it. Deploy the participant lifecycle and controller-fencing foundation, permanently terminate or fence legacy processes, and prevent their return before online finalization. Roll out the reserved configuration before finish. For first-cell address refresh, update every router first and retain old endpoints until every router refreshes its routing table or restarts after the directory change. A generation comparison cannot prove fleet-wide agreement.
  • Rollback: rerun an interrupted action or explicitly revert a pending configuration through the documented protocol. Revert preserves immutable placements and local tenancy rows. An interrupted cutoff leaves local acceptance single and directory reservations dual. No migration is added by this stacked diff; reverting code alone does not undo committed directory or tenancy changes.

Tests

  • The preceding hosted run failed two target-census cases because five in-process ASGI clients used an unsupported placeholder origin, and failed the exception-text ratchet because a caught exception became response text. The clients now use the existing supported test origin. Configuration refusal maps only four fixed domain reasons; unknown exceptions propagate without exposing their text. A public-boundary regression fails before the repair, then passes with 27 related controls. Scoped type, lint and format checks pass; all 69 prior assertions remain.
  • Both translation-check worker losses remain unexplained. Their diagnostic stacks sample different Markdown engines and establish no process-exit cause. The actual second CI merge uses the main parent’s translated-output tree, which differs from the topic head at 60 paths; matching pipeline code does not establish matching inputs. No speculative parser change, timeout change or waiver is included. That run’s coverage job was skipped after unit failures and is not accepted. Its Cell check also failed with an empty failure ledger; this does not establish a cause or a performance result. The new head requires its own complete hosted acceptance.
  • The unchanged six placement HTTP deadline cases pass in a bounded local check in 1.60 seconds, so the hosted failures are not locally reproduced. Transport construction cost and the post-acknowledgment termination cause remain unmeasured. No proposed fixture change is included and the failed hosted gate remains blocking.
  • The composed-source check runs the seven actual update provisioning cases with ten configuration, repository-parser and control-census controls. It reproduced seven call-contract failures and ten passes. The parent census removed its then-unused target argument; update needs that target to check SCIM-on before claiming a generation and to revert to SCIM-off without provisioning reads. The target-only contract and deployment check are restored. A corrected rerun was refused before execution by the shared memory admission guard. After observed capacity recovery, the same seventeen cases and the added foreign-target case all pass: eighteen pass in 33.22 seconds.
  • A foreign-target regression requires refusal before identity reads, directory claims or writes. All 38 existing assertions remain unchanged. It passes in the eighteen-case focused check. After removal of the unused update-state tenancy field and its fixture arguments, all twenty-two actual coordinator and provisioning cases pass in 1.28 seconds; every assertion remains unchanged.
  • All sixty Python files in this concern pass scoped Ruff lint, formatting and AST parsing. Four coupled product modules pass scoped mypy checks after adopting the merged prerequisite. The same eighteen target-policy, configuration, repository-parser and control-census cases pass in 32.00 seconds on that composition. Both actual CLI snapshot checks pass in 0.82 seconds and reproduce both snapshots exactly; the actual documentation generator reproduces all 59 outputs exactly. Earlier capacity refusals remain incomplete attempts.
  • Retained focused evidence establishes participant conflict refusal before winner selection: eight demonstrated failures and ten controls become the same eighteen passing cases, together with forty-two existing participant cases. Sixty pass in 1.877 seconds. These results precede this foundation merge.
  • Retained owner, placement, request-size and deadline regressions cover directory fencing, synchronous acceptance, cleanup failure precedence, complete request encoding, cancellation and selected-configuration turnover. The full participant and placement assertions remain. Earlier unit and native results are preserved; they do not establish this composition's acceptance.
  • Three added native cases call the actual update precondition on private cell stores, check positive provisioning, missing-person refusal and changed local acceptance, and compare full local/directory snapshots for no mutation. They are selected for both Postgres 16 and 18. Their corrected-composition execution and complete native coordinator, turnover and physical-standby placement acceptance remain required.
  • The shared Postgres connector binds placement and control cleanup ownership before deployment or codec initialization can wait. Eleven added connection-owner cases first fail on the earlier implementation and then pass on the corrected implementation. On that corrected parent implementation, all eleven pass again in 2.40 seconds; the three product inputs remain byte-identical in this composition. Twenty-four selected caller, late-session, fatal-error, retirement and default-connector controls pass. The five CLI snapshot and connection-census checks pass and reproduce both snapshots exactly; scoped mypy passes on all three product files. The documentation reference check passes, and the architecture text matches the pinned formatter output. The original 223 test assertions and eight assertions in embedded programs remain unchanged. Native fixture seams exercise raw acquisition; native execution remains required in CI.
  • The native placement drill retains the connector’s exact participant tag and all nineteen cancellation, backend/lock-release, retry, audit and promotion assertions. Both preceding native jobs failed the first lookup before promotion. The seed returned after client cancellation without establishing that server cancellation had completed. The seed now awaits bounded driver closure before its existing unconditional termination. Two isolated marked/unmarked cancellation controls fail before this change and pass afterward; scoped syntax, lint and format checks pass. Both actual-source Postgres 16 and 18 jobs now pass: each reports 906 passing authority cases, one skip and one existing xpass, plus passing standby placement, authenticated isolation and reconciliation checks. These are native results for this published head; the failed unit and Cell gates remain blocking.
  • The published head’s Cell run completed all ten arms: 20,500 successful API requests, 25,000 deliveries and its 45,500-row provenance check. Recalculation from retained raw latencies gives a median p99 difference of 31.326599 ms against the unchanged 10 ms limit. Throughput meets its unchanged limit. This is a completed negative performance result; the exact latency cause remains unknown. No retry, workload reduction or threshold change is included.
  • No broad or native local suite ran. Full unit, coverage floors, benchmark, integration, Postgres 16/18, physical-standby placement, mixed-version, generator/schema and all other required hosted gates must pass before merge. Fresh independent review of all 67 paths on this repaired head found no source findings or nits.

AI assistance in the code

  • AI-generated: coding agents wrote most of the diff. Codex checked the foundation conflict resolutions, retained assertions, generated references, scoped static checks and the five coordinator cases. Fresh independent review of all 67 paths on this repaired head found no source findings or nits. Native and full CI remain required.

  • I can explain every line of this diff and how it interacts with the rest of Loom.

Checklist

  • All required format, lint, type, unit and integration CI gates pass on the publication head.
  • All applicable generated-file checks pass on the publication head; the two CLI snapshots and generated CLI reference match locally.
  • No migration is added or changed by the stacked diff.
  • No plugin payload or frontend source changes.
  • The cell architecture and operations pages describe operator steps, wire changes and recovery.
  • Public-copy CI passes on the publication head.
  • Commits are signed off.

zlareb1 and others added 30 commits November 16, 2026 20:44
…are takes the same lock

The attach command holds the attach lock on a direct, marked session of the
cell's Postgres for its run and resumes by the directory row and the cell's
mode. It refuses before any write on the stores' identity, the session, the
roles, settings and subscriptions that would let an unchecked writer through,
the database encoding, durability, its own grants, the ClickHouse writers,
the table list and the processes' heartbeats; posts attach/begin; creates the
triggers under the migration lock; in recording scans and writes the tenancy
rows, refusing an org past ORG_MAX_BYTES; commits enforced, proves it durable,
waits out every transaction that could have read recording, rescans, places
every org in batches and marks the cell serving. A refusal after the mode
commit leaves the cell enforced and attaching, and a rerun resumes there.

Prepare refuses a session behind a pooler or a database that is not UTF8,
and takes the attach lock. Doctor runs attach's Postgres reads again and
reads stray orgs with --stray-orgs. instances.read_recent keeps stopped rows
inside the widened window, and PRUNE_AFTER_S names the sweep's hour.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…t gate measured end to end

docs/operations/cell-attach.md is the operator's procedure: the preconditions
attach checks and those it relies on, the flags, the point of no return at the
mode commit, the orgs attach does not place and the manual removal of an org
past the length limit, and doctor's reads after serving. cells.md describes
the first attach as it runs (the lock, the refusals, the trigger pass, the mode
commit and its durable read, step 4's wait, rescan and final checks), with its
stated limits and failure rows. upgrades.md step 18 rotates the ClickHouse
writer credential after the LOOM_CELL rollout. bench/cell_trigger_gate.py
measures memory.set and a delivery-sized insert through an attached cell with
the org triggers on and off; results.md records a local run.

Attach compares the final root-secret fingerprint with the one its begin
wrote, and the nonce cleanup's message names no single command.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…s no boot or insights module

instances.read_recent takes the window it reads back; attach's heartbeat
module computes it from the live window and a stopping process's drain and
retirement budgets. PRUNE_AFTER_S is marked as the contract it is.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… in wall time, and says when the mode commit's outcome is unknown

The refusals name every table the trigger pass would alter whose owner role
attach's role is not a member of, before any write; ensure_table and
_run_ddl answer applied, busy or denied, so a denial during the pass refuses
at once rather than after --wait as a busy lock.

--wait is wall time: each bounded wait charges its elapsed time, lock tries
included, and every lock try waits at most what is left; scan time stays
outside it. From the mode commit on, a stop that comes before the durable read
says the commit's outcome is unknown and to rerun attach, for a refusal and
for any other error alike.

The prune-window check runs with the refusals, before any write; an enforced
resume runs one trigger pass; the lock session opens inside the block that
closes it; the durable read retries a timeout or an outage only; refusals
name no command that does not exist.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… the attach docs describe one step numbering and today's procedure

--stray-orgs labels only a spent budget as tables left unchecked; any other
refusal names its table and the read continues. A failed catalog read reports
both of attach's Postgres checks as not read. The runbook and doctor describe
removing a stray or over-long org by hand, and name no command that does not
exist yet.

cells.md labels the first attach's list with the design's step names, so step 1
to step 4 mean the same everywhere, rewrites the stuck-process failure row and
the planned tests for a mode that only rises, and says --wait is wall time. The
trigger-cost harness uses cell_triggers.create_statement and deletes the rows
its inserts wrote.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… inside --wait, and doctor warns on the role it runs as

The mode is taken from the first state read, set to unknown only once the
router accepted attach/enforced, and set from what the durable read saw; an
interrupt prints the mode line and goes on. The trigger DDL's lock bound is
taken after the migration lock, from what --wait has left then. An ended mode
transaction whose lock does not clear refuses, naming its backend. A busy
table's holders come back with ensure_table's answer, and attach says them once
per change rather than a boot's warning a try. Attach counts the role it runs as
among its own; doctor does not. The dead SCIM recheck and the unused scim_ok
parameter are gone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… figures say what they establish

cells.md and the runbook state that attach exempts the role it runs as and
doctor does not. results.md gives the marked batch's per-round changes and
their mean, says the delivery-pass gate is met on the mean but not established
by three rounds alone, and that the memory.set p99 gate is unresolved locally.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…nknown only while a try's UPDATE is out, and a busy migration lock is named

Each trigger and mode-commit try gets a lock wait of at least TRY_FLOOR_MS
before --wait is judged spent, so --wait 0 is one try of each wait with no
retry, and an idle cell attaches with it. The run's mode turns unknown just
before a try sends its UPDATE and back to recording when that try rolls back.
A trigger try that finds the migration lock busy names that lock's holder, in
the retry line and in the refusal. The step-4 watch task is awaited after its
cancel. The ATTACH_LOCK_KEY comment says who holds the lock.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…span on one line inside its list items

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Check each probe privilege separately because a comma-separated privilege list accepts any one of them.

Run the attach integration tests in the Postgres matrix and limit their heartbeat reads to the test's own process IDs while retaining the real queries.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Manage mode and direct-session transactions explicitly so a canceled statement cannot start an unbounded rollback. Roll back ordinary mode statement errors within the try's deadline; terminate synchronously when a try ends with an error or cancellation.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Give each trigger attempt a client deadline covering migration lock acquisition, DDL, commit, rollback and unlock. Use explicit transactions so cancellation terminates the session without waiting for rollback or masking the original error with lock cleanup.

Give gate batch scopes a unique prefix per run so cleanup preserves existing rows.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…ancy

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Exercise primary-visible commits, durable duplicate retries and cancellation cleanup on an isolated physical standby pair in both supported Postgres CI jobs.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…are takes the same lock

The attach command holds the attach lock on a direct, marked session of the
cell's Postgres for its run and resumes by the directory row and the cell's
mode. It refuses before any write on the stores' identity, the session, the
roles, settings and subscriptions that would let an unchecked writer through,
the database encoding, durability, its own grants, the ClickHouse writers,
the table list and the processes' heartbeats; posts attach/begin; creates the
triggers under the migration lock; in recording scans and writes the tenancy
rows, refusing an org past ORG_MAX_BYTES; commits enforced, proves it durable,
waits out every transaction that could have read recording, rescans, places
every org in batches and marks the cell serving. A refusal after the mode
commit leaves the cell enforced and attaching, and a rerun resumes there.

Prepare refuses a session behind a pooler or a database that is not UTF8,
and takes the attach lock. Doctor runs attach's Postgres reads again and
reads stray orgs with --stray-orgs. instances.read_recent keeps stopped rows
inside the widened window, and PRUNE_AFTER_S names the sweep's hour.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…t gate measured end to end

docs/operations/cell-attach.md is the operator's procedure: the preconditions
attach checks and those it relies on, the flags, the point of no return at the
mode commit, the orgs attach does not place and the manual removal of an org
past the length limit, and doctor's reads after serving. cells.md describes
the first attach as it runs (the lock, the refusals, the trigger pass, the mode
commit and its durable read, step 4's wait, rescan and final checks), with its
stated limits and failure rows. upgrades.md step 18 rotates the ClickHouse
writer credential after the LOOM_CELL rollout. bench/cell_trigger_gate.py
measures memory.set and a delivery-sized insert through an attached cell with
the org triggers on and off; results.md records a local run.

Attach compares the final root-secret fingerprint with the one its begin
wrote, and the nonce cleanup's message names no single command.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…s no boot or insights module

instances.read_recent takes the window it reads back; attach's heartbeat
module computes it from the live window and a stopping process's drain and
retirement budgets. PRUNE_AFTER_S is marked as the contract it is.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… in wall time, and says when the mode commit's outcome is unknown

The refusals name every table the trigger pass would alter whose owner role
attach's role is not a member of, before any write; ensure_table and
_run_ddl answer applied, busy or denied, so a denial during the pass refuses
at once rather than after --wait as a busy lock.

--wait is wall time: each bounded wait charges its elapsed time, lock tries
included, and every lock try waits at most what is left; scan time stays
outside it. From the mode commit on, a stop that comes before the durable read
says the commit's outcome is unknown and to rerun attach, for a refusal and
for any other error alike.

The prune-window check runs with the refusals, before any write; an enforced
resume runs one trigger pass; the lock session opens inside the block that
closes it; the durable read retries a timeout or an outage only; refusals
name no command that does not exist.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… the attach docs describe one step numbering and today's procedure

--stray-orgs labels only a spent budget as tables left unchecked; any other
refusal names its table and the read continues. A failed catalog read reports
both of attach's Postgres checks as not read. The runbook and doctor describe
removing a stray or over-long org by hand, and name no command that does not
exist yet.

cells.md labels the first attach's list with the design's step names, so step 1
to step 4 mean the same everywhere, rewrites the stuck-process failure row and
the planned tests for a mode that only rises, and says --wait is wall time. The
trigger-cost harness uses cell_triggers.create_statement and deletes the rows
its inserts wrote.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… inside --wait, and doctor warns on the role it runs as

The mode is taken from the first state read, set to unknown only once the
router accepted attach/enforced, and set from what the durable read saw; an
interrupt prints the mode line and goes on. The trigger DDL's lock bound is
taken after the migration lock, from what --wait has left then. An ended mode
transaction whose lock does not clear refuses, naming its backend. A busy
table's holders come back with ensure_table's answer, and attach says them once
per change rather than a boot's warning a try. Attach counts the role it runs as
among its own; doctor does not. The dead SCIM recheck and the unused scim_ok
parameter are gone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… figures say what they establish

cells.md and the runbook state that attach exempts the role it runs as and
doctor does not. results.md gives the marked batch's per-round changes and
their mean, says the delivery-pass gate is met on the mean but not established
by three rounds alone, and that the memory.set p99 gate is unresolved locally.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…nknown only while a try's UPDATE is out, and a busy migration lock is named

Each trigger and mode-commit try gets a lock wait of at least TRY_FLOOR_MS
before --wait is judged spent, so --wait 0 is one try of each wait with no
retry, and an idle cell attaches with it. The run's mode turns unknown just
before a try sends its UPDATE and back to recording when that try rolls back.
A trigger try that finds the migration lock busy names that lock's holder, in
the retry line and in the refusal. The step-4 watch task is awaited after its
cancel. The ATTACH_LOCK_KEY comment says who holds the lock.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…span on one line inside its list items

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Check each probe privilege separately because a comma-separated privilege list accepts any one of them.

Run the attach integration tests in the Postgres matrix and limit their heartbeat reads to the test's own process IDs while retaining the real queries.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Personal callers await verification once; guarded identity rows retain signed domain claims and personal-token kind. The verified-email migration follows the existing journal.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
A failed global-row or Keeper cleanup must still allow remaining exact-resource cleanup and disconnect. Propagate the first teardown failure after all attempts.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Compose the reviewed attachment foundation while retaining every update and placement integration selection and the physical-standby durability drill.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Reserve the largest live or operator request with the same body limit. Keep parser diagnostics observable and attempt independent fixture cleanup after setup or teardown failures.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Carry the existing placement deadline, first-failure cleanup and regression coverage into shared control. Reserve materialized default fields without replacing the recorded fingerprint or dropping unknown fields.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Drain independently registered resources before propagating setup failures; keep teardown errors fatal after successful use.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
An unresolved shared contact could repair admin owner grants before refusing sign-in. Check active passwordless and linked accounts before repair or signup while retaining genuine first sign-ins.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Reuse the cell provisioning census before claiming update ownership, after local acceptance and before final reservation release. Explicit cutoffs retain the same subject leases and immediate reporting as attachment.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
@zlareb1
zlareb1 changed the base branch from feat/cell-attach-cli to feat/cell-scim-person November 18, 2026 15:29
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Compare repeated identity and version pairs independently of their order so a newer replica row cannot hide conflicting older evidence.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Use the complete provisioning decision for authentication, consent, token ancestry and first-cell attachment while retaining verified ownership and cell scope.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Remove unused policy branches, describe dry-run participation and adopt the verified generated OAuth schema. Reuse the existing authorization import to retain the invalidation guard within the function limit.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Keep the blank-person refusal inside enforced provisioning and redact tenancy refusal details. Match test I/O fakes and public refusal expectations to the shared authentication path, and regenerate the schema statement corpus.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Read the diagnostic owner's four-value result and assert the prepared
first-cell identity. Preserve the marker and trigger checks.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Adopt the provisioning foundation while retaining update and placement control. Check the intended target before claims and reservation release, and remove an unused local tenancy observation.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Bind cleanup ownership before deployment and codec checks can wait, so cancellation closes the session within the control attempt deadline. Placement uses the same acquisition path once.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Use the connector's exact participant tag when waiting for synchronous replication, so the drill reaches cancellation and standby promotion checks.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
@zlareb1
zlareb1 changed the base branch from feat/cell-scim-person to main November 19, 2026 22:45
@zlareb1 zlareb1 closed this Nov 19, 2026
@zlareb1 zlareb1 reopened this Nov 19, 2026
…ocal

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Drain the cancellation acknowledgement before closing the seed connection so the first lookup sees the completed transaction. Keep the standby paused and retain the durability assertions.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>

This branch has not been deployed

No deployments
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