Update - WunderGraph

Usage

npx wgc subgraph update <name> [-r, --routing-url <url>] [--label [labels...]] [--readme <path-to-readme>]

Update is an irreversible action. However, the change will only be visible to the routers once the composition has been successful. Until then, the routers will operate with the most recent valid composition. Please use subgraph check to understand the impact of your change.

Description

The npx wgc subgraph update command allows you to update an existing subgraph on the Cosmo platform’s control plane. With this command, you can modify the routing URL and apply or change labels associated with the subgraph. Use npx wgc subgraph update -h to see all the available options.

If the subgraph was created as an Event-Driven Graph (EDG), attempting to provide any one of the following parameters will produce an error: routing-url, susbcription-url, subscription-protocol, or websocket-subprotocol.

Parameters

• <name>: The name of the subgraph you want to update. This should be the exact name of the subgraph you wish to modify.

Options

• -n, --namespace : The namespace of the monograph (Default: “default”).
• -r, --routing-url <url>: The updated routing URL of your subgraph. This URL defines the endpoint where the subgraph will fetch data from. Use this option to change the subgraph’s data source URL. If the subgraph is a gRPC service, must follow the format from the gRPC protocol ( https://grpc.github.io/grpc/core/md_doc_naming.html). Will produce an error if the subgraph is an Event-Driven Graph.
  • Example for a GraphQL subgraph: --routing-url http://new-domain.com/graphql
  • Example for a gRPC service: --routing-url dns:///new-domain.com:1300/
• --label [labels...]: The labels to apply or change for the subgraph. Labels are passed in the format <key>=<value> <key>=<value>, where each <key>=<value> pair represents a label key and its corresponding value. Use this option to update the subgraph’s metadata.
  • Example: --label team=A
• --unset-labels: This will remove all labels. It will not add new labels if both this and —labels option is passed.
• --subscription-url: Optionally, use a different URL for subscription requests. If no subscription URL is provided, the router URL is used for subscriptions. To remove a previously set subscription URL, use the flag without provided a URL argument. Will produce an error if the subgraph is an Event-Driven Graph.
• --subscription-protocol: Optionally, set a protocol to use for subscriptions. Will produce an error if the subgraph is an Event-Driven Graph. The available options are:
  • ws (default): Negotiate an appropriate protocol over websockets. Both graphql-ws and subscription-transport-ws are supported.
  • sse: Use Server-Sent Events with a GET request.
  • sse_post: Use Server-Sent events with a POST request.
• --readme <path-to-readme>: The path to the markdown file which describes the subgraph.
• --websocket-subprotocol: The subprotocol to use when subscribing to the subgraph. Will produce an error if the subgraph is an Event-Driven Graph. The supported protocols are auto(default), graphql-ws, and graphql-transport-ws. It should be used only if the subscription protocol is ws.
• --suppress-warnings: This flag suppresses any warnings produced by composition.

Examples

1. Update the routing URL of the subgraph “products”:

npx wgc subgraph update products -r http://new-domain.com/graphql

2. Update the labels for the subgraph “users”:

npx wgc subgraph update users --label team=B department=HR

Notes

• The npx wgc subgraph update command interacts with the Cosmo platform’s control plane to update the specified subgraph.
• If you want to update both the routing URL and labels, you can combine the options in a single command as demonstrated in the examples.