This differs from removing an existing assignment and recreating a new one by providing a transactional change that ensures an assignee always has an associated reservation.
HTTP request
POST https://bigqueryreservation.googleapis.com/v1/{name=projects/*/locations/*/reservations/*/assignments/*}:move
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-25 UTC."],[[["This endpoint allows moving an assignment to a new reservation, ensuring a transactional change that maintains an assignee's associated reservation."],["The HTTP request uses the `POST` method with a specific URL structure utilizing gRPC Transcoding syntax to identify the assignment to be moved."],["The `name` path parameter is required to identify the assignment, and the request body requires `destinationId` and optionally `assignmentId` to specify the target reservation."],["Successful execution returns an `Assignment` instance, indicating the move was completed, and requires either `bigquery.reservationAssignments.delete` IAM permission, or one of two OAuth Scopes."]]],[]]