Goal

To be able to flexible configure and validate dynamic plugins and assign them to Backstage instance.

Background/Feature Origin

For the time being the role of Operator is only to mount configured dynamic-plugin ConfigMap to Backstage container where script processes it. The disadvantages of current approach is that:

• volumes with plugins binaries are hardcoded
• default dynamic plugins configuration is hardcoded in the image as well, so it can not be changed without Backstage image rebuild
• In case if config is incorrect, installation is failed on later stage in container, no chances for preflight validation

Why is this important?{}

In a context of Marketplace we need to be able to configure and better validate Backstage (RHDH) instance (CR).

User Scenarios

User

• User wants to create/update and configures RHDH instance on UI
• User wants to edit the list of plugins for RHDH instance
• UI shows the list of available plugins
• User picks the plugin, modify its configuration if needed and adds to CR/associated ConfigMap

Admin

• Admin user wants to provide/change default dynamic plugins independently from deployment