2026-10-22
▼ ▲ compute.regionSslCertificates.fetchEncryptionKey
HTTP Method : GET
Path : projects/{project}/regions/{region}/sslCertificates/encryptionKey
Parameter Order :
Parameters :
project
Description : Project ID for this request.
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])?))
Required : Yes
region
Description : Name of the region scoping this request.
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Apiversion : 2026-10-01-preview
Description : Returns the public encryption key used to encrypt the TLS private key before upload.
Scopes :
Flat Path : projects/{project}/regions/{region}/sslCertificates/encryptionKey
▼ ▲ compute.folderZoneVmExtensionPolicies.listVmExtensions
Parameters :
maxResults
Format : uint32
Type : integer
Default : 500
Minimum : 0
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Location : query
zone
Description : Name of the zone for this request.
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Required : Yes
folder
Description : Folder ID for this request.
Location : path
Required : Yes
Type : string
Pattern : folders/[0-9]{0,20}
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Type : string
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
Location : query
filter
Type : string
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Description : Lists all VM extensions within a specific zone for a folder. This is a read-only API.
Apiversion : 2026-10-01-preview
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensions
Path : {+folder}/zones/{zone}/vmExtensions
Parameter Order :
HTTP Method : GET
Scopes :
▼ ▲ compute.folderZoneVmExtensionPolicies.delete
Description : Deletes a specified zone VM extension policy within a folder.
Path : {+folder}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
HTTP Method : DELETE
Scopes :
Parameter Order :
Parameters :
zone
Type : string
Required : Yes
Description : Name of the zone for this request.
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
folder
Location : path
Pattern : folders/[0-9]{0,20}
Type : string
Required : Yes
Description : Folder ID for this request.
vmExtensionPolicy
Location : path
Required : Yes
Type : string
Description : Name of the zone VM extension policy to delete.
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
Apiversion : 2026-10-01-preview
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
▼ ▲ compute.folderZoneVmExtensionPolicies.insert
Path : {+folder}/zones/{zone}/vmExtensionPolicies
Scopes :
HTTP Method : POST
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).
Type : string
Location : query
zone
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Description : Name of the zone for this request.
Location : path
folder
Required : Yes
Description : Folder ID for this request.
Pattern : folders/[0-9]{0,20}
Location : path
Type : string
Parameter Order :
Apiversion : 2026-10-01-preview
Description : Creates a new zone-level VM extension policy within a folder.
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies
▼ ▲ compute.folderZoneVmExtensionPolicies.update
HTTP Method : PATCH
Parameter Order :
Scopes :
Description : Modifies an existing zone VM extension policy within a folder.
Apiversion : 2026-10-01-preview
Path : {+folder}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Parameters :
vmExtensionPolicy
Location : path
Required : Yes
Description : Name of the zone VM extension policy to update.
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).
zone
Location : path
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
Description : Name of the zone for this request.
folder
Description : Folder ID for this request.
Required : Yes
Type : string
Pattern : folders/[0-9]{0,20}
Location : path
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
▼ ▲ compute.folderZoneVmExtensionPolicies.list
Parameters :
zone
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
Location : path
Description : Name of the zone for this request.
maxResults
Location : query
Default : 500
Minimum : 0
Type : integer
Format : uint32
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
filter
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Location : query
orderBy
Type : string
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Type : string
folder
Required : Yes
Description : Folder ID for this request.
Type : string
Location : path
Pattern : folders/[0-9]{0,20}
Scopes :
Apiversion : 2026-10-01-preview
Parameter Order :
Description : Lists all VM extension policies within a specific zone for a folder.
Path : {+folder}/zones/{zone}/vmExtensionPolicies
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies
HTTP Method : GET
▼ ▲ compute.folderZoneVmExtensionPolicies.getVmExtension
Parameter Order :
Apiversion : 2026-10-01-preview
Parameters :
folder
Location : path
Pattern : folders/[0-9]{0,20}
Type : string
Description : Folder ID for this request.
Required : Yes
extensionName
Description : Required. Name of the VM extension for this request.
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Required : Yes
zone
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Description : Name of the zone for this request.
Location : path
Scopes :
Description : Retrieves details of a specific VM extension within a folder.
HTTP Method : GET
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensions/{extensionName}
Path : {+folder}/zones/{zone}/vmExtensions/{extensionName}
▼ ▲ compute.folderZoneVmExtensionPolicies.get
Scopes :
Parameter Order :
Path : {+folder}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
HTTP Method : GET
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Description : Retrieves details of a specific zone VM extension policy within a folder.
Parameters :
zone
Type : string
Location : path
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
vmExtensionPolicy
Required : Yes
Type : string
Location : path
Description : Name of the VM extension policy resource to return.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
folder
Description : Folder ID for this request.
Location : path
Pattern : folders/[0-9]{0,20}
Type : string
Required : Yes
Apiversion : 2026-10-01-preview
▼ ▲ compute.zoneFolderOperations.get
Apiversion : 2026-10-01-preview
Parameters :
operation
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location : path
Type : string
Required : Yes
Description : Name of the Operations resource to return.
zone
Location : path
Description : Name of the zone for this request.
Type : string
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
folder
Pattern : folders/[0-9]{0,20}
Required : Yes
Description : Folder ID for this request.
Location : path
Type : string
Scopes :
Path : {+folder}/zones/{zone}/operations/{operation}
HTTP Method : GET
Parameter Order :
Description : Retrieves the specified Operations resource.
Flat Path : folders/{foldersId}/zones/{zone}/operations/{operation}
▼ ▲ compute.zoneFolderOperations.list
Description : Retrieves a list of Operation resources contained within the specified folder.
Scopes :
Flat Path : folders/{foldersId}/zones/{zone}/operations
Path : {+folder}/zones/{zone}/operations
HTTP Method : GET
Parameter Order :
Parameters :
zone
Description : Name of the zone for request.
Type : string
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Location : query
Type : string
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
Location : query
folder
Required : Yes
Type : string
Description : Folder ID for this request.
Location : path
Pattern : folders/[0-9]{0,20}
pageToken
Type : string
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
maxResults
Location : query
Default : 500
Minimum : 0
Format : uint32
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Type : integer
Apiversion : 2026-10-01-preview
▼ ▲ compute.zoneVmExtensionPolicies.getVmExtension
Parameter Order :
Parameters :
extensionName
Description : Required. Name of the VM extension for 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
zone
Required : Yes
Description : Name of the zone for this request.
Location : path
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
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])?))
Description : Project ID for this request.
Required : Yes
Type : string
Apiversion : 2026-10-01-preview
Path : projects/{project}/zones/{zone}/vmExtensions/{extensionName}
Flat Path : projects/{project}/zones/{zone}/vmExtensions/{extensionName}
HTTP Method : GET
Scopes :
Description : Retrieves details of a specific VM extension within a project.
▼ ▲ compute.zoneVmExtensionPolicies.listVmExtensions
HTTP Method : GET
Parameters :
zone
Description : Name of the zone for this request.
Location : path
Type : string
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
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
Location : path
Description : Required. Project ID for this request.
pageToken
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Type : string
orderBy
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
maxResults
Type : integer
Location : query
Format : uint32
Default : 500
Minimum : 0
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
filter
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Location : query
Path : projects/{project}/zones/{zone}/vmExtensions
Scopes :
Description : Lists all VM extensions within a specific zone for a project. This is a read-only API.
Apiversion : 2026-10-01-preview
Parameter Order :
Flat Path : projects/{project}/zones/{zone}/vmExtensions
▼ ▲ compute.sslCertificates.fetchEncryptionKey
HTTP Method : GET
Description : Returns the public encryption key used to encrypt the TLS private key before upload.
Scopes :
Parameter Order : project
Parameters :
project
Description : Project ID for this request.
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])?))
Required : Yes
Path : projects/{project}/global/sslCertificates/encryptionKey
Flat Path : projects/{project}/global/sslCertificates/encryptionKey
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationZoneVmExtensionPolicies.delete
HTTP Method : DELETE
Description : Deletes a specified zone VM extension policy within an organization.
Path : {+organization}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Parameter Order :
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
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Type : string
Required : Yes
Description : Name of the zone for this request.
vmExtensionPolicy
Description : Name of the zone VM extension policy to delete.
Location : path
Required : Yes
Type : string
organization
Required : Yes
Type : string
Pattern : organizations/[0-9]{0,20}
Description : Organization ID for this request.
Location : path
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Apiversion : 2026-10-01-preview
Scopes :
▼ ▲ compute.organizationZoneVmExtensionPolicies.list
HTTP Method : GET
Description : Lists all VM extension policies within a specific zone for an organization.
Scopes :
Parameter Order :
Apiversion : 2026-10-01-preview
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies
Path : {+organization}/zones/{zone}/vmExtensionPolicies
Parameters :
maxResults
Location : query
Type : integer
Default : 500
Minimum : 0
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Format : uint32
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
Location : query
organization
Type : string
Required : Yes
Description : Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
Location : path
zone
Description : Name of the zone for this request.
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Required : Yes
pageToken
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Type : string
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
Type : string
▼ ▲ compute.organizationZoneVmExtensionPolicies.getVmExtension
Description : Retrieves details of a specific VM extension within an organization.
Apiversion : 2026-10-01-preview
Parameters :
organization
Description : Organization ID for this request.
Location : path
Required : Yes
Pattern : organizations/[0-9]{0,20}
Type : string
extensionName
Required : Yes
Description : Required. Name of the VM extension for this request.
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location : path
zone
Required : Yes
Description : Name of the zone for this request.
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Scopes :
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensions/{extensionName}
HTTP Method : GET
Parameter Order :
Path : {+organization}/zones/{zone}/vmExtensions/{extensionName}
▼ ▲ compute.organizationZoneVmExtensionPolicies.get
Path : {+organization}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
HTTP Method : GET
Scopes :
Parameter Order :
Parameters :
vmExtensionPolicy
Description : Name of the VM extension policy resource to return.
Location : path
Type : string
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
zone
Description : Name of the zone for this request.
Required : Yes
Type : string
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
organization
Pattern : organizations/[0-9]{0,20}
Location : path
Type : string
Required : Yes
Description : Organization ID for this request.
Description : Retrieves details of a specific zone VM extension policy within an organization.
Apiversion : 2026-10-01-preview
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
▼ ▲ compute.organizationZoneVmExtensionPolicies.insert
Scopes :
Parameters :
organization
Location : path
Description : Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
Required : Yes
Type : string
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
Location : path
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Required : Yes
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies
Parameter Order :
Description : Creates a new zone-level VM extension policy within an organization.
Apiversion : 2026-10-01-preview
Path : {+organization}/zones/{zone}/vmExtensionPolicies
HTTP Method : POST
▼ ▲ compute.organizationZoneVmExtensionPolicies.update
Scopes :
Parameter Order :
Apiversion : 2026-10-01-preview
Description : Modifies an existing zone VM extension policy within an organization.
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
vmExtensionPolicy
Location : path
Required : Yes
Description : Name of the zone VM extension policy to update.
Type : string
zone
Type : string
Description : Name of the zone for this request.
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
organization
Required : Yes
Pattern : organizations/[0-9]{0,20}
Type : string
Description : Organization ID for this request.
Location : path
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
HTTP Method : PATCH
Path : {+organization}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
▼ ▲ compute.organizationZoneVmExtensionPolicies.listVmExtensions
Apiversion : 2026-10-01-preview
Path : {+organization}/zones/{zone}/vmExtensions
Parameters :
maxResults
Default : 500
Minimum : 0
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Format : uint32
Location : query
Type : integer
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Type : string
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Location : query
Type : string
organization
Required : Yes
Type : string
Pattern : organizations/[0-9]{0,20}
Location : path
Description : Organization ID for this request.
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Location : path
Description : Name of the zone for this request.
Required : Yes
orderBy
Location : query
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Description : Lists all VM extensions within a specific zone for an organization. This is a read-only API.
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensions
Parameter Order :
HTTP Method : GET
Scopes :
▼ ▲ compute.globalFolderOperations.list
Parameter Order : folder
HTTP Method : GET
Flat Path : folders/{foldersId}/global/operations
Scopes :
Parameters :
folder
Pattern : folders/[0-9]{0,20}
Location : path
Required : Yes
Description : Folder ID for this request.
Type : string
pageToken
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Type : string
orderBy
Type : string
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
filter
Location : query
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
maxResults
Location : query
Default : 500
Minimum : 0
Type : integer
Format : uint32
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Apiversion : 2026-10-01-preview
Description : Retrieves a list of Operation resources contained within the specified folder.
Path : {+folder}/global/operations
▼ ▲ compute.globalFolderOperations.get
Flat Path : folders/{foldersId}/global/operations/{operation}
HTTP Method : GET
Path : {+folder}/global/operations/{operation}
Description : Retrieves the specified Operations resource.
Parameter Order :
Apiversion : 2026-10-01-preview
Scopes :
Parameters :
operation
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Required : Yes
Type : string
Description : Name of the Operations resource to return.
Location : path
folder
Description : Folder ID for this request.
Required : Yes
Pattern : folders/[0-9]{0,20}
Location : path
Type : string
▼ ▲ compute.zoneOrganizationOperations.get
Path : {+organization}/zones/{zone}/operations/{operation}
Parameters :
zone
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Description : Name of the zone for this request.
Required : Yes
organization
Pattern : organizations/[0-9]{0,20}
Type : string
Location : path
Description : Organization ID for this request.
Required : Yes
operation
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Required : Yes
Description : Name of the Operations resource to return. Parent is derived from this field.
Type : string
Location : path
Apiversion : 2026-10-01-preview
Flat Path : organizations/{organizationsId}/zones/{zone}/operations/{operation}
Scopes :
Parameter Order :
HTTP Method : GET
Description : Retrieves the specified Operations resource.
▼ ▲ compute.zoneOrganizationOperations.list
Scopes :
Apiversion : 2026-10-01-preview
Parameters :
maxResults
Location : query
Default : 500
Minimum : 0
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Format : uint32
Type : integer
organization
Type : string
Location : path
Required : Yes
Pattern : ^organizations/[^/]+$
Description : Organization ID for this request.
zone
Type : string
Description : Name of the zone for request.
Required : Yes
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
orderBy
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
filter
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Location : query
pageToken
Location : query
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Flat Path : organizations/{organizationsId}/zones/{zone}/operations
HTTP Method : GET
Path : {+organization}/zones/{zone}/operations
Description : Retrieves a list of Operation resources contained within the specified organization.
Parameter Order :
▼ ▲ compute.globalVmExtensionPolicies.listVmExtensions
Parameter Order : project
Apiversion : 2026-10-01-preview
Parameters :
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
Location : query
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Location : query
Type : string
pageToken
Location : query
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
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])?))
Location : path
Type : string
Description : Required. Project ID for this request.
maxResults
Type : integer
Default : 500
Minimum : 0
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Location : query
Format : uint32
Description : Lists all VM extensions within a specific zone for a project. This is a read-only API.
Scopes :
HTTP Method : GET
Flat Path : projects/{project}/global/vmExtensions
Path : projects/{project}/global/vmExtensions
▼ ▲ compute.globalVmExtensionPolicies.getVmExtension
Apiversion : 2026-10-01-preview
Scopes :
Parameters :
extensionName
Type : string
Location : path
Required : Yes
Description : Required. Name of the VM extension for this request.
project
Required : Yes
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])?))
Location : path
Type : string
Description : Retrieves details of a specific VM extension.
Path : projects/{project}/global/vmExtensions/{extensionName}
HTTP Method : GET
Flat Path : projects/{project}/global/vmExtensions/{extensionName}
Parameter Order :
▼ ▲ compute.networks.updateNetworkProfile
Description : Updates the network profile of the specified network. Currently only the following operations are supported: - Removing a Regionally Bound Network Profile
Parameter Order :
HTTP Method : POST
Flat Path : projects/{project}/global/networks/{network}/updateNetworkProfile
Scopes :
Path : projects/{project}/global/networks/{network}/updateNetworkProfile
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
network
Location : path
Description : Name of the network resource to update the network profile for.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Required : Yes
project
Type : string
Location : path
Description : Project ID for this request.
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])?))
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationGlobalVmExtensionPolicies.insert
Parameters :
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).
organization
Location : path
Description : Organization ID for this request.
Type : string
Pattern : organizations/[0-9]{0,20}
Required : Yes
Path : {+organization}/global/vmExtensionPolicies
Apiversion : 2026-10-01-preview
Parameter Order : organization
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies
Scopes :
Description : Creates a new organization level GlobalVmExtensionPolicy.
HTTP Method : POST
▼ ▲ compute.organizationGlobalVmExtensionPolicies.update
Scopes :
HTTP Method : PATCH
Description : Updates an organization level GlobalVmExtensionPolicy.
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
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
globalVmExtensionPolicy
Type : string
Location : path
Required : Yes
Description : Name of the global VM extension policy to update.
organization
Location : path
Description : Organization ID for this request.
Type : string
Required : Yes
Pattern : organizations/[0-9]{0,20}
Apiversion : 2026-10-01-preview
Path : {+organization}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Parameter Order :
▼ ▲ compute.organizationGlobalVmExtensionPolicies.listVmExtensions
Scopes :
Parameters :
maxResults
Type : integer
Default : 500
Minimum : 0
Location : query
Format : uint32
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
organization
Required : Yes
Pattern : organizations/[0-9]{0,20}
Location : path
Type : string
Description : Required. Organization ID for this request.
orderBy
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
filter
Type : string
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
pageToken
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Apiversion : 2026-10-01-preview
Path : {+organization}/global/vmExtensions
Parameter Order : organization
Description : Lists all VM extensions within an organization. This is a read-only API.
Flat Path : organizations/{organizationsId}/global/vmExtensions
HTTP Method : GET
▼ ▲ compute.organizationGlobalVmExtensionPolicies.list
Scopes :
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies
Apiversion : 2026-10-01-preview
Description : Lists organization level GlobalVmExtensionPolicies.
Path : {+organization}/global/vmExtensionPolicies
Parameters :
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Type : string
filter
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
orderBy
Location : query
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
maxResults
Type : integer
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Default : 500
Minimum : 0
Format : uint32
Location : query
organization
Type : string
Required : Yes
Location : path
Description : Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
Parameter Order : organization
HTTP Method : GET
▼ ▲ compute.organizationGlobalVmExtensionPolicies.aggregatedList
Parameter Order : organization
HTTP Method : GET
Description : Retrieves the list of all organization level VM Extension Policy resources available to the specified organization. To prevent failure, it's recommended that you set the `returnPartialSuccess` parameter to `true`.
Path : {+organization}/aggregated/vmExtensionPolicies
Flat Path : organizations/{organizationsId}/aggregated/vmExtensionPolicies
Scopes :
Parameters :
pageToken
Type : string
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
serviceProjectNumber
Location : query
Description : The Shared VPC service project id or service project number for which aggregated list request is invoked for subnetworks list-usable api.
Format : int64
Type : string
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
Location : query
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
Type : string
includeAllScopes
Location : query
Type : boolean
Description : Indicates whether every visible scope for each scope type (zone, region, global) should be included in the response. For new resource types added after this field, the flag has no effect as new resource types will always include every visible scope for each scope type in response. For resource types which predate this field, if this flag is omitted or false, only scopes of the scope types where the resource type is expected to be found will be included.
organization
Required : Yes
Pattern : organizations/[0-9]{0,20}
Type : string
Location : path
Description : Organization ID for this request.
maxResults
Location : query
Format : uint32
Default : 500
Minimum : 0
Type : integer
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationGlobalVmExtensionPolicies.delete
Parameter Order :
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
Apiversion : 2026-10-01-preview
Parameters :
globalVmExtensionPolicy
Description : Name of the global VM extension policy to purge scoped resources for.
Type : string
Location : path
Required : Yes
organization
Pattern : organizations/[0-9]{0,20}
Required : Yes
Description : Organization ID for this request.
Type : string
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
Description : Purge scoped resources (zonal policies) from an organization level global VM extension policy, and then delete the global VM extension policy. Purge of the scoped resources is a pre-condition of the global VM extension policy deletion. The deletion of the global VM extension policy happens after the purge rollout is done, so it's not a part of the LRO. It's an automatic process that triggers in the backend.
HTTP Method : POST
Scopes :
Path : {+organization}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
▼ ▲ compute.organizationGlobalVmExtensionPolicies.getVmExtension
Scopes :
Path : {+organization}/global/vmExtensions/{extensionName}
Parameters :
extensionName
Type : string
Location : path
Required : Yes
Description : Required. Name of the VM extension for this request.
organization
Required : Yes
Type : string
Description : Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
Location : path
Apiversion : 2026-10-01-preview
Parameter Order :
Flat Path : organizations/{organizationsId}/global/vmExtensions/{extensionName}
Description : Retrieves details of a specific VM extension.
HTTP Method : GET
▼ ▲ compute.organizationGlobalVmExtensionPolicies.get
Parameters :
organization
Required : Yes
Location : path
Pattern : organizations/[0-9]{0,20}
Description : Organization ID for this request.
Type : string
globalVmExtensionPolicy
Description : Name of the GlobalVmExtensionPolicy resource to return.
Required : Yes
Type : string
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Apiversion : 2026-10-01-preview
Description : Gets details of an organization level GlobalVmExtensionPolicy.
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Parameter Order :
Scopes :
Path : {+organization}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
HTTP Method : GET
▼ ▲ compute.folderGlobalVmExtensionPolicies.get
Flat Path : folders/{foldersId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
HTTP Method : GET
Description : Gets details of a folder level GlobalVmExtensionPolicy.
Parameters :
globalVmExtensionPolicy
Description : Name of the GlobalVmExtensionPolicy resource to return.
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location : path
Type : string
folder
Location : path
Pattern : folders/[0-9]{0,20}
Required : Yes
Type : string
Description : Folder ID for this request.
Path : {+folder}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Scopes :
Apiversion : 2026-10-01-preview
Parameter Order :
▼ ▲ compute.folderGlobalVmExtensionPolicies.delete
Flat Path : folders/{foldersId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
Scopes :
Parameter Order :
HTTP Method : POST
Path : {+folder}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
Description : Purge scoped resources (zonal policies) from a folder level global VM extension policy, and then delete the global VM extension policy. Purge of the scoped resources is a pre-condition of the global VM extension policy deletion. The deletion of the global VM extension policy happens after the purge rollout is done, so it's not a part of the LRO. It's an automatic process that triggers in the backend.
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
folder
Required : Yes
Type : string
Pattern : folders/[0-9]{0,20}
Location : path
Description : Folder ID for this request.
globalVmExtensionPolicy
Description : Name of the global VM extension policy to purge scoped resources for.
Location : path
Required : Yes
Type : string
Apiversion : 2026-10-01-preview
▼ ▲ compute.folderGlobalVmExtensionPolicies.listVmExtensions
HTTP Method : GET
Parameter Order : folder
Description : Lists all VM extensions within a folder. This is a read-only API.
Parameters :
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
Location : query
orderBy
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
folder
Type : string
Description : Required. Folder ID for this request.
Required : Yes
Pattern : folders/[0-9]{0,20}
Location : path
pageToken
Type : string
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
maxResults
Type : integer
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Format : uint32
Location : query
Default : 500
Minimum : 0
Flat Path : folders/{foldersId}/global/vmExtensions
Apiversion : 2026-10-01-preview
Path : {+folder}/global/vmExtensions
Scopes :
▼ ▲ compute.folderGlobalVmExtensionPolicies.list
Flat Path : folders/{foldersId}/global/vmExtensionPolicies
HTTP Method : GET
Scopes :
Parameter Order : folder
Description : Lists folder level GlobalVmExtensionPolicies.
Path : {+folder}/global/vmExtensionPolicies
Apiversion : 2026-10-01-preview
Parameters :
maxResults
Format : uint32
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Location : query
Type : integer
Default : 500
Minimum : 0
folder
Description : Folder ID for this request.
Required : Yes
Pattern : folders/[0-9]{0,20}
Type : string
Location : path
orderBy
Location : query
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
pageToken
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
filter
Location : query
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
▼ ▲ compute.folderGlobalVmExtensionPolicies.aggregatedList
Scopes :
HTTP Method : GET
Parameter Order : folder
Flat Path : folders/{foldersId}/aggregated/vmExtensionPolicies
Path : {+folder}/aggregated/vmExtensionPolicies
Parameters :
serviceProjectNumber
Location : query
Description : The Shared VPC service project id or service project number for which aggregated list request is invoked for subnetworks list-usable api.
Format : int64
Type : string
maxResults
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Default : 500
Minimum : 0
Format : uint32
Type : integer
Location : query
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
Type : string
filter
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
pageToken
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
includeAllScopes
Type : boolean
Description : Indicates whether every visible scope for each scope type (zone, region, global) should be included in the response. For new resource types added after this field, the flag has no effect as new resource types will always include every visible scope for each scope type in response. For resource types which predate this field, if this flag is omitted or false, only scopes of the scope types where the resource type is expected to be found will be included.
Location : query
folder
Required : Yes
Pattern : folders/[0-9]{0,20}
Location : path
Type : string
Description : Folder ID for this request.
Apiversion : 2026-10-01-preview
Description : Retrieves the list of all folder level VM Extension Policy resources available to the specified folder. To prevent failure, it's recommended that you set the `returnPartialSuccess` parameter to `true`.
▼ ▲ compute.folderGlobalVmExtensionPolicies.insert
Flat Path : folders/{foldersId}/global/vmExtensionPolicies
Parameters :
folder
Type : string
Location : path
Description : Folder ID for this request.
Pattern : folders/[0-9]{0,20}
Required : Yes
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).
Scopes :
Apiversion : 2026-10-01-preview
Path : {+folder}/global/vmExtensionPolicies
Description : Creates a new folder level GlobalVmExtensionPolicy.
Parameter Order : folder
HTTP Method : POST
▼ ▲ compute.folderGlobalVmExtensionPolicies.update
Description : Updates a folder level GlobalVmExtensionPolicy.
HTTP Method : PATCH
Scopes :
Parameters :
globalVmExtensionPolicy
Location : path
Required : Yes
Description : Name of the global VM extension policy to update.
Type : string
folder
Type : string
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Required : Yes
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
Parameter Order :
Flat Path : folders/{foldersId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Apiversion : 2026-10-01-preview
Path : {+folder}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
▼ ▲ compute.folderGlobalVmExtensionPolicies.getVmExtension
Scopes :
Flat Path : folders/{foldersId}/global/vmExtensions/{extensionName}
HTTP Method : GET
Path : {+folder}/global/vmExtensions/{extensionName}
Parameter Order :
Description : Retrieves details of a specific VM extension.
Apiversion : 2026-10-01-preview
Parameters :
extensionName
Type : string
Location : path
Required : Yes
Description : Required. Name of the VM extension for this request.
folder
Pattern : folders/[0-9]{0,20}
Location : path
Type : string
Description : Folder ID for this request.
Required : Yes
▼ ▲ compute.instances.update
Parameters :
mostDisruptiveAllowedAction
Enum RESTART_IN_PLACE
Enum Descriptions The instance will restart on the same host. Data on all local SSDs will be preserved.
minimalAction
Enum RESTART_IN_PLACE
Enum Descriptions The instance will restart on the same host. Data on all local SSDs will be preserved.
▼ ▲ compute.instances.troubleshoot
Description : Initiates diagnostic troubleshooting on the specified instance. This operation cannot be cancelled.
Parameter Order :
Parameters :
project
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
Required : Yes
Description : Project ID for this request.
instance
Description : Name of the instance scoping this request.
Type : string
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
zone
Type : string
Required : Yes
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : The name of the zone for this request.
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).
params.startTime
Location : query
Description : Input only. Timestamp representing the beginning of the troubleshooting window in RFC3339 text format. If omitted, defaults to the last 12 hours.
Type : string
params.endTime
Location : query
Description : Input only. Timestamp representing the end of the troubleshooting window in RFC3339 text format. If omitted, defaults to 'now'.
Type : string
Scopes :
Apiversion : 2026-10-01-preview
Path : projects/{project}/zones/{zone}/instances/{instance}/troubleshoot
Flat Path : projects/{project}/zones/{zone}/instances/{instance}/troubleshoot
HTTP Method : POST