Support Postgres branches in branch infra#1287
Merged
Merged
Conversation
Bump planetscale-go to v0.177.0, which models branch infrastructure as a per-engine union. The infra command now renders a Postgres-native table (nodes and bouncers with role, size, availability zone, and storage) for Postgres branches, and keeps the existing pods table for Vitess branches.
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
2 participants
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.
Summary
pscale branch infraonly worked for Vitess branches. The branch infrastructure API now serves Postgres branches too, so this bumps planetscale-go to v0.177.0 and renders the Postgres response.Changes
planetscale-gov0.176.0 → v0.177.0, which modelsBranchInfrastructureas a per-engine union (Vitess/Postgres); the Vitess path is updated for the new field layout with no behavior change.postgres) and per bouncer (pgbouncer) with role, size, availability zone, and storage usage/capacity. JSON/CSV output marshals the underlying SDK objects, matching how the Vitess pods table behaves.Why
The API returns an engine-native shape per database kind rather than forcing Postgres data into the Vitess pods shape, so the command branches once on which engine the response describes. The command remains hidden and the API is feature-gated with no stability guarantee.