1

git aws.push在使用 AWS-ElasticBeanstalk-CLI-2.6.0（需要 Ruby 的版本）时，我开始收到以下错误：

MacBook-Pro:apps-prd katia$ git aws.push
Counting objects: 18, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (17/17), done.
Writing objects: 100% (18/18), 126.20 KiB | 0 bytes/s, done.
Total 18 (delta 10), reused 4 (delta 1)
error: RPC failed; result=22, HTTP code = 400
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

我遇到了这个解决方案，它建议获取最新版本的 EB 命令行工具并重置它引用的所有位置。

在获得最近的 ASW CLI (2.6.4) 并重新配置后，我收到以下消息git aws.push：

MacBook-Pro:apps-prd katia$ git aws.push
Updating the AWS Elastic Beanstalk environment eb-prescoapps-php-env...
Environment update initiated successfully.

但是，在每次提交之后部署我的应用程序大约需要 20-30 分钟（第 2 行和第 3 行之间的长时间姿势），而之前根据提交需要 1-3 分钟。

这是标准行为吗？是否部署了整个应用程序而不仅仅是提交的更改？有没有办法修复它？

4

2 回答 2

1

我刚刚对 EB CLI 2.6.4 进行了更新，现在它可以工作了。它比以前的版本慢一点，但不超过 2 分钟。

各位，如果您不想eb init在升级到 2.6.4 后执行此操作，则只能.git/config使用以下内容更新文件

[alias "aws.elasticbeanstalk"]
    remote = !.git/AWSDevTools/aws.elasticbeanstalk.push --remote-url
    push = !.git/AWSDevTools/aws.elasticbeanstalk.push
    config = !.git/AWSDevTools/aws.elasticbeanstalk.config
    createapplicationversion = !.git/AWSDevTools/aws.elasticbeanstalk.createapplicationversion
[aws "endpoint"]
    us-east-1 = git.elasticbeanstalk.us-east-1.amazonaws.com
    ap-northeast-1 = git.elasticbeanstalk.ap-northeast-1.amazonaws.com
    eu-west-1 = git.elasticbeanstalk.eu-west-1.amazonaws.com
    us-west-1 = git.elasticbeanstalk.us-west-1.amazonaws.com
    us-west-2 = git.elasticbeanstalk.us-west-2.amazonaws.com
    ap-southeast-1 = git.elasticbeanstalk.ap-southeast-1.amazonaws.com
    ap-southeast-2 = git.elasticbeanstalk.ap-southeast-2.amazonaws.com
    sa-east-1 = git.elasticbeanstalk.sa-east-1.amazonaws.com
[alias "aws"]
    push = !git aws.elasticbeanstalk.push
    config = !git aws.elasticbeanstalk.config
    createapplicationversion = !git aws.elasticbeanstalk.createapplicationversion

也许 AWS Support 可以确认上述内容。

问候，

于 2014-11-21T09:45:23.297 回答
0

如果您仍有问题，我强烈建议您升级到EB CLI 3.x。它修复了以前版本存在的许多问题，并且是更好的体验。

您可以通过以下方式查看您正在运行的版本：

eb --version
于 2014-12-02T19:58:02.727 回答