-
Notifications
You must be signed in to change notification settings - Fork 187
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
Updating Lambda that was using 8.10 won't update anymore and How to end Travis with fail after unsuccessful deploy? #525
Comments
|
|
Travis Config
|
motdotla#525 ``` The runtime parameter of nodejs8.10 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs12.x) while creating or updating functions. ``` Current Code: First, update the function code. At this time, the configuration is still outdated, so the runtime updates it with nodejs.8.10, which results in an error. Modifications: Update your settings at the beginning. This will update the runtime, so the update is expected to succeed. Since I can't create any nodejs8.10 functions already, I can't confirm their operation at hand.
Thank you. |
OK let me know, I still have a few older lambdas that I can test this on. I know there is no going back after updating the lambda, but there are plenty of us with older lambdas that could use this fix. |
#525 ``` The runtime parameter of nodejs8.10 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs12.x) while creating or updating functions. ``` Current Code: First, update the function code. At this time, the configuration is still outdated, so the runtime updates it with nodejs.8.10, which results in an error. Modifications: Update your settings at the beginning. This will update the runtime, so the update is expected to succeed. Since I can't create any nodejs8.10 functions already, I can't confirm their operation at hand.
updateCodeReuest 😂 |
Long as it's consistent.. heh |
I can confirm it's working. Just pushed an older 6 lambda to 12 that was throwing errors previously. Can you push it to npm? I think your pusher is broken. Thanks. |
Jenkins has been set up to push on tags, once we have a 0.17.0 PR like this we can go ahead and get a tag up that will be automatically pushed. |
As for my second issue. Do you think node-lambda exists with a 0 on fail deploys? Is that the case with Travis thinking it was successful? Any advice how to properly setup the travis? |
@DeviaVir I see the 17 release, but https://www.npmjs.com/package/node-lambda still showing 16, some test fail? |
Two issues.
My .env file has
AWS_RUNTIME=nodejs12.x
set when calling deploy. I can verify that it is using it, because the log hasRuntime: 'nodejs12.x',
string before it fails.Any way to force update it? I had to manually log into AWS and change the version in the lambda.
The text was updated successfully, but these errors were encountered: