Magento Commerce (Cloud) 2.1.3 and 2.0.11 Release Notes

These Release Notes provide up-to-date information about changes, additions, and fixes to the Magento Enterprise Cloud Edition for versions 2.1.3 and 2.0.11.

Changes in this release

Required update to .magento.app.yaml

Before you upgrade to version 2.1.3 or 2.0.11, you must add a rule to the web section of your .magento.app.yaml file. You must make the change in your local system, push it to your integration server, then, after upgrading, push the changes to staging and production.

Get started

Update .magento.app.yaml

Update your Elasticsearch configuration

This section discusses how to update your integration system to replace Solr with Elasticsearch. Currently, all Magento Enterprise Cloud Edition upgrades to 2.1.3 must perform these tasks.

Elasticsearch is supported by Magento Cloud Enterprise Edition 2.1.x only.

If you installed Magento Enterprise Cloud Edition 2.1.3 for the first time, you don’t need to do this because Elasticsearch is already the default search engine.

To use Elasticsearch on a staging or production system, open a Support ticket and request Elasticsearch.

After installing Elasticsearch, you must do a full index of your fulltext index. This process can take a while if the index is large.

The search functionality will be unavailable until the process completes.

To use Elasticsearch, you must perform all the tasks discussed in this section.

Get started

Step 1: Update .magento.app.yaml

Step 2: Update .magento/services.yaml

Step 3: Push the changes and redeploy the environment

Step 4: Get Elasticsearch connection information

This section discusses how to get connection information for Elasticsearch so you can configure the Magento application to use it as your search engine.

Step 5: Configure the Magento application to use Elasticsearch

Configure Magento using the instructions in the Magento configuration for Elasticsearch guide.

Fixed issue

Note the following issue in this release:

  • The magento setup:install command (used for deployment) succeeds in either a staging or production system if a Magento database already exists.

Magento Commerce Release Notes