imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-16 12:22:03 +00:00
Code Activity

gcloud: Wed Aug 2 11:22:33 UTC 2023

Browse source
This commit is contained in:
Automated 2023-08-02 11:22:33 +00:00
parent 4558a00e48
commit 678b9afba9
240 changed files with 7837 additions and 521 deletions
Download patch file Download diff file Expand all files Collapse all files

12
gcloud/alpha/pubsub/subscriptions/create
View file

@ -174,7 +174,11 @@ OPTIONAL FLAGS
--write-metadata
Whether or not to write message metadata including message ID,
publish timestamp, ordering key, and attributes to BigQuery.
publish timestamp, ordering key, and attributes to BigQuery. The
subscription name, message_id, and publish_time fields are put in
their own columns while all other message properties other than
data (for example, an ordering_key, if present) are written to a
JSON object in the attributes column.
Cloud Storage Config Options. The Cloud Pub/Sub service account
associated with the enclosing subscription's parent project (i.e.,
@ -216,7 +220,11 @@ OPTIONAL FLAGS
--cloud-storage-write-metadata
Whether or not to write the subscription name, message_id,
publish_time, attributes, and ordering_key as additional fields in
the output. This has an effect only for subscriptions with
the output. The subscription name, message_id, and publish_time
fields are put in their own fields while all other message
properties other than data (for example, an ordering_key, if
present) are added as entries in the attributes map. This has an
effect only for subscriptions with
--cloud-storage-output-format=avro.
Dead Letter Queue Options. The Cloud Pub/Sub service account associated

12
gcloud/alpha/pubsub/subscriptions/update
View file

@ -144,7 +144,11 @@ FLAGS
--write-metadata
Whether or not to write message metadata including message ID,
publish timestamp, ordering key, and attributes to BigQuery.
publish timestamp, ordering key, and attributes to BigQuery. The
subscription name, message_id, and publish_time fields are put in
their own columns while all other message properties other than
data (for example, an ordering_key, if present) are written to a
JSON object in the attributes column.
At most one of these can be specified:
@ -195,7 +199,11 @@ FLAGS
--cloud-storage-write-metadata
Whether or not to write the subscription name, message_id,
publish_time, attributes, and ordering_key as additional fields
in the output. This has an effect only for subscriptions with
in the output. The subscription name, message_id, and
publish_time fields are put in their own fields while all other
message properties other than data (for example, an ordering_key,
if present) are added as entries in the attributes map. This has
an effect only for subscriptions with
--cloud-storage-output-format=avro.
At most one of these can be specified: