How to restrict Remote Schemas GraphQL from showing endpoints that we don't need? #7157
Unanswered
antonioberetini
asked this question in
Question
Replies: 1 comment 1 reply
-
@antonioberetini Remote schema permissions is currently the only way to restrict other fields from showing up. You'll have to use this role in graphiQL as well to avoid seeing unwanted nodes. @tirumaraiselvan Can perhaps comment about the schema customisation options planned in the near future. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We added a GraphQL endpoint to Remote Schema then we created a relationship within a table to corelate based on a unique identifier. Once this was finished, we see ALL nodes available under the remote schema GraphQL endpoint, under Hasura API tab. We really need just the one we selected under the relationship settings. Is there a way to only allow the one we need?
Remote Schema Relationship
![image](https://user-images.githubusercontent.com/65619488/124021439-2c439f00-d9b1-11eb-88ec-23d4fda51f96.png)
API explorer:
Brand section is coming from remote schema. See previous attachment, we haven't selected that.
Beta Was this translation helpful? Give feedback.
All reactions