2023-08-21
▼ ▲ compute.resourcePolicies.getNetworkCapacityConstraints
Description : Returns the network capacity constraints for the specified placement policies.
Parameter Order :
Scopes :
Flat Path : projects/{project}/regions/{region}/resourcePolicies/getNetworkCapacityConstraints
Parameters :
project
Description : Project ID for this request.
Type : string
Location : path
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Required : Yes
region
Description : Name of the region for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
Location : path
Type : string
resourcePolicies
Type : string
Location : query
Description : Partial or full URL of the resource policies for which to retrieve the network capacity constraints.
Repeated : Yes
Path : projects/{project}/regions/{region}/resourcePolicies/getNetworkCapacityConstraints
HTTP Method : POST
▼ ▲ compute.networkFirewallPolicies.patchAssociation
Parameter Order :
Description : Updates an association for the specified network firewall policy.
HTTP Method : POST
Flat Path : projects/{project}/global/firewallPolicies/{firewallPolicy}/patchAssociation
Path : projects/{project}/global/firewallPolicies/{firewallPolicy}/patchAssociation
Parameters :
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])?))
Description : Project ID for this request.
Type : string
Location : path
Required : Yes
firewallPolicy
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Name of the firewall policy to update.
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
Scopes :