feat: clear tenant's cache on update or delete #309
Merged
Conversation
This file contains 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
chasers
reviewed
Feb 19, 2024
|
Is there a reason you're doing those inspects everywhere? Seems odd idk. |
chasers
approved these changes
Feb 19, 2024
|
I use inspect() to make valid map's key/value pairs, and then it will be possible to safely encode them to JSON. |
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.
In this PR, we have introduced functionality to clear the entire internal cache for a specific tenant when an update or delete operation is performed through an API call. Additionally, we have disabled cache clearing when the pool is terminated.