Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(rate-limit/redis): Use redis to store throttling data for admin endpoints #2863

Merged
merged 6 commits into from
Jan 31, 2024

Conversation

gagantrivedi
Copy link
Member

@gagantrivedi gagantrivedi commented Oct 19, 2023

Thanks for submitting a PR! Please check the boxes below:

  • I have run pre-commit to check linting
  • I have filled in the "Changes" section below?
  • I have filled in the "How did you test this code" section below?
  • I have used a Conventional Commit title for this Pull Request

Changes

Add support for using redis to store throttling data

How did you test this code?

Adds unit tests

@gagantrivedi gagantrivedi marked this pull request as draft October 19, 2023 09:21
@vercel
Copy link

vercel bot commented Oct 19, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 22, 2024 1:23pm
flagsmith-frontend-preview ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 22, 2024 1:23pm
flagsmith-frontend-staging ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 22, 2024 1:23pm

@github-actions
Copy link
Contributor

github-actions bot commented Oct 19, 2023

Uffizzi Preview deployment-44326 was deleted.

@codecov-commenter
Copy link

codecov-commenter commented Oct 20, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (37831a8) 95.99% compared to head (f1a875a) 95.64%.
Report is 27 commits behind head on main.

❗ Current head f1a875a differs from pull request most recent head 01d0f2b. Consider uploading reports for the commit 01d0f2b to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2863      +/-   ##
==========================================
- Coverage   95.99%   95.64%   -0.36%     
==========================================
  Files        1068     1013      -55     
  Lines       32721    29033    -3688     
==========================================
- Hits        31411    27769    -3642     
+ Misses       1310     1264      -46     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@gagantrivedi gagantrivedi changed the title Feat/redis feat(rate-limit/redis): Use redis to store rate limit data for admin endpoints Oct 20, 2023
@gagantrivedi gagantrivedi requested review from a team, khvn26 and matthewelwell October 20, 2023 06:30
@gagantrivedi gagantrivedi changed the title feat(rate-limit/redis): Use redis to store rate limit data for admin endpoints feat(rate-limit/redis): Use redis to store throttling data for admin endpoints Oct 20, 2023
@gagantrivedi gagantrivedi marked this pull request as ready for review October 20, 2023 06:32
use redis for user throttle cache

implement admin rate throttle

Add default value for redis cache env

Add redis cache url

misc throttle fixes

[minor]

refac: remove explicit redis cache

review fixes

fix tests

change scope

refac: use explicit throttle_class

Add helpful comments to settings

rollback sentry sampler changes

[minor]

fix test settings

improve settings

wip: tests

[minor]

don't throttle selfhosted telemetry view

update lock file

refactor tests
@gagantrivedi
Copy link
Member Author

Will be merged after the release

@gagantrivedi gagantrivedi added this pull request to the merge queue Jan 31, 2024
Merged via the queue into main with commit 61537ce Jan 31, 2024
18 checks passed
@gagantrivedi gagantrivedi deleted the feat/redis branch January 31, 2024 03:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Issue related to the REST API
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants