Making the Lambda timeout value configurable from grunt options file#3
Merged
Tim-B merged 1 commit intoTim-B:masterfrom May 23, 2015
Merged
Making the Lambda timeout value configurable from grunt options file#3Tim-B merged 1 commit intoTim-B:masterfrom
Tim-B merged 1 commit intoTim-B:masterfrom
Conversation
|
+1 |
Tim-B
added a commit
that referenced
this pull request
May 23, 2015
Making the Lambda timeout value configurable from grunt options file
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
3 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.
I'd like to add a configuration option to make it possible to increase the timeout value for the AWS Lambda function.
I think it's best not to default an initial value for this property as AWS may decide to change the default value from a 3 seconds timeout to something else in future....