apisonator
apisonator copied to clipboard
3scale
Red Hat 3scale API Management Apisonator backend
Twemproxy is no longer maintained and Envoy can act as a Redis proxy: https://www.envoyproxy.io/docs/envoy/v1.13.0/api-v2/config/filter/network/redis_proxy/v2/redis_proxy.proto I tried to pass the test container by simply stopping Twemproxy and starting an Envoy with...
We can't do this yet, but when possible, we should drop support for Ruby 2.4. After that, we'll be able to update some gems like the async ones.
Hi there! I was using a docker image of Apisonator to avoid reliance on [SaaS](https://www.3scale.net/) for integration testing of WASM filters, being developed under the GSoC'21 program. I am using...
We should group the jobs and use Redis pipelining here: https://github.com/3scale/apisonator/blob/ea235743c72e9365926c4bfea08bc13df56cd4b7/lib/3scale/backend/transactor/notify_batcher.rb#L104
I don't think it's used anywhere. We probably forgot to delete it when we removed the "end-users" feature.
In some environments, that's done using a Redis exporter. However, that's not available in some setups. For that reason, it'd be nice if the Apisonator workers exposed the queue sizes...
We learnt in #280 that Porta is storing OIDC apps' client_secrets as `app_key`'s, and that has caused confusion as to how to deal with OIDC in the 3scale Istio Adapter,...
This validator **might** no longer be necessary. This issue should be closed whenever we find out whether it is or isn't needed as of the latest 3scale versions: it might...
We should delete the SAAS env. There are no differences any more. In the process, we should also unify all the dependencies under a single Gemfile and reorganize the Rake...
Perhaps it is my misunderstanding but I am finding it confusing the way rejections due to breach of rate limits are presented to the caller. For example in a standard...
