• L
    • False
    • Hide

      None

      Show
      None
    • False
    • RHDHPLAN-192Base RHDH frontend on the upstream new frontend system
    • 33% To Do, 67% In Progress, 0% Done

      Feature Overview (aka. Goal Summary)

      • Integrate the upstream Backstage new frontend system.
      • The new frontend system should be able to load dynamic plugins that support it.
      • The goal is to get the new frontend system into customer and engineering hands as soon as possible.
      • Provides a non-invasive integration into the existing RHDH builds.
      • Enables alignment of dynamic plugin functionality with upstream design.
      • The abstraction layer to load plugins implemented in the old frontend system can be added at a later time.

      Goals (aka. expected user outcomes)

      • Validate compatibility of RHDH dynamic plugin mechanism with upstream architecture.
      • Provide a migration path to new frontend system.

      Requirements (aka. Acceptance Criteria):

      • RHDH frontend application can be built on the upstream Backstage new frontend system.
        • app-next, the new frontend system should be available in RHDH builds.
        • Using app-next should be possible by setting a configuration flag or an environment variable.

      Out of Scope (Optional)

      • abstraction layer for plugins that use the old system.

      Customer Considerations (Optional)

      Documentation Considerations

              stlewis_2 Stan Lewis
              rh-ee-mhild Marcel Hild
              RHIDP - Plugins
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: