Support nodejs10.x runtime in Lambda

[hhakkala]

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 "me too" comments, 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

Specifying nodejs10.x as function runtime currently results in validation error:

$ terraform -v
Terraform v0.11.13
+ provider.aws v2.10.0

$ terraform apply
Error: module.default.aws_lambda_function.default: expected runtime to be one of [dotnetcore1.0 dotnetcore2.0 dotnetcore2.1 go1.x java8 nodejs4.3 nodejs4.3-edge nodejs6.10 nodejs8.10 provided python2.7 python3.6 python3.7 ruby2.5], got nodejs10.x

New or Affected Resource(s)

• aws_lambda_function

Potential Terraform Configuration

resource "aws_lambda_function" "default" {
  function_name = "MyFunction"
  ...
  runtime = "nodejs10.x"
}

References

• Support NodeJS v8.10.0 runtime in Lambda functions #4019

[acburdine]

I've got a PR open to add support here: #8622

[bflad]

Support for the new nodejs10.x runtime in the aws_lambda_function resource has been merged and will be released with version 2.11.0 of the Terraform AWS Provider later this week. 👍

[bflad]

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

[ghost]

The docs should be updated to reflect support for the new nodejs version (nodejs8 is being deprecated).
https://www.terraform.io/docs/providers/aws/r/lambda_function.html#basic-example
I clicked edit this page but could not understand where to make the change.

[ghost]

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!