-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Contribute dynamic frontend plugins upstream based on the new frontend system and module federation enhanced
-
False
-
-
True
-
To Do
-
RHIDP-2035 - Full adoption of dynamic plugins by upstream backstage
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
100% To Do, 0% In Progress, 0% Done
-
-
EPIC Goal
Based on the current state of the upstream new frontend system and experimental module federation support, it should be relatively straightforward to contribute upstream decent support for dynamic frontend plugins based on those 2 upstream features, that would not require anything RHDH-specific.
We should do that, provided there is path forward to migrate RHDH frontend dynamic plugins to this new upstream dynamic frontend plugins feature.
Background/Feature Origin
Even though new frontend system is well advanced, and experimental module federation support are there in the upstream backstage, and they are both enablers of dynamic frontend plugins, upstream is still missing the bits that would enable a seamless experience of dynamic frontend plugins integrated with the already-existing backend dynamic plugins.
We should fix this gap.
Why is this important?
It is important in order to raise awareness about this feature, its value and its ease of use, inside the upstream backstage community.
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>
