Repository navigation
Send deployment routing headers from cluster metadata - #83
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.
Session and OAuth requests now discover the selected cluster through the existing
/v1/clusters?organization=<name>endpoint and send its serving deployment headers automatically. Existing CLI commands, cluster paths, organization query parameters and the size catalog stay unchanged.Routing metadata is cached for 30 seconds and invalidated by cluster/organization mutations. Both headers are omitted when metadata is absent or invalid, preserving the gateway migration fallback. API keys use embedded routing and skip discovery. Explicit request timeouts include discovery; gzip, bodies, idempotency keys and JWT/OAuth token contents retain their behavior.
Prepares CLI
0.7.0; publication is deferred. The organization-scoped endpoint migration is outside this PR.Companions: Platform https://github.com/rawtreedb/rawtree-platform/pull/1524 and MCP rawtreedb/rawtree-mcp#34.
Validation: all CLI unit and contract tests pass, including routing, browser login and unchanged cluster URL assertions. Six live CLI tests pass against the rebuilt backend. P3 autoreview and thermonuclear maintainability review are clean.