Add AWS_LAMBDA_INITIALIZATION_TYPE env var #7533
Merged
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.
Which issue(s) does this change fix?
fixes #7532
Why is this change necessary?
According to the official AWS documentation there is a environment variable named
AWS_LAMBDA_INITIALIZATION_TYPE
that can contains following values:on-demand
,provisioned-concurrency
, orsnap-start
. Since SAM is intended to emulate Lambda in local environment, so, its good if SAM can include this env var with the default valueon-demand
, for example.How does it address the issue?
Adding the correspondent env var.
What side effects does this change have?
I don't see any.
Mandatory Checklist
PRs will only be reviewed after checklist is complete
make pr
passesmake update-reproducible-reqs
if dependencies were changedBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.