Crevil
a4fa1ce090
When working with the proxy configuration or plugins facilitating the proxy package the workflow is currently somewhat cumbersom as changes to the proxy configuration requires a full restart of the backend server. Use cases where the proxy configuration is updated is when testing out new routes for plugins to use and updating header configuration like authorization tokens. This change updates the proxy-backend to subscribe to configuration changes and update the router when changes to the proxy is made. Signed-off-by: Crevil <bjoern.soerensen@gmail.com>
Proxy backend plugin
This is the backend plugin that enables proxy definitions to be declared in,
and read from, app-config.yaml.
Relies on the http-proxy-middleware package.
Getting Started
This backend plugin can be started in a standalone mode from directly in this package
with yarn start. However, it will have limited functionality and that process is
most convenient when developing the plugin itself.
The proxy is already installed in the Backstage backend per default, so you can also start up the full example backend to experiment with the proxy.
yarn workspace example-backend start
Configuration
See the proxy docs.
Links
- Call Existing API helps the decision process of what method of communication to use from a frontend plugin to your API
- The proxy plugin documentation describes configuration options and more
- http-proxy-middleware