feat: Added task_id-related TTL for cache plugin - #635
Open
DrRebus wants to merge 1 commit into
Open
Conversation
Signed-off-by: Ruben Tordjman <144785435+DrRebus@users.noreply.github.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
New feature.
What is the current behavior? (You can also link to an open issue here)
Cache entries from the cache plugin can only be expired according to a given date.
What is the new behavior (if this is a feature change)?
When setting a cache value (new or update) using the cache plugin, instead of specifying an expiration date, we can now specify the public ID of a task, making the cache entry live as long as the related task exists.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No: existing cache entries are unaffected and new cache entries can still be created without specifying a task ID
Other information: