2025-12-04
▼ ▲ compute.regionInstanceGroupManagers.adoptInstances
Scopes :
Path : projects/{project}/regions/{region}/instanceGroupManagers/{instanceGroupManager}/adoptInstances
Parameter Order :
Parameters :
requestId
Description : 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).
Location : query
Type : string
region
Location : path
Description : Name of the region scoping this request. It should conform to RFC1035.
Required : Yes
Type : string
instanceGroupManager
Required : Yes
Description : Name of the managed instance group. It should conform to RFC1035 or be a resource ID.
Location : path
Type : string
project
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Required : Yes
Location : path
Description : Project ID for this request.
Type : string
Flat Path : projects/{project}/regions/{region}/instanceGroupManagers/{instanceGroupManager}/adoptInstances
Description : Flags the specified instances to be adopted to the managed instance group. Adopting an instance does not change the instance status, but it adds the instance to any target pools that are applied by the managed instance group. This method increases the targetSize of the managed instance group by the number of instances that you adopt. This operation is marked as DONE when the action is scheduled even if the instances have not been adopted to the group yet. You must separately verify the status of the adopting action with the listManagedInstances method.
HTTP Method : POST
▼ ▲ compute.networks.cancelRequestRemovePeering
Path : projects/{project}/global/networks/{network}/cancelRequestRemovePeering
Parameter Order :
Description : Cancel requests to remove a peering from the specified network. Applicable only for PeeringConnection with update_strategy=CONSENSUS. Cancels a request to remove a peering from the specified network.
Scopes :
Parameters :
network
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Description : Name of the network resource to remove peering from.
project
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Location : path
Required : Yes
Description : Project ID for this request.
Type : string
requestId
Type : string
Location : query
Description : 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).
HTTP Method : POST
Flat Path : projects/{project}/global/networks/{network}/cancelRequestRemovePeering
▼ ▲ compute.regionInstanceGroupManagers.adoptInstances
Scopes :
Path : projects/{project}/regions/{region}/instanceGroupManagers/{instanceGroupManager}/adoptInstances
Parameter Order :
Parameters :
requestId
Description : 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).
Location : query
Type : string
region
Location : path
Description : Name of the region scoping this request. It should conform to RFC1035.
Required : Yes
Type : string
instanceGroupManager
Required : Yes
Description : Name of the managed instance group. It should conform to RFC1035 or be a resource ID.
Location : path
Type : string
project
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Required : Yes
Location : path
Description : Project ID for this request.
Type : string
Flat Path : projects/{project}/regions/{region}/instanceGroupManagers/{instanceGroupManager}/adoptInstances
Description : Flags the specified instances to be adopted to the managed instance group. Adopting an instance does not change the instance status, but it adds the instance to any target pools that are applied by the managed instance group. This method increases the targetSize of the managed instance group by the number of instances that you adopt. This operation is marked as DONE when the action is scheduled even if the instances have not been adopted to the group yet. You must separately verify the status of the adopting action with the listManagedInstances method.
HTTP Method : POST
▼ ▲ compute.networks.cancelRequestRemovePeering
Path : projects/{project}/global/networks/{network}/cancelRequestRemovePeering
Parameter Order :
Description : Cancel requests to remove a peering from the specified network. Applicable only for PeeringConnection with update_strategy=CONSENSUS. Cancels a request to remove a peering from the specified network.
Scopes :
Parameters :
network
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Description : Name of the network resource to remove peering from.
project
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Location : path
Required : Yes
Description : Project ID for this request.
Type : string
requestId
Type : string
Location : query
Description : 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).
HTTP Method : POST
Flat Path : projects/{project}/global/networks/{network}/cancelRequestRemovePeering