blam
fe3ec5d3c6
* 'master' of github.com:spotify/backstage: (63 commits) packages/cli: add lint rule to avoid cross-package src imports fix(catalog-backend): make location delete work again Add Other component category (#1292) packages/core-api: add initial definition of IdentityApi additional sqli protection build(deps): bump eslint from 7.1.0 to 7.2.0 (#1285) return 204 when there's no response data build(deps-dev): bump @types/codemirror from 0.0.95 to 0.0.96 (#1284) build(deps-dev): bump @types/morgan from 1.9.0 to 1.9.1 (#1287) build(deps): bump chalk from 4.0.0 to 4.1.0 (#1286) catalog: suffix entiy kind typeswith Entity feat(catalog): new kind LocationRef packages/cli: assume browser build if esm output is included packages/backend-common: import winston as namespace plugins/catalog-backend: typecheck migration files plugins/catalog-backend: move migrations to JS with type annotations packages/cli: fix jest module mapper to only match entire module name github/workflows: use env app config to set e2e test port packages/cli: use app.baseUrl to configure dev server packages/config-loader: more docs! ...
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 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 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.