Uploaded image for project: 'RH Developer Hub Planning'
  1. RH Developer Hub Planning
  2. RHDHPLAN-1001

Remove plugin wrappers in favor of OCI artifacts

Create Doc EPIC from R...Prepare for Y ReleasePrepare for Z ReleasePrepare Test Plan (Y R...XMLWordPrintable

    • 100% To Do, 0% In Progress, 0% Done
    • False
    • Hide

      None

      Show
      None

      Description:

      Provide a quick overview of the goal and key background or context.

      Dynamic plugins are not built into the RHDH container at all, and wrapper projects and mechanism are removed. 

      Benefits/Value:

      What are the benefits or value for our customers if we do this?

      •  

      Acceptance Criteria:

      What must be true for this to be considered complete?

      • All RHDH core plugins have moved away from wrappers, and not built into the RHDH container
      • Plugins are built and delivered as OCI artifacts, available via the non-authenticated Red Ht Ecosystem Catalog at registry.access.redhat.com
      • SBOMs and other security information must be accurate, and not include information at the monorepo level
      • Wrappers are removed

      Out of Scope:

      If there are significant scope constraints, note them so goals and non-goals are clear.

      •  

      Metrics:

      What metrics and telemetry data influence this and either help inform this work, or could help us understand its impact?

      •  

      Dependencies:

      Note any major team or technology dependencies outside of our direct control that we may need to plan around.

      •  

              nickboldt Nick Boldt
              mreid1@redhat.com Matt Reid
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: