连接后,eb cli 3.0没有从我现有的环境中设置我的设置

问题描述:

I created a customized Elastic Beanstalk environment from the web interface with configuration for VPC and other things. I now have a local repo that I want to connect to this created environment.

I ran eb init and was able to spot my environment and selected it.

I then ran eb deploy and it succesfully deployed my repo to my instances.

My confusion now is with regards to the option files. I thought eb init was supposed to fetch my configuration from the web interface and save it locally to .elasticbeanstalk?

The only thing it did right now is created a file .elasticbeanstalk/config.yml

branch-defaults:
  staging:
    environment: test-staging-env
global:
  application_name: test-staging
  default_ec2_keyname: test-staging-kp
  default_platform: php
  default_region: us-east-1
  profile: eb-cli
  sc: git

1) Where can I put my configuration for things such as

[aws:elasticbeanstalk:container:php:phpini]
allow_url_fopen=On
composer_options=--no-dev
display_errors=Off
document_root=/public
max_execution_time=60
memory_limit=256M
zlib.output_compression=Off

2) How can I fetch the configuration details done through the web interface to a file?

我从Web界面创建了一个自定义的Elastic Beanstalk环境,其中包含VPC和其他内容的配置。 我现在有一个本地仓库,我想连接到这个创建的环境。 p>

我运行了 eb init code>,并且能够发现我的环境并选择它。 / p>

然后我运行 eb deploy code>,它成功地将我的repo部署到我的实例。 p>

我现在的困惑是关于 选项文件。 我以为 eb init code>应该从Web界面获取配置并将其本地保存到.elasticbeanstalk? p>

它现在唯一做的就是创建一个文件 .elasticbeanstalk / config.yml strong> p>

 分支 -defaults:
 staging:
 environment:test-staging-env 
global:
 application_name:test-staging 
 default_ec2_keyname:test-staging-kp 
 default_platform:php 
 default_region:us-east-1 \  n profile:eb-cli 
 sc:git 
  code>  pre> 
 
 

1)我在哪里可以配置 p>

  [AWS:elasticbeanstalk:容器:PHP:phpini] 
allow_url_fopen =开
composer_options =  - 无-dev的
display_errors =关
document_root = /公共
max_execution_time = 60 
memory_limit = 256M 
zlib.output_compression =关 
  code>  pre> 
 
 

2)如何通过Web界面获取文件的配置详细信息? p> div>

eb init grabs the basic settings from your currently running environment. This includes:

  • Platform
  • Keypair name

Everything else is environment specific. If you would like to save your environments configuration to a file, you can use

eb config save

Typically, you can edit the configurations in place by using

eb config

You shouldn't need a file. But if you prefer to put those settings in a file you can create an ebextension file. Create a directory called .ebextensions and a file called [somename].config. Put the option settings in that file.