diff --git a/_data/toc/cloud-guide.yml b/_data/toc/cloud-guide.yml index beddf82ec06..8580beb5f33 100644 --- a/_data/toc/cloud-guide.yml +++ b/_data/toc/cloud-guide.yml @@ -38,14 +38,6 @@ pages: - label: Git url: /cloud/reference/git-integration.html - - label: Bitbucket integration - url: /cloud/project/bitbucket-integration.html - include_versions: ["2.0"] - - - label: GitHub integration - url: /cloud/project/project-integrate-github.html - include_versions: ["2.0"] - - label: SSH and sFTP url: /cloud/env/environments-ssh.html @@ -138,7 +130,6 @@ pages: - label: Set up PayPal url: /cloud/live/paypal-onboarding.html - exclude_versions: ["2.0"] - label: Set up Magento B2B url: /cloud/configure/setup-b2b.html @@ -165,22 +156,20 @@ pages: children: - label: Set up Fastly url: /cloud/cdn/configure-fastly.html - exclude_versions: ["2.0"] children: - label: Customize error pages url: /cloud/cdn/cloud-fastly-custom-response.html - label: Web Application Firewall url: /cloud/cdn/fastly-waf-service.html - exclude_versions: ["2.0"] - label: Image Optimization url: /cloud/cdn/fastly-image-optimization.html - exclude_versions: ["2.0"] - label: Custom VCL snippets url: /cloud/cdn/cloud-vcl-custom-snippets.html exclude_versions: ["2.0"] + children: - label: Reroute requests to a CMS backend url: /cloud/cdn/fastly-vcl-wordpress.html @@ -208,7 +197,7 @@ pages: - label: Build and deploy url: /cloud/project/magento-env-yaml.html - exclude_versions: ["2.0"] + children: - label: Set up notifications url: /cloud/env/setup-notifications.html @@ -224,28 +213,23 @@ pages: - label: Global variables url: /cloud/env/variables-global.html - exclude_versions: ["2.0"] - + - label: Build variables url: /cloud/env/variables-build.html - exclude_versions: ["2.0"] - + - label: Cloud variables url: /cloud/env/variables-cloud.html include_versions: ["2.1","2.2","2.3"] - label: Deploy variables url: /cloud/env/variables-deploy.html - exclude_versions: ["2.0"] - label: Post-deploy variables url: /cloud/env/variables-post-deploy.html - exclude_versions: ["2.0"] - + - label: Working with variables url: /cloud/env/working-with-variables.html - exclude_versions: ["2.0"] - + - label: Routes url: /cloud/project/project-conf-files_routes.html children: @@ -267,20 +251,15 @@ pages: - label: Set up Redis service url: /cloud/project/project-conf-files_services-redis.html - - label: Set up Solr service - url: /cloud/project/project-conf-files_services-solr.html - include_versions: ["2.0"] - - label: Set up Elasticsearch service url: /cloud/project/project-conf-files_services-elastic.html - exclude_versions: ["2.0"] - + - label: Set up RabbitMQ service url: /cloud/project/project-conf-files_services-rabbit.html - label: Configuration management for store settings url: /cloud/live/sens-data-over.html - include_versions: ["2.1","2.2","2.3"] + include_versions: [2.2","2.3"] children: - label: Example of managing system-specific settings url: /cloud/live/sens-data-initial.html @@ -381,7 +360,6 @@ pages: - label: Reset cron jobs url: /cloud/trouble/reset-cron-jobs.html - exclude_versions: ["2.0"] - label: Resolve issues with encryption key url: /cloud/trouble/trouble-crypt-key-variable.html @@ -394,7 +372,6 @@ pages: - label: Restore configuration files url: /cloud/trouble/restore-configuration-files.html - exclude_versions: ["2.0"] - label: Site availability url: /cloud/trouble/site-availability.html @@ -408,17 +385,11 @@ pages: - label: Upgrades and patches url: /cloud/project/project-upgrade-parent.html children: - - label: Release notes for ece-tools - url: /cloud/release-notes/cloud-tools.html - exclude_versions: ["2.0"] - - label: Upgrade to use ece-tools url: /cloud/project/ece-tools-upgrade-project.html - exclude_versions: ["2.0"] - label: Update ece-tools version url: /cloud/project/ece-tools-update.html - exclude_versions: ["2.0"] - label: Apply custom patches url: /cloud/project/project-patch.html @@ -426,6 +397,5 @@ pages: - label: Upgrade Magento version url: /cloud/project/project-upgrade.html - - label: Upgrade from 2.0.4 (Cloud) - include_versions: ["2.0"] - + - label: Release notes + url: /cloud/release-notes/cloud-tools.html \ No newline at end of file diff --git a/guides/v2.2/cloud/release-notes/cloud-tools.md b/guides/v2.2/cloud/release-notes/cloud-tools.md index eeb18bc9318..cb925aa5324 100644 --- a/guides/v2.2/cloud/release-notes/cloud-tools.md +++ b/guides/v2.2/cloud/release-notes/cloud-tools.md @@ -8,7 +8,6 @@ functional_areas: redirect_from: - /guides/v2.2/cloud/release-notes/CloudReleaseNotes.html --- - The following updates describe the latest improvements to the `{{site.data.var.ct}}` package, which uses the following version sequence: `200..`. See [Upgrades and patches]({{ page.baseurl }}/cloud/project/project-upgrade-parent.html) for information about updating to the latest release of the `{{site.data.var.ct}}` package. @@ -17,6 +16,26 @@ The release notes include: - {:.new}New features - {:.fix}Fixes and improvements +## v2002.0.22 + +The `{{ site.data.var.ct }}` 2002.0.22 release changes the structure of the `{{ site.data.var.ct }}` package to decouple the release of `{{ site.data.var.ece }}` patches from the {{ site.data.var.ct }} release. Starting with this release, patches and critical fixes will be delivered using the [`magento/magento-cloud-patches`](https://github.com/magento/magento-cloud-patches) package, which is a new dependency for the `{{ site.data.var.ct }}` package. We made these changes to reduce complexity for scheduling release updates and working with community contributions. + +- {:.new}**Changes to the ece-tools package** + + - {:.new}Moved the {{ site.data.var.ee }} patches from the `{{ site.data.var.ct }}` package to a new [`magento/magento-cloud-patches`](https://github.com/magento/magento-cloud-patches) composer package. + + - {:.new}Updated the `composer.json` file for the `{{ site.data.var.ct }}` package to add a dependency for the `magento/magento-cloud-patches` v1.0.0 package. + +- {:.fix}**Patches and critical fixes**–Update your Cloud environments with `{{ site.data.var.ct }}` version 2002.0.22 to apply the following patches and critical fixes. These patches are included in the `magento/magento-cloud-patches` v1.0.0 package. + + - {:.fix}**Page Builder security patches for 2.3.1.x and 2.3.2.x releases**–Fixes an issue in Page Builder preview that allows unauthenticated users to access some templating methods that can be used to trigger arbitrary code execution over the network (RCE) resulting in global information leaks. This issue can occur when using unsupported versions of Page Builder with {{ site.data.var.ee }} versions 2.3.1 and 2.3.2. + + - {:.fix}**MSI patches**–Fixes issues that caused indexing errors and performance issues when using default inventory settings for managing stock. + + - {:.fix}**Backward Compatibility of new Mail Interfaces**-Fixes a backward incompatibility issue caused by the `Magento\Framework\Mail\EmailMessageInterface` PHP interface introduced in {{ site.data.var.ee }} v2.3.3. In the scope of this patch, the new `EmailMessageInterface` inherits from the old `MessageInterface`, and {{ site.data.var.ee }} core modules are reverted to depend on `MessageInterface`. + + - {:.fix}**Catalog pagination does not work on Elasticsearch 6.x**–Fixes a critical issue with search result pagination that affects customers using Elasticsearch 6.x as the catalog search engine. + ## v2002.0.21 - {:.new}**Docker updates**— @@ -63,9 +82,7 @@ The release notes include: - {:.new}**Docker Updates**— - - {:.new}You can now perform functional testing using the - `{{site.data.var.ct}}` package in the Docker environment. - See[Functional testing in Docker]({{page.baseurl}}/cloud/docker/docker-development-testing.html). + - {:.new}You can now perform functional testing using the `{{site.data.var.ct}}` package in the Docker environment. See [Functional testing in Docker]({{page.baseurl}}/cloud/docker/docker-development-testing.html). - {:.new}Added support for configuring PHP modules using the `.magento.app.yaml` file. Any [PHP Extensions specified in the `.magento.app.yaml` file]({{page.baseurl}}/cloud/project/project-conf-files_magento-app.html#php-extensions) become available in the Docker PHP containers. @@ -77,8 +94,8 @@ The release notes include: - {:.fix}Updated the Sodium library from version 1.0.11 to version 1.0.18, and updated the Sodium PHP extension. - {:.bs-callout-warning} - {{site.data.var.ece}} customers must submit a support ticket to upgrade the libsodium package on Pro Production and Staging environments prior to upgrading to {{site.data.var.ee}} 2.3.2. Currently, you cannot upgrade Starter environments to {{site.data.var.ee}} 2.3.2. + {:.bs-callout-warning} + {{site.data.var.ece}} customers must submit a support ticket to upgrade the libsodium package on Pro Production and Staging environments prior to upgrading to {{site.data.var.ee}} 2.3.2. Currently, you cannot upgrade Starter environments to {{site.data.var.ee}} 2.3.2. - {:.fix}Added the `analysis-icu` and the `analysis-phonetic` Elasticsearch plugins to all Docker images. @@ -124,9 +141,9 @@ The release notes include: - {:.new}**New Docker Container**—Added a [TLS termination proxy container]({{page.baseurl}}/cloud/docker/docker-development.html#varnish-container) to facilitate the Varnish SSL termination over HTTPS. - - {:.new}**New Docker Image**—Added a Node.js image to support Gulp and other capabilities, such as Jasmine JS Unit Testing. + - {:.new}**New Docker Image**—Added a Node.js image to support Gulp and other capabilities, such as Jasmine JS Unit Testing. - - {:.new}**Docker build modes**—Now you can choose to launch the Docker environment in [Production mode or Developer mode]({{page.baseurl}}/cloud/docker/docker-config.html#launch-modes). Developer mode supports active development with full, writable filesystem permissions. + - {:.new}**Docker build modes**—Now you can choose to launch the Docker environment in [Production mode or Developer mode]({{page.baseurl}}/cloud/docker/docker-config.html#launch-modes). Developer mode supports active development with full, writable filesystem permissions. - {:.fix}Fixed an issue that caused Docker deploy to fail with a `Name or service not known` error if the cache is configured for a service that is not available. Now, you can remove a service from the [`.magento/services.yaml` file]({{page.baseurl}}/cloud/project/project-conf-files_services.html). The Docker configuration generator updates the service in the `docker/config.php.dist` file automatically. @@ -134,7 +151,7 @@ The release notes include: - {:.fix}Fixed an issue with the Docker compose `db-dump` command that erased existing dumps. -- {:.fix}Fixed an issue that assigned Redis `session`, `default`, and `page_cache` cache storage to the same database ID. + - {:.fix}Fixed an issue that assigned Redis `session`, `default`, and `page_cache` cache storage to the same database ID. - {:.new}**Environment variable updates**— @@ -142,9 +159,9 @@ The release notes include: - {:.new}Added the **SCD_MAX_EXECUTION_TIMEOUT** environment variable so you can increase the time to complete the static content deployment from the `.magento.env.yaml` file. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#scd_max_execution_time), the [build variables]({{ page.baseurl }}/cloud/env/variables-build.html#scd_max_execution_time), and the [global variables]({{ page.baseurl }}/cloud/env/variables-global.html#scd_max_execution_time). - - {:.new}Added the **MAGENTO_CLOUD_LOCKS_DIR** environment variable to configure the path to the mount point for the lock provider on the cloud infrastructure. The lock provider prevents the launch of duplicate cron jobs and cron groups. This variable is supported on {{ site.data.var.ee }} version 2.2.5 and later and automatically configured. See the definition in [Cloud variables]({{ page.baseurl }}/cloud/env/variables-cloud.html). + - {:.new}Added the **MAGENTO_CLOUD_LOCKS_DIR** environment variable to configure the path to the mount point for the lock provider on the cloud infrastructure. The lock provider prevents the launch of duplicate cron jobs and cron groups. This variable is supported on {{ site.data.var.ee }} version 2.2.5 and later and automatically configured. See the definition in [Cloud variables]({{ page.baseurl }}/cloud/env/variables-cloud.html). - - {:.fix}Changed the **SCD_THREADS** environment variable default values to automatically determine the optimal value based on the detected CPU thread count. See the updated definitions in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#scd_threads) and the [build variables]({{ page.baseurl }}/cloud/env/variables-build.html#scd_threads). + - {:.fix}Changed the **SCD_THREADS** environment variable default values to automatically determine the optimal value based on the detected CPU thread count. See the updated definitions in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#scd_threads) and the [build variables]({{ page.baseurl }}/cloud/env/variables-build.html#scd_threads). - {:.fix}Fixed an issue with a patch for DB Isolation Mechanism that caused an error when upgrading to {{site.data.var.ece}} version 2002.0.16. @@ -161,7 +178,7 @@ The release notes include: {:.bs-callout .bs-callout-info} The `{{site.data.var.ct}}` version 2002.0.17 includes an important security patch. See [Tech Resources: Magento Open Source Patches](https://magento.com/tech-resources/download#download2288). -- {:.new}**Service updates**—Supported by Magento versions 2.2.8 and later 2.2.x versions. +- {:.new}**Service updates**—Supported by the following Magento versions: 2.2.8 and later 2.2.x, 2.3.1 and later 2.3.x - Added support for Elasticsearch version 6.x. @@ -247,13 +264,13 @@ The `{{site.data.var.ct}}` version 2002.0.17 includes an important security patc - Added a [Cron container]({{page.baseurl}}/cloud/docker/docker-development.html#cron-container) based on the PHP-CLI image. - - Added the following services to the Docker build: + - Added the following services to the Docker build: - - RabbitMQ 3.5 and 3.7 + - RabbitMQ 3.5 and 3.7 - - ElasticSearch 1.7, 2.4, and 5.2 + - ElasticSearch 1.7, 2.4, and 5.2 - - Redis 3.2 and 4.0 + - Redis 3.2 and 4.0 - Now you have the DB dump capability when using the Cloud Docker [database container]({{page.baseurl}}/cloud/docker/docker-development.html#database-container). Also, you can [share files]({{page.baseurl}}/cloud/docker/docker-development.html#sharing-data-between-host-machine-and-container) between a host machine and a container using the `docker/mnt` directory. @@ -287,9 +304,9 @@ The `{{site.data.var.ct}}` version 2002.0.17 includes an important security patc - Now maintenance mode is enabled at the start of the deploy phase and disabled at the end. If the deployment fails, the site remains in maintenance mode until the deployment issues are resolved. Previously, the site returned to production mode even if the deployment failed. - - Reworked the deploy phase validation checks to downgrade the error level for the following deployment issues from `CRITICAL` to `WARNING` so that the deployment completes. Previously, these issues caused the deployment to fail. + - Reworked the deploy phase validation checks to downgrade the error level for the following deployment issues from `CRITICAL` to `WARNING` so that the deployment completes. Previously, these issues caused the deployment to fail. - - Environment configuration contains incorrect values for deploy or cloud variables. + - Environment configuration contains incorrect values for deploy or cloud variables. - The Elasticsearch version on the cloud infrastructure is incompatible with the version of the elasticsearch/elasticsearch module supported by {{ site.data.var.ece }}. See the [Elasticsearch troubleshooting article](https://support.magento.com/hc/en-us/articles/360015758471-Deployment-fails-or-interrupts-with-cloud-log-error-Elasticsearch-version-is-not-compatible-with-current-version-of-magento) in the Magento Support Knowledgebase. @@ -333,13 +350,13 @@ The `{{site.data.var.ct}}` version 2002.0.17 includes an important security patc - Added an Elasticsearch compatibility check to warn users about Elasticsearch configuration issues. Now, the deployment fails if the version of Elasticsearch service on the server is incompatible with {{site.data.var.ee}}. Previously, the deployment succeeded even if the Elasticsearch version was incompatible, which caused product catalog issues after site deployment. - You can resolve the incompatibility by [submitting a Support ticket]({{ page.baseurl }}/cloud/trouble/trouble.html) to upgrade Elasticsearch to a compatible version, or change the {{site.data.var.ee}} configuration to specify a compatible version of the Elasticsearch PHP client. + You can resolve the incompatibility by [submitting a Support ticket]({{ page.baseurl }}/cloud/trouble/trouble.html) to upgrade Elasticsearch to a compatible version, or change the {{site.data.var.ee}} configuration to specify a compatible version of the Elasticsearch PHP client. - - For {{site.data.var.ee}} version 2.1.x to 2.2.2, upgrade Elasticsearch to version 2.4. + - For {{site.data.var.ee}} version 2.1.x to 2.2.2, upgrade Elasticsearch to version 2.4. - - For {{site.data.var.ee}} version 2.2.3 and later, upgrade Elasticsearch to version 5.2. + - For {{site.data.var.ee}} version 2.2.3 and later, upgrade Elasticsearch to version 5.2. - - If you have Elasticsearch 1.x or 2.x and do not want to upgrade, update the {{site.data.var.ee}} Elasticsearch PHP client version requirement in composer.json to `"elasticsearch/elasticsearch": "~2.0"`. + - If you have Elasticsearch 1.x or 2.x and do not want to upgrade, update the {{site.data.var.ee}} Elasticsearch PHP client version requirement in composer.json to `"elasticsearch/elasticsearch": "~2.0"`. - Improved validation of environment variables to identify configuration settings that can cause conflicts during the build, deploy, and post-deploy phases. For example, a warning message displays during the install and upgrade process if the global setting for static content deployment conflicts with settings on the build or deploy phase. @@ -485,7 +502,7 @@ The ece-tools version 2002.0.11 is required for 2.2.4 compatibility. ## v2002.0.9 -{:.bs-callout .bs-callout-info} +{.bs-callout-info} You must [upgrade the {{site.data.var.ece}} metapackage]({{ site.baseurl }}/guides/v2.2/cloud/project/project-upgrade-parent.html) to get this and all future updates. - {:.new}**ece-tools**—The `{{site.data.var.ct}}` package now supports Magento 2.1.x. @@ -497,6 +514,7 @@ You must [upgrade the {{site.data.var.ece}} metapackage]({{ site.baseurl }}/guid - {:.fix}**Environment variables**— - The use of `env:STATIC_CONTENT_THREADS` was deprecated and will be removed in a future release. Use the [SCD_THREADS]({{page.baseurl}}/cloud/env/variables-deploy.html#scd_threads) instead. + - The `STATIC_CONTENT_EXCLUDE_THEMES` environment variable was deprecated. You must use the `SCD_EXCLUDE_THEMES` environment variable instead. - {:.fix}**Logging**—We simplified logging around built-in patching operations. diff --git a/guides/v2.3/cloud/release-notes/cloud-tools.md b/guides/v2.3/cloud/release-notes/cloud-tools.md deleted file mode 100644 index aff78c73162..00000000000 --- a/guides/v2.3/cloud/release-notes/cloud-tools.md +++ /dev/null @@ -1,510 +0,0 @@ ---- -group: cloud-guide -title: Release notes for ece-tools -functional_areas: - - Cloud - - Setup - - Configuration -redirect_from: - - /guides/v2.3/cloud/release-notes/CloudReleaseNotes.html ---- - - -The following updates describe the latest improvements to the `{{site.data.var.ct}}` package, which uses the following version sequence: `200..`. See [Upgrades and patches]({{ page.baseurl }}/cloud/project/project-upgrade-parent.html) for information about updating to the latest release of the `{{site.data.var.ct}}` package. - -The release notes include: - -- {:.new}New features -- {:.fix}Fixes and improvements - -## v2002.0.21 - -- {:.new}**Docker updates**— - - - {:.new}**New Docker Images**—Supported by Magento versions 2.3.3 and later - - - PHP version 7.3. - - - Varnish Cache 6.2.0 - - - {:.new}Added support to apply custom hook configuration specified in `.magento.app.yaml` in the Docker environment. Previously, the Docker environment supported only the default hook configuration. - - - {:.new}Docker ENV files are no longer generated during the Docker build, and the `docker:config:convert` command is deprecated. The corresponding data is now stored in the `docker-compose.yml` file. - - - {:.new}**Updated PHP image**–Added Node.js to the PHP Docker image to support node, npm, and grunt-cli capabilities. - -- {:.new}**Environment variable updates**– - - - {:.new}Added the **LOCK_PROVIDER** deploy variable to configure the lock provider which prevents the launch of duplicate cron jobs and cron groups. See the variable description in the [deploy variables]({{page.baseurl}}/cloud/env/variables-deploy.html#lock_provider) topic. - - - {:.new}Added the **CONSUMERS_WAIT_FOR_MAX_MESSAGES** environment variable to configure how consumers process messages from the message queue when using the `CRON_CONSUMERS_RUNNER` environment variable to manage cron jobs. See the variable description in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#consumers_wait_for_max_messages) topic. - - - {:.fix}Fixed an issue that can cause database deadlock errors when the `consumers_runner` cron job starts multiple instances of the same consumer on different nodes. Now, if you have enabled the [**CRON_CONSUMERS_RUNNER**]({{ page.baseurl }}/cloud/env/variables-deploy.html#cron_consumers_runner) deploy variable in your environment, the `consumers_runner` job uses the `single-thread` option to start one instance of each consumer on only one node. - - - {:.fix}Fixed an issue affecting [**WARM_UP_PAGES**]({{ page.baseurl }}/cloud/env/variables-post-deploy.html#warm_up_pages) functionality that uses a default store URL. Now, if the `config:show:default-url` command cannot fetch a base URL, then the URL from the MAGENTO_CLOUD_ROUTES variable is used. - -- {:.new}Updated the logging information returned by the `module:refresh` command. Now, you can see a detailed list of enabled modules in the `cloud.log` file. - -- {:.new}Improved version compatibility validation and warning notifications for compatibility issues between Magento version and installed services, such as Elasticsearch, RabbitMq, Redis, and DB. - -- {:.new}Updated interactive validations for service compatibility to reflect supported versions for the new {{ site.data.var.ee }} 2.3.3 and 2.2.10 releases. See [Service versions]({{ page.baseurl }}/cloud/project/project-conf-files_services.html#service-versions). - -- {:.fix}Improved the log message returned when the cron job management process in the deploy phase tries to stop a cron job that has already finished to clarify that this issue is not an error. Changed the log level from `INFO` to `DEBUG`. - -- {:.fix}Fixed an issue when running the `setup:upgrade` command that did not interrupt the deployment process when a failure occurred during the `app:config:import` task. - -- {:.new}Changed the default log level for the file handler to `debug` to reduce the amount of detail in the log displayed in the Project Web Interface, while still providing detailed information for debugging. - -- {:.fix}Fixed an issue that caused an error with static content deployment during build. After a Magento installation and `{{site.data.var.ct}}` config dump, an error occurred if there was no locale specified for the admin user in the `config.php` file. Now, there is a default locale for the admin user in the `config.php` file. - -- {:.fix}Fixed an `Undefined index error` that occurs when a Magento Cloud CLI command fails in an environment that is not configured with a secure URL (https). Now, the ece-tools package uses the base URL (http) if the secure URL is not available. - -## v2002.0.20 - -- {:.new}**Docker Updates**— - - - {:.new}You can now perform functional testing using the `{{site.data.var.ct}}` package in the Docker environment. See [Functional testing in Docker]({{page.baseurl}}/cloud/docker/docker-development-testing.html). - - - {:.new}Added support for configuring PHP modules using the `.magento.app.yaml` file. Any [PHP Extensions specified in the `.magento.app.yaml` file]({{page.baseurl}}/cloud/project/project-conf-files_magento-app.html#php-extensions) become available in the Docker PHP containers. - - - {:.new}There are new commands available to improve the Docker command line experience. See the [`bin/docker` section of the Docker reference]({{page.baseurl}}/cloud/docker/docker-quick-reference.html#bindocker). - - - {:.new}Added the ability to use Mutagen.io to synchronize files during development between the local host and Docker. See [Docker prerequisites]({{page.baseurl}}/cloud/docker/docker-config.html#prerequisites). - - - {:.fix}Corrected the default path when using the Docker environment. Now, when you use SSH to log in to the Docker container, you are at the Magento root in the `/app` directory, as expected. - - - {:.fix}Updated the Sodium library from version 1.0.11 to version 1.0.18, and updated the Sodium PHP extension. - - {:.bs-callout-warning} - {{site.data.var.ece}} customers must submit a support ticket to upgrade the libsodium package on Pro Production and Staging environments prior to upgrading to {{site.data.var.ee}} 2.3.2. Currently, you cannot upgrade Starter environments to {{site.data.var.ee}} 2.3.2. - - - {:.fix}Added the `analysis-icu` and the `analysis-phonetic` Elasticsearch plugins to all Docker images. - - - {:.fix}Improved validations: When using options for the `docker:build` command, you must provide a value when using an option. Also, added validation for the Node version when using the `docker:build run` command. - -- {:.new}**Environment variable updates**— - - - {:.new}Added support for database table prefixes using the [DATABASE_CONFIGURATION environment variable]({{page.baseurl}}/cloud/env/variables-deploy.html#database_configuration). - - - {:.new}Added the **FORCE_UPDATE_URLS** deploy variable to update Magento base URLs when deploying to Pro and Starter production and staging environments. See the definition in the [deploy variables]({{page.baseurl}}/cloud/env/variables-deploy.html#force_update_urls) content. - - - {:.new}Added the **TTFB_TESTED_PAGES** post-deploy variable to configure _Time to First Byte_ page tests to check Magento Commerce application performance on sites deployed to Cloud infrastructure. See the variable description in [post-deploy variables]({{ page.baseurl }}/cloud/env/variables-post-deploy.html). - - - {:.fix}Fixed an issue with multi-threaded SCD, which caused random failures in static content deployment. The workaround involved setting the **SCD_THREADS** variable to `1`. You can now increase the count as needed. See the definitions in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#scd_threads) and the [build variables]({{ page.baseurl }}/cloud/env/variables-build.html#scd_threads). - - - {:.fix}You can configure the **WARM_UP_PAGES** environment variable to cache single pages, multiple domains, and multiple pages. See the expanded definition in the [post-deploy variables]({{page.baseurl}}/cloud/env/variables-post-deploy.html#warm_up_pages) content. - - - {:.fix}Added the `pub/static/.htaccess` file to the exclude list. [Fix submitted by Björn Kraus of PHOENIX MEDIA GmbH](https://github.com/magento/ece-tools/pull/455). - -- {:.fix}Fixed an error when all validation messages were showing as `Critical` if at least one critical level validator returned an error. - -- {:.fix}Fixed an issue that caused a deployment failure if the Magento base URL did not exist in the database. - -- {:.new}Added a new **`env:config:show` command** to the `{{site.data.var.ct}}` package that displays environment services, routes, or variables. See [Services, routes, and variables]({{page.baseurl}}/cloud/reference/ece-tools-reference.html#services-routes-and-variables). [Feature submitted by Vladimir Kerkhoff](https://github.com/magento/ece-tools/pull/486). - -- {:.fix}Decreased the `cloud.log` log level for shell output from `info` to `debug`. - -- {:.fix}Added the `--remove-definers (-d)` option to the `ece-tools db-dump` command to remove definers from the dump file. - -## v2002.0.19 - -- {:.fix}Fixed an issue that overwrites the `env.php` file during a deploy, resulting in a loss of custom configurations. This update ensures that {{site.data.var.ece}} updates the `env.php` file with every deployment, while preserving custom configurations. - -## v2002.0.18 - -- {:.new}**Docker Updates**— - - - {:.new}Now, the Docker environment supports the cron configuration defined in the [crons property of the .magento.app.yaml file]({{page.baseurl}}/cloud/project/project-conf-files_magento-app.html#crons). - - - {:.new}**New Docker Container**—Added a [TLS termination proxy container]({{page.baseurl}}/cloud/docker/docker-development.html#varnish-container) to facilitate the Varnish SSL termination over HTTPS. - - - {:.new}**New Docker Image**—Added a Node.js image to support Gulp and other capabilities, such as Jasmine JS Unit Testing. - - - {:.new}**Docker build modes**—Now you can choose to launch the Docker environment in [Production mode or Developer mode]({{page.baseurl}}/cloud/docker/docker-config.html#launch-modes). Developer mode supports active development with full, writable filesystem permissions. This improves the developer experience by providing an easier way to develop and sync extensions, for example. - - - {:.fix}Fixed an issue that caused Docker deploy to fail with a `Name or service not known` error if the cache is configured for a service that is not available. Now, you can remove a service from the [`.magento/services.yaml` file]({{page.baseurl}}/cloud/project/project-conf-files_services.html). The Docker configuration generator updates the service in the `docker/config.php.dist` file automatically. - - - {:.new}Added interactive validations for service compatibility. Now, if a requested service is incompatible with the Magento version or other services, the _interactive mode_ prompts the user with a message and a choice to continue. See the [Service versions]({{page.baseurl}}/cloud/docker/docker-config.html#service-versions) available for Docker. Use the `-n` option to skip the interactivity for CICD purposes. - - - {:.fix}Fixed an issue with the Docker compose `db-dump` command that erased existing dumps. - -- {:.fix}Fixed an issue that assigned Redis `session`, `default`, and `page_cache` cache storage to the same database ID. - -- {:.new}**Environment variable updates**— - - - {:.new}The new **ELASTICSUITE\_CONFIGURATION** environment variable retains your customized service settings between deployments. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#elasticsuite_configuration) content. - - - {:.new}Added the **SCD_MAX_EXECUTION_TIMEOUT** environment variable so you can increase the time to complete the static content deployment from the `.magento.env.yaml` file. See the definition in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#scd_max_execution_time), the [build variables]({{ page.baseurl }}/cloud/env/variables-build.html#scd_max_execution_time), and the [global variables]({{ page.baseurl }}/cloud/env/variables-global.html#scd_max_execution_time). - - - {:.new}Added the **MAGENTO_CLOUD_LOCKS_DIR** environment variable to configure the path to the mount point for the lock provider on the cloud infrastructure. The lock provider prevents the launch of duplicate cron jobs and cron groups. This variable is supported on {{ site.data.var.ee }} version 2.2.5 and later and automatically configured. See the definition in [Cloud variables]({{ page.baseurl }}/cloud/env/variables-cloud.html). - - - {:.fix}Changed the **SCD_THREADS** environment variable default values to automatically determine the optimal value based on the detected CPU thread count. See the updated definitions in the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#scd_threads) and the [build variables]({{ page.baseurl }}/cloud/env/variables-build.html#scd_threads). - -- {:.fix}Fixed an issue with a patch for DB Isolation Mechanism that caused an error when upgrading to {{site.data.var.ece}} version 2002.0.16. - -- {:.fix}Added a patch that replaces _Google Image Charts_ with _Image-Charts_. See the DevBlog article [Google Image Charts deprecation and update for M1](https://community.magento.com/t5/Magento-DevBlog/Google-Image-Charts-deprecation-and-update-for-M1/ba-p/125006). - -- {:.fix}Added validation for the [SEARCH_CONFIGURATION variable]({{ page.baseurl }}/cloud/env/variables-deploy.html#search_configuration). Deploy fails when the 'engine' option is not set and `_merge` is not required. - -- {:.fix}Fixed an issue that exposed sensitive data after an exception occurs. Now the sensitive information is masked appropriately. - -- {:.fix}Improved the fault-tolerant settings of the {{site.data.var.ece}} package. In the case when Magento 2 cannot read data from the Redis `slave` instance, a reading is made from the Redis `master` instance. See [REDIS_USE_SLAVE_CONNECTION]({{ page.baseurl }}/cloud/env/variables-deploy.html#redis_use_slave_connection). - -## v2002.0.17 - -{:.bs-callout .bs-callout-info} -The `{{site.data.var.ct}}` version 2002.0.17 includes an important security patch. See [Tech Resources: Magento Open Source Patches](https://magento.com/tech-resources/download#download2288). - -- {:.new}**Service updates**—Supported by Magento versions 2.3.1 and later 2.3.x versions. - - - Added support for Elasticsearch version 6.x. - - - Added support for Redis version 5.0. - -- {:.new}**New Docker images**—Added the following services to the Docker build: - - - Elasticsearch 6.5 - - - Redis 5.0 - -- {:.new}**New environment variable**—Previously, there was a hard-coded timeout for SCD compression. Now you can configure the SCD compression timeout using the **SCD_COMPRESSION_TIMEOUT** environment variable. See the definitions in the [build variables]({{page.baseurl}}/cloud/env/variables-build.html#scd_compression_timeout) and the [deploy variables]({{ page.baseurl }}/cloud/env/variables-deploy.html#scd_compression_timeout) content. - -- {:.fix}Added the `--use-rewrites` option to the Magento install command so that it uses web server rewrites for generated links in the storefront and Admin access to improve security and customer experience. - -- {:.fix}Added timestamps to the `var/log/install_upgrade.log` file so that it shows dates for the Magento installation and upgrade events. - -## v2002.0.16 - -- {:.new}**Docker updates**— - - - Now, the default service configuration generated in the Docker environment is the same as the default configuration in the Cloud template. - - - You can send mail from your Docker environment using the [`sendmail` service]({{page.baseurl}}/cloud/docker/docker-development.html#sendmail-service). - - - Added the ability to [configure Xdebug]({{page.baseurl}}/cloud/docker/docker-development-debug.html) to debug in the Cloud Docker environment. - - - Fixed an issue with web service permissions when generating the `docker-compose.yml` file. - -- {:.new}**Upgrade improvement**—Added validation to confirm that the `autoload` property in the `composer.json` file contains required configuration changes before upgrading to {{ site.data.var.ee }} v2.3. See [Upgrade Magento version]({{site.baseurl }}/guides/v2.3/cloud/project/project-upgrade.html). - -- {:.new}The compression process in deploying static content now includes all assets—natively generated or customized—and occurs during the build phase at the beginning of the [`build:transfer` section]({{ page.baseurl }}/cloud/project/project-conf-files_magento-app.html#hooks). Previously, the compression process occurred before applying custom minification and bundling of static assets. [Fix submitted by Rafael Garcia Lepper from Tryzens Limited](https://github.com/magento/ece-tools/pull/413). - -- {:.fix}Fixed a database connection error that occurred during deployment immediately after configuring an additional database and service relationship. Also, this fix addresses an issue that occurred during the configuration process of MBI for Starter. For Starter, this upgrade is a "must have" for using MBI. - -- {:.fix}Fixed a validation issue with the database configuration that caused the deploy process to fail. - -- {:.fix}Updated the constraint with the appropriate version of the `symfony/yaml` package to use with [PHP constants]({{page.baseurl}}/cloud/project/magento-env-yaml.html#php-constants). Constant parsing does not work when using a `symfony/yaml` package version earlier than 3.2. [Fix submitted by Vladimir Kerkhoff](https://github.com/magento/ece-tools/pull/404). - -- {:.new}**Environment configuration check**—Added validation to check the PHP version and warn users if they are not using the latest recommended version. - -- {:.fix}Fixed an issue with processing malformed JSON variables. Now, if a JSON variable causes a syntax error, a warning appears in the `cloud.log` file and deployment continues using the default variable. - -- {:.fix}Fixed a connection error that occurred during deployment immediately after disabling the Redis service. - -- {:.new}**Logging changes**—Updated the [log level]({{ page.baseurl }}/cloud/env/log-handlers.html#log-levels) from `Info` to `Notice` for the following build and deploy process events: - - - Begin and end of the process for reconciling installed modules in `composer.json` with shared configuration settings in the `app/etc/config.php` file - - - Begin and end of the configuration validation process - - - Begin and end of the `setup:di:compile` process for generating classes - -- {:.new}**New environment variables**— - - - **[RESOURCE_CONFIGURATION deploy variable]({{page.baseurl}}/cloud/env/variables-deploy.html#resource_configuration)**—Use this variable to map a resource name to a database connection. - - - **[X_FRAME_CONFIGURATION global variable]({{ page.baseurl }}/cloud/env/variables-global.html#x_frame_configuration)**—Use this variable to change the `X-Frame-Options` header configuration for rendering a {{ site.data.var.ee }} page in a ``, `