title: Why should I ignore .elastbeanstalk folder?
body: <p>I have an Elastic Beanstalk Python Application.</p>
  
  <p>So I already made my build script where I do generate a deploy.zip file that I do deploy into EB. It does work just as it suppose to.</p>
  
  <p>So after building my script for building an artifact (my deploy.zip) that is compatible with EB, I began to work on configuring EB cli for using <code>eb deploy</code> in my gitlab-ci, so it will deploy to EB homologation server when there be a commit on development branch and into EB production when get into master. ( right now I'm just working on homologation server).</p>
  
  <p>So I did read the documentation and notice that eb would build the artifactory by itself. But as I already had my own build script, this Deploying an <a href="http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3-configuration.html" rel="noreferrer">Artifact Instead of the Project Folder</a> so I made a <code>.elasticbeanstalk</code> folder and a <code>config.yml</code> in it with the follow configuration.</p>
  
  <pre><code>deploy:
       artifact: deploy.zip
  </code></pre>
  
  <p>So I did a <code>eb init</code>, did set everything (region, id, key and selected my existing project.</p>
  
  <p>When I did <code>eb deploy</code> it worked just as it suppose to. So I did suspect that <code>eb</code> was making de artifactory by itself, so I checked the config file and notice that <code>eb</code> had add a bunch of other config into the file, my deploy config was there, so for another test I did deleted my <code>deploy.zip</code> so when I did a <code>eb deploy</code> it failed just as it suppose to. </p>
  
  <p>Until this point everything was running just as I was planning to, so I did a <code>git status</code> for checking before adding the <code>.elasticbeanstalk</code> folder into git. For my surprise the folder was not been listed and the <code>.gitignore</code> file was changed. When checking the <code>.gitignore</code> it had the <code>.elasticbeanstalk</code> in it.</p>
  
  <p>So it got me alert about if I should add this folder into the git, as de default behavior of <code>eb</code> is to add it into ignore.</p>
  
  <p>I was planning to commit the eb configurations and set the keys using environment variables as is says in <a href="http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3-configuration.html" rel="noreferrer">Configuration Settings and Precedence</a> session.</p>
  
  <p>I've tried to run <code>eb deploy</code> without the configurations just passing env vars before the command, something like <code>AWSAccessKeyId=&lt;access_key&gt; AWSSecretKey=&lt;secret_key&gt;  eb deploy</code>, but it says that I should run <code>eb init</code> before it.</p>
  
  <p>So shouldn't I git my <code>eb</code> configuration? If not how should I procede for a CI deploy with EB ?</p>