Closed Bug 1345909 Opened 7 years ago Closed 4 years ago

[Meta] Add a comprehensive GraphQL API to Treeherder and use it to speed up the front-end

Categories

(Tree Management :: Treeherder: API, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: wlach, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: meta)

Bug 1332457 proved that adding a GraphQL frontend to Treeherder's datastore was a reasonable proposition. Now the task is to make this actually useful. This includes fleshing it out (to cover a useful subset of treeherder's data model, if not the whole thing) and then actually using it for something. 

There are also some unanswered questions as far as preventing people from either accidentally or deliberately using this API to DDOS treeherder (say be repeatedly making extremely demanding queries). Personally I'm not too worried about this-- it's already quite possible to easily construct a query to (say) the existing jobs REST endpoint that will bring treeherder to its knees, but it's something to discuss I suppose.
Depends on: 1345914
Depends on: 1353093
Priority: -- → P3
Keywords: meta

I think we're in the process of removing support for graphQL, per some work :camd recently did.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.