WIP feat: migration script for dynamic plugins to oci artifacts#1679
Conversation
Signed-off-by: Fortune Ndlovu <fndlovu@redhat.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Signed-off-by: Fortune Ndlovu <fndlovu@redhat.com>
…d-plugins-to-oci-artifacts
Signed-off-by: Fortune Ndlovu <fndlovu@redhat.com>
…d-plugins-to-oci-artifacts
Signed-off-by: Fortune Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune Ndlovu <fndlovu@redhat.com>
…igrated and provide the extraction path forward Signed-off-by: Fortune Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune Ndlovu <fndlovu@redhat.com>
|
closing issue, because Resolution: Won't Fix - Scope Changed After team discussion and analysis, we've decided to close this issue and focus on documentation instead. Decision rationale: Migration is simple enough for users to do manually with clear documentation |
Description
A migration script to help customers transition from bundled plugin wrappers to OCI artifacts. By auto-detecting RHDH installations in OpenShift/Kubernetes clusters, then extracting the catalog index from
quay.io/rhdh/plugin-catalog-index:1.8, and also extracting the bundled plugins in the RHDH container, and then mapping the plugins to their OCI equivalents with specific versions. Lastly, generating a user-friendly migration plan in the logs so the user can do the migration themselves.Which issue(s) does this PR fix or relate to
PR acceptance criteria
How to test changes / Special notes to the reviewer
You need an OCP cluster up and have an rhdh/backstage application created.
./migrate-dynamic-plugins-to-oci.sh