Merge branch 'ryanvazquez-patch-1' of github.com:backstage/backstage into ryanvazquez-patch-1

2020-11-19 15:08:27 -05:00
parent 8e6728e254 aa22f839ca
commit 0045eefa8e
123 changed files with 964 additions and 594 deletions
@@ -1,13 +0,0 @@
---
-'@backstage/backend-common': patch
-'@backstage/cli': patch
-'@backstage/core': patch
-'@backstage/plugin-cost-insights': patch
-'@backstage/plugin-lighthouse': patch
-'@backstage/plugin-rollbar': patch
-'@backstage/plugin-sentry': patch
-'@backstage/plugin-techdocs': patch
-'@backstage/plugin-user-settings': patch
---
-
-Added configuration schema
@@ -1,27 +0,0 @@
---
-'@backstage/backend-common': minor
-'@backstage/cli': minor
-'@backstage/config-loader': minor
---
-
-Added support for loading and validating configuration schemas, as well as declaring config visibility through schemas.
-
-The new `loadConfigSchema` function exported by `@backstage/config-loader` allows for the collection and merging of configuration schemas from all nearby dependencies of the project.
-
-A configuration schema is declared using the `https://backstage.io/schema/config-v1` JSON Schema meta schema, which is based on draft07. The only difference to the draft07 schema is the custom `visibility` keyword, which is used to indicate whether the given config value should be visible in the frontend or not. The possible values are `frontend`, `backend`, and `secret`, where `backend` is the default. A visibility of `secret` has the same scope at runtime, but it will be treated with more care in certain contexts, and defining both `frontend` and `secret` for the same value in two different schemas will result in an error during schema merging.
-
-Packages that wish to contribute configuration schema should declare it in a root `"configSchema"` field in `package.json`. The field can either contain an inlined JSON schema, or a relative path to a schema file. Schema files can be in either `.json` or `.d.ts` format.
-
-TypeScript configuration schema files should export a single `Config` type, for example:
-
-```ts
-export interface Config {
-  app: {
-    /**
-     * Frontend root URL
-     * @visibility frontend
-     */
-    baseUrl: string;
-  };
-}
-```
@@ -1,7 +0,0 @@
---
-'@backstage/plugin-app-backend': minor
---
-
-Use new config schema support to automatically inject config with frontend visibility, in addition to the existing env schema injection.
-
-This removes the confusing behavior where configuration was only injected into the app at build time. Any runtime configuration (except for environment config) in the backend used to only apply to the backend itself, and not be injected into the frontend.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-cost-insights': patch
---
-
-remove excessive margin from cost overview banner
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-cost-insights': minor
---
-
-remove cost insights currency feature flag
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-cost-insights': patch
---
-
-Fix savings/excess display calculation
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-catalog-backend': patch
---
-
-An entity A, that exists in the catalog, can no longer be overwritten by registering a different location that also tries to supply an entity with the same kind+namespace+name. Writes of that new entity will instead be rejected with a log message similar to `Rejecting write of entity Component:default/artist-lookup from file:/Users/freben/dev/github/backstage/packages/catalog-model/examples/components/artist-lookup-component.yaml because entity existed from github:https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/components/artist-lookup-component.yaml`
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Support specifying listen host/port for frontend
@@ -1,6 +0,0 @@
---
-'@backstage/backend-common': patch
-'@backstage/integration': patch
---
-
-Added the integration package
@@ -1,5 +0,0 @@
---
-'@backstage/backend-common': minor
---
-
-Refactored UrlReader.readTree to be required and accept (url, options)
@@ -1,5 +0,0 @@
---
-'@backstage/catalog-client': minor
---
-
-Changed the getEntities interface to (1) nest parameters in an object, (2) support field selection, and (3) return an object with an items field for future extension
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-scaffolder-backend': patch
---
-
-Extracted pushToRemote function for reuse between publishers