We aren't supposed to import from '.' or '../..' etc; point to the actual node being imported instead. I did allow e.g. '../../bigfolder' however. Going all the way to the individual file could be done too, but is a matter of taste perhaps.
Also ran Organize Imports on all the touched files :)
No changeset since there are no functional changes at all - only the imports changed
Signed-off-by: Fredrik Adelöw <freben@gmail.com>
* 'master' of github.com:spotify/backstage: (139 commits)
Cleanup
Update PinButton.test.tsx
feat: update github insights plugin version (#2973)
Ignore IntelliJ *.iml files (#2971)
chore(deps): bump rollup-plugin-dts from 1.4.11 to 1.4.13
fix the plugin card on plugins page
align 'Add to Marketplace' button on plugins page
fix the PluginGrid on mobiles sizes
use getBy query instead of queryBy when asserting for elements present in document (#2951)
Update PinButton.tsx
Add test case for Progress component (#2953)
fix the styling of footer copy on mobile
add changeset
handle the case where no entities are available to show
core-api: work around issue with ApiRef export const declarations
core-api: move utility api system implementation into apis/system
Update docs regarding npm config ignore-scripts flag
Another try
Fix Core Features configuration id (#2948)
Fix test?
...
* '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
Travis Truman