Skip to content

fix(cdc): expose truthful target execution capabilities - #249

Closed
seonghobae wants to merge 4 commits into
developfrom
fix/cdc-target-capability-truth-c2511f6
Closed

fix(cdc): expose truthful target execution capabilities#249
seonghobae wants to merge 4 commits into
developfrom
fix/cdc-target-capability-truth-c2511f6

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 10, 2026

Copy link
Copy Markdown
Collaborator

Fixes the Java-SPI portion of #202 without racing the active CdcController writer. The branch was cut from protected develop@c2511f6b9d716ef9ab8de60a91fffd826714a4c5; the independently resolved live protected tip is now develop@942d164ceb7af497bb28a95f842db96429d1bdc4. Exact source head remains f2fd61a50c028535ec30a92d1751e6bf419b1fc4. The intervening protected change (#245) is confined to config-alias sources/resources/tests and does not overlap this PR's four CDC SPI/test paths, but this branch has not been refreshed onto that live base and no evidence transfers across base movement.

Implemented scope

  • CdcTargetConnector exposes immutable machine-readable execution capabilities instead of overloading scaffoldOnly().
  • Kafka truthfully reports a live raw-Debezium Kafka product path with canonical SPI writes still unwired.
  • JDBC replica truthfully reports the live processed_data JDBC-replica path with canonical SPI writes still unwired.
  • A focused regression test covers both live target descriptors.
  • The HTTP /api/cdc/targets and /status projection remains a separate follow-up after the controller writer lane clears; this PR must not claim that portion complete.

Exact observed validation

  • exact source head: f2fd61a50c028535ec30a92d1751e6bf419b1fc4;
  • CI run 31430806262 checked out synthetic merge bd74de4e72a5c1915f2a5b2f94a6093c29ecd7a6 (f2fd61a... merged into historical base c2511f6...), not the literal source head and not the current live protected base;
  • that synthetic checkout passed ETL 275/275 tests, CDC 112/112 tests including CdcTargetCapabilityTest, and gateway 3/3 tests; config-server and eureka-server had no tests;
  • the same CI log explicitly reported JaCoCo Analyzed bundle 'etl-service' with 0 classes followed by All coverage checks have been met, so the observed coverage gate is vacuous rather than qualifying 100% owned-production evidence;
  • formal reviews: none; unresolved review threads: none;
  • exposed security/dependency/SBOM workflow aggregates on this source head were terminal-success, but synthetic-merge execution and repository-wide scanner-completeness gaps remain non-transferable acceptance evidence.

Remaining boundary

Keep Draft. Before any merge, rebuild or non-destructively refresh from the exact current protected ancestry and require literal-source exact-head/current-base validation, non-vacuous owned-production statement/branch coverage, complete applicable vulnerability/dependency scanning, all required security/SBOM/provenance gates, zero valid unresolved findings, and qualifying independent non-author formal approval. Predecessor-head, stale-base, synthetic-merge, status-only, incomplete-scanner, skipped-required, neutral, or author-only evidence is not merge authority.

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8ee36ab9-20ce-4ba6-ae46-c9cd36f4d73a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant