* 'master' of github.com:spotify/backstage: (66 commits)
chore: fix lerna linting
v0.1.1-alpha.25
Add Code Insights plugin to sample app and marketplace (#2833)
Improve main CI build status badge in README (#2866)
Update roadmap: Design System 🚢 (#2858)
github/codecov: switch to informational mode
github/workflows: use the tip of master as the base for comparing PR code coverage
make saml provider path from globalConfig (#2855)
fix(catalog-backend): limit search value lengths
Update project Copyright (#2852)
fix(catalog-backend): actually use modified entity output (default namespace was broken)
remove unnecessary center keyword
Move card header bg to up contrast, fix#2558
Update name of env authentication env vars
Fix feedback from dtuite
Remove chart testing workflow for now
Only lint charts on Pull Requests
Move the k8s deployment docs to its own helm deployment page
Remove line in initdb script that creates backend db
Use app-config.development.yaml to provide configuration instead of local
...
* 'master' of github.com:spotify/backstage: (110 commits)
chore(catalog-backend): removing redudant classes and some functions
chore(deps-dev): bump @types/webpack from 4.41.21 to 4.41.22 (#2765)
move codecov.yml to .github
feat(catalog-backend): add batch concurrency
create-app: remove build step
cli: simplify jest transform ignore regex
feat(catalog-backend): introduce batching, speed up reading and writing of large datasets
Techdocs: add Azure DevOps prepare support (#2748)
feat(techdocs-header): Show breadcrumbs on docs page (#2786)
changesets: add entry for create-app template location fix
create-app: revert to github location type for example templates
fix: make catalog filter work again
Use new url scheme for techdocs
feat: remove LocationProcessor.processEntity
Add Dockerfile for helm chart
feat: use the new UrlReader in the CodeOwnersProcessor
feat: use new UrlReader in PlaceholderProcessor
feat: remove the backstage.io/definition-at-location annotation
Update loud-lamps-visit.md
feat(proxy-backend): limit the forwarded http headers to a safe set
...
* Allow for Kubernetes cluster authentication via google auth
- For the kubernetes and kubernetes-backend plugins
- The kubernetes (front-end) plugin uses the googleAuthApi and goes
through oauth flow to fetch a Google auth token for the current user
and pass that in a request to the kubernetes-backend plugin, which
uses this token as the service account token (and hence as the
authentication token for making K8s API requests).
- Related to https://github.com/spotify/backstage/issues/2552
* Use KubernetesAuthProvider and KubernetesAuthTranslator interfaces for K8s auth
- Implementations of KubernetesAuthProvider decorate the bodies of requests (for
Kubernetes resources) sent from the kubernetes plugin (frontend) to the
kubernetes-backend plugin (backend) with whatever information is
needed for K8s authentication
- Implementations of KubernetesAuthTranslator take the contents of these request
bodies sent from the kubernetes plugin (frontend) to the kubernetes-backend plugin
(backend) and use specific values in the bodies to properly set up tokens for K8s auth
- Start with KubernetesAuthProvider + KubernetesAuthTranslator
implementations for 'serviceAccount' and 'google' as auth providers
- Implementation of what was proposed at https://github.com/spotify/backstage/issues/2552#issuecomment-702545382
- Load in and prepare KubernetesAuthProvider implementations at plugin
startup time via KubernetesAuthProviders API (that essentially stores
or wraps these KubernetesAuthProvider instances)
- Related to https://github.com/spotify/backstage/issues/2552
blam