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>
51 lines
2.4 KiB
Markdown
51 lines
2.4 KiB
Markdown
---
|
||
kind: CONCEPT
|
||
slug: adapter-outbound-objectstorage-c02
|
||
title: 레거시 경로 셋이 서로 다른 스위치로 서로를 배제한다
|
||
topic: admission-budget-and-backpressure
|
||
project: clean-architecture-backend-template
|
||
status: 게시 전
|
||
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
||
rootTreeNode: concept:adapter-outbound-objectstorage-c02
|
||
evidenceCapturedOn: 2026-09-01
|
||
assets:
|
||
- key: adapter-outbound-objectstorage-c02
|
||
file: ../../../final/evidence/rendered/adapter-outbound-objectstorage-c02.svg
|
||
evidence:
|
||
- ../../../final/evidence/raw/adapter-outbound-objectstorage-c02.txt
|
||
source:
|
||
- 원본 분석 절은 analysis/09-adapter-outbound-objectstorage.md#L92 이다.
|
||
module: adapter-outbound-objectstorage
|
||
---
|
||
|
||
# 레거시 경로 셋이 서로 다른 스위치로 서로를 배제한다
|
||
|
||
폐기 경로가 셋인데 서로 다른 스위치를 쓰고 서로를 배제한다. 겹침은 컴파일러가 거부한다.
|
||
|
||
## 본문
|
||
|
||
<!-- body:start -->
|
||
|
||
폐기 경로가 셋인데 서로 다른 스위치를 쓰고 서로를 배제한다.
|
||
|
||
| 경로 | 스위치 | 성격 |
|
||
|---|---|---|
|
||
| 선호 임시 활성화 | `app.object-storage.legacy.enabled=true` + 명시적 backend | `ObjectStoragePort`(whole-`byte[]`) 노출 |
|
||
| 구 alias | `ca-skeleton.objectstorage.*` | `LegacyObjectStorageActivationGuard` 조건, canonical과 혼용 시 실패 |
|
||
| 채택(adoption) | `app.object-storage.legacy-adoption.enabled=true` | raw locator 유지보수 전용, 별도 config 클래스 |
|
||
|
||
## 겹침을 거부하는 지점
|
||
|
||
`ObjectStorageBindingCompiler.rejectLegacyOverlap`가 legacy filesystem 루트와 canonical provider 루트가 **어느 방향으로든 포함 관계**면 거부한다.
|
||
|
||
## ObjectStorageBindingCompiler 참조 위치
|
||
|
||
:::evidence key="adapter-outbound-objectstorage-c02" alt="코드베이스에서 ObjectStorageBindingCompiler 를 검색한 출력 22줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="ObjectStorageBindingCompiler 코드베이스 검색 — 22줄 · exit 0" zoom="true"
|
||
:::
|
||
|
||
## 채택 모드가 추가로 요구하는 것
|
||
|
||
`LegacyObjectAdoptionSettings`는 `APPLY` 모드일 때 검토된 manifest 경로와 64자리 SHA-256을 요구하고, batch size 1–1000, timeout 5분 이내를 강제한다. legacy runtime은 `AutoCloseable` holder로 감싸 S3 client 수명을 정확히 소유하고, `@Bean(destroyMethod = "close")`로 등록된다.
|
||
|
||
<!-- body:end -->
|