Repository navigation
Route cluster creation by region; bump CLI to 0.7.1 - #84
Merged
Merged
Conversation
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.
Add
rtree cluster regionsand--region-idon cluster creation and size discovery. Resolve the selected region through the organization's catalog, send its deployment routing headers for both size validation and creation, and saveregion_idin the create body. This lets the regional backend provision through its local Console satellite.Omitting the option preserves the default backend. Disabled, unknown, or unroutable selections fail before creation; the legacy public US East region retains its default route. API keys cannot override their embedded routing. Bump CLI 0.7.0 → 0.7.1.
Validation:
cargo test --locked(222 passed; 6 live Platform tests ignored),cargo fmt --all -- --check, actual CLI command tests, and HTTP routing tests. Strict thermo-nuclear/autoreview through P3 completed clean. Strict Clippy still reports existing issues in insert/query code and unchanged older routing tests; CI's formatting and test contract passes locally. No live regional cluster was provisioned.Note
Medium Risk
Changes cluster provisioning HTTP routing and create payloads; mistakes could send creates to the wrong deployment, though validation and API-key restrictions limit exposure.
Overview
Regional cluster provisioning is the main theme: the CLI bumps to 0.7.1 and adds ways to pick a deployment region when creating clusters or listing sizes.
New
rtree cluster regionslists an org’s region catalog.--region-idoncluster sizesandcluster createresolves the region via/v1/organizations/{id}/regions, validates it (enabled, routable deployment, org required), and scopes API calls throughApiClient::for_regionso size checks and creation sendX-RawTree-Deployment-Id/X-RawTree-Regionwithout mutating the default client. Create requests also includeregion_idin the JSON body.Omitting
--region-idkeeps prior default routing; the legacy public US East region stays special-cased when it has no deployment.rt_*API keys cannot use region selection. README documents the workflow; unit, routing, and integration tests cover headers, validation failures, and CLI behavior.Reviewed by Cursor Bugbot for commit 06116a0. Bugbot is set up for automated code reviews on this repo. Configure here.