feat(pubsub): update the api

#### pubsub:v1

The following keys were added:
- schemas.BigQueryConfig.properties.useTableSchema.type (Total Keys: 1)

Author: yoshi-automation

docs/dyn/pubsub_v1.projects.subscriptions.html

@@ -170,7 +170,8 @@ <h3>Method Details</h3>
     &quot;dropUnknownFields&quot;: True or False, # Optional. When true and use_topic_schema is true, any fields that are a part of the topic schema that are not part of the BigQuery table schema are dropped when writing to BigQuery. Otherwise, the schemas must be kept in sync and any messages with extra fields are not written and remain in the subscription&#x27;s backlog.
     &quot;state&quot;: &quot;A String&quot;, # Output only. An output-only field that indicates whether or not the subscription can receive messages.
     &quot;table&quot;: &quot;A String&quot;, # Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}
-    &quot;useTopicSchema&quot;: True or False, # Optional. When true, use the topic&#x27;s schema as the columns to write to in BigQuery, if it exists.
+    &quot;useTableSchema&quot;: True or False, # Optional. When true, use the BigQuery table&#x27;s schema as the columns to write to in BigQuery. `use_table_schema` and `use_topic_schema` cannot be enabled at the same time.
+    &quot;useTopicSchema&quot;: True or False, # Optional. When true, use the topic&#x27;s schema as the columns to write to in BigQuery, if it exists. `use_topic_schema` and `use_table_schema` cannot be enabled at the same time.
     &quot;writeMetadata&quot;: True or False, # Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key to additional columns in the table. The subscription name, message_id, and publish_time fields are put in their own columns while all other message properties (other than data) are written to a JSON object in the attributes column.
   },
   &quot;cloudStorageConfig&quot;: { # Configuration for a Cloud Storage subscription. # Optional. If delivery to Google Cloud Storage is used with this subscription, this field is used to configure it.
@@ -241,7 +242,8 @@ <h3>Method Details</h3>
     &quot;dropUnknownFields&quot;: True or False, # Optional. When true and use_topic_schema is true, any fields that are a part of the topic schema that are not part of the BigQuery table schema are dropped when writing to BigQuery. Otherwise, the schemas must be kept in sync and any messages with extra fields are not written and remain in the subscription&#x27;s backlog.
     &quot;state&quot;: &quot;A String&quot;, # Output only. An output-only field that indicates whether or not the subscription can receive messages.
     &quot;table&quot;: &quot;A String&quot;, # Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}
-    &quot;useTopicSchema&quot;: True or False, # Optional. When true, use the topic&#x27;s schema as the columns to write to in BigQuery, if it exists.
+    &quot;useTableSchema&quot;: True or False, # Optional. When true, use the BigQuery table&#x27;s schema as the columns to write to in BigQuery. `use_table_schema` and `use_topic_schema` cannot be enabled at the same time.
+    &quot;useTopicSchema&quot;: True or False, # Optional. When true, use the topic&#x27;s schema as the columns to write to in BigQuery, if it exists. `use_topic_schema` and `use_table_schema` cannot be enabled at the same time.
     &quot;writeMetadata&quot;: True or False, # Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key to additional columns in the table. The subscription name, message_id, and publish_time fields are put in their own columns while all other message properties (other than data) are written to a JSON object in the attributes column.
   },
   &quot;cloudStorageConfig&quot;: { # Configuration for a Cloud Storage subscription. # Optional. If delivery to Google Cloud Storage is used with this subscription, this field is used to configure it.
@@ -355,7 +357,8 @@ <h3>Method Details</h3>
     &quot;dropUnknownFields&quot;: True or False, # Optional. When true and use_topic_schema is true, any fields that are a part of the topic schema that are not part of the BigQuery table schema are dropped when writing to BigQuery. Otherwise, the schemas must be kept in sync and any messages with extra fields are not written and remain in the subscription&#x27;s backlog.
     &quot;state&quot;: &quot;A String&quot;, # Output only. An output-only field that indicates whether or not the subscription can receive messages.
     &quot;table&quot;: &quot;A String&quot;, # Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}
-    &quot;useTopicSchema&quot;: True or False, # Optional. When true, use the topic&#x27;s schema as the columns to write to in BigQuery, if it exists.
+    &quot;useTableSchema&quot;: True or False, # Optional. When true, use the BigQuery table&#x27;s schema as the columns to write to in BigQuery. `use_table_schema` and `use_topic_schema` cannot be enabled at the same time.
+    &quot;useTopicSchema&quot;: True or False, # Optional. When true, use the topic&#x27;s schema as the columns to write to in BigQuery, if it exists. `use_topic_schema` and `use_table_schema` cannot be enabled at the same time.
     &quot;writeMetadata&quot;: True or False, # Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key to additional columns in the table. The subscription name, message_id, and publish_time fields are put in their own columns while all other message properties (other than data) are written to a JSON object in the attributes column.
   },
   &quot;cloudStorageConfig&quot;: { # Configuration for a Cloud Storage subscription. # Optional. If delivery to Google Cloud Storage is used with this subscription, this field is used to configure it.
@@ -473,7 +476,8 @@ <h3>Method Details</h3>
         &quot;dropUnknownFields&quot;: True or False, # Optional. When true and use_topic_schema is true, any fields that are a part of the topic schema that are not part of the BigQuery table schema are dropped when writing to BigQuery. Otherwise, the schemas must be kept in sync and any messages with extra fields are not written and remain in the subscription&#x27;s backlog.
         &quot;state&quot;: &quot;A String&quot;, # Output only. An output-only field that indicates whether or not the subscription can receive messages.
         &quot;table&quot;: &quot;A String&quot;, # Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}
-        &quot;useTopicSchema&quot;: True or False, # Optional. When true, use the topic&#x27;s schema as the columns to write to in BigQuery, if it exists.
+        &quot;useTableSchema&quot;: True or False, # Optional. When true, use the BigQuery table&#x27;s schema as the columns to write to in BigQuery. `use_table_schema` and `use_topic_schema` cannot be enabled at the same time.
+        &quot;useTopicSchema&quot;: True or False, # Optional. When true, use the topic&#x27;s schema as the columns to write to in BigQuery, if it exists. `use_topic_schema` and `use_table_schema` cannot be enabled at the same time.
         &quot;writeMetadata&quot;: True or False, # Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key to additional columns in the table. The subscription name, message_id, and publish_time fields are put in their own columns while all other message properties (other than data) are written to a JSON object in the attributes column.
       },
       &quot;cloudStorageConfig&quot;: { # Configuration for a Cloud Storage subscription. # Optional. If delivery to Google Cloud Storage is used with this subscription, this field is used to configure it.
@@ -630,7 +634,8 @@ <h3>Method Details</h3>
       &quot;dropUnknownFields&quot;: True or False, # Optional. When true and use_topic_schema is true, any fields that are a part of the topic schema that are not part of the BigQuery table schema are dropped when writing to BigQuery. Otherwise, the schemas must be kept in sync and any messages with extra fields are not written and remain in the subscription&#x27;s backlog.
       &quot;state&quot;: &quot;A String&quot;, # Output only. An output-only field that indicates whether or not the subscription can receive messages.
       &quot;table&quot;: &quot;A String&quot;, # Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}
-      &quot;useTopicSchema&quot;: True or False, # Optional. When true, use the topic&#x27;s schema as the columns to write to in BigQuery, if it exists.
+      &quot;useTableSchema&quot;: True or False, # Optional. When true, use the BigQuery table&#x27;s schema as the columns to write to in BigQuery. `use_table_schema` and `use_topic_schema` cannot be enabled at the same time.
+      &quot;useTopicSchema&quot;: True or False, # Optional. When true, use the topic&#x27;s schema as the columns to write to in BigQuery, if it exists. `use_topic_schema` and `use_table_schema` cannot be enabled at the same time.
       &quot;writeMetadata&quot;: True or False, # Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key to additional columns in the table. The subscription name, message_id, and publish_time fields are put in their own columns while all other message properties (other than data) are written to a JSON object in the attributes column.
     },
     &quot;cloudStorageConfig&quot;: { # Configuration for a Cloud Storage subscription. # Optional. If delivery to Google Cloud Storage is used with this subscription, this field is used to configure it.
@@ -703,7 +708,8 @@ <h3>Method Details</h3>
     &quot;dropUnknownFields&quot;: True or False, # Optional. When true and use_topic_schema is true, any fields that are a part of the topic schema that are not part of the BigQuery table schema are dropped when writing to BigQuery. Otherwise, the schemas must be kept in sync and any messages with extra fields are not written and remain in the subscription&#x27;s backlog.
     &quot;state&quot;: &quot;A String&quot;, # Output only. An output-only field that indicates whether or not the subscription can receive messages.
     &quot;table&quot;: &quot;A String&quot;, # Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}
-    &quot;useTopicSchema&quot;: True or False, # Optional. When true, use the topic&#x27;s schema as the columns to write to in BigQuery, if it exists.
+    &quot;useTableSchema&quot;: True or False, # Optional. When true, use the BigQuery table&#x27;s schema as the columns to write to in BigQuery. `use_table_schema` and `use_topic_schema` cannot be enabled at the same time.
+    &quot;useTopicSchema&quot;: True or False, # Optional. When true, use the topic&#x27;s schema as the columns to write to in BigQuery, if it exists. `use_topic_schema` and `use_table_schema` cannot be enabled at the same time.
     &quot;writeMetadata&quot;: True or False, # Optional. When true, write the subscription name, message_id, publish_time, attributes, and ordering_key to additional columns in the table. The subscription name, message_id, and publish_time fields are put in their own columns while all other message properties (other than data) are written to a JSON object in the attributes column.
   },
   &quot;cloudStorageConfig&quot;: { # Configuration for a Cloud Storage subscription. # Optional. If delivery to Google Cloud Storage is used with this subscription, this field is used to configure it.

googleapiclient/discovery_cache/documents/pubsub.v1.json

@@ -1573,7 +1573,7 @@
       }
     }
   },
