From 44bb4cb345467269b61a8630e95b11c5a682fd0a Mon Sep 17 00:00:00 2001 From: Aramis Sennyey <159921952+aramissennyeydd@users.noreply.github.com> Date: Mon, 11 Mar 2024 19:40:31 -0400 Subject: [PATCH] Update beps/0005-split-backend-discovery/README.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Fredrik Adelöw Signed-off-by: Aramis Sennyey <159921952+aramissennyeydd@users.noreply.github.com> --- beps/0005-split-backend-discovery/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/beps/0005-split-backend-discovery/README.md b/beps/0005-split-backend-discovery/README.md index 1050e25052..8ffa9f0af4 100644 --- a/beps/0005-split-backend-discovery/README.md +++ b/beps/0005-split-backend-discovery/README.md @@ -56,7 +56,7 @@ This section is for explicitly listing the motivation, goals, and non-goals of this BEP. Describe why the change is important and the benefits to users. --> -Split backends are a consistently difficult space to operate in and design for. There has been a growing desire for the framework to provide a way to get a list of the installed plugins. This was nearly impossible in the old backend, where plugins were hosted on unnormalized routes and had non-standard startup sequences. In the new backend, this has become significantly more doable. Moving this forward would unblock a number of cases that require knowledge of your entire Backstage installation, namely a single OpenAPI spec for your instance, checking installed permissions, and DevTools information. +Split backends are a consistently difficult space to operate in and design for. There has been a growing desire for the framework to provide a way to get a list of the installed plugins. This was nearly impossible in the old backend, where plugins were hosted on denormalized routes and had non-standard startup sequences. In the new backend, this has become significantly more doable. Moving this forward would unblock a number of cases that require knowledge of your entire Backstage installation, namely a single OpenAPI spec for your instance, checking installed permissions, and DevTools information. Ideally, this work will also make it easier for adopters to go down the path of split backends.