Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-4395

Remove the Debezium UI backend - move logic to the Debezium UI frontend

    XMLWordPrintable

Details

    Description

      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

      Attachments

        Issue Links

          is blocked by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) DBZ-4393 Create a Debezium schema generator for Debezium connectors (initial work)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) DBZ-4394 Build and deploy Debezium OpenAPI / JSON Schema definitions with every Debezium release

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Sub-task - The sub-task of the issue DBZ-6757 Use new Debezium connect REST extension based URIs

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Sub-task - The sub-task of the issue DBZ-6761 Implement the "validate connection" endpoints in connector specific Connect REST extensions

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Sub-task - The sub-task of the issue DBZ-6766 Add ways to configure the Kafka Connect clusters for the UI without a UI backend

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Sub-task - The sub-task of the issue DBZ-6762 Implement "validate filters" endpoint in connector-specific Connect REST extensions

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Sub-task - The sub-task of the issue DBZ-6763 Add (integration) tests for Oracle connector-specific Debezium Connect REST extension

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Sub-task - The sub-task of the issue DBZ-6764 Move metrics endpoint from UI backend to the Debezium Connect REST extension/s

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Sub-task - The sub-task of the issue DBZ-5361 Endpoint for managing offsets of a specific connector

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Sub-task - The sub-task of the issue DBZ-5362 Create a connector offets manipulation UI

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Sub-task - The sub-task of the issue DBZ-6765 Update "debezium/connect" and/or "debezium/connect-base" (if applicable) container images for the new Debezium Connect REST extension architecture

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) DBZ-5320 Manipulate connector offsets tool for Debezium UI

          • Critical - To be worked on immediately following BLOCKER issues.
          • Open

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) DBZ-5326 Add incremental snapshot configuration to the Debezium UI

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Coding In Progress
          is triggering

          Task - Represents a small unit of work that is not end-user facing. DBZ-4848 Remove Debezium connector dependencies in Debezium UI

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          1.
          		 Implement the "validate connection" endpoints in connector specific Connect REST extensions Sub-task Resolved Major René Kerner
          2.
          		 Add (integration) tests for Oracle connector-specific Debezium Connect REST extension Sub-task Closed Major René Kerner
          3.
          		 Use new Debezium connect REST extension based URIs Sub-task Resolved Major Indra Shukla
          4.
          		 Move metrics endpoint from UI backend to the Debezium Connect REST extension/s Sub-task Closed Major Anisha Mohanty
          5.
          		 Implement "validate filters" endpoint in connector-specific Connect REST extensions Sub-task Closed Major René Kerner
          6.
          		 Add ways to configure the Kafka Connect clusters for the UI without a UI backend Sub-task Resolved Major Indra Shukla
          7.
          		 Update "debezium/connect" and/or "debezium/connect-base" (if applicable) container images for the new Debezium Connect REST extension architecture Sub-task Open Major Unassigned
          8.
          		 Evaluate switching to `MongoDbDatabaseProvider` for Mongo DB Connect REST extension tests Sub-task Open Major Unassigned
          9.
          		 Make MongoDb Testcontainers (ReplicaSet, Provider, etc) not managing the Docker network at all Sub-task Open Major Unassigned
          10.
          		 Split up / refactor `RestExtensionTestInfrastructure` class, which idea is to provice a homogeneous test stack / infrastructure for REST extension tests Sub-task Open Major Unassigned
          11.
          		 Evaluate ifand how a common test class for connector-specific tests makes sense (similar to IncrementalSnapshotIT) Sub-task Open Major Unassigned
          12.
          		 Evaluate if and how a ServiceLoader based implementation can be used to replace mapping of connector class names to identifiers / connector type names for the API / UI Sub-task Open Major Unassigned
          13.
          		 Enable CORS for accessing the rest extension APIs end points via UI Sub-task Coding In Progress Major René Kerner

          Activity

            People

              Unassigned Unassigned
              rk3rn3r René Kerner
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: