Repository navigation
feat(grid): Add settings, connections, and classifier commands - #173
Merged
Merged
Conversation
ShivainVij
added this pull request to stack #174
October 20, 2026 04:20
youngzheng-oss
approved these changes
Oct 20, 2026
youngzheng-oss
left a comment
youngzheng-oss
left a comment
Contributor
There was a problem hiding this comment.
Approving since it's just squashing a stack
…basetenlabs/baseten-cli into shivain/additional-cli-commands
ShivainVij
removed this pull request from stack #174
October 20, 2026 09:18
ShivainVij
added a commit
that referenced
this pull request
Oct 21, 2026
* fix(harness): Read usage settings per team instead of the user teams listing
The usage command listed your teams and your Code settings in each with
GET /v1/routes/settings/users/me/teams, which is being removed. Use
GET /v1/teams for your teams and GET /v1/routes/settings/teams/{team}/users/me
for your settings in each, which say the same things. Org admins are
members of every team, so they still see every team.
Claude-Session: https://claude.ai/code/session_01UkWMh7GwDgbmR88spBWMEm
* grid rename
* Update command.harness_usage_test.go
* Call the /v1/grid API and let the server pick the team for grid usage
Pins baseten-go to the client regenerated for the renamed Grid API, so
every call site moves to the GetGrid*/PostGrid*/PatchGrid*/DeleteGrid*
methods. grid usage now reads your settings from
GET /v1/grid/team_settings/users/me and passes --team straight through
as team_id: the server uses your only team, or asks for --team when you
belong to several. The client-side team listing and name matching are
gone, along with the "No usage this month" branch they fed.
Claude-Session: https://claude.ai/code/session_01UkWMh7GwDgbmR88spBWMEm
* refactor(grid): align command files and symbols with Grid hierarchy
* Update go.sum
* feat(grid): Add settings, connections, and classifier commands (#173)
* adding functionality to cli
* Update go.sum
* adding functionality to cli
* responding to comments (1)
* responding to comments (2)
* renaming
* Update command.grid.go
* Removing to match spec
* updating with new sdk
* grid settings flag rename to route id
* updated create/update outputs to be concise confirmations
* Update command.grid_test.go
* test renaming
* matching create (use hasGridRouteClassifier)
* Fold grid usage into grid route usage
`grid usage` listed your teams and fetched your settings in each to draw
your spend against your limit, the one place the CLI still stitched teams
together client-side. Per the review on this PR, usage is one command:
`grid route usage [--team] [--user-id]`, whose arguments behave as the API
does. Without --team, usage spans the teams you can see; without --user-id,
members see their own usage and admins see everyone's. Your spend against
your limit in a team is `grid user-settings describe`.
Claude-Session: https://claude.ai/code/session_01UkWMh7GwDgbmR88spBWMEm
* Show the team in grid route list
The list spans every team you can see unless --team narrows it, so two
rows can share a name. A TEAM column, as the connection list already
has, tells them apart.
Claude-Session: https://claude.ai/code/session_01UkWMh7GwDgbmR88spBWMEm
* inline cleanup
* command. filename matching
* more file org cleanup
* formatting
* defaultToCaller never set
* Addressing more comments
* show ids as well in route describe
* updating SDK + use ID for setup command
---------
Co-authored-by: Young Zheng <young.zheng@baseten.co>
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
2 participants
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.
🚀 What
Extend the Grid command tree with the remaining API-backed management commands:
grid team-settings describe|updategrid user-settings list|describe|updategrid connection list|create|update|deletegrid classifier listAlso:
teamandroutergrouping, plus team filtering, togrid route usage.--teamserver-side during setup.grid harness-defaultsalongside the new team-settings commands.connection describeandclassifier describeare intentionally omitted because their individual-resource GET APIs do not exist.💻 How
31f58c2from Regenerate the management API client for the /v1/grid API and Grid schema renames baseten-go#70, matching the final Grid API.Grid*types and union helpers./v1/grid/team_settings.team_idwhen--teamis omitted, then use the server-resolved team for subsequent requests and the saved sync configuration./v1/teamsand fetching per-team user settings; no calls remain to the removed settings-across-teams endpoint.Stacked on
shivain/grid-rename(#169).🔬 Testing
go vet ./...pass.