Dynamic plugins

Red Hat Developer Hub implements a dynamic plugin system. You can install, configure, and load plugins at runtime without changing or rebuilding the application. You only need a restart. You can load these plugins from NPM, tarballs, or OCI compliant container images.

With dynamic plugins, instead of modifying the Backstage application itself, you create a dynamic-plugins.yaml file to specify the plugins that Red Hat Developer Hub will install and enable at startup. For example, the following configuration loads a plugin named plugin-name, which is stored in a Quay.io container image at quay.io/account-name/image-name:

dynamic-plugins.yaml fragment

plugins:
  - package: oci://quay.io/account-name/image-name:tag
    disabled: false
    pluginConfig: {}
Note
In RHDH 2.1, bundled Dynamic Plugin Wrappers are removed from the RHDH image. Plugins are consumed as OCI artifacts only. A plugin that uses a local wrapper path, such as package: ./dynamic-plugins/dist/<plugin-name>, no longer resolves. If you are upgrading from an earlier release, replace each local wrapper path with an OCI reference.