Update timeout to match API Gateway #421
Merged
Conversation
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
Is this correct? I get a warning from Serverless that the max timeout API Gateway and the Serverless config are not the same. ``` Serverless: WARNING: Function crawl has timeout of 60 seconds, however, it's attached to API Gateway so it's automatically limited to 30 seconds. ```
christophgysin
approved these changes
Jul 23, 2019
|
The build is failing for this change though. Could you look into that? Then I can merge right away. |
@eahefnawy, All good? |
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.
Is this correct? I get a warning from Serverless that the max timeout API Gateway and the Serverless config are not the same.