ÃÛ¶¹ÊÓƵ

OpenSearch—A»å»å±ð»å support for OpenSearch for ÃÛ¶¹ÊÓƵ Commerce versions 2.4.4, 2.4.3-p2, and 2.3.7-p3.

PHP—A»å»å±ð»å support for PHP 8.1.

symfony/process—A»å»å±ð»å the compatibility with symfony/process ^5.3.

Consumer multiple processes—A»å»å±ð»å a multiple_processes option so that you can specify the number of processes to spawn for each consumer. See the CRON_CONSUMERS_RUNNER variable description in the Deploy variables.

OpenSearch scheme and full host path—A»å»å±ð»å the ability to configure an Elasticsearch scheme and full host path.

AWS S3—Changed the method of AWS S3 enablement.

Fix driver_options reader—A»å»å±ð»å reading driver_options configuration for DB connection from the env.php file by ece-tools for validators.

Added support for Composer 2.0.

Updated composer requirements for symphony/console—Updated the ECE-Tools composer.json version requirements for the symphony/console package to fix an issue that caused the di:compile commands to fail with the following error: Incompatible argument type: Required type: int. Actual type: string

Updated the end-of-life software checks (eol.yaml) to include Elasticsearch 7.9.x.

Redis authentication credentials—A»å»å±ð»å the ability to read Redis authorization credentials from the relationships property during the deploy phase.

Elasticsearch authorization credentials—A»å»å±ð»å the ability to read Elasticsearch authorization credentials from the relationships property during the deploy phase.

Dedicated session storage service—A»å»å±ð»å redis-session as a second option for session storage. You can use the redis-session service to store session information and use the redis service for cache to provide better performance.

Deprecated SPLIT_DB messages—A»å»å±ð»å validator warning and critical messages for the deprecated SPLIT_DB option for ÃÛ¶¹ÊÓƵ Commerce 2.4.2 and its removal in ÃÛ¶¹ÊÓƵ Commerce 2.5.0.

Elasticsearch version from relationships—Fixed Service validator to retrieve the correct version of Elasticsearch from the relationships properties in Cloud Docker and integration environments.

Flexible Redis port validation—Redis can now validate the port in a custom cache connection from the server URL. For example, you can add your port number to your server URL as follows: server: 'tcp://rfs-store-simple-page-cache:26379'. This helps prevent validation errors where the port option is either missing or incorrect.

Upgrading to ÃÛ¶¹ÊÓƵ Commerce 2.4.2—Fixed the issue that required users to manually run bin/magento setup:upgrade to make their sites operational after upgrading to ÃÛ¶¹ÊÓƵ Commerce 2.4.2.

Remote storage—A»å»å±ð»å the REMOTE_STORAGE environment variable to enable Cloud Projects for remote storage of media files using a storage service, such as AWS S3. This configuration option is part of the ECE-Tools package, but is not supported on ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure.

New cloud:config:validate command—A»å»å±ð»å command php vendor/bin/ece-tools cloud:config:validate to validate the .magento.env.yaml configuration before pushing changes to the remote Cloud environment.

Flushing the opcache—A»å»å±ð»å support for the opcache.enable_cli PHP option to flush the OPcache before running the deploy hook. This configuration resets the cache configuration to ensure that the current configuration settings are applied on each deployment.

Validation of Aurora DB—Updated the database service validation so that it is compatible with the Aurora database.

New SCD_NO_PARENT environment variable—A»å»å±ð»å the SCD_NO_PARENT environment variable (for ÃÛ¶¹ÊÓƵ Commerce >=2.4.2) to manage the generation of static content for parent themes.

Memory limits and commands—Fixed an issue where php vendor/bin/ece-tools commands would not work if the size of the cloud.log file exceeded the PHP memory_limit. Instead of reading the entire cloud.log file into memory, we now only read a smaller subset of data from the log file.

Custom database connections—Fixed a .magento.env.yaml configuration issue in which custom database connections defined for DATABASE_CONFIGURATION were not used. The connection settings were not being added to app/etc/env.php.

Empty error logs—Fixed an issue that caused deployments to fail if the cloud.error.log was empty.

MariaDB 10.3 validation—Fixed validation of MariaDB 10.3 for ÃÛ¶¹ÊÓƵ Commerce 2.3.6-p1.

Cache:flush logging—Improved log entries to indicate the start and finish of the cache:flush step.

Added ECE-Tools support for the read-only pub/static directory when static content is set to deploy in the build stage.

Added support for Elasticsearch 7.9 and Redis 6 for compatibility with upcoming ÃÛ¶¹ÊÓƵ Commerce releases.

Updated the ECE-Tools composer.json to add a required dependency for the Quality Patches Tool. This fixes a circular dependency that existed between the ECE-Tools and magento-cloud-patches packages.

Added search-engine validation to ensure that elasticsearch is set for ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure 2.4 and later. If the validation fails, the deployment is stopped with a critical error message that suggests fixes for the issue. See Critical Errors, Deploy stage.

Added Elasticsearch validation to check the compatibility between the Elasticsearch service version and the ÃÛ¶¹ÊÓƵ Commerce version.

