[英]ask-cli deploy lambda takes long time
Whenever I try to run ask deploy lambda
for the python lambda, it first attach and zip all the libraries and then updates the lambda scripts, which takes a long time.每当我尝试为 python lambda 运行
ask deploy lambda
,它首先附加并压缩所有库,然后更新 lambda 脚本,这需要很长时间。 Is there any way to limit it to only updating the .py files that changed?有什么方法可以限制它只更新更改的 .py 文件?
Thanks,谢谢,
as far as I know there is no "changeset" concept from Lambda service to only provide the changed part of the code.据我所知,Lambda 服务没有“变更集”概念来仅提供代码的更改部分。 Hence ask-cli might be able to do that.
因此 ask-cli 可能能够做到这一点。
CLI can deploy smartly when it's related to the changes in AWS service using cloudformation, like it only deploys changes for the modified service.当 CLI 与使用 cloudformation 的 AWS 服务中的更改相关时,它可以智能地部署,就像它只为修改后的服务部署更改一样。 With this idea, CLI does support localHash comparison to avoid unnecessary deployments, if there is no change to your code at all locally.
有了这个想法,CLI 确实支持 localHash 比较以避免不必要的部署,如果您的代码在本地根本没有更改。 However, it has to be the entire source code plus its build for Lambda code uploading.
但是,它必须是完整的源代码加上其用于 Lambda 代码上传的构建。 This means as long as you change the code, the re-build time and the upload time are kinda a must have.
这意味着只要您更改代码,重新构建时间和上传时间是必须的。
Btw, how long usually do you need to wait for this code upload process? Btw,这个代码上传过程通常需要等待多长时间?
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.