See The following phases occur in your local development environment and the Integration environment. Actual result. For example, you may want to add an Elasticsearch instance. See Use SSH to log in to the remote server and verify the connection to the MySQL database. All environment file systems are This phase puts the application in maintenance mode until deployment is complete.The last step runs a deployment script, which you can use to anonymize data in development environments, clear caches, and ping external, continuous integration tools. For Pro plans, the code is not deployed to the Staging or Production environments in these initial phases. However, you can view logs for every phase of the deployment in any environment using the Magento A set of YAML configuration files located in the project root directory define your Magento installation and describe its dependencies. Read more. Magento supports multiple deployment configurations using Google Cloud. This process helps us to sustain consistent configurations for any different environments. Magento 2 Developer Documentation. Magento Commerce (Cloud) 2.2 and later for Configuration Management/Pipeline Deployment What is Configuration Management To make a long story short, the Configuration Management (also known as Pipeline Deployment) process extracts all configuration settings from your Magento implementation (database) into a single PHP file. Trigger the deployment manually or by performing a merge, push, or synchronization of your environment. The built-in Git server detects this and verifies that the topology of your cluster is modified to your new needs.If you have a syntax error in a configuration file, our Git server refuses the push. This feature is available only for Production and Staging environments. You will gain the practical knowledge and skills required to deploy, test, troubleshoot, and operate the MOM product. See Verify available storage in the remote environmentâUse the Check the size of the upgraded database and verify that the Free up disk spaceâClear the cache, and clean the Use SSH to log in to the remote server and verify the following:Complete post-upgrade User Acceptance Testing UAT on Staging and Production environments and fix any issues related to third-party and custom extension upgrades. Steps to reproduce. You can merge to the Staging and Production environments using the Project Web Interface or using SSH and Magento Cloud CLI commands. See Ensure that you can connect to all three nodes in the Production environment using Prepare the environment by updating any environment-specific variables in the Production code, verifying service availability and compatibility, and making any other required configuration changes.Follow best practices for builds and deployment, and use the Ensure that any custom themes are compatible with the new Magento Commerce versionAfter upgrading third party and custom extensions, use the Review the Magento Commerce release notes and extension documentation to ensure that you have implemented any workarounds or configuration changes required to address known functional issues and bugs related to the upgraded Magento version and extensions.Ensure that the installed service versions are compatible with the new Magento Commerce version, and upgrade services as needed.