v0.21 lane: migrate/kc CLI
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 18/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- go, kafka
- Área
- cli, data-engineering
Línea de trabajo
Start with the parent issue #3002, ROADMAP.md, and the prior design document at docs/design-documents/20260722-debezium-compete-roadmap.md. The issue requires a new CLI contract, report schema, and error codes before implementation, with mappings, tests, and documentation spanning several connector types. Done means the listed commands, compatibility reporting, per-connector tests, guides, and other definition-of-done items are complete.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Roadmap item: v0.21: migrate/kc CLI. Parent: #3002. Plan: ROADMAP.md (#2945).
Goal
Ship conduit migrate kafka-connect v1 plus conduit kc lint and conduit kc diff. migrate reads Kafka Connect worker and connector configs and emits Conduit pipeline config and a compatibility report. It never silently drops config it cannot translate. It covers exactly the connectors certified in this release: Debezium Postgres and MySQL, JDBC source and sink, S3 sink, Elasticsearch/OpenSearch sink, Kafka to Kafka. kc lint includes KIP-1188 override risks; kc diff diffs connector-config versions and checks schema compatibility against the registry.
Risk tier
Tier 2 (CLI). The compatibility report schema and error codes are public contracts.
Definition of done
- Every command supports
--json; every error has a stable code, the failing config path and a suggested fix (CLAUDE.md). - The report lists every input key as translated, mapped with a note, or untranslatable. A test fails if any key is unaccounted for.
- Unit tests per connector mapping; golden-file tests for the emitted pipelines.
- Docs: the 'Migrating from Kafka Connect' concept mapping (worker to instance, task to pipeline, SMT to processor, converter to schema) and per-connector guides for the v0.21 set;
llms.txtupdated with the docs. - Concept mapping page states plainly that only Postgres resumes from imported offsets in v0.21; every other migration re-snapshots.
- Tests: unit and integration green with the race detector; every bug fix ships with the test that would have caught it.
- Docs move with the code:
conduit.iodocs source andllms.txtupdated, changelog entry. - Lint clean; PR descriptions carry the roadmap item, risk tier, adversarial self-review and, for Tier 1, a failure-mode analysis.
Linked issues and PRs
Progress (merged work, checked 2026-10-14): design merged in #3026 (migrate kafka-connect v1, kc lint, kc diff) and #3029 (the migrate surface for Debezium Postgres offset import). No implementation merged yet, so no box is met.
No existing issue; this issue is the tracker. SMT pack (v0.22) is #2960 and is out of scope here. Prior design context: docs/design-documents/20260722-debezium-compete-roadmap.md.
Dependencies on other lanes
Defines the connector set that migrate emits, so every certification lane depends on its mapping tables. Depends on the migration harness lane for the diff-based tests. Offset import for Postgres is wired in through the Postgres lane, and the Debezium output mode through #3032.
Design document
Required: a CLI contract, a report schema and error codes. Design doc in docs/design-documents/ with problem, constraints, at least two alternatives, failure modes (malformed input, unknown connector classes, secrets in configs), upgrade/rollback and observability.
Owner
Agent lane, DeVaris sign-off for Tier 1.
🤖 Generated with Claude Code
- Lenguaje dominante
- Go
- Estrellas
- 614
- Forks
- 66
- Merge medio
- 1 d 6 min
- PR fusionados (30 d)
- 152
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ConduitIO/conduit
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
housekeeping
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 42/100
ConduitIO/conduit#3172 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de ConduitIO/conduit
Issues similares
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:session-state issue-rating: 🦞 diamond lobster no-stale P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
openclaw/wacli#503 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 81/100
apache/rocketmq-dashboard#6895 ·
Los mantenedores suelen responder en 3 días
-
agent-butler-finding chore
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
jordansmall/spindrift#5466 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
open-telemetry/opentelemetry-go-compile-instrumentation#1507 ·
Los mantenedores suelen responder en 3 días
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 87/100
777genius/agent-notifications#490 ·
Los mantenedores suelen responder en 1 día