2002.0.15
shiftedreality
released this
14 Nov 15:41
·
185 commits
to 2002.0
since this release
Changelog (21 related PRs)
- Docker updates—
- Now the Docker generator uses the services specified in the
.magento.app.yaml
and.magento/services.yaml
configuration files when building your Docker environment. You can choose a different service version using build parameters. - Added PHP 7.2 image—Added support for PHP 7.2 in Cloud Docker; updated the Launch Docker configuration to include the
docker:build --php
option to specify the version of PHP compatible with your Magento Commerce version. - Added a Cron container based on the PHP-CLI image.
- Added the following services to the Docker build:
- RabbitMQ 3.5 and 3.7
- ElasticSearch 1.7, 2.4, and 5.2
- Redis 3.2 and 4.0
- Now you have the DB dump capability when using the Cloud Docker database container. Also, you can share files between a host machine and a container using the
docker/mnt
directory.
- Now the Docker generator uses the services specified in the
- Configure with PHP constants—Added support for PHP constants in the
.magento.env.yaml
configuration file. - New environment variable—By default, only the Production environment has Google Analytics enabled. You can enable Google Analytics on the Staging and Integration environments using the
ENABLE_GOOGLE_ANALYTICS
environment variable. - Fixed an issue that removed customized cron configurations from the
env.php
file after a redeployment. Now, custom cron configurations safely remain in theenv.php
file. - Fixed inconsistencies in the messages and log levels for build, deploy, and post-deploy phases. Increased beginning and ending log message levels from
info
tonotice
for all phases and sub-phases. Added beginning and ending log messages, where appropriate. - Fixed an issue involving cron processes that prevented the start of the post-deploy phase, when configured. Now, if you have the post-deploy hook enabled, the cron processes are enabled again at the beginning of the post-deploy phase.
- Resolved an issue that prevented a successful installation of Magento when specifying a custom database configuration. Previously, the installation process used the database configuration from the
MAGENTO_CLOUD_RELATIONSHIP
variable even if you designated customized connection information in theDATABASE_CONFIGURATION
environment variable. - Corrected the
config:dump
command so that it includes each website locale in thesystem
section of theconfig.php
file. - Fixed an issue that resulted in warm-up errors during the post-deploy phase by correcting the source base URL reference.
- Fixed an issue that generated files improperly during the
setup:di:compile
process, which affected the Amazon Pay module.