Gateway should offer configuration point for introspection query
See original GitHub issueGateways currently offer a configuration point for buildService
-> willSendRequest
, which allows setting headers on normal federated requests to their services, but they offer no configuration hook for sending the initial query GetServiceDefinition { _service { sdl } }
request.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Why You Should Disable GraphQL Introspection In Production
In this post, we'll discuss why we believe you should disable GraphQL introspection in production, how to do it, and present a way...
Read more >node.js - Apollo gateway not picking up managed federation ...
UnhandledPromiseRejectionWarning: Error: When serviceList is not set, an Apollo Engine configuration must be provided. I've been following ...
Read more >Validating Access_Tokens Through the Introspection Endpoint
Set up AM: Select Applications > Agents > Identity Gateway, add an agent with the following values:.
Read more >Apollo Federation specification - Apollo GraphQL Docs
Schema composition at the gateway requires having each service's schema, annotated with its federation configuration. This information is fetched from each ...
Read more >The complete GraphQL Security Guide: Fixing the 13 most ...
You should not trust any GraphQL library without heavy testing, ... Playground use the introspection Query to then be able to give the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This would be quite helpful, but I also see it as useful for us to possibly configure the actual method used to communicate with the service. One might want to use
lambda.invoke
as opposed tofetch
, and all we would need is to provide a function that implements a similar API.I have patched the Apollo Gateway in my own codebase to facilitate my desire for leveraging
lambda.invoke
(why add an API Gateway layer if I don’t need it? 😄 ) with some of the services, ensuring to construct the context object to be properly accepted by theapollo-server-lambda
handler.I just ran into this issue today (my service requires a particular header), FWIW it would be nice to be able to manipulate headers on a per-service basis rather than just globally. Perhaps as a
headers
prop that can be included alongsidename
andurl
?