Removed legacy Cloud infrastructure info #5125
Conversation
meker12
added
Internal Dev
There was a problem hiding this comment.
This cleans up a lot, and we need this. But this is a lot to review because I think that you creeped in scope many times. I understand the temptation; these improvements help greatly, but still a lot to review! In the spirit of your cleansing, I added a couple of quick suggestions to clear some command steps.
| * For Starter, we recommend you create a `staging` branch from Master, then branch from `staging` for development. | ||
| * For Pro, you want to branch from Development (Integration `master`). | ||
| - For Starter, we recommend you create a `staging` branch from Master, then branch from `staging` for development. | ||
| - For Pro, you want to branch from the development branch (Integration `master`). |
There was a problem hiding this comment.
| - For Pro, you want to branch from the development branch (Integration `master`). | |
| - For Pro, create a development branch from the Integration environment. |
| - `magento-cloud user:add` adds a user to the project | ||
| - `magento-cloud user:delete` deletes a user | ||
| - `magento-cloud user:list [users]` lists project users | ||
| - `magento-cloud user:role` views or change a user's role | ||
|
|
||
| For example, the following command adds the project administrator (`admin`) role to `[email protected]` and gives her `contributor` privileges to the `development` environment: | ||
|
|
||
| The following prompts are displayed: |
There was a problem hiding this comment.
| The following prompts are displayed: |
|
|
||
| * **Staging and Production environments in the UI for Pro projects**. Starting October 23, 2017, all projects created using the free 30-day trial or provisioned for new accounts includes Staging and Production environments in the Project Web Interface. Existing accounts created before October 23, 2017 can enter a ticket to be updated. For more information, see [Add Staging and Production to Pro projects UI]({{ site.baseurl }}/guides/v2.2/cloud/trouble/pro-env-management.html). | ||
| * **Staging and Production environments in the UI for Pro projects**. Starting October 23, 2017, all projects created using the free 30-day trial or provisioned for new accounts includes Staging and Production environments in the Project Web Interface. See |
m2-community-project
bot
added
Progress: changes requested
and removed
Progress: review
labels
Co-Authored-By: hguthrie <[email protected]>
| url: /cloud/architecture/pro-architecture-legacy.html | ||
|
|
||
| - label: Add Staging and Production to Pro projects UI | ||
| url: /cloud/trouble/pro-env-management.html |
There was a problem hiding this comment.
There are still links to this topic in the whatsnew topic. It will likely fail link checking. Should this redirect somewhere?
There was a problem hiding this comment.
👍 Added a redirect to the Pro develop and deploy workflow topic.
|
|
||
| ### Migrate your `.magento.app.yaml` file {#pro-yaml} | ||
|
|
||
| **Important:** If you have **not modified** the default deployment hooks or configurations, skip this step and continue with [Get your Pro access URLs](#pro-urls). Only migrate the file if you modified the deployment hooks or added configuration updates. | ||
| {:.bs-callout-important} |
There was a problem hiding this comment.
The important class doesn't exist. You can use info, warning, or tip.
meker12
dismissed
hguthrie’s stale review
Made the requested change, but the reviewer is on vacation. Can make further updates to content on a separate PR as needed.
|
running tests |
|
Hi @meker12, thank you for your contribution! |
Purpose of this pull request
Update Cloud documentation to remove legacy infrastructure references and instructions:
Validation
Affected DevDocs pages
whatsnew
Updated Magento Commerce Cloud Guide to remove obsolete instructions for configuring legacy environments and migrating legacy Cloud environments to use the Project Web UI. Legacy environments are those provisioned prior to October 23, 2017.