Files
backstage/plugins
Marvin9 f05e4b9608 re: make consistent environment variables
GITHUB_PRIVATE_TOKEN & GITHUB_ACCESS_TOKEN => GITHUB_TOKEN
GITLAB_PRIVATE_TOKEN, GITLAB_ACCESS_TOKEN & SCAFFOLDER_GITLAB_PRIVATE_TOKEN => GITLAB_TOKEN
AZURE_PRIVATE_TOKEN => AZURE_TOKEN
GHE_PRIVATE_TOKEN => GHE_TOKEN
2020-10-08 10:34:06 +05:30
..
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-06 08:35:44 +01:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-06 08:35:44 +01:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00
2020-10-05 15:45:33 +02:00

Plugins

Backstage is a single-page application composed of a set of plugins.

Our goal for the plugin ecosystem is that the definition of a plugin is flexible enough to allow you to expose pretty much any kind of infrastructure or software development tool as a plugin in Backstage. By following strong design guidelines we ensure the overall user experience stays consistent between plugins.

plugin

Creating a plugin

To create a plugin, follow the steps outlined here.

Suggesting a plugin

If you start developing a plugin that you aim to release as open source, we suggest that you create a new Issue. This helps the community know what plugins are in development.

You can also use this process if you have an idea for a good plugin but you hope that someone else will pick up the work.