Graphql Mesh Build hitting endpoint twice- 1. with schema header and 2. without schema header?

[shadikkhan]

I am using Node V16.x with below mesh packages

"@escape.tech/graphql-armor-max-depth": "^2.2.0",
"@graphql-mesh/cli": "0.82.35",
"@graphql-mesh/graphql": "0.93.1",
"@graphql-mesh/http": "0.93.1",
"@graphql-mesh/openapi": "0.93.1",
"@graphql-mesh/plugin-http-details-extensions": "0.93.1",
"@graphql-mesh/plugin-prometheus": "0.93.1",
"@graphql-mesh/runtime": "0.93.1",
"@graphql-mesh/transform-rename": "0.93.1",
"@whatwg-node/fetch": "^0.9.13",

I have once source in my meshrc.ts file (graphql endpoint) and I am passing a schema header to build it. It hit that endpoint twice 1 with schema header and 2 without schema header, which is causing build failure since the source MS have some machnism in place and need that schema header to go through.

I am not sure why it is hitting twice, any idea why this is happening? OR please comment if graphql mesh does not hit twice.

Error that I am getting

[ardatan]

If the given GraphQL endpoint is a federated service, it goes to the endpoint to fetch the SDL from _service.sdl.

[shadikkhan]

Hi @ardatan Thank you for response.

1. I am using Netflix DGS on the microservice side to make MS graphql but I am not doing any federation in it. Its just one query with one input/type
2. Is there any way to pass the same schema header in it (no operation header) even it goes for SDL?
3. OR is there any way to stop it for _service.sdl?