feat(all): auto-regenerate discovery clients (#2409)

networkmanagement/v1/networkmanagement-api.json

@@ -591,7 +591,7 @@
       }
     }
   },
-  "revision": "20240124",
+  "revision": "20240131",
   "rootUrl": "https://networkmanagement.googleapis.com/",
   "schemas": {
     "AbortInfo": {
@@ -2232,7 +2232,7 @@
             "No result was specified.",
             "Possible scenarios are: * The configuration analysis determined that a packet originating from the source is expected to reach the destination. * The analysis didn't complete because the user lacks permission for some of the resources in the trace. However, at the time the user's permission became insufficient, the trace had been successful so far.",
             "A packet originating from the source is expected to be dropped before reaching the destination.",
-            "The source and destination endpoints do not uniquely identify the test location in the network, and the reachability result contains multiple traces. For some traces, a packet could be delivered, and for others, it would not be.",
+            "The source and destination endpoints do not uniquely identify the test location in the network, and the reachability result contains multiple traces. For some traces, a packet could be delivered, and for others, it would not be. This result is also assigned to configuration analysis of return path if on its own it should be REACHABLE, but configuration analysis of forward path is AMBIGUOUS.",
             "The configuration analysis did not complete. Possible reasons are: * A permissions error occurred--for example, the user might not have read permission for all of the resources named in the test. * An internal error occurred. * The analyzer received an invalid or unsupported argument or was unable to identify a known endpoint."
           ],
           "type": "string"
@@ -2711,6 +2711,11 @@
           "$ref": "EndpointInfo",
           "description": "Derived from the source and destination endpoints definition specified by user request, and validated by the data plane model. If there are multiple traces starting from different source locations, then the endpoint_info may be different between traces."
         },
+        "forwardTraceId": {
+          "description": "ID of trace. For forward traces, this ID is unique for each trace. For return traces, it matches ID of associated forward trace. A single forward trace can be associated with none, one or more than one return trace.",
+          "format": "int32",
+          "type": "integer"
+        },
         "steps": {
           "description": "A trace of a test contains multiple steps from the initial state to the final state (delivered, dropped, forwarded, or aborted). The steps are ordered by the processing sequence within the simulated network state machine. It is critical to preserve the order of the steps and avoid reordering or sorting them.",
           "items": {

networkmanagement/v1beta1/networkmanagement-api.json

@@ -591,7 +591,7 @@
       }
     }
   },
-  "revision": "20240124",
+  "revision": "20240131",
   "rootUrl": "https://networkmanagement.googleapis.com/",
   "schemas": {
     "AbortInfo": {
@@ -2237,7 +2237,7 @@
             "No result was specified.",
             "Possible scenarios are: * The configuration analysis determined that a packet originating from the source is expected to reach the destination. * The analysis didn't complete because the user lacks permission for some of the resources in the trace. However, at the time the user's permission became insufficient, the trace had been successful so far.",
             "A packet originating from the source is expected to be dropped before reaching the destination.",
-            "The source and destination endpoints do not uniquely identify the test location in the network, and the reachability result contains multiple traces. For some traces, a packet could be delivered, and for others, it would not be.",
+            "The source and destination endpoints do not uniquely identify the test location in the network, and the reachability result contains multiple traces. For some traces, a packet could be delivered, and for others, it would not be. This result is also assigned to configuration analysis of return path if on its own it should be REACHABLE, but configuration analysis of forward path is AMBIGUOUS.",
             "The configuration analysis did not complete. Possible reasons are: * A permissions error occurred--for example, the user might not have read permission for all of the resources named in the test. * An internal error occurred. * The analyzer received an invalid or unsupported argument or was unable to identify a known endpoint."
           ],
           "type": "string"
@@ -2716,6 +2716,11 @@
           "$ref": "EndpointInfo",
           "description": "Derived from the source and destination endpoints definition specified by user request, and validated by the data plane model. If there are multiple traces starting from different source locations, then the endpoint_info may be different between traces."
         },
+        "forwardTraceId": {
+          "description": "ID of trace. For forward traces, this ID is unique for each trace. For return traces, it matches ID of associated forward trace. A single forward trace can be associated with none, one or more than one return trace.",
+          "format": "int32",
+          "type": "integer"
+        },
         "steps": {
           "description": "A trace of a test contains multiple steps from the initial state to the final state (delivered, dropped, forwarded, or aborted). The steps are ordered by the processing sequence within the simulated network state machine. It is critical to preserve the order of the steps and avoid reordering or sorting them.",
           "items": {

spanner/v1/spanner-api.json

@@ -2729,7 +2729,7 @@
       }
     }
   },
-  "revision": "20240131",
+  "revision": "20240207",
   "rootUrl": "https://spanner.googleapis.com/",
   "schemas": {
     "AutoscalingConfig": {
@@ -3285,7 +3285,7 @@
           "type": "array"
         },
         "protoDescriptors": {
-          "description": "Optional. Proto descriptors used by CREATE/ALTER PROTO BUNDLE statements in 'extra_statements' above. Contains a protobuf-serialized [google.protobuf.FileDescriptorSet](https://github.com/protocolbuffers/protobuf/blob/main/src/google/protobuf/descriptor.proto). To generate it, [install](https://grpc.io/docs/protoc-installation/) and run `protoc` with --include_imports and --descriptor_set_out. For example, to generate for moon/shot/app.proto, run \"\"\" $protoc --proto_path=/app_path --proto_path=/lib_path \\ --include_imports \\ --descriptor_set_out=descriptors.data \\ moon/shot/app.proto \"\"\" For more details, see protobuffer [self description](https://developers.google.com/protocol-buffers/docs/techniques#self-description).",
+          "description": "Optional. Proto descriptors used by CREATE/ALTER PROTO BUNDLE statements in 'extra_statements' above. Contains a protobuf-serialized [google.protobuf.FileDescriptorSet](https://github.com/protocolbuffers/protobuf/blob/main/src/google/protobuf/descriptor.proto). To generate it, [install](https://grpc.io/docs/protoc-installation/) and run `protoc` with --include_imports and --descriptor_set_out. For example, to generate for moon/shot/app.proto, run ``` $protoc --proto_path=/app_path --proto_path=/lib_path \\ --include_imports \\ --descriptor_set_out=descriptors.data \\ moon/shot/app.proto ``` For more details, see protobuffer [self description](https://developers.google.com/protocol-buffers/docs/techniques#self-description).",
           "format": "byte",
           "type": "string"
         }
@@ -3345,6 +3345,20 @@
           "format": "google-datetime",
           "type": "string"
         },
