DPC-4966 remove redis #2831
Merged
DPC-4966 remove redis #2831
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🎫 Ticket
https://jira.cms.gov/browse/DPC-4966
🛠 Changes
ℹ️ Context
With the removal of sidekiq we no longer need redis. Web and Admin were using Redis to cache email address to throttle potential spam; this caching was moved to the default Rails cache (FileStore). As we only have one instance of each running in the sandbox, localized caching should not affect behavior.
🧪 Validation
Local testing with logs showed that email throttling still works.
Quick Deployment works: https://github.com/CMSgov/dpc-app/actions/runs/19374573001
(ci did the testing)