-
Notifications
You must be signed in to change notification settings - Fork 602
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
Add support for Nodejs16.x #2283
Comments
Is support for Nodejs16.x added in previous releases? Still facing an issue while setting lambda runtime to nodejs16.x |
Its included the automated maintenance scripts so it always doesn't get automatically called out. From the current version of the spec "LambdaRuntime": {
"AllowedValues": [
"dotnet6",
"dotnetcore1.0",
"dotnetcore2.0",
"dotnetcore2.1",
"dotnetcore3.1",
"go1.x",
"java11",
"java8",
"java8.al2",
"nodejs",
"nodejs10.x",
"nodejs12.x",
"nodejs14.x",
"nodejs16.x",
"nodejs4.3",
"nodejs4.3-edge",
"nodejs6.10",
"nodejs8.10",
"provided",
"provided.al2",
"python2.7",
"python3.6",
"python3.7",
"python3.8",
"python3.9",
"ruby2.5",
"ruby2.7"
]
}, whats your |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
cfn-lint version: (
cfn-lint --version
)Description of issue.
AWS has added support for nodejs16.x for Lambda runtime. However this will generate an error using cfn-lint as it doesnt support this yet
E3030 You must specify a valid value for Runtime (nodejs16.x). Valid values are ["dotnetcore1.0", "dotnetcore2.0", "dotnetcore2.1", "dotnetcore3.1", "go1.x", "java11", "java8", "java8.al2", "nodejs", "nodejs10.x", "nodejs12.x", "nodejs14.x", "nodejs4.3", "nodejs4.3-edge", "nodejs6.10", "nodejs8.10", "provided", "provided.al2", "python2.7", "python3.6", "python3.7", "python3.8", "python3.9", "ruby2.5", "ruby2.7"]
The text was updated successfully, but these errors were encountered: