-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Explore if RHDH dynamic plugins support is compatible with the distributed plugins deployment scheme
-
M
-
False
-
-
False
-
RHDHPLAN-241Explore if RHDH dynamic plugins support is compatible with the distributed plugins deployment scheme
-
To Do
-
RHDHPLAN-241 - Explore if RHDH dynamic plugins support is compatible with the distributed plugins deployment scheme
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
50% To Do, 0% In Progress, 50% Done
-
-
EPIC Goal
Explore, through some Spike, whether RHDH dynamic plugins support is compatible with the distributed plugins deployment scheme.
We should include the upcoming support of new-frontend plugins based on the upstream module federation feature.
Outcome of this EPIC should be :
- a list of pain points, blocking points or limitations, along with related required implementation tasks,
- if no blocking points, a blog post to explain how to do it, along with constraints and specific settings.
Background/Feature Origin
Why is this important?
User Scenarios
Dependencies (internal and external)
Acceptance Criteria
Release Enablement/Demo - Provide necessary release enablement details
and documents
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Playwright: <link or reference to playwright>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>
