From dda6526be8204c2fd689e4bd4e833e275691a1cf Mon Sep 17 00:00:00 2001 From: Stephen Barlow Date: Tue, 11 Oct 2022 13:54:15 -0700 Subject: [PATCH] Fix some broken links --- docs/source/commands/graphs.mdx | 4 ++-- docs/source/commands/readmes.mdx | 4 ++-- docs/source/commands/subgraphs.mdx | 8 ++++---- docs/source/commands/supergraphs.mdx | 4 ++-- docs/source/commands/template.mdx | 2 +- 5 files changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/source/commands/graphs.mdx b/docs/source/commands/graphs.mdx index 1af3abd1e..1f85bee95 100644 --- a/docs/source/commands/graphs.mdx +++ b/docs/source/commands/graphs.mdx @@ -23,7 +23,7 @@ Run the `graph fetch` command, like so: rover graph fetch my-graph@my-variant ``` -The argument `my-graph@my-variant` in the example above specifies the ID of the Studio graph you're fetching from, along with which [variant](/studio/org/graphs/#managing-variants) you're fetching. +The argument `my-graph@my-variant` in the example above specifies the ID of the Studio graph you're fetching from, along with which [variant](/studio/org/graphs/#variants) you're fetching. > You can omit `@` and the variant name. If you do, Rover uses the default variant, named `current`. @@ -82,7 +82,7 @@ Use the `graph publish` command, like so: rover graph publish my-graph@my-variant --schema ./schema.graphql ``` -The argument `my-graph@my-variant` in the example above specifies the ID of the Studio graph you're publishing to, along with which [variant](/studio/org/graphs/#managing-variants) you're publishing to. +The argument `my-graph@my-variant` in the example above specifies the ID of the Studio graph you're publishing to, along with which [variant](/studio/org/graphs/#variants) you're publishing to. > You can omit `@` and the variant name. If you do, Rover publishes the schema to the default variant, named `current`. diff --git a/docs/source/commands/readmes.mdx b/docs/source/commands/readmes.mdx index 0445ec80c..5250d70b8 100644 --- a/docs/source/commands/readmes.mdx +++ b/docs/source/commands/readmes.mdx @@ -3,9 +3,9 @@ title: Rover README commands description: Publish and retrieve your graph variant's README --- -These Rover commands enable you to publish and fetch the [README](/studio/org/graphs/#the-readme-page) associated with a particular graph variant. +These Rover commands enable you to publish and fetch the [README](/studio/studio-graph-features/#the-readme-page) associated with a particular graph variant. -READMEs are [Markdown-based](/studio/org/graphs/#supported-markdown) and support Apollo-specific shortcodes, which are documented [here](/studio/org/graphs/#readme-shortcodes). +READMEs are [Markdown-based](/studio/studio-graph-features/#supported-markdown) and support Apollo-specific shortcodes, which are documented [here](/studio/studio-graph-features/#readme-shortcodes). ## Fetching a README from Apollo Studio diff --git a/docs/source/commands/subgraphs.mdx b/docs/source/commands/subgraphs.mdx index f4620364d..8d5283177 100644 --- a/docs/source/commands/subgraphs.mdx +++ b/docs/source/commands/subgraphs.mdx @@ -18,7 +18,7 @@ Rover commands that interact with subgraphs begin with `rover subgraph`. ## Fetching a subgraph schema -These commands enable you to fetch the schema for a single subgraph in a federated graph. To instead fetch the API schema for a supergraph, use [`rover graph fetch`](./graphs#graph-fetch). To fetch the supergraph schema, use [`rover supergraph fetch`](./supergraph#supergraph-fetch). +These commands enable you to fetch the schema for a single subgraph in a federated graph. To instead fetch the API schema for a supergraph, use [`rover graph fetch`](./graphs#graph-fetch). To fetch the supergraph schema, use [`rover supergraph fetch`](./supergraphs#supergraph-fetch). ### `subgraph fetch` @@ -32,7 +32,7 @@ Run the `subgraph fetch` command, like so: rover subgraph fetch my-graph@my-variant --name accounts ``` -The argument `my-graph@my-variant` in the example above is a [graph ref](../conventions/#graph-refs) that specifies the ID of the Studio graph you're fetching from, along with which [variant](/studio/org/graphs/#managing-variants) you're fetching. +The argument `my-graph@my-variant` in the example above is a [graph ref](../conventions/#graph-refs) that specifies the ID of the Studio graph you're fetching from, along with which [variant](/studio/org/graphs/#variants) you're fetching. > You can omit `@` and the variant name. If you do, Rover uses the default variant, named `current`. @@ -50,7 +50,7 @@ rover subgraph introspect http://localhost:4001 The subgraph must be reachable by Rover. The subgraph does _not_ need to have introspection enabled. -> Unlike a standard introspection query, the result of `rover subgraph introspect` _does_ include certain directives (specifically, directives related to federation like `@key`). This is possible because the command uses a separate introspection mechanism provided by the [Apollo Federation subgraph specification](/federation/federation-spec/#enhanced-introspection-with-query_service). +> Unlike a standard introspection query, the result of `rover subgraph introspect` _does_ include certain directives (specifically, directives related to federation like `@key`). This is possible because the command uses a separate introspection mechanism provided by the [Apollo Federation subgraph specification](/federation/subgraph-spec/#enhanced-introspection-with-query_service). #### Watching for schema changes @@ -137,7 +137,7 @@ rover subgraph publish my-supergraph@my-variant \ --routing-url "https://my-running-subgraph.com/api" ``` -The argument `my-supergraph@my-variant` in the example above is a [graph ref](../conventions/#graph-refs) that specifies the ID of the Studio graph you're publishing to, along with which [variant](/studio/org/graphs/#managing-variants) you're publishing to. +The argument `my-supergraph@my-variant` in the example above is a [graph ref](../conventions/#graph-refs) that specifies the ID of the Studio graph you're publishing to, along with which [variant](/studio/org/graphs/#variants) you're publishing to. > You can omit `@` and the variant name. If you do, Rover publishes the schema to the default variant, named `current`. diff --git a/docs/source/commands/supergraphs.mdx b/docs/source/commands/supergraphs.mdx index 01b4a8d01..c8b362025 100644 --- a/docs/source/commands/supergraphs.mdx +++ b/docs/source/commands/supergraphs.mdx @@ -30,7 +30,7 @@ rover supergraph fetch my-supergraph@my-variant > To fetch a supergraph's API schema instead, use [`graph fetch`](./graphs/#fetching-a-schema). [Learn about different schema types.](/federation/federated-types/overview/) -The argument `my-supergraph@my-variant` in the example above specifies the ID of the Studio graph you're fetching from, along with which [variant](/studio/org/graphs/#managing-variants) you're fetching. +The argument `my-supergraph@my-variant` in the example above specifies the ID of the Studio graph you're fetching from, along with which [variant](/studio/org/graphs/#variants) you're fetching. > You can omit `@` and the variant name. If you do, Rover uses the default variant, named `current`. @@ -53,7 +53,7 @@ cat ./supergraph.yaml | rover supergraph compose --config - ### YAML configuration file -The supergraph configuration file (often referred to as `supergraph.yaml`) includes configuration options for each of your [subgraphs](/federation/subgraphs). The following example file configures a supergraph with two subgraphs (`films` and `people`): +The supergraph configuration file (often referred to as `supergraph.yaml`) includes configuration options for each of your [subgraphs](/federation/building-supergraphs/subgraphs-overview/). The following example file configures a supergraph with two subgraphs (`films` and `people`): ```yaml title="supergraph.yaml" federation_version: 2 diff --git a/docs/source/commands/template.mdx b/docs/source/commands/template.mdx index 3df1cd8d6..986054277 100644 --- a/docs/source/commands/template.mdx +++ b/docs/source/commands/template.mdx @@ -14,7 +14,7 @@ graph BT; gateway --- serviceA & serviceB & serviceC; ``` -Rover template commands help you create new subgraphs from templated projects in various [federation-compatible implementations](/federation/supported-subgraphs). +Rover template commands help you create new subgraphs from templated projects in various [federation-compatible implementations](/federation/building-supergraphs/supported-subgraphs). This feature helps you quickly start up a new GraphQL project or explore various subgraph implementations. If you want to contribute a new template, [open an issue here](https://github.com/apollographql/rover/issues/new/choose)!