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

Update docs/backend-system/building-plugins-and-modules/08-migrating.md

Browse Source 
Signed-off-by: Johan Haals <johan.haals@gmail.com>

Co-authored-by: Fredrik Adelöw <freben@gmail.com>
Signed-off-by: Johan Haals <johan@haals.se>
This commit is contained in:
Johan Haals
2023-01-18 14:55:39 +01:00
committed by GitHub
parent 4a997f5f57
commit 39179d4fa0
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/backend-system/building-plugins-and-modules/08-migrating.md
+1 -1
View File
@@ -8,7 +8,7 @@ description: How to migrate existing backend plugins to the new backend system
Migrating an existing backend plugin to the new backend system is fairly straightforward. The process is similar across the majority of plugins which just return a `Router` that is then wired up in the `index.ts` file of your backend. The primary thing that we need to do is to make sure that the dependencies that are required by the plugin are available, and then registering the router with the HTTP router service.
Let's look at an example of migrating the Kubernetes Backend Plugin. In the existing(old) system the kubernetes backend is structured like this:
Let's look at an example of migrating the Kubernetes backend plugin. In the existing (old) system, the kubernetes backend is structured like this:
```ts
// @backstage/plugin-kubernetes-backend/src/service/router.ts