-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
r/lambda_function: support nodejs 10.x runtime #8622
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks for the additional test, @acburdine! 🚀
--- PASS: TestAccAWSLambdaFunction_runtimeValidation_NodeJs10x (43.24s)
@bflad I am desperately waiting for Lamdba Runtime Node.js 10? Is there any schedule/frequency followed to release patches ? |
@chintan-patel typically weekly (roughly Thursdays) see also the repository CHANGELOG: https://github.com/terraform-providers/terraform-provider-aws/blob/master/CHANGELOG.md |
Thank you I ll look |
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. |
@acburdine @bflad This fix made it into 2.11 but I need this in 2.4 to test other bug fixes with api gateway stage and deployment resources. What is the best way to make this happen? |
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! |
Community Note
Fixes #8627
Release note for CHANGELOG:
Output from acceptance testing:
Looks like it failed on trying to create another VPC.......must be an issue with the specific account I ran this in, everything else looked fine.