-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ FR: Supergraph support for Router and Studio #209
Comments
👋 Hi @hinogi - have you tried using Apollo's Managed Federation workflows? Wondering if there is a specific reason why you are running composition / publishing in a self-managed way. https://www.apollographql.com/docs/federation/managed-federation/overview/ |
Actually I was attempting to use apollo studio as a client for sending queries to the gateway and to add convenience a little help from the existing schema would be handy to see how it would run in production. |
It would be great if instead of uploading individual subgraphs one could just upload the supergraph to studio. Because, if you try out the production mode and there is no introspection, and if you want to test the gateway this really interferes with usability. The supergraph schema has already been composed but I can only use it for the gateway and not for apollo studio.
Also, the Router also wipes all references to subgraphs from the sdl which also renders it a bit useless for the gateway since I cannot seem to make requests that include subgraphs because all the joins are gone.
The text was updated successfully, but these errors were encountered: