Multiple calls to AddFusionGatewayServer()
result in mismatched schemas
#7386
Labels
AddFusionGatewayServer()
result in mismatched schemas
#7386
Product
Hot Chocolate
Version
13.9.10
Link to minimal reproduction
https://github.com/andrew-brad-cmg/hot-chocolate-fusion-multiple-gateway-bug
Steps to reproduce
Copying steps from the readme on that repo:
dotnet build
dotnet tool restore
gateway1.fgp
:gateway1.fgp
file.gateway2.fgp
:gateway2.fgp
file.http://localhost:5000/graphql/
and ensure Banana Cake Pop UI loads. Ensure schema endpoint:http://localhost:5000/graphql/
Reviews
schema. If you load the other schema endpointhttp://localhost:5000/api/
, you will see the correct schema for that, which isReviews
.AddFusionGatewayServer()
with gateway 2 first, followed by gateway1. In that scenario, theAccounts
subgraph will "win" (i.e. show for both schema endpoints).fgp
files can be rebuilt and inspected as desired for reproducton, to the best of our knowledge they are correctly packaging all artifacts.What is expected?
The
Accounts
schema should be hosted and viewable at schema endpointhttp://localhost:5000/graphql/
The
Reviews
schema should be hosted and viewable at schema endpointhttp://localhost:5000/api/
What is actually happening?
Only the
Reviews
schema is coming back from both endpoints. We've refreshed Banana Cake Pop UI, and also exported the schemas to.graphql
files using CLI. This same behavior remains, whereAccounts
schema is nowhere to be found, despite being present in thefgp
artifact.Relevant log output
No response
Additional context
See readme in the repo: switching the order of operations such that gateway2 is invoked first followed by gateway1, results in only the
Accounts
schema being available. Same fgp files.The text was updated successfully, but these errors were encountered: