Skip to content

Latest commit

 

History

History
52 lines (41 loc) · 2.25 KB

File metadata and controls

52 lines (41 loc) · 2.25 KB

Preinstalled dynamic plugins

{product} is preinstalled with a selection of dynamic plugins.

The following 15 preinstalled dynamic plugins are enabled by default:

  • @backstage-community/plugin-analytics-provider-segment

  • @backstage-community/plugin-scaffolder-backend-module-regex

  • @backstage/plugin-techdocs-backend

  • @backstage/plugin-techdocs-module-addons-contrib

  • @backstage/plugin-techdocs

  • @red-hat-developer-hub/backstage-plugin-adoption-insights-backend

  • @red-hat-developer-hub/backstage-plugin-adoption-insights

  • @red-hat-developer-hub/backstage-plugin-analytics-module-adoption-insights

  • @red-hat-developer-hub/backstage-plugin-catalog-backend-module-extensions

  • @red-hat-developer-hub/backstage-plugin-dynamic-home-page

  • @red-hat-developer-hub/backstage-plugin-extensions-backend

  • @red-hat-developer-hub/backstage-plugin-extensions

  • @red-hat-developer-hub/backstage-plugin-global-floating-action-button

  • @red-hat-developer-hub/backstage-plugin-global-header

  • @red-hat-developer-hub/backstage-plugin-quickstart

The dynamic plugins that require custom configuration are disabled by default.

Upon application startup, for each plugin that is disabled by default, the install-dynamic-plugins init container within the {product-short} pod log displays a message similar to the following:

======= Skipping disabled dynamic plugin ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-github-dynamic

To enable this plugin, add a package with the same name to the Helm chart and change the value in the disabled field to false. For example:

global:
  dynamic:
    includes:
      - dynamic-plugins.default.yaml
    plugins:
      - package: ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-github-dynamic
        disabled: false
Note
The default configuration for a plugin is extracted from the dynamic-plugins.default.yaml file, however, you can use a pluginConfig entry to override the default configuration.