-
Epic
-
Resolution: Unresolved
-
Blocker
-
1.5.0
-
None
-
Onboard new RHDH plugin OCI arifacts to Konflux (1.7)
-
L
-
False
-
-
False
-
-
To Do
-
RHIDP-5362 - Productization / Konflux build pipelines 1.6 (feature)
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
100% To Do, 0% In Progress, 0% Done
-
Release Note Not Required
-
-
EPIC Goal
What are we trying to solve here?
Onboard new RHDH plugin registry container(s) to Konflux, because OSBS is being sunset and Konflux is the way.
Background/Feature Origin
Part of RHIDP-1809, support for external plugins in RHDH from a registry
Why is this important?
We need a continuity plan to continue to be able to build RHDH containers in 2025.
Customers want to be able to install plugins into their RHDH instance, and have the ability to develop their own content internally to their corp. We want to support the idea of having access to multiple registries (community, RH-supported/validated, and private registries too)
User Scenarios
Dependencies (internal and external)
Acceptance Criteria
A quick summary of the actions to get to a plugin catalog for 1.5. Will switch the 
to 
once completed, or add 
if problems arise.
- a list of regexes: which plugins to include in rhidp/rhdh-plugins GL repo - new yaml file in the https://gitlab.cee.redhat.com/rhidp/rhdh-plugin-catalog repo
- for now, https://github.com/davidfestal/rhdh-dynamic-plugin-export-overlays/blob/release-1.4/workspaces/quay/plugins-list.yaml (and ocm)
- in future extend this to include more
- a tool to fetch those plugin sources from the 3+ upstream repos (b/b, bcp, roadiehq?, rhdh-plugins, janus-idp/backstage-plugins) - new sync-midstream.sh script - RHIDP-5769
- a tool to BUILD those plugins with the npx ... dynamic plugin export command based on / wrapper for https://github.com/davidfestal/rhdh-plugin-export-utils/blob/main/export-dynamic/export-dynamic.sh inside a Tekton task (
RHIDP-5415) - a way to pass the output tarball(s) to the existing konflux oci-copy tekton task
- orchestration to avoid rebuilding things things that haven't changed (same SHA in the upstream repo, same SHA in the overlay repo) - need to store up (BCP, rhdh-plugins) /mid (overlay) /downstream (gitlab) SHAs in some set of files we can easily parse to check if a new plugin needs to be build/exported/pushed to quay - RHIDP-5416 (generate pipelines from a template - see also ?)
- clones
-
-
- In Progress
-
