graphprotocol / graphprotocol/graph-node

[Feature] Need a environment variable for Alias limit in GraphQL

Open
#5,404 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Stale
Dominant language
Rust
Stars
3.2k
Forks
1.1k
Avg merge
4d 1h
Merged PRs (30d)
1

Description

Description

I use the docker to start graphnode postgres and ipfs , I can find the GRAPH_GRAPHQL_MAX_DEPTH in Environment Variables, but I can not find Alias limit in GraphQL.

Maybe you can add the environment variable .

According to this blog https://checkmarx.com/blog/alias-and-directive-overloading-in-graphql/
When we talk about preventing DoS in GraphQL, we’re usually discussing how to handle complex queries with deeply nested or circular relationships or even about preventing batching attacks, but it’s not often that alias and directives are mentioned as potential vectors.

Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.

No response

Some information to help us out
  • Tick this box if you plan on implementing this feature yourself.
  • I have searched the issue tracker to make sure this issue is not a duplicate.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing GRAPH_GRAPHQL_MAX_DEPTH environment-variable handling and the GraphQL query-limit configuration. Check how Docker environment variables are documented and configured, then verify that an alias limit can be set and enforced alongside the existing depth limit.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, graphql, rust
Domain
api, devops, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.