Purpose

Long-term we need to have the dynamic plugins (frontend and backend) fully adopted in upstream backstage, in order to:

• have our work on dynamic plugins be recognized by the overall Backstage community
• contribute back to the community as RedHat should do,
• reduce to its minimum the amount of code and processes specific to RHDH,
• increase our expertise , presence and contributions in the core backstage,
• further maximize the compatibility of RHDH with upstream backstage, especially in terms of plugin development and support, which would allow an even broader community adopting dynamic plugins and RHDH.

Concrete goals

• Have dynamic plugins support enabled by default, or very easily enabled in the default upstream frontend and backend backstage applications,
• Have dynamic plugin support fully tested by upstream backstage E2E tests,
• Have the dynamic plugins tooling (CLI, as well as dynamic plugin packaging and distribution flow) completely integrated into the upstream Backstage tool-chain and CI flow,
• Have upstream documentation mention the dynamic plugins and how to export, on install them.

Requirements:

• Reach technical agreement with the upstream backstage maintainers and community about the dynamic plugins designs, both in terms of complete and default integration into the upstream frontend and backend applications, and in terms of unified tooling
• Contribute the agreed-on technical approaches to upstream