blam
f60b02bec4
* 'master' of github.com:backstage/backstage: (23 commits) cli: fix windows tests Introduce slight bias towards positive trend in cost insights mock data core-api: rename BackstageRoutes to FlatRoutes Update plugins/catalog/src/hooks/useEntity.ts Fix parameter name in docstring for duration#inclusiveStartDateOf Adjust test Add changeset fix: token expiration in s, not ms Create loud-days-breathe.md Create polite-glasses-occur.md dev-utils: add a small label with the entity name to EntityGridItems dev-utils: add EntityGridItem for easily displaying various entity cards dev-utils: use dev index module as root for hot reloading dev-utils: add .registerPage for use with extensions catalog: rename EntityProvider to EntityLoaderProvider, and add new EntityProvider reduce close timeout to 100 ms changeset: add changeset for core-api RouteRef deprecations core-api: use typescript workaround for using private constructor instead of a runtime one core-api: deprecate RouteRef path and remove deprecated createSubRoute delay window close by 200 ms ...
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.
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.