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: Thu Jun 15 10:31:27 UTC 2023

Browse source
This commit is contained in:
Automated 2023-06-15 10:31:27 +00:00
parent 435c9359b5
commit 2102dc5511
223 changed files with 8143 additions and 443 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -141,31 +141,33 @@ OPTIONAL FLAGS
--message-retention-duration window. Acknowledged messages are not
retained by default.
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.
At most one of these can be specified:
--bigquery-table=BIGQUERY_TABLE
A BigQuery table of the form {project}:{dataset_name}.{table_name} to
which to write messages for this 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.
This flag argument must be specified if any of the other arguments in
this group are specified.
--bigquery-table=BIGQUERY_TABLE
A BigQuery table of the form {project}:{dataset_name}.{table_name}
to which to write messages for this subscription.
--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.
This flag argument must be specified if any of the other arguments
in this group are specified.
--use-topic-schema
Whether or not to use the schema for the subscription's topic (if it
exists) when writing messages to BigQuery.
--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.
--write-metadata
Whether or not to write message metadata including message ID,
publish timestamp, ordering key, and attributes to BigQuery.
--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.
Dead Letter Queue Options. The Cloud Pub/Sub service account associated
with the enclosing subscription's parent project (i.e.,

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

@ -106,34 +106,37 @@ FLAGS
At most one of these can be specified:
--clear-bigquery-config
If set, clear the BigQuery config from the subscription.
At most one of these can be specified:
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.
--clear-bigquery-config
If set, clear the BigQuery config from the subscription.
--bigquery-table=BIGQUERY_TABLE
A BigQuery table of the form {project}:{dataset_name}.{table_name}
to which to write messages for this 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.
This flag argument must be specified if any of the other arguments
in this group are specified.
--bigquery-table=BIGQUERY_TABLE
A BigQuery table of the form
{project}:{dataset_name}.{table_name} to which to write messages
for this subscription.
--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.
This flag argument must be specified if any of the other
arguments in this group are specified.
--use-topic-schema
Whether or not to use the schema for the subscription's topic (if
it exists) when writing messages to BigQuery.
--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.
--write-metadata
Whether or not to write message metadata including message ID,
publish timestamp, ordering key, and attributes to BigQuery.
--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: