-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(router): add route to invalidate cache entry #1100
feat(router): add route to invalidate cache entry #1100
Conversation
ff92f9c
to
0850a4f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than that, looks good to me!
2f1974c
to
f0d6624
Compare
added remove method to invalidate the cache key
added endpont added unit test
refactored route to include route parameters Added flow type Added API error response type Created cache interface for db module updated unit test: Check if the key/value is invalidated.
remove dthe cache interface
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than that, looks good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than LGTM
# Conflicts: # Cargo.lock
# Conflicts: # crates/router_env/src/logger/types.rs
3e5736a
Type of Change
Description
A new route to invalidate the in-memory cache and redis
Additional Changes
Motivation and Context
Currently we don't have any way to manually invalidate cache that's stored in redis and in-memory,
Closes #995.
How did you test it?
A unit test is added to test the in-memory cache and postman script used for redis cache.
Checklist
cargo +nightly fmt --all
cargo clippy