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

Update default value of reserved_concurrent_executions to -1 #39

Merged
merged 2 commits into from
Mar 14, 2019
Merged

Update default value of reserved_concurrent_executions to -1 #39

merged 2 commits into from
Mar 14, 2019

Conversation

jeohist
Copy link
Contributor

@jeohist jeohist commented Feb 27, 2019

As hashicorp/terraform-provider-aws#3806 has been merged into the Terraform AWS Provider 2.0, the current default value of this module will effectively mean no Lambda invocations will be handled. By setting the default value to -1 instead of 0, we return to the original unrestricted value.

@Rowern
Copy link

Rowern commented Mar 4, 2019

Yes, please, this made for a really weird deploy day for us...

@raymondbutcher
Copy link
Contributor

Hi, sorry I didn't see this sooner.

I think we should add an AWS provider restriction for >= 2.0.0 to aws.tf when doing this.

@raymondbutcher
Copy link
Contributor

Just looking into this myself and I don't think you can really pin a provider version in a module without also specifying other fields like region, credentials, etc. I'm currently testing how this works with different versions and will report back.

@raymondbutcher
Copy link
Contributor

How the AWS provider works:

  • The old provider checks for > 0 when deciding if it should set a value or be unlimited.
    • -1 is unlimited
    • 0 is unlimited
  • The new provider checks for >= 0 when deciding if it should set a value or be unlimited.
    • -1 is unlimited
    • 0 sets a value of 0 which disables the function

So setting it to -1 has no downside. I'll merge and release this, thanks!

@raymondbutcher raymondbutcher merged commit 6bd81fe into claranet:master Mar 14, 2019
@raymondbutcher
Copy link
Contributor

This is in v0.11.3

asavoy added a commit to mathspace/terraform-aws-lambda that referenced this pull request Aug 17, 2020
gokuldaemon pushed a commit to Daemon-Solutions/tf-aws-elasticsearch-curator that referenced this pull request Oct 22, 2020
As per claranet/terraform-aws-lambda#39 if a recent version of the AWS provider is used and that fix is not in place then the result is that the Lambda function is disabled. Upgrading the Lambda module makes this module work with recent AWS provider versions.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants