Add ttl CLI parameter and function input value - #371
Merged
Merged
Conversation
Signed-off-by: Bob Haddleton <bob.haddleton@nokia.com>
bobh66
requested review from
negz,
phisco,
sergenyalcin,
turkenf and
ulucinar
as code owners
September 25, 2026 15:20
phisco
approved these changes
Sep 25, 2026
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
2 participants
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.
Add support for customizing the function response TTL value which is presently hard-coded to 1m.
This affects realtime compositions because the shortest TTL returned by the pipeline is used as the requeueAfter value, so any composite that uses this function will always requeue after 1m.