mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-11 23:49:35 +00:00
gcloud: Wed Oct 25 11:42:23 UTC 2023
This commit is contained in:
parent
a15665661a
commit
d34c41a2ce
305 changed files with 5549 additions and 699 deletions
|
|
@ -91,12 +91,14 @@ OPTIONAL FLAGS
|
|||
message with a given value of message_id on this subscription: The
|
||||
message sent to a subscriber is guaranteed not to be resent before the
|
||||
message's acknowledgment deadline expires. An acknowledged message will
|
||||
not be resent to a subscriber.
|
||||
not be resent to a subscriber. Use --no-enable-exactly-once-delivery to
|
||||
disable this flag.
|
||||
|
||||
--enable-message-ordering
|
||||
Whether to receive messages with the same ordering key in order. If
|
||||
set, messages with the same ordering key are sent to subscribers in the
|
||||
order that Pub/Sub receives them.
|
||||
order that Pub/Sub receives them. Use --no-enable-message-ordering to
|
||||
disable this flag.
|
||||
|
||||
--expiration-period=EXPIRATION_PERIOD
|
||||
The subscription will expire if it is inactive for the given period.
|
||||
|
|
@ -146,7 +148,8 @@ OPTIONAL FLAGS
|
|||
Whether or not to retain acknowledged messages. If true, messages are
|
||||
not expunged from the subscription's backlog until they fall out of the
|
||||
--message-retention-duration window. Acknowledged messages are not
|
||||
retained by default.
|
||||
retained by default. Use --no-retain-acked-messages to disable this
|
||||
flag.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
|
|
@ -166,11 +169,13 @@ OPTIONAL FLAGS
|
|||
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.
|
||||
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.
|
||||
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,
|
||||
|
|
@ -178,7 +183,8 @@ OPTIONAL FLAGS
|
|||
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.
|
||||
JSON object in the attributes column. Use --no-write-metadata to
|
||||
disable this flag.
|
||||
|
||||
Cloud Storage Config Options. The Cloud Pub/Sub service account
|
||||
associated with the enclosing subscription's parent project (i.e.,
|
||||
|
|
@ -225,7 +231,8 @@ OPTIONAL FLAGS
|
|||
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.
|
||||
--cloud-storage-output-format=avro. Use
|
||||
--no-cloud-storage-write-metadata to disable this flag.
|
||||
|
||||
Dead Letter Queue Options. The Cloud Pub/Sub service account associated
|
||||
with the enclosing subscription's parent project (i.e.,
|
||||
|
|
@ -284,6 +291,7 @@ OPTIONAL FLAGS
|
|||
|
||||
--push-no-wrapper
|
||||
When set, the message data is delivered directly as the HTTP body.
|
||||
Use --no-push-no-wrapper to disable this flag.
|
||||
|
||||
This flag argument must be specified if any of the other arguments in
|
||||
this group are specified.
|
||||
|
|
@ -292,7 +300,8 @@ OPTIONAL FLAGS
|
|||
When true, writes the Pub/Sub message metadata to
|
||||
x-goog-pubsub-<KEY>:<VAL> headers of the HTTP request. Writes the
|
||||
Pub/Sub message attributes to <KEY>:<VAL> headers of the HTTP
|
||||
request.
|
||||
request. Use --no-push-no-wrapper-write-metadata to disable this
|
||||
flag.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
|
|
|
|||
|
|
@ -51,6 +51,7 @@ OPTIONAL FLAGS
|
|||
|
||||
--push-no-wrapper
|
||||
When set, the message data is delivered directly as the HTTP body.
|
||||
Use --no-push-no-wrapper to disable this flag.
|
||||
|
||||
This flag argument must be specified if any of the other arguments in
|
||||
this group are specified.
|
||||
|
|
@ -59,7 +60,8 @@ OPTIONAL FLAGS
|
|||
When true, writes the Pub/Sub message metadata to
|
||||
x-goog-pubsub-<KEY>:<VAL> headers of the HTTP request. Writes the
|
||||
Pub/Sub message attributes to <KEY>:<VAL> headers of the HTTP
|
||||
request.
|
||||
request. Use --no-push-no-wrapper-write-metadata to disable this
|
||||
flag.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
|
|
|
|||
|
|
@ -42,7 +42,8 @@ POSITIONAL ARGUMENTS
|
|||
|
||||
FLAGS
|
||||
--auto-ack
|
||||
Automatically ACK every message pulled from this subscription.
|
||||
Automatically ACK every message pulled from this subscription. Use
|
||||
--no-auto-ack to disable this flag.
|
||||
|
||||
--max-messages=MAX_MESSAGES; default=1
|
||||
(DEPRECATED) The maximum number of messages that Cloud Pub/Sub can
|
||||
|
|
@ -59,7 +60,8 @@ FLAGS
|
|||
messages readily available in memory buffers. If no messages are
|
||||
available in the buffers, returns an empty list of messages as
|
||||
response, even if having messages in the backlog. Do not set this
|
||||
flag as it adversely impacts the performance of pull.
|
||||
flag as it adversely impacts the performance of pull. Use
|
||||
--no-return-immediately to disable this flag.
|
||||
|
||||
--wait
|
||||
(DEPRECATED) Wait (for a bounded amount of time) for new messages
|
||||
|
|
|
|||
|
|
@ -66,7 +66,8 @@ FLAGS
|
|||
message sent to a subscriber is guaranteed not to be resent before the
|
||||
message's acknowledgment deadline expires. An acknowledged message will
|
||||
not be resent to a subscriber. To disable exactly-once delivery use
|
||||
--no-enable-exactly-once-delivery.
|
||||
--no-enable-exactly-once-delivery. Use
|
||||
--no-enable-exactly-once-delivery to disable this flag.
|
||||
|
||||
--expiration-period=EXPIRATION_PERIOD
|
||||
The subscription will expire if it is inactive for the given period.
|
||||
|
|
@ -101,7 +102,8 @@ FLAGS
|
|||
Whether or not to retain acknowledged messages. If true, messages are
|
||||
not expunged from the subscription's backlog until they fall out of the
|
||||
--message-retention-duration window. Acknowledged messages are not
|
||||
retained by default.
|
||||
retained by default. Use --no-retain-acked-messages to disable this
|
||||
flag.
|
||||
|
||||
--update-labels=[KEY=VALUE,...]
|
||||
List of label KEY=VALUE pairs to update. If a label exists, its value
|
||||
|
|
@ -117,7 +119,8 @@ FLAGS
|
|||
At most one of these can be specified:
|
||||
|
||||
--clear-bigquery-config
|
||||
If set, clear the BigQuery config from the subscription.
|
||||
If set, clear the BigQuery config from the subscription. Use
|
||||
--no-clear-bigquery-config to disable this flag.
|
||||
|
||||
BigQuery Config Options. The Cloud Pub/Sub service account associated
|
||||
with the enclosing subscription's parent project (i.e.,
|
||||
|
|
@ -136,11 +139,13 @@ FLAGS
|
|||
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.
|
||||
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.
|
||||
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,
|
||||
|
|
@ -148,12 +153,14 @@ FLAGS
|
|||
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.
|
||||
JSON object in the attributes column. Use --no-write-metadata to
|
||||
disable this flag.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--clear-cloud-storage-config
|
||||
If set, clear the Cloud Storage config from the subscription.
|
||||
If set, clear the Cloud Storage config from the subscription. Use
|
||||
--no-clear-cloud-storage-config to disable this flag.
|
||||
|
||||
Cloud Storage Config Options. The Cloud Pub/Sub service account
|
||||
associated with the enclosing subscription's parent project (i.e.,
|
||||
|
|
@ -204,12 +211,14 @@ FLAGS
|
|||
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.
|
||||
--cloud-storage-output-format=avro. Use
|
||||
--no-cloud-storage-write-metadata to disable this flag.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--clear-dead-letter-policy
|
||||
If set, clear the dead letter policy from the subscription.
|
||||
If set, clear the dead letter policy from the subscription. Use
|
||||
--no-clear-dead-letter-policy to disable this flag.
|
||||
|
||||
Dead Letter Queue Options. The Cloud Pub/Sub service account associated
|
||||
with the enclosing subscription's parent project (i.e.,
|
||||
|
|
@ -270,12 +279,14 @@ FLAGS
|
|||
At most one of these can be specified:
|
||||
|
||||
--clear-push-no-wrapper-config
|
||||
If set, clear the NoWrapper config from the subscription.
|
||||
If set, clear the NoWrapper config from the subscription. Use
|
||||
--no-clear-push-no-wrapper-config to disable this flag.
|
||||
|
||||
NoWrapper Config Options.
|
||||
|
||||
--push-no-wrapper
|
||||
When set, the message data is delivered directly as the HTTP body.
|
||||
Use --no-push-no-wrapper to disable this flag.
|
||||
|
||||
This flag argument must be specified if any of the other arguments
|
||||
in this group are specified.
|
||||
|
|
@ -284,12 +295,14 @@ FLAGS
|
|||
When true, writes the Pub/Sub message metadata to
|
||||
x-goog-pubsub-<KEY>:<VAL> headers of the HTTP request. Writes the
|
||||
Pub/Sub message attributes to <KEY>:<VAL> headers of the HTTP
|
||||
request.
|
||||
request. Use --no-push-no-wrapper-write-metadata to disable this
|
||||
flag.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--clear-retry-policy
|
||||
If set, clear the retry policy from the subscription.
|
||||
If set, clear the retry policy from the subscription. Use
|
||||
--no-clear-retry-policy to disable this flag.
|
||||
|
||||
Retry Policy Options. Retry policy specifies how Cloud Pub/Sub retries
|
||||
message delivery for this subscription.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue