-
Notifications
You must be signed in to change notification settings - Fork 425
[GM-835] Change --tag references to --variant for commands #819
Conversation
@@ -35,7 +35,7 @@ The rest of this article focuses on managing a federated graph with the Apollo p | |||
|
|||
If you're running a distributed GraphQL infrastructure, where federated services [compose](https://www.apollographql.com/docs/apollo-server/federation/federation-spec/#fetch-service-capabilities) to form a complete schema, tracking the history of the graph and its underlying services is essential. Running `apollo service:push` from within CI/CD on any federated service registers the overall schema of the graph and updates the graph's [managed configuration](#managed-configuration). | |||
|
|||
To push a single federated service to Apollo, run `apollo service:push` in CI/CD with the `--serviceName`, `--endpoint`, and `--serviceURL` tags. The CLI will know where to fetch your service's capabilities based on the `--endpoint` flag, and the `--serviceURL` flag indicates where the federated service can be reached by the gateway. The `--serviceName` flag is used as a unique identifier for each federated service. | |||
To push a single federated service to Apollo, run `apollo service:push` in CI/CD with the `--serviceName`, `--endpoint`, and `--serviceURL` flags. The CLI will know where to fetch your service's capabilities based on the `--endpoint` flag, and the `--serviceURL` flag indicates where the federated service can be reached by the gateway. The `--serviceName` flag is used as a unique identifier for each federated service. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was just a typo fix
|
||
To specify the schema tag to register operations on, pass an additional `--tag <TAG>` argument (`npx apollo client:push --tag <TAG>`). | ||
To specify the schema variant to register operations on, pass an additional `--variant <VARIANT>` argument (`npx apollo client:push --variant <VARIANT>`). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should really be graph variant
@@ -213,9 +213,9 @@ const gateway = new ApolloGateway({ | |||
|
|||
</ExpansionPanel> | |||
|
|||
#### 5.1 Optionally, set the schema tag | |||
#### 5.1 Optionally, set the graph variant (AKA schemaTag) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
leaving this reference since the Apollo Server / plugin option is still schemaTag
@@ -340,8 +340,8 @@ const server = new ApolloServer({ | |||
willUpdateManifest(newManifest, oldManifest) { | |||
metrics.report( | |||
"safelist.numberOperations", | |||
newManifest && | |||
newManifest.operations && | |||
newManifest && |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My VS Code did this automatically? 🤷♂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feel free to merge whenever the associated tooling change is ready!
This is to support a change to the command line tool to prefer using --variant to --tag and deprecate the latter.
88e4d92
to
cd07760
Compare
This is to support a change to the command line tool to prefer using
--variant to --tag and deprecate the latter. Please see apollographql/apollo-tooling#1849 for reference! We should correspond timing of the two :)