v0.5.6

This release officially marks the end of the v0.5.x milestone. This milestone contained all these features, fixes and cleanups:

1. Introduce a new Admin API, so that plugins can query for information from GatewayD, information such as version, global and plugins config, plugins, pools, proxies and servers. The API works over gRPC with protobuf and has a thin HTTP layer that proxies call to the gRPC API. The HTTP API has an OpenAPI v2 specification document that can be accessed via /swagger.json. The specification document can be viewed and interacted with using the Swagger UI, which is accessible via /swagger-ui/.
2. Introduce the --dev persistent (global) flag for the gatewayd command that can be used by plugin developers to bypass checksum validation of plugins in development.
3. Add a new configuration parameter to the gatewayd_plugins.yaml config file, called ReloadOnCrash, to reload a crashed plugin upon the next scheduled call to the plugin health check, if enabled. The default is true.
4. Fix bugs in the client that were reported in Sentry.
5. Introduce a small usage report feature that reports some information back to the usage report service, devoid of any PII, which can be completely disabled by passing --usage-report=false to the gatewayd command.
6. Change the type of hook names from constant string to protobuf enumeration.
7. Fix bugs in graceful shutdown of the server.
8. Fix bug in handling client.ID.
9. Increase the buffer size to 128 MB and the chunk size to 8 KB.
10. Improve client performance by using bytes.Buffer instead of append to a byte array to handle large inputs passed between the client, the server and the plugins.

What's Changed

• Improve client performance by @mostafa in #200

Full Changelog: v0.5.5...v0.5.6