test(cdc): replay truthful target capability RED on live develop - #308
test(cdc): replay truthful target capability RED on live develop#308seonghobae wants to merge 1 commit into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Superseded by current-base replacement #312. Immediately before this disposition, protected |
Rebuilds issue #202's bounded capability/execution-authority slice from exact protected
develop@502d1e2136f18b7dea3baa792559128dc87fec39instead of mutating stale-base Draft #255.RED identity
f698e8e6b1dcd0703cc2b134c5d0c2f4dd09f4b5502d1e2136f18b7dea3baa792559128dc87fec39cdc-service/src/test/java/com/xtrmetl/cdc/spi/CdcTargetCapabilityTest.javaCdcTargetConnectorstill has onlyscaffoldOnly()plus unconditionalwrite(...)authority, so live raw Kafka/JDBC-replica product paths cannot truthfully disclose that their canonical write SPI is unwired.The fail-first contract reaches the public production SPI via reflection and requires machine-readable product-path liveness, canonical-write support, and delivery mode for both shipped targets. Valid RED is the focused assertion failing because
capabilities()is absent after normal compilation/test startup; setup/import/dependency/runner failure does not qualify.After valid current-base RED, replay only the bounded capability record/enum and Kafka/JDBC capability implementations already isolated in #255, preserving backward-compatible raw product paths and keeping HTTP projection outside this slice. No checks/reviews from #255 or predecessors transfer.