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

[catalog index] DUPLICATE all 'dynamic-plugin/dist/' paths with their matching oci:// references, but disabled

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • 1.9.0
    • 1.9.0
    • Build, Catalog, Marketplace
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Requires a README for 1.9 stating that:
      * you can toggle away from the wrapper to the oci artifact
      * you cannot enable BOTH the wrapper and the oci artifact or your system will crash

      I'm thinking this can go in the TP section of the release notes as we're not 100% confident in our ability to support the oci artifacts in 1.9, but intend to be there in 1.10.
      Show
      Requires a README for 1.9 stating that: * you can toggle away from the wrapper to the oci artifact * you cannot enable BOTH the wrapper and the oci artifact or your system will crash I'm thinking this can go in the TP section of the release notes as we're not 100% confident in our ability to support the oci artifacts in 1.9, but intend to be there in 1.10.
    • Technology Preview
    • Proposed

      Currently in the quay.io/rhdh/plugin-catalog-index1.9-5 container, we see 41 plugins still refer to their wrappers:

       ./dynamic-plugins/dist/backstage-community-plugin-3scale-backend-dynamic
       ./dynamic-plugins/dist/backstage-community-plugin-analytics-provider-segment
       ./dynamic-plugins/dist/backstage-community-plugin-azure-devops
       ./dynamic-plugins/dist/backstage-community-plugin-azure-devops-backend-dynamic
       ./dynamic-plugins/dist/backstage-community-plugin-dynatrace
       ./dynamic-plugins/dist/backstage-community-plugin-github-actions
       ./dynamic-plugins/dist/backstage-community-plugin-github-issues
       ./dynamic-plugins/dist/backstage-community-plugin-jenkins
       ./dynamic-plugins/dist/backstage-community-plugin-jenkins-backend-dynamic
       ./dynamic-plugins/dist/backstage-community-plugin-lighthouse
       ./dynamic-plugins/dist/backstage-community-plugin-tech-radar
       ./dynamic-plugins/dist/backstage-community-plugin-tech-radar-backend-dynamic
       ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-bitbucket-cloud-dynamic
       ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-bitbucket-server-dynamic
       ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-github-dynamic
       ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-github-org-dynamic
       ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-gitlab-dynamic
       ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-gitlab-org-dynamic
       ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-ldap-dynamic
       ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-msgraph-dynamic
       ./dynamic-plugins/dist/backstage-plugin-scaffolder-backend-module-azure-dynamic
       ./dynamic-plugins/dist/backstage-plugin-scaffolder-backend-module-bitbucket-cloud-dynamic
       ./dynamic-plugins/dist/backstage-plugin-scaffolder-backend-module-bitbucket-server-dynamic
       ./dynamic-plugins/dist/backstage-plugin-scaffolder-backend-module-gerrit-dynamic
       ./dynamic-plugins/dist/backstage-plugin-scaffolder-backend-module-github-dynamic
       ./dynamic-plugins/dist/backstage-plugin-scaffolder-backend-module-gitlab-dynamic
       ./dynamic-plugins/dist/immobiliarelabs-backstage-plugin-gitlab
       ./dynamic-plugins/dist/immobiliarelabs-backstage-plugin-gitlab-backend-dynamic
       ./dynamic-plugins/dist/pagerduty-backstage-plugin
       ./dynamic-plugins/dist/pagerduty-backstage-plugin-backend-dynamic
       ./dynamic-plugins/dist/parfuemerie-douglas-scaffolder-backend-module-azure-repositories-dynamic
       ./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-marketplace
       ./dynamic-plugins/dist/roadiehq-backstage-plugin-argo-cd-backend-dynamic
       ./dynamic-plugins/dist/roadiehq-backstage-plugin-datadog
       ./dynamic-plugins/dist/roadiehq-backstage-plugin-github-insights
       ./dynamic-plugins/dist/roadiehq-backstage-plugin-github-pull-requests
       ./dynamic-plugins/dist/roadiehq-backstage-plugin-jira
       ./dynamic-plugins/dist/roadiehq-backstage-plugin-security-insights
       ./dynamic-plugins/dist/roadiehq-scaffolder-backend-argocd-dynamic
       ./dynamic-plugins/dist/roadiehq-scaffolder-backend-module-http-request-dynamic
       ./dynamic-plugins/dist/roadiehq-scaffolder-backend-module-utils-dynamic
      

      Over time, these should be replaced by oci:// references like

      package: oci://quay.io/rhdh/backstage-plugin-notifications:1.9.0--0.5.8!backstage-plugin-notifications
      

      However for 1.9, on the call on 11/26, it was suggested that we include:

      • BOTH wrapper and oci reference in the generated DPDY, but
      • mark all the oci refs DISABLED.

      This will allow a potentially smoother transition from wrapper to oci.

      Requires a README for 1.9 stating that:

      • you can toggle away from the wrapper to the oci artifact
      • you cannot enable BOTH the wrapper and the oci artifact or your system will crash

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              RHIDP - Cope
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: