Extend Admin API #181
Labels
enhancement
New feature or request
epic
To be broken down into multiple tasks
triage
Triage based on the content
Description
Currently the Admin API has endpoints that are used for serving information (get requests only), and there is no endpoint that can change the (runtime) configuration or control the behavior of GatewayD.
Planning for different features of the new API consists mostly of CRUD operations and/or updating configuration to enable/disable features. Also, reading configuration is okay, and is considered (partially) harmless, thus authentication is not needed, plus the API servers are only exposed locally. However, updating configuration might cause interruptions, especially if done via unverified sources. Adding some authentication and authorization helps secure the API.
Task list
Move API to the SDK for easier access by pluginsHarder than it looks and is a big breaking change. Might pick up later.cmd/run.go
#370The text was updated successfully, but these errors were encountered: