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

gcloud: Wed Feb 1 11:38:52 UTC 2023

Browse source
This commit is contained in:
Automated 2023-02-01 11:38:52 +00:00
parent 6dc17bdd4a
commit fc11b54760
173 changed files with 5650 additions and 253 deletions
Download patch file Download diff file Expand all files Collapse all files

9
gcloud/beta/ai/hp-tuning-jobs/create
View file

@ -5,9 +5,8 @@ SYNOPSIS
gcloud beta ai hp-tuning-jobs create --config=CONFIG
--display-name=DISPLAY_NAME [--algorithm=ALGORITHM]
[--enable-dashboard-access] [--enable-web-access]
[--labels=[KEY=VALUE,...]]
[--max-trial-count=MAX_TRIAL_COUNT; default=1] [--network=NETWORK]
[--parallel-trial-count=PARALLEL_TRIAL_COUNT; default=1]
[--labels=[KEY=VALUE,...]] [--max-trial-count=MAX_TRIAL_COUNT]
[--network=NETWORK] [--parallel-trial-count=PARALLEL_TRIAL_COUNT]
[--region=REGION] [--service-account=SERVICE_ACCOUNT]
[--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
--kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
@ -82,7 +81,7 @@ OPTIONAL FLAGS
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
--max-trial-count=MAX_TRIAL_COUNT; default=1
--max-trial-count=MAX_TRIAL_COUNT
Desired total number of trials. The default value is 1.
--network=NETWORK
@ -90,7 +89,7 @@ OPTIONAL FLAGS
peered with. Private services access must already have been configured.
If unspecified, the Job is not peered with any network.
--parallel-trial-count=PARALLEL_TRIAL_COUNT; default=1
--parallel-trial-count=PARALLEL_TRIAL_COUNT
Desired number of Trials to run in parallel. The default value is 1.
Region resource - Cloud region to create a hyperparameter tuning job. This

50
gcloud/beta/alloydb/clusters/create
View file

@ -5,6 +5,10 @@ NAME
SYNOPSIS
gcloud beta alloydb clusters create CLUSTER --password=PASSWORD
--region=REGION [--async] [--network=NETWORK]
[--continuous-backup-recovery-window-days=RECOVERY_PERIOD
--enable-continuous-backup
[--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY
: --continuous-backup-encryption-key-keyring=CONTINUOUS_BACKUP_ENCRYPTION_KEY_KEYRING --continuous-backup-encryption-key-location=CONTINUOUS_BACKUP_ENCRYPTION_KEY_LOCATION --continuous-backup-encryption-key-project=CONTINUOUS_BACKUP_ENCRYPTION_KEY_PROJECT]]
[--disable-automated-backup
| [--automated-backup-days-of-week=[DAYS_OF_WEEK,...]
--automated-backup-start-times=[START_TIMES,...]
@ -48,6 +52,52 @@ OPTIONAL FLAGS
network, 'testsharednetwork', this would be of the
form:--network=projects/testproject/global/networks/testsharednetwork
Continuous Backup configuration.
--continuous-backup-recovery-window-days=RECOVERY_PERIOD
Recovery window of the log files and backups saved to support
Continuous Backups.
--enable-continuous-backup
Enables Continuous Backups on the cluster.
Key resource - The Cloud KMS (Key Management Service) cryptokey that
will be used to protect the continuous backup. The 'AlloyDB Service
Agent's service account must hold permission 'Cloud KMS CryptoKey
Encrypter/Decrypter'. The arguments in this group can be used to specify
the attributes of this resource.
--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY
ID of the key or fully qualified identifier for the key. To set the
kms-key attribute:
▫ provide the argument --continuous-backup-encryption-key on the
command line.
This flag argument must be specified if any of the other arguments
in this group are specified.
--continuous-backup-encryption-key-keyring=CONTINUOUS_BACKUP_ENCRYPTION_KEY_KEYRING
The KMS keyring of the key. To set the kms-keyring attribute:
▫ provide the argument --continuous-backup-encryption-key on the
command line with a fully specified name;
▫ provide the argument --continuous-backup-encryption-key-keyring
on the command line.
--continuous-backup-encryption-key-location=CONTINUOUS_BACKUP_ENCRYPTION_KEY_LOCATION
The Cloud location for the key. To set the kms-location attribute:
▫ provide the argument --continuous-backup-encryption-key on the
command line with a fully specified name;
▫ provide the argument
--continuous-backup-encryption-key-location on the command line.
--continuous-backup-encryption-key-project=CONTINUOUS_BACKUP_ENCRYPTION_KEY_PROJECT
The Cloud project for the key. To set the kms-project attribute:
▫ provide the argument --continuous-backup-encryption-key on the
command line with a fully specified name;
▫ provide the argument --continuous-backup-encryption-key-project
on the command line;
▫ set the property core/project.
Automated backup policy. If unspecified, automated backups are enabled.
At most one of these can be specified:

39
gcloud/beta/alloydb/clusters/restore
View file

@ -3,8 +3,10 @@ NAME
given backup
SYNOPSIS
gcloud beta alloydb clusters restore CLUSTER --region=REGION
--backup=BACKUP [--async] [--network=NETWORK]
gcloud beta alloydb clusters restore CLUSTER --region=REGION [--async]
[--network=NETWORK]
[--backup=BACKUP
: --point-in-time=POINT_IN_TIME --source-cluster=SOURCE_CLUSTER]
[--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
--kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
[GCLOUD_WIDE_FLAG ...]
@ -28,15 +30,6 @@ REQUIRED FLAGS
regions at https://cloud.google.com/sql/docs/instance-locations.
OPTIONAL FLAGS
RestoreCluster source types.
At most one of these can be specified:
Restore a cluster using a specific backup as the source.
--backup=BACKUP
AlloyDB backup ID
--async
Return immediately, without waiting for the operation in progress to
complete.
@ -48,6 +41,30 @@ OPTIONAL FLAGS
network, 'testsharednetwork', this would be of the
form:--network=projects/testproject/global/networks/testsharednetwork
RestoreCluster source types.
At most one of these can be specified:
Restore a cluster using a specific backup as the source.
--backup=BACKUP
AlloyDB backup ID
Restore a cluster from a source cluster at a given point in time.
--point-in-time=POINT_IN_TIME
Point in time to restore to, in RFC 3339 format. For example,
2012-11-15T16:19:00.094Z.
This flag argument must be specified if any of the other arguments
in this group are specified.
--source-cluster=SOURCE_CLUSTER
Source cluster name.
This flag argument must be specified if any of the other arguments
in this group are specified.
Key resource - The Cloud KMS (Key Management Service) cryptokey that will
be used to protect the cluster. The 'AlloyDB Service Agent' service
account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'.

50
gcloud/beta/alloydb/clusters/update
View file

@ -10,6 +10,10 @@ SYNOPSIS
: --automated-backup-window=TIMEOUT_PERIOD
[--automated-backup-encryption-key=AUTOMATED_BACKUP_ENCRYPTION_KEY
: --automated-backup-encryption-key-keyring=AUTOMATED_BACKUP_ENCRYPTION_KEY_KEYRING --automated-backup-encryption-key-location=AUTOMATED_BACKUP_ENCRYPTION_KEY_LOCATION --automated-backup-encryption-key-project=AUTOMATED_BACKUP_ENCRYPTION_KEY_PROJECT] --automated-backup-retention-count=RETENTION_COUNT | --automated-backup-retention-period=RETENTION_PERIOD]]
[--continuous-backup-recovery-window-days=RECOVERY_PERIOD
--enable-continuous-backup
[--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY
: --continuous-backup-encryption-key-keyring=CONTINUOUS_BACKUP_ENCRYPTION_KEY_KEYRING --continuous-backup-encryption-key-location=CONTINUOUS_BACKUP_ENCRYPTION_KEY_LOCATION --continuous-backup-encryption-key-project=CONTINUOUS_BACKUP_ENCRYPTION_KEY_PROJECT]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -126,6 +130,52 @@ OPTIONAL FLAGS
Retention period of the backup relative to creation time. See $
gcloud topic datetimes for information on duration formats.
Continuous Backup configuration.
--continuous-backup-recovery-window-days=RECOVERY_PERIOD
Recovery window of the log files and backups saved to support
Continuous Backups.
--enable-continuous-backup
Enables Continuous Backups on the cluster.
Key resource - The Cloud KMS (Key Management Service) cryptokey that
will be used to protect the continuous backup. The 'AlloyDB Service
Agent's service account must hold permission 'Cloud KMS CryptoKey
Encrypter/Decrypter'. The arguments in this group can be used to specify
the attributes of this resource.
--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY
ID of the key or fully qualified identifier for the key. To set the
kms-key attribute:
▫ provide the argument --continuous-backup-encryption-key on the
command line.
This flag argument must be specified if any of the other arguments
in this group are specified.
--continuous-backup-encryption-key-keyring=CONTINUOUS_BACKUP_ENCRYPTION_KEY_KEYRING
The KMS keyring of the key. To set the kms-keyring attribute:
▫ provide the argument --continuous-backup-encryption-key on the
command line with a fully specified name;
▫ provide the argument --continuous-backup-encryption-key-keyring
on the command line.
--continuous-backup-encryption-key-location=CONTINUOUS_BACKUP_ENCRYPTION_KEY_LOCATION
The Cloud location for the key. To set the kms-location attribute:
▫ provide the argument --continuous-backup-encryption-key on the
command line with a fully specified name;
▫ provide the argument
--continuous-backup-encryption-key-location on the command line.
--continuous-backup-encryption-key-project=CONTINUOUS_BACKUP_ENCRYPTION_KEY_PROJECT
The Cloud project for the key. To set the kms-project attribute:
▫ provide the argument --continuous-backup-encryption-key on the
command line with a fully specified name;
▫ provide the argument --continuous-backup-encryption-key-project
on the command line;
▫ set the property core/project.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

3
gcloud/beta/app/instances/help
View file

@ -42,7 +42,8 @@ COMMANDS
project.
scp
(BETA) SCP from or to the VM of an App Engine Flexible instance.
(BETA) SCP from or to the VM of an App Engine Flexible environment
instance.
ssh
(BETA) SSH into the VM of an App Engine Flexible instance.

13
gcloud/beta/app/instances/scp
View file

@ -1,15 +1,15 @@
NAME
gcloud beta app instances scp - SCP from or to the VM of an App Engine
Flexible instance
Flexible environment instance
SYNOPSIS
gcloud beta app instances scp [INSTANCE:]SRC [[INSTANCE:]SRC ...]
[INSTANCE:]DEST [--compress] [--recurse] [--service=SERVICE]
[--version=VERSION] [GCLOUD_WIDE_FLAG ...]
[--tunnel-through-iap] [--version=VERSION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta app instances scp lets you remotely copy files to or
from an App Engine Flexible instance.
from an App Engine Flexible environment instance.
gcloud beta app instances scp resolves the instance's IP address and
pre-populates the VM with a public key managed by gcloud. If the gcloud
@ -54,6 +54,13 @@ FLAGS
--service=SERVICE
The service ID.
--tunnel-through-iap
Tunnel the ssh connection through Identity-Aware Proxy for TCP
forwarding.
To learn more, see the IAP for TCP forwarding documentation
(https://cloud.google.com/iap/docs/tcp-forwarding-overview).
--version=VERSION
The version ID.

2
gcloud/beta/app/instances/ssh
View file

@ -60,7 +60,7 @@ FLAGS
The service ID.
--tunnel-through-iap
Tunnel the ssh connection through Cloud Identity-Aware Proxy for TCP
Tunnel the ssh connection through Identity-Aware Proxy for TCP
forwarding.
To learn more, see the IAP for TCP forwarding documentation

11
gcloud/beta/compute/commitments/create
View file

@ -173,8 +173,7 @@ OPTIONAL FLAGS
--maintenance-interval=MAINTENANCE_INTERVAL
Specifies how infrastructure upgrades should be applied to the
VM. MAINTENANCE_INTERVAL must be (currently only one value is
supported):
VM. MAINTENANCE_INTERVAL must be one of:
PERIODIC
VMs receive infrastructure and hypervisor updates on a
@ -182,6 +181,14 @@ OPTIONAL FLAGS
operations (live migrations or terminations) on an individual
VM. Security updates will still be applied as soon as they
are available.
RECURRENT
VMs receive infrastructure and hypervisor updates on a
periodic basis, minimizing the number of maintenance
operations (live migrations or terminations) on an individual
VM. This may mean a VM will take longer to receive an update
than if it was configured for AS_NEEDED. Security updates
will still be applied as soonas they are available. RECURRENT
is used for GEN3 and Sliceof Hardware VMs.
--min-cpu-platform=MIN_CPU_PLATFORM
Optional minimum CPU platform of the reservation to create.

12
gcloud/beta/compute/forwarding-rules/create
View file

@ -14,9 +14,10 @@ SYNOPSIS
| --target-ssl-proxy=TARGET_SSL_PROXY
| --target-tcp-proxy=TARGET_TCP_PROXY
| --target-vpn-gateway=TARGET_VPN_GATEWAY) [--address=ADDRESS]
[--allow-global-access] [--description=DESCRIPTION]
[--disable-automate-dns-zone] [--ip-protocol=IP_PROTOCOL]
[--ip-version=IP_VERSION] [--is-mirroring-collector]
[--allow-global-access] [--allow-psc-global-access]
[--description=DESCRIPTION] [--disable-automate-dns-zone]
[--ip-protocol=IP_PROTOCOL] [--ip-version=IP_VERSION]
[--is-mirroring-collector]
[--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--network=NETWORK]
[--network-tier=NETWORK_TIER]
[--service-directory-registration=SERVICE_DIRECTORY_REGISTRATION]
@ -199,6 +200,11 @@ OPTIONAL FLAGS
forwarding rules of type INTERNAL, the target must be either a backend
service or a target instance.
--allow-psc-global-access
If specified, clients from all regions can access this Private Service
Connect forwarding rule. This can only be specified if the forwarding
rule's target is a service attachment (--target-service-attachment).
--description=DESCRIPTION
Optional textual description for the forwarding rule.

7
gcloud/beta/compute/forwarding-rules/update
View file

@ -4,7 +4,7 @@ NAME
SYNOPSIS
gcloud beta compute forwarding-rules update NAME [--allow-global-access]
[--source-ip-ranges=SOURCE_IP_RANGE,[...]]
[--allow-psc-global-access] [--source-ip-ranges=SOURCE_IP_RANGE,[...]]
[--update-labels=[KEY=VALUE,...]]
[--clear-labels | --remove-labels=[KEY,...]]
[--global | --region=REGION] [GCLOUD_WIDE_FLAG ...]
@ -47,6 +47,11 @@ FLAGS
forwarding rules of type INTERNAL, the target must be either a backend
service or a target instance.
--allow-psc-global-access
If specified, clients from all regions can access this Private Service
Connect forwarding rule. This can only be specified if the forwarding
rule's target is a service attachment (--target-service-attachment).
--source-ip-ranges=SOURCE_IP_RANGE,[...]
List of comma-separated IP addresses or IP ranges. If not empty, this
Forwarding Rule will only forward the traffic when the source IP

18
gcloud/beta/compute/instance-groups/managed/create
View file

@ -29,14 +29,16 @@ DESCRIPTION
(BETA) gcloud beta compute instance-groups managed create creates a Compute
Engine managed instance group.
For example, running:
EXAMPLES
Running:
$ gcloud beta compute instance-groups managed create \
example-managed-instance-group --zone us-central1-a \
--template example-instance-template --size 1
example-managed-instance-group --zone=us-central1-a \
--template=example-global-instance-template --size=1
will create one managed instance group called
'example-managed-instance-group' in the us-central1-a zone.
'example-managed-instance-group' in the us-central1-a zone with global
instance template resource: 'example-global-instance-template'.
POSITIONAL ARGUMENTS
NAME
@ -44,16 +46,16 @@ POSITIONAL ARGUMENTS
REQUIRED FLAGS
--size=SIZE
The initial number of instances you want in this group.
Initial number of instances you want in this group.
--template=TEMPLATE
Specifies the instance template to use when creating new instances.
OPTIONAL FLAGS
--base-instance-name=BASE_INSTANCE_NAME
The base name to use for the Compute Engine instances that will be
created with the managed instance group. If not provided base instance
name will be the prefix of instance group name.
Base name to use for the Compute Engine instances that will be created
with the managed instance group. If not provided base instance name
will be the prefix of instance group name.
--description=DESCRIPTION
An optional description for this group.

4
gcloud/beta/compute/instances/bulk/create
View file

@ -443,8 +443,8 @@ OPTIONAL FLAGS
Policy for which zones to include or exclude during bulk instance
creation within a region. Policy is defined as a list of key-value
pairs, with the key being the zone name, and value being the applied
policy. Available policies are allow and deny. Default for zones left
unspecified is allow.
policy. Available policies are allow and deny. Default for zones if
left unspecified is allow.
Example:

13
gcloud/beta/compute/resource-policies/create-snapshot-schedule
View file

@ -39,17 +39,20 @@ REQUIRED FLAGS
Exactly one of these must be specified:
From file:
Using a file:
--weekly-schedule-from-file=WEEKLY_CYCLE_FROM_FILE
A JSON/YAML file which specifies a weekly schedule. It should be a
list of objects with the following fields:
A JSON/YAML file which specifies a weekly schedule. The file should
contain the following fields:
day: Day of the week with the same choices as --weekly-schedule.
startTime: Start time of the snapshot schedule with the same format
as --start-time.
From flags:
For more information about using a file, see
https://cloud.google.com/compute/docs/disks/scheduled-snapshots#create_snapshot_schedule
Using command flags:
--start-time=START_TIME
Start time for the disk snapshot schedule. See $ gcloud topic
@ -120,7 +123,7 @@ OPTIONAL FLAGS
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
These will be added to the disk snapshots on creation.
The label is added to each snapshot created by the schedule.
--storage-location=LOCATION
Google Cloud Storage location, either regional or multi-regional,

13
gcloud/beta/compute/resource-policies/create/snapshot-schedule
View file

@ -37,17 +37,20 @@ REQUIRED FLAGS
Exactly one of these must be specified:
From file:
Using a file:
--weekly-schedule-from-file=WEEKLY_CYCLE_FROM_FILE
A JSON/YAML file which specifies a weekly schedule. It should be a
list of objects with the following fields:
A JSON/YAML file which specifies a weekly schedule. The file should
contain the following fields:
day: Day of the week with the same choices as --weekly-schedule.
startTime: Start time of the snapshot schedule with the same format
as --start-time.
From flags:
For more information about using a file, see
https://cloud.google.com/compute/docs/disks/scheduled-snapshots#create_snapshot_schedule
Using command flags:
--start-time=START_TIME
Start time for the disk snapshot schedule in UTC. For example,
@ -118,7 +121,7 @@ OPTIONAL FLAGS
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
These will be added to the disk snapshots on creation.
The label is added to each snapshot created by the schedule.
--storage-location=LOCATION
Google Cloud Storage location, either regional or multi-regional,

3
gcloud/beta/compute/resource-policies/help
View file

@ -27,6 +27,9 @@ GROUPS
create
(BETA) Create Compute Engine Resource Policies.
update
(BETA) Update Compute Engine Resource Policies.
COMMANDS
COMMAND is one of the following:

27
gcloud/beta/compute/resource-policies/update/help Normal file
View file

@ -0,0 +1,27 @@
NAME
gcloud beta compute resource-policies update - update Compute Engine
Resource Policies
SYNOPSIS
gcloud beta compute resource-policies update COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update Compute Engine Resource Policies.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
snapshot-schedule
(BETA) Update a Compute Engine Snapshot Schedule Resource Policy.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha compute resource-policies update

114
gcloud/beta/compute/resource-policies/update/snapshot-schedule Normal file
View file

@ -0,0 +1,114 @@
NAME
gcloud beta compute resource-policies update snapshot-schedule - update a
Compute Engine Snapshot Schedule Resource Policy
SYNOPSIS
gcloud beta compute resource-policies update snapshot-schedule NAME
[--description=DESCRIPTION] [--region=REGION]
[--snapshot-labels=[KEY=VALUE,...]]
[--weekly-schedule-from-file=WEEKLY_CYCLE_FROM_FILE
| --start-time=START_TIME (--daily-schedule | --hourly-schedule=HOURS
| --weekly-schedule=WEEKLY_CYCLE)] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update a Compute Engine Snapshot Schedule Resource Policy.
EXAMPLES
The following command updates a Compute Engine Snapshot Schedule Resource
Policy to take a daily snapshot taken at 13:00 UTC
$ gcloud beta compute resource-policies update snapshot-schedule \
my-resource-policy --region=REGION --start-time=13:00 \
--daily-schedule
POSITIONAL ARGUMENTS
NAME
Name of the resource policy to operate on.
FLAGS
--description=DESCRIPTION
An optional, textual description for the backend.
--region=REGION
Region of the resource policy to operate on. If not specified, you
might be prompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/region property:
$ gcloud config set compute/region REGION
A list of regions can be fetched by running:
$ gcloud compute regions list
To unset the property, run:
$ gcloud config unset compute/region
Alternatively, the region can be stored in the environment variable
CLOUDSDK_COMPUTE_REGION.
--snapshot-labels=[KEY=VALUE,...]
List of label KEY=VALUE pairs to add.
Keys must start with a lowercase character and contain only hyphens
(-), underscores (_), lowercase characters, and numbers. Values must
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
The label is added to each snapshot created by the schedule.
Cycle Frequency Group.
At most one of these can be specified:
Using a file:
--weekly-schedule-from-file=WEEKLY_CYCLE_FROM_FILE
A JSON/YAML file which specifies a weekly schedule. The file should
contain the following fields:
day: Day of the week with the same choices as --weekly-schedule.
startTime: Start time of the snapshot schedule with the same format
as --start-time.
For more information about using a file, see
https://cloud.google.com/compute/docs/disks/scheduled-snapshots#create_snapshot_schedule
Using command flags:
--start-time=START_TIME
Start time for the disk snapshot schedule in UTC. For example,
--start-time="15:00".
This flag argument must be specified if any of the other arguments
in this group are specified.
Exactly one of these must be specified:
--daily-schedule
Snapshot schedule starts daily at START_TIME.
--hourly-schedule=HOURS
Snapshot schedule occurs every n hours starting at START_TIME.
--weekly-schedule=WEEKLY_CYCLE
Snapshot schedule occurs weekly on WEEKLY_SCHEDULE at START_TIME.
WEEKLY_CYCLE must be one of: monday, tuesday, wednesday,
thursday, friday, saturday, sunday.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha compute resource-policies update snapshot-schedule

8
gcloud/beta/config/get
View file

@ -648,6 +648,14 @@ AVAILABLE PROPERTIES
SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service
account and SERVICE_ACCOUNT_2 is the delegate.
service_account_disable_id_token_refresh
If True, disable ID token refresh for service account.
service_account_use_self_signed_jwt
If True, use self signed jwt flow to get service account
credentials access token. This only applies to service account json
file and not to the legacy .p12 file.
token_host
Overrides the token endpoint to provision access tokens. It can be
used with Private Service Connect.

8
gcloud/beta/config/help
View file

@ -680,6 +680,14 @@ AVAILABLE PROPERTIES
SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service
account and SERVICE_ACCOUNT_2 is the delegate.
service_account_disable_id_token_refresh
If True, disable ID token refresh for service account.
service_account_use_self_signed_jwt
If True, use self signed jwt flow to get service account
credentials access token. This only applies to service account json
file and not to the legacy .p12 file.
token_host
Overrides the token endpoint to provision access tokens. It can be
used with Private Service Connect.

8
gcloud/beta/config/list
View file

@ -692,6 +692,14 @@ AVAILABLE PROPERTIES
SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service
account and SERVICE_ACCOUNT_2 is the delegate.
service_account_disable_id_token_refresh
If True, disable ID token refresh for service account.
service_account_use_self_signed_jwt
If True, use self signed jwt flow to get service account
credentials access token. This only applies to service account json
file and not to the legacy .p12 file.
token_host
Overrides the token endpoint to provision access tokens. It can be
used with Private Service Connect.

8
gcloud/beta/config/set
View file

@ -695,6 +695,14 @@ AVAILABLE PROPERTIES
SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service
account and SERVICE_ACCOUNT_2 is the delegate.
service_account_disable_id_token_refresh
If True, disable ID token refresh for service account.
service_account_use_self_signed_jwt
If True, use self signed jwt flow to get service account
credentials access token. This only applies to service account json
file and not to the legacy .p12 file.
token_host
Overrides the token endpoint to provision access tokens. It can be
used with Private Service Connect.

8
gcloud/beta/config/unset
View file

@ -656,6 +656,14 @@ AVAILABLE PROPERTIES
SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service
account and SERVICE_ACCOUNT_2 is the delegate.
service_account_disable_id_token_refresh
If True, disable ID token refresh for service account.
service_account_use_self_signed_jwt
If True, use self signed jwt flow to get service account
credentials access token. This only applies to service account json
file and not to the legacy .p12 file.
token_host
Overrides the token endpoint to provision access tokens. It can be
used with Private Service Connect.

11
gcloud/beta/container/fleet/identity-service/delete
View file

@ -4,6 +4,7 @@ NAME
SYNOPSIS
gcloud beta container fleet identity-service delete
[--fleet-default-member-config]
[--membership=MEMBERSHIP : --location=LOCATION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -16,6 +17,16 @@ EXAMPLES
--membership=MEMBERSHIP_NAME
FLAGS
--fleet-default-member-config
If specified, deletes the default membership configuration present in
your fleet.
To delete the default membership configuration present in your
fleet, run:
$ gcloud beta container fleet identity-service delete \
--fleet-default-member-config
Membership resource - The group of arguments defining a membership. The
arguments in this group can be used to specify the attributes of this
resource. (NOTE) Some attributes are not given arguments in this group but

18
gcloud/beta/container/fleet/identity-service/enable
View file

@ -3,7 +3,9 @@ NAME
Service Feature
SYNOPSIS
gcloud beta container fleet identity-service enable [GCLOUD_WIDE_FLAG ...]
gcloud beta container fleet identity-service enable
[--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) This command enables the Identity Service Feature in a fleet.
@ -13,6 +15,20 @@ EXAMPLES
$ gcloud beta container fleet identity-service enable
FLAGS
--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG
The path to an identity-service.yaml identity configuration file. If
specified, this configuration would be the default Identity Service
configuration for all memberships in your fleet. It could be overridden
with a membership-specific configuration by using the the Apply command
with the --config argument.
To enable the Identity Service Feature with a fleet-level default
membership configuration, run:
$ gcloud beta container fleet identity-service enable \
--fleet-default-member-config=/path/to/identity-service.yaml
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

11
gcloud/beta/container/hub/identity-service/delete
View file

@ -4,6 +4,7 @@ NAME
SYNOPSIS
gcloud beta container hub identity-service delete
[--fleet-default-member-config]
[--membership=MEMBERSHIP : --location=LOCATION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -16,6 +17,16 @@ EXAMPLES
--membership=MEMBERSHIP_NAME
FLAGS
--fleet-default-member-config
If specified, deletes the default membership configuration present in
your fleet.
To delete the default membership configuration present in your
fleet, run:
$ gcloud beta container hub identity-service delete \
--fleet-default-member-config
Membership resource - The group of arguments defining a membership. The
arguments in this group can be used to specify the attributes of this
resource. (NOTE) Some attributes are not given arguments in this group but

18
gcloud/beta/container/hub/identity-service/enable
View file

@ -3,7 +3,9 @@ NAME
Feature
SYNOPSIS
gcloud beta container hub identity-service enable [GCLOUD_WIDE_FLAG ...]
gcloud beta container hub identity-service enable
[--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) This command enables the Identity Service Feature in a fleet.
@ -13,6 +15,20 @@ EXAMPLES
$ gcloud beta container hub identity-service enable
FLAGS
--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG
The path to an identity-service.yaml identity configuration file. If
specified, this configuration would be the default Identity Service
configuration for all memberships in your fleet. It could be overridden
with a membership-specific configuration by using the the Apply command
with the --config argument.
To enable the Identity Service Feature with a fleet-level default
membership configuration, run:
$ gcloud beta container hub identity-service enable \
--fleet-default-member-config=/path/to/identity-service.yaml
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

15
gcloud/beta/filestore/instances/create
View file

@ -9,8 +9,8 @@ SYNOPSIS
--network=[connect-mode=CONNECT-MODE],
[name=NAME],[reserved-ip-range=RESERVED-IP-RANGE] [--async]
[--description=DESCRIPTION] [--labels=[KEY=VALUE,...]]
[--location=LOCATION] [--region=REGION]
[--tier=TIER; default="BASIC_HDD"]
[--location=LOCATION] [--protocol=PROTOCOL; default="NFS_V3"]
[--region=REGION] [--tier=TIER; default="BASIC_HDD"]
[--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
--kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
[GCLOUD_WIDE_FLAG ...]
@ -23,7 +23,7 @@ EXAMPLES
volume.
$ gcloud beta filestore instances create NAME \
--description=DESCRIPTION --tier=TIER \
--description=DESCRIPTION --tier=TIER --protocol=PROTOCOL \
--file-share=name=VOLUME_NAME,capacity=CAPACITY \
--network=name=NETWORK_NAME,\
reserved-ip-range=RESERVED_IP_RANGE,connect-mode=CONNECT_MODE \
@ -195,6 +195,15 @@ OPTIONAL FLAGS
--location=LOCATION
Location of the Cloud Filestore instance/operation.
--protocol=PROTOCOL; default="NFS_V3"
The service protocol for the Cloud Filestore instance. PROTOCOL must be
one of:
nfs-v3
NFSv3 protocol.
nfs-v4-1
NFSv4.1 protocol.
--region=REGION
Region of the Cloud Filestore instance.

3
gcloud/beta/run/jobs/help
View file

@ -30,6 +30,9 @@ GROUPS
executions
(BETA) View and manage your Cloud Run jobs executions.
logs
(BETA) Read logs for Cloud Run jobs.
COMMANDS
COMMAND is one of the following:

43
gcloud/beta/run/jobs/logs/help Normal file
View file

@ -0,0 +1,43 @@
NAME
gcloud beta run jobs logs - read logs for Cloud Run jobs
SYNOPSIS
gcloud beta run jobs logs COMMAND [--region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Read logs for Cloud Run jobs.
EXAMPLES
To tail logs executions for a job, run:
$ gcloud beta run jobs logs tail my-job
To read logs executions for a job, run:
$ gcloud beta run jobs logs read my-job
FLAGS
--region=REGION
Region in which the resource can be found. Alternatively, set the
property [run/region].
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
read
(BETA) Read logs for Cloud Run jobs.
tail
(BETA) Tail logs for Cloud Run jobs.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha run jobs logs

82
gcloud/beta/run/jobs/logs/read Normal file
View file

@ -0,0 +1,82 @@
NAME
gcloud beta run jobs logs read - read logs for Cloud Run jobs
SYNOPSIS
gcloud beta run jobs logs read JOB [--freshness=FRESHNESS; default="1d"]
[--log-filter=LOG_FILTER] [--order=ORDER; default="desc"]
[--region=REGION] [--limit=LIMIT] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta run jobs logs read reads log entries. Log entries
matching --log-filter are returned according to the specified --order. If
the log entries come from multiple logs, then entries from different logs
might be intermingled in the results.
EXAMPLES
To read log entries from for a Cloud Run job, run:
$ gcloud beta run jobs logs read my-job
To read log entries with severity ERROR or higher, run:
$ gcloud beta run jobs logs read my-job \
--log-filter="severity>=ERROR"
To read log entries written in a specific time window, run:
$ gcloud beta run jobs logs read my-job \
--log-filter='timestamp<="2015-05-31T23:59:59Z" AND
timestamp>="2015-05-31T00:00:00Z"'
To read up to 10 log entries in your job payloads that include the word
SearchText and format the output in JSON format, run:
$ gcloud beta run jobs logs read my-job \
--log-filter="textPayload:SearchText" --limit=10 --format=json
Detailed information about filters can be found at:
https://cloud.google.com/logging/docs/view/advanced_filters
POSITIONAL ARGUMENTS
JOB
Name for a Cloud Run job.
FLAGS
--freshness=FRESHNESS; default="1d"
Return entries that are not older than this value. Works only with DESC
ordering and filters without a timestamp. See $ gcloud topic datetimes
for information on duration formats.
--log-filter=LOG_FILTER
Filter expression that specifies the log entries to return. Detailed
information about filters can be found at:
https://cloud.google.com/logging/docs/view/logging-query-language
--order=ORDER; default="desc"
Ordering of returned log entries based on timestamp field. ORDER must
be one of: desc, asc.
--region=REGION
Region in which the resource can be found. Alternatively, set the
property [run/region].
LIST COMMAND FLAGS
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha run jobs logs read

53
gcloud/beta/run/jobs/logs/tail Normal file
View file

@ -0,0 +1,53 @@
NAME
gcloud beta run jobs logs tail - tail logs for Cloud Run jobs
SYNOPSIS
gcloud beta run jobs logs tail JOB [--log-filter=LOG_FILTER]
[--region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta run jobs logs tail tails log-entries for a particular
Cloud Run job in real time. The log entries are formatted for consumption
in a terminal.
EXAMPLES
To tail log entries for a Cloud Run job, run:
$ gcloud beta run jobs logs tail my-job
To tail log entries with severity ERROR or higher, run:
$ gcloud beta run jobs logs tail my-job \
--log-filter="severity>=ERROR"
Detailed information about filters can be found at:
https://cloud.google.com/logging/docs/view/advanced_filters
POSITIONAL ARGUMENTS
JOB
Name for a Cloud Run job.
FLAGS
--log-filter=LOG_FILTER
Filter expression that specifies the log entries to return. Detailed
information about filters can be found at:
https://cloud.google.com/logging/docs/view/logging-query-language
--region=REGION
Region in which the resource can be found. Alternatively, set the
property [run/region].
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha run jobs logs tail

2
gcloud/beta/run/revisions/help
View file

@ -102,7 +102,7 @@ GROUPS
GROUP is one of the following:
logs
(BETA) Read logs for Cloud Run (fully managed) revisions.
(BETA) Read logs for Cloud Run revisions.
COMMANDS
COMMAND is one of the following:

9
gcloud/beta/run/revisions/logs/help
View file

@ -1,6 +1,5 @@
NAME
gcloud beta run revisions logs - read logs for Cloud Run (fully managed)
revisions
gcloud beta run revisions logs - read logs for Cloud Run revisions
SYNOPSIS
gcloud beta run revisions logs COMMAND
@ -10,7 +9,7 @@ SYNOPSIS
| --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Read logs for Cloud Run (fully managed) revisions.
(BETA) Read logs for Cloud Run revisions.
FLAGS
--platform=PLATFORM; default="managed"
@ -97,10 +96,10 @@ COMMANDS
COMMAND is one of the following:
read
(BETA) Read logs for a revision.
(BETA) Read logs for a Cloud Run revision.
tail
(BETA) Tail logs for a revision.
(BETA) Tail logs for a Cloud Run revision.
NOTES
This command is currently in beta and might change without notice. This

2
gcloud/beta/run/revisions/logs/read
View file

@ -1,5 +1,5 @@
NAME
gcloud beta run revisions logs read - read logs for a revision
gcloud beta run revisions logs read - read logs for a Cloud Run revision
SYNOPSIS
gcloud beta run revisions logs read REVISION

2
gcloud/beta/run/revisions/logs/tail
View file

@ -1,5 +1,5 @@
NAME
gcloud beta run revisions logs tail - tail logs for a revision
gcloud beta run revisions logs tail - tail logs for a Cloud Run revision
SYNOPSIS
gcloud beta run revisions logs tail REVISION [--log-filter=LOG_FILTER]

2
gcloud/beta/run/services/help
View file

@ -104,7 +104,7 @@ GROUPS
GROUP is one of the following:
logs
(BETA) Read logs for Cloud Run (fully managed) services.
(BETA) Read logs for Cloud Run services.
COMMANDS
COMMAND is one of the following:

9
gcloud/beta/run/services/logs/help
View file

@ -1,6 +1,5 @@
NAME
gcloud beta run services logs - read logs for Cloud Run (fully managed)
services
gcloud beta run services logs - read logs for Cloud Run services
SYNOPSIS
gcloud beta run services logs COMMAND
@ -10,7 +9,7 @@ SYNOPSIS
| --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Read logs for Cloud Run (fully managed) services.
(BETA) Read logs for Cloud Run services.
FLAGS
--platform=PLATFORM; default="managed"
@ -97,10 +96,10 @@ COMMANDS
COMMAND is one of the following:
read
(BETA) Read logs for a service.
(BETA) Read logs for a Cloud Run service.
tail
(BETA) Tail logs for a service.
(BETA) Tail logs for a Cloud Run service.
NOTES
This command is currently in beta and might change without notice. This

2
gcloud/beta/run/services/logs/read
View file

@ -1,5 +1,5 @@
NAME
gcloud beta run services logs read - read logs for a service
gcloud beta run services logs read - read logs for a Cloud Run service
SYNOPSIS
gcloud beta run services logs read SERVICE

2
gcloud/beta/run/services/logs/tail
View file

@ -1,5 +1,5 @@
NAME
gcloud beta run services logs tail - tail logs for a service
gcloud beta run services logs tail - tail logs for a Cloud Run service
SYNOPSIS
gcloud beta run services logs tail SERVICE [--log-filter=LOG_FILTER]

6
gcloud/beta/sql/users/describe
View file

@ -43,8 +43,10 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud sql users describe
$ gcloud alpha sql users describe