Skip to content

Add VTGate parameter commands - #1459

Draft
no-itsbackpack wants to merge 1 commit into
mainfrom
egomez/vtgate-parameters
Draft

no-itsbackpack wants to merge 1 commit into
mainfrom
egomez/vtgate-parameters

Conversation

@no-itsbackpack

Copy link
Copy Markdown
Contributor

Adds commands for viewing and changing the VTGate parameters of a Vitess branch, such as max_memory_rows and query-timeout, the same parameters on the VTGates config page in the dashboard. They follow the same shape as the other components' parameter commands: list with parameters, change with update --parameters namespace.name=value, and follow changes with changes.

  • branch vtgate parameters shows each parameter with its current value, default, and whether it's overridden.
  • branch vtgate update changes parameters with repeatable --parameters vtgate.name=value, and resets them to their defaults with --reset vtgate.name.
  • branch vtgate changes list, show, and cancel follow a change's rollout or cancel one that hasn't started.
pscale branch vtgate update mydb main --org acme \
  --parameters vtgate.max_memory_rows=500000 \
  --parameters vtgate.query-timeout=30000

The keyspace parameter commands now share their flag parsing and output with these, with no change in behavior. The agent guide (AGENTS.md) documents the new commands.

🤖 Generated with Claude Code

pscale branch vtgate parameters lists a Vitess branch's VTGate
parameters, pscale branch vtgate update changes them with
--parameters vtgate.name=value or --reset vtgate.name, and
pscale branch vtgate changes list, show, and cancel follow each change.

Keyspace and VTGate parameter commands now share their flag parsing and
output, and submitting config changes moves to the branches service.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
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.

1 participant