Update info about getting Fastly credentials #3479
Conversation
meker12
added
2.1.x
Major Update
|
|
||
| If you have an existing Fastly account that has been configured with the same apex and sub-domains used for your {{ site.data.var.ece }} project, remove those domains from your Fastly account before submitting the request to add Fastly services to your project environments. See [Working with Domains](https://docs.fastly.com/guides/basic-configuration/working-with-domains) in the Fastly documentation. | ||
|
|
||
| **DNS delegation** |
There was a problem hiding this comment.
I'd like some clarification on this section. I'll meet with you to discuss, @meker12
| subdomains of shoes.mystore.com and socks.mystore.com managed by an existing | ||
| Fastly account, you need to remove them from that account before going live with | ||
| Fastly and {{site.data.var.ece}}. | ||
| {{ site.data.var.ece }} projects do not require a dedicated Fastly account or account owner. Instead, each project environment has its own set of Fastly credentials (API key and service ID) that you use to configure and manage Fastly services from the Magento Admin UI. You also use these credentials to submit requests to the Fastly API service. |
There was a problem hiding this comment.
Replace "its own set" with "a set" or something better.
|
|
||
| We'll provide you with the following credentials for your Staging and Production | ||
| services: | ||
| - For Pro projects, include the origin URLs for your Production and Staging sites. |
There was a problem hiding this comment.
Origin is in caps in some places. Is this a reference to the Origin shields or is it a reference to a particular remote?
There was a problem hiding this comment.
an inherited sentence -- it's actually referring to the site URLs ... so origin is not correct here.
| file in that location. If you do not locate this file, please enter a ticket | ||
| for [Support]({{ page.baseurl }}/cloud/trouble/trouble.html) asking to have the | ||
| file added. We can help provide this credentials file. | ||
| If the domains included in your Cloud project are associated with an existing Fastly service account, see [Multiple Fastly accounts and assigned domains](#domain). |
There was a problem hiding this comment.
This seems choppy. Maybe "If your project domains link to an existing..."
|
|
||
| ### Multiple Fastly accounts and assigned domains {#domain} | ||
|
|
||
| If you have an existing Fastly account that has been configured with the same apex and sub-domains used for your {{ site.data.var.ece }} project, remove those domains from your Fastly account before submitting the request to add Fastly services to your project environments. See [Working with Domains](https://docs.fastly.com/guides/basic-configuration/working-with-domains) in the Fastly documentation. |
There was a problem hiding this comment.
Don't need "that has been".
| For details, review your Fastly accounts and [documentation](https://docs.fastly.com/) | ||
| to remove the domains. This may include removing and updating CNAME records and | ||
| more. | ||
| To get these credentials, Magento needs to add your project environments to the Fastly service account for {{ site.data.var.ece }} and add the Fastly account credentials to your project environment configurations. |
There was a problem hiding this comment.
When it says "add your project environments", does it mean you are adding a link?
There was a problem hiding this comment.
Yes-- link is the right concept. Thanks.
| @@ -258,12 +274,15 @@ handle your blog. | |||
| - us-west-1 => sjc-ca-us | |||
| - us-west-2 => sea-wa-us | |||
|
|
|||
| 4. Modify the timeout values (in microseconds for the connection to the | |||
| 1. Modify the timeout values (in microseconds for the connection to the | |||
| @@ -337,16 +362,21 @@ a Magento extension for GeoIP handling, you may need to verify the features with | |||
| Fastly options. | |||
|
|
|||
| 1. In the **Fastly Configuration** section, expand **Advanced**. | |||
There was a problem hiding this comment.
Locations are italicized and action elements are bold.
|
|
||
| 1. Click **Save Config** at the top of the page. | ||
|
|
||
| 1. After page reload, click *Upload VCL to Fastly* in the *Fastly Configuration* section. |
There was a problem hiding this comment.
If you click Upload VCL to Fastly, then it should be bold.
| @@ -124,6 +125,13 @@ This displays the following page, which enables you to configure settings, [vari | |||
|
|
|||
|  | |||
|
|
|||
| ### Environment configuration variables | |||
| On the Variables page, you can view, create, and manage environment variables for your project. For example, after we add your project to the {{ site.data.var.ece }} Fastly service account, you can view the Fastly API key and service ID credentials as shown in the following example. | |||
There was a problem hiding this comment.
Variables is a tab.
Use a colon after example.
|
|
||
|  | ||
|
|
||
| You can also view environment variables using the Magento CLI `magento-cloud variable:get -e <environment ID>` command. See [List and review variables]({{ page.baseurl }}/cloud/before/before-setup-env-2_clone.html#variablelist). |
There was a problem hiding this comment.
Also splits the verb...
This command is long enough that it is difficult to see in the sentence. It might be more user friendly if they are able to copy it using the Copy function of a code block.
|
running tests |
|
@meker12 please add |
|
@meker12 please move |
This PR is a:
List all affected URLs:
whatsnew
Added information about retrieving Fastly credentials from project environment variables and updated information about how to manage Magento Commerce Cloud project domains associated with an existing Fastly account. See Get Fastly credentials.