hasura / hasura/graphql-engine

Remote schema permission - allow full access to the remote schema with a wildcard character

Open
#6,949 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

Hello all,

We're currently trying to use the remote schema permission feature from the v2 of Hasura and it would be very convenient to be able to specify a full access to the remote schema for a given role by using this syntax :

```yaml

permissions:
- role: user
definition:
schema: "*"

```

The reason is that our remote schema is implementing a large chunk of our business logic (mainly mutations) and it's very painful to synchronize our remote schema types definitions with the remote permissions as we need to dump our entire remote schema into the metadata file each time we evolve our business logic. By accepting a wildcard, we could just refresh the remote schema and that's it. ⚡

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.