Method: instanceGroupManagers.deleteInstances

• HTTP request
• Path parameters
• Query parameters
• Request body
  • JSON representation
• Response body
  • JSON representation
    • JSON representation
    • JSON representation
• Authorization Scopes
• Examples
• Try it!

Flags the specified instances in the managed instance group for immediate deletion. The instances are also removed from any target pools of which they were a member. This method reduces the targetSize of the managed instance group by the number of instances that you delete. This operation is marked as DONE when the action is scheduled even if the instances are still being deleted. You must separately verify the status of the deleting action with the listmanagedinstances method.

If the group is part of a backend service that has enabled connection draining, it can take up to 60 seconds after the connection draining duration has elapsed before the VM instance is removed or deleted.

You can specify a maximum of 1000 instances with this method per request.

HTTP request

POST https://compute.googleapis.com/compute/v1/projects/{project}/zones/{zone}/instanceGroupManagers/{resourceId}/deleteInstances

The URL uses gRPC Transcoding syntax.

Path parameters

Parameters
project	string Project ID for this request.
zone	string The name of the zone where the managed instance group is located.
resourceId	string The name of the managed instance group. Authorization requires the following IAM permission on the specified resource instanceGroupManager: compute.instanceGroupManagers.update

Query parameters

Parameters

requestId

string 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 (00000000-0000-0000-0000-000000000000).

Request body

The request body contains data with the following structure: