EPIC Goal

What are we trying to solve here?

All plugins that we can safely and securely produce with Konflux in 1.9 should be switched from the local path reference to the oci:// reference. More may move over in 1.10 - see followup JIRAs if this is the case.

Before, we have (for example):

  dynamicArtifact: ./dynamic-plugins/dist/backstage-community-plugin-quay

and

package: ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-github-dynamic

or

package: ./dynamic-plugins/dist/backstage-community-plugin-github-actions

that is one of these four patterns:

  dynamicArtifact: ./dynamic-plugins/dist/<plugin-name>
  dynamicArtifact: ./dynamic-plugins/dist/<backend-plugin-name>-dynamic

  package: ./dynamic-plugins/dist/<plugin-name>
  package: ./dynamic-plugins/dist/<backend-plugin-name>dynamic

After migration we'll have this:

• for community CI), for a plugin called red-hat-developer-hub-backstage-plugin-scorecard

    dynamicArtifact: oci://ghcr.io/redhat-developer/rhdh-plugin-export-overlays/red-hat-developer-hub-backstage-plugin-scorecard:bs_1.42.5__1.0.0!red-hat-developer-hub-backstage-plugin-scorecard
  

• for for TP/GA CI builds:

    dynamicArtifact: oci://quay.io/rhdh/red-hat-developer-hub-backstage-plugin-scorecard:1.9.0__1.0.0!red-hat-developer-hub-backstage-plugin-scorecard
  

• or ultimately, for GA releases:

    dynamicArtifact: oci://registry.redhat.io/rhdh/red-hat-developer-hub-backstage-plugin-scorecard@sha256:some-digest-here
  

The addendum of the !<plugin-name> suffix is going away in RHIDP-8960

The work to perform these replacements will be handled by Plugins team, COPE team, Install team, etc.

There will also be a documentation impact here as we update the Dynamic plugins tables to include BOTH the wrapper path and the new oci:// reference, so that end users can migrate their own configurations.

IF REQUIRED the Docs team may reach out to the COPE team to help with table content generation