reserved_concurrent_executions for aws_lambda_function does not support 0 concurrency #3803
Labels
enhancement
Requests to existing resources that expand the functionality or scope.
service/lambda
Issues and PRs that pertain to the lambda service.
Milestone
Actual Result
If
reserved_concurrent_executions = 0
for anaws_lambda_function
in Terraform, reserve concurrency is disabled:Expected Result
However, 0 is actually a valid value with a specific meaning, which you can see via the console:
Why would you ever set reserved concurrency to 0? From the AWS documentation:
If you need a function to stop processing any invocations, you can choose to set the concurrency to 0 and throttle all incoming executions.
This is useful for long-running jobs (example: airbnb/binaryalert#46)
Requested Change
Provide a way to distinguish between disabled reserve concurrency and no reserve concurrency. Not sure the best approach here - maybe a negative value or an empty string disables it?
Versions
Terraform 0.11.3 with AWS provider 1.11.0
Affected Resource(s)
Terraform Configuration Files
The text was updated successfully, but these errors were encountered: