test(cdc): replay secure DDL default RED on live develop

[seonghobae]

Rebuilds issue #233 from exact protected develop@609b2901d9b6b7a32c38cbbce4d27ace30dbe042 rather than rewriting stale/diverged PR #286.

This replacement starts as test-only RED at exact source 386f566086d4080ea6975449dc06eecb6df974bc. The focused contract instantiates the real XtrmetlProperties production object and requires both ddlEnabled=false and ddlValidationMode=whitelist.

Fresh protected source still initializes XtrmetlProperties.Replica.ddlValidationMode to none, while issue #233 records application.yml and Spring configuration metadata as whitelist; therefore the current Java object default remains the weaker inconsistent boundary. Historical hosted GREEN on #286 does not transfer because that head diverges from four newer protected commits.

After hosted RED proves none != whitelist on this exact live base, the only intended GREEN is the bounded production initializer change from none to whitelist, preserving explicit operator override semantics, ddlEnabled=false, allowed/blocked prefixes, runtime validation, standalone/MSA behavior and all current security/coverage controls.

Keep Draft through RED -> GREEN. Do not close #286 until unique work is proven preserved on the replacement. Stale/predecessor/synthetic-only/status-only/author-only/queued/pending/skipped-required evidence is not merge authority, and protected integration still requires unchanged exact-head checks plus qualifying independent non-author approval.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 16 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f4959504-e528-4425-9ac1-a72008c588a5

📥 Commits

Reviewing files that changed from the base of the PR and between 609b290 and b6466d4.

📒 Files selected for processing (2)

• cdc-service/src/main/java/com/xtrmetl/cdc/config/XtrmetlProperties.java
• cdc-service/src/test/java/com/xtrmetl/cdc/config/XtrmetlPropertiesSecurityDefaultTest.java

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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