Dynamic plugin support

[serenamarie125]

The problem
Currently users are forced to rebuild/redeploy after adding a new Backstage plugin

Sub-Tasks

• First POC of dynamic frontend plugins: POC of basic scalprum integration
• First RFC about dynamic frontend plugins: [WIP] 💬 RFC: Dynamic microservice plugins for front-end backstage/backstage#17054
• POC of dynamic backend plugins: backstage/backstage@master...davidfestal:backstage:backend-dynamic-plugins
• RFC of dynamic backend plugins: 💬 RFC: Dynamic backend plugins backstage/backstage#18390
• Experimental MVP implementation of dynamic backend plugin support in upstream
  • Allow using external or alternate application templates in the create-app CLI command book#18
  • Propose the backend-plugin-manager to upstream as an experimental package #444
• Add dynamic backend plugin support to the Janus Showcase
  • Add support for the dynamic backend plugins in the showcase application #526
  • Change @janus-idp/cli package build to accommodate dynamic backend plugins backstage-plugins#727
  • Integrate Dynamic Plugins support in helm charts helm-backstage#118
  • Switch static plugins in the showcase backend to dynamic plugins #528
  • Integrate frontend dynamic plugins in the Showcase build + container build #627
  • Allow including files and overriding their content in the list of dynamic plugins  #641
• final attempt at dynamic frontend plugins
  • New frontend POC / RFC compatible with the declarative-integration
  • Change @janus-idp/cli package build to accommodate dynamic frontend plugins backstage-plugins#726
  • Create a DynamicFrontendPluginProvider backend plugin, and integrate it with the frontend dynamic plugins POC #583
  • final implementation of frontend changes in Janus showcase
    • finishing implementation (Add dynamic frontends #659)
    • removing static frontend plugins
    • adding dynamic frontend plugins and configuration ( feat(dynamic-plugins): add wrappers for frontend plugins #683 feat(dynamic-plugins): add imports for plugins supporting both static and dynamic import #699)
    • final integration/polishing
• Robustness
  • Explore how to verify NPM package integrity when npm packing dynamic plugin packages #527
  • Regression: Dynamic frontend plugins configuration is missing responsive settings #727
  • Menu icons from dynamic plugins should use imports #725
  • Config schema aggregation is missing for dynamic plugins #724
  • Missing error handling on dynamic frontend plugins #726

[davidfestal]

Proposed list of related items/tasks:

• First POC of dynamic frontend plugins: POC of basic scalprum integration
• First RFC about dynamic frontend plugins: [WIP] 💬 RFC: Dynamic microservice plugins for front-end backstage/backstage#17054
• POC of dynamic backend plugins: backstage/backstage@master...davidfestal:backstage:backend-dynamic-plugins
• RFC of dynamic backend plugins: 💬 RFC: Dynamic backend plugins backstage/backstage#18390
• Experimental MVP implementation of dynamic backend plugin support in upstream
  • Allow using external or alternate application templates in the create-app CLI command book#18
  • Propose the backend-plugin-manager to upstream as an experimental package #444
  • Propose the export-dynamic-plugin CLI sub-command to upstream, as an experimental sub-command. #445
• New frontend POC / RFC compatible with the declarative-integration
• Let the backend plugin manager drive front-end dynamic plugins serving

[mario-mui]

First POC of dynamic frontend plugins: POC of basic scalprum integration

This link is unavailable. I got 404 @davidfestal

[davidfestal]

First POC of dynamic frontend plugins: POC of basic scalprum integration

This link is unavailable. I got 404 @davidfestal

cc @tumido

[kadel]

It looks like everything here was completed. I'm closing this one.
@davidfestal @davidfestal If something is still missing please let me know, or just reopen this issue.
We should track follow-up work in a separate epic