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>
49 lines
2.4 KiB
Plaintext
49 lines
2.4 KiB
Plaintext
# 벤더 설정 — 사건을 기록한 javadoc
|
|
/**
|
|
* The vendor's migration location, as a default rather than as an override.
|
|
*
|
|
* <p>This unconditionally called {@code locations(...)}, which replaces whatever Spring bound
|
|
* from {@code spring.flyway.locations}. An operator could therefore set {@code
|
|
* SPRING_FLYWAY_LOCATIONS} to add the capability streams, watch Flyway report a successful
|
|
* migration, and get only the vendor stream — the property was read, bound, and then discarded by
|
|
* a customizer that runs after it. The {@code local-notification-ingest} lane set seven locations
|
|
* and applied one.
|
|
*
|
|
* <p>It is the same shape as {@code application-local.yml}'s literal pins, which outranked every
|
|
* environment a caller supplied, and the same fix: contribute the value when nobody has chosen
|
|
* one, and stay out of the way when somebody has. A deployment that names its own locations is
|
|
* responsible for including this one, which is exactly the responsibility it took by naming them.
|
|
*
|
|
* @param environment the resolved environment, consulted for an operator-supplied value
|
|
* @return the customizer
|
|
*/
|
|
|
|
# 벤더 설정 — 지금 구현
|
|
@Bean
|
|
public static FlywayConfigurationCustomizer postgreSqlFlywayLocationCustomizer(
|
|
org.springframework.core.env.Environment environment) {
|
|
return configuration -> {
|
|
String chosen = environment.getProperty("spring.flyway.locations", "").trim();
|
|
if (chosen.isEmpty()) {
|
|
configuration.locations("classpath:db/migration/postgresql");
|
|
}
|
|
};
|
|
}
|
|
|
|
# 같은 빈 이름을 쓰는 sample 쪽 — 아직 무조건 호출
|
|
* {@code static @Bean} (called without instantiating the owning class, so no
|
|
* {@code @PersistenceContext} injection during Flyway init). Sets both migration locations:
|
|
* production {@code db/migration/postgresql} + sample {@code db/sample-migration}. {@code
|
|
* locations(...)} replaces rather than appends, so this — not {@code spring.flyway.locations} in
|
|
* application.yml — is the effective source of truth. See README.
|
|
*/
|
|
@Bean
|
|
public static FlywayConfigurationCustomizer postgreSqlFlywayLocationCustomizer() {
|
|
return configuration ->
|
|
configuration.locations(
|
|
"classpath:db/migration/postgresql", "classpath:db/sample-migration");
|
|
}
|
|
|
|
# H2 쪽은 커스터마이저를 아예 두지 않는다
|
|
21: * <p><b>No Flyway location customizer, deliberately.</b> The PostgreSQL vendor points Flyway at
|