Skip to content
This repository has been archived by the owner on Jun 8, 2022. It is now read-only.

AWS provider 2.0.0 disables the function #40

Closed
raymondbutcher opened this issue Mar 14, 2019 · 1 comment
Closed

AWS provider 2.0.0 disables the function #40

raymondbutcher opened this issue Mar 14, 2019 · 1 comment

Comments

@raymondbutcher
Copy link
Contributor

https://github.com/terraform-providers/terraform-provider-aws/blob/master/CHANGELOG.md#200-february-27-2019

resource/aws_lambda_function: Setting reserved_concurrent_executions to 0 will now disable Lambda Function invocations, causing downtime for the Lambda Function. Previously reserved_concurrent_executions accepted 0 and below for unreserved concurrency, which means it was not previously possible to disable invocations. The argument now differentiates between a new value for unreserved concurrency (-1) and disabling Lambda invocations (0). If previously configuring this value to 0 for unreserved concurrency, update the configured value to -1 or the resource will disable Lambda Function invocations on update. If previously unconfigured, the argument does not require any changes. See the Lambda User Guide for more information about concurrency.

@raymondbutcher
Copy link
Contributor Author

Resolved by #39

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant