refactor: align drift query CLI with shared protobuf schemas#217
Merged
Conversation
sohankshirsagar
approved these changes
Apr 7, 2026
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
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.
Summary
Align
tusk drift querywith the shared protobuf query contract so the CLI sends the same request shape as the backend and MCP while still accepting ergonomic user input.Changes
tusk-drift-schemasprotojsonand enum numbers so CLI payloads match the backend's protobuf JSON contract--whereparsing and convenience flag builders to the new recursiveWhereClause/fieldsshape, including normalization of ergonomic access enums likecastAs: "int"anddecode: "base64"jsonb-filtersCLI path in favor of the unified protobuf-drivenwherestructuregithub.com/Use-Tusk/tusk-drift-schemasto released versionv0.1.33and add coverage for--whereenum normalization