What problem does it solve?
Managing TiCDC changefeeds across different operational interfaces (CLI, OpenAPI v2) is error-prone due to inconsistent parameter formats, risky unvalidated update workflows that can cause data loss or duplicate change delivery, and the need to manually translate between CLI flags, TOML configuration files, and JSON API payloads.
Core Features & Use Cases
- Cross-interface changefeed operations: Create, list, query, pause, resume, and remove TiCDC changefeeds via either the cdc cli or OpenAPI v2 API to match your environment and tooling preferences.
- Config and payload translation: Convert seamlessly between CLI flags, TOML changefeed configs, and OpenAPI v2 JSON payloads to eliminate manual formatting errors.
- Safe update guardrails: Follow a validated pause → update → resume lifecycle to prevent data loss or duplicate delivery when modifying sink URIs, target timestamps, or replica configurations.
- Real-world use case: If you need to migrate a TiCDC changefeed's downstream sink from a MySQL database to a Kafka cluster without data loss, use this skill to execute the safe update workflow and verify the change across both CLI and API interfaces.
Quick Start
Use the manage-ticdc-changefeeds skill to update the sink URI of your existing TiCDC changefeed to a new Kafka endpoint, following the safe pause-update-resume workflow to avoid data loss or duplicate change delivery.
