New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configure Lambda Timeout for local run #510
Comments
Looks like
|
FYI, current iteration also doesn't pick up the value specified in the |
I think it should take the template.yaml value when it can find one, and it should be possible to override this in the lambda configuration (in templates.json) |
I second this, unusable doing local invocation when using with slow external APIs in function |
this is going to be in a next release?? It's pointless to limit local execution to just 3 seconds. |
Issue has been revised to accept the configuration from the SAM Template. |
This change is now in the develop branch. |
You can configure a Lambda Function's timeout in the SAM template, but you cannot configure it during local iteration. It should be possible to specify a different timeout configuration without changing the template file directly.Lambda Function's Timeout is configurable via SAM Template, but is not honored in local run/debug sessions.
This should apply to run only. Hitting breakpoints during debug increases the likelihood of exceeding the timeout, which wouldn't make sense.
Reference: Template Spec
The text was updated successfully, but these errors were encountered: