![]() Delete the remote Git branch too? ĭeleting the remote Git branch removes the environment from the project. The environment is currently active: deleting it will delete all associated data.Īre you sure you want to delete the environment ? ĭeleting the environment places it in an inactive state. Respond to the prompts to delete the local environment and the corresponding remote environment. Optionally, you can delete more than one environment at a time by adding multiple environment IDs to the delete command. To delete the environment completely, you must also delete the corresponding remote Git branch.įetch updates from the remote server. The code is still available in the Git branch, but no longer contains the services or the database. When you delete an environment, the environment is set to inactive. See Manage user access to Cloud projects. ![]() You must be a project administrator, environment administrator, or Account Owner to perform this task. You cannot delete the master branch of any project. You cannot recover an environment after you delete it. Only delete an environment if you are certain that you no longer need it. Merge with the parent environment: magento-cloud environment:merge Create a snapshot of the environment.Īfter completing development, merge this branch to the parent:Ĭommit and push code changes: git add -A & git commit -m "Add message here" composer -no-ansi -no-interaction install -no-progress -prefer-dist -optimize-autoloader On your local workstation, change to your project directory.Ĭreate an environment based on the branch recommended for your project workflow. For Pro, create development branches based on the Integration branch.For Starter, consider creating a branch for staging, then create a development branch based on the staging branch.As stated earlier, you must create an environment using the magento-cloud environment:branch command or the Project Web Interface for the environment to become active. Create a branch for developmentĪfter cloning your project and updating the Adobe Commerce administrator account configuration, you can branch for development. See Integrations for information about using Git-based hosting services with Adobe Commerce on cloud infrastructure. To see a full list of magento-cloud CLI commands, use the magento-cloud list command. ![]() The following instructions use a combination of magento-cloud CLI commands and Git commands to clone your project to your local workstation. When run from a project directory, you can omit the -p parameter. Although you can run the commands from any directory, we recommend that you run them from a project directory. You can use them to connect to your project and manage your environments. The magento-cloud CLI commands are similar to Git commands. To manage the branches and environments with the Project Web Interface, see Manage branches with the Project Web Interface. ![]() For information about the environment architecture, see Starter architecture or Pro architecture. After you install the magento-cloud CLI and set up SSH keys for remote access to your cloud infrastructure, you can use magento-cloud CLI commands to manage the environments for your projects. To install the magento-cloud CLI, see the Cloud CLI reference. ![]()
0 Comments
Leave a Reply. |