imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-11 07:29:40 +00:00
Code Activity

gcloud: Wed Jan 31 10:36:17 UTC 2024

Browse source
This commit is contained in:
Automated 2024-01-31 10:36:17 +00:00
parent 7a546ffea4
commit fa6c1dc7ec
142 changed files with 1981 additions and 793 deletions
Download patch file Download diff file Expand all files Collapse all files

25
gcloud/beta/pubsub/topics/create
View file

@ -5,11 +5,12 @@ SYNOPSIS
gcloud beta pubsub topics create TOPIC [TOPIC ...]
[--labels=[KEY=VALUE,...]]
[--message-retention-duration=MESSAGE_RETENTION_DURATION]
[--message-storage-policy-allowed-regions=[REGION,...]]
[--message-encoding=ENCODING (--schema=SCHEMA
: --schema-project=SCHEMA_PROJECT)
: --first-revision-id=FIRST_REVISION_ID
--last-revision-id=LAST_REVISION_ID]
[--message-storage-policy-allowed-regions=[REGION,...]
: --message-storage-policy-enforce-in-transit]
[--topic-encryption-key=TOPIC_ENCRYPTION_KEY
: --topic-encryption-key-keyring=TOPIC_ENCRYPTION_KEY_KEYRING
--topic-encryption-key-location=TOPIC_ENCRYPTION_KEY_LOCATION
@ -64,12 +65,6 @@ FLAGS
is one of "s", "m", "h", and "d" for seconds, minutes, hours, and days,
respectively. If the unit is omitted, seconds is assumed.
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.
@ -111,6 +106,22 @@ FLAGS
▫ provide the argument --project on the command line;
▫ set the property core/project.
Options for explicitly specifying the message storage policy
(https://cloud.google.com/pubsub/docs/resource-location-restriction) 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.
This flag argument must be specified if any of the other arguments in
this group are specified.
--message-storage-policy-enforce-in-transit
Whether or not to enforce in-transit guarantees for this topic using
the allowed regions. This ensures that publishing, pulling, and push
delivery are only handled in allowed Cloud regions.
Key resource - The Cloud KMS (Key Management Service) cryptokey that will
be used to protect the topic. The specified Cloud KMS key should have
purpose set to "ENCRYPT_DECRYPT". The service account,

33
gcloud/beta/pubsub/topics/update
View file

@ -11,8 +11,9 @@ SYNOPSIS
: --schema-project=SCHEMA_PROJECT)
: --first-revision-id=FIRST_REVISION_ID
--last-revision-id=LAST_REVISION_ID]]
[--message-storage-policy-allowed-regions=[REGION,...]
| --recompute-message-storage-policy]
[--recompute-message-storage-policy
| [--message-storage-policy-allowed-regions=[REGION,...]
: --message-storage-policy-enforce-in-transit]]
[--topic-encryption-key=TOPIC_ENCRYPTION_KEY
: --topic-encryption-key-keyring=TOPIC_ENCRYPTION_KEY_KEYRING
--topic-encryption-key-location=TOPIC_ENCRYPTION_KEY_LOCATION
@ -65,6 +66,13 @@ EXAMPLES
$ gcloud beta pubsub topics update mytopic \
--recompute-message-storage-policy
To enforce both at-rest and in-transit guarantees for messages published to
the topic, run:
$ gcloud beta pubsub topics update mytopic \
--message-storage-policy-allowed-regions=some-cloud-region1,\
some-cloud-region2 --message-storage-policy-enforce-in-transit
POSITIONAL ARGUMENTS
Topic resource - Name of the topic to update. This represents a Cloud
resource. (NOTE) Some attributes are not given arguments in this group but
@ -184,18 +192,27 @@ FLAGS
At most one of these can be specified:
Options for explicitly specifying the message storage policy for a
topic. These fields can be set only if the
--recompute-message-storage-policy
If given, Pub/Sub recomputes the regions where messages can be stored
at rest, based on your organization's "Resource Location Restriction"
policy.
Options for explicitly specifying the message storage policy
(https://cloud.google.com/pubsub/docs/resource-location-restriction) 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, Pub/Sub recomputes the regions where messages can be stored
at rest, based on your organization's "Resource Location Restriction"
policy.
This flag argument must be specified if any of the other arguments
in this group are specified.
--message-storage-policy-enforce-in-transit
Whether or not to enforce in-transit guarantees for this topic
using the allowed regions. This ensures that publishing, pulling,
and push delivery are only handled in allowed Cloud regions.
Key resource - The Cloud KMS (Key Management Service) cryptokey that will
be used to protect the topic. The specified Cloud KMS key should have