Closed anarsen closed 4 years ago
Good point. I think we can have Lambda module version 1.6.0 updated to have support for AWS provider version 3, which is going to be used just by this notify-slack module.
v3.5.0 has been just released with this improvement.
Thanks for the swift response, @antonbabenko. It works as expected.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Note This issue might belong in terraform-aws-modules/terraform-aws-lambda - sorry if that's the case
Context
The latest version for TF 0.12 as of this writing is v3.4.0, and relies on https://github.com/terraform-aws-modules/terraform-aws-lambda/tree/v1.6.0.
Unfortunately,
terraform-aws-modules/terraform-aws-lambda
v1.6.0 has a pretty strict version requirement on theaws
provider:https://github.com/terraform-aws-modules/terraform-aws-lambda/blob/aea2b6da21bcde99ed5fdd0ccc27378b84eeda25/versions.tf#L5
Question
What are your thoughts on creating a Terraform 0.12-compatible version of
terraform-aws-modules/terraform-aws-lambda
with a more relaxed AWS provider version pin such asaws = ">= 2.46"
.