Skip to content

Add move-tables start and stop commands - #1437

Closed
no-itsbackpack wants to merge 1 commit into
mainfrom
cursor/move-tables-start-stop-8f7d
Closed

no-itsbackpack wants to merge 1 commit into
mainfrom
cursor/move-tables-start-stop-8f7d

Conversation

@no-itsbackpack

Copy link
Copy Markdown
Contributor

Problem:

MoveTables workflows can be created with --auto-start=false, stop after copy, or be paused later. Those workflows had no move-tables subcommands to start or stop them; operators had to use the generic vtctld start-workflow / stop-workflow commands with a different flag shape.

Solution:

Add pscale branch vtctld move-tables start and move-tables stop. Both take --workflow and --target-keyspace, matching the other MoveTables commands, and call the existing workflow start/stop API.

status now suggests start when every stream is stopped. create --auto-start=false suggests start as the next step.


Security impact:

None. These commands call existing authenticated start/stop endpoints and do not change authorization or expand access.


Testing:

  • Unit tests for start/stop flag wiring, JSON output, progress text, and next-step hints
  • go test ./internal/cmd/branch/vtctld/... ./internal/planetscale/...

Slack Thread

Open in Web Open in Cursor 

Wire `pscale branch vtctld move-tables start` and `stop` to the existing
vtctld workflow start/stop endpoints, using the same --workflow and
--target-keyspace flags as the other move-tables commands.

Co-authored-by: Gomez <no-itsbackpack@users.noreply.github.com>
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