Task

Currently, the only supported OCI artifacts in RHEC are the Orchestrator plugins. In 1.10, we are going to have Lightspeed and ROS (and possibly many more if we can resolve the SBOM issues).

In the supported plugins table, the Orchestrator plugins have the full path, including the SHA256 digest. e.g.

oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets@sha256:692afe6b19aabf47a4ea02177d7637083db0adfeb7240b5321d64ee39d5cd040

In 1.9, there were sync issues. e.g this PR was cherrypicked but the digests were not updated. Discussed this with nickboldtand we agreed that a more generic <tag> suffix with instructions on how to determine the tag would be the best way forward. It's also consistent with the formats in the other tables.

We have instructions to determine the digests for Community plugins in the overlays repo but we will need to figure out instructions for RHEC plugins

Update: See March 6 Slack Discussion with Tomas for more perspectives:

Customers will need to rely on dynamic plugin reference tables for configuration.  They can't be expected to compute the tag and then figure out the SHA256 digest.  Copy and paste from the table would be preferred.  

Background

Dependencies and Blockers

QE impacted work
Documentation impacted work 

Acceptance Criteria (TBD)

• updated the rhdh-supported-plugins.sh script to remove sha256 digests and replace with <tag>
• write up instructions for customers to determine these digests using CLI, UI, (and REST API?).  Note, officially supported plugins should be available in registry.redhat.io.