google-api-python-client 2.178.0__py3-none-any.whl → 2.181.0__py3-none-any.whl

googleapiclient/discovery_cache/documents/compute.v1.json

@@ -18178,6 +18178,48 @@
 "https://www.googleapis.com/auth/compute"
 ]
 },
+"requestRemovePeering": {
+"description": "Requests to remove a peering from the specified network. Applicable only for PeeringConnection with update_strategy=CONSENSUS.",
+"flatPath": "projects/{project}/global/networks/{network}/requestRemovePeering",
+"httpMethod": "POST",
+"id": "compute.networks.requestRemovePeering",
+"parameterOrder": [
+"project",
+"network"
+],
+"parameters": {
+"network": {
+"description": "Name of the network resource to remove peering from.",
+"location": "path",
+"pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}",
+"required": true,
+"type": "string"
+},
+"project": {
+"description": "Project ID for this request.",
+"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": true,
+"type": "string"
+},
+"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"
+}
+},
+"path": "projects/{project}/global/networks/{network}/requestRemovePeering",
+"request": {
+"$ref": "NetworksRequestRemovePeeringRequest"
+},
+"response": {
+"$ref": "Operation"
+},
+"scopes": [
+"https://www.googleapis.com/auth/cloud-platform",
+"https://www.googleapis.com/auth/compute"
+]
+},
 "switchToCustomMode": {
 "description": "Switches the network mode from auto subnet mode to custom subnet mode.",
 "flatPath": "projects/{project}/global/networks/{network}/switchToCustomMode",
@@ -39954,7 +39996,7 @@
 }
 }
 },
-"revision": "20250728",
+"revision": "20250810",
 "rootUrl": "https://compute.googleapis.com/",
 "schemas": {
 "AWSV4Signature": {
@@ -42771,6 +42813,10 @@ false
 "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
 "type": "string"
 },
+"params": {
+"$ref": "BackendBucketParams",
+"description": "Input only. [Input Only] Additional params passed with the request, but not persisted as part of resource payload."
+},
 "selfLink": {
 "description": "[Output Only] Server-defined URL for the resource.",
 "type": "string"
@@ -43070,6 +43116,20 @@ false
 },
 "type": "object"
 },
+"BackendBucketParams": {
+"description": "Additional Backend Bucket parameters.",
+"id": "BackendBucketParams",
+"properties": {
+"resourceManagerTags": {
+"additionalProperties": {
+"type": "string"
+},
+"description": "Tag keys/values directly bound to this resource. Tag keys and values have the same definition as resource manager tags. The field is allowed for INSERT only. The keys/values to set on the resource should be specified in either ID { : } or Namespaced format { : }. For example the following are valid inputs: * {\"tagKeys/333\" : \"tagValues/444\", \"tagKeys/123\" : \"tagValues/456\"} * {\"123/environment\" : \"production\", \"345/abc\" : \"xyz\"} Note: * Invalid combinations of ID & namespaced format is not supported. For instance: {\"123/environment\" : \"tagValues/444\"} is invalid.",
+"type": "object"
+}
+},
+"type": "object"
+},
 "BackendBucketUsedBy": {
 "id": "BackendBucketUsedBy",
 "properties": {
@@ -43281,7 +43341,7 @@ false
 "type": "array"
 },
 "localityLbPolicy": {
-"description": "The load balancing algorithm used within the scope of the locality. The possible values are: - ROUND_ROBIN: This is a simple policy in which each healthy backend is selected in round robin order. This is the default. - LEAST_REQUEST: An O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests. - RING_HASH: The ring/modulo hash load balancer implements consistent hashing to backends. The algorithm has the property that the addition/removal of a host from a set of N hosts only affects 1/N of the requests. - RANDOM: The load balancer selects a random healthy host. - ORIGINAL_DESTINATION: Backend host is selected based on the client connection metadata, i.e., connections are opened to the same address as the destination address of the incoming connection before the connection was redirected to the load balancer. - MAGLEV: used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, see https://ai.google/research/pubs/pub44824 - WEIGHTED_ROUND_ROBIN: Per-endpoint Weighted Round Robin Load Balancing using weights computed from Backend reported Custom Metrics. If set, the Backend Service responses are expected to contain non-standard HTTP response header field Endpoint-Load-Metrics. The reported metrics to use for computing the weights are specified via the customMetrics field. This field is applicable to either: - A regional backend service with the service_protocol set to HTTP, HTTPS, HTTP2 or H2C, and load_balancing_scheme set to INTERNAL_MANAGED. - A global backend service with the load_balancing_scheme set to INTERNAL_SELF_MANAGED, INTERNAL_MANAGED, or EXTERNAL_MANAGED. If sessionAffinity is not configured\u2014that is, if session affinity remains at the default value of NONE\u2014then the default value for localityLbPolicy is ROUND_ROBIN. If session affinity is set to a value other than NONE, then the default value for localityLbPolicy is MAGLEV. Only ROUND_ROBIN and RING_HASH are supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true. localityLbPolicy cannot be specified with haPolicy.",
+"description": "The load balancing algorithm used within the scope of the locality. The possible values are: - ROUND_ROBIN: This is a simple policy in which each healthy backend is selected in round robin order. This is the default. - LEAST_REQUEST: An O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests. - RING_HASH: The ring/modulo hash load balancer implements consistent hashing to backends. The algorithm has the property that the addition/removal of a host from a set of N hosts only affects 1/N of the requests. - RANDOM: The load balancer selects a random healthy host. - ORIGINAL_DESTINATION: Backend host is selected based on the client connection metadata, i.e., connections are opened to the same address as the destination address of the incoming connection before the connection was redirected to the load balancer. - MAGLEV: used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, see Maglev: A Fast and Reliable Software Network Load Balancer. - WEIGHTED_ROUND_ROBIN: Per-endpoint Weighted Round Robin Load Balancing using weights computed from Backend reported Custom Metrics. If set, the Backend Service responses are expected to contain non-standard HTTP response header field Endpoint-Load-Metrics. The reported metrics to use for computing the weights are specified via the customMetrics field. This field is applicable to either: - A regional backend service with the service_protocol set to HTTP, HTTPS, HTTP2 or H2C, and load_balancing_scheme set to INTERNAL_MANAGED. - A global backend service with the load_balancing_scheme set to INTERNAL_SELF_MANAGED, INTERNAL_MANAGED, or EXTERNAL_MANAGED. If sessionAffinity is not configured\u2014that is, if session affinity remains at the default value of NONE\u2014then the default value for localityLbPolicy is ROUND_ROBIN. If session affinity is set to a value other than NONE, then the default value for localityLbPolicy is MAGLEV. Only ROUND_ROBIN and RING_HASH are supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true. localityLbPolicy cannot be specified with haPolicy.",
 "enum": [
 "INVALID_LB_POLICY",
 "LEAST_REQUEST",
@@ -43290,17 +43350,19 @@ false
 "RANDOM",
 "RING_HASH",
 "ROUND_ROBIN",
+"WEIGHTED_GCP_RENDEZVOUS",
 "WEIGHTED_MAGLEV",
 "WEIGHTED_ROUND_ROBIN"
 ],
 "enumDescriptions": [
 "",
 "An O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests.",
-"This algorithm implements consistent hashing to backends. Maglev can be used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, see https://ai.google/research/pubs/pub44824",
+"This algorithm implements consistent hashing to backends. Maglev can be used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, see Maglev: A Fast and Reliable Software Network Load Balancer.",
 "Backend host is selected based on the client connection metadata, i.e., connections are opened to the same address as the destination address of the incoming connection before the connection was redirected to the load balancer.",
 "The load balancer selects a random healthy host.",
 "The ring/modulo hash load balancer implements consistent hashing to backends. The algorithm has the property that the addition/removal of a host from a set of N hosts only affects 1/N of the requests.",
 "This is a simple policy in which each healthy backend is selected in round robin order. This is the default.",
+"Per-instance weighted Load Balancing via health check reported weights. In internal passthrough network load balancing, it is weighted rendezvous hashing. This option is only supported in internal passthrough network load balancing.",
 "Per-instance weighted Load Balancing via health check reported weights. If set, the Backend Service must configure a non legacy HTTP-based Health Check, and health check replies are expected to contain non-standard HTTP response header field X-Load-Balancing-Endpoint-Weight to specify the per-instance weights. If set, Load Balancing is weighted based on the per-instance weights reported in the last processed health check replies, as long as every instance either reported a valid weight or had UNAVAILABLE_WEIGHT. Otherwise, Load Balancing remains equal-weight. This option is only supported in Network Load Balancing.",
 "Per-endpoint weighted round-robin Load Balancing using weights computed from Backend reported Custom Metrics. If set, the Backend Service responses are expected to contain non-standard HTTP response header field Endpoint-Load-Metrics. The reported metrics to use for computing the weights are specified via the customMetrics fields."
 ],
@@ -43334,6 +43396,10 @@ false
 "$ref": "OutlierDetection",
 "description": "Settings controlling the ejection of unhealthy backend endpoints from the load balancing pool of each individual proxy instance that processes the traffic for the given backend service. If not set, this feature is considered disabled. Results of the outlier detection algorithm (ejection of endpoints from the load balancing pool and returning them back to the pool) are executed independently by each proxy instance of the load balancer. In most cases, more than one proxy instance handles the traffic received by a backend service. Thus, it is possible that an unhealthy endpoint is detected and ejected by only some of the proxies, and while this happens, other proxies may continue to send requests to the same unhealthy endpoint until they detect and eject the unhealthy endpoint. Applicable backend endpoints can be: - VM instances in an Instance Group - Endpoints in a Zonal NEG (GCE_VM_IP, GCE_VM_IP_PORT) - Endpoints in a Hybrid Connectivity NEG (NON_GCP_PRIVATE_IP_PORT) - Serverless NEGs, that resolve to Cloud Run, App Engine, or Cloud Functions Services - Private Service Connect NEGs, that resolve to Google-managed regional API endpoints or managed services published using Private Service Connect Applicable backend service types can be: - A global backend service with the loadBalancingScheme set to INTERNAL_SELF_MANAGED or EXTERNAL_MANAGED. - A regional backend service with the serviceProtocol set to HTTP, HTTPS, HTTP2 or H2C, and loadBalancingScheme set to INTERNAL_MANAGED or EXTERNAL_MANAGED. Not supported for Serverless NEGs. Not supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true."
 },
+"params": {
+"$ref": "BackendServiceParams",
+"description": "Input only. [Input Only] Additional params passed with the request, but not persisted as part of resource payload."
+},
 "port": {
 "deprecated": true,
 "description": "Deprecated in favor of portName. The TCP port to connect on the backend. The default value is 80. For internal passthrough Network Load Balancers and external passthrough Network Load Balancers, omit port.",
@@ -43394,7 +43460,7 @@ false
 "type": "array"
 },
 "serviceLbPolicy": {
-"description": "URL to networkservices.ServiceLbPolicy resource. Can only be set if load balancing scheme is EXTERNAL, EXTERNAL_MANAGED, INTERNAL_MANAGED or INTERNAL_SELF_MANAGED and the scope is global.",
+"description": "URL to networkservices.ServiceLbPolicy resource. Can only be set if load balancing scheme is EXTERNAL_MANAGED, INTERNAL_MANAGED or INTERNAL_SELF_MANAGED and the scope is global.",
 "type": "string"
 },
 "sessionAffinity": {
@@ -44266,17 +44332,19 @@ false
 "RANDOM",
 "RING_HASH",
 "ROUND_ROBIN",
+"WEIGHTED_GCP_RENDEZVOUS",
 "WEIGHTED_MAGLEV",
 "WEIGHTED_ROUND_ROBIN"
 ],
 "enumDescriptions": [
 "",
 "An O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests.",
-"This algorithm implements consistent hashing to backends. Maglev can be used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, see https://ai.google/research/pubs/pub44824",
+"This algorithm implements consistent hashing to backends. Maglev can be used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, see Maglev: A Fast and Reliable Software Network Load Balancer.",
 "Backend host is selected based on the client connection metadata, i.e., connections are opened to the same address as the destination address of the incoming connection before the connection was redirected to the load balancer.",
 "The load balancer selects a random healthy host.",
 "The ring/modulo hash load balancer implements consistent hashing to backends. The algorithm has the property that the addition/removal of a host from a set of N hosts only affects 1/N of the requests.",
 "This is a simple policy in which each healthy backend is selected in round robin order. This is the default.",
+"Per-instance weighted Load Balancing via health check reported weights. In internal passthrough network load balancing, it is weighted rendezvous hashing. This option is only supported in internal passthrough network load balancing.",
 "Per-instance weighted Load Balancing via health check reported weights. If set, the Backend Service must configure a non legacy HTTP-based Health Check, and health check replies are expected to contain non-standard HTTP response header field X-Load-Balancing-Endpoint-Weight to specify the per-instance weights. If set, Load Balancing is weighted based on the per-instance weights reported in the last processed health check replies, as long as every instance either reported a valid weight or had UNAVAILABLE_WEIGHT. Otherwise, Load Balancing remains equal-weight. This option is only supported in Network Load Balancing.",
 "Per-endpoint weighted round-robin Load Balancing using weights computed from Backend reported Custom Metrics. If set, the Backend Service responses are expected to contain non-standard HTTP response header field Endpoint-Load-Metrics. The reported metrics to use for computing the weights are specified via the customMetrics fields."
 ],
@@ -44322,6 +44390,20 @@ false
 },
 "type": "object"
 },
+"BackendServiceParams": {
+"description": "Additional Backend Service parameters.",
+"id": "BackendServiceParams",
+"properties": {
+"resourceManagerTags": {
+"additionalProperties": {
+"type": "string"
+},
+"description": "Tag keys/values directly bound to this resource. Tag keys and values have the same definition as resource manager tags. The field is allowed for INSERT only. The keys/values to set on the resource should be specified in either ID { : } or Namespaced format { : }. For example the following are valid inputs: * {\"tagKeys/333\" : \"tagValues/444\", \"tagKeys/123\" : \"tagValues/456\"} * {\"123/environment\" : \"production\", \"345/abc\" : \"xyz\"} Note: * Invalid combinations of ID & namespaced format is not supported. For instance: {\"123/environment\" : \"tagValues/444\"} is invalid.",
+"type": "object"
+}
+},
+"type": "object"
+},
 "BackendServiceReference": {
 "id": "BackendServiceReference",
 "properties": {
@@ -57691,10 +57773,18 @@ false
 "description": "Represents an Interconnect resource. An Interconnect resource is a dedicated connection between the Google Cloud network and your on-premises network. For more information, read the Dedicated Interconnect Overview.",
 "id": "Interconnect",
 "properties": {
+"aaiEnabled": {
+"description": "Enable or disable the application awareness feature on this Cloud Interconnect.",
+"type": "boolean"
+},
 "adminEnabled": {
 "description": "Administrative status of the interconnect. When this is set to true, the Interconnect is functional and can carry traffic. When set to false, no packets can be carried over the interconnect and no BGP routes are exchanged over it. By default, the status is set to true.",
 "type": "boolean"
 },
+"applicationAwareInterconnect": {
+"$ref": "InterconnectApplicationAwareInterconnect",
+"description": "Configuration information for application awareness on this Cloud Interconnect."
+},
 "availableFeatures": {
 "description": "[Output only] List of features available for this Interconnect connection, which can take one of the following values: - IF_MACSEC If present then the Interconnect connection is provisioned on MACsec capable hardware ports. If not present then the Interconnect connection is provisioned on non-MACsec capable ports and MACsec isn't supported and enabling MACsec fails.",
 "items": {
@@ -57898,6 +57988,81 @@ false
 },
 "type": "object"
 },
+"InterconnectApplicationAwareInterconnect": {
+"description": "Configuration information for application awareness on this Cloud Interconnect.",
+"id": "InterconnectApplicationAwareInterconnect",
+"properties": {
+"bandwidthPercentagePolicy": {
+"$ref": "InterconnectApplicationAwareInterconnectBandwidthPercentagePolicy"
+},
+"profileDescription": {
+"description": "Description for the application awareness profile on this Cloud Interconnect.",
+"type": "string"
+},
+"shapeAveragePercentages": {
+"description": "Optional field to specify a list of shape average percentages to be applied in conjunction with StrictPriorityPolicy or BandwidthPercentagePolicy.",
+"items": {
+"$ref": "InterconnectApplicationAwareInterconnectBandwidthPercentage"
+},
+"type": "array"
+},
+"strictPriorityPolicy": {
+"$ref": "InterconnectApplicationAwareInterconnectStrictPriorityPolicy"
+}
+},
+"type": "object"
+},
+"InterconnectApplicationAwareInterconnectBandwidthPercentage": {
+"description": "Specify bandwidth percentages [1-100] for various traffic classes in BandwidthPercentagePolicy. The sum of all percentages must equal 100. All traffic classes must have a percentage value specified.",
+"id": "InterconnectApplicationAwareInterconnectBandwidthPercentage",
+"properties": {
+"percentage": {
+"description": "Bandwidth percentage for a specific traffic class.",
+"format": "uint32",
+"type": "integer"
+},
+"trafficClass": {
+"description": "TrafficClass whose bandwidth percentage is being specified.",
+"enum": [
+"TC1",
+"TC2",
+"TC3",
+"TC4",
+"TC5",
+"TC6"
+],
+"enumDescriptions": [
+"Traffic Class 1, corresponding to DSCP ranges (0-7) 000xxx.",
+"Traffic Class 2, corresponding to DSCP ranges (8-15) 001xxx.",
+"Traffic Class 3, corresponding to DSCP ranges (16-23) 010xxx.",
+"Traffic Class 4, corresponding to DSCP ranges (24-31) 011xxx.",
+"Traffic Class 5, corresponding to DSCP ranges (32-47) 10xxxx.",
+"Traffic Class 6, corresponding to DSCP ranges (48-63) 11xxxx."
+],
+"type": "string"
+}
+},
+"type": "object"
+},
+"InterconnectApplicationAwareInterconnectBandwidthPercentagePolicy": {
+"id": "InterconnectApplicationAwareInterconnectBandwidthPercentagePolicy",
+"properties": {
+"bandwidthPercentages": {
+"description": "Specify bandwidth percentages for various traffic classes for queuing type Bandwidth Percent.",
+"items": {
+"$ref": "InterconnectApplicationAwareInterconnectBandwidthPercentage"
+},
+"type": "array"
+}
+},
+"type": "object"
+},
+"InterconnectApplicationAwareInterconnectStrictPriorityPolicy": {
+"description": "Specify configuration for StrictPriorityPolicy.",
+"id": "InterconnectApplicationAwareInterconnectStrictPriorityPolicy",
+"properties": {},
+"type": "object"
+},
 "InterconnectAttachment": {
 "description": "Represents an Interconnect Attachment (VLAN) resource. You can use Interconnect attachments (VLANS) to connect your Virtual Private Cloud networks to your on-premises networks through an Interconnect. For more information, read Creating VLAN Attachments.",
 "id": "InterconnectAttachment",
@@ -65207,6 +65372,10 @@ false
 "description": "This field will be deprecated soon. Use the exchange_subnet_routes field instead. Indicates whether full mesh connectivity is created and managed automatically between peered networks. Currently this field should always be true since Google Compute Engine will automatically create and manage subnetwork routes between two networks when peering state is ACTIVE.",
 "type": "boolean"
 },
+"connectionStatus": {
+"$ref": "NetworkPeeringConnectionStatus",
+"description": "[Output Only] The effective state of the peering connection as a whole."
+},
 "exchangeSubnetRoutes": {
 "description": "Indicates whether full mesh connectivity is created and managed automatically between peered networks. Currently this field should always be true since Google Compute Engine will automatically create and manage subnetwork routes between two networks when peering state is ACTIVE.",
 "type": "boolean"
@@ -65267,6 +65436,122 @@ false
 "stateDetails": {
 "description": "[Output Only] Details about the current state of the peering.",
 "type": "string"
+},
+"updateStrategy": {
+"description": "The update strategy determines the semantics for updates and deletes to the peering connection configuration.",
+"enum": [
+"CONSENSUS",
+"INDEPENDENT",
+"UNSPECIFIED"
+],
+"enumDescriptions": [
+"Updates are reflected in the local peering but aren't applied to the peering connection until a complementary change is made to the matching peering. To delete a peering with the consensus update strategy, both the peerings must request the deletion of the peering before the peering can be deleted.",
+"In this mode, changes to the peering configuration can be unilaterally altered by changing either side of the peering. This is the default value if the field is unspecified.",
+"Peerings with update strategy UNSPECIFIED are created with update strategy INDEPENDENT."
+],
+"type": "string"
+}
+},
+"type": "object"
+},
+"NetworkPeeringConnectionStatus": {
+"description": "[Output Only] Describes the state of a peering connection, not just the local peering. This field provides information about the effective settings for the connection as a whole, including pending delete/update requests for CONSENSUS peerings.",
+"id": "NetworkPeeringConnectionStatus",
+"properties": {
+"consensusState": {
+"$ref": "NetworkPeeringConnectionStatusConsensusState",
+"description": "The consensus state contains information about the status of update and delete for a consensus peering connection."
+},
+"trafficConfiguration": {
+"$ref": "NetworkPeeringConnectionStatusTrafficConfiguration",
+"description": "The active connectivity settings for the peering connection based on the settings of the network peerings."
+},
+"updateStrategy": {
+"description": "The update strategy determines the update/delete semantics for this peering connection.",
+"enum": [
+"CONSENSUS",
+"INDEPENDENT",
+"UNSPECIFIED"
+],
+"enumDescriptions": [
+"Updates are reflected in the local peering but aren't applied to the peering connection until a complementary change is made to the matching peering. To delete a peering with the consensus update strategy, both the peerings must request the deletion of the peering before the peering can be deleted.",
+"In this mode, changes to the peering configuration can be unilaterally altered by changing either side of the peering. This is the default value if the field is unspecified.",
+"Peerings with update strategy UNSPECIFIED are created with update strategy INDEPENDENT."
+],
+"type": "string"
+}
+},
+"type": "object"
+},
+"NetworkPeeringConnectionStatusConsensusState": {
+"description": "The status of update/delete for a consensus peering connection. Only set when connection_status.update_strategy is CONSENSUS or a network peering is proposing to update the strategy to CONSENSUS.",
+"id": "NetworkPeeringConnectionStatusConsensusState",
+"properties": {
+"deleteStatus": {
+"description": "The status of the delete request.",
+"enum": [
+"DELETE_ACKNOWLEDGED",
+"DELETE_STATUS_UNSPECIFIED",
+"LOCAL_DELETE_REQUESTED",
+"PEER_DELETE_REQUESTED"
+],
+"enumDescriptions": [
+"Both network admins have agreed this consensus peering connection can be deleted.",
+"",
+"Network admin has requested deletion of this peering connection.",
+"The peer network admin has requested deletion of this peering connection."
+],
+"type": "string"
+},
+"updateStatus": {
+"description": "The status of the update request.",
+"enum": [
+"IN_SYNC",
+"PENDING_LOCAL_ACKNOWLEDMENT",
+"PENDING_PEER_ACKNOWLEDGEMENT",
+"UPDATE_STATUS_UNSPECIFIED"
+],
+"enumDescriptions": [
+"No pending configuration update proposals to the peering connection.",
+"The peer network admin has made an updatePeering call. The change is awaiting acknowledgment from this peering's network admin.",
+"The local network admin has made an updatePeering call. The change is awaiting acknowledgment from the peer network admin.",
+""
+],
+"type": "string"
+}
+},
+"type": "object"
+},
+"NetworkPeeringConnectionStatusTrafficConfiguration": {
+"id": "NetworkPeeringConnectionStatusTrafficConfiguration",
+"properties": {
+"exportCustomRoutesToPeer": {
+"description": "Whether custom routes are being exported to the peer network.",
+"type": "boolean"
+},
+"exportSubnetRoutesWithPublicIpToPeer": {
+"description": "Whether subnet routes with public IP ranges are being exported to the peer network.",
+"type": "boolean"
+},
+"importCustomRoutesFromPeer": {
+"description": "Whether custom routes are being imported from the peer network.",
+"type": "boolean"
+},
+"importSubnetRoutesWithPublicIpFromPeer": {
+"description": "Whether subnet routes with public IP ranges are being imported from the peer network.",
+"type": "boolean"
+},
+"stackType": {
+"description": "Which IP version(s) of traffic and routes are being imported or exported between peer networks.",
+"enum": [
+"IPV4_IPV6",
+"IPV4_ONLY"
+],
+"enumDescriptions": [
+"This Peering will allow IPv4 traffic and routes to be exchanged. Additionally if the matching peering is IPV4_IPV6, IPv6 traffic and routes will be exchanged as well.",
+"This Peering will only allow IPv4 traffic and routes to be exchanged, even if the matching peering is IPV4_IPV6."
+],
+"type": "string"
 }
 },
 "type": "object"
@@ -66089,6 +66374,16 @@ false
 },
 "type": "object"
 },
+"NetworksRequestRemovePeeringRequest": {
+"id": "NetworksRequestRemovePeeringRequest",
+"properties": {
+"name": {
+"description": "Name of the peering, which should conform to RFC1035.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "NetworksUpdatePeeringRequest": {
 "id": "NetworksUpdatePeeringRequest",
 "properties": {
@@ -73497,6 +73792,10 @@ false
 "description": "Represents a reservation resource. A reservation ensures that capacity is held in a specific zone even if the reserved VMs are not running. For more information, read Reserving zonal resources.",
 "id": "Reservation",
 "properties": {
+"advancedDeploymentControl": {
+"$ref": "ReservationAdvancedDeploymentControl",
+"description": "Advanced control for cluster management, applicable only to DENSE deployment type reservations."
+},
 "aggregateReservation": {
 "$ref": "AllocationAggregateReservation",
 "description": "Reservation for aggregated resources, providing shape flexibility."
@@ -73638,6 +73937,27 @@ false
 },
 "type": "object"
 },
+"ReservationAdvancedDeploymentControl": {
+"description": "Advance control for cluster management, applicable only to DENSE deployment type reservations.",
+"id": "ReservationAdvancedDeploymentControl",
+"properties": {
+"reservationOperationalMode": {
+"description": "Indicates chosen reservation operational mode for the reservation.",
+"enum": [
+"ALL_CAPACITY",
+"HIGHLY_AVAILABLE_CAPACITY",
+"RESERVATION_OPERATIONAL_MODE_UNSPECIFIED"
+],
+"enumDescriptions": [
+"Google Cloud does not manage the failure of machines, but provides additional capacity, which is not guaranteed to be available.",
+"Google Cloud manages the failure of machines to provide high availability.",
+""
+],
+"type": "string"
+}
+},
+"type": "object"
+},
 "ReservationAffinity": {
 "description": "Specifies the reservations that this instance can consume from.",
 "id": "ReservationAffinity",
@@ -75074,7 +75394,8 @@ false
 "type": "string"
 },
 "workloadPolicy": {
-"$ref": "ResourcePolicyWorkloadPolicy"
+"$ref": "ResourcePolicyWorkloadPolicy",
+"description": "Resource policy for defining instance placement for MIGs."
 }
 },
 "type": "object"
@@ -75691,9 +76012,11 @@ false
 "id": "ResourcePolicyWorkloadPolicy",
 "properties": {
 "acceleratorTopology": {
+"description": "Specifies the topology required to create a partition for VMs that have interconnected GPUs.",
 "type": "string"
 },
 "maxTopologyDistance": {
+"description": "Specifies the maximum distance between instances.",
 "enum": [
 "BLOCK",
 "CLUSTER",
@@ -75707,13 +76030,14 @@ false
 "type": "string"
 },
 "type": {
+"description": "Specifies the intent of the instance placement in the MIG.",
 "enum": [
 "HIGH_AVAILABILITY",
 "HIGH_THROUGHPUT"
 ],
 "enumDescriptions": [
-"VMs will be provisioned in such a way which provides high availability.",
-"VMs will be provisioned in such a way which provides high throughput."
+"MIG spreads out the instances as much as possible for high availability.",
+"MIG provisions instances as close to each other as possible for high throughput."
 ],
 "type": "string"
 }
@@ -75724,6 +76048,10 @@ false
 "description": "Contains output only fields. Use this sub-message for actual values set on Instance attributes as compared to the value requested by the user (intent) in their instance CRUD calls.",
 "id": "ResourceStatus",
 "properties": {
+"effectiveInstanceMetadata": {
+"$ref": "ResourceStatusEffectiveInstanceMetadata",
+"description": "[Output Only] Effective metadata is a field that consolidates project, zonal instance settings, and instance-level predefined metadata keys to provide the overridden value for those metadata keys at the instance level."
+},
 "physicalHost": {
 "description": "[Output Only] The precise location of your instance within the zone's data center, including the block, sub-block, and host. The field is formatted as follows: blockId/subBlockId/hostId.",
 "type": "string"
@@ -75741,6 +76069,45 @@ false
 },
 "type": "object"
 },
+"ResourceStatusEffectiveInstanceMetadata": {
+"description": "Effective values of predefined metadata keys for an instance.",
+"id": "ResourceStatusEffectiveInstanceMetadata",
+"properties": {
+"blockProjectSshKeysMetadataValue": {
+"description": "Effective block-project-ssh-keys value at Instance level.",
+"type": "boolean"
+},
+"enableGuestAttributesMetadataValue": {
+"description": "Effective enable-guest-attributes value at Instance level.",
+"type": "boolean"
+},
+"enableOsInventoryMetadataValue": {
+"description": "Effective enable-os-inventory value at Instance level.",
+"type": "boolean"
+},
+"enableOsconfigMetadataValue": {
+"description": "Effective enable-osconfig value at Instance level.",
+"type": "boolean"
+},
+"enableOsloginMetadataValue": {
+"description": "Effective enable-oslogin value at Instance level.",
+"type": "boolean"
+},
+"serialPortEnableMetadataValue": {
+"description": "Effective serial-port-enable value at Instance level.",
+"type": "boolean"
+},
+"serialPortLoggingEnableMetadataValue": {
+"description": "Effective serial-port-logging-enable value at Instance level.",
+"type": "boolean"
+},
+"vmDnsSettingMetadataValue": {
+"description": "Effective VM DNS setting at Instance level.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "ResourceStatusPhysicalHostTopology": {
 "description": "Represents the physical host topology of the host on which the VM is running.",
 "id": "ResourceStatusPhysicalHostTopology",
@@ -78937,7 +79304,7 @@ false
 "type": "string"
 },
 "type": {
-"description": "The type indicates the intended use of the security policy. - CLOUD_ARMOR: Cloud Armor backend security policies can be configured to filter incoming HTTP requests targeting backend services. They filter requests before they hit the origin servers. - CLOUD_ARMOR_EDGE: Cloud Armor edge security policies can be configured to filter incoming HTTP requests targeting backend services (including Cloud CDN-enabled) as well as backend buckets (Cloud Storage). They filter requests before the request is served from Google's cache. - CLOUD_ARMOR_INTERNAL_SERVICE: Cloud Armor internal service policies can be configured to filter HTTP requests targeting services managed by Traffic Director in a service mesh. They filter requests before the request is served from the application. - CLOUD_ARMOR_NETWORK: Cloud Armor network policies can be configured to filter packets targeting network load balancing resources such as backend services, target pools, target instances, and instances with external IPs. They filter requests before the request is served from the application. This field can be set only at resource creation time.",
+"description": "The type indicates the intended use of the security policy. - CLOUD_ARMOR: Cloud Armor backend security policies can be configured to filter incoming HTTP requests targeting backend services. They filter requests before they hit the origin servers. - CLOUD_ARMOR_EDGE: Cloud Armor edge security policies can be configured to filter incoming HTTP requests targeting backend services (including Cloud CDN-enabled) as well as backend buckets (Cloud Storage). They filter requests before the request is served from Google's cache. - CLOUD_ARMOR_INTERNAL_SERVICE (preview only): Cloud Armor internal service policies can be configured to filter HTTP requests targeting services managed by Traffic Director in a service mesh. They filter requests before the request is served from the application. - CLOUD_ARMOR_NETWORK: Cloud Armor network policies can be configured to filter packets targeting network load balancing resources such as backend services, target pools, target instances, and instances with external IPs. They filter requests before the request is served from the application. This field can be set only at resource creation time.",
 "enum": [
 "CLOUD_ARMOR",
 "CLOUD_ARMOR_EDGE",
@@ -79323,7 +79690,7 @@ false
 "id": "SecurityPolicyRule",
 "properties": {
 "action": {
-"description": "The Action to perform when the rule is matched. The following are the valid actions: - allow: allow access to target. - deny(STATUS): deny access to target, returns the HTTP response code specified. Valid values for `STATUS` are 403, 404, and 502. - rate_based_ban: limit client traffic to the configured threshold and ban the client if the traffic exceeds the threshold. Configure parameters for this action in RateLimitOptions. Requires rate_limit_options to be set. - redirect: redirect to a different target. This can either be an internal reCAPTCHA redirect, or an external URL-based redirect via a 302 response. Parameters for this action can be configured via redirectOptions. This action is only supported in Global Security Policies of type CLOUD_ARMOR. - throttle: limit client traffic to the configured threshold. Configure parameters for this action in rateLimitOptions. Requires rate_limit_options to be set for this. ",
+"description": "The Action to perform when the rule is matched. The following are the valid actions: - allow: allow access to target. - deny(STATUS): deny access to target, returns the HTTP response code specified. Valid values for `STATUS` are 403, 404, and 502. - rate_based_ban: limit client traffic to the configured threshold and ban the client if the traffic exceeds the threshold. Configure parameters for this action in RateLimitOptions. Requires rate_limit_options to be set. - redirect: redirect to a different target. This can either be an internal reCAPTCHA redirect, or an external URL-based redirect via a 302 response. Parameters for this action can be configured via redirectOptions. This action is only supported in Global Security Policies of type CLOUD_ARMOR. - throttle: limit client traffic to the configured threshold. Configure parameters for this action in rateLimitOptions. Requires rate_limit_options to be set for this. - fairshare (preview only): when traffic reaches the threshold limit, requests from the clients matching this rule begin to be rate-limited using the Fair Share algorithm. This action is only allowed in security policies of type `CLOUD_ARMOR_INTERNAL_SERVICE`. ",
 "type": "string"
 },
 "description": {
@@ -79362,7 +79729,7 @@ false
 },
 "rateLimitOptions": {
 "$ref": "SecurityPolicyRuleRateLimitOptions",
-"description": "Must be specified if the action is \"rate_based_ban\" or \"throttle\". Cannot be specified for any other actions."
+"description": "Must be specified if the action is \"rate_based_ban\" or \"throttle\" or \"fairshare\". Cannot be specified for any other actions."
 },
 "redirectOptions": {
 "$ref": "SecurityPolicyRuleRedirectOptions",
@@ -79654,7 +80021,7 @@ false
 "type": "string"
 },
 "enforceOnKey": {
-"description": "Determines the key to enforce the rate_limit_threshold on. Possible values are: - ALL: A single rate limit threshold is applied to all the requests matching this rule. This is the default value if \"enforceOnKey\" is not configured. - IP: The source IP address of the request is the key. Each IP has this limit enforced separately. - HTTP_HEADER: The value of the HTTP header whose name is configured under \"enforceOnKeyName\". The key value is truncated to the first 128 bytes of the header value. If no such header is present in the request, the key type defaults to ALL. - XFF_IP: The first IP address (i.e. the originating client IP address) specified in the list of IPs under X-Forwarded-For HTTP header. If no such header is present or the value is not a valid IP, the key defaults to the source IP address of the request i.e. key type IP. - HTTP_COOKIE: The value of the HTTP cookie whose name is configured under \"enforceOnKeyName\". The key value is truncated to the first 128 bytes of the cookie value. If no such cookie is present in the request, the key type defaults to ALL. - HTTP_PATH: The URL path of the HTTP request. The key value is truncated to the first 128 bytes. - SNI: Server name indication in the TLS session of the HTTPS request. The key value is truncated to the first 128 bytes. The key type defaults to ALL on a HTTP session. - REGION_CODE: The country/region from which the request originates. - TLS_JA3_FINGERPRINT: JA3 TLS/SSL fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3. If not available, the key type defaults to ALL. - USER_IP: The IP address of the originating client, which is resolved based on \"userIpRequestHeaders\" configured with the security policy. If there is no \"userIpRequestHeaders\" configuration or an IP address cannot be resolved from it, the key type defaults to IP. - TLS_JA4_FINGERPRINT: JA4 TLS/SSL fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3. If not available, the key type defaults to ALL. ",
+"description": "Determines the key to enforce the rate_limit_threshold on. Possible values are: - ALL: A single rate limit threshold is applied to all the requests matching this rule. This is the default value if \"enforceOnKey\" is not configured. - IP: The source IP address of the request is the key. Each IP has this limit enforced separately. - HTTP_HEADER: The value of the HTTP header whose name is configured under \"enforceOnKeyName\". The key value is truncated to the first 128 bytes of the header value. If no such header is present in the request, the key type defaults to ALL. - XFF_IP: The first IP address (i.e. the originating client IP address) specified in the list of IPs under X-Forwarded-For HTTP header. If no such header is present or the value is not a valid IP, the key defaults to the source IP address of the request i.e. key type IP. - HTTP_COOKIE: The value of the HTTP cookie whose name is configured under \"enforceOnKeyName\". The key value is truncated to the first 128 bytes of the cookie value. If no such cookie is present in the request, the key type defaults to ALL. - HTTP_PATH: The URL path of the HTTP request. The key value is truncated to the first 128 bytes. - SNI: Server name indication in the TLS session of the HTTPS request. The key value is truncated to the first 128 bytes. The key type defaults to ALL on a HTTP session. - REGION_CODE: The country/region from which the request originates. - TLS_JA3_FINGERPRINT: JA3 TLS/SSL fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3. If not available, the key type defaults to ALL. - USER_IP: The IP address of the originating client, which is resolved based on \"userIpRequestHeaders\" configured with the security policy. If there is no \"userIpRequestHeaders\" configuration or an IP address cannot be resolved from it, the key type defaults to IP. - TLS_JA4_FINGERPRINT: JA4 TLS/SSL fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3. If not available, the key type defaults to ALL. For \"fairshare\" action, this value is limited to ALL i.e. a single rate limit threshold is enforced for all the requests matching the rule.",
 "enum": [
 "ALL",
 "HTTP_COOKIE",
@@ -85890,7 +86257,7 @@ false
 "type": "object"
 },
 "TargetHttpsProxy": {
-"description": "Represents a Target HTTPS Proxy resource. Google Compute Engine has two Target HTTPS Proxy resources: * [Global](/compute/docs/reference/rest/v1/targetHttpsProxies) * [Regional](/compute/docs/reference/rest/v1/regionTargetHttpsProxies) A target HTTPS proxy is a component of Google Cloud HTTPS load balancers. * targetHttpProxies are used by global external Application Load Balancers, classic Application Load Balancers, cross-region internal Application Load Balancers, and Traffic Director. * regionTargetHttpProxies are used by regional internal Application Load Balancers and regional external Application Load Balancers. Forwarding rules reference a target HTTPS proxy, and the target proxy then references a URL map. For more information, read Using Target Proxies and Forwarding rule concepts.",
+"description": "Represents a Target HTTPS Proxy resource. Google Compute Engine has two Target HTTPS Proxy resources: * [Global](/compute/docs/reference/rest/v1/targetHttpsProxies) * [Regional](/compute/docs/reference/rest/v1/regionTargetHttpsProxies) A target HTTPS proxy is a component of Google Cloud HTTPS load balancers. * targetHttpsProxies are used by global external Application Load Balancers, classic Application Load Balancers, cross-region internal Application Load Balancers, and Traffic Director. * regionTargetHttpsProxies are used by regional internal Application Load Balancers and regional external Application Load Balancers. Forwarding rules reference a target HTTPS proxy, and the target proxy then references a URL map. For more information, read Using Target Proxies and Forwarding rule concepts.",
 "id": "TargetHttpsProxy",
 "properties": {
 "authorizationPolicy": {
@@ -88927,6 +89294,7 @@ false
 "FAILURE_MEMORY",
 "FAILURE_NETWORK",
 "FAILURE_NVLINK",
+"FAILURE_REDUNDANT_HARDWARE_FAULT",
 "INFRASTRUCTURE_RELOCATION",
 "MAINTENANCE_REASON_UNKNOWN",
 "PLANNED_NETWORK_UPDATE",
@@ -88942,6 +89310,7 @@ false
 "Maintenance due to memory errors.",
 "Maintenance due to network errors.",
 "Maintenance due to NVLink failure.",
+"Maintenance due to redundant hardware fault.",
 "Maintenance due to infrastructure relocation.",
 "Unknown maintenance reason. Do not use this value.",
 "Maintenance due to planned network update.",