Usage
Description
Pushes the provided operations to the control plane, enabling them to be used from the router when using the givengraph_name. Additionally, it registers the given client_name as a well-known client.
The operations file might be one of the following formats:
- Plain
.graphqlor.gqlfile - An Apollo operation manifest
- A Relay Query Map
Options
-n, --namespace: The namespace of the federated graph (Default: “default”).-c, --client-name <client-name>The client name / identifier to register these operations under. By default, the client name must be sent by the client at request time via thegraphql-client-nameHTTP header. When the router runs in manifest mode, the client name is used only for organizational structure in the Studio (e.g. you could use"default") and is not matched against incoming requests.-f, --file <filename>Filename to read operations from. This argument can be used multiple times to read operations from multiple files. See Description for a list of the supported file formats.-q, --quietDon’t produce any output, just exit with success or error. Intended for use in CI checks.--format <output-format>Specify an output format for the returned data. Support types includetext(the default) andjson.