Fix volume lookups broken by GraphQL API change - #5039
Merged
Conversation
The node(id:) GraphQL field was removed, which broke GetAppNameFromVolume and friends — and with them fly postgres create --fork-from, fly volumes show/destroy/update, and the snapshot commands when given a bare volume ID. - Bump fly-go to v0.9.2, which moves those queries to the volume(id:) root query - Drop the GraphQL lookup from postgres create --fork-from entirely: the Machines API volume lookup is already scoped to the fork-from app, so it both resolves the volume and validates ownership Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The node(id:) GraphQL field was removed, which broke
GetAppNameFromVolume and friends — and with them fly postgres create
--fork-from, fly volumes show/destroy/update, and the snapshot
commands when given a bare volume ID.
root query
the Machines API volume lookup is already scoped to the fork-from
app, so it both resolves the volume and validates ownership
Co-Authored-By: Claude Fable 5 noreply@anthropic.com