Document how to configure schemaTag in operation registry plugin - AP-468#466
Document how to configure schemaTag in operation registry plugin - AP-468#466cheapsteak merged 5 commits intomasterfrom
Conversation
cheapsteak
changed the title
daniman
left a comment
daniman
left a comment
There was a problem hiding this comment.
Nice, thanks @cheapsteak! 😸
| }) | ||
| ] | ||
| }); | ||
| ``` |
There was a problem hiding this comment.
We should also mention the need to set the tag in the client push command here in order to get the operations into the manifest the plugin pulls
evans
left a comment
evans
left a comment
There was a problem hiding this comment.
Let's make sure we release the plugin and new apollo version before publishing these new docs
|
|
||
| ####5.1 Optionally, set the schema tag | ||
|
|
||
| The plugin will automatically pickup the value of the environment variable `ENGINE_SCHEMA_TAG` and use that as the schema tag. |
There was a problem hiding this comment.
If users specify this env var, then our new changes will be breaking, since they'll pick up a new manifest. Let's make sure this is in the upgrade guide
There was a problem hiding this comment.
I will remove this to match changes in https://github.com/apollographql/apollo-platform-commercial/pull/125
Thanks for picking up on this 🙏
The only way to specify a tag will initially be manually passing it in through the config to avoid a breaking change
cheapsteak
changed the title
cheapsteak
changed the title
3 participants
(Note: can merge after apollographql/apollo-tooling#1307 is released. update: released)
This PR adds 2 optional sub-steps in the setup flow to demonstrate how to configure the schema tag for the operation registry plugin and the cli
It also removes the "Only the default schema tag (
current) is supported." section from the "Limitations" section