Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Updating Lambda that was using 8.10 won't update anymore and How to end Travis with fail after unsuccessful deploy? #525

Copy link
Copy link
@teebu

Description

@teebu
Issue body actions

Two issues.

  1. Updating a lambda with runtime of 8 to 12 now fails to deploy with a message:

My .env file has AWS_RUNTIME=nodejs12.x set when calling deploy. I can verify that it is using it, because the log has Runtime: 'nodejs12.x', string before it fails.

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.

Any way to force update it? I had to manually log into AWS and change the version in the lambda.

  1. How can I end Travis with a fail instead of success on any type of fail to deploy thrown by node-lambda?
Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.