fix(visualize): parse backend_usages array sidecar format#43
Merged
Conversation
Toolbox exports may write backend_usages.json as a top-level array. Accept both that shape and the wrapped Admin API object so topology and auth resolution work for Copec-style exports. Co-authored-by: Cursor <cursoragent@cursor.com>
fmenesesg
added a commit
that referenced
this pull request
Jun 11, 2026
…ay-format fix(visualize): parse backend_usages array sidecar format
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.
Proposed change
Parse
backend_usages.jsonwhen exported as a top-level JSON array (toolbox sidecars), not only the wrapped{ "backend_usages": [...] }Admin API shape.Type of change
Test plan
go test ./internal/visualize/...Additional information
Made with Cursor