gcloud: Wed May 25 08:41:12 UTC 2022

gcloud/beta/pubsub/subscriptions/update

@@ -11,6 +11,8 @@ SYNOPSIS
         [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE]
         [--push-endpoint=PUSH_ENDPOINT] [--retain-acked-messages]
         [--update-labels=[KEY=VALUE,...]]
+        [--clear-bigquery-config | [--bigquery-table=BIGQUERY_TABLE
+          : --drop-unknown-fields --use-topic-schema --write-metadata]]
         [--clear-dead-letter-policy
           | --max-delivery-attempts=MAX_DELIVERY_ATTEMPTS
           [--dead-letter-topic=DEAD_LETTER_TOPIC
@@ -97,6 +99,37 @@ FLAGS
         contain only hyphens (-), underscores (_), lowercase characters, and
         numbers.
 
+     At most one of these can be specified:
+
+       --clear-bigquery-config
+          If set, clear the BigQuery config from the subscription.
+
+       BigQuery Config Options. The Cloud Pub/Sub service account associated
+       with the enclosing subscription's parent project (i.e.,
+       service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must
+       have permission to write to this BigQuery table.
+
+         --bigquery-table=BIGQUERY_TABLE
+            A BigQuery table of the form {project}:{dataset_name}.{table_name}
+            to which to write messages for this subscription.
+
+            This flag must be specified if any of the other arguments in this
+            group are specified.
+
+         --drop-unknown-fields
+            When --use-topic-schema is set, whether or not to ignore fields in
+            the topic schema that do not appear in the BigQuery schema. If
+            false, then the BigQuery schema must contain all fields that are
+            also present in the topic schema.
+
+         --use-topic-schema
+            Whether or not to use the schema for the subscription's topic (if
+            it exists) when writing messages to BigQuery.
+
+         --write-metadata
+            Whether or not to write message metadata including message ID,
+            publish timestamp, ordering key, and attributes to BigQuery.
+
      At most one of these can be specified:
 
        --clear-dead-letter-policy