- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- IAM Permissions
- Try it!
Starting September 29, 2025, you can't use the moveDisk API on new projects. To move a disk to a different region or zone, follow the steps in Change the location of a disk. Projects that already use the moveDisk API can continue usage until September 29, 2026. Starting November 1, 2025, API responses will include a warning message in the response body about the upcoming deprecation. You can skip the message to continue using the service without interruption.
HTTP request
POST https://compute.s3nsapis.fr/compute/v1/projects/{project}/moveDisk
The URL uses gRPC Transcoding syntax. To know more about valid error responses that can be thrown by this HTTP request, please refer to the service error catalog
Path parameters
Parameters | |
---|---|
project |
Project ID for this request. |
Query parameters
Parameters | |
---|---|
requestId |
An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (
). |
Request body
The request body contains data with the following structure:
JSON representation |
---|
{ "targetDisk": string, "destinationZone": string } |
Fields | |
---|---|
targetDisk |
The URL of the target disk to move. This can be a full or partial URL. For example, the following are all valid URLs to a disk:
Authorization requires one or more of the following IAM permissions on the specified resource
|
destinationZone |
The URL of the destination zone to move the disk. This can be a full or partial URL. For example, the following are all valid URLs to a zone:
|
Response body
If successful, the response body contains an instance of Operation
.
Authorization scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/compute
https://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.
IAM Permissions
In addition to any permissions specified on the fields above, authorization requires one or more of the following IAM permissions:
compute.disks.create
compute.projects.get
compute.regions.get
compute.snapshots.create
compute.snapshots.delete
compute.snapshots.useReadOnly
To find predefined roles that contain those permissions, see Compute Engine IAM Roles.