- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization Scopes
- Try it!
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.
The URL uses gRPC Transcoding syntax.
The resource name of the assignment, e.g.: projects/myproject/locations/US/reservations/team1-prod/assignments/123
Authorization requires the following Google IAM permission on the specified resource
The new reservation ID, e.g.: projects/myotherproject/locations/US/reservations/team2-prod
The request body must be empty.
If successful, the response body contains an instance of
Requires one of the following OAuth scopes:
For more information, see the Authentication Overview.