2002.0.16
Changelog (30 related PRs)
-
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 -
Added the ability to configure Xdebug to debug in the Cloud Docker environment.
-
Fixed an issue with web service permissions when generating the
docker-compose.yml
file.
-
-
Upgrade improvement—Added validation to confirm that the
autoload
property in thecomposer.json
file contains required configuration changes before upgrading to Magentgo v2.3. -
The compression process in deploying static content now includes all assets—naively generated or customized—and occurs during the build phase at the beginning of the
build:transfer
section. Previously, the compression process occurred before applying custom minification and bundling of static assets. -
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.
-
Fixed a validation issue with the database configuration that caused the deploy process to fail.
-
Updated the constraint with the appropriate version of the
symfony/yaml
package to use with PHP constants. Constant parsing does not work when using asymfony/yaml
package version earlier than 3.2. -
Environment configuration check—Added validation to check the PHP version and warn users if they are not using the latest recommended version.
-
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. -
Fixed a connection error that occurred during deployment immediately after disabling the Redis service.
-
Logging changes—Updated the log level from
Info
toNotice
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 theapp/etc/config.php
file - Begin and end of the configuration validation process
- Begin and end of the
setup:di:compile
process for generating classes
- Begin and end of the process for reconciling installed modules in
-
New environment variables—
- RESOURCE_CONFIGURATION deploy variable—Use this variable to map a resource name to a database connection.
- X_FRAME_CONFIGURATION global variable—Use this variable to change the
X-Frame-Options
header configuration for rendering a Magento page in a<frame>
,<iframe>
, or<object>
.
-
Environment variable updates—Changed the following environment variables:
- WARM_UP_PAGES—Added the capability to preload the cache for specified pages on all domains defined for a Magento store. Previously, if your site was configured with multiple domains, the post-deploy process failed to preload the cache for the specified pages on non-default domains and returned the following error in the post-deploy log:
ERROR: Warming up failed: <uri>
- SCD_COMPRESSION_LEVEL—Updated the documentation and the sample
.magento.env.yaml
file with the correct default values for SCD compression level. See the definitions in the build variables and the deploy variables content. - SCD_EXCLUDE_THEMES—This environment variable is deprecated. Use the
SCD_MATRIX
variable to control theme configuration. See the definitions in the build variables and the deploy variables content. - SCD_MATRIX—Fixed the validation process to prevent a problem that occurred when the
SCD_MATRIX
ignored a theme value that contained different character cases. See the definitions in the build variables and the deploy variables content. - ADMIN variables—
- Improved security when managing credentials for the Magento Admin user using environment variables. You can no longer use the
ADMIN_EMAIL
,ADMIN_USERNAME
, andADMIN_PASSWORD
environment variables to override admin credentials during upgrades. If you cannot access the Admin panel, use the Forgot password feature or the Magento CLIadmin:user:create
command to create a new admin user. ADMIN_EMAIL
is no longer required when upgrading or applying patches.
- Improved security when managing credentials for the Magento Admin user using environment variables. You can no longer use the
- WARM_UP_PAGES—Added the capability to preload the cache for specified pages on all domains defined for a Magento store. Previously, if your site was configured with multiple domains, the post-deploy process failed to preload the cache for the specified pages on non-default domains and returned the following error in the post-deploy log: