feat(networkmanagement): update the api

#### networkmanagement:v1 The following keys were added: - schemas.ConnectivityTest.properties.bypassFirewallChecks.type (Total Keys: 1) #### networkmanagement:v1beta1 The following keys were added: - schemas.ConnectivityTest.properties.bypassFirewallChecks.type (Total Keys: 1)
googleapis · Mar 19, 2024 · 4df586d · 4df586d
1 parent 4f1084b
commit 4df586d
Show file tree

Hide file tree

Showing 4 changed files with 46 additions and 10 deletions.
diff --git a/docs/dyn/networkmanagement_v1.projects.locations.global_.connectivityTests.html b/docs/dyn/networkmanagement_v1.projects.locations.global_.connectivityTests.html
@@ -123,6 +123,7 @@ <h3>Method Details</h3>
     The object takes the form of:
 
 { # A Connectivity Test for a network reachability analysis.
+  &quot;bypassFirewallChecks&quot;: True or False, # Whether the test should skip firewall checking. If not provided, we assume false.
   &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time the test was created.
   &quot;description&quot;: &quot;A String&quot;, # The user-supplied description of the Connectivity Test. Maximum of 512 characters.
   &quot;destination&quot;: { # Source or destination of the Connectivity Test. # Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, Compute Engine VM instance, or VPC network to uniquely identify the destination location. Even if the destination IP address is not unique, the source IP location is unique. Usually, the analysis can infer the destination endpoint from route information. If the destination you specify is a VM instance and the instance has multiple network interfaces, then you must also specify either a destination IP address or VPC network to identify the destination interface. A reachability analysis proceeds even if the destination location is ambiguous. However, the result can include endpoints that you don&#x27;t intend to test.
@@ -561,6 +562,7 @@ <h3>Method Details</h3>
   An object of the form:
 
     { # A Connectivity Test for a network reachability analysis.
+  &quot;bypassFirewallChecks&quot;: True or False, # Whether the test should skip firewall checking. If not provided, we assume false.
   &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time the test was created.
   &quot;description&quot;: &quot;A String&quot;, # The user-supplied description of the Connectivity Test. Maximum of 512 characters.
   &quot;destination&quot;: { # Source or destination of the Connectivity Test. # Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, Compute Engine VM instance, or VPC network to uniquely identify the destination location. Even if the destination IP address is not unique, the source IP location is unique. Usually, the analysis can infer the destination endpoint from route information. If the destination you specify is a VM instance and the instance has multiple network interfaces, then you must also specify either a destination IP address or VPC network to identify the destination interface. A reachability analysis proceeds even if the destination location is ambiguous. However, the result can include endpoints that you don&#x27;t intend to test.
@@ -990,6 +992,7 @@ <h3>Method Details</h3>
   &quot;nextPageToken&quot;: &quot;A String&quot;, # Page token to fetch the next set of Connectivity Tests.
   &quot;resources&quot;: [ # List of Connectivity Tests.
     { # A Connectivity Test for a network reachability analysis.
+      &quot;bypassFirewallChecks&quot;: True or False, # Whether the test should skip firewall checking. If not provided, we assume false.
       &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time the test was created.
       &quot;description&quot;: &quot;A String&quot;, # The user-supplied description of the Connectivity Test. Maximum of 512 characters.
       &quot;destination&quot;: { # Source or destination of the Connectivity Test. # Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, Compute Engine VM instance, or VPC network to uniquely identify the destination location. Even if the destination IP address is not unique, the source IP location is unique. Usually, the analysis can infer the destination endpoint from route information. If the destination you specify is a VM instance and the instance has multiple network interfaces, then you must also specify either a destination IP address or VPC network to identify the destination interface. A reachability analysis proceeds even if the destination location is ambiguous. However, the result can include endpoints that you don&#x27;t intend to test.
@@ -1378,6 +1381,7 @@ <h3>Method Details</h3>
     The object takes the form of:
 
 { # A Connectivity Test for a network reachability analysis.
+  &quot;bypassFirewallChecks&quot;: True or False, # Whether the test should skip firewall checking. If not provided, we assume false.
   &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time the test was created.
   &quot;description&quot;: &quot;A String&quot;, # The user-supplied description of the Connectivity Test. Maximum of 512 characters.
   &quot;destination&quot;: { # Source or destination of the Connectivity Test. # Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, Compute Engine VM instance, or VPC network to uniquely identify the destination location. Even if the destination IP address is not unique, the source IP location is unique. Usually, the analysis can infer the destination endpoint from route information. If the destination you specify is a VM instance and the instance has multiple network interfaces, then you must also specify either a destination IP address or VPC network to identify the destination interface. A reachability analysis proceeds even if the destination location is ambiguous. However, the result can include endpoints that you don&#x27;t intend to test.

diff --git a/docs/dyn/networkmanagement_v1beta1.projects.locations.global_.connectivityTests.html b/docs/dyn/networkmanagement_v1beta1.projects.locations.global_.connectivityTests.html
@@ -123,6 +123,7 @@ <h3>Method Details</h3>
     The object takes the form of:
 
 { # A Connectivity Test for a network reachability analysis.
+  &quot;bypassFirewallChecks&quot;: True or False, # Whether the test should skip firewall checking. If not provided, we assume false.
   &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time the test was created.
   &quot;description&quot;: &quot;A String&quot;, # The user-supplied description of the Connectivity Test. Maximum of 512 characters.
   &quot;destination&quot;: { # Source or destination of the Connectivity Test. # Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, Compute Engine VM instance, or VPC network to uniquely identify the destination location. Even if the destination IP address is not unique, the source IP location is unique. Usually, the analysis can infer the destination endpoint from route information. If the destination you specify is a VM instance and the instance has multiple network interfaces, then you must also specify either a destination IP address or VPC network to identify the destination interface. A reachability analysis proceeds even if the destination location is ambiguous. However, the result can include endpoints that you don&#x27;t intend to test.
@@ -562,6 +563,7 @@ <h3>Method Details</h3>
   An object of the form:
 
     { # A Connectivity Test for a network reachability analysis.
+  &quot;bypassFirewallChecks&quot;: True or False, # Whether the test should skip firewall checking. If not provided, we assume false.
   &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time the test was created.
   &quot;description&quot;: &quot;A String&quot;, # The user-supplied description of the Connectivity Test. Maximum of 512 characters.
   &quot;destination&quot;: { # Source or destination of the Connectivity Test. # Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, Compute Engine VM instance, or VPC network to uniquely identify the destination location. Even if the destination IP address is not unique, the source IP location is unique. Usually, the analysis can infer the destination endpoint from route information. If the destination you specify is a VM instance and the instance has multiple network interfaces, then you must also specify either a destination IP address or VPC network to identify the destination interface. A reachability analysis proceeds even if the destination location is ambiguous. However, the result can include endpoints that you don&#x27;t intend to test.
@@ -992,6 +994,7 @@ <h3>Method Details</h3>
   &quot;nextPageToken&quot;: &quot;A String&quot;, # Page token to fetch the next set of Connectivity Tests.
   &quot;resources&quot;: [ # List of Connectivity Tests.
     { # A Connectivity Test for a network reachability analysis.
+      &quot;bypassFirewallChecks&quot;: True or False, # Whether the test should skip firewall checking. If not provided, we assume false.
       &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time the test was created.
       &quot;description&quot;: &quot;A String&quot;, # The user-supplied description of the Connectivity Test. Maximum of 512 characters.
       &quot;destination&quot;: { # Source or destination of the Connectivity Test. # Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, Compute Engine VM instance, or VPC network to uniquely identify the destination location. Even if the destination IP address is not unique, the source IP location is unique. Usually, the analysis can infer the destination endpoint from route information. If the destination you specify is a VM instance and the instance has multiple network interfaces, then you must also specify either a destination IP address or VPC network to identify the destination interface. A reachability analysis proceeds even if the destination location is ambiguous. However, the result can include endpoints that you don&#x27;t intend to test.
@@ -1381,6 +1384,7 @@ <h3>Method Details</h3>
     The object takes the form of:
 
 { # A Connectivity Test for a network reachability analysis.
+  &quot;bypassFirewallChecks&quot;: True or False, # Whether the test should skip firewall checking. If not provided, we assume false.
   &quot;createTime&quot;: &quot;A String&quot;, # Output only. The time the test was created.
   &quot;description&quot;: &quot;A String&quot;, # The user-supplied description of the Connectivity Test. Maximum of 512 characters.
   &quot;destination&quot;: { # Source or destination of the Connectivity Test. # Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, Compute Engine VM instance, or VPC network to uniquely identify the destination location. Even if the destination IP address is not unique, the source IP location is unique. Usually, the analysis can infer the destination endpoint from route information. If the destination you specify is a VM instance and the instance has multiple network interfaces, then you must also specify either a destination IP address or VPC network to identify the destination interface. A reachability analysis proceeds even if the destination location is ambiguous. However, the result can include endpoints that you don&#x27;t intend to test.

diff --git a/googleapiclient/discovery_cache/documents/networkmanagement.v1.json b/googleapiclient/discovery_cache/documents/networkmanagement.v1.json
@@ -591,7 +591,7 @@
 }
 }
 },
-"revision": "20240228",
+"revision": "20240306",
 "rootUrl": "https://networkmanagement.googleapis.com/",
 "schemas": {
 "AbortInfo": {
@@ -630,7 +630,9 @@
 "GOOGLE_MANAGED_SERVICE_AMBIGUOUS_PSC_ENDPOINT",
 "SOURCE_PSC_CLOUD_SQL_UNSUPPORTED",
 "SOURCE_FORWARDING_RULE_UNSUPPORTED",
-"NON_ROUTABLE_IP_ADDRESS"
+"NON_ROUTABLE_IP_ADDRESS",
+"UNKNOWN_ISSUE_IN_GOOGLE_MANAGED_PROJECT",
+"UNSUPPORTED_GOOGLE_MANAGED_PROJECT_CONFIG"
 ],
 "enumDeprecated": [
 false,
@@ -662,6 +664,8 @@ false,
 false,
 false,
 false,
+false,
+false,
 false
 ],
 "enumDescriptions": [
@@ -694,7 +698,9 @@ false
 "Aborted because a PSC endpoint selection for the Google-managed service is ambiguous (several PSC endpoints satisfy test input).",
 "Aborted because tests with a PSC-based Cloud SQL instance as a source are not supported.",
 "Aborted because tests with a forwarding rule as a source are not supported.",
-"Aborted because one of the endpoints is a non-routable IP address (loopback, link-local, etc)."
+"Aborted because one of the endpoints is a non-routable IP address (loopback, link-local, etc).",
+"Aborted due to an unknown issue in the Google-managed project.",
+"Aborted due to an unsupported configuration of the Google-managed project."
 ],
 "type": "string"
 },
@@ -930,6 +936,10 @@ false
 "description": "A Connectivity Test for a network reachability analysis.",
 "id": "ConnectivityTest",
 "properties": {
+"bypassFirewallChecks": {
+"description": "Whether the test should skip firewall checking. If not provided, we assume false.",
+"type": "boolean"
+},
 "createTime": {
 "description": "Output only. The time the test was created.",
 "format": "google-datetime",
@@ -1105,13 +1115,15 @@ false
 "PSC_ENDPOINT_ACCESSED_FROM_PEERED_NETWORK",
 "PSC_NEG_PRODUCER_ENDPOINT_NO_GLOBAL_ACCESS",
 "PSC_NEG_PRODUCER_FORWARDING_RULE_MULTIPLE_PORTS",
+"CLOUD_SQL_PSC_NEG_UNSUPPORTED",
 "NO_NAT_SUBNETS_FOR_PSC_SERVICE_ATTACHMENT",
 "HYBRID_NEG_NON_DYNAMIC_ROUTE_MATCHED",
 "HYBRID_NEG_NON_LOCAL_DYNAMIC_ROUTE_MATCHED",
 "CLOUD_RUN_REVISION_NOT_READY",
 "DROPPED_INSIDE_PSC_SERVICE_PRODUCER",
 "LOAD_BALANCER_HAS_NO_PROXY_SUBNET",
-"CLOUD_NAT_NO_ADDRESSES"
+"CLOUD_NAT_NO_ADDRESSES",
+"ROUTING_LOOP"
 ],
 "enumDescriptions": [
 "Cause is unspecified.",
@@ -1165,13 +1177,15 @@ false
 "The packet is sent to the Private Service Connect endpoint over the peering, but [it's not supported](https://cloud.google.com/vpc/docs/configure-private-service-connect-services#on-premises).",
 "The packet is sent to the Private Service Connect backend (network endpoint group), but the producer PSC forwarding rule does not have global access enabled.",
 "The packet is sent to the Private Service Connect backend (network endpoint group), but the producer PSC forwarding rule has multiple ports specified.",
+"The packet is sent to the Private Service Connect backend (network endpoint group) targeting a Cloud SQL service attachment, but this configuration is not supported.",
 "No NAT subnets are defined for the PSC service attachment.",
 "The packet sent from the hybrid NEG proxy matches a non-dynamic route, but such a configuration is not supported.",
 "The packet sent from the hybrid NEG proxy matches a dynamic route with a next hop in a different region, but such a configuration is not supported.",
 "Packet sent from a Cloud Run revision that is not ready.",
 "Packet was dropped inside Private Service Connect service producer.",
 "Packet sent to a load balancer, which requires a proxy-only subnet and the subnet is not found.",
-"Packet sent to Cloud Nat without active NAT IPs."
+"Packet sent to Cloud Nat without active NAT IPs.",
+"Packet is stuck in a routing loop."
 ],
 "type": "string"
 },

diff --git a/googleapiclient/discovery_cache/documents/networkmanagement.v1beta1.json b/googleapiclient/discovery_cache/documents/networkmanagement.v1beta1.json
@@ -591,7 +591,7 @@
 }
 }
 },
-"revision": "20240228",
+"revision": "20240306",
 "rootUrl": "https://networkmanagement.googleapis.com/",
 "schemas": {
 "AbortInfo": {
@@ -630,7 +630,9 @@
 "GOOGLE_MANAGED_SERVICE_AMBIGUOUS_PSC_ENDPOINT",
 "SOURCE_PSC_CLOUD_SQL_UNSUPPORTED",
 "SOURCE_FORWARDING_RULE_UNSUPPORTED",
-"NON_ROUTABLE_IP_ADDRESS"
+"NON_ROUTABLE_IP_ADDRESS",
+"UNKNOWN_ISSUE_IN_GOOGLE_MANAGED_PROJECT",
+"UNSUPPORTED_GOOGLE_MANAGED_PROJECT_CONFIG"
 ],
 "enumDeprecated": [
 false,
@@ -662,6 +664,8 @@ false,
 false,
 false,
 false,
+false,
+false,
 false
 ],
 "enumDescriptions": [
@@ -694,7 +698,9 @@ false
 "Aborted because a PSC endpoint selection for the Google-managed service is ambiguous (several PSC endpoints satisfy test input).",
 "Aborted because tests with a PSC-based Cloud SQL instance as a source are not supported.",
 "Aborted because tests with a forwarding rule as a source are not supported.",
-"Aborted because one of the endpoints is a non-routable IP address (loopback, link-local, etc)."
+"Aborted because one of the endpoints is a non-routable IP address (loopback, link-local, etc).",
+"Aborted due to an unknown issue in the Google-managed project.",
+"Aborted due to an unsupported configuration of the Google-managed project."
 ],
 "type": "string"
 },
@@ -935,6 +941,10 @@ false
 "description": "A Connectivity Test for a network reachability analysis.",
 "id": "ConnectivityTest",
 "properties": {
+"bypassFirewallChecks": {
+"description": "Whether the test should skip firewall checking. If not provided, we assume false.",
+"type": "boolean"
+},
 "createTime": {
 "description": "Output only. The time the test was created.",
 "format": "google-datetime",
@@ -1110,13 +1120,15 @@ false
 "PSC_ENDPOINT_ACCESSED_FROM_PEERED_NETWORK",
 "PSC_NEG_PRODUCER_ENDPOINT_NO_GLOBAL_ACCESS",
 "PSC_NEG_PRODUCER_FORWARDING_RULE_MULTIPLE_PORTS",
+"CLOUD_SQL_PSC_NEG_UNSUPPORTED",
 "NO_NAT_SUBNETS_FOR_PSC_SERVICE_ATTACHMENT",
 "HYBRID_NEG_NON_DYNAMIC_ROUTE_MATCHED",
 "HYBRID_NEG_NON_LOCAL_DYNAMIC_ROUTE_MATCHED",
 "CLOUD_RUN_REVISION_NOT_READY",
 "DROPPED_INSIDE_PSC_SERVICE_PRODUCER",
 "LOAD_BALANCER_HAS_NO_PROXY_SUBNET",
-"CLOUD_NAT_NO_ADDRESSES"
+"CLOUD_NAT_NO_ADDRESSES",
+"ROUTING_LOOP"
 ],
 "enumDescriptions": [
 "Cause is unspecified.",
@@ -1170,13 +1182,15 @@ false
 "The packet is sent to the Private Service Connect endpoint over the peering, but [it's not supported](https://cloud.google.com/vpc/docs/configure-private-service-connect-services#on-premises).",
 "The packet is sent to the Private Service Connect backend (network endpoint group), but the producer PSC forwarding rule does not have global access enabled.",
 "The packet is sent to the Private Service Connect backend (network endpoint group), but the producer PSC forwarding rule has multiple ports specified.",
+"The packet is sent to the Private Service Connect backend (network endpoint group) targeting a Cloud SQL service attachment, but this configuration is not supported.",
 "No NAT subnets are defined for the PSC service attachment.",
 "The packet sent from the hybrid NEG proxy matches a non-dynamic route, but such a configuration is not supported.",
 "The packet sent from the hybrid NEG proxy matches a dynamic route with a next hop in a different region, but such a configuration is not supported.",
 "Packet sent from a Cloud Run revision that is not ready.",
 "Packet was dropped inside Private Service Connect service producer.",
 "Packet sent to a load balancer, which requires a proxy-only subnet and the subnet is not found.",
-"Packet sent to Cloud Nat without active NAT IPs."
+"Packet sent to Cloud Nat without active NAT IPs.",
+"Packet is stuck in a routing loop."
 ],
 "type": "string"
 },