fix: migrate Orchestrator plugins to ref:// references (RHIDP-16970)

[Fortune-Ndlovu]

Summary

• Migrate Orchestrator dynamic plugin configuration from registry-specific oci://...:{{inherit}} URLs to stable ref:// plugin names
• Update orchestrator README example to match

Related

• https://redhat.atlassian.net/browse/RHIDP-16970

[github-actions]

Warning

This PR targets main. This repository uses a main/dev branching model.

• All development work (features, docs, dependency updates) should target dev.
• Bug fixes for a supported release should target release-x.y.
• Only maintainer-managed merges and cherry-picks should go into main.

If this is intentional (e.g., a backport or maintainer merge), you can ignore this message.
Otherwise, please retarget your PR to dev.

See the branching strategy for details.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rhdh-qodo-merge]

PR Summary by Qodo

Migrate Orchestrator plugins to stable ref:// references

🐞 Bug fix ⚙️ Configuration changes 📝 Documentation 🕐 Less than 10 minutes

AI Description

• Replace registry-specific Orchestrator plugin URLs with stable ref:// package references.
• Align setup documentation with the corrected dynamic plugin configuration.

Diagram

graph TD
  Docs["README Guidance"] --> Config["Plugin Config"] --> Installer["Plugin Installer"] --> Resolver["Reference Resolver"] --> Frontend["Frontend Plugins"]
  Resolver --> Backend["Backend Plugins"]

Loading

High-Level Assessment

The PR uses the intended stable reference abstraction and keeps runtime configuration and documentation synchronized. Retaining direct OCI URLs was considered but would preserve registry coupling and {{inherit}} tag dependence, so the current approach is preferable.

Files changed (2) +8 / -8

Bug fix (1) +4 / -4

dynamic-plugins.yamlConfigure Orchestrator plugins through ref:// identifiers +4/-4

Configure Orchestrator plugins through ref:// identifiers

• Migrates the Orchestrator frontend, backend, scaffolder module, and form-widget packages from explicit registry URLs to stable references. Existing enablement and Data Index configuration remain unchanged.

orchestrator/configs/dynamic-plugins/dynamic-plugins.yaml

Documentation (1) +4 / -4

README.mdDocument stable Orchestrator plugin references +4/-4

Document stable Orchestrator plugin references

• Replaces all four registry-specific OCI package examples with stable 'ref://' plugin names. The documented setup now matches the runtime configuration.

orchestrator/README.md

[rhdh-qodo-merge]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can group findings by type and pick your Finding display, from Minimal to Full

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[rhdh-qodo-merge]

Important

The /generate_labels command by Qodo is sunsetting on the 1st of October 2026 and will no longer be available. We recommend switching to the latest Qodo review capabilities. Learn more

[rm3l]

This PR should target the dev branch instead: #325 (comment)

[Fortune-Ndlovu]

Closing this PR — the ref:// orchestrator migration for rhdh-local is already merged on dev in #304.

This PR targeted main, which uses the pinned rhdh:1.10.3 image. That version does not resolve ref:// references during plugin install, which is why CI failed with:

InstallException: No integrity hash provided for Package ref://red-hat-developer-hub-backstage-plugin-orchestrator

Per the branching model, development work targets dev (which uses :next images with ref:// support). Changes flow to main at GA via release branches.

RHIDP-16970 rhdh-local scope is covered by #304 on dev.

Signed-off-by: Fortune Ndlovu fndlovu@redhat.com