Refresh User cache when user is modified #435
Merged
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.
Redis cache is now refreshed when User is modified.
Problem:
After creating or deleting a shared key, it is not immediately reflected on
/get_user
endpoint as it serves now stale cached version.This adds functionality to bust the user cache - both by id and by api_key - ensuring the cached results are always fresh.
How to test:
GET /api/v2/find_user
, you should see[]
undersharedkey_ids
GET /api/v2/users/:user_id
, you should see[]
undersharedkey_ids
PUT /api/v2/sharedkeys
with body{}
GET /api/v2/find_user
again, you should see['5d81849a...']
undersharedkey_ids
GET /api/v2/users/:user_id
again, you should also see['5d81849a...']
undersharedkey_ids
DELETE /api/v2/sharedkeys/:keyId
GET /api/v2/find_user
, you should see[]
undersharedkey_ids
GET /api/v2/users/:user_id
, you should see[]
undersharedkey_ids