From 021b03669a712afacb210a3ec13a2711dd9be1ed Mon Sep 17 00:00:00 2001 From: Ivan Shmidt Date: Mon, 13 Jul 2020 11:19:20 +0200 Subject: [PATCH] docs(proxy): add link to plugin creation docs --- docs/getting-started/structure-of-a-plugin.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/getting-started/structure-of-a-plugin.md b/docs/getting-started/structure-of-a-plugin.md index fcfb2c0d46..a277628b6c 100644 --- a/docs/getting-started/structure-of-a-plugin.md +++ b/docs/getting-started/structure-of-a-plugin.md @@ -95,4 +95,13 @@ There are two things needed for a Backstage app to start making use of a plugin. Luckily these two steps happen automatically when you create a plugin with the Backstage CLI. +## Talking to the outside world + +If your plugin needs to communicate with services outside the backstage +environment you will probably face challenges like CORS policies and/or +backend-side authorization. To smooth this process out you can use proxy - +either the one you already have (like nginx/haproxy/etc) or the proxy-backend +plugin that we provide for the backstage backend. +[Read more](../../plugins/proxy-backend/README.md) + [Back to Getting Started](README.md)