-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NodeJS 8.10 environment support for lambdas #4223
Comments
This was previously merged in via #4020 and released in version 1.14.0 of the AWS provider and has been available in all releases since. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
@bflad This issue is still ongoing for me
|
@maxprovin check your AWS provider version:
or
Terraform core (0.11.7) is separately released from providers after 0.10+. The Terraform documentation on provider versioning goes into details about how to update your providers (I prefer |
As @bflad said, you have outdated providers. To fix that just rerun |
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! |
This issue was originally opened by @aleybovich as hashicorp/terraform#17872. It was migrated here as a result of the provider split. The original body of the issue is below.
Terraform Version
Terraform Configuration Files
Expected Behavior
Terraform should run normally and a new lambda with node8.10 environment should be created
Actual Behavior
Steps to Reproduce
Create a lambda function element with
runtime = "nodejs8.10"
Additional Context
AWS is now supporting nodejs 8.10 environment as of a couple of weeks ago. Please add support for the environment in terraform. I assume it's as simple as adding
nodejs8.10
enumeration somewhere to have the element correctly validatedThe text was updated successfully, but these errors were encountered: