This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
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.
Enable cache time-based expiry by default #11849
Enable cache time-based expiry by default #11849
Changes from 14 commits
f798aba
adbd8ed
bdeaf52
83661c5
4eb3e6a
652c620
6784e1e
253edca
775cbf7
6dddbc7
8efac83
c86e536
327ea5a
8d06aac
f37e95f
3299583
77ac0d7
604145a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
It may be worth mentioning the new configuration options that are available, or otherwise pointing to the relevant section of the sample config for the full details.
This could also be done via our upgrading docs, where we have more room.
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.
I would likely still sneak a keyword or two in there:
expiry_time
will be superseded byexpire_caches
andcache_entry_ttl
.Helps perk people's ears up and helps if you ever need to do a Ctrl+F for one of the config option names.
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.
Since we're changing config options, we should include backwards-compatibility support for the previous config option name. Thus if someone set
expiry_time
previously, that same value should continue to work even after this update. At some point ™️ in the future we can remove support for the old option name.