-  "revision": "20231128",
+  "revision": "20231205",
   "rootUrl": "https://pubsub.googleapis.com/",
   "schemas": {
     "AcknowledgeRequest": {
@@ -1634,8 +1634,12 @@
           "description": "Optional. The name of the table to which to write data, of the form {projectId}.{datasetId}.{tableId}",
           "type": "string"
         },
+        "useTableSchema": {
+          "description": "Optional. When true, use the BigQuery table's schema as the columns to write to in BigQuery. `use_table_schema` and `use_topic_schema` cannot be enabled at the same time.",
+          "type": "boolean"
+        },
         "useTopicSchema": {
-          "description": "Optional. When true, use the topic's schema as the columns to write to in BigQuery, if it exists.",
+          "description": "Optional. When true, use the topic's schema as the columns to write to in BigQuery, if it exists. `use_topic_schema` and `use_table_schema` cannot be enabled at the same time.",
           "type": "boolean"
         },
         "writeMetadata": {

googleapiclient/discovery_cache/documents/pubsub.v1beta1a.json

@@ -464,7 +464,7 @@
       }
     }
   },
-  "revision": "20231128",
+  "revision": "20231205",
   "rootUrl": "https://pubsub.googleapis.com/",
   "schemas": {
     "AcknowledgeRequest": {

googleapiclient/discovery_cache/documents/pubsub.v1beta2.json

@@ -731,7 +731,7 @@
       }
     }
   },
-  "revision": "20231128",
+  "revision": "20231205",
   "rootUrl": "https://pubsub.googleapis.com/",
   "schemas": {
     "AcknowledgeRequest": {