You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The _service field allows for runtime introspection of the full schema with Federated directives. It is helpful for Rover to fetch the schema if needed. However, if I have a schema file I can use to publish and share the schema the _service field is a security risk to potentially over expose the schema information. Just like how we recommend turning off introspection in production we should also have the option to turn off _service in production.
This is part an Apollo Server issue as well, but the library that adds the field is here. I will leave it up to the team to decide the best place to accept configuration options
Option 1
Disable adding the field in the first place
constoptions={disableFederationServiceField: true};// New options paramconstschema=buildSubgraphSchema({ typeDefs, resolvers, options });
Option 2
Infer from introspection config
constserver=newApolloServer({
typeDefs,
resolvers,introspection: false// Infer from here to hide the `_service` field ??});
The text was updated successfully, but these errors were encountered:
The
_service
field allows for runtime introspection of the full schema with Federated directives. It is helpful for Rover to fetch the schema if needed. However, if I have a schema file I can use to publish and share the schema the_service
field is a security risk to potentially over expose the schema information. Just like how we recommend turning off introspection in production we should also have the option to turn off_service
in production.This is part an Apollo Server issue as well, but the library that adds the field is here. I will leave it up to the team to decide the best place to accept configuration options
Option 1
Disable adding the field in the first place
Option 2
Infer from introspection config
The text was updated successfully, but these errors were encountered: