2023-09-29
▼ ▲ compute.instanceGroupManagerResizeRequests.cancel
HTTP Method: POST
Scopes:
Parameter Order:
Flat Path: projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/resizeRequests/{resizeRequest}/cancel
Parameters:
requestId
Location: query
Type: string
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).
instanceGroupManager
Required: Yes
Type: string
Location: path
Description: The name of the managed instance group. The name should conform to RFC1035 or be a resource ID.
zone
Required: Yes
Type: string
Location: path
Description: The name of the zone where the managed instance group is located. The name should conform to RFC1035.
project
Required: Yes
Type: string
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
Description: Project ID for this request.
resizeRequest
Required: Yes
Location: path
Type: string
Description: The name of the resize request to cancel. The name should conform to RFC1035 or be a resource ID.
Path: projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/resizeRequests/{resizeRequest}/cancel
Description: Cancels the specified resize request and removes it from the queue. Cancelled resize request does no longer wait for the resources to be provisioned. Cancel is only possible for requests that are accepted in the queue.
▼ ▲ compute.regionInstanceGroupManagers.stopInstances
Scopes:
Description: Flags the specified instances in the managed instance group to be immediately stopped. You can only specify instances that are running in this request. This method reduces the targetSize and increases the targetStoppedSize of the managed instance group by the number of instances that you stop. The stopInstances operation is marked DONE if the stopInstances request is successful. The underlying actions take additional time. You must separately verify the status of the STOPPING action with the listmanagedinstances method. If the standbyPolicy.initialDelaySec field is set, the group delays stopping the instances until initialDelaySec have passed from instance.creationTimestamp (that is, when the instance was created). This delay gives your application time to set itself up and initialize on the instance. If more than initialDelaySec seconds have passed since instance.creationTimestamp when this method is called, there will be zero delay. 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 stopped. Stopped instances can be started using the startInstances method. You can specify a maximum of 1000 instances with this method per request.
Parameters:
requestId
Type: string
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
project
Location: path
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])?))
Type: string
Required: Yes
Description: Project ID for this request.
instanceGroupManager
Location: path
Type: string
Required: Yes
Description: The name of the managed instance group.
region
Location: path
Required: Yes
Type: string
Description: Name of the region scoping this request.
Flat Path: projects/{project}/regions/{region}/instanceGroupManagers/{instanceGroupManager}/stopInstances
Parameter Order:
HTTP Method: POST
Path: projects/{project}/regions/{region}/instanceGroupManagers/{instanceGroupManager}/stopInstances
▼ ▲ compute.regionInstanceGroupManagers.startInstances
Description: Flags the specified instances in the managed instance group to be started. This method increases the targetSize and decreases the targetStoppedSize of the managed instance group by the number of instances that you start. The startInstances operation is marked DONE if the startInstances request is successful. The underlying actions take additional time. You must separately verify the status of the STARTING action with the listmanagedinstances method. In this request, you can only specify instances that are stopped. For example, if an instance was previously stopped using the stopInstances method, it can be started using the startInstances method. If a health check is attached to the managed instance group, the specified instances will be verified as healthy after they are started. You can specify a maximum of 1000 instances with this method per request.
Flat Path: projects/{project}/regions/{region}/instanceGroupManagers/{instanceGroupManager}/startInstances
Parameters:
instanceGroupManager
Location: path
Description: Name of the managed instance group.
Required: Yes
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).
project
Required: Yes
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])?))
Type: string
Location: path
Description: Project ID for this request.
region
Description: Name of the region scoping this request.
Location: path
Type: string
Required: Yes
Scopes:
Parameter Order:
HTTP Method: POST
Path: projects/{project}/regions/{region}/instanceGroupManagers/{instanceGroupManager}/startInstances
▼ ▲ compute.regionInstanceGroupManagers.resumeInstances
Flat Path: projects/{project}/regions/{region}/instanceGroupManagers/{instanceGroupManager}/resumeInstances
Parameters:
instanceGroupManager
Type: string
Required: Yes
Description: Name of the managed instance group.
Location: path
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
Type: string
Description: Project ID for this request.
Location: path
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
Required: Yes
Type: string
Description: Name of the region scoping this request.
Path: projects/{project}/regions/{region}/instanceGroupManagers/{instanceGroupManager}/resumeInstances
Description: Flags the specified instances in the managed instance group to be resumed. This method increases the targetSize and decreases the targetSuspendedSize of the managed instance group by the number of instances that you resume. The resumeInstances operation is marked DONE if the resumeInstances request is successful. The underlying actions take additional time. You must separately verify the status of the RESUMING action with the listmanagedinstances method. In this request, you can only specify instances that are suspended. For example, if an instance was previously suspended using the suspendInstances method, it can be resumed using the resumeInstances method. If a health check is attached to the managed instance group, the specified instances will be verified as healthy after they are resumed. You can specify a maximum of 1000 instances with this method per request.
Scopes:
HTTP Method: POST
Parameter Order:
▼ ▲ compute.regionInstanceGroupManagers.suspendInstances
Description: Flags the specified instances in the managed instance group to be immediately suspended. You can only specify instances that are running in this request. This method reduces the targetSize and increases the targetSuspendedSize of the managed instance group by the number of instances that you suspend. The suspendInstances operation is marked DONE if the suspendInstances request is successful. The underlying actions take additional time. You must separately verify the status of the SUSPENDING action with the listmanagedinstances method. If the standbyPolicy.initialDelaySec field is set, the group delays suspension of the instances until initialDelaySec have passed from instance.creationTimestamp (that is, when the instance was created). This delay gives your application time to set itself up and initialize on the instance. If more than initialDelaySec seconds have passed since instance.creationTimestamp when this method is called, there will be zero delay. 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 suspended. Suspended instances can be resumed using the resumeInstances method. You can specify a maximum of 1000 instances with this method per request.
Flat Path: projects/{project}/regions/{region}/instanceGroupManagers/{instanceGroupManager}/suspendInstances
Scopes:
Parameters:
instanceGroupManager
Description: Name of the managed instance group.
Required: Yes
Type: string
Location: path
requestId
Type: string
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
project
Location: path
Required: Yes
Type: string
Description: Project ID for this request.
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])?))
region
Description: Name of the region scoping this request.
Location: path
Type: string
Required: Yes
HTTP Method: POST
Path: projects/{project}/regions/{region}/instanceGroupManagers/{instanceGroupManager}/suspendInstances
Parameter Order:
▼ ▲ compute.instanceGroupManagers.resumeInstances
Scopes:
Path: projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/resumeInstances
Description: Flags the specified instances in the managed instance group to be resumed. This method increases the targetSize and decreases the targetSuspendedSize of the managed instance group by the number of instances that you resume. The resumeInstances operation is marked DONE if the resumeInstances request is successful. The underlying actions take additional time. You must separately verify the status of the RESUMING action with the listmanagedinstances method. In this request, you can only specify instances that are suspended. For example, if an instance was previously suspended using the suspendInstances method, it can be resumed using the resumeInstances method. If a health check is attached to the managed instance group, the specified instances will be verified as healthy after they are resumed. You can specify a maximum of 1000 instances with this method per request.
Parameters:
requestId
Location: query
Type: string
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).
zone
Type: string
Location: path
Description: The name of the zone where the managed instance group is located.
Required: Yes
instanceGroupManager
Type: string
Location: path
Description: The name of the managed instance group.
Required: Yes
project
Required: Yes
Location: path
Type: string
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])?))
Description: Project ID for this request.
Flat Path: projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/resumeInstances
HTTP Method: POST
Parameter Order:
▼ ▲ compute.instanceGroupManagers.suspendInstances
Scopes:
Path: projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/suspendInstances
Flat Path: projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/suspendInstances
Parameter Order:
Description: Flags the specified instances in the managed instance group to be immediately suspended. You can only specify instances that are running in this request. This method reduces the targetSize and increases the targetSuspendedSize of the managed instance group by the number of instances that you suspend. The suspendInstances operation is marked DONE if the suspendInstances request is successful. The underlying actions take additional time. You must separately verify the status of the SUSPENDING action with the listmanagedinstances method. If the standbyPolicy.initialDelaySec field is set, the group delays suspension of the instances until initialDelaySec have passed from instance.creationTimestamp (that is, when the instance was created). This delay gives your application time to set itself up and initialize on the instance. If more than initialDelaySec seconds have passed since instance.creationTimestamp when this method is called, there will be zero delay. 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 suspended. Suspended instances can be resumed using the resumeInstances method. You can specify a maximum of 1000 instances with this method per request.
Parameters:
requestId
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).
Type: string
zone
Description: The name of the zone where the managed instance group is located.
Location: path
Required: Yes
Type: string
instanceGroupManager
Required: Yes
Type: string
Location: path
Description: The name of the managed instance group.
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
Description: Project ID for this request.
Location: path
Type: string
HTTP Method: POST
▼ ▲ compute.instanceGroupManagers.startInstances
Description: Flags the specified instances in the managed instance group to be started. This method increases the targetSize and decreases the targetStoppedSize of the managed instance group by the number of instances that you start. The startInstances operation is marked DONE if the startInstances request is successful. The underlying actions take additional time. You must separately verify the status of the STARTING action with the listmanagedinstances method. In this request, you can only specify instances that are stopped. For example, if an instance was previously stopped using the stopInstances method, it can be started using the startInstances method. If a health check is attached to the managed instance group, the specified instances will be verified as healthy after they are started. You can specify a maximum of 1000 instances with this method per request.
Scopes:
Parameters:
instanceGroupManager
Location: path
Type: string
Required: Yes
Description: The name of the managed instance group.
zone
Description: The name of the zone where the managed instance group is located.
Type: string
Location: path
Required: Yes
project
Type: string
Location: path
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
Description: Project ID for this request.
requestId
Type: string
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
Path: projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/startInstances
Parameter Order:
HTTP Method: POST
Flat Path: projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/startInstances
▼ ▲ compute.instanceGroupManagers.stopInstances
Parameters:
instanceGroupManager
Required: Yes
Type: string
Location: path
Description: The name of the managed instance group.
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).
zone
Required: Yes
Type: string
Description: The name of the zone where the managed instance group is located.
Location: path
project
Required: Yes
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])?))
Type: string
Description: Project ID for this request.
Location: path
Description: Flags the specified instances in the managed instance group to be immediately stopped. You can only specify instances that are running in this request. This method reduces the targetSize and increases the targetStoppedSize of the managed instance group by the number of instances that you stop. The stopInstances operation is marked DONE if the stopInstances request is successful. The underlying actions take additional time. You must separately verify the status of the STOPPING action with the listmanagedinstances method. If the standbyPolicy.initialDelaySec field is set, the group delays stopping the instances until initialDelaySec have passed from instance.creationTimestamp (that is, when the instance was created). This delay gives your application time to set itself up and initialize on the instance. If more than initialDelaySec seconds have passed since instance.creationTimestamp when this method is called, there will be zero delay. 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 stopped. Stopped instances can be started using the startInstances method. You can specify a maximum of 1000 instances with this method per request.
HTTP Method: POST
Flat Path: projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/stopInstances
Parameter Order:
Scopes:
Path: projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/stopInstances
▼ ▲ compute.nodeGroups.performMaintenance
HTTP Method: POST
Description: Perform maintenance on a subset of nodes in the node group.
Scopes:
Flat Path: projects/{project}/zones/{zone}/nodeGroups/{nodeGroup}/performMaintenance
Parameter Order:
Path: projects/{project}/zones/{zone}/nodeGroups/{nodeGroup}/performMaintenance
Parameters:
project
Description: Project ID for this request.
Required: Yes
Location: path
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])?))
Type: string
nodeGroup
Description: Name of the node group scoping this request.
Pattern: [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location: path
Type: string
Required: Yes
requestId
Location: query
Type: string
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).
zone
Description: The name of the zone for this request.
Type: string
Required: Yes
Pattern: [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location: path
▼ ▲ compute.urlMaps.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Type: string
Location: query
▼ ▲ compute.instances.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Location: query
Type: string
▼ ▲ compute.nodeTemplates.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Type: string
Location: query
▼ ▲ compute.subnetworks.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Type: string
Location: query
▼ ▲ compute.forwardingRules.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Location: query
Format: int64
▼ ▲ compute.targetTcpProxies.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Location: query
Format: int64
▼ ▲ compute.resourcePolicies.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Location: query
Format: int64
▼ ▲ compute.vpnGateways.aggregatedList
Parameters:
serviceProjectNumber
Location: query
Format: int64
Type: string
▼ ▲ compute.networkEndpointGroups.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Location: query
Type: string
▼ ▲ compute.diskTypes.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Type: string
Location: query
▼ ▲ compute.instanceGroups.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Location: query
Format: int64
▼ ▲ compute.autoscalers.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Type: string
Location: query
▼ ▲ compute.addresses.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Location: query
Format: int64
▼ ▲ compute.targetInstances.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Format: int64
Location: query
▼ ▲ compute.instanceGroupManagers.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Format: int64
Location: query
▼ ▲ compute.targetHttpProxies.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Location: query
Type: string
▼ ▲ compute.networkEdgeSecurityServices.aggregatedList
Parameters:
serviceProjectNumber
Location: query
Format: int64
Type: string
▼ ▲ compute.securityPolicies.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Location: query
Type: string
▼ ▲ compute.regionCommitments.aggregatedList
Parameters:
serviceProjectNumber
Location: query
Type: string
Format: int64
▼ ▲ compute.interconnectAttachments.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Format: int64
Location: query
▼ ▲ compute.nodeTypes.aggregatedList
Parameters:
serviceProjectNumber
Location: query
Type: string
Format: int64
▼ ▲ compute.futureReservations.aggregatedList
Parameters:
serviceProjectNumber
Location: query
Type: string
Format: int64
▼ ▲ compute.sslPolicies.aggregatedList
Parameters:
serviceProjectNumber
Location: query
Type: string
Format: int64
▼ ▲ compute.disks.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Location: query
Type: string
▼ ▲ compute.reservations.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Type: string
Location: query
▼ ▲ compute.targetVpnGateways.aggregatedList
Parameters:
serviceProjectNumber
Location: query
Format: int64
Type: string
▼ ▲ compute.globalOperations.aggregatedList
Parameters:
serviceProjectNumber
Location: query
Format: int64
Type: string
▼ ▲ compute.packetMirrorings.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Location: query
Type: string
▼ ▲ compute.healthChecks.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Type: string
Location: query
▼ ▲ compute.serviceAttachments.aggregatedList
Parameters:
serviceProjectNumber
Location: query
Type: string
Format: int64
▼ ▲ compute.targetPools.aggregatedList
Parameters:
serviceProjectNumber
Location: query
Format: int64
Type: string
▼ ▲ compute.sslCertificates.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Location: query
Format: int64
▼ ▲ compute.routers.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Format: int64
Location: query
▼ ▲ compute.publicDelegatedPrefixes.aggregatedList
Parameters:
serviceProjectNumber
Location: query
Format: int64
Type: string
▼ ▲ compute.targetHttpsProxies.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Location: query
Format: int64
▼ ▲ compute.vpnTunnels.aggregatedList
Parameters:
serviceProjectNumber
Location: query
Type: string
Format: int64
▼ ▲ compute.backendServices.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Location: query
Format: int64
▼ ▲ compute.nodeGroups.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Format: int64
Location: query
▼ ▲ compute.instantSnapshots.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Format: int64
Location: query
▼ ▲ compute.networkAttachments.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Location: query
Format: int64
▼ ▲ compute.machineTypes.aggregatedList
Parameters:
serviceProjectNumber
Type: string
Location: query
Format: int64
▼ ▲ compute.instanceTemplates.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Type: string
Location: query
▼ ▲ compute.acceleratorTypes.aggregatedList
Parameters:
serviceProjectNumber
Format: int64
Location: query
Type: string