Updated the Elasticsearch compatibility error message to show the versions of Elasticsearch that are compatible with the ÃÛ¶¹ÊÓƵ Commerce Elasticsearch module. The error message now provides the specific Elasticsearch versions to install in your Cloud infrastructure so that it is compatible with the Elasticsearch module used by your version of ÃÛ¶¹ÊÓƵ Commerce. See Warning Errors, Deploy stage.

Added warning errors 2026 and 2027 for invalid MAGE_MODE environment variable setting. The only valid value is production. Before this fix, MAGE_MODE could be set to developer without deployment errors, only to cause errors later when trying to write to read-only files. See Warning Errors.

Fixed validation for Redis, RabbitMQ, and MySQL services to ensure that these versions are compatible with the ÃÛ¶¹ÊÓƵ Commerce version. Valid versions of these services are now written to the cloud.log.

Updated the cloud.log to include the concurrent requests limit for sending requests during cache warmup. This value is configured in the WARM_UP_CONCURRENCY post-deploy variable.

Added the schema.error.yaml file that includes all error and warning notifications that can occur during the build, deploy, and post-deploy process along with suggestions for resolving the errors. The information in this file is also available in the Cloud Guide for Commerce. See Error message reference for ece-tools.

Changed the Cloud error log (/var/log/cloud.error.log) entries to JSON format to make the log easier to parse programmatically.

Added additional error checks to build, deploy, and post-deploy processing and improved existing checks:

• Error code 2026—Failed to restore some data generated during the build phase to the mounted directories

• Error code 3004—Cannot create backup files

• Error code 102—A»å»å±ð»å additional checks for issues that occur when the env.php file is not writable

Added the QUALITY_PATCHES environment variable to specify one or more quality patches to apply during the deployment process. See Build variables.

Infrastructure updates—

• Logging improvements—Improved log-tracking capability by assigning exit codes to critical deploy errors and exposing the exit codes in error message notifications and log events. See Error message reference for ece-tools.

• Improved the process for database dumps (vendor/bin/ece-tools db-dump) and updated log messages to clarify that the database dump operation switches the application to maintenance mode, stops consumer queue processes, and disables cron jobs before the dump begins.

• Fixed an issue to ensure that the project URL is updated correctly when deploying to Staging and Production environments. Now, ece-tools uses the URL for the route with the primary:true attribute set in the project route configuration. See Deploy variables.

• Updated the generate.xml build scenario workflow for applying patches. Patches must be applied earlier to update ÃÛ¶¹ÊÓƵ Commerce to fix any issues that might cause the di:compile and module:refresh steps to fail.

• Fixed an issue in the installation process that incorrectly returns the Crypt key missing error. The crypt/key value is generated automatically during the installation.

Service updates—

• Added support for PHP 7.4 and MariaDB 10.4.

Environment variable updates—

• Added the SCD_USE_BALER variable to enable the Baler module for JavaScript bundling during the ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure build process. See the variable description in the build variables.

• Added the REDIS_BACKEND environment variable to configure the Redis backend model for Redis cache for ÃÛ¶¹ÊÓƵ Commerce 2.3.5 or later. See the variable description in the deploy variables.

CLI command updates—

• Updated the following CLI commands with an option for more detailed logging:

  • app:config:dump
  • app:config:import
  • module:enable

  The logging level for each call is determined by the configuration of the VERBOSE_COMMANDS variable in the .magento.env.yaml file.

Validation improvements—

• Elasticsearch 7.x compatibility checks—Updated Elasticsearch validation for Elasticsearch 7.x software compatibility checks.

• Updated service version and EOL validation checks—Updated validation to check installed service versions against ÃÛ¶¹ÊÓƵ Commerce 2.4. requirements.

• Fixed a validation issue so that the following post-deploy warning message displays only if the post-deploy hook configuration is missing from the .magento.app.yaml file:

  code language-text
  Your application does not have the "post_deploy" hook enabled.

• Added validation for Zend Framework dependencies—A»å»å±ð»å composer dependency validation for the Zend Framework which has migrated to the Laminas project. If the required dependencies are missing, the following error message displays during the build process.

  code language-text
  Required configuration is missing from the autoload section of the composer.json file. Add ("Laminas\Mvc\Controller\Zend\": "setupsrc/ Zend/Mvc/Controller/") to the `autoload -> psr-4` section. Then, re-run the "composer update" command locally, and commit the updated composer.json and composer.lock files.

  See Verify Zend Framework dependencies.

• Added validation for env.php file and data—A»å»å±ð»å checks for the env.php file and data during the install and upgrade process.

  • If the env.php file is missing from the installation, and the crypt/key value is not specified in the .magento.app.yaml file, the deployment fails with the following notification:

    code language-text
    The crypt/key key value does not exist in the ./app/etc/env.php file or the CRYPT_KEY cloud environment variable``Missing crypt key for upgrading Magento`.

  • If the installation does not include the env.php file, or the configuration contains only one cache type, the cron:enable command runs during the upgrade process to restore the file with all cache_types. The following notification is added to the log:

    code language-text
    Magento state indicated as installed but configuration file app/etc/env.php was empty or did not exist. Required data will be restored from environment configurations and from the .magento.env.yaml file.