2002.0.5

Changelog (29 related PRs)

• New features
  • Configure a cron consumer with an environment variable—You can now configure cron consumers using the new CRON_CONSUMERS_RUNNER environment variable.
  • Configuration scanning—We now scan for critical components during the build/deploy process and halt the process if the scan fails, which prevents unnecessary downtime due to the site being in maintenance mode.
  • Build/deploy notifications—We added a configuration file that you can use to set up Slack and/or email notifications for build/deploy actions in all your environments.
  • Static content compression—We now compress static content using gzip during the build and deploy phases. This compression, coupled with Fastly compression, helps reduce the size of your store and increase deployment speed. If necessary, you can disable compression using a build option or deploy variable.
  • Configuration management—We now auto-generate an app/etc/config.php file in your Git repository during the build phase if it does not already exist. The auto-generated file includes only a list of modules and extensions. If the file already exists, the build phase continues as normal. If you follow Configuration Management at a later time, the commands update the file without requiring additional steps.
  • Database dumps—We added a magento/ece-tools CLI command for creating database dumps in all environments. For Pro plan Production environments, this command only dumps from one of three high-availability nodes, so production data written to a different node during the dump may not be copied. We recommend putting the application in maintenance mode before doing a database dump in Production environments.
  • Cron interval limitations lifted—The default cron interval for all environments provisioned in the us-3, eu-3, and ap-3 regions is 1 minute. The default cron interval in all other regions is 5 minutes for Pro Integration environments and 1 minute for Pro Staging and Production environments. To modify your existing cron jobs, edit your settings in .magento.app.yaml or create a support ticket for Production/Staging environments.
• Resolved issues
  • We fixed an issue that was causing long deploy times due to the deploy process invoking the cache-clean operation before static content deployment.
  • We fixed an issue causing errors during the static content generation step of deployment on Production environments.
  • We fixed an issue preventing some magento/ece-tools commands from logging output to stderr.
  • We fixed an issue preventing base URL values in env.php from being updated in forked branches.
  • We fixed an issue causing the magento setup:install command to add an unsecure prefix (http://) to secure base URLs.
  • We fixed an issue preventing patch errors from causing deployment failures.
  • We fixed an issue preventing {{site.data.var.ct}} from halting execution and throwing an exception if no patches can be applied.
  • We fixed an issue causing errors when loading the storefront after enabling HTML minification in the Magento Admin.

2002.0.4

Changelog (2 related PRs)

• You can now manually reset stuck Magento cron jobs using a CLI command in all environments via SSH access. The deployment process automatically resets cron jobs.

2002.0.3

Changelog (1 related PR)

• We fixed an issue that was causing pages to time out because Redis was taking too long to read/write. You can now use the disable_locking parameter in Redis configurations to prevent this issue.

2002.0.2

Changelog (1 related PR)

• The RabbitMQ configuration process now obtains all required parameters automatically.

2002.0.1

Changelog (21 related PR)

• New features
  • ECE-Tools now supports scopes and static content deployment strategies. We have added the –s parameter with a default setting of quick for the static content deployment strategy. You can use the environment variable SCD_STRATEGY to customize and use these strategies with your build and deploy actions. This variable supports the options standard, quick, or compact. If you select compact, we override the STATIC_CONTENT_THREADS value with 1, which can slow deployment, especially in production environments. Not available in 2.1.
  • We have created a log file on environments to capture and compile build and deploy actions. The file is located in the var/log/cloud.log file inside the Magento root application directory.
• Resolved issues
  • Refactored the ECE-Tools package to make it compatible with Magento 2.2.0 and higher.
  • We fixed an issue that was preventing ECE-Tools from halting execution and throwing an exception if no patches can be applied.
  • We fixed an issue that was causing exceptions to be thrown when dependency injection (di) compilation is skipped during builds.
  • We fixed an issue that was causing the deploy process to overwrite custom Redis configurations in the env.php file.
  • We fixed an issue that was causing redirect loops due to disabled by default secure admin.

2002.0.0

Initial ECE-Tools Release

• This package is no longer compatible with other versions of Magento and should not be used.