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.