-
Notifications
You must be signed in to change notification settings - Fork 276
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
Feat/qp dry run #6656
Feat/qp dry run #6656
Conversation
|
✅ Docs preview readyThe preview is ready to be viewed. View the preview File Changes 0 new, 1 changed, 0 removed
Build ID: fdc6e7bef873059e2b2fe904 URL: https://www.apollographql.com/docs/deploy-preview/fdc6e7bef873059e2b2fe904 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! i'll refrain from approving since I wrote most of this tho
@Mergifyio refresh |
✅ Pull request refreshed |
@Mergifyio backport 1.x |
✅ Backports have been created
|
Description
Duplicating #5826 (and #6635 as it's acting odd due to being a fork) to more easily rebase. This just copies the code needed for the change (specifically the plugin changes). All work done by @lennyburdette and @aaronArinder - I'm just helping get this across the line.
This PR adds a new
dry-run
option to theApollo-Expose-Query-Plan
header value that emits the query plans back to Studio for visualizations. This new value will only emit the query plan, and abort execution. This can be helpful for tools likerover
, where query plan generation is needed but not full runtime, or for potentially prewarming query plan caches out of band.Checklist
Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.
Exceptions
None; this is net new functionality.
Notes
Footnotes
It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this. ↩
Configuration is an important part of many changes. Where applicable please try to document configuration examples. ↩
Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions. ↩