gcloud: Wed Dec 6 10:10:36 UTC 2023

2026-07-18 23:08:48 +00:00 · 2023-12-06 10:10:36 +00:00 · 2023-12-06 10:10:36 +00:00 · f36750d203
commit f36750d203
parent d3074f94bb
469 changed files with 9617 additions and 1400 deletions
--- a/gcloud/beta/pubsub/subscriptions/create
+++ b/gcloud/beta/pubsub/subscriptions/create
@ -13,8 +13,8 @@ SYNOPSIS
        [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE]
        [--push-endpoint=PUSH_ENDPOINT] [--retain-acked-messages]
        [[--bigquery-table=BIGQUERY_TABLE
-          : --drop-unknown-fields --use-topic-schema --write-metadata]
-          | [--cloud-storage-bucket=CLOUD_STORAGE_BUCKET
+          : --drop-unknown-fields --write-metadata --use-table-schema
+          | --use-topic-schema] | [--cloud-storage-bucket=CLOUD_STORAGE_BUCKET
          : --cloud-storage-file-prefix=CLOUD_STORAGE_FILE_PREFIX
          --cloud-storage-file-suffix=CLOUD_STORAGE_FILE_SUFFIX
          --cloud-storage-max-bytes=CLOUD_STORAGE_MAX_BYTES
@ -166,16 +166,10 @@ OPTIONAL FLAGS
            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 --no-drop-unknown-fields to
-            disable this flag.
-
-         --use-topic-schema
-            Whether or not to use the schema for the subscription's topic (if
-            it exists) when writing messages to BigQuery. Use
-            --no-use-topic-schema to disable this flag.
+            If either --use-topic-schema or --use-table-schema is set, whether
+            or not to ignore fields in the message that do not appear in the
+            BigQuery table schema. Use --no-drop-unknown-fields to disable this
+            flag.

         --write-metadata
            Whether or not to write message metadata including message ID,
@ -186,6 +180,20 @@ OPTIONAL FLAGS
            JSON object in the attributes column. Use --no-write-metadata to
            disable this flag.

+         At most one of these can be specified:
+
+           --use-table-schema
+              Whether or not to use the BigQuery table schema when writing
+              messages to BigQuery. Use --no-use-table-schema to disable this
+              flag.
+
+           --use-topic-schema
+              Whether or not to use the schema for the subscription's topic (if
+              it exists) when writing messages to BigQuery. If
+              --drop-unknown-fields is not set, then the BigQuery schema must
+              contain all fields that are present in the topic schema. Use
+              --no-use-topic-schema to disable this flag.
+
       Cloud Storage 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
--- a/gcloud/beta/pubsub/subscriptions/update
+++ b/gcloud/beta/pubsub/subscriptions/update
@ -12,8 +12,8 @@ SYNOPSIS
        [--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-cloud-storage-config
+          : --drop-unknown-fields --write-metadata --use-table-schema
+          | --use-topic-schema] | --clear-cloud-storage-config
          | [--cloud-storage-bucket=CLOUD_STORAGE_BUCKET
          : --cloud-storage-file-prefix=CLOUD_STORAGE_FILE_PREFIX
          --cloud-storage-file-suffix=CLOUD_STORAGE_FILE_SUFFIX
@ -136,17 +136,11 @@ FLAGS
              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 --no-drop-unknown-fields to
+              If either --use-topic-schema or --use-table-schema is set,
+              whether or not to ignore fields in the message that do not appear
+              in the BigQuery table schema. Use --no-drop-unknown-fields to
              disable this flag.

-           --use-topic-schema
-              Whether or not to use the schema for the subscription's topic (if
-              it exists) when writing messages to BigQuery. Use
-              --no-use-topic-schema to disable this flag.
-
           --write-metadata
              Whether or not to write message metadata including message ID,
              publish timestamp, ordering key, and attributes to BigQuery. The
@ -156,6 +150,20 @@ FLAGS
              JSON object in the attributes column. Use --no-write-metadata to
              disable this flag.

+           At most one of these can be specified:
+
+             --use-table-schema
+                Whether or not to use the BigQuery table schema when writing
+                messages to BigQuery. Use --no-use-table-schema to disable this
+                flag.
+
+             --use-topic-schema
+                Whether or not to use the schema for the subscription's topic
+                (if it exists) when writing messages to BigQuery. If
+                --drop-unknown-fields is not set, then the BigQuery schema must
+                contain all fields that are present in the topic schema. Use
+                --no-use-topic-schema to disable this flag.
+
       At most one of these can be specified:

         --clear-cloud-storage-config
--- a/gcloud/beta/pubsub/topics/create
+++ b/gcloud/beta/pubsub/topics/create
@ -64,9 +64,11 @@ FLAGS
        is one of "s", "m", "h", and "d" for seconds, minutes, hours, and days,
        respectively. If the unit is omitted, seconds is assumed.

-     --message-storage-policy-allowed-regions=[REGION,...]
-        A list of one or more Cloud regions where messages are allowed to be
-        stored at rest.
+     Options for explicitly specifying the message storage policy for a topic.
+
+       --message-storage-policy-allowed-regions=[REGION,...]
+          A list of one or more Cloud regions where messages are allowed to be
+          stored at rest.

     Schema settings. The schema that messages published to this topic must
     conform to and the expected message encoding.
--- a/gcloud/beta/pubsub/topics/update
+++ b/gcloud/beta/pubsub/topics/update
@ -184,14 +184,18 @@ FLAGS

     At most one of these can be specified:

-       --message-storage-policy-allowed-regions=[REGION,...]
-          A list of one or more Cloud regions where messages are allowed to be
-          stored at rest.
+       Options for explicitly specifying the message storage policy for a
+       topic. These fields can be set only if the
+       --recompute-message-storage-policy flag is not set.
+
+         --message-storage-policy-allowed-regions=[REGION,...]
+            A list of one or more Cloud regions where messages are allowed to
+            be stored at rest.

       --recompute-message-storage-policy
-          If given, Cloud Pub/Sub will recompute the regions where messages can
-          be stored at rest, based on your organization's "Resource Location
-          Restriction" policy.
+          If given, Pub/Sub recomputes the regions where messages can be stored
+          at rest, based on your organization's "Resource Location Restriction"
+          policy.

     Key resource - The Cloud KMS (Key Management Service) cryptokey that will
     be used to protect the topic. The specified Cloud KMS key should have