Releases: envoyproxy/ratelimit
v1.4.0
go 1.11 update and a few other changes
This release brings in the following changes:
- Update to go 1.11.
- Fix log level bug: the user defined log level was not correctly wired up to the codebase.
- Fix and update the docker setup.
- Add gRPC healthchecking.
Redis: option to use a separate Redis cluster for per second limits
Relevant documentation in the README.
Check in data-plane-api compiled protos
Ratelimit can be compiled as a full fledged gRPC service directly from this repo with make compile
; the make target will also compile the necessary protos. However, if users want to import ratelimit as a go dependency and build on top of it, glide will complain with:
[ERROR] Error scanning github.com/lyft/ratelimit/proto/envoy/api/v2/ratelimit: open /Users/josenino/.glide/cache/src/https-github.com-lyft-ratelimit/proto/envoy/api/v2/ratelimit: no such file or directory
...
[ERROR] Error scanning github.com/lyft/ratelimit/proto/envoy/service/ratelimit/v2: open /Users/josenino/.glide/cache/src/https-github.com-lyft-ratelimit/proto/envoy/service/ratelimit/v2: no such file or directory
This release includes the compiled protos in order to allow users to import ratelimit as a library without any dependency issues.
Deprecating legacy ratelimit proto
Fixes #14
In order to not break any clients using the legacy ratelimit.proto, Ratelimit is going to support both handlers: the one for the data-plane-api service definition (rls) and the legacy service definition (ratelimit.proto).
The legacy handler will accept a request, translate it into a data-plane-api proto request and use the rest of the codebase as if the new handler had been called. This will incur a perf penalty for clients using the legacy proto.
v1.0.0: update dependencies (#35)
* update dependencies