Add configurable HTTP read timeout for Lambda invocation (default 240s)#6
Merged
MarcoRBosco merged 1 commit intomainfrom Apr 9, 2026
Merged
Conversation
…vocation Agent-Logs-Url: https://github.com/uampio/invoke-aws-lambda-rs/sessions/6edc07b1-2e37-41d9-b688-0620424cc85b Co-authored-by: MarcoRBosco <62314876+MarcoRBosco@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
MarcoRBosco
April 9, 2026 16:15
View session
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
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.
Lambda functions running longer than the SDK's default HTTP read timeout cause the action to fail client-side before Lambda even returns. This adds a
TIMEOUTinput to control how long the action waits for a response.Changes
action.yml: New optionalTIMEOUTinput (default"240"seconds), forwarded asINPUT_TIMEOUTenv var to the binaryCargo.toml: Addedaws-smithy-typesforTimeoutConfigsrc/main.rs:TIMEOUT, warns and falls back toDEFAULT_TIMEOUT_SECS = 240on invalid inputTimeoutConfig::builder().read_timeout(...)to the AWS SDK client configUsage