+        "expectedFulfillmentPeriod": {
+          "description": "The expected fulfillment period of this create operation.",
+          "enum": [
+            "FULFILLMENT_PERIOD_UNSPECIFIED",
+            "FULFILLMENT_PERIOD_NORMAL",
+            "FULFILLMENT_PERIOD_EXTENDED"
+          ],
+          "enumDescriptions": [
+            "Not specified.",
+            "Normal fulfillment period. The operation is expected to complete within minutes.",
+            "Extended fulfillment period. It can take up to an hour for the operation to complete."
+          ],
+          "type": "string"
+        },
         "instance": {
           "$ref": "Instance",
           "description": "The instance being created."
@@ -3585,7 +3599,7 @@
       "properties": {
         "excludeReplicas": {
           "$ref": "ExcludeReplicas",
-          "description": "Exclude_replicas indicates that should be excluded from serving requests. Spanner will not route requests to the replicas in this list."
+          "description": "Exclude_replicas indicates that specified replicas should be excluded from serving requests. Spanner will not route requests to the replicas in this list."
         },
         "includeReplicas": {
           "$ref": "IncludeReplicas",
@@ -5210,7 +5224,7 @@
       "type": "object"
     },
     "ReplicaSelection": {
-      "description": "The directed read replica selector. Callers must provide one or more of the following fields for replica selection: * `location` - The location must be one of the regions within the multi-region configuration of your database. * `type` - The type of the replica. Some examples of using replica_selectors are: * `location:us-east1` --\u003e The \"us-east1\" replica(s) of any available type will be used to process the request. * `type:READ_ONLY` --\u003e The \"READ_ONLY\" type replica(s) in nearest . available location will be used to process the request. * `location:us-east1 type:READ_ONLY` --\u003e The \"READ_ONLY\" type replica(s) in location \"us-east1\" will be used to process the request.",
+      "description": "The directed read replica selector. Callers must provide one or more of the following fields for replica selection: * `location` - The location must be one of the regions within the multi-region configuration of your database. * `type` - The type of the replica. Some examples of using replica_selectors are: * `location:us-east1` --\u003e The \"us-east1\" replica(s) of any available type will be used to process the request. * `type:READ_ONLY` --\u003e The \"READ_ONLY\" type replica(s) in nearest available location will be used to process the request. * `location:us-east1 type:READ_ONLY` --\u003e The \"READ_ONLY\" type replica(s) in location \"us-east1\" will be used to process the request.",
       "id": "ReplicaSelection",
       "properties": {
         "location": {
@@ -5855,7 +5869,7 @@
           "type": "string"
         },
         "protoDescriptors": {
-          "description": "Optional. Proto descriptors used by CREATE/ALTER PROTO BUNDLE statements. Contains a protobuf-serialized [google.protobuf.FileDescriptorSet](https://github.com/protocolbuffers/protobuf/blob/main/src/google/protobuf/descriptor.proto). To generate it, [install](https://grpc.io/docs/protoc-installation/) and run `protoc` with --include_imports and --descriptor_set_out. For example, to generate for moon/shot/app.proto, run \"\"\" $protoc --proto_path=/app_path --proto_path=/lib_path \\ --include_imports \\ --descriptor_set_out=descriptors.data \\ moon/shot/app.proto \"\"\" For more details, see protobuffer [self description](https://developers.google.com/protocol-buffers/docs/techniques#self-description).",
+          "description": "Optional. Proto descriptors used by CREATE/ALTER PROTO BUNDLE statements. Contains a protobuf-serialized [google.protobuf.FileDescriptorSet](https://github.com/protocolbuffers/protobuf/blob/main/src/google/protobuf/descriptor.proto). To generate it, [install](https://grpc.io/docs/protoc-installation/) and run `protoc` with --include_imports and --descriptor_set_out. For example, to generate for moon/shot/app.proto, run ``` $protoc --proto_path=/app_path --proto_path=/lib_path \\ --include_imports \\ --descriptor_set_out=descriptors.data \\ moon/shot/app.proto ``` For more details, see protobuffer [self description](https://developers.google.com/protocol-buffers/docs/techniques#self-description).",
           "format": "byte",
           "type": "string"
         },
@@ -5959,6 +5973,20 @@
           "format": "google-datetime",
           "type": "string"
         },
+        "expectedFulfillmentPeriod": {
+          "description": "The expected fulfillment period of this update operation.",
+          "enum": [
+            "FULFILLMENT_PERIOD_UNSPECIFIED",
+            "FULFILLMENT_PERIOD_NORMAL",
+            "FULFILLMENT_PERIOD_EXTENDED"
+          ],
+          "enumDescriptions": [
+            "Not specified.",
+            "Normal fulfillment period. The operation is expected to complete within minutes.",
+            "Extended fulfillment period. It can take up to an hour for the operation to complete."
+          ],
+          "type": "string"
+        },
         "instance": {
           "$ref": "Instance",
           "description": "The desired end state of the update."