Terraform-provider-aws: AWS Lambda support for .NET Core 3.1

[ewbankkit]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

AWS Lambda now supports .NET Core 3.1.

New or Affected Resource(s)

• aws_lambda_function
• aws_lambda_layer_version

Potential Terraform Configuration

resource "aws_lambda_function" "example" {
  runtime = "dotnetcore3.1"
}

References

Announcement.
Blog post.

Requires AWS SDK v1.30.1:

• https://github.com/terraform-providers/terraform-provider-aws/pull/12414

[Abbatss]

Hi @ewbankkit ,
I can see that you've added support for other runtimes previously.
Are you working on this issue?
If not, let me know, I'll create PR with fix.
I want to deploy my lambda with new runtime as soon as possible.

[ewbankkit]

@Abbatss We'll need #12414 merged first in order to pick up the new runtime constant value. Once that's done you are welcome to work on this. Thanks.

[bflad]

Support for this has been merged in and will release with version 2.57.0 of the Terraform AWS Provider, later this week. Thanks to @ewbankkit for the implementation. 👍

[hashibot[bot]]

This has been released in version 2.57.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

[hashibot[bot]]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!