-
Task
-
Resolution: Unresolved
-
Critical
-
None
-
2
-
True
-
-
False
-
-
Removed Functionality
-
Proposed
-
-
For the plugins which we have downgraded the support level from TP to Community, it seems to make sense to simply REMOVE those wrappers in 1.9 in favour of the oci:// refs to ghcr.io
Asking because this would:
- move us toward the "no wrappers" state we want to get to in 1.9 / 1.10
- make it easier to onboard the RHDH repo to the latest BS 1.45.z without worrying about so many wrappers/patches
If we can get onto 1.45.z sooner, we can unlock the work being done downstream by plugin owners (rhdh-plugins, BCP) to move to 1.45 too, which will accelerate getting things built in Konflux, as I'll see the problems sooner
List of community plugins in 1.9: https://issues.redhat.com/secure/attachment/13563634/community-wrappers.txt (see parent issue RHIDP-10847)
NOTE:
- Of those 32 plugins, 3 are considered "part of the core" from Ben's sheet:
- bitbucket-cloud-catalog-integration
- bitbucket-server-catalog-integration
- roadie-scaffolder-util-actions
so... those three might remain as wrappers a bit longer ![]()
If we have agreement from all stakeholders the DoD here would be to:
delete community-supported wrappers from the rhdh repo
update the DPDY file and catalog entities files for those same plugins to refer to their oci://ghcr.io refs instead - RHIDP-9955
provide detailed doc about which plugins have moved in a table showing the before/after plugin reference - RHIDP-9744
- is related to
-
RHIDP-9420 [Plugins] Replace local file wrapper paths with oci:// references in dynamic-plugins.default.yaml and catalog-entities
-
- New
-
-
RHIDP-9525 Relabel Community Supported plugins that were moved to Technology Preview
-
- In Progress
-
-
RHIDP-9955 [Plugins] Replace local file wrapper paths with oci:// references in dynamic-plugins.default.yaml and catalog-entities for community support plugins
-
- Refinement
-