Option to apply ratelimiting over a single API #46
Comments
Surbhi-sharma1
added a commit
that referenced
this issue
Oct 12, 2022
12 tasks
Surbhi-sharma1
added a commit
that referenced
this issue
Feb 15, 2023
Surbhi-sharma1
added a commit
that referenced
this issue
Feb 15, 2023
Surbhi-sharma1
added a commit
that referenced
this issue
Feb 15, 2023
…er single API Added an option to apply ratelimiting over single API GH-46
|
This issue has been marked stale because it has not seen any activity within three months. If you believe this to be an error, please contact one of the code owners. This issue will be closed within 15 days of being stale. |
Surbhi-sharma1
added a commit
that referenced
this issue
Feb 28, 2023
…er single API Added an option to apply ratelimiting over single API GH-46
|
🎉 This issue has been resolved in version 4.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
As of the now, the module provides a way to ratelimit all api except a few that are disabled using a decorator. There should be a way to ratelimit only a few of the many available apis.
Expected behavior
There should be a configurable default mode of ratelimiting for a microservice, if it is false, ratelimiting should be disabled for all APIs except those that are enabled using the decorator.
The text was updated successfully, but these errors were encountered: