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>
31 lines
2.1 KiB
Plaintext
31 lines
2.1 KiB
Plaintext
# command: ./gradlew :messaging:messaging-outbox-jdbc-postgresql:test --rerun-tasks --console=plain
|
|
# revision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
|
# exit: 0
|
|
|
|
BUILD SUCCESSFUL in 20s
|
|
29 actionable tasks: 29 executed
|
|
|
|
name="dev.caskeleton.messaging.outbox.AdminOperationJournalPostgresIT" tests="7" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.outbox.DebeziumOutboxRecordMapperTest" tests="16" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.outbox.JdbcOutboxTransactionRequirementTest" tests="4" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.outbox.OutboxEnvelopeFactoryTest" tests="6" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.outbox.OutboxOperationsTest" tests="10" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.outbox.OutboxPostgresIT" tests="21" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.outbox.OutboxRelayTest" tests="9" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.outbox.OutboxRelayWorkerTest" tests="3" skipped="0" failures="0" errors="0"
|
|
TOTAL tests=76 failures=0 errors=0 skipped=0
|
|
|
|
# ***중요*** 컨테이너 레인이 실제로 실행되었다.
|
|
# OutboxPostgresIT 21건, AdminOperationJournalPostgresIT 7건 — skipped=0 이며 tests>0.
|
|
# 즉 Testcontainers 가 Postgres 컨테이너를 띄웠고 그에 대해 단언이 실행되었다.
|
|
#
|
|
# command: docker version --format "client={{.Client.Version}} server={{.Server.Version}}"
|
|
# client=29.1.3 server=29.6.1
|
|
# command: ls -la /var/run/docker.sock
|
|
# srw-rw---- 1 root 984 0 Aug 27 03:28 /var/run/docker.sock
|
|
#
|
|
# => 이 분석 환경(workmachine)에서 컨테이너 런타임을 쓸 수 있다.
|
|
# 앞선 리프 문서들이 "컨테이너 필요 — 이 세션에서 미실행" 으로 남긴 항목들
|
|
# (messaging-kafka 인증 레인, messaging-rabbit 브로커 IT 등)은
|
|
# 실행 불가가 아니라 아직 실행하지 않은 것이다. 해당 리프 분석 시 실행한다.
|