Why should I ignore the .elastbeanstalk folder?

I have a Python application from an elastic bean stitch.

So, I already created my build script where I create the deploy.zip file that I am deploying to EB. It works as expected.

So, after creating my script to create an artifact (my deploy.zip) compatible with EB, I started working on setting up EB cli for use eb deployin my gitlab-ci, so it will deploy EB homologations when the development process requires fixing to branch of development and production EB. (Now I just work on a homologation server).

So, I read the documentation and noticed that eb will build artifactory on its own. But since I already had my own build script, this is Artifact Deployment instead of the project folder , so I made a folder .elasticbeanstalkand a config.ymlin it with the subsequent configuration.

deploy:
     artifact: deploy.zip

So, I did eb init, installed everything (region, id, key and selected my existing project.

When I did eb deploy, he worked as he believed. Therefore, I suspected that I ebwas doing artifactory myself, so I checked the configuration file and noticed that I ebadded another configuration to the file, my deployment version was there, so for another test I did mine deploy.zip, so when I did eb deploy, it failed. as expected.

, , git status .elasticbeanstalk git. , , .gitignore . .gitignore .elasticbeanstalk.

, git, eb , .

eb , .

eb deploy , env vars , - AWSAccessKeyId=<access_key> AWSSecretKey=<secret_key> eb deploy, , eb init .

, git my eb? , CI EB?

+4
1

.elasticbeanstalk - , eb cli . - config.yml , . eb init, .

, , . , ssh, . . , .gitignore.

, test, pre-prod, prod, - . - , .

, - .ebextensions ...

- - , .

+3

Source: https://habr.com/ru/post/1691204/


All Articles