Improve: update and enhance slot migration API documentation #369
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
This PR improves the Slot Migration API documentation in
docs/API.md.The earlier version of this section was incomplete and did not fully explain the fields, behavior, or possible responses of the migration endpoint.
Since this API is important for resharding and operational workflows, having accurate documentation is essential.
Improvements in This PR
(
slot_only,pipeline_size,speed)slot_onlyto boolean, matching the real API behaviorMotivation
Users relying on slot migration (especially for automation or cluster maintenance) need complete and reliable documentation.
The previous version did not cover several important details, which could cause confusion or incorrect usage.
This update aims to provide a clearer and more accurate reference for anyone interacting with the migration API.
Notes