Skip to content

Commit b2c2878

Browse files
committed
Minor style updates
1 parent 7b98812 commit b2c2878

File tree

1 file changed

+10
-14
lines changed

1 file changed

+10
-14
lines changed

docs/source/routing/cloud/migrate-to-self-hosted.mdx

Lines changed: 10 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ description: Migrate all Apollo GraphOS cloud graphs (Serverless and Dedicated)
66

77
The Serverless and Dedicated plans end on [TODO SUNSET DATE]. After this date, cloud routers are no longer available.
88

9-
If you are on a Serverless or Dedicated plan, you will need to migrate your graphs to use self-hosted routers by [TODO SUNSET DATE]. After migration, move your organization to a [supported plan](https://www.apollographql.com/pricing).
9+
If you are on a Serverless or Dedicated plan, migrate your graphs to use self-hosted routers by [TODO SUNSET DATE]. After migrating your graphs, move your organization to a [supported plan](https://www.apollographql.com/pricing).
1010

1111
During the migration window, your cloud router continues to receive traffic, schema updates, and configuration updates. The migration window ends on [TODO SUNSET DATE].
1212

@@ -16,7 +16,7 @@ This guide provides step-by-step instructions to migrate graphs on Serverless or
1616
1. Change your graph's hosting mode to self-hosted
1717
1. Deploy a self-hosted router
1818
1. Validate and shift traffic to your self-hosted endpoint
19-
1. Move your organization to a supported plan
19+
1. Once all graphs have been migrated to self-hosted, move your organization to a supported plan
2020

2121
## Steps to migrate
2222

@@ -32,20 +32,18 @@ In Studio, navigate to your graph's **Cloud Router** page and click the **Router
3232

3333
[TODO SCREENSHOT]
3434

35-
If you cannot access the Cloud Router page (for example, if you have already changed your graph's hosting mode), use the Rover CLI to export the configuration.
35+
If you can't access the Cloud Router page (for example, if you have already changed your graph's hosting mode), use the Rover CLI to export the configuration.
3636

3737
#### Using the Rover CLI
3838

39-
Use the Rover CLI's [`cloud config fetch` command](/rover/commands/cloud#cloud-config-fetch).
39+
Use the [`cloud config fetch` command](/rover/commands/cloud#cloud-config-fetch). [Install](/rover/getting-started) and [configure](/rover/configuring) the Rover CLI to run this command.
4040

4141
Replace the `<GRAPH_REF>` placeholder in the following command with your own graph ref to download the router configuration YAML to a local `router.yaml` file.
4242

4343
```bash showLineNumbers={false}
4444
rover cloud config fetch <GRAPH_REF> > router.yaml
4545
```
4646

47-
[Install](/rover/getting-started) and [configure](/rover/configuring) the Rover CLI to run this command.
48-
4947
### Change the graph's hosting mode to self-hosted
5048

5149
In Studio, click the **Start the migration process** button at the top of the graph variant's page to change the graph's hosting mode to self-hosted.
@@ -79,22 +77,20 @@ After you migrate all graphs to self-hosted mode, navigate to [TODO] to move you
7977

8078
## Frequently asked questions
8179

82-
### What happens to my running cloud routers when I change my graph's hosting mode?
80+
### What happens to your running cloud routers when you change your graph's hosting mode?
8381

84-
Changing a graph's hosting mode does not affect running cloud routers. Cloud routers continue to receive traffic, emit telemetry, and receive schema and configuration updates until a [shutdown event occurs for Serverless routers](/graphos/routing/cloud/serverless#automatic-deletion-of-unused-routers) or the migration period ends on [TODO SUNSET DATE].
82+
Changing a graph's hosting mode doesn't affect running cloud routers. Cloud routers continue to receive traffic, emit telemetry, and receive schema and configuration updates until a [shutdown event occurs for Serverless routers](/graphos/routing/cloud/serverless#automatic-deletion-of-unused-routers) or the migration period ends on [TODO SUNSET DATE].
8583

86-
### How do I retrieve and update the configuration of my running cloud routers after converting to self-hosted mode?
84+
### How do you retrieve and update the configuration of your running cloud routers after converting to self-hosted mode?
8785

88-
Use the [Rover CLI's `cloud config fetch` command](/rover/commands/cloud#cloud-config-fetch) to fetch your cloud router configuration:
86+
Use the [`cloud config fetch` command](/rover/commands/cloud#cloud-config-fetch) to fetch your cloud router configuration. [Install](/rover/getting-started) and [configure](/rover/configuring) the Rover CLI to run this command.
8987

9088
```bash showLineNumbers={false}
9189
rover cloud config fetch <GRAPH_REF> > router.yaml
9290
```
9391

94-
Use the [Rover CLI's `cloud config update` command](/rover/commands/cloud#cloud-config-update) to update your running cloud routers' configuration. For example, to apply changes from a local `router.yaml`:
92+
Use the [`cloud config update` command](/rover/commands/cloud#cloud-config-update) to update your running cloud routers' configuration. For example, to apply changes from a local `router.yaml`:
9593

96-
```bash
94+
```bash showLineNumbers={false}
9795
rover cloud config update --file router.yaml <GRAPH_REF>
9896
```
99-
100-
[Install](/rover/getting-started) and [configure](/rover/configuring) the Rover CLI to run this command.

0 commit comments

Comments
 (0)