Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-5309

Migrate or remove dependencies to @janus-idp/shared-react package

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • 1.8.0
    • None
    • Documentation, UI
    • None
    • Migrate or remove dependencies to @janus-idp/shared-react package
    • M
    • False
    • Hide

      None

      Show
      None
    • False
    • RHIDP-3227Sunset Janus IDP
    • In Progress
    • RHIDP-3227 - Sunset Janus IDP
    • QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      ## Breaking Change

      With RHDH 1.8 the **Argo CD**, **Tekton** and **Topology** plugin requires now the **Kubernetes Frontend** and Kubernetes Backend plugin. Before these plugins depends only on the Kubernetes Backend plugin.

      Customers which has enabled one of these three plugins but didn't enabled the Kubernetes Frontend plugin so far needs to enable this dynamic plugin:

      ```yaml
      global:
        dynamic:
          plugins:
            # With RHDH 1.8 the Kubernetes frontend is required for the Argo CD,
            # Tekton or Topology plugin.
            - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes
              disabled: false
            - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes-backend-dynamic
              disabled: false
      ```

      The Kubernetes Frontend plugin shows automatically a "Kubernetes" tab for Software Catalog entities with the annotation `backstage.io/kubernetes-id` or `backstage.io/kubernetes-namespace`. Customers that want ensure that there is no "Kubernetes" tab available in the Software Catalog can disable this feature with this dynamic plugin configuration:

      ```yaml
      global:
        dynamic:
          plugins:
            # With RHDH 1.8 the Kubernetes frontend is required for the Argo CD,
            # Tekton or Topology plugin.
            - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes
              disabled: false
              pluginConfig:
                dynamicPlugins:
                  frontend:
                    backstage.plugin-kubernetes:
                      mountPoints: []
            - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes-backend-dynamic
              disabled: false
      ```
      Show
      ## Breaking Change With RHDH 1.8 the **Argo CD**, **Tekton** and **Topology** plugin requires now the **Kubernetes Frontend** and Kubernetes Backend plugin. Before these plugins depends only on the Kubernetes Backend plugin. Customers which has enabled one of these three plugins but didn't enabled the Kubernetes Frontend plugin so far needs to enable this dynamic plugin: ```yaml global:   dynamic:     plugins:       # With RHDH 1.8 the Kubernetes frontend is required for the Argo CD,       # Tekton or Topology plugin.       - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes         disabled: false       - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes-backend-dynamic         disabled: false ``` The Kubernetes Frontend plugin shows automatically a "Kubernetes" tab for Software Catalog entities with the annotation `backstage.io/kubernetes-id` or `backstage.io/kubernetes-namespace`. Customers that want ensure that there is no "Kubernetes" tab available in the Software Catalog can disable this feature with this dynamic plugin configuration: ```yaml global:   dynamic:     plugins:       # With RHDH 1.8 the Kubernetes frontend is required for the Argo CD,       # Tekton or Topology plugin.       - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes         disabled: false         pluginConfig:           dynamicPlugins:             frontend:               backstage.plugin-kubernetes:                 mountPoints: []       - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes-backend-dynamic         disabled: false ```
    • Unspecified Release Note Type - Unknown

      EPIC Goal

      We deprecated the complete https://github.com/janus-idp/backstage-plugins repository and that should also include the package @janus-idp/shared-react package from https://github.com/janus-idp/backstage-plugins/tree/main/plugins/shared-react

      This package includes common and pipelines (Tekton) related components and utilities.

      We should rethink/reevaluate which components.

      • We can/want duplicate into the plugins itself (if it's just a few lines of code, for example, or esp. when it's used by just one plugin )
      • of if we want to migrate the code to a new / another shared package like:
        1. A new BCP or rhdh-plugins workspace with just the shared code?
        2. Can it live as a shared package in one workspace that another workspace is using via npm
        3. Should we move code to https://github.com/redhat-developer/aonic-ui (maybe a good candidate for the pipelines code since there is already a pipelines package)

      Why is this important?

      We want to deprecate and remove all Janus-IDP references.

      User Scenarios

      None

      Dependencies (internal and external)

      1. Technically none
      2. Some plugins are now owned by the RHTAP team

      Acceptance Criteria

      There is no dependency from any BCP or rhdh-plugin code to @janus-idp/shared-react

              dsantra12 Debsmita Santra
              cjerolim Christoph Jerolimov
              RHIDP - Frontend Plugins & UI
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: