Additional backends for Debezium UI other than Kafka [DBZ-5751]
Open
component/core-library
migrated-from-jira
type/enhancement
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-5751](https://issues.redhat.com/browse/DBZ-5751)
Configuring Debezium Connectors via Debezium UI when using other Backend than Kafka to pass the configuration to Debezium
Currently Kafka is coupled with Debezium UI. We would like to allow for additional bridges between the output of Debezium UI and the configuration profile passed to Debezium
h2. Implementation ideas (optional)
Contributor guide
Research direction
The issue concerns Debezium UI and its current Kafka coupling, but names no files, tests, or entry points. Start by locating the UI's configuration path and how Kafka currently passes connector profiles; done means an additional non-Kafka backend or bridge can pass the configuration to Debezium.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100