Add collection browsing and metadata discovery commands#29
Merged
Conversation
Add read-only collection commands so users and agents can browse Metabase collections and discover their contents: - collection list: list all collections - collection get <id>: collection details (accepts "root") - collection items <id>: cards, dashboards, and nested collections inside a collection, with --models filtering Collection.ID is typed as any because the Metabase API returns the root collection with the string id "root" alongside numeric ids. Closes #13
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
Adds read-only collection commands so users and agents can browse Metabase collections and discover their contents. Closes #13.
Commands
collection list— list all collectionscollection get <id>— collection details (acceptsroot, case-insensitive)collection items <id>— cards, dashboards, and nested collections inside a collection, with--modelsfilteringNotes
Collection.IDis typed asanybecause the Metabase API genuinely returns the root collection with the string id"root"alongside numeric ids (confirmed via smoke testing). JSON output stays natural — numbers as numbers,"root"as a string.mberr.RequestError/ResourceCollectionpath, so a 404 is classified asAPI_ERRORwith a collection-specific suggestion.--format jsonand--format tableare supported.Testing
--modelsfiltering, therootcollection, and 404 handling.make test);make fmtandmake vetclean.list,get <id>,get root,items <id>(table + JSON),items root --models dashboard, and a 404.Changelog
Entry added under
## [Unreleased](#13).