Moves a assignment under a new reservation. Customers can do this by deleting the existing assignment followed by creating another assignment under the new reservation, but this method provides a transactional way to do so, to make sure the assignee always has an associated reservation. Without the method customers might see some queries run on-demand which might be unexpected.
HTTP request
POST https://bigqueryreservation.googleapis.com/v1beta1/{name=projects/*/locations/*/reservations/*/assignments/*}:move
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
name |
Required. The resource name of the assignment, e.g.: projects/myproject/locations/US/reservations/team1-prod/assignments/123 Authorization requires the following IAM permission on the specified resource
|
Request body
The request body contains data with the following structure:
| JSON representation | |
|---|---|
{ "destinationId": string } |
|
| Fields | |
|---|---|
destinationId |
The new reservation ID, e.g.: projects/myotherproject/locations/US/reservations/team2-prod |
Response body
If successful, the response body contains an instance of Assignment.
Authorization Scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/bigqueryhttps://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.