Invalidate cache after deactivation in renewal flow #712
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.
Adds cache invalidation to deactivation script. Adds test case that checks whether cached clubs are flushed after running deactivation command.
For context: we run a command to deactivate all clubs at the beginning of the year. This kicks off the renewal cycle. The command changes club attributes but doesn't invalidate the cache. This results in incorrect behavior -- the frontend marks clubs as having been approved prematurely.