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

未关闭
#525 11 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
aws, javascript, node.js
领域
cli, cloud

调研方向

Start by reproducing the AWS Lambda update with AWS_RUNTIME=nodejs12.x and the Travis deployment failure described in the issue. Trace node-lambda's deploy entry point and its handling of deployment errors; done means supported runtime updates no longer use nodejs8.10 and Travis reports deployment failures as failed builds.

由索引模型根据 Issue 内容生成。

描述

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?
主要语言
JavaScript
星标
1.4k
派生
185
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

motdotla/node-lambda 的其他 Issue

查看 motdotla/node-lambda 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。