DongHyeonkaandClaude Opus 5
b2963105a8
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
16 lines
958 B
Plaintext
16 lines
958 B
Plaintext
### 8.2 P2 — admin 스위치가 가드를 켜고 서비스는 켜지 않는다
|
|
|
|
`app.messaging.admin.enabled=true`가 만드는 bean은 넷이다: `DestructiveOperationGuard`, `AdminOperationJournal`, `MessagingAdminDurabilityValidator`, (`BrokerTopologyInspector`가 있을 때) `CompositeTopologyValidator`.
|
|
|
|
만들지 않는 것:
|
|
|
|
| 타입 | leaf | main 참조 | 부재가 문서화됐는가 |
|
|
|---|---|---|---|
|
|
| `DestructiveMessagingAdmin` | admin-runtime | 2 | **예** — javadoc이 명시 |
|
|
| `DefaultMessagingAdminService` | admin-runtime | **0** | 아니오 |
|
|
| `HmacApprovalVerifier` | admin-api | **0** (test 4) | 아니오 |
|
|
| `TopologyValidationRuntime` | admin-runtime | **0** | 아니오 |
|
|
| `RedriveService` / `ReplayService` | admin-runtime | 2 / 1 | 아니오 |
|
|
|
|
`DefaultMessagingAdminService`는 `MessagingAdminService`(인터페이스, main 참조 2)의 **유일한 구현**이다. 즉 admin plane을 켜도 admin 서비스가 없다.
|