Description
If my understanding is correct, this error is being thrown here because my subgraphs are using a recent version of async-graphql
that supports Federation v2, thus their SDLs have a extension for the schema (as they should based on this code).
Expected Behavior
Supergraph should accept SDLs following Apollo Federation v2.
Actual Behavior
Server returns all requests with {"data": null,"errors": [{"message": "Not ready."}]}
and logs ERROR Failed to update schema. error=Redefining the schema is not allowed.
Steps to Reproduce the Problem
- Clone the repo.
- Run
docker build -t graphgate-with-examples -f Dockerfile-standalone-demo .
. I was getting errors so had to change versions ofrust
andubuntu
tolatest
. - Run
docker run --name graphgate-issue-27 -d -p 8000:8000 -p 8001:8001 -p 8002:8002 -p 8003:8003 graphgate-with-examples
. - Notice that the supergraph runs as expected. Also notice that running
query{_service {sdl}}
against the individual subgraphs does NOT returnextend schema @link...
- Run
docker stop graphgate-issue-27 && docker rm graphgate-issue-27
- Open
Cargo.toml
and change versions ofasync-graphql
andasync-graphql-warp
to5.0.8
. - Run
docker build -t graphgate-with-examples -f Dockerfile-standalone-demo .
. - Run
docker run --name graphgate-issue-27 -d -p 8000:8000 -p 8001:8001 -p 8002:8002 -p 8003:8003 graphgate-with-examples
. - Notice that the supergraph doesn't work. Also notice that running
query{_service {sdl}}
against the individual subgraphs returnsextend schema @link...
(which I think is causing the issue) - Run
docker stop graphgate-issue-27 && docker rm graphgate-issue-27
to clean up
Specifications
- Version: 0.5.1
- Platform: Mac
- Subsystem: idk