feat(webapp,core,cli): filter runs by region in dashboard, API, and MCP#3612
feat(webapp,core,cli): filter runs by region in dashboard, API, and MCP#3612ericallam wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: aac03ef The changes in this PR will be included in the next version bump. This PR includes changesets to release 32 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
125a478 to
cd003da
Compare
36ccf22 to
a90949b
Compare
cd003da to
eb89909
Compare
Adds a "Region" column and "Region" filter (under More filters) to the runs list, plus the same filter on the public runs list API (filter[region]) and the MCP list_runs tool (region input). Each run's executing region is exposed as a new optional region field on the runs list and run retrieve responses, populated from the worker instance group's masterQueue identifier.
eb89909 to
aac03ef
Compare
Summary
Adds a Region column and Region filter (under More filters) to the runs list dashboard, the same filter on the public runs list API (
filter[region]), and a matchingregioninput on the MCPlist_runstool. Each run's executing region is also surfaced as a new optionalregionfield on the runs list and run retrieve responses, populated from the worker instance group'smasterQueueidentifier.Useful when you run tasks across multiple regions and want to slice the runs list — or your existing run-querying scripts — by where the run actually executed.
Design
The filter value in the URL / API is the
masterQueueidentifier (the same string already persisted onTaskRunand replicated to ClickHouse asworker_queue), so the query just becomesworker_queue IN (...)with no server-side translation. The Region dropdown options come from a new resource loader backed byRegionsPresenter, which now also exposesmasterQueuealongside the existing region metadata.Test plan
–for legacy runs with emptymasterQueue).?regions=<masterQueue>and the list narrows.GET /api/v1/runs?filter[region]=<masterQueue>returns only matching runs, and each item has aregionfield set.GET /api/v1/runs/<id>returnsregionfor a run that has a non-emptyworkerQueue.list_runswithregion: "..."; verify the formatted output line includesregion:<value>.This is part 1 of 5 in a stack made with GitButler: