From 4a997f5f571d43554893500cb28119c463bde588 Mon Sep 17 00:00:00 2001 From: Johan Haals Date: Wed, 18 Jan 2023 14:55:32 +0100 Subject: [PATCH] Update docs/backend-system/building-plugins-and-modules/08-migrating.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Johan Haals Co-authored-by: Fredrik Adelöw Signed-off-by: Johan Haals --- .../backend-system/building-plugins-and-modules/08-migrating.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/backend-system/building-plugins-and-modules/08-migrating.md b/docs/backend-system/building-plugins-and-modules/08-migrating.md index b9bd392583..8f5182ae12 100644 --- a/docs/backend-system/building-plugins-and-modules/08-migrating.md +++ b/docs/backend-system/building-plugins-and-modules/08-migrating.md @@ -6,7 +6,7 @@ sidebar_label: Migration Guide 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 and similar across as the majority of return a `Router` that is then wired up in the index.ts file. 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 register the router with the http router service. +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: