feat: Create Django Command for Deleting Rate Limit Redis Keys #935
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose/Motivation
This PR adds a new django command to be run on CRON clearing any lingering users who may have had a redis key for their rate limit failing to expire.
The command runs only on user's (non-anon) by default, but an option can be passed in to run the deletion on anon users instead as well. We utilize the scan_iter function on redis because it's capable of having a regex path passed in, from which we go through and delete each of the keys. We only delete keys which have no TTL (comes back as -1 when you call the ttl function)
Redis Scan Docs - https://redis.io/docs/latest/commands/scan/
Redis TTL Docs - https://redis.io/docs/latest/commands/ttl/
Closes #2527
Will need the second half to be completed by codecov/engineering-team#2588
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. In 2022 this entity acquired Codecov and as result Sentry is going to need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.