blam
d721c5c2d2
* 'master' of github.com:spotify/backstage: (52 commits) build(deps): bump @rollup/plugin-json from 4.0.3 to 4.1.0 (#1360) build(deps-dev): bump lerna from 3.22.0 to 3.22.1 (#1390) build(deps): bump graphql from 15.0.0 to 15.1.0 (#1391) core-api: switch IdentityApi id token access to async Adding name of signed in user to greeting message (#1387) Fix CircleCI plugin (#1384) packages/core: update to not use default exports for components auth-backend: clean up naming and types of TokenFactory time handling auth-backend: some review feedback of oidc bits auth-backend: remove logging from DatabaseKeyStore auth-backend: more docs for TokenFactory auth-backend: added tests for TokenFactory and fix keyDuration being ignored auth-backend: added tests for DatabaseKeyStore auth-backend: refactor identity to remove logic from storage layer auth-backend: document identity types auth-backend: refactor identity APIs for forwards compatibility auth-backend: update standalone setup to use service builder and HMR auth-backend: issue user id tokens when signing in with google or github auth-backend: move logger setup out from constructors and use non-reserved fields auth-backend: make key duration configurable ...
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.