Skip to content

Document turbopuffer namespace branching - #378

Open
skreborn wants to merge 1 commit into
mainfrom
skreborn/turbopuffer-branching
Open

skreborn wants to merge 1 commit into
mainfrom
skreborn/turbopuffer-branching

Conversation

@skreborn

Copy link
Copy Markdown
Contributor

Resolves INT-506.

@linear-code

linear-code Bot commented Sep 18, 2026

Copy link
Copy Markdown

INT-506

@greptile-apps

greptile-apps Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Retrigger

This PR should not merge until the documented turbopuffer configuration is aligned with a CLI release that accepts the engine type.

Fix All in CursorFindings

  1. P1 Unsupported turbopuffer config type
Fix with agent prompt
### Issue 1
docs/sharing-the-cluster/db-branching/turbopuffer.md:26
When a user on the documented minimum CLI 3.260.0 or current CLI 3.261.0 copies this configuration, the CLI's `DatabaseBranchConfig` enum rejects `"type": "turbopuffer"` as an unknown variant, preventing the documented branch from being configured. Align this guide and its stated minimum version with a CLI release whose schema includes turbopuffer support.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Summary

The PR adds documentation and navigation for turbopuffer namespace branching, including configuration, copy modes, cleanup, limitations, and support-matrix entries. However, the documented configuration is not accepted by the current mirrord CLI schema.

Reviews (1) · Last reviewed commit: "Document turbopuffer namespace branching"

Comment thread docs/sharing-the-cluster/db-branching/turbopuffer.md
@skreborn
skreborn force-pushed the skreborn/turbopuffer-branching branch from 98b60df to 7ea4406 Compare September 18, 2026 09:29
@skreborn
skreborn requested a review from giIuis September 18, 2026 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants