-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Include reserved_concurrent_executions in get_function response #12654
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
Conversation
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 1h 18m 55s ⏱️ - 23m 14s Results for commit 543f91b. ± Comparison against base commit 20c40d1. This pull request removes 1206 and adds 1 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice fix! I just have some minor comments :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for addressing my comments! LGTM!
Motivation
This PR fixes a bug reported by a user. The issue was that when a Lambda function was created in Localstack using Terraform, the
reserved_concurrent_executions
value always reset to -1 in tfstate after apply.While trying to reproduce the issue, I saw that the
reserved_concurrent_executions
value was saved correctly in the created lambda, butreserved_concurrent_executions
wasn’t returned in theAWSLambda::GetFunction
response. Because the response didn’t include the value, Terraform set the value to default -1 and saved that in the tfstate file.Changes
Added code to return the function's
reserved_concurrent_executions
value if it is setTesting
reserved_concurrent_executions
value is updated it is also being returned in response ofAWSLambda::GetFunction