Uploaded image for project: 'Image Builder'
  1. Image Builder
  2. COMPOSER-2133

Cockpit Composer and Hosted Service Parity

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • None
    • cockpit-composer
    • None
    • Cockpit Composer and Hosted Service Parity
    • False
    • None
    • False
    • Testable
    • To Do

      Goal:

      • The Image Builder hosted service now supports blueprints. There are now no major obstacles for a unified experience between the on-prem Cockpit Composer UI and the hosted service UI.

      Acceptance Criteria:

      • The blueprints table and wizard in Cockpit Composer and the UI should look, feel, and function the same way
      • Cockpit Composer should be updated to use PF5
        • Use deprecated PF4 components when necessary
      • RTKQ should be used for communication with the Weldr API
      • The React component code should be agnostic as to which API is used, so that in the future an easy transition from Weldr API to Cloud API is possible

      Open questions:

      • The hosted service integrates tightly with Insights, the majority of differences between the Cockpit Composer and service UI will come from this
        • We will need to work closely with UX and our POs to determine what to do in these cases, but the primary goal should be to advertise Insights and convert on-prem users to service users if possible.

              jkozol1 Jacob Kozol (Inactive)
              lgarfiel@redhat.com Lucas Garfield
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: