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>
2.4 KiB
kind, slug, title, topic, project, status, sourceRevision, rootTreeNode, evidenceCapturedOn, assets, evidence, source, module
| kind | slug | title | topic | project | status | sourceRevision | rootTreeNode | evidenceCapturedOn | assets | evidence | source | module | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CONCEPT | adapter-outbound-cache-redis-c02 | 기본값이 가리키는 리소스가 없고 그것이 시작 실패로 잡힌다 | composition-and-lifecycle-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-cache-redis-c02 | 2026-09-01 |
|
|
|
adapter-outbound-cache-redis |
기본값이 가리키는 리소스가 없고 그것이 시작 실패로 잡힌다
RedisSdkSettings.Raw.policyResource 기본값 classpath:redis-sdk/raw-command-allowlist.yml은 저장소에 없는 파일이다. 결함이 아니라 이미 잡혀 있는 함정이다.
본문
RedisSdkSettings.Raw.policyResource 기본값은 classpath:redis-sdk/raw-command-allowlist.yml인데, 저장소에 그 파일은 없다(159-... §8.3b, git ls-files 매치 0. 이 leaf의 main resource는 AutoConfiguration.imports와 redis-sdk/redis-command-policy.yml 둘뿐).
결함이 아니라 이미 잡혀 있는 함정이다
requireRawPolicyResource가 그 사실과 과거 증상을 함께 적는다.
"
validate()only checks that the setting is non-blank, and the default points at … a resource this module does not ship. So enabling the raw gateway passed configuration validation and then failed at the first raw command, from inside a request, against a live connection. The allowlist is the entire authorisation model for that gateway; not being able to read it is a startup failure."
test enabledRejectsAMissingRawAllowlistResource와 enabledAcceptsAReadableRawAllowlistResource가 양쪽을 고정한다.
분석 원문의 확인 절차
:::evidence key="adapter-outbound-cache-redis-c02" alt="분석 문서 analysis/10-adapter-outbound-cache-redis.md 에서 이 기록의 근거 절을 그대로 잘라낸 15줄. 코드베이스를 측정한 것이 아니라 원본 판정이 무엇을 적었는지를 보여 준다." caption="analysis/10-adapter-outbound-cache-redis.md 발췌 — 15줄" zoom="true" :::