-
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
chore(env): add ttl as env variable #2653
Conversation
66abe63
[kv_config] | ||
# TTL for KV in seconds | ||
ttl = 900 |
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.
Authentication of client secret is done based on merchant_intent_fullfillment time, so shouldn't data live in KV for merchant_intent_fullfillment time interval.
Will failing to fetch from KV fallback to DB ?
Will the data be found in DB always as soon as it is expired in Redis ?
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.
We will have a bigger TTL in prod env so this problem won't occur
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.
Few questions apart from that LGTM
Type of Change
Description
Add TTL for KV as environment variable.
Additional Changes
Motivation and Context
Add TTL for KV as environment variable.
How did you test it?
Checklist
cargo +nightly fmt --all
cargo clippy