Git aws.push: 'aws.push' is not a git command

Question

From the directory of my site / application:

$ git aws.push git: 'aws.push' is not a git command. See 'git --help'. 

git --help does not help.

All the messages I read were written before the EB command line interface (CLI) 3.x.

I followed the official instructions here: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3-getting-set-up.html

And here: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_PHP_eb.sdlc.html

Unfortunately, the latter still says:

 $ export PATH=$PATH:<path to unzipped eb CLI package>/eb/linux/python2.7/ 

But I do not know this path, because I did not download or unpack the package. I installed awsebcli using pip according to the instructions in the first link above.

Everything else seems to be in place. I have WordPress configured and working locally (OS X / Apache) with a remote MySQL RDS database. Not that the content of the application matters. My AWS IAM credentials are being entered (via prompt).

eb create works! And it loads my local application (files) perfectly. But I do not want to create a new application / environment. I already have one, and I just want to git push my files to it.

1. How can I find /eb/linux/python2.7/ to set PATH?
2. Is there any other reason / solution?

Answer 1

Decision:

 eb deploy 

Turns off eb --help . Great help.

But, strangely enough, it was like I was sitting looking at the screen, and I remembered that I saw the eb deploy command somewhere else (on the website).

I tried. It worked.

If you are using AWS Elastic Beanstalk CLI 3.x ...

Do not use git aws.push !

Instead, use eb deploy to upgrade your application version.

Answer 2

I had the same problem. I used aws.push to update my application. Then I switched to a new computer, and I had to configure everything again.

you can use

 eb deploy 

However, depending on how you set up the project, you may need to map the deployment to a branch. Using:

 eb branch 

I was attached and wanted to make sure that I did not spoil the deployment by introducing any new problems into the production environment, and I wanted to use:

 git aws.push 

It can still be done.

Download an outdated version of the AWS Elastic Beanstalk command-line tool here

Then, from inside your repo, do AWSDevTools-RepositorySetup.sh . You can find this file in the zip file you just downloaded, AWS-ElasticBeanstalk-CLI-2.6.4 / AWSDevTools / Linux

Now run

 git aws.config 

After setting up, you can run git aws.push without any problems.

Now I use eb deploy, but I was in a binding and never used it and had no time to test it. So it worked for me.