You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/routing/cloud/migrate-to-self-hosted.mdx
+10-14Lines changed: 10 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ description: Migrate all Apollo GraphOS cloud graphs (Serverless and Dedicated)
6
6
7
7
The Serverless and Dedicated plans end on [TODO SUNSET DATE]. After this date, cloud routers are no longer available.
8
8
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).
10
10
11
11
During the migration window, your cloud router continues to receive traffic, schema updates, and configuration updates. The migration window ends on [TODO SUNSET DATE].
12
12
@@ -16,7 +16,7 @@ This guide provides step-by-step instructions to migrate graphs on Serverless or
16
16
1. Change your graph's hosting mode to self-hosted
17
17
1. Deploy a self-hosted router
18
18
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
20
20
21
21
## Steps to migrate
22
22
@@ -32,20 +32,18 @@ In Studio, navigate to your graph's **Cloud Router** page and click the **Router
32
32
33
33
[TODO SCREENSHOT]
34
34
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.
36
36
37
37
#### Using the Rover CLI
38
38
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.
40
40
41
41
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.
42
42
43
43
```bash showLineNumbers={false}
44
44
rover cloud config fetch <GRAPH_REF>> router.yaml
45
45
```
46
46
47
-
[Install](/rover/getting-started) and [configure](/rover/configuring) the Rover CLI to run this command.
48
-
49
47
### Change the graph's hosting mode to self-hosted
50
48
51
49
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
79
77
80
78
## Frequently asked questions
81
79
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?
83
81
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].
85
83
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?
87
85
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.
89
87
90
88
```bash showLineNumbers={false}
91
89
rover cloud config fetch <GRAPH_REF>> router.yaml
92
90
```
93
91
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`:
0 commit comments