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

package metadata source code URL and backstage.io/source-location url should not point at wrappers

      the workspaces/<workspacename>/metadata/*.yaml files for the PACKAGES point to wrapper URLs instead of to the overlays repo or the upstream repo from which we're fetching, overlaying, and exporting as a dynamic plugin.

      For example:

          - title: Source Code
            url: https://github.com/redhat-developer/rhdh/tree/main/dynamic-plugins/wrappers/backstage-community-plugin-topology
        annotations:
          backstage.io/source-location: url
            https://github.com/redhat-developer/rhdh/tree/main/dynamic-plugins/wrappers/backstage-community-plugin-topology
      

      Once we have committed to switching these to OCI artifacts, those links and annotations should point to the equivalent path in the overlays repo, eg., https://github.com/redhat-developer/rhdh-plugin-export-overlays/tree/main/workspaces/topology

      Meanwhile the PLUGIN metadata in https://github.com/redhat-developer/rhdh-plugin-export-overlays/blob/main/catalog-entities/marketplace/plugins/topology.yaml#L25 points to the upstream repo, eg.

          - title: Source Code
            url: https://github.com/backstage/community-plugins/tree/main/workspaces/topology/plugins/topology
      

      So... we should decide which URL makes more sense for sources and use that everywhere for consistency.

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

                Created:
                Updated: