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

Prepare Debezium UI to participate in upstream releases

    XMLWordPrintable

Details

    Description

      A few things which should be addressed:

      • Rename the repository (no PoC any longer)
      • Decide on delivery artifact:
        • go with the separate container image we already have and publish this as part of the release process (my preference for now)
        • add the UI to the debezium/connect image
        • release as separate archive, just containing the Quarkus application
      • Consider UI in the debezium-examples repo; either as part of the tutorial set-up, or as a separate example

      Attachments

        Issue Links

          is cloned by

          Task - A task that needs to be done. DBZ-3169 Debezium UI participating in upstream releases -- follow-up

          • 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

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: DBZ

              People

                mdrillin1@redhat.com Mark Drilling
                gunnar.morling Gunnar Morling
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: