-
Enhancement
-
Resolution: Unresolved
-
Optional
-
None
-
False
-
False
-
When we have the Debezium connector schema as JSON files deployed after DBZ-4394 we could step by step move backend logic into the Debezium UI frontend and remove the backend eventually.
- instead of loading JSON Schema files from the backend they can be deployed / mounted to the UI
- database connection checks can be moved to Kafka Connect REST extension
- additional backend logic could still go to the Debezium REST extension too
- is blocked by
-
DBZ-4393 Create a Debezium schema generator for Debezium connectors (initial work)
- Closed
-
DBZ-4394 Build and deploy Debezium OpenAPI / JSON Schema definitions with every Debezium release
- Closed
- is related to
-
DBZ-6757 Use new Debezium connect REST extension based URIs
- Resolved
-
DBZ-6761 Implement the "validate connection" endpoints in connector specific Connect REST extensions
- Resolved
-
DBZ-6766 Add ways to configure the Kafka Connect clusters for the UI without a UI backend
- Resolved
-
DBZ-6762 Implement "validate filters" endpoint in connector-specific Connect REST extensions
- Closed
-
DBZ-6763 Add (integration) tests for Oracle connector-specific Debezium Connect REST extension
- Closed
-
DBZ-6764 Move metrics endpoint from UI backend to the Debezium Connect REST extension/s
- Closed
-
DBZ-5361 Endpoint for managing offsets of a specific connector
- Open
-
DBZ-5362 Create a connector offets manipulation UI
- Open
-
DBZ-6765 Update "debezium/connect" and/or "debezium/connect-base" (if applicable) container images for the new Debezium Connect REST extension architecture
- Open
-
DBZ-5320 Manipulate connector offsets tool for Debezium UI
- Open
-
DBZ-5326 Add incremental snapshot configuration to the Debezium UI
- Coding In Progress
- is triggering
-
DBZ-4848 Remove Debezium connector dependencies in Debezium UI
- Closed