Repository navigation
Route CLI requests across regional deployments (0.7.4) - #85
Merged
Merged
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 39fa9a6. Configure here.
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.

CLI user sessions previously listed clusters through only the default deployment, so clusters in other regions could be missing or receive requests at the wrong endpoint. Discovery now merges enabled regional catalogs and joins each cluster's region ID to authoritative deployment metadata. Requests to the public RawTree API use deployment-specific hosts and retain routing and client headers.
Duplicate records are selected by catalog authority: the owning deployment wins over gateway or other-deployment copies, even when those copies contain a region ID. This preserves full cluster fields and routing independently of response order, including separate deployments in the same AWS region.
Supports 8-character and legacy 32-character deployment IDs, preserves custom API URLs and API-key behavior, and carries request deadlines through discovery. Regional failures do not cache partial results. Cluster lists without an organization discover across accessible organizations. Patch version: 0.7.3 → 0.7.4.
Current
mainis merged, including the workflow schedule API compatibility fix from #87; this removes the old flatenabled/interval_secondspayloads responsible for the earlier Compose failures. The S3 contract fixture includes the new discovery requests.Validation:
cargo test --locked: 239 passed.cargo fmt --all -- --checkandgit diff --check: passed.Related Platform change: https://github.com/rawtreedb/rawtree-platform/pull/1566.
Companion MCP change: rawtreedb/rawtree-mcp#36. Duplicate-cluster UI follow-up: https://github.com/rawtreedb/rawtree-platform/pull/1575.