Uploaded image for project: 'Red Hat Developer Hub Bugs'
  1. Red Hat Developer Hub Bugs
  2. RHDHBUGS-2240

Document Breaking Change/Known Issue: existing Operator users with Orchestrator 1.7 require a manual update in their dynamic-plugins ConfigMap

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 1.8.0
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      = Existing Operator users with Orchestator 1.7 require a manual update in their dynamic-plugins ConfigMap

      If you have an existing Operator-backed instance of {product-short} with the Orchestrator, you must update your dynamic-plugins ConfigMap to set the version of the Orchestrator plugins to 1.8.2 once the {product-short} Operator is upgraded to 1.8.
      Otherwise, the {product-short} instance will not be upgraded at all.

      .Example of a dynamic-plugins ConfigMap enabling the Orchestrator plugins in 1.8 for Operator-backed instances
      [source,yaml,subs='+attributes,+quotes']
      ----
      apiVersion: v1
      kind: ConfigMap
      metadata:
        name: dynamic-plugins-rhdh
      data:
        dynamic-plugins.yaml: |
          includes:
            - dynamic-plugins.default.yaml
          plugins:
            - package: "@redhat/backstage-plugin-orchestrator@1.8.2"
              disabled: false
            - package: "@redhat/backstage-plugin-orchestrator-backend-dynamic@1.8.2"
              disabled: false
              dependencies:
                - ref: sonataflow
            - package: "@redhat/backstage-plugin-scaffolder-backend-module-orchestrator-dynamic@1.8.2"
              disabled: false
            - package: "@redhat/backstage-plugin-orchestrator-form-widgets@1.8.2"
              disabled: false
      ----
      Show
      = Existing Operator users with Orchestator 1.7 require a manual update in their dynamic-plugins ConfigMap If you have an existing Operator-backed instance of {product-short} with the Orchestrator, you must update your dynamic-plugins ConfigMap to set the version of the Orchestrator plugins to 1.8.2 once the {product-short} Operator is upgraded to 1.8. Otherwise, the {product-short} instance will not be upgraded at all. .Example of a dynamic-plugins ConfigMap enabling the Orchestrator plugins in 1.8 for Operator-backed instances [source,yaml,subs='+attributes,+quotes'] ---- apiVersion: v1 kind: ConfigMap metadata:   name: dynamic-plugins-rhdh data:   dynamic-plugins.yaml: |     includes:       - dynamic-plugins.default.yaml     plugins:       - package: "@redhat/backstage-plugin-orchestrator@1.8.2"         disabled: false       - package: "@redhat/backstage-plugin-orchestrator-backend-dynamic@1.8.2"         disabled: false         dependencies:           - ref: sonataflow       - package: "@redhat/backstage-plugin-scaffolder-backend-module-orchestrator-dynamic@1.8.2"         disabled: false       - package: "@redhat/backstage-plugin-orchestrator-form-widgets@1.8.2"         disabled: false ----
    • Known Issue
    • Done

      This is a JIRA to document RHDHBUGS-2223 as a known issue/breaking change in 1.8.0

      See RHDHBUGS-2223 for detailed context about this issue, including the reproduction steps.

              Unassigned Unassigned
              rh-ee-asoro Armel Soro
              RHIDP - Install
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: