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>
48 lines
3.2 KiB
Plaintext
48 lines
3.2 KiB
Plaintext
# evidence 259 — messaging-flyway-migration-namespace
|
|
# revision: a24ece9cf797f7ea647e33bf846b115208ed1ba5
|
|
# cwd: /shared/codebase/clean-architecture-backend-template/src/messaging
|
|
# command: bash /tmp/flyway.sh
|
|
# ---- raw output ----
|
|
---- messaging migrations (git-tracked) ----
|
|
src/messaging/messaging-inbox-jdbc-postgresql/src/main/resources/db/migration/messaging/V2__messaging_inbox.sql
|
|
src/messaging/messaging-outbox-jdbc-postgresql/src/main/resources/db/migration/messaging/V1__messaging_outbox.sql
|
|
src/messaging/messaging-outbox-jdbc-postgresql/src/main/resources/db/migration/messaging/V2__messaging_outbox_lease_fencing.sql
|
|
src/messaging/messaging-outbox-jdbc-postgresql/src/main/resources/db/migration/messaging/V3__messaging_admin_operation_journal.sql
|
|
src/messaging/messaging-outbox-jdbc-postgresql/src/main/resources/db/migration/messaging/V4__messaging_outbox_canonical_metadata.sql
|
|
|
|
---- primary Flyway location set by the composition root ----
|
|
src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/experimental/schema/SchemaTenantMigrationOrchestrator.java:83: .locations(migrationLocation)
|
|
src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/postgresql/PostgreSqlPersistenceConfig.java:94: * <p>This unconditionally called {@code locations(...)}, which replaces whatever Spring bound
|
|
src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/postgresql/PostgreSqlPersistenceConfig.java:115: configuration.locations("classpath:db/migration/postgresql");
|
|
src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/notification/NotificationSchemaStream.java:60: .locations(LOCATION)
|
|
|
|
---- conditional schema streams (each with its own history table) ----
|
|
src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/notification/NotificationSchemaStream.java:25: public static final String LOCATION = "classpath:db/migration/jpa/notification-platform";
|
|
|
|
---- does any main-code location name db/migration/messaging? ----
|
|
(no main-code hit above == the messaging migration stream is never applied)
|
|
|
|
---- the two V2 files sharing one resource directory ----
|
|
inbox leaf:
|
|
V2__messaging_inbox.sql
|
|
outbox leaf:
|
|
V1__messaging_outbox.sql
|
|
V2__messaging_outbox_lease_fencing.sql
|
|
V3__messaging_admin_operation_journal.sql
|
|
V4__messaging_outbox_canonical_metadata.sql
|
|
|
|
V2__messaging_inbox.sql creates:
|
|
7:CREATE TABLE messaging_inbox
|
|
V2__messaging_outbox_lease_fencing.sql changes:
|
|
15:ALTER TABLE messaging_outbox
|
|
22:ALTER TABLE messaging_outbox
|
|
28:ALTER TABLE messaging_outbox
|
|
31:ALTER TABLE messaging_outbox
|
|
37:CREATE INDEX ix_messaging_outbox_next_attempt
|
|
|
|
---- the implementation plan specified separate locations ----
|
|
3010:- Create: `modules/messaging/messaging-outbox-jpa/src/main/resources/db/migration/messaging-outbox/V1__create_messaging_outbox.sql`
|
|
3011:- Create: `modules/messaging/messaging-inbox-jpa/src/main/resources/db/migration/messaging-inbox/V1__create_messaging_inbox.sql`
|
|
3032: migrate("classpath:db/migration/messaging-outbox");
|
|
3055: migrate("classpath:db/migration/messaging-inbox");
|