Update Vitess parallel deploy request guidance - #18
Draft
cursor[bot] wants to merge 1 commit into
Draft
Conversation
Co-authored-by: Sam Lambert <samlambert@users.noreply.github.com>
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
1 participant
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
--strategy parallelis only appropriate for independent changes touching different tables and can increase database load.Changelog entry
Why
PlanetScale now supports running two Vitess deploy requests at once when the changes touch different tables. The affected skills need to teach agents to preserve serial deployment by default, use the parallel strategy only when explicitly approved or authorized, and account for load and throttler settings.
Validation
git diff --check HEAD~1 HEAD