我最近老AWS EB CLI工具（2.6.4）切换到最新的版本（3.0.10），并想知道如何确保迁移我的项目的配置，和什么样的配置文件，我应该保持。

I've recently switched from old AWS EB CLI tools (2.6.4) to the current ones (3.0.10) and am wondering how to ensure that my project's configuration is migrated, and what configuration files I should keep.

我已经运行（新版） EB的init 和现在，在我的项目的 .elasticbeanstalk 目录中，一个新的文件

I've run (the new version of) eb init and now have, in my project's .elasticbeanstalk directory, a new file

config.yml

随着几个那些人那里之前

along with several ones that were there before

config
optionsettings.sitetest-develop-env
optionsettings.sitetest-env

而这些都仍然需要;我可以删除;并需要采取以确保所有的旧的设置已迁移到（和正确的地方）的3.x的AWS EB CLI工具哪些步骤我？

which of these are still needed; which can I delete; and what steps to I need to take to ensure that all of the old settings have been migrated to (and to the right place for) the 3.x AWS EB CLI tools?

推荐答案

我直接使用最新版本（3.X）并没有意识到，在开始EB的2.6.x和EB CLI 3.X之间的差异。由于提出这个问题（+1）。

I used the latest version (3.x) directly and didn't realise the difference between eb 2.6.x and EB CLI 3.x at beginning. Thanks to raise this question (+1) .

下面是我从AWS弹性魔豆文件了。

Here is what I got from AWS Elastic Beanstalk documents.

老版本被称为 EB的2.6.x ，新的版本叫做 EB CLI 3.X ，配置这些版本之间的区别已经清楚的解释，这个网址 EB命令行界面

Old version is called eb 2.6.x, new version is called EB CLI 3.x, the configuration difference between these versions has been explained clearly by this url EB Command Line Interface

EB是一个命令行界面（CLI）的AWS弹性魔豆，你可以用它来快速，更轻松地部署应用程序。 AWS弹性魔豆支持EB的2.6.x和EB CLI 3.x的您可以使用EB CLI 3.X来管理您推出了采用EB的2.6.x或更早版本的EB环境。 EB的CLI将自动从使用EB如果环境运行创造的环境中检索设置。 与EB，EB CLI不存储选项设置本地的

为什么你有这些文件夹/文件（如配置，optionsettings.sitetest-开发-ENV，optionsettings.sitetest-envin）在您的环境，这里是解释的的Eb操作，这只是对 EB的2.6.x

Why you have these folder/files (such as config, optionsettings.sitetest-develop-env, optionsettings.sitetest-envin) in your environment, here is the explanation Eb Operations, that's only for eb 2.6.x

您可以使用配置文件中的的 .ebextensions / 的.conf文件* 目录中配置一些是在 相同的设置。 elasticbeanstalk / optionsettings 的文件。然而，对于在.elasticbeanstalk的设置值/ optionsettings将precedence在任何东西在.ebextensions / *。CONF如果设置被配置在这两个。此外，使用API​​，包括通过EB指定的任何选项设置，以后就不能在环境中使用.ebextensions配置文件更改。 You can use a configuration file in an .ebextensions/.conf* directory to configure some of the same settings that are in an .elasticbeanstalk/optionsettings file. However, the values for the settings in .elasticbeanstalk/optionsettings will take precedence over anything in .ebextensions/*.conf if the settings are configured in both. Additionally, any option setting that is specified using the API, including through eb, cannot later be changed in an environment using .ebextensions configuration files.

最后，回答你的问题。如果你已经升级的版本，以EB CLI 3.x的，那么你就可以清理这些文件，但你仍然需要保持 config.yml ，它在创建时 EB在EB CLI 3.X的init 。

Finally, answer your question. If you have upgraded the version to EB CLI 3.x, then you can clean these files, but you still need keep config.yml, it is created when eb init in EB CLI 3.x.