* '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
...
* feat - add code insights plugin to sample app and plugin to marketplace
* feat - update plugin package version
* Update code-insights.yaml
Add an empty lane on the end of the file.
* Update plugins.ts
Add an empty lane at the end of the file after conflicts resolve.
* Update code-insights.yaml
* Update code-insights.yaml
* Update code-insights.yaml
* feat: update sample app with github insight plugin
* Update github-insights.yaml
* Update EntityPage.tsx
The app-config.yaml file that comes inside the docker image for the
backend contains configuration for the key `scaffolder.azure`. This
automatically enables the use of azure and it is not possible to set its
values to dummy ones because it will fail when it tries to validate
them.
To avoid the backend throwing an exception for this, the charts are
using the "development" mode (via setting NODE_ENV=development).
This means that the app-config.development.yaml file that ships in the
container woud have higher precedence than the app-config.local.yaml
file that the charts tried to create before. For that reason, for now,
they will override the development file.
A better solution would be to ship the docker images with a minimal
app-config.yaml or even without any config. And then have these charts
provide said file.