Removed legacy Cloud infrastructure info

_data/toc/cloud-guide.yml

@@ -23,12 +23,6 @@ pages:
         - label: Pro develop and deploy workflow
           url: /cloud/architecture/pro-develop-deploy-workflow.html
 
-        - label: Pro architecture (legacy)
-          url: /cloud/architecture/pro-architecture-legacy.html
-
-        - label: Add Staging and Production to Pro projects UI
-          url: /cloud/trouble/pro-env-management.html
-
     - label: Technologies and requirements
       url: /cloud/requirements/cloud-requirements.html
       children:

_data/whats-new.yml

@@ -2968,7 +2968,7 @@ entries:
   date: Oct 23 2017
 - description: Updated content for Magento Commerce (Cloud) for the updated Pro projects
     in [Manage your project](https://devdocs.magento.com/guides/v2.2/cloud/project/projects.html),
-    [Add Staging and Production to Pro projects](https://devdocs.magento.com/guides/v2.2/cloud/trouble/pro-env-management.html),
+    Add Staging and Production to Pro projects,
     [Deploy your store](https://devdocs.magento.com/guides/v2.2/cloud/live/stage-prod-live.html),
     [Deployment process](https://devdocs.magento.com/guides/v2.2/cloud/reference/discover-deploy.html),
     [Prepare to deploy to Staging and Production](https://devdocs.magento.com/guides/v2.2/cloud/live/stage-prod-migrate-prereq.html),
@@ -2985,7 +2985,7 @@ entries:
   date: Oct 18 2017
 - description: 'Update Magento Commerce (Cloud) content for new features for Pro plan:
     [Manage your project](https://devdocs.magento.com/guides/v2.2/cloud/project/projects.html),
-    [Add Staging and Production to Pro projects](https://devdocs.magento.com/guides/v2.2/cloud/trouble/pro-env-management.html),
+    Add Staging and Production to Pro projects,
     [Configure your project](https://devdocs.magento.com/guides/v2.2/cloud/project/project-webint-basic.html),
     [Create and manage users](https://devdocs.magento.com/guides/v2.2/cloud/project/user-admin.html),
     [Manage branches with the Interface](https://devdocs.magento.com/guides/v2.2/cloud/project/project-webint-branch.html),

_includes/cloud/hooks.md

@@ -1,8 +1,4 @@
-For technical reasons, you must enter a Support ticket to add your [`.magento.app.yaml`]({{ page.baseurl }}/cloud/project/project-conf-files_magento-app.html) file to Staging and Production environments. This affects all Pro projects created before and after October 23, 2017.
-
 You can request that we push `.magento.app.yaml`, `services.yaml`, and `routes.yaml`, set up cron jobs, and enable Xdebug and PHPUnit, which assists you in troubleshooting coding issues encountered during deployment. Because of the memory requirements, we recommend you disable Xdebug before your site is live.
 
-If you added your SSH keys to the Staging and Production environments, you can also directly SSH into the environment to use the Git CLI commands for deployments.
-
 {: .bs-callout .bs-callout-info}
 Optionally, you can replace the `hooks` section with a shell script that you can maintain without intervention. You need only to create a support ticket the first time you use the shell script.

_includes/cloud/note-pro-using-yaml-support.md

@@ -1,2 +1,2 @@
 {: .bs-callout .bs-callout-info}
-For Pro projects, the changes you make using this YAML file affects your Integration environment only. To make these changes in a Staging or Production environment, you must create a [Support ticket](http://support.magento.com).
+For Pro projects, you must create a [Support ticket](http://support.magento.com) to install or update services in Staging and Production environments. Indicate the service changes needed and include your updated `.magento.app.yaml` and `services.yaml` files in the ticket.

guides/v2.2/cloud/architecture/cloud-architecture.md

@@ -112,9 +112,7 @@ The [Starter plan architecture]({{ page.baseurl }}/cloud/basic-information/start
 
 The [Pro plan architecture]({{ page.baseurl }}/cloud/architecture/pro-architecture.html) has a global master with three environments:
 
--  **Integration**—The Integration environment provides a testable environment that includes a database, web server, caching, some services, environment variables, and configurations. You can develop, deploy, and test your code before merging to the Staging environment.
-    -  _Inactive_—You can have an unlimited number of inactive branches based on the Integration environment.
--  **Staging**—The Staging environment is for pre-Production testing and includes a database, web server, caching, services, environment variables, configurations, and services, such as Fastly.
--  **Production**—The Production environment includes a three-node, high-availability architecture for your data, services, caching, and store. This is your live, public store environment with environment variables, configurations, and third-party services.
-
-{% include cloud/note-pro-legacy.md %}
+- **Integration**—The Integration environment provides a testable environment that includes a database, web server, caching, some services, environment variables, and configurations. You can develop, deploy, and test your code before merging to the Staging environment.
+  - _Inactive_—You can have an unlimited number of inactive branches based on the Integration environment.
+- **Staging**—The Staging environment is for pre-Production testing and includes a database, web server, caching, services, environment variables, configurations, and services, such as Fastly.
+- **Production**—The Production environment includes a three-node, high-availability architecture for your data, services, caching, and store. This is your live, public store environment with environment variables, configurations, and third-party services.