v0.6.7

This release contains two fixes:

1. All the default values are moved from New<feature> functions to the config package.
2. The port of the metrics is changed from 2112 to 9090 to conform with Prometheus port.

What's Changed

• Move default values to config package by @mostafa in #257

Full Changelog: v0.6.6...v0.6.7

v0.6.6

This release contains many fixes and a new feature: non-default config groups will receive default values for each config object.

What's Changed

• Generate checksum for APT and RPM packages on release by @mostafa in #253
• Default value for non default config groups by @mostafa in #256

Full Changelog: v0.6.5...v0.6.6

v0.6.5

This release contains three changes:

1. Update README for the BIG RELEASE, which still needs some polishing.
2. APT and RPM packages are built and released from now on for AMD64 and ARM64 platforms.
3. The config file location for gatewayd.yaml and gatewayd_plugins.yaml are now read from the current working directory, then the /etc, and the fallback will be the current working directory. Loading the config is done at a later stage.

What's Changed

• Add a proper README by @mostafa in #120
• Create linux packages by @mostafa in #251
• Choose config file location conditionally by @mostafa in #252

Full Changelog: v0.6.4...v0.6.5

v0.6.4

This release contain a bugfix that resulted in addition of a new policy parameter for determining whether to stop processing hooks when one wants to terminate the request or continue running the rest of the hooks. This also adds a few more validation rules for validating the global config file.

What's Changed

• Fix termination issue by @mostafa in #248

Full Changelog: v0.6.3...v0.6.4

v0.6.3

This release contains a new feature and a few fixes to configuration handling of GatewayD. There is a new subcommand, config, that can be used to manage GatewayD global configuration file. The config init will generate or overwrite (using -f) the global configuration file. The config lint will validate the global configuration file to find inconsistencies.

What's Changed

• Add config command by @mostafa in #246

Full Changelog: v0.6.2...v0.6.3

v0.6.2

This release contains updates and the fix to a long-standing issue that caused clients to wait indefinitely for reading from the server. The dependencies are also updated to the latest versions.

What's Changed

• Fix receive issue of the client connection by @mostafa in #245

Full Changelog: v0.6.1...v0.6.2

v0.6.1

In this release, these changes has been made:

1. Update all dependencies to their latest versions.
2. Fix linter timeout.
3. Fix check for the existence of the requires in the plugin config.
4. Check if plugin metadata is present and not nil.
5. Kill the plugin client if it can't be started or dispensed.
6. Fix default chunk size.
7. Regenerate gRPC API stubs.
8. Remove SHA256SUM function and its tests in favor of secure config.
9. Fix CI for testing the go plugin template.

What's Changed

• Use secure config for checksum verification by @mostafa in #233

Full Changelog: v0.6.0...v0.6.1

v0.6.0

This release contains these changes:

1. Go is updated to 1.20 plus all the dependencies.
2. The gRPC and HTTP API ports are changed to 18080 and 19090 respectively.
3. Timeouts are added to plugin hooks: previously, hooks could block the main thread indefinitely, thus making GatewayD unresponsive, but now they will time out and return the control back to the GatewayD's main thread. The timeout parameter can be adjusted in the gatewayd_plugins.yaml file.

What's Changed

• Use context timeout in hooks by @mostafa in #204

Full Changelog: v0.5.6...v0.6.0

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

v0.5.5

This release contains a few fixes:

1. Shutdown server(s) gracefully (#198)
2. Check if client.ID is not empty by (d72bd1b)
3. Increase buffer size to 128 MB and chunk size to 8 KB (97f49f7)
4. Update SDK and other dependencies (4c80fd7)

Full Changelog: v0.5.4...v0.5.5