paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 34 Packages Projects Releases Wiki Activity

packages: remove backend-legacy package

Browse Source 
Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
This commit is contained in:
Patrik Oldsberg
2025-04-16 11:58:56 +02:00
parent f6bea04286
commit 4d61d24961
22 changed files with 12 additions and 9810 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/conf/reading.md
+5 -9
View File
@@ -141,15 +141,7 @@ from `@backstage/core-plugin-api`.
## Accessing ConfigApi in Backend Plugins
### Old Backend System
In the old backend system plugins, the configuration is passed in via options from the main
backend package. See for example
[packages/backend-legacy/src/plugins/auth.ts](https://github.com/backstage/backstage/blob/244eef851f5aa19f91c7c9b5c12d5df95cf482ca/packages/backend/src/plugins/auth.ts#L23).
### New Backend System
In the new backend system, plugins are able to directly access config through dependencies. You can access config like so,
In the backend system, plugins are able to directly access config through dependencies. You can access config like so,
```ts title="plugins/your-plugin-backend/src/plugin.ts"
export const yourPlugin = createBackendPlugin({
@@ -175,3 +167,7 @@ export const yourPlugin = createBackendPlugin({
},
});
```
### Old Backend System
In the old backend system plugins, the configuration is passed in via options from the main backend package.
docs/features/software-catalog/external-integrations.md
+2 -6
View File
@@ -53,9 +53,7 @@ Some defining traits of entity providers:
### Creating an Entity Provider
The recommended way of instantiating the catalog backend classes is to use the
`CatalogBuilder`, as illustrated in the
[example backend here](https://github.com/backstage/backstage/blob/master/packages/backend-legacy/src/plugins/catalog.ts).
The recommended way of instantiating the catalog backend classes is to use the `CatalogBuilder`.
We will create a new
[`EntityProvider`](https://github.com/backstage/backstage/blob/master/plugins/catalog-node/src/api/provider.ts)
subclass that can be added to this catalog builder.
@@ -637,9 +635,7 @@ does so!
### Creating a Catalog Data Reader Processor
The recommended way of instantiating the catalog backend classes is to use the
`CatalogBuilder`, as illustrated in the
[example backend here](https://github.com/backstage/backstage/blob/master/packages/backend-legacy/src/plugins/catalog.ts).
The recommended way of instantiating the catalog backend classes is to use the `CatalogBuilder`.
We will create a new
[`CatalogProcessor`](https://github.com/backstage/backstage/blob/master/plugins/catalog-node/src/api/processor.ts)
subclass that can be added to this catalog builder.