2026-10-31
▼ ▲ compute.folderRolloutPlans.get
Description : Gets details of a single folder-scoped RolloutPlan.
Flat Path : folders/{foldersId}/global/rolloutPlans/{rolloutPlan}
Apiversion : 2026-10-01-preview
HTTP Method : GET
Parameters :
rolloutPlan
Location : path
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Name of the persistent rollout plan to return.
folder
Required : Yes
Pattern : folders/[0-9]{0,20}
Location : path
Type : string
Description : Folder ID for this request.
Scopes :
Parameter Order :
Path : {+folder}/global/rolloutPlans/{rolloutPlan}
▼ ▲ compute.folderRolloutPlans.list
Apiversion : 2026-10-01-preview
HTTP Method : GET
Parameters :
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.
maxResults
Format : uint32
Type : integer
Location : query
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`)
Default : 500
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
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
folder
Description : Folder ID for this request.
Location : path
Required : Yes
Pattern : folders/[0-9]{0,20}
Type : string
Path : {+folder}/global/rolloutPlans
Flat Path : folders/{foldersId}/global/rolloutPlans
Description : Lists FolderRolloutPlans in a given folder and location.
Scopes :
Parameter Order : folder
▼ ▲ compute.folderRolloutPlans.insert
Apiversion : 2026-10-01-preview
HTTP Method : POST
Parameters :
folder
Type : string
Description : Folder ID for this request.
Location : path
Pattern : folders/[0-9]{0,20}
Required : Yes
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
Path : {+folder}/global/rolloutPlans
Scopes :
Parameter Order : folder
Description : Creates a new RolloutPlan in a given folder and location.
Flat Path : folders/{foldersId}/global/rolloutPlans
▼ ▲ compute.folderRolloutPlans.delete
Description : Deletes a FolderRolloutPlan.
Path : {+folder}/global/rolloutPlans/{rolloutPlan}
Apiversion : 2026-10-01-preview
HTTP Method : DELETE
Parameters :
folder
Type : string
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Location : path
Required : Yes
rolloutPlan
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Name of the FolderRolloutPlan resource to delete.
Required : Yes
Location : path
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
Flat Path : folders/{foldersId}/global/rolloutPlans/{rolloutPlan}
Parameter Order :
Scopes :
▼ ▲ compute.folderRollouts.delete
Description : Deletes a Rollout.
Path : {+folder}/global/rollouts/{rollout}
Apiversion : 2026-10-01-preview
HTTP Method : DELETE
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
rollout
Required : Yes
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Name of the Rollout resource to delete.
Type : string
folder
Location : path
Required : Yes
Pattern : folders/[0-9]{1,19}
Description : Required. Folder ID for this request.
Type : string
Flat Path : folders/{foldersId}/global/rollouts/{rollout}
Scopes :
Parameter Order :
▼ ▲ compute.folderRollouts.advance
Scopes :
Parameter Order :
Apiversion : 2026-10-01-preview
HTTP Method : POST
Parameters :
rollout
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location : path
Description : Required. Name of the Rollout resource to advance.
Required : Yes
Type : string
currentWaveNumber
Type : string
Location : query
Description : Required. Wave number of the current wave.
Format : int64
folder
Pattern : folders/[0-9]{1,19}
Description : Required. Folder ID for this request.
Required : Yes
Location : path
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).
Path : {+folder}/global/rollouts/{rollout}/advance
Description : Advances a Rollout to the next wave, or completes it if no waves remain.
Flat Path : folders/{foldersId}/global/rollouts/{rollout}/advance
▼ ▲ compute.folderRollouts.list
Description : Lists Rollouts in a given folder and location.
Scopes :
Path : {+folder}/global/rollouts
Parameter Order : folder
Flat Path : folders/{foldersId}/global/rollouts
Apiversion : 2026-10-01-preview
HTTP Method : GET
Parameters :
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.
folder
Location : path
Required : Yes
Description : Required. Folder ID for this request.
Type : string
Pattern : folders/[0-9]{1,19}
maxResults
Default : 500
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
Minimum : 0
Type : integer
Format : uint32
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
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.
Type : string
Location : query
▼ ▲ compute.folderRollouts.cancel
Path : {+folder}/global/rollouts/{rollout}
Scopes :
Flat Path : folders/{foldersId}/global/rollouts/{rollout}
Apiversion : 2026-10-01-preview
HTTP Method : PATCH
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
rollout
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Required : Yes
Description : Name of the Rollout resource to cancel.
Location : path
Type : string
folder
Location : path
Required : Yes
Description : Required. Folder ID for this request.
Type : string
Pattern : folders/[0-9]{1,19}
rollback
Type : boolean
Description : Optional. If true, then the ongoing rollout must be rolled back. Else, just cancel the rollout without taking any further actions. Note that products must support at least one of these options, however, it does not need to support both.
Location : query
Description : Cancels a Rollout.
Parameter Order :
▼ ▲ compute.folderRollouts.get
Path : {+folder}/global/rollouts/{rollout}
Apiversion : 2026-10-01-preview
HTTP Method : GET
Parameters :
rollout
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Name of the persistent rollout to return.
Type : string
Location : path
Required : Yes
folder
Pattern : folders/[0-9]{0,20}
Required : Yes
Location : path
Description : Folder ID for this request.
Type : string
Description : Gets details of a single folder-scoped Rollout.
Parameter Order :
Scopes :
Flat Path : folders/{foldersId}/global/rollouts/{rollout}
▼ ▲ compute.folderRollouts.pause
Description : Pauses a Rollout.
Path : {+folder}/global/rollouts/{rollout}/pause
Parameter Order :
Flat Path : folders/{foldersId}/global/rollouts/{rollout}/pause
Scopes :
Apiversion : 2026-10-01-preview
HTTP Method : POST
Parameters :
folder
Required : Yes
Location : path
Type : string
Pattern : folders/[0-9]{1,19}
Description : Required. Folder ID for this request.
rollout
Required : Yes
Description : Required. Name of the Rollout resource to pause.
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
etag
Description : The etag of the Rollout. If this is provided, the request will only succeed if the etag matches the current etag of the Rollout.
Type : string
Location : query
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
▼ ▲ compute.folderRollouts.resume
Flat Path : folders/{foldersId}/global/rollouts/{rollout}/resume
Apiversion : 2026-10-01-preview
HTTP Method : POST
Parameters :
etag
Type : string
Description : The etag of the Rollout. If this is provided, the request will only succeed if the etag matches the current etag of the Rollout.
Location : query
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).
folder
Pattern : folders/[0-9]{1,19}
Type : string
Description : Required. Folder ID for this request.
Required : Yes
Location : path
rollout
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Required. Name of the Rollout resource to resume.
Location : path
Type : string
Required : Yes
Parameter Order :
Scopes :
Path : {+folder}/global/rollouts/{rollout}/resume
Description : Resumes a Rollout.
▼ ▲ compute.networkLocationBindings.get
Scopes :
Apiversion : 2026-10-01-preview
HTTP Method : GET
Parameters :
project
Type : string
Description : Project ID for this request.
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Required : Yes
Location : path
networkLocationBinding
Description : Name of the NetworkLocationBinding resource to return.
Required : Yes
Location : path
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
region
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
Type : string
Location : path
Description : Name of the region of this request.
Flat Path : projects/{project}/regions/{region}/networkLocationBindings/{networkLocationBinding}
Description : Returns the specified NetworkLocationBinding resource in the given scope.
Path : projects/{project}/regions/{region}/networkLocationBindings/{networkLocationBinding}
Parameter Order :
▼ ▲ compute.networkLocationBindings.list
Scopes :
Path : projects/{project}/regions/{region}/networkLocationBindings
Description : Lists the NetworkLocationBindings for a project in the given scope.
Flat Path : projects/{project}/regions/{region}/networkLocationBindings
Apiversion : 2026-10-01-preview
HTTP Method : GET
Parameters :
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.
maxResults
Location : query
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
Format : uint32
Type : integer
Minimum : 0
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 : Project ID for this request.
region
Type : string
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
Description : Name of the region of this request.
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.
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
Parameter Order :
▼ ▲ compute.sslCertificates.fetchEncryptionKey
Parameters :
name
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : query
Description : Required. Name of the SslCertificate resource to be created. The name must be 1-63 characters long, and comply withRFC1035.
▼ ▲ compute.regionSslCertificates.fetchEncryptionKey
Parameters :
name
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Required. Name of the SslCertificate resource to be created. The name must be 1-63 characters long, and comply withRFC1035.
Location : query