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>
32 lines
1.7 KiB
Plaintext
32 lines
1.7 KiB
Plaintext
# 출하 파일 안의 같은 이름, 다른 타입 — 네임스페이스와 함께
|
|
37: hikari:
|
|
connection-timeout: ${APP_DATASOURCE_CONNECTION_TIMEOUT:5000}
|
|
322: tomcat:
|
|
connection-timeout: ${APP_SERVER_TOMCAT_CONNECTION_TIMEOUT:20s}
|
|
|
|
# 앞쪽이 바인딩되는 세터
|
|
public long getConnectionTimeout();
|
|
public void setConnectionTimeout(long);
|
|
|
|
# 같은 키를 읽는 시작 검증기는 다른 규칙으로 읽는다
|
|
16:public class HikariPoolConstraintValidator implements SmartInitializingSingleton {
|
|
18: static final String CONNECTION_TIMEOUT_KEY = "spring.datasource.hikari.connection-timeout";
|
|
26: static final String CONNECTION_TIMEOUT_ENV_KEY = "APP_DATASOURCE_CONNECTION_TIMEOUT";
|
|
8:import org.springframework.boot.convert.DurationStyle;
|
|
125: return DurationStyle.detectAndParse(raw.trim(), ChronoUnit.MILLIS).toMillis();
|
|
|
|
# 지금은 정적 가드가 이 형식을 막는다
|
|
private static final List<String> PLAIN_MILLISECOND_KEYS =
|
|
List.of(
|
|
"spring.datasource.hikari.connection-timeout",
|
|
"spring.datasource.hikari.validation-timeout",
|
|
"spring.datasource.hikari.idle-timeout",
|
|
"spring.datasource.hikari.keepalive-time",
|
|
"spring.datasource.hikari.max-lifetime",
|
|
"spring.datasource.hikari.leak-detection-threshold",
|
|
"spring.datasource.hikari.initialization-fail-timeout");
|
|
(그 가드가 한 번 헛짚었던 자리)
|
|
* <p>An earlier version matched the key's leaf name with a regex and reported {@code
|
|
* server.tomcat.connection-timeout: 20s} — a genuine {@code Duration} — as a defect. Flattening
|
|
* through the real loader means the check is about the property this list names and not about
|