Azure / Azure/data-api-builder
[Enhancement] : Allow role level query depth limits
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 370
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 9
Description
With this feature https://github.com/Azure/data-api-builder/issues/1577 coming in place, we should also have a way to define this at role level.
"runtime": {
```
"rest": {
"enabled": false,
"path": "/api",
"request-body-strict": true
},
"graphql": {
"enabled": true,
"path": "/graphql",
"allow-introspection": true
"depth-limit": 1
},
```
and the above configuration should also be applicable to specific role.
```
"permissions": [
{
"role": "anonymous",
"depth-limit": 2
"actions": [
{
"action": "*"
}
]
}
]
```
Contributor guide
Research direction
Start by reviewing issue 1577 and the existing runtime GraphQL and permissions configuration described here. Determine how a depth limit should be represented and applied at role level, including its relationship to the runtime setting. Done means a role can define its own query depth limit and the configuration is validated and honored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, graphql
- Domain
- api, authorization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100