We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've found the lambda that is created when using existing = true, see here: https://forum.serverless.com/t/function-s3-trigger-with-existing-true-generates-another-lambda-called-custom-resources/9440 is using the soon to be sunset node16.x runtime. This triggers AWS to send warning emails regularly. We can not currently control what runtime it uses.
existing
true
node16.x
I'm thinking:
node18.x
node20.x
existingRuntime
The text was updated successfully, but these errors were encountered:
This one is related to #12133
Sorry, something went wrong.
No branches or pull requests
Is there an existing issue for this?
Use case description
I've found the lambda that is created when using
existing
=true
, see here: https://forum.serverless.com/t/function-s3-trigger-with-existing-true-generates-another-lambda-called-custom-resources/9440is using the soon to be sunset
node16.x
runtime. This triggers AWS to send warning emails regularly. We can not currently control what runtime it uses.Proposed solution (optional)
I'm thinking:
node18.x
ornode20.x
, or,existingRuntime
The text was updated successfully, but these errors were encountered: