2026-07-05
▼ ▲ compute.routers.updateNamedSet
Parameter Order :
Scopes :
Description : Updates or creates new Named Set
Flat Path : projects/{project}/regions/{region}/routers/{router}/updateNamedSet
HTTP Method : POST
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
router
Location : path
Required : Yes
Description : Name of the Router resource where Named Set is defined.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
region
Type : string
Description : Name of the region for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
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
Path : projects/{project}/regions/{region}/routers/{router}/updateNamedSet
▼ ▲ compute.routers.deleteNamedSet
Parameter Order :
Scopes :
Description : Deletes Named Set
Flat Path : projects/{project}/regions/{region}/routers/{router}/deleteNamedSet
HTTP Method : POST
Parameters :
namedSet
Type : string
Description : The Named Set name for this request. Name must conform to RFC1035
Location : query
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
region
Description : Name of the region for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Location : path
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).
Location : query
Type : string
router
Location : path
Required : Yes
Description : Name of the Router resource where Named Set is defined.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Path : projects/{project}/regions/{region}/routers/{router}/deleteNamedSet
▼ ▲ compute.routers.getNamedSet
Flat Path : projects/{project}/regions/{region}/routers/{router}/getNamedSet
Parameter Order :
Scopes :
Description : Returns specified Named Set
Path : projects/{project}/regions/{region}/routers/{router}/getNamedSet
Parameters :
project
Location : path
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])?))
Type : string
router
Description : Name of the Router resource to query for the named set. The name should conform to RFC1035.
Location : path
Type : string
Required : Yes
namedSet
Description : The Named Set name for this request. Name must conform to RFC1035
Location : query
Type : string
region
Description : Name of the region for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Location : path
Required : Yes
HTTP Method : GET
▼ ▲ compute.routers.patchNamedSet
Flat Path : projects/{project}/regions/{region}/routers/{router}/patchNamedSet
Parameter Order :
Scopes :
Description : Patches Named Set
Path : projects/{project}/regions/{region}/routers/{router}/patchNamedSet
Parameters :
project
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])?))
Type : string
Location : path
Required : Yes
router
Type : string
Description : Name of the Router resource where Named Set is defined.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Required : Yes
Location : path
region
Required : Yes
Location : path
Type : string
Description : Name of the region for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
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
HTTP Method : POST
▼ ▲ compute.routers.listNamedSets
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.
Location : query
Type : string
region
Description : Name of the region for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Location : path
Required : Yes
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
router
Location : path
Required : Yes
Description : Name or id of the resource for this request. Name should conform to RFC1035.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
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
returnPartialSuccess
Type : boolean
Description : Opt-in for partial success behavior which provides partial results in case of failure. The default value is false. For example, when partial success behavior is enabled, aggregatedList for a single zone scope either returns all resources in the zone or no resources, with an error code.
Location : query
maxResults
Location : query
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`)
Default : 500
Type : integer
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
Path : projects/{project}/regions/{region}/routers/{router}/listNamedSets
HTTP Method : GET
Flat Path : projects/{project}/regions/{region}/routers/{router}/listNamedSets
Parameter Order :
Scopes :
Description : Retrieves a list of router named set subresources available to the specified project.
▼ ▲ compute.regionInstanceGroupManagers.deleteInstances
Parameters :
noGracefulShutdown
Type : boolean
Default : false
Description : When set, graceful shutdown is skipped for instance deletion even if it's configured for the instances.
Location : query
▼ ▲ compute.regionInstanceGroupManagers.delete
Parameters :
noGracefulShutdown
Type : boolean
Default : false
Description : When set, graceful shutdown is skipped for instance deletion even if it's configured for the instances.
Location : query
▼ ▲ compute.regionInstanceGroupManagers.recreateInstances
Parameters :
noGracefulShutdown
Description : When set, graceful shutdown is skipped for instance recreation even if it's configured for the instances.
Location : query
Default : false
Type : boolean
▼ ▲ compute.regionInstanceGroupManagers.stopInstances
Parameters :
noGracefulShutdown
Type : boolean
Default : false
Description : When set, graceful shutdown is skipped for instance stopping even if it's configured for the instances.
Location : query
▼ ▲ compute.instanceGroupManagers.stopInstances
Parameters :
noGracefulShutdown
Default : false
Description : When set, graceful shutdown is skipped for instance stopping even if it's configured for the instances.
Location : query
Type : boolean
▼ ▲ compute.instanceGroupManagers.recreateInstances
Parameters :
noGracefulShutdown
Default : false
Description : When set, graceful shutdown is skipped for instance recreation even if it's configured for the instances.
Location : query
Type : boolean
▼ ▲ compute.instanceGroupManagers.delete
Parameters :
noGracefulShutdown
Description : When set, graceful shutdown is skipped for instance deletion even if it's configured for the instances.
Location : query
Default : false
Type : boolean
▼ ▲ compute.instanceGroupManagers.deleteInstances
Parameters :
noGracefulShutdown
Type : boolean
Default : false
Description : When set, graceful shutdown is skipped for instance deletion even if it's configured for the instances.
Location : query