diff --git a/gcloud/_version b/gcloud/_version index bcd0fef21..c5c9aa100 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 433.0.1 -alpha 2023.06.01 -beta 2023.06.01 +Google Cloud SDK 434.0.0 +alpha 2023.06.02 +beta 2023.06.02 bq 2.0.93 bundled-python3-unix 3.9.16 -core 2023.06.01 +core 2023.06.02 gcloud-crc32c 1.0.0 gsutil 5.24 diff --git a/gcloud/alloydb/clusters/create b/gcloud/alloydb/clusters/create index 507f69a87..521fb4c37 100644 --- a/gcloud/alloydb/clusters/create +++ b/gcloud/alloydb/clusters/create @@ -5,6 +5,10 @@ NAME SYNOPSIS gcloud 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,59 @@ 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 Google 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 Google 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: diff --git a/gcloud/alloydb/clusters/help b/gcloud/alloydb/clusters/help index df24069b5..b57dc181a 100644 --- a/gcloud/alloydb/clusters/help +++ b/gcloud/alloydb/clusters/help @@ -35,7 +35,8 @@ COMMANDS Promote an AlloyDB SECONDARY cluster in a given project and region. restore - Restore an AlloyDB cluster from a given backup. + Restore an AlloyDB cluster from a given backup or a source cluster and + a timestamp. update Update an AlloyDB cluster within a given project and region. diff --git a/gcloud/alloydb/clusters/restore b/gcloud/alloydb/clusters/restore index 045fb3a55..1fef89cae 100644 --- a/gcloud/alloydb/clusters/restore +++ b/gcloud/alloydb/clusters/restore @@ -1,16 +1,19 @@ NAME gcloud alloydb clusters restore - restore an AlloyDB cluster from a given - backup + backup or a source cluster and a timestamp SYNOPSIS - gcloud alloydb clusters restore CLUSTER --backup=BACKUP --region=REGION + gcloud alloydb clusters restore CLUSTER --region=REGION + (--backup=BACKUP + | --point-in-time=POINT_IN_TIME --source-cluster=SOURCE_CLUSTER) [--async] [--network=NETWORK] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Restore an AlloyDB cluster from a given backup. + Restore an AlloyDB cluster from a given backup or a source cluster and a + timestamp. EXAMPLES To restore a cluster from a backup, run: @@ -18,18 +21,43 @@ EXAMPLES $ gcloud alloydb clusters restore my-cluster --region=us-central1 \ --backup=my-backup + To restore a cluster from a source cluster and a timestamp, run: + + $ gcloud alloydb clusters restore my-cluster --region=us-central1 \ + --source-cluster=old-cluster \ + --point-in-time=2012-11-15T16:19:00.094Z + POSITIONAL ARGUMENTS CLUSTER AlloyDB cluster ID REQUIRED FLAGS - --backup=BACKUP - AlloyDB backup ID - --region=REGION Regional location (e.g. asia-east1, us-east1). See the full list of regions at https://cloud.google.com/sql/docs/instance-locations. + RestoreCluster source types. + + Exactly one of these must be specified: + + --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. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alloydb/clusters/update b/gcloud/alloydb/clusters/update index 9f3f763f6..a355efaf0 100644 --- a/gcloud/alloydb/clusters/update +++ b/gcloud/alloydb/clusters/update @@ -10,6 +10,9 @@ 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 --clear-continuous-backup-encryption-key + | [--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 @@ -132,6 +135,68 @@ 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. + + Encryption configuration for Continuous Backups. + + At most one of these can be specified: + + --clear-continuous-backup-encryption-key + Clears the encryption configuration for Continuous Backups. Google + default encryption will be used for future Continuous Backups. + + 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 Google 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 Google 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, diff --git a/gcloud/alpha/alloydb/clusters/help b/gcloud/alpha/alloydb/clusters/help index c14a3afda..04dc5c792 100644 --- a/gcloud/alpha/alloydb/clusters/help +++ b/gcloud/alpha/alloydb/clusters/help @@ -37,7 +37,8 @@ COMMANDS region. restore - (ALPHA) Restore an AlloyDB cluster from a given backup. + (ALPHA) Restore an AlloyDB cluster from a given backup or a source + cluster and a timestamp. update (ALPHA) Update an AlloyDB cluster within a given project and region. diff --git a/gcloud/alpha/alloydb/clusters/restore b/gcloud/alpha/alloydb/clusters/restore index f095d8605..ce4e463cf 100644 --- a/gcloud/alpha/alloydb/clusters/restore +++ b/gcloud/alpha/alloydb/clusters/restore @@ -1,18 +1,19 @@ NAME gcloud alpha alloydb clusters restore - restore an AlloyDB cluster from a - given backup + given backup or a source cluster and a timestamp SYNOPSIS - gcloud alpha alloydb clusters restore CLUSTER --region=REGION [--async] - [--network=NETWORK] - [--backup=BACKUP - | --point-in-time=POINT_IN_TIME --source-cluster=SOURCE_CLUSTER] + gcloud alpha alloydb clusters restore CLUSTER --region=REGION + (--backup=BACKUP + | --point-in-time=POINT_IN_TIME --source-cluster=SOURCE_CLUSTER) + [--async] [--network=NETWORK] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Restore an AlloyDB cluster from a given backup. + (ALPHA) Restore an AlloyDB cluster from a given backup or a source cluster + and a timestamp. EXAMPLES To restore a cluster from a backup, run: @@ -20,6 +21,12 @@ EXAMPLES $ gcloud alpha alloydb clusters restore my-cluster \ --region=us-central1 --backup=my-backup + To restore a cluster from a source cluster and a timestamp, run: + + $ gcloud alpha alloydb clusters restore my-cluster \ + --region=us-central1 --source-cluster=old-cluster \ + --point-in-time=2012-11-15T16:19:00.094Z + POSITIONAL ARGUMENTS CLUSTER AlloyDB cluster ID @@ -29,26 +36,12 @@ REQUIRED FLAGS Regional location (e.g. asia-east1, us-east1). See the full list of regions at https://cloud.google.com/sql/docs/instance-locations. -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --network=NETWORK - Network in the current project that the instance will be part of. To - specify using a network with a shared VPC, use the full URL of the - network. For an example host project, 'testproject', and shared - 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: + Exactly one of these must be specified: - Restore a cluster using a specific backup as the source. - - --backup=BACKUP - AlloyDB backup ID + --backup=BACKUP + AlloyDB backup ID Restore a cluster from a source cluster at a given point in time. @@ -65,6 +58,18 @@ OPTIONAL FLAGS This flag argument must be specified if any of the other arguments in this group are specified. +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --network=NETWORK + Network in the current project that the instance will be part of. To + specify using a network with a shared VPC, use the full URL of the + network. For an example host project, 'testproject', and shared + network, 'testsharednetwork', this would be of the + form:--network=projects/testproject/global/networks/testsharednetwork + 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'. diff --git a/gcloud/alpha/auth/help b/gcloud/alpha/auth/help index a5780a8c5..2e48b3f0f 100644 --- a/gcloud/alpha/auth/help +++ b/gcloud/alpha/auth/help @@ -14,7 +14,7 @@ DESCRIPTION the gcloud CLI (https://cloud.google.com/sdk/docs/authorizing). For information about authorizing a service account, see Authorizing with a service account - (https://cloud.google.com/sdk/docs/authorizing#authorizing_with_a_service_account). + (https://cloud.google.com/sdk/docs/authorizing#service-account). After running gcloud auth commands, you can run other commands with --account=ACCOUNT to authenticate the command with the credentials of the diff --git a/gcloud/alpha/compute/disks/create b/gcloud/alpha/compute/disks/create index 4e83dd497..a9004fe55 100644 --- a/gcloud/alpha/compute/disks/create +++ b/gcloud/alpha/compute/disks/create @@ -13,7 +13,8 @@ SYNOPSIS [--provisioned-iops=PROVISIONED_IOPS] [--provisioned-throughput=PROVISIONED_THROUGHPUT] [--replica-zones=ZONE,ZONE] [--no-require-csek-key-create] - [--resource-policies=[RESOURCE_POLICY,...]] [--size=SIZE] [--type=TYPE] + [--resource-policies=[RESOURCE_POLICY,...]] [--size=SIZE] + [--storage-pool=STORAGE_POOL] [--type=TYPE] [--user-licenses=[LICENSE,...]] [--image-family-scope=IMAGE_FAMILY_SCOPE --image-project=IMAGE_PROJECT --image=IMAGE @@ -167,6 +168,9 @@ FLAGS will be used. For details about disk size limits, refer to: https://cloud.google.com/compute/docs/disks + --storage-pool=STORAGE_POOL + Specifies the URI of the storage pool in which the disk is created. + --type=TYPE Specifies the type of disk to create. To get a list of available disk types, run gcloud compute disk-types list. The default disk type is diff --git a/gcloud/alpha/compute/disks/update b/gcloud/alpha/compute/disks/update index 06f004aad..4b7d8326f 100644 --- a/gcloud/alpha/compute/disks/update +++ b/gcloud/alpha/compute/disks/update @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha compute disks update DISK_NAME [--provisioned-iops=PROVISIONED_IOPS] - [--provisioned-throughput=PROVISIONED_THROUGHPUT] + [--provisioned-throughput=PROVISIONED_THROUGHPUT] [--size=SIZE] [--update-labels=[KEY=VALUE,...]] [--clear-architecture | --update-architecture=UPDATE_ARCHITECTURE] [--clear-labels | --remove-labels=[KEY,...]] @@ -48,6 +48,12 @@ FLAGS Provisioned throughput of disk to update. The throughput unit is MB per sec. + --size=SIZE + Size of the disks. The value must be a whole number followed by a size + unit of GB for gigabyte, or TB for terabyte. If no size unit is + specified, GB is assumed. For details about disk size limits, refer to: + https://cloud.google.com/compute/docs/disks + --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. diff --git a/gcloud/alpha/compute/images/list b/gcloud/alpha/compute/images/list index 96572ff82..e50d5da83 100644 --- a/gcloud/alpha/compute/images/list +++ b/gcloud/alpha/compute/images/list @@ -2,10 +2,11 @@ NAME gcloud alpha compute images list - list Google Compute Engine images SYNOPSIS - gcloud alpha compute images list [NAME ...] [--preview-images] - [--regexp=REGEXP, -r REGEXP] [--show-deprecated] [--no-standard-images] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + gcloud alpha compute images list [NAME ...] [--image-zone=IMAGE_ZONE] + [--preview-images] [--regexp=REGEXP, -r REGEXP] [--show-deprecated] + [--no-standard-images] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute images list displays all Google Compute Engine @@ -35,6 +36,11 @@ POSITIONAL ARGUMENTS instead. FLAGS + --image-zone=IMAGE_ZONE + Zone to query. Returns the latest image available in the image family, + for the specified zone. If not specified, returns the latest globally + available image. + --preview-images Show images that are in limited preview. The preview image projects are: (none) diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index 57d800df8..aaf826122 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -127,10 +127,8 @@ FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index 7b2cbbc16..0bd01f74c 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -122,10 +122,8 @@ FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index 1ce9ba06b..f5dcafae9 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -35,6 +35,7 @@ SYNOPSIS [--network-interface=[PROPERTY=VALUE,...]] [--network-performance-configs=[PROPERTY=VALUE,...]] [--network-tier=NETWORK_TIER] [--numa-node-count=NUMA_NODE_COUNT] + [--per-instance-hostnames=[INSTANCE_NAME=INSTANCE_HOSTNAME,...]] [--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT] [--post-key-revocation-action-type=POLICY] [--preemptible] [--provisioning-model=PROVISIONING_MODEL] @@ -170,10 +171,8 @@ OPTIONAL FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new @@ -664,6 +663,13 @@ OPTIONAL FLAGS 1, 2, 4 or 8. Setting NUMA node count to 0 means using the default setting. + --per-instance-hostnames=[INSTANCE_NAME=INSTANCE_HOSTNAME,...] + Specify the hostname of the instance to be created. The specified + hostname must be RFC1035 compliant. If hostname is not specified, the + default hostname is [INSTANCE_NAME].c.[PROJECT_ID].internal when using + the global DNS, and [INSTANCE_NAME].[ZONE].c.[PROJECT_ID].internal when + using zonal DNS. + --performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT The set of performance measurement counters to enable for the instance. PERFORMANCE_MONITORING_UNIT must be one of: diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index c97b9f564..f8fd65c3c 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -182,10 +182,8 @@ FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index 5a3a1e9d2..70ac1f225 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -133,10 +133,8 @@ FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new diff --git a/gcloud/alpha/compute/interconnects/attachments/dedicated/create b/gcloud/alpha/compute/interconnects/attachments/dedicated/create index 716e85d5b..257003336 100644 --- a/gcloud/alpha/compute/interconnects/attachments/dedicated/create +++ b/gcloud/alpha/compute/interconnects/attachments/dedicated/create @@ -61,14 +61,7 @@ OPTIONAL FLAGS 50 Gbit/s --candidate-ipv6-subnets=[IPV6_SUBNET,...] - Up to 16 candidate prefixes that control the allocation of - cloudRouterIpv6Address and customerRouterIpv6Address for this - attachment. Each prefix must be in the Global Unique Address (GUA) - space. It is highly recommended that it be in a range owned by the - requestor. A GUA in a range owned by Google will cause the request to - fail. Google will select an available prefix from the supplied - candidates or fail the request. If not supplied, a /125 from a - Google-owned GUA block will be selected. + The candididate-ipv6-subnets field is not available. --candidate-subnets=[SUBNET,...] Up to 16 candidate prefixes that can be used to restrict the allocation @@ -81,16 +74,10 @@ OPTIONAL FLAGS request fails if all candidate subnets are in use at Google's edge. --cloud-router-ipv6-interface-id=INTERFACE_ID - If supplied, the interface id (index within the subnet) to be used for - the Cloud Router address. The id must be in the range of 1 to 6. If a - subnet mask is supplied, it must be /125, and the subnet should either - be 0 or match the selected subnet. + The cloud-router-ipv6-interface-id field is not available. --customer-router-ipv6-interface-id=PEER_INTERFACE_ID - If supplied, the interface id (index within the subnet) to be used for - the Cloud Router address. The id must be in the range of 1 to 6. If a - subnet mask is supplied, it must be /125, and the subnet should either - be 0 or match the selected subnet. + The customer-router-ipv6-interface-id field is not available. --description=DESCRIPTION Human-readable plain-text description of attachment. diff --git a/gcloud/alpha/compute/interconnects/attachments/dedicated/update b/gcloud/alpha/compute/interconnects/attachments/dedicated/update index fdd2f92e7..39d7a8f38 100644 --- a/gcloud/alpha/compute/interconnects/attachments/dedicated/update +++ b/gcloud/alpha/compute/interconnects/attachments/dedicated/update @@ -52,26 +52,13 @@ FLAGS 50 Gbit/s --candidate-ipv6-subnets=[IPV6_SUBNET,...] - Up to 16 candidate prefixes that control the allocation of - cloudRouterIpv6Address and customerRouterIpv6Address for this - attachment. Each prefix must be in the Global Unique Address (GUA) - space. It is highly recommended that it be in a range owned by the - requestor. A GUA in a range owned by Google will cause the request to - fail. Google will select an available prefix from the supplied - candidates or fail the request. If not supplied, a /125 from a - Google-owned GUA block will be selected. + The candididate-ipv6-subnets field is not available. --cloud-router-ipv6-interface-id=INTERFACE_ID - If supplied, the interface id (index within the subnet) to be used for - the Cloud Router address. The id must be in the range of 1 to 6. If a - subnet mask is supplied, it must be /125, and the subnet should either - be 0 or match the selected subnet. + The cloud-router-ipv6-interface-id field is not available. --customer-router-ipv6-interface-id=PEER_INTERFACE_ID - If supplied, the interface id (index within the subnet) to be used for - the Cloud Router address. The id must be in the range of 1 to 6. If a - subnet mask is supplied, it must be /125, and the subnet should either - be 0 or match the selected subnet. + The customer-router-ipv6-interface-id field is not available. --description=DESCRIPTION Human-readable plain-text description of attachment. diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index aad9c1b2b..18f0e8ced 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -35,6 +35,7 @@ SYNOPSIS [--network-interface=[PROPERTY=VALUE,...]] [--network-performance-configs=[PROPERTY=VALUE,...]] [--network-tier=NETWORK_TIER] [--numa-node-count=NUMA_NODE_COUNT] + [--per-instance-hostnames=[INSTANCE_NAME=INSTANCE_HOSTNAME,...]] [--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT] [--post-key-revocation-action-type=POLICY] [--preemptible] [--provisioning-model=PROVISIONING_MODEL] @@ -154,10 +155,8 @@ OPTIONAL FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new @@ -637,6 +636,13 @@ OPTIONAL FLAGS 1, 2, 4 or 8. Setting NUMA node count to 0 means using the default setting. + --per-instance-hostnames=[INSTANCE_NAME=INSTANCE_HOSTNAME,...] + Specify the hostname of the instance to be created. The specified + hostname must be RFC1035 compliant. If hostname is not specified, the + default hostname is [INSTANCE_NAME].c.[PROJECT_ID].internal when using + the global DNS, and [INSTANCE_NAME].[ZONE].c.[PROJECT_ID].internal when + using zonal DNS. + --performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT The set of performance measurement counters to enable for the instance. PERFORMANCE_MONITORING_UNIT must be one of: diff --git a/gcloud/alpha/compute/scp b/gcloud/alpha/compute/scp index d84b47624..e789f4899 100644 --- a/gcloud/alpha/compute/scp +++ b/gcloud/alpha/compute/scp @@ -52,6 +52,19 @@ EXAMPLES $ gcloud alpha compute scp ~/localtest.txt ~/localtest2.txt \ example-instance:~/narnia + Remote Windows-based virtual machines require you to provide a path using + backslash notation: + + $ gcloud alpha compute scp ~/localtest.txt ~/localtest2.txt \ + example-windows-instance:"C:\Users\Public" + + Paths for remote Windows-based virtual machines which contain spaces in + directory name should be appropriately protected with a pair of nested + single and double quotes: + + $ gcloud alpha compute scp ~/localtest.txt \ + 'example-windows-instance:"C:\Users\Public\Test Folder"' + If the zone cannot be determined, you will be prompted for it. Use the --zone flag to avoid being prompted: diff --git a/gcloud/alpha/compute/target-http-proxies/create b/gcloud/alpha/compute/target-http-proxies/create index 58a6ecad1..f2626165a 100644 --- a/gcloud/alpha/compute/target-http-proxies/create +++ b/gcloud/alpha/compute/target-http-proxies/create @@ -51,11 +51,11 @@ OPTIONAL FLAGS An optional, textual description for the target HTTP proxy. --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC - Specifies how long to keep a connection open, after completing a - response, while there is no matching traffic (in seconds). If an HTTP - keep-alive is not specified, a default value (610 seconds) will be - used. For Global external HTTP(S) load balancer, the minimum allowed - value is 5 seconds and the maximum allowed value is 1200 seconds. + Represents the maximum amount of time that a TCP connection can be idle + between the (downstream) client and the target HTTP proxy. If an HTTP + keepalive timeout is not specified, the default value is 610 seconds. + For global external HTTP(S) load balancer, the minimum allowed value is + 5 seconds and the maximum allowed value is 1200 seconds. --proxy-bind This flag applies when the load_balancing_scheme of the associated diff --git a/gcloud/alpha/compute/target-http-proxies/update b/gcloud/alpha/compute/target-http-proxies/update index 0f47b74e8..68f3ae9ea 100644 --- a/gcloud/alpha/compute/target-http-proxies/update +++ b/gcloud/alpha/compute/target-http-proxies/update @@ -46,14 +46,15 @@ OPTIONAL FLAGS At most one of these can be specified: --clear-http-keep-alive-timeout-sec - Clears previously configured http keep alive timeout sec + Clears the previously configured HTTP keepalive timeout. --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC - Specifies how long to keep a connection open, after completing a - response, while there is no matching traffic (in seconds). If an HTTP - keep-alive is not specified, a default value (610 seconds) will be - used. For Global external HTTP(S) load balancer, the minimum allowed - value is 5 seconds and the maximum allowed value is 1200 seconds. + Represents the maximum amount of time that a TCP connection can be + idle between the (downstream) client and the target HTTP proxy. If an + HTTP keepalive timeout is not specified, the default value is 610 + seconds. For global external HTTP(S) load balancer, the minimum + allowed value is 5 seconds and the maximum allowed value is 1200 + seconds. At most one of these can be specified: diff --git a/gcloud/alpha/compute/target-https-proxies/create b/gcloud/alpha/compute/target-https-proxies/create index 731891d5c..cafc6c2f7 100644 --- a/gcloud/alpha/compute/target-https-proxies/create +++ b/gcloud/alpha/compute/target-https-proxies/create @@ -80,11 +80,11 @@ OPTIONAL FLAGS An optional, textual description for the target HTTPS proxy. --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC - Specifies how long to keep a connection open, after completing a - response, while there is no matching traffic (in seconds). If an HTTP - keep-alive is not specified, a default value (610 seconds) will be - used. For Global external HTTP(S) load balancer, the minimum allowed - value is 5 seconds and the maximum allowed value is 1200 seconds. + Represents the maximum amount of time that a TCP connection can be idle + between the (downstream) client and the target HTTP proxy. If an HTTP + keepalive timeout is not specified, the default value is 610 seconds. + For global external HTTP(S) load balancer, the minimum allowed value is + 5 seconds and the maximum allowed value is 1200 seconds. --proxy-bind This flag applies when the load_balancing_scheme of the associated diff --git a/gcloud/alpha/compute/target-https-proxies/update b/gcloud/alpha/compute/target-https-proxies/update index d0a312e36..da07b6a3d 100644 --- a/gcloud/alpha/compute/target-https-proxies/update +++ b/gcloud/alpha/compute/target-https-proxies/update @@ -166,14 +166,15 @@ FLAGS At most one of these can be specified: --clear-http-keep-alive-timeout-sec - Clears previously configured http keep alive timeout sec + Clears the previously configured HTTP keepalive timeout. --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC - Specifies how long to keep a connection open, after completing a - response, while there is no matching traffic (in seconds). If an HTTP - keep-alive is not specified, a default value (610 seconds) will be - used. For Global external HTTP(S) load balancer, the minimum allowed - value is 5 seconds and the maximum allowed value is 1200 seconds. + Represents the maximum amount of time that a TCP connection can be + idle between the (downstream) client and the target HTTP proxy. If an + HTTP keepalive timeout is not specified, the default value is 610 + seconds. For global external HTTP(S) load balancer, the minimum + allowed value is 5 seconds and the maximum allowed value is 1200 + seconds. At most one of these can be specified: diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 9d47a6e88..a021fef6d 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -24,8 +24,8 @@ SYNOPSIS [--no-enable-autoupgrade] [--enable-cloud-logging] [--enable-cloud-monitoring] [--enable-cloud-run-alpha] [--enable-confidential-nodes] [--enable-cost-allocation] - [--enable-dataplane-v2] [--enable-fleet] [--enable-gke-oidc] - [--enable-google-cloud-access] [--enable-gvnic] + [--enable-dataplane-v2] [--enable-fleet] [--enable-fqdn-network-policy] + [--enable-gke-oidc] [--enable-google-cloud-access] [--enable-gvnic] [--enable-identity-service] [--enable-image-streaming] [--enable-intra-node-visibility] [--enable-ip-alias] [--enable-kubernetes-alpha] @@ -425,6 +425,10 @@ FLAGS different project, please use --fleet-project=FLEET_HOST_PROJECT. Example: $ gcloud alpha container clusters create --enable-fleet + --enable-fqdn-network-policy + Enable FQDN Network Policies on the cluster. FQDN Network Policies are + disabled by default. + --enable-gke-oidc (DEPRECATED) Enable GKE OIDC authentication on the cluster. diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 0c973d13e..67249ba72 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -10,7 +10,8 @@ SYNOPSIS | --database-encryption-key=DATABASE_ENCRYPTION_KEY | --disable-database-encryption | --disable-default-snat | --disable-workload-identity | --enable-autoscaling - | --enable-cost-allocation | --enable-fleet | --enable-gke-oidc + | --enable-cost-allocation | --enable-fleet + | --enable-fqdn-network-policy | --enable-gke-oidc | --enable-google-cloud-access | --enable-identity-service | --enable-image-streaming | --enable-intra-node-visibility | --enable-kubernetes-unstable-apis=API,[API,...] @@ -215,6 +216,10 @@ REQUIRED FLAGS different project, please use --fleet-project=FLEET_HOST_PROJECT. Example: $ gcloud alpha container clusters update --enable-fleet + --enable-fqdn-network-policy + Enable FQDN Network Policies on the cluster. FQDN Network Policies + are disabled by default. + --enable-gke-oidc (DEPRECATED) Enable GKE OIDC authentication on the cluster. diff --git a/gcloud/alpha/container/fleet/scopes/create b/gcloud/alpha/container/fleet/scopes/create index 2763f2cf7..bff98e617 100644 --- a/gcloud/alpha/container/fleet/scopes/create +++ b/gcloud/alpha/container/fleet/scopes/create @@ -3,7 +3,10 @@ NAME SYNOPSIS gcloud alpha container fleet scopes create SCOPE [--async] - [GCLOUD_WIDE_FLAG ...] + [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + --upstream-scope=UPSTREAM_SCOPE + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + --upgrade-selector=[UPGRADE_SELECTOR,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a Fleet Scope resource. @@ -42,6 +45,70 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + Rollout Sequencing + + These flags are not compatible with the --async flag. + + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + Configures the default soaking duration for each upgrade propagating + through the current scope to become "COMPLETE". Soaking begins after + all clusters in the scope are on the target version, or after 30 days + if all cluster upgrades are not complete. Once an upgrade state + becomes "COMPLETE", it will automatically be propagated to the + downstream scope. Max is 30 days. + + See $ gcloud topic datetimes for information on duration formats. + + To configure Rollout Sequencing for a given scope, SCOPE_NAME, this + attribute must be set. To do this while specifying a default soaking + duration of 7 days, run: + + $ gcloud alpha container fleet scopes create SCOPE_NAME \ + default-upgrade-soaking=7d + + --upstream-scope=UPSTREAM_SCOPE + Full resource name of the upstream scope in the format of + projects/{project}/locations/{location}/scopes/{scope}. GKE will + finish upgrades on the upstream scope before applying the same + upgrades to the current scope. + + To configure the upstream scope for SCOPE_NAME, run: + + $ gcloud alpha container fleet scopes create SCOPE_NAME \ + --upstream-scope=projects/{upstream_project}/locations/global/scopes/{upstream_scope} + + Upgrade soaking override. + + Defines a specific soaking time override for a particular upgrade + propagating through the current scope that supercedes the default + soaking duration configured by --default-upgrade-soaking. + + To set an upgrade soaking override of 12 hours for the upgrade with + name, k8s_control_plane, and version, 1.23.1-gke.1000, run: + + $ gcloud alpha container fleet scopes create SCOPE_NAME \ + --add-upgrade-soaking-override=12h \ + --upgrade-selector=name="k8s_control_plane",version="1.23.1-gke.1000" + + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + Overrides the soaking time for a particular upgrade name and + version propagating through the current scope. Set soaking to 0 + days to bypass soaking and fast-forward the upgrade to the + downstream scope. + + See $ gcloud topic datetimes for information on duration formats. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --upgrade-selector=[UPGRADE_SELECTOR,...] + Name and version of the upgrade to be overridden where version is a + full GKE version. Currently, name can be either k8s_control_plane + or k8s_node. + + This flag argument must be specified if any of the other arguments + in this group are specified. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/container/fleet/scopes/describe b/gcloud/alpha/container/fleet/scopes/describe index 2418ba84c..0f0b3fd9b 100644 --- a/gcloud/alpha/container/fleet/scopes/describe +++ b/gcloud/alpha/container/fleet/scopes/describe @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud alpha container fleet scopes describe (SCOPE : --location=LOCATION) + [--show-cluster-upgrade | --show-linked-cluster-upgrade] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -50,6 +51,33 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line; ▸ global is the only supported location. +FLAGS + Rollout Sequencing + + At most one of these can be specified: + + --show-cluster-upgrade + Shows the cluster upgrade feature information for the current scope. + + To view the cluster upgrade feature information for SCOPE_NAME, run: + + $ gcloud alpha container fleet scopes describe SCOPE_NAME \ + --show-cluster-upgrade + + --show-linked-cluster-upgrade + Shows the cluster upgrade feature information for the current scope + as well as information for all other scopes linked in the same + rollout sequence (provided that the caller has permission to view the + upstream and downstream scopes that exist in other fleets). This + displays cluster upgrade information for scopes in the current + scope's rollout sequence in order of furthest upstream to downstream. + + To view the cluster upgrade feature information for the rollout + sequence containing SCOPE_NAME, run: + + $ gcloud alpha container fleet scopes describe SCOPE_NAME \ + --show-linked-cluster-upgrade + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/container/fleet/scopes/help b/gcloud/alpha/container/fleet/scopes/help index 6efd09985..a8e3f82bf 100644 --- a/gcloud/alpha/container/fleet/scopes/help +++ b/gcloud/alpha/container/fleet/scopes/help @@ -2,7 +2,7 @@ NAME gcloud alpha container fleet scopes - manage scopes of all your GKE fleets SYNOPSIS - gcloud alpha container fleet scopes COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha container fleet scopes GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Manage scopes of all your GKE fleets. @@ -27,6 +27,9 @@ COMMANDS list (ALPHA) List fleet scopes. + update + (ALPHA) Update a scope. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/container/fleet/scopes/update b/gcloud/alpha/container/fleet/scopes/update new file mode 100644 index 000000000..333814454 --- /dev/null +++ b/gcloud/alpha/container/fleet/scopes/update @@ -0,0 +1,162 @@ +NAME + gcloud alpha container fleet scopes update - update a scope + +SYNOPSIS + gcloud alpha container fleet scopes update (SCOPE : --location=LOCATION) + [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + --remove-upgrade-soaking-overrides + | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + --upgrade-selector=[UPGRADE_SELECTOR,...] --reset-upstream-scope + | --upstream-scope=UPSTREAM_SCOPE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an existing Fleet Scope. + +EXAMPLES + First retrieve the ID of the scope using the command below. + + $ gcloud alpha container fleet scopes list + + Update a scope. + + $ gcloud alpha container fleet scopes update SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - fleet scope resource. 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 can be set in other ways. + + To set the project attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. + + To set the scope attribute: + ▸ provide the argument scope on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location name. + + To set the location attribute: + ▸ provide the argument scope on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +FLAGS + Rollout Sequencing + + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + Configures the default soaking duration for each upgrade propagating + through the current scope to become "COMPLETE". Soaking begins after + all clusters in the scope are on the target version, or after 30 days + if all cluster upgrades are not complete. Once an upgrade state + becomes "COMPLETE", it will automatically be propagated to the + downstream scope. Max is 30 days. + + See $ gcloud topic datetimes for information on duration formats. + + To configure Rollout Sequencing for a given scope, SCOPE_NAME, this + attribute must be set. To do this while specifying a default soaking + duration of 7 days, run: + + $ gcloud alpha container fleet scopes update SCOPE_NAME \ + default-upgrade-soaking=7d + + At most one of these can be specified: + + --remove-upgrade-soaking-overrides + Removes soaking time overrides for all upgrades propagating through + the current scope. Consequently, all upgrades will follow the soak + time configured by --default-upgrade-soaking until new overrides + are configured with --add_upgrade_soaking_override and + --upgrade_selector. + + To remove all soaking time overrides configured for SCOPE_NAME, + run: + + $ gcloud alpha container fleet scopes update SCOPE_NAME \ + --remove-upgrade-soaking-overrides + + Upgrade soaking override. + + Defines a specific soaking time override for a particular upgrade + propagating through the current scope that supercedes the default + soaking duration configured by --default-upgrade-soaking. + + To set an upgrade soaking override of 12 hours for the upgrade with + name, k8s_control_plane, and version, 1.23.1-gke.1000, run: + + $ gcloud alpha container fleet scopes update SCOPE_NAME \ + --add-upgrade-soaking-override=12h \ + --upgrade-selector=name="k8s_control_plane",version="1.23.1-gke.1000" + + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + Overrides the soaking time for a particular upgrade name and + version propagating through the current scope. Set soaking to 0 + days to bypass soaking and fast-forward the upgrade to the + downstream scope. + + See $ gcloud topic datetimes for information on duration formats. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --upgrade-selector=[UPGRADE_SELECTOR,...] + Name and version of the upgrade to be overridden where version is + a full GKE version. Currently, name can be either + k8s_control_plane or k8s_node. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + At most one of these can be specified: + + --reset-upstream-scope + Clears the relationship between the current scope and its upstream + scope in the rollout sequence. + + To remove the link between SCOPE_NAME and its upstream scope, run: + + $ gcloud alpha container fleet scopes update SCOPE_NAME \ + --reset-upstream-scope + + --upstream-scope=UPSTREAM_SCOPE + Full resource name of the upstream scope in the format of + projects/{project}/locations/{location}/scopes/{scope}. GKE will + finish upgrades on the upstream scope before applying the same + upgrades to the current scope. + + To configure the upstream scope for SCOPE_NAME, run: + + $ gcloud alpha container fleet scopes update SCOPE_NAME \ + --upstream-scope=projects/{upstream_project}/locations/global/scopes/{upstream_scope} + +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. + +API REFERENCE + This command uses the gkehub/v1alpha API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/container/hub/scopes/create b/gcloud/alpha/container/hub/scopes/create index 0414c3f1f..72c53ac42 100644 --- a/gcloud/alpha/container/hub/scopes/create +++ b/gcloud/alpha/container/hub/scopes/create @@ -3,7 +3,10 @@ NAME SYNOPSIS gcloud alpha container hub scopes create SCOPE [--async] - [GCLOUD_WIDE_FLAG ...] + [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + --upstream-scope=UPSTREAM_SCOPE + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + --upgrade-selector=[UPGRADE_SELECTOR,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a Fleet Scope resource. @@ -42,6 +45,70 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + Rollout Sequencing + + These flags are not compatible with the --async flag. + + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + Configures the default soaking duration for each upgrade propagating + through the current scope to become "COMPLETE". Soaking begins after + all clusters in the scope are on the target version, or after 30 days + if all cluster upgrades are not complete. Once an upgrade state + becomes "COMPLETE", it will automatically be propagated to the + downstream scope. Max is 30 days. + + See $ gcloud topic datetimes for information on duration formats. + + To configure Rollout Sequencing for a given scope, SCOPE_NAME, this + attribute must be set. To do this while specifying a default soaking + duration of 7 days, run: + + $ gcloud alpha container hub scopes create SCOPE_NAME \ + default-upgrade-soaking=7d + + --upstream-scope=UPSTREAM_SCOPE + Full resource name of the upstream scope in the format of + projects/{project}/locations/{location}/scopes/{scope}. GKE will + finish upgrades on the upstream scope before applying the same + upgrades to the current scope. + + To configure the upstream scope for SCOPE_NAME, run: + + $ gcloud alpha container hub scopes create SCOPE_NAME \ + --upstream-scope=projects/{upstream_project}/locations/global/scopes/{upstream_scope} + + Upgrade soaking override. + + Defines a specific soaking time override for a particular upgrade + propagating through the current scope that supercedes the default + soaking duration configured by --default-upgrade-soaking. + + To set an upgrade soaking override of 12 hours for the upgrade with + name, k8s_control_plane, and version, 1.23.1-gke.1000, run: + + $ gcloud alpha container hub scopes create SCOPE_NAME \ + --add-upgrade-soaking-override=12h \ + --upgrade-selector=name="k8s_control_plane",version="1.23.1-gke.1000" + + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + Overrides the soaking time for a particular upgrade name and + version propagating through the current scope. Set soaking to 0 + days to bypass soaking and fast-forward the upgrade to the + downstream scope. + + See $ gcloud topic datetimes for information on duration formats. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --upgrade-selector=[UPGRADE_SELECTOR,...] + Name and version of the upgrade to be overridden where version is a + full GKE version. Currently, name can be either k8s_control_plane + or k8s_node. + + This flag argument must be specified if any of the other arguments + in this group are specified. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/container/hub/scopes/describe b/gcloud/alpha/container/hub/scopes/describe index 1ebe9a0c3..58945d151 100644 --- a/gcloud/alpha/container/hub/scopes/describe +++ b/gcloud/alpha/container/hub/scopes/describe @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud alpha container hub scopes describe (SCOPE : --location=LOCATION) + [--show-cluster-upgrade | --show-linked-cluster-upgrade] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -50,6 +51,33 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line; ▸ global is the only supported location. +FLAGS + Rollout Sequencing + + At most one of these can be specified: + + --show-cluster-upgrade + Shows the cluster upgrade feature information for the current scope. + + To view the cluster upgrade feature information for SCOPE_NAME, run: + + $ gcloud alpha container hub scopes describe SCOPE_NAME \ + --show-cluster-upgrade + + --show-linked-cluster-upgrade + Shows the cluster upgrade feature information for the current scope + as well as information for all other scopes linked in the same + rollout sequence (provided that the caller has permission to view the + upstream and downstream scopes that exist in other fleets). This + displays cluster upgrade information for scopes in the current + scope's rollout sequence in order of furthest upstream to downstream. + + To view the cluster upgrade feature information for the rollout + sequence containing SCOPE_NAME, run: + + $ gcloud alpha container hub scopes describe SCOPE_NAME \ + --show-linked-cluster-upgrade + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/container/hub/scopes/help b/gcloud/alpha/container/hub/scopes/help index b86c53d8c..055e382b4 100644 --- a/gcloud/alpha/container/hub/scopes/help +++ b/gcloud/alpha/container/hub/scopes/help @@ -2,7 +2,7 @@ NAME gcloud alpha container hub scopes - manage scopes of all your GKE fleets SYNOPSIS - gcloud alpha container hub scopes COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha container hub scopes GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Manage scopes of all your GKE fleets. @@ -27,6 +27,9 @@ COMMANDS list (ALPHA) List fleet scopes. + update + (ALPHA) Update a scope. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/container/hub/scopes/update b/gcloud/alpha/container/hub/scopes/update new file mode 100644 index 000000000..785a44c20 --- /dev/null +++ b/gcloud/alpha/container/hub/scopes/update @@ -0,0 +1,162 @@ +NAME + gcloud alpha container hub scopes update - update a scope + +SYNOPSIS + gcloud alpha container hub scopes update (SCOPE : --location=LOCATION) + [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + --remove-upgrade-soaking-overrides + | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + --upgrade-selector=[UPGRADE_SELECTOR,...] --reset-upstream-scope + | --upstream-scope=UPSTREAM_SCOPE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an existing Fleet Scope. + +EXAMPLES + First retrieve the ID of the scope using the command below. + + $ gcloud alpha container hub scopes list + + Update a scope. + + $ gcloud alpha container hub scopes update SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - fleet scope resource. 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 can be set in other ways. + + To set the project attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. + + To set the scope attribute: + ▸ provide the argument scope on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location name. + + To set the location attribute: + ▸ provide the argument scope on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +FLAGS + Rollout Sequencing + + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + Configures the default soaking duration for each upgrade propagating + through the current scope to become "COMPLETE". Soaking begins after + all clusters in the scope are on the target version, or after 30 days + if all cluster upgrades are not complete. Once an upgrade state + becomes "COMPLETE", it will automatically be propagated to the + downstream scope. Max is 30 days. + + See $ gcloud topic datetimes for information on duration formats. + + To configure Rollout Sequencing for a given scope, SCOPE_NAME, this + attribute must be set. To do this while specifying a default soaking + duration of 7 days, run: + + $ gcloud alpha container hub scopes update SCOPE_NAME \ + default-upgrade-soaking=7d + + At most one of these can be specified: + + --remove-upgrade-soaking-overrides + Removes soaking time overrides for all upgrades propagating through + the current scope. Consequently, all upgrades will follow the soak + time configured by --default-upgrade-soaking until new overrides + are configured with --add_upgrade_soaking_override and + --upgrade_selector. + + To remove all soaking time overrides configured for SCOPE_NAME, + run: + + $ gcloud alpha container hub scopes update SCOPE_NAME \ + --remove-upgrade-soaking-overrides + + Upgrade soaking override. + + Defines a specific soaking time override for a particular upgrade + propagating through the current scope that supercedes the default + soaking duration configured by --default-upgrade-soaking. + + To set an upgrade soaking override of 12 hours for the upgrade with + name, k8s_control_plane, and version, 1.23.1-gke.1000, run: + + $ gcloud alpha container hub scopes update SCOPE_NAME \ + --add-upgrade-soaking-override=12h \ + --upgrade-selector=name="k8s_control_plane",version="1.23.1-gke.1000" + + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + Overrides the soaking time for a particular upgrade name and + version propagating through the current scope. Set soaking to 0 + days to bypass soaking and fast-forward the upgrade to the + downstream scope. + + See $ gcloud topic datetimes for information on duration formats. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --upgrade-selector=[UPGRADE_SELECTOR,...] + Name and version of the upgrade to be overridden where version is + a full GKE version. Currently, name can be either + k8s_control_plane or k8s_node. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + At most one of these can be specified: + + --reset-upstream-scope + Clears the relationship between the current scope and its upstream + scope in the rollout sequence. + + To remove the link between SCOPE_NAME and its upstream scope, run: + + $ gcloud alpha container hub scopes update SCOPE_NAME \ + --reset-upstream-scope + + --upstream-scope=UPSTREAM_SCOPE + Full resource name of the upstream scope in the format of + projects/{project}/locations/{location}/scopes/{scope}. GKE will + finish upgrades on the upstream scope before applying the same + upgrades to the current scope. + + To configure the upstream scope for SCOPE_NAME, run: + + $ gcloud alpha container hub scopes update SCOPE_NAME \ + --upstream-scope=projects/{upstream_project}/locations/global/scopes/{upstream_scope} + +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. + +API REFERENCE + This command uses the gkehub/v1alpha API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/datastore/databases/help b/gcloud/alpha/datastore/databases/help deleted file mode 100644 index 5093fca95..000000000 --- a/gcloud/alpha/datastore/databases/help +++ /dev/null @@ -1,25 +0,0 @@ -NAME - gcloud alpha datastore databases - manage Creation of Cloud Firestore in - Native mode Database - -SYNOPSIS - gcloud alpha datastore databases COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Creation of Cloud Firestore in Native mode Database. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud datastore databases - - $ gcloud beta datastore databases - diff --git a/gcloud/alpha/datastore/help b/gcloud/alpha/datastore/help index 61a05818d..c55d258ee 100644 --- a/gcloud/alpha/datastore/help +++ b/gcloud/alpha/datastore/help @@ -30,9 +30,6 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: - databases - (ALPHA) Manage Creation of Cloud Firestore in Native mode Database. - indexes (ALPHA) Manage your Cloud Datastore indexes. diff --git a/gcloud/alpha/firestore/databases/create b/gcloud/alpha/firestore/databases/create index 735c03316..bf3a0360f 100644 --- a/gcloud/alpha/firestore/databases/create +++ b/gcloud/alpha/firestore/databases/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha firestore databases create --location=LOCATION - [--database=DATABASE; default="(default)"] [--enable-delete-protection] + [--database=DATABASE; default="(default)"] [--delete-protection] [--type=TYPE; default="firestore-native"] [GCLOUD_WIDE_FLAG ...] EXAMPLES @@ -26,14 +26,17 @@ EXAMPLES enabled. $ gcloud alpha firestore databases create --location=nam5 \ - --enable-delete-protection + --delete-protection REQUIRED FLAGS --location=LOCATION - The location to create the Google Cloud Firestore Native database - within. Available locations are listed at + The location to operate on. Available locations are listed at https://cloud.google.com/firestore/docs/locations. + For example, to operate on location us-east1: + + $ gcloud alpha firestore databases create --location='us-east1' + OPTIONAL FLAGS --database=DATABASE; default="(default)" The ID to use for the database, which will become the final component @@ -46,7 +49,7 @@ OPTIONAL FLAGS Using "(default)" database ID is also allowed. - --enable-delete-protection + --delete-protection Whether to enable delete protection on the created database. If set to true, delete protection of the new database will be enabled diff --git a/gcloud/alpha/firestore/databases/describe b/gcloud/alpha/firestore/databases/describe index 9c53db048..a929ce457 100644 --- a/gcloud/alpha/firestore/databases/describe +++ b/gcloud/alpha/firestore/databases/describe @@ -1,38 +1,23 @@ NAME - gcloud alpha firestore databases describe - describe a Google Cloud - Firestore database + gcloud alpha firestore databases describe - describes information about a + Cloud Firestore database SYNOPSIS - gcloud alpha firestore databases describe [--database=DATABASE] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha firestore databases describe + [--database=DATABASE; default="(default)"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe a Google Cloud Firestore database. - -EXAMPLES - The following command describes a Google Cloud Firestore database. + (ALPHA) The following command describes a Google Cloud Firestore database. $ gcloud alpha firestore databases describe FLAGS - Database resource - The Google Cloud Firestore database to describe. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + --database=DATABASE; default="(default)" + The database to operate on. The default value is (default). - To set the project attribute: - ◆ provide the argument --database on the command line with a fully - specified name; - ◆ the default value of argument [--database] is (default) with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. + For example, to operate on database foo: - --database=DATABASE - ID of the database or fully qualified identifier for the database. - - To set the database attribute: - ▸ provide the argument --database on the command line; - ▸ the default value of argument [--database] is (default). + $ gcloud alpha firestore databases describe --database='foo' GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -42,10 +27,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the firestore/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/firestore - NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/firestore/databases/help b/gcloud/alpha/firestore/databases/help index b1f51183d..25c8919d2 100644 --- a/gcloud/alpha/firestore/databases/help +++ b/gcloud/alpha/firestore/databases/help @@ -20,7 +20,7 @@ COMMANDS (ALPHA) Create a Google Cloud Firestore database via Firestore API. describe - (ALPHA) Describe a Google Cloud Firestore database. + (ALPHA) Describes information about a Cloud Firestore database. list (ALPHA) Lists all Firestore databases under the project. diff --git a/gcloud/alpha/functions/add-invoker-policy-binding b/gcloud/alpha/functions/add-invoker-policy-binding index dd528b0e4..daa8a64e8 100644 --- a/gcloud/alpha/functions/add-invoker-policy-binding +++ b/gcloud/alpha/functions/add-invoker-policy-binding @@ -10,8 +10,8 @@ DESCRIPTION (ALPHA) This command applies to Cloud Functions 2nd Gen only. EXAMPLES - To add the invoker policy binding for FUNCTION-1 from role ROLE-1 for - member MEMBER-1 run: + To add the invoker role policy binding for FUNCTION-1 for member MEMBER-1 + run: $ gcloud alpha functions add-invoker-policy-binding FUNCTION-1 \ --member=MEMBER-1 diff --git a/gcloud/alpha/functions/remove-invoker-policy-binding b/gcloud/alpha/functions/remove-invoker-policy-binding index 2edc50957..b308198b4 100644 --- a/gcloud/alpha/functions/remove-invoker-policy-binding +++ b/gcloud/alpha/functions/remove-invoker-policy-binding @@ -10,8 +10,8 @@ DESCRIPTION (ALPHA) This command applies to Cloud Functions 2nd gen only. EXAMPLES - To remove the invoker policy binding for FUNCTION-1 from role ROLE-1 for - member MEMBER-1 run: + To remove the invoker role policy binding for FUNCTION-1 for member + MEMBER-1 run: $ gcloud alpha functions remove-invoker-policy-binding FUNCTION-1 \ --member=MEMBER-1 diff --git a/gcloud/alpha/kms/inventory/get-protected-resources-summary b/gcloud/alpha/kms/inventory/get-protected-resources-summary index 60381b1d5..85b40e2e1 100644 --- a/gcloud/alpha/kms/inventory/get-protected-resources-summary +++ b/gcloud/alpha/kms/inventory/get-protected-resources-summary @@ -11,9 +11,9 @@ DESCRIPTION (ALPHA) gcloud alpha kms inventory get-protected-resources-summary returns a summary of the resources a key is protecting. - The summary includes: How many projects contain protected resources How - many protected resources there are What types of protected resources The - count for each type of protected resource + The summary includes how many projects contain protected resources, how + many protected resources there are, what are the types of protected + resources, and the count for each type of protected resource. EXAMPLES To view the summary of protected resources for the key puppy, run: @@ -70,7 +70,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud kms inventory get-protected-resources-summary $ gcloud beta kms inventory get-protected-resources-summary diff --git a/gcloud/alpha/kms/inventory/help b/gcloud/alpha/kms/inventory/help index 8f3d5220a..2829e9f5e 100644 --- a/gcloud/alpha/kms/inventory/help +++ b/gcloud/alpha/kms/inventory/help @@ -29,7 +29,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud kms inventory $ gcloud beta kms inventory diff --git a/gcloud/alpha/kms/inventory/list-keys b/gcloud/alpha/kms/inventory/list-keys index 3efa5d091..8365c525f 100644 --- a/gcloud/alpha/kms/inventory/list-keys +++ b/gcloud/alpha/kms/inventory/list-keys @@ -63,7 +63,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud kms inventory list-keys $ gcloud beta kms inventory list-keys diff --git a/gcloud/alpha/kms/inventory/search-protected-resources b/gcloud/alpha/kms/inventory/search-protected-resources index 579eee095..ad59e6f63 100644 --- a/gcloud/alpha/kms/inventory/search-protected-resources +++ b/gcloud/alpha/kms/inventory/search-protected-resources @@ -105,7 +105,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud kms inventory search-protected-resources $ gcloud beta kms inventory search-protected-resources diff --git a/gcloud/alpha/logging/sinks/create b/gcloud/alpha/logging/sinks/create index 43e184272..e7b2851b4 100644 --- a/gcloud/alpha/logging/sinks/create +++ b/gcloud/alpha/logging/sinks/create @@ -1,5 +1,5 @@ NAME - gcloud alpha logging sinks create - creates a log sink + gcloud alpha logging sinks create - create a log sink SYNOPSIS gcloud alpha logging sinks create SINK_NAME DESTINATION @@ -13,8 +13,8 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Creates a log used to route log entries to a destination. The sink - routes all log entries that match its --log-filter flag. + (ALPHA) Create a log sink used to route log entries to a destination. The + sink routes all log entries that match its --log-filter flag. An empty filter matches all logs. @@ -72,9 +72,9 @@ POSITIONAL ARGUMENTS FLAGS --custom-writer-identity=SERVICE_ACCOUNT_EMAIL - Writer identity for the sink. Only available for writing to - cross-project LogBucket sinks. Note a writer identity is automatically - generated if needed for the sink when it is not explicitly provided. + Writer identity for the sink. This flag can only be used if the + destination is a log bucket in a different project. The writer identity + is automatically generated when it is not provided for a sink. --description=DESCRIPTION Description of the sink. diff --git a/gcloud/alpha/logging/sinks/help b/gcloud/alpha/logging/sinks/help index 631536c26..4423eb230 100644 --- a/gcloud/alpha/logging/sinks/help +++ b/gcloud/alpha/logging/sinks/help @@ -17,7 +17,7 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Creates a log sink. + (ALPHA) Create a log sink. delete (ALPHA) Delete a sink. diff --git a/gcloud/alpha/logging/sinks/update b/gcloud/alpha/logging/sinks/update index d58525b8e..fe2aeec9f 100644 --- a/gcloud/alpha/logging/sinks/update +++ b/gcloud/alpha/logging/sinks/update @@ -67,9 +67,9 @@ FLAGS Remove all logging exclusions from the sink. --custom-writer-identity=SERVICE_ACCOUNT_EMAIL - Writer identity for the sink. Only available for writing to - cross-project LogBucket sinks. Note a writer identity is automatically - generated if needed for the sink when it is not explicitly provided. + Writer identity for the sink. This flag can only be used if the + destination is a log bucket in a different project. The writer identity + is automatically generated when it is not provided for a sink. --description=DESCRIPTION Description of the sink. diff --git a/gcloud/alpha/netapp/volumes/create b/gcloud/alpha/netapp/volumes/create index 5acd5db1e..b4905c746 100644 --- a/gcloud/alpha/netapp/volumes/create +++ b/gcloud/alpha/netapp/volumes/create @@ -15,8 +15,7 @@ SYNOPSIS [kerberos-5i-read-write=KERBEROS-5I-READ-WRITE], [kerberos-5p-read-only=KERBEROS-5P-READ-ONLY], [kerberos-5p-read-write=KERBEROS-5P-READ-WRITE], - [nfsv3=NFSV3],[nfsv4=NFSV4]] [--from-snapshot=FROM_SNAPSHOT] - [--labels=[KEY=VALUE,...]] + [nfsv3=NFSV3],[nfsv4=NFSV4]] [--labels=[KEY=VALUE,...]] [--security-style=SECURITY_STYLE; default="SECURITY_STYLE_UNSPECIFIED"] [--smb-settings=SMB_SETTING,[SMB_SETTING,...]] [--snap-reserve=SNAP_RESERVE] @@ -29,6 +28,7 @@ SYNOPSIS [hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]] [--snapshot-weekly=[day=DAY], [hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]] + [--source-snapshot=SOURCE_SNAPSHOT] [--unix-permissions=UNIX_PERMISSIONS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -144,32 +144,6 @@ OPTIONAL FLAGS kerberos-5p-read-only=KERBEROS_5P_READ_ONLY, kerberos-5p-read-write=KERBEROS_5P_READ_WRITE - Snapshot resource - The Snapshot to create the Volume from. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument --from-snapshot on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - To set the location attribute: - ◆ provide the argument --from-snapshot on the command line with a fully - specified name; - ◆ set the property netapp/location; - ◆ set the property netapp/region. - - To set the volume attribute: - ◆ provide the argument --from-snapshot on the command line with a fully - specified name. - - --from-snapshot=FROM_SNAPSHOT - ID of the snapshot or fully qualified identifier for the snapshot. - - To set the snapshot attribute: - ▸ provide the argument --from-snapshot on the command line. - --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. @@ -219,6 +193,32 @@ OPTIONAL FLAGS Make a snapshot every week e.g. at Monday 04:00, Wednesday 05:20, Sunday 23:50 + Snapshot resource - The source Snapshot to create the Volume from. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --source-snapshot on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument --source-snapshot on the command line with a + fully specified name; + ◆ set the property netapp/location; + ◆ set the property netapp/region. + + To set the volume attribute: + ◆ provide the argument --source-snapshot on the command line with a + fully specified name. + + --source-snapshot=SOURCE_SNAPSHOT + ID of the snapshot or fully qualified identifier for the snapshot. + + To set the snapshot attribute: + ▸ provide the argument --source-snapshot on the command line. + --unix-permissions=UNIX_PERMISSIONS Unix permissions the mount point will be created with.Unix permissions are only applicable with NFS protocol only diff --git a/gcloud/alpha/netapp/volumes/update b/gcloud/alpha/netapp/volumes/update index c1b8002a0..2efcca13e 100644 --- a/gcloud/alpha/netapp/volumes/update +++ b/gcloud/alpha/netapp/volumes/update @@ -13,8 +13,7 @@ SYNOPSIS [kerberos-5i-read-write=KERBEROS-5I-READ-WRITE], [kerberos-5p-read-only=KERBEROS-5P-READ-ONLY], [kerberos-5p-read-write=KERBEROS-5P-READ-WRITE], - [nfsv3=NFSV3],[nfsv4=NFSV4]] [--from-snapshot=FROM_SNAPSHOT] - [--protocols=PROTOCOL,[PROTOCOL,...]] + [nfsv3=NFSV3],[nfsv4=NFSV4]] [--protocols=PROTOCOL,[PROTOCOL,...]] [--security-style=SECURITY_STYLE; default="SECURITY_STYLE_UNSPECIFIED"] [--share-name=SHARE_NAME] [--smb-settings=SMB_SETTING,[SMB_SETTING,...]] @@ -28,8 +27,8 @@ SYNOPSIS [hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]] [--snapshot-weekly=[day=DAY], [hour=HOUR],[minute=MINUTE],[snapshots-to-keep=SNAPSHOTS-TO-KEEP]] - [--storage-pool=STORAGE_POOL] [--unix-permissions=UNIX_PERMISSIONS] - [--update-labels=[KEY=VALUE,...]] + [--source-snapshot=SOURCE_SNAPSHOT] [--storage-pool=STORAGE_POOL] + [--unix-permissions=UNIX_PERMISSIONS] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -94,32 +93,6 @@ FLAGS kerberos-5p-read-only=KERBEROS_5P_READ_ONLY, kerberos-5p-read-write=KERBEROS_5P_READ_WRITE - Snapshot resource - The Snapshot to create the Volume from. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument --from-snapshot on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - To set the location attribute: - ◆ provide the argument --from-snapshot on the command line with a fully - specified name; - ◆ set the property netapp/location; - ◆ set the property netapp/region. - - To set the volume attribute: - ◆ provide the argument --from-snapshot on the command line with a fully - specified name. - - --from-snapshot=FROM_SNAPSHOT - ID of the snapshot or fully qualified identifier for the snapshot. - - To set the snapshot attribute: - ▸ provide the argument --from-snapshot on the command line. - --protocols=PROTOCOL,[PROTOCOL,...] Type of File System protocols for the Cloud NetApp Files VolumeValid component values are: NFSV3, NFSV4, SMB @@ -170,6 +143,32 @@ FLAGS Make a snapshot every week e.g. at Monday 04:00, Wednesday 05:20, Sunday 23:50 + Snapshot resource - The source Snapshot to create the Volume from. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --source-snapshot on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument --source-snapshot on the command line with a + fully specified name; + ◆ set the property netapp/location; + ◆ set the property netapp/region. + + To set the volume attribute: + ◆ provide the argument --source-snapshot on the command line with a + fully specified name. + + --source-snapshot=SOURCE_SNAPSHOT + ID of the snapshot or fully qualified identifier for the snapshot. + + To set the snapshot attribute: + ▸ provide the argument --source-snapshot on the command line. + Storage pool resource - The Storage Pool to associate with Volume. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. diff --git a/gcloud/alpha/pubsub/subscriptions/create b/gcloud/alpha/pubsub/subscriptions/create index 4fa6945a0..6d7489b86 100644 --- a/gcloud/alpha/pubsub/subscriptions/create +++ b/gcloud/alpha/pubsub/subscriptions/create @@ -18,6 +18,7 @@ SYNOPSIS [--dead-letter-topic=DEAD_LETTER_TOPIC : --dead-letter-topic-project=DEAD_LETTER_TOPIC_PROJECT]] [--max-retry-delay=MAX_RETRY_DELAY --min-retry-delay=MIN_RETRY_DELAY] + [--push-no-wrapper : --push-no-wrapper-write-metadata] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -219,6 +220,20 @@ OPTIONAL FLAGS of "s", "m", "h", and "d" for seconds, minutes, hours, and days, respectively. If the unit is omitted, seconds is assumed. + NoWrapper Config Options. + + --push-no-wrapper + When set, the message data is delivered directly as the HTTP body. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --push-no-wrapper-write-metadata + When true, writes the Pub/Sub message metadata to + x-goog-pubsub-: headers of the HTTP request. Writes the + Pub/Sub message attributes to : headers of the HTTP + request. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/pubsub/subscriptions/modify-push-config b/gcloud/alpha/pubsub/subscriptions/modify-push-config index bc2cc9ec5..907da2b52 100644 --- a/gcloud/alpha/pubsub/subscriptions/modify-push-config +++ b/gcloud/alpha/pubsub/subscriptions/modify-push-config @@ -7,6 +7,7 @@ SYNOPSIS --push-endpoint=PUSH_ENDPOINT [--push-auth-service-account=SERVICE_ACCOUNT_EMAIL] [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] + [--push-no-wrapper : --push-no-wrapper-write-metadata] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -46,6 +47,20 @@ OPTIONAL FLAGS Audience used in the generated Open ID Connect token for authenticated push. If not specified, it will be set to the push-endpoint. + NoWrapper Config Options. + + --push-no-wrapper + When set, the message data is delivered directly as the HTTP body. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --push-no-wrapper-write-metadata + When true, writes the Pub/Sub message metadata to + x-goog-pubsub-: headers of the HTTP request. Writes the + Pub/Sub message attributes to : headers of the HTTP + request. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/pubsub/subscriptions/update b/gcloud/alpha/pubsub/subscriptions/update index fde18b978..51bceaf58 100644 --- a/gcloud/alpha/pubsub/subscriptions/update +++ b/gcloud/alpha/pubsub/subscriptions/update @@ -18,6 +18,8 @@ SYNOPSIS [--dead-letter-topic=DEAD_LETTER_TOPIC : --dead-letter-topic-project=DEAD_LETTER_TOPIC_PROJECT]] [--clear-labels | --remove-labels=[KEY,...]] + [--clear-push-no-wrapper-config + | [--push-no-wrapper : --push-no-wrapper-write-metadata]] [--clear-retry-policy | --max-retry-delay=MAX_RETRY_DELAY --min-retry-delay=MIN_RETRY_DELAY] [GCLOUD_WIDE_FLAG ...] @@ -194,6 +196,25 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + At most one of these can be specified: + + --clear-push-no-wrapper-config + If set, clear the NoWrapper config from the subscription. + + NoWrapper Config Options. + + --push-no-wrapper + When set, the message data is delivered directly as the HTTP body. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --push-no-wrapper-write-metadata + When true, writes the Pub/Sub message metadata to + x-goog-pubsub-: headers of the HTTP request. Writes the + Pub/Sub message attributes to : headers of the HTTP + request. + At most one of these can be specified: --clear-retry-policy diff --git a/gcloud/alpha/storage/buckets/add-iam-policy-binding b/gcloud/alpha/storage/buckets/add-iam-policy-binding index a322c0b79..2ccfaaab9 100644 --- a/gcloud/alpha/storage/buckets/add-iam-policy-binding +++ b/gcloud/alpha/storage/buckets/add-iam-policy-binding @@ -23,7 +23,7 @@ EXAMPLES To make objects in BUCKET publicly readable: $ gcloud alpha storage buckets add-iam-policy-binding gs://BUCKET \ - --member=AllUsers --role=roles/storage.objectViewer + --member=allUsers --role=roles/storage.objectViewer To specify a custom role for a principal on BUCKET: diff --git a/gcloud/auth/help b/gcloud/auth/help index d0696d151..f8e1e382e 100644 --- a/gcloud/auth/help +++ b/gcloud/auth/help @@ -14,7 +14,7 @@ DESCRIPTION the gcloud CLI (https://cloud.google.com/sdk/docs/authorizing). For information about authorizing a service account, see Authorizing with a service account - (https://cloud.google.com/sdk/docs/authorizing#authorizing_with_a_service_account). + (https://cloud.google.com/sdk/docs/authorizing#service-account). After running gcloud auth commands, you can run other commands with --account=ACCOUNT to authenticate the command with the credentials of the diff --git a/gcloud/beta/alloydb/clusters/help b/gcloud/beta/alloydb/clusters/help index ec25d1919..3852392ad 100644 --- a/gcloud/beta/alloydb/clusters/help +++ b/gcloud/beta/alloydb/clusters/help @@ -37,7 +37,8 @@ COMMANDS region. restore - (BETA) Restore an AlloyDB cluster from a given backup. + (BETA) Restore an AlloyDB cluster from a given backup or a source + cluster and a timestamp. update (BETA) Update an AlloyDB cluster within a given project and region. diff --git a/gcloud/beta/alloydb/clusters/restore b/gcloud/beta/alloydb/clusters/restore index 386ea13e4..f8a578812 100644 --- a/gcloud/beta/alloydb/clusters/restore +++ b/gcloud/beta/alloydb/clusters/restore @@ -1,18 +1,19 @@ NAME gcloud beta alloydb clusters restore - restore an AlloyDB cluster from a - given backup + given backup or a source cluster and a timestamp SYNOPSIS - gcloud beta alloydb clusters restore CLUSTER --region=REGION [--async] - [--network=NETWORK] - [--backup=BACKUP - | --point-in-time=POINT_IN_TIME --source-cluster=SOURCE_CLUSTER] + gcloud beta alloydb clusters restore CLUSTER --region=REGION + (--backup=BACKUP + | --point-in-time=POINT_IN_TIME --source-cluster=SOURCE_CLUSTER) + [--async] [--network=NETWORK] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Restore an AlloyDB cluster from a given backup. + (BETA) Restore an AlloyDB cluster from a given backup or a source cluster + and a timestamp. EXAMPLES To restore a cluster from a backup, run: @@ -20,6 +21,12 @@ EXAMPLES $ gcloud beta alloydb clusters restore my-cluster \ --region=us-central1 --backup=my-backup + To restore a cluster from a source cluster and a timestamp, run: + + $ gcloud beta alloydb clusters restore my-cluster \ + --region=us-central1 --source-cluster=old-cluster \ + --point-in-time=2012-11-15T16:19:00.094Z + POSITIONAL ARGUMENTS CLUSTER AlloyDB cluster ID @@ -29,26 +36,12 @@ REQUIRED FLAGS Regional location (e.g. asia-east1, us-east1). See the full list of regions at https://cloud.google.com/sql/docs/instance-locations. -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --network=NETWORK - Network in the current project that the instance will be part of. To - specify using a network with a shared VPC, use the full URL of the - network. For an example host project, 'testproject', and shared - 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: + Exactly one of these must be specified: - Restore a cluster using a specific backup as the source. - - --backup=BACKUP - AlloyDB backup ID + --backup=BACKUP + AlloyDB backup ID Restore a cluster from a source cluster at a given point in time. @@ -65,6 +58,18 @@ OPTIONAL FLAGS This flag argument must be specified if any of the other arguments in this group are specified. +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --network=NETWORK + Network in the current project that the instance will be part of. To + specify using a network with a shared VPC, use the full URL of the + network. For an example host project, 'testproject', and shared + network, 'testsharednetwork', this would be of the + form:--network=projects/testproject/global/networks/testsharednetwork + 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'. diff --git a/gcloud/beta/auth/help b/gcloud/beta/auth/help index 156fc341f..77e4a1252 100644 --- a/gcloud/beta/auth/help +++ b/gcloud/beta/auth/help @@ -14,7 +14,7 @@ DESCRIPTION the gcloud CLI (https://cloud.google.com/sdk/docs/authorizing). For information about authorizing a service account, see Authorizing with a service account - (https://cloud.google.com/sdk/docs/authorizing#authorizing_with_a_service_account). + (https://cloud.google.com/sdk/docs/authorizing#service-account). After running gcloud auth commands, you can run other commands with --account=ACCOUNT to authenticate the command with the credentials of the diff --git a/gcloud/beta/compute/disks/update b/gcloud/beta/compute/disks/update index 5529cbf03..966e5caee 100644 --- a/gcloud/beta/compute/disks/update +++ b/gcloud/beta/compute/disks/update @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta compute disks update DISK_NAME [--provisioned-iops=PROVISIONED_IOPS] - [--provisioned-throughput=PROVISIONED_THROUGHPUT] + [--provisioned-throughput=PROVISIONED_THROUGHPUT] [--size=SIZE] [--update-labels=[KEY=VALUE,...]] [--clear-architecture | --update-architecture=UPDATE_ARCHITECTURE] [--clear-labels | --remove-labels=[KEY,...]] @@ -48,6 +48,12 @@ FLAGS Provisioned throughput of disk to update. The throughput unit is MB per sec. + --size=SIZE + Size of the disks. The value must be a whole number followed by a size + unit of GB for gigabyte, or TB for terabyte. If no size unit is + specified, GB is assumed. For details about disk size limits, refer to: + https://cloud.google.com/compute/docs/disks + --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index acaf96b1c..a5ad6e708 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -120,10 +120,8 @@ FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new diff --git a/gcloud/beta/compute/instance-templates/create-with-container b/gcloud/beta/compute/instance-templates/create-with-container index 6415a171e..5babe1c67 100644 --- a/gcloud/beta/compute/instance-templates/create-with-container +++ b/gcloud/beta/compute/instance-templates/create-with-container @@ -114,10 +114,8 @@ FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index 94996bf14..73fc26b75 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -32,6 +32,7 @@ SYNOPSIS [--network-interface=[PROPERTY=VALUE,...]] [--network-performance-configs=[PROPERTY=VALUE,...]] [--network-tier=NETWORK_TIER] + [--per-instance-hostnames=[INSTANCE_NAME=INSTANCE_HOSTNAME,...]] [--post-key-revocation-action-type=POLICY] [--preemptible] [--provisioning-model=PROVISIONING_MODEL] [--resource-manager-tags=[KEY=VALUE,...]] @@ -165,10 +166,8 @@ OPTIONAL FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new @@ -615,6 +614,13 @@ OPTIONAL FLAGS NETWORK_TIER must be one of: PREMIUM, STANDARD, FIXED_STANDARD. The default value is PREMIUM. + --per-instance-hostnames=[INSTANCE_NAME=INSTANCE_HOSTNAME,...] + Specify the hostname of the instance to be created. The specified + hostname must be RFC1035 compliant. If hostname is not specified, the + default hostname is [INSTANCE_NAME].c.[PROJECT_ID].internal when using + the global DNS, and [INSTANCE_NAME].[ZONE].c.[PROJECT_ID].internal when + using zonal DNS. + --post-key-revocation-action-type=POLICY Specifies the behavior of the instance when the KMS key of one of its attached disks is revoked. The default is noop. POLICY must be one of: diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index 5befbd261..2158a702d 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -163,10 +163,8 @@ FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index 1e7926b16..ee8191dbd 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -123,10 +123,8 @@ FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new diff --git a/gcloud/beta/compute/interconnects/attachments/dedicated/create b/gcloud/beta/compute/interconnects/attachments/dedicated/create index 144c34eea..4e6c804bb 100644 --- a/gcloud/beta/compute/interconnects/attachments/dedicated/create +++ b/gcloud/beta/compute/interconnects/attachments/dedicated/create @@ -61,14 +61,7 @@ OPTIONAL FLAGS 50 Gbit/s --candidate-ipv6-subnets=[IPV6_SUBNET,...] - Up to 16 candidate prefixes that control the allocation of - cloudRouterIpv6Address and customerRouterIpv6Address for this - attachment. Each prefix must be in the Global Unique Address (GUA) - space. It is highly recommended that it be in a range owned by the - requestor. A GUA in a range owned by Google will cause the request to - fail. Google will select an available prefix from the supplied - candidates or fail the request. If not supplied, a /125 from a - Google-owned GUA block will be selected. + The candididate-ipv6-subnets field is not available. --candidate-subnets=[SUBNET,...] Up to 16 candidate prefixes that can be used to restrict the allocation @@ -81,16 +74,10 @@ OPTIONAL FLAGS request fails if all candidate subnets are in use at Google's edge. --cloud-router-ipv6-interface-id=INTERFACE_ID - If supplied, the interface id (index within the subnet) to be used for - the Cloud Router address. The id must be in the range of 1 to 6. If a - subnet mask is supplied, it must be /125, and the subnet should either - be 0 or match the selected subnet. + The cloud-router-ipv6-interface-id field is not available. --customer-router-ipv6-interface-id=PEER_INTERFACE_ID - If supplied, the interface id (index within the subnet) to be used for - the Cloud Router address. The id must be in the range of 1 to 6. If a - subnet mask is supplied, it must be /125, and the subnet should either - be 0 or match the selected subnet. + The customer-router-ipv6-interface-id field is not available. --description=DESCRIPTION Human-readable plain-text description of attachment. diff --git a/gcloud/beta/compute/interconnects/attachments/dedicated/update b/gcloud/beta/compute/interconnects/attachments/dedicated/update index 28ba033dc..fb36ad741 100644 --- a/gcloud/beta/compute/interconnects/attachments/dedicated/update +++ b/gcloud/beta/compute/interconnects/attachments/dedicated/update @@ -52,26 +52,13 @@ FLAGS 50 Gbit/s --candidate-ipv6-subnets=[IPV6_SUBNET,...] - Up to 16 candidate prefixes that control the allocation of - cloudRouterIpv6Address and customerRouterIpv6Address for this - attachment. Each prefix must be in the Global Unique Address (GUA) - space. It is highly recommended that it be in a range owned by the - requestor. A GUA in a range owned by Google will cause the request to - fail. Google will select an available prefix from the supplied - candidates or fail the request. If not supplied, a /125 from a - Google-owned GUA block will be selected. + The candididate-ipv6-subnets field is not available. --cloud-router-ipv6-interface-id=INTERFACE_ID - If supplied, the interface id (index within the subnet) to be used for - the Cloud Router address. The id must be in the range of 1 to 6. If a - subnet mask is supplied, it must be /125, and the subnet should either - be 0 or match the selected subnet. + The cloud-router-ipv6-interface-id field is not available. --customer-router-ipv6-interface-id=PEER_INTERFACE_ID - If supplied, the interface id (index within the subnet) to be used for - the Cloud Router address. The id must be in the range of 1 to 6. If a - subnet mask is supplied, it must be /125, and the subnet should either - be 0 or match the selected subnet. + The customer-router-ipv6-interface-id field is not available. --description=DESCRIPTION Human-readable plain-text description of attachment. diff --git a/gcloud/beta/compute/scp b/gcloud/beta/compute/scp index 76f320353..46df6952f 100644 --- a/gcloud/beta/compute/scp +++ b/gcloud/beta/compute/scp @@ -52,6 +52,19 @@ EXAMPLES $ gcloud beta compute scp ~/localtest.txt ~/localtest2.txt \ example-instance:~/narnia + Remote Windows-based virtual machines require you to provide a path using + backslash notation: + + $ gcloud beta compute scp ~/localtest.txt ~/localtest2.txt \ + example-windows-instance:"C:\Users\Public" + + Paths for remote Windows-based virtual machines which contain spaces in + directory name should be appropriately protected with a pair of nested + single and double quotes: + + $ gcloud beta compute scp ~/localtest.txt \ + 'example-windows-instance:"C:\Users\Public\Test Folder"' + If the zone cannot be determined, you will be prompted for it. Use the --zone flag to avoid being prompted: diff --git a/gcloud/beta/compute/target-http-proxies/create b/gcloud/beta/compute/target-http-proxies/create index 09fe18f65..04a5965fe 100644 --- a/gcloud/beta/compute/target-http-proxies/create +++ b/gcloud/beta/compute/target-http-proxies/create @@ -3,7 +3,9 @@ NAME SYNOPSIS gcloud beta compute target-http-proxies create NAME --url-map=URL_MAP - [--description=DESCRIPTION] [--global | --region=REGION] + [--description=DESCRIPTION] + [--http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC] + [--global | --region=REGION] [--global-url-map | --url-map-region=URL_MAP_REGION] [GCLOUD_WIDE_FLAG ...] @@ -47,6 +49,13 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional, textual description for the target HTTP proxy. + --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC + Represents the maximum amount of time that a TCP connection can be idle + between the (downstream) client and the target HTTP proxy. If an HTTP + keepalive timeout is not specified, the default value is 610 seconds. + For global external HTTP(S) load balancer, the minimum allowed value is + 5 seconds and the maximum allowed value is 1200 seconds. + At most one of these can be specified: --global diff --git a/gcloud/beta/compute/target-http-proxies/update b/gcloud/beta/compute/target-http-proxies/update index e3019c165..18300a6b8 100644 --- a/gcloud/beta/compute/target-http-proxies/update +++ b/gcloud/beta/compute/target-http-proxies/update @@ -3,6 +3,8 @@ NAME SYNOPSIS gcloud beta compute target-http-proxies update NAME --url-map=URL_MAP + [--clear-http-keep-alive-timeout-sec + | --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC] [--global | --region=REGION] [--global-url-map | --url-map-region=URL_MAP_REGION] [GCLOUD_WIDE_FLAG ...] @@ -39,6 +41,19 @@ REQUIRED FLAGS referring to, you must first delete the target HTTP proxy. OPTIONAL FLAGS + At most one of these can be specified: + + --clear-http-keep-alive-timeout-sec + Clears the previously configured HTTP keepalive timeout. + + --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC + Represents the maximum amount of time that a TCP connection can be + idle between the (downstream) client and the target HTTP proxy. If an + HTTP keepalive timeout is not specified, the default value is 610 + seconds. For global external HTTP(S) load balancer, the minimum + allowed value is 5 seconds and the maximum allowed value is 1200 + seconds. + At most one of these can be specified: --global diff --git a/gcloud/beta/compute/target-https-proxies/create b/gcloud/beta/compute/target-https-proxies/create index e68d5ac0d..a471b7969 100644 --- a/gcloud/beta/compute/target-https-proxies/create +++ b/gcloud/beta/compute/target-https-proxies/create @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta compute target-https-proxies create NAME --url-map=URL_MAP [--certificate-map=CERTIFICATE_MAP] [--description=DESCRIPTION] + [--http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC] [--quic-override=QUIC_OVERRIDE; default="NONE"] [--ssl-policy=SSL_POLICY] [--certificate-manager-certificates=[CERTIFICATE_MANAGER_CERTIFICATES, @@ -78,6 +79,13 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional, textual description for the target HTTPS proxy. + --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC + Represents the maximum amount of time that a TCP connection can be idle + between the (downstream) client and the target HTTP proxy. If an HTTP + keepalive timeout is not specified, the default value is 610 seconds. + For global external HTTP(S) load balancer, the minimum allowed value is + 5 seconds and the maximum allowed value is 1200 seconds. + --quic-override=QUIC_OVERRIDE; default="NONE" Controls whether load balancer may negotiate QUIC with clients. QUIC is a new transport which reduces latency compared to that of TCP. See diff --git a/gcloud/beta/compute/target-https-proxies/update b/gcloud/beta/compute/target-https-proxies/update index fc7e8796c..1967204d0 100644 --- a/gcloud/beta/compute/target-https-proxies/update +++ b/gcloud/beta/compute/target-https-proxies/update @@ -10,6 +10,8 @@ SYNOPSIS | --ssl-certificates=SSL_CERTIFICATE,[...] --global-ssl-certificates | --ssl-certificates-region=SSL_CERTIFICATES_REGION | --certificate-map=CERTIFICATE_MAP | --clear-certificate-map] + [--clear-http-keep-alive-timeout-sec + | --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC] [--clear-ssl-policy | --ssl-policy=SSL_POLICY --global-ssl-policy | --ssl-policy-region=SSL_POLICY_REGION] [--global | --region=REGION] [--global-url-map | --url-map-region=URL_MAP_REGION] @@ -160,6 +162,19 @@ FLAGS --clear-certificate-map Removes any attached certificate map from the HTTPS proxy. + At most one of these can be specified: + + --clear-http-keep-alive-timeout-sec + Clears the previously configured HTTP keepalive timeout. + + --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC + Represents the maximum amount of time that a TCP connection can be + idle between the (downstream) client and the target HTTP proxy. If an + HTTP keepalive timeout is not specified, the default value is 610 + seconds. For global external HTTP(S) load balancer, the minimum + allowed value is 5 seconds and the maximum allowed value is 1200 + seconds. + At most one of these can be specified: --clear-ssl-policy diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 9f3248dbc..9cc09aafe 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -24,8 +24,8 @@ SYNOPSIS [--no-enable-autoupgrade] [--enable-cloud-logging] [--enable-cloud-monitoring] [--enable-cloud-run-alpha] [--enable-confidential-nodes] [--enable-cost-allocation] - [--enable-dataplane-v2] [--enable-fleet] [--enable-gke-oidc] - [--enable-google-cloud-access] [--enable-gvnic] + [--enable-dataplane-v2] [--enable-fleet] [--enable-fqdn-network-policy] + [--enable-gke-oidc] [--enable-google-cloud-access] [--enable-gvnic] [--enable-identity-service] [--enable-image-streaming] [--enable-intra-node-visibility] [--enable-ip-alias] [--enable-kubernetes-alpha] @@ -420,6 +420,10 @@ FLAGS different project, please use --fleet-project=FLEET_HOST_PROJECT. Example: $ gcloud beta container clusters create --enable-fleet + --enable-fqdn-network-policy + Enable FQDN Network Policies on the cluster. FQDN Network Policies are + disabled by default. + --enable-gke-oidc (DEPRECATED) Enable GKE OIDC authentication on the cluster. @@ -1174,8 +1178,9 @@ FLAGS --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE Enable Binary Authorization for this cluster. - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, MONITORING, - MONITORING_AND_PROJECT_SINGLETON_POLICY_ENFORCE, + BINAUTHZ_EVALUATION_MODE must be one of: BOUND_POLICIES, + BOUND_POLICIES_AND_PROJECT_SINGLETON_POLICY_ENFORCE, DISABLED, + MONITORING, MONITORING_AND_PROJECT_SINGLETON_POLICY_ENFORCE, PROJECT_SINGLETON_POLICY_ENFORCE. --enable-binauthz diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 5877df1e8..acab8d7c8 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -272,8 +272,9 @@ FLAGS --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE Enable Binary Authorization for this cluster. - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, MONITORING, - MONITORING_AND_PROJECT_SINGLETON_POLICY_ENFORCE, + BINAUTHZ_EVALUATION_MODE must be one of: BOUND_POLICIES, + BOUND_POLICIES_AND_PROJECT_SINGLETON_POLICY_ENFORCE, DISABLED, + MONITORING, MONITORING_AND_PROJECT_SINGLETON_POLICY_ENFORCE, PROJECT_SINGLETON_POLICY_ENFORCE. --binauthz-policy=BINAUTHZ_POLICY diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index 025262000..b57acf1ae 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -10,7 +10,8 @@ SYNOPSIS | --database-encryption-key=DATABASE_ENCRYPTION_KEY | --disable-database-encryption | --disable-default-snat | --disable-workload-identity | --enable-autoscaling - | --enable-cost-allocation | --enable-fleet | --enable-gke-oidc + | --enable-cost-allocation | --enable-fleet + | --enable-fqdn-network-policy | --enable-gke-oidc | --enable-google-cloud-access | --enable-identity-service | --enable-image-streaming | --enable-intra-node-visibility | --enable-kubernetes-unstable-apis=API,[API,...] @@ -214,6 +215,10 @@ REQUIRED FLAGS different project, please use --fleet-project=FLEET_HOST_PROJECT. Example: $ gcloud beta container clusters update --enable-fleet + --enable-fqdn-network-policy + Enable FQDN Network Policies on the cluster. FQDN Network Policies + are disabled by default. + --enable-gke-oidc (DEPRECATED) Enable GKE OIDC authentication on the cluster. @@ -645,8 +650,9 @@ REQUIRED FLAGS --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE Enable Binary Authorization for this cluster. - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, MONITORING, - MONITORING_AND_PROJECT_SINGLETON_POLICY_ENFORCE, + BINAUTHZ_EVALUATION_MODE must be one of: BOUND_POLICIES, + BOUND_POLICIES_AND_PROJECT_SINGLETON_POLICY_ENFORCE, DISABLED, + MONITORING, MONITORING_AND_PROJECT_SINGLETON_POLICY_ENFORCE, PROJECT_SINGLETON_POLICY_ENFORCE. --enable-binauthz diff --git a/gcloud/beta/container/fleet/scopes/help b/gcloud/beta/container/fleet/scopes/help index c0b4a3433..f77d8c1b2 100644 --- a/gcloud/beta/container/fleet/scopes/help +++ b/gcloud/beta/container/fleet/scopes/help @@ -2,7 +2,7 @@ NAME gcloud beta container fleet scopes - manage scopes of all your GKE fleets SYNOPSIS - gcloud beta container fleet scopes COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud beta container fleet scopes GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Manage scopes of all your GKE fleets. diff --git a/gcloud/beta/container/hub/scopes/help b/gcloud/beta/container/hub/scopes/help index c278fb660..35b985453 100644 --- a/gcloud/beta/container/hub/scopes/help +++ b/gcloud/beta/container/hub/scopes/help @@ -2,7 +2,7 @@ NAME gcloud beta container hub scopes - manage scopes of all your GKE fleets SYNOPSIS - gcloud beta container hub scopes COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud beta container hub scopes GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Manage scopes of all your GKE fleets. diff --git a/gcloud/beta/datastore/databases/help b/gcloud/beta/datastore/databases/help deleted file mode 100644 index b90a62675..000000000 --- a/gcloud/beta/datastore/databases/help +++ /dev/null @@ -1,23 +0,0 @@ -NAME - gcloud beta datastore databases - manage Creation of Cloud Firestore in - Native mode Database - -SYNOPSIS - gcloud beta datastore databases COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Manage Creation of Cloud Firestore in Native mode Database. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud datastore databases - - $ gcloud alpha datastore databases - diff --git a/gcloud/beta/datastore/help b/gcloud/beta/datastore/help index ef16ee02a..9384c3930 100644 --- a/gcloud/beta/datastore/help +++ b/gcloud/beta/datastore/help @@ -30,9 +30,6 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: - databases - (BETA) Manage Creation of Cloud Firestore in Native mode Database. - indexes (BETA) Manage your Cloud Datastore indexes. diff --git a/gcloud/beta/firestore/databases/create b/gcloud/beta/firestore/databases/create index 2b1445813..c1e4a4b8a 100644 --- a/gcloud/beta/firestore/databases/create +++ b/gcloud/beta/firestore/databases/create @@ -24,10 +24,13 @@ EXAMPLES REQUIRED FLAGS --location=LOCATION - The location to create the Google Cloud Firestore Native database - within. Available locations are listed at + The location to operate on. Available locations are listed at https://cloud.google.com/firestore/docs/locations. + For example, to operate on location us-east1: + + $ gcloud beta firestore databases create --location='us-east1' + OPTIONAL FLAGS --database=DATABASE; default="(default)" The ID to use for the database, which will become the final component diff --git a/gcloud/beta/functions/add-invoker-policy-binding b/gcloud/beta/functions/add-invoker-policy-binding index 8e3a54ddc..9a9455b39 100644 --- a/gcloud/beta/functions/add-invoker-policy-binding +++ b/gcloud/beta/functions/add-invoker-policy-binding @@ -10,8 +10,8 @@ DESCRIPTION (BETA) This command applies to Cloud Functions 2nd gen only. EXAMPLES - To add the invoker policy binding for FUNCTION-1 from role ROLE-1 for - member MEMBER-1 run: + To add the invoker role policy binding for FUNCTION-1 for member MEMBER-1 + run: $ gcloud beta functions add-invoker-policy-binding FUNCTION-1 \ --member=MEMBER-1 diff --git a/gcloud/beta/functions/remove-invoker-policy-binding b/gcloud/beta/functions/remove-invoker-policy-binding index 3d17ce532..1361b524a 100644 --- a/gcloud/beta/functions/remove-invoker-policy-binding +++ b/gcloud/beta/functions/remove-invoker-policy-binding @@ -10,8 +10,8 @@ DESCRIPTION (BETA) This command applies to Cloud Functions 2nd gen only. EXAMPLES - To remove the invoker policy binding for FUNCTION-1 from role ROLE-1 for - member MEMBER-1 run: + To remove the invoker role policy binding for FUNCTION-1 for member + MEMBER-1 run: $ gcloud beta functions remove-invoker-policy-binding FUNCTION-1 \ --member=MEMBER-1 diff --git a/gcloud/beta/kms/inventory/get-protected-resources-summary b/gcloud/beta/kms/inventory/get-protected-resources-summary index e8c96147e..bfd25794f 100644 --- a/gcloud/beta/kms/inventory/get-protected-resources-summary +++ b/gcloud/beta/kms/inventory/get-protected-resources-summary @@ -11,9 +11,9 @@ DESCRIPTION (BETA) gcloud beta kms inventory get-protected-resources-summary returns a summary of the resources a key is protecting. - The summary includes: How many projects contain protected resources How - many protected resources there are What types of protected resources The - count for each type of protected resource + The summary includes how many projects contain protected resources, how + many protected resources there are, what are the types of protected + resources, and the count for each type of protected resource. EXAMPLES To view the summary of protected resources for the key puppy, run: @@ -67,8 +67,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 kms inventory get-protected-resources-summary $ gcloud alpha kms inventory get-protected-resources-summary diff --git a/gcloud/beta/kms/inventory/help b/gcloud/beta/kms/inventory/help index e31071c83..c29214493 100644 --- a/gcloud/beta/kms/inventory/help +++ b/gcloud/beta/kms/inventory/help @@ -26,8 +26,10 @@ COMMANDS (BETA) Searches the resources protected by a key. 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 kms inventory $ gcloud alpha kms inventory diff --git a/gcloud/beta/kms/inventory/list-keys b/gcloud/beta/kms/inventory/list-keys index 206857897..9d956d22e 100644 --- a/gcloud/beta/kms/inventory/list-keys +++ b/gcloud/beta/kms/inventory/list-keys @@ -60,8 +60,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 kms inventory list-keys $ gcloud alpha kms inventory list-keys diff --git a/gcloud/beta/kms/inventory/search-protected-resources b/gcloud/beta/kms/inventory/search-protected-resources index 69754996f..b48803653 100644 --- a/gcloud/beta/kms/inventory/search-protected-resources +++ b/gcloud/beta/kms/inventory/search-protected-resources @@ -101,8 +101,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 kms inventory search-protected-resources $ gcloud alpha kms inventory search-protected-resources diff --git a/gcloud/beta/logging/sinks/create b/gcloud/beta/logging/sinks/create index d5ffad477..2712f9842 100644 --- a/gcloud/beta/logging/sinks/create +++ b/gcloud/beta/logging/sinks/create @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud beta logging sinks create SINK_NAME DESTINATION + [--custom-writer-identity=SERVICE_ACCOUNT_EMAIL] [--description=DESCRIPTION] [--disabled] [--exclusion=[description=DESCRIPTION], [disabled=DISABLED],[filter=FILTER],[name=NAME]] [--include-children] @@ -70,6 +71,11 @@ POSITIONAL ARGUMENTS The destination for the sink. FLAGS + --custom-writer-identity=SERVICE_ACCOUNT_EMAIL + Writer identity for the sink. This flag can only be used if the + destination is a log bucket in a different project. The writer identity + is automatically generated when it is not provided for a sink. + --description=DESCRIPTION Description of the sink. diff --git a/gcloud/beta/logging/sinks/update b/gcloud/beta/logging/sinks/update index d3d9b1b50..ba4ce50cc 100644 --- a/gcloud/beta/logging/sinks/update +++ b/gcloud/beta/logging/sinks/update @@ -5,6 +5,7 @@ SYNOPSIS gcloud beta logging sinks update SINK_NAME [DESTINATION] [--add-exclusion=[description=DESCRIPTION], [disabled=DISABLED],[filter=FILTER],[name=NAME]] [--clear-exclusions] + [--custom-writer-identity=SERVICE_ACCOUNT_EMAIL] [--description=DESCRIPTION] [--disabled] [--log-filter=LOG_FILTER] [--remove-exclusions=[EXCLUSION ID,...]] [--update-exclusion=[description=DESCRIPTION], @@ -65,6 +66,11 @@ FLAGS --clear-exclusions Remove all logging exclusions from the sink. + --custom-writer-identity=SERVICE_ACCOUNT_EMAIL + Writer identity for the sink. This flag can only be used if the + destination is a log bucket in a different project. The writer identity + is automatically generated when it is not provided for a sink. + --description=DESCRIPTION Description of the sink. diff --git a/gcloud/beta/pubsub/subscriptions/create b/gcloud/beta/pubsub/subscriptions/create index bddb7b5b3..5c2eb92fa 100644 --- a/gcloud/beta/pubsub/subscriptions/create +++ b/gcloud/beta/pubsub/subscriptions/create @@ -18,6 +18,7 @@ SYNOPSIS [--dead-letter-topic=DEAD_LETTER_TOPIC : --dead-letter-topic-project=DEAD_LETTER_TOPIC_PROJECT]] [--max-retry-delay=MAX_RETRY_DELAY --min-retry-delay=MIN_RETRY_DELAY] + [--push-no-wrapper : --push-no-wrapper-write-metadata] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -219,6 +220,20 @@ OPTIONAL FLAGS of "s", "m", "h", and "d" for seconds, minutes, hours, and days, respectively. If the unit is omitted, seconds is assumed. + NoWrapper Config Options. + + --push-no-wrapper + When set, the message data is delivered directly as the HTTP body. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --push-no-wrapper-write-metadata + When true, writes the Pub/Sub message metadata to + x-goog-pubsub-: headers of the HTTP request. Writes the + Pub/Sub message attributes to : headers of the HTTP + request. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/pubsub/subscriptions/modify-push-config b/gcloud/beta/pubsub/subscriptions/modify-push-config index 0d7ab2efc..aa3dec754 100644 --- a/gcloud/beta/pubsub/subscriptions/modify-push-config +++ b/gcloud/beta/pubsub/subscriptions/modify-push-config @@ -7,6 +7,7 @@ SYNOPSIS --push-endpoint=PUSH_ENDPOINT [--push-auth-service-account=SERVICE_ACCOUNT_EMAIL] [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] + [--push-no-wrapper : --push-no-wrapper-write-metadata] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -46,6 +47,20 @@ OPTIONAL FLAGS Audience used in the generated Open ID Connect token for authenticated push. If not specified, it will be set to the push-endpoint. + NoWrapper Config Options. + + --push-no-wrapper + When set, the message data is delivered directly as the HTTP body. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --push-no-wrapper-write-metadata + When true, writes the Pub/Sub message metadata to + x-goog-pubsub-: headers of the HTTP request. Writes the + Pub/Sub message attributes to : headers of the HTTP + request. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/pubsub/subscriptions/update b/gcloud/beta/pubsub/subscriptions/update index ffbf8227c..8aa626622 100644 --- a/gcloud/beta/pubsub/subscriptions/update +++ b/gcloud/beta/pubsub/subscriptions/update @@ -18,6 +18,8 @@ SYNOPSIS [--dead-letter-topic=DEAD_LETTER_TOPIC : --dead-letter-topic-project=DEAD_LETTER_TOPIC_PROJECT]] [--clear-labels | --remove-labels=[KEY,...]] + [--clear-push-no-wrapper-config + | [--push-no-wrapper : --push-no-wrapper-write-metadata]] [--clear-retry-policy | --max-retry-delay=MAX_RETRY_DELAY --min-retry-delay=MIN_RETRY_DELAY] [GCLOUD_WIDE_FLAG ...] @@ -194,6 +196,25 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + At most one of these can be specified: + + --clear-push-no-wrapper-config + If set, clear the NoWrapper config from the subscription. + + NoWrapper Config Options. + + --push-no-wrapper + When set, the message data is delivered directly as the HTTP body. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --push-no-wrapper-write-metadata + When true, writes the Pub/Sub message metadata to + x-goog-pubsub-: headers of the HTTP request. Writes the + Pub/Sub message attributes to : headers of the HTTP + request. + At most one of these can be specified: --clear-retry-policy diff --git a/gcloud/compute/disks/update b/gcloud/compute/disks/update index 8c098eb74..8a1377447 100644 --- a/gcloud/compute/disks/update +++ b/gcloud/compute/disks/update @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud compute disks update DISK_NAME [--provisioned-iops=PROVISIONED_IOPS] - [--provisioned-throughput=PROVISIONED_THROUGHPUT] + [--provisioned-throughput=PROVISIONED_THROUGHPUT] [--size=SIZE] [--update-labels=[KEY=VALUE,...]] [--clear-architecture | --update-architecture=UPDATE_ARCHITECTURE] [--clear-labels | --remove-labels=[KEY,...]] @@ -44,6 +44,12 @@ FLAGS Provisioned throughput of disk to update. The throughput unit is MB per sec. + --size=SIZE + Size of the disks. The value must be a whole number followed by a size + unit of GB for gigabyte, or TB for terabyte. If no size unit is + specified, GB is assumed. For details about disk size limits, refer to: + https://cloud.google.com/compute/docs/disks + --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index 538e93dc7..8bbecd716 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -110,10 +110,8 @@ FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new diff --git a/gcloud/compute/instance-templates/create-with-container b/gcloud/compute/instance-templates/create-with-container index ced5e647a..e204179d6 100644 --- a/gcloud/compute/instance-templates/create-with-container +++ b/gcloud/compute/instance-templates/create-with-container @@ -99,10 +99,8 @@ FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index c24b667f4..362aaff03 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -160,10 +160,8 @@ OPTIONAL FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index dfc62e86f..58eda4dc1 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -160,10 +160,8 @@ FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index 742dfa64e..a9ea52d57 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -121,10 +121,8 @@ FLAGS boot disk is being created (as opposed to mounting an existing persistent disk). The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for - terabyte. For example, 10GB will produce a 10 gigabyte disk. The - minimum size a boot disk can have is 10 GB. Disk size must be a - multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR - partition table limitations. Default size unit is GB. + terabyte. For example, 10GB will produce a 10 gigabyte disk. Disk size + must be a multiple of 1 GB. Default size unit is GB. --boot-disk-type=BOOT_DISK_TYPE The type of the boot disk. This option can only be specified if a new diff --git a/gcloud/compute/interconnects/attachments/dedicated/create b/gcloud/compute/interconnects/attachments/dedicated/create index 3cd7812eb..b9f2d9548 100644 --- a/gcloud/compute/interconnects/attachments/dedicated/create +++ b/gcloud/compute/interconnects/attachments/dedicated/create @@ -61,14 +61,7 @@ OPTIONAL FLAGS 50 Gbit/s --candidate-ipv6-subnets=[IPV6_SUBNET,...] - Up to 16 candidate prefixes that control the allocation of - cloudRouterIpv6Address and customerRouterIpv6Address for this - attachment. Each prefix must be in the Global Unique Address (GUA) - space. It is highly recommended that it be in a range owned by the - requestor. A GUA in a range owned by Google will cause the request to - fail. Google will select an available prefix from the supplied - candidates or fail the request. If not supplied, a /125 from a - Google-owned GUA block will be selected. + The candididate-ipv6-subnets field is not available. --candidate-subnets=[SUBNET,...] Up to 16 candidate prefixes that can be used to restrict the allocation @@ -81,16 +74,10 @@ OPTIONAL FLAGS request fails if all candidate subnets are in use at Google's edge. --cloud-router-ipv6-interface-id=INTERFACE_ID - If supplied, the interface id (index within the subnet) to be used for - the Cloud Router address. The id must be in the range of 1 to 6. If a - subnet mask is supplied, it must be /125, and the subnet should either - be 0 or match the selected subnet. + The cloud-router-ipv6-interface-id field is not available. --customer-router-ipv6-interface-id=PEER_INTERFACE_ID - If supplied, the interface id (index within the subnet) to be used for - the Cloud Router address. The id must be in the range of 1 to 6. If a - subnet mask is supplied, it must be /125, and the subnet should either - be 0 or match the selected subnet. + The customer-router-ipv6-interface-id field is not available. --description=DESCRIPTION Human-readable plain-text description of attachment. diff --git a/gcloud/compute/interconnects/attachments/dedicated/update b/gcloud/compute/interconnects/attachments/dedicated/update index 1682cfcaa..6d7691179 100644 --- a/gcloud/compute/interconnects/attachments/dedicated/update +++ b/gcloud/compute/interconnects/attachments/dedicated/update @@ -50,26 +50,13 @@ FLAGS 50 Gbit/s --candidate-ipv6-subnets=[IPV6_SUBNET,...] - Up to 16 candidate prefixes that control the allocation of - cloudRouterIpv6Address and customerRouterIpv6Address for this - attachment. Each prefix must be in the Global Unique Address (GUA) - space. It is highly recommended that it be in a range owned by the - requestor. A GUA in a range owned by Google will cause the request to - fail. Google will select an available prefix from the supplied - candidates or fail the request. If not supplied, a /125 from a - Google-owned GUA block will be selected. + The candididate-ipv6-subnets field is not available. --cloud-router-ipv6-interface-id=INTERFACE_ID - If supplied, the interface id (index within the subnet) to be used for - the Cloud Router address. The id must be in the range of 1 to 6. If a - subnet mask is supplied, it must be /125, and the subnet should either - be 0 or match the selected subnet. + The cloud-router-ipv6-interface-id field is not available. --customer-router-ipv6-interface-id=PEER_INTERFACE_ID - If supplied, the interface id (index within the subnet) to be used for - the Cloud Router address. The id must be in the range of 1 to 6. If a - subnet mask is supplied, it must be /125, and the subnet should either - be 0 or match the selected subnet. + The customer-router-ipv6-interface-id field is not available. --description=DESCRIPTION Human-readable plain-text description of attachment. diff --git a/gcloud/compute/scp b/gcloud/compute/scp index c8df0bfa0..1eec19245 100644 --- a/gcloud/compute/scp +++ b/gcloud/compute/scp @@ -51,6 +51,19 @@ EXAMPLES $ gcloud compute scp ~/localtest.txt ~/localtest2.txt \ example-instance:~/narnia + Remote Windows-based virtual machines require you to provide a path using + backslash notation: + + $ gcloud compute scp ~/localtest.txt ~/localtest2.txt \ + example-windows-instance:"C:\Users\Public" + + Paths for remote Windows-based virtual machines which contain spaces in + directory name should be appropriately protected with a pair of nested + single and double quotes: + + $ gcloud compute scp ~/localtest.txt \ + 'example-windows-instance:"C:\Users\Public\Test Folder"' + If the zone cannot be determined, you will be prompted for it. Use the --zone flag to avoid being prompted: diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 0b70bd814..d780a98d8 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -1055,7 +1055,8 @@ FLAGS --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE Enable Binary Authorization for this cluster. - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, + BINAUTHZ_EVALUATION_MODE must be one of: BOUND_POLICIES, + BOUND_POLICIES_AND_PROJECT_SINGLETON_POLICY_ENFORCE, DISABLED, PROJECT_SINGLETON_POLICY_ENFORCE. --enable-binauthz diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 2c5eaeb79..6667f56e4 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -68,7 +68,8 @@ FLAGS --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE Enable Binary Authorization for this cluster. - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, + BINAUTHZ_EVALUATION_MODE must be one of: BOUND_POLICIES, + BOUND_POLICIES_AND_PROJECT_SINGLETON_POLICY_ENFORCE, DISABLED, PROJECT_SINGLETON_POLICY_ENFORCE. --boot-disk-kms-key=BOOT_DISK_KMS_KEY diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index c62667a44..f793dfc2a 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -551,7 +551,8 @@ REQUIRED FLAGS --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE Enable Binary Authorization for this cluster. - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, + BINAUTHZ_EVALUATION_MODE must be one of: BOUND_POLICIES, + BOUND_POLICIES_AND_PROJECT_SINGLETON_POLICY_ENFORCE, DISABLED, PROJECT_SINGLETON_POLICY_ENFORCE. --enable-binauthz diff --git a/gcloud/datastore/databases/help b/gcloud/datastore/databases/help deleted file mode 100644 index 05794c8ba..000000000 --- a/gcloud/datastore/databases/help +++ /dev/null @@ -1,22 +0,0 @@ -NAME - gcloud datastore databases - manage Creation of Cloud Firestore in Native - mode Database - -SYNOPSIS - gcloud datastore databases COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - Manage Creation of Cloud Firestore in Native mode Database. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -NOTES - These variants are also available: - - $ gcloud alpha datastore databases - - $ gcloud beta datastore databases - diff --git a/gcloud/datastore/help b/gcloud/datastore/help index 5231cb7ec..77440f9cd 100644 --- a/gcloud/datastore/help +++ b/gcloud/datastore/help @@ -30,9 +30,6 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: - databases - Manage Creation of Cloud Firestore in Native mode Database. - indexes Manage your Cloud Datastore indexes. diff --git a/gcloud/firestore/databases/create b/gcloud/firestore/databases/create index f24db2965..0a3423396 100644 --- a/gcloud/firestore/databases/create +++ b/gcloud/firestore/databases/create @@ -24,10 +24,13 @@ EXAMPLES REQUIRED FLAGS --location=LOCATION - The location to create the Google Cloud Firestore Native database - within. Available locations are listed at + The location to operate on. Available locations are listed at https://cloud.google.com/firestore/docs/locations. + For example, to operate on location us-east1: + + $ gcloud firestore databases create --location='us-east1' + OPTIONAL FLAGS --database=DATABASE; default="(default)" The ID to use for the database, which will become the final component diff --git a/gcloud/functions/add-invoker-policy-binding b/gcloud/functions/add-invoker-policy-binding index d64238785..b76acbb93 100644 --- a/gcloud/functions/add-invoker-policy-binding +++ b/gcloud/functions/add-invoker-policy-binding @@ -10,8 +10,8 @@ DESCRIPTION This command applies to Cloud Functions 2nd gen only. EXAMPLES - To add the invoker policy binding for FUNCTION-1 from role ROLE-1 for - member MEMBER-1 run: + To add the invoker role policy binding for FUNCTION-1 for member MEMBER-1 + run: $ gcloud functions add-invoker-policy-binding FUNCTION-1 \ --member=MEMBER-1 diff --git a/gcloud/functions/remove-invoker-policy-binding b/gcloud/functions/remove-invoker-policy-binding index 8213dc3e8..666fbb8ec 100644 --- a/gcloud/functions/remove-invoker-policy-binding +++ b/gcloud/functions/remove-invoker-policy-binding @@ -10,8 +10,8 @@ DESCRIPTION This command applies to Cloud Functions 2nd gen only. EXAMPLES - To remove the invoker policy binding for FUNCTION-1 from role ROLE-1 for - member MEMBER-1 run: + To remove the invoker role policy binding for FUNCTION-1 for member + MEMBER-1 run: $ gcloud functions remove-invoker-policy-binding FUNCTION-1 \ --member=MEMBER-1 diff --git a/gcloud/kms/help b/gcloud/kms/help index 414a71ba9..98e68cc09 100644 --- a/gcloud/kms/help +++ b/gcloud/kms/help @@ -37,6 +37,9 @@ GROUPS import-jobs Create and manage import jobs. + inventory + Manages the KMS Inventory and Key Tracking commands. + keyrings Create and manage keyrings. diff --git a/gcloud/kms/inventory/get-protected-resources-summary b/gcloud/kms/inventory/get-protected-resources-summary new file mode 100644 index 000000000..2559c9600 --- /dev/null +++ b/gcloud/kms/inventory/get-protected-resources-summary @@ -0,0 +1,75 @@ +NAME + gcloud kms inventory get-protected-resources-summary - gets the protected + resources summary + +SYNOPSIS + gcloud kms inventory get-protected-resources-summary + (--keyname=KEYNAME : --keyring=KEYRING --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud kms inventory get-protected-resources-summary returns a summary of + the resources a key is protecting. + + The summary includes how many projects contain protected resources, how + many protected resources there are, what are the types of protected + resources, and the count for each type of protected resource. + +EXAMPLES + To view the summary of protected resources for the key puppy, run: + + $ gcloud kms inventory get-protected-resources-summary \ + --keyname=puppy + +REQUIRED FLAGS + Key resource - The KMS key resource. 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 can be set in other ways. + + To set the project attribute: + ◆ provide the argument --keyname on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + --keyname=KEYNAME + ID of the key or fully qualified identifier for the key. + + To set the key attribute: + ▸ provide the argument --keyname on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --keyring=KEYRING + The KMS keyring of the key. + + To set the keyring attribute: + ▸ provide the argument --keyname on the command line with a fully + specified name; + ▸ provide the argument --keyring on the command line. + + --location=LOCATION + The Google Cloud location for the key. + + To set the location attribute: + ▸ provide the argument --keyname on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +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 + These variants are also available: + + $ gcloud alpha kms inventory get-protected-resources-summary + + $ gcloud beta kms inventory get-protected-resources-summary + diff --git a/gcloud/kms/inventory/help b/gcloud/kms/inventory/help new file mode 100644 index 000000000..a45c7a1bf --- /dev/null +++ b/gcloud/kms/inventory/help @@ -0,0 +1,33 @@ +NAME + gcloud kms inventory - manages the KMS Inventory and Key Tracking commands + +SYNOPSIS + gcloud kms inventory COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manages the KMS Inventory and Key Tracking commands. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + get-protected-resources-summary + Gets the protected resources summary. + + list-keys + Lists the keys in a project. + + search-protected-resources + Searches the resources protected by a key. + +NOTES + These variants are also available: + + $ gcloud alpha kms inventory + + $ gcloud beta kms inventory + diff --git a/gcloud/kms/inventory/list-keys b/gcloud/kms/inventory/list-keys new file mode 100644 index 000000000..b373f4d55 --- /dev/null +++ b/gcloud/kms/inventory/list-keys @@ -0,0 +1,67 @@ +NAME + gcloud kms inventory list-keys - lists the keys in a project + +SYNOPSIS + gcloud kms inventory list-keys [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud kms inventory list-keys lists the keys in the specified project. + +EXAMPLES + To view the keys in the default project, run: + + $ gcloud kms inventory list-keys + + To view the keys in project jellyfish, run: + + $ gcloud kms inventory list-keys --project=jellyfish + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --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. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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 + These variants are also available: + + $ gcloud alpha kms inventory list-keys + + $ gcloud beta kms inventory list-keys + diff --git a/gcloud/kms/inventory/search-protected-resources b/gcloud/kms/inventory/search-protected-resources new file mode 100644 index 000000000..274074fb8 --- /dev/null +++ b/gcloud/kms/inventory/search-protected-resources @@ -0,0 +1,108 @@ +NAME + gcloud kms inventory search-protected-resources - searches the resources + protected by a key + +SYNOPSIS + gcloud kms inventory search-protected-resources --scope=ORGANIZATION_ID + (--keyname=KEYNAME : --keyring=KEYRING --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud kms inventory search-protected-resources returns a list of the + resources a key is protecting within the specified organization. + +EXAMPLES + To view the protected resources for the key puppy and organization number + 1234 run: + + $ gcloud kms inventory search-protected-resources --keyname=puppy \ + --scope=1234 + +REQUIRED FLAGS + --scope=ORGANIZATION_ID + Organization ID. + + Key resource - The KMS key resource. 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 can be set in other ways. + + To set the project attribute: + ◆ provide the argument --keyname on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + --keyname=KEYNAME + ID of the key or fully qualified identifier for the key. + + To set the key attribute: + ▸ provide the argument --keyname on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --keyring=KEYRING + The KMS keyring of the key. + + To set the keyring attribute: + ▸ provide the argument --keyname on the command line with a fully + specified name; + ▸ provide the argument --keyring on the command line. + + --location=LOCATION + The Google Cloud location for the key. + + To set the location attribute: + ▸ provide the argument --keyname on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --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. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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 + These variants are also available: + + $ gcloud alpha kms inventory search-protected-resources + + $ gcloud beta kms inventory search-protected-resources + diff --git a/gcloud/logging/sinks/create b/gcloud/logging/sinks/create index 676f68129..6dd0e46e2 100644 --- a/gcloud/logging/sinks/create +++ b/gcloud/logging/sinks/create @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud logging sinks create SINK_NAME DESTINATION + [--custom-writer-identity=SERVICE_ACCOUNT_EMAIL] [--description=DESCRIPTION] [--disabled] [--exclusion=[description=DESCRIPTION], [disabled=DISABLED],[filter=FILTER],[name=NAME]] [--include-children] @@ -70,6 +71,11 @@ POSITIONAL ARGUMENTS The destination for the sink. FLAGS + --custom-writer-identity=SERVICE_ACCOUNT_EMAIL + Writer identity for the sink. This flag can only be used if the + destination is a log bucket in a different project. The writer identity + is automatically generated when it is not provided for a sink. + --description=DESCRIPTION Description of the sink. diff --git a/gcloud/logging/sinks/update b/gcloud/logging/sinks/update index 1fda3a08e..04eb55208 100644 --- a/gcloud/logging/sinks/update +++ b/gcloud/logging/sinks/update @@ -5,6 +5,7 @@ SYNOPSIS gcloud logging sinks update SINK_NAME [DESTINATION] [--add-exclusion=[description=DESCRIPTION], [disabled=DISABLED],[filter=FILTER],[name=NAME]] [--clear-exclusions] + [--custom-writer-identity=SERVICE_ACCOUNT_EMAIL] [--description=DESCRIPTION] [--disabled] [--log-filter=LOG_FILTER] [--remove-exclusions=[EXCLUSION ID,...]] [--update-exclusion=[description=DESCRIPTION], @@ -64,6 +65,11 @@ FLAGS --clear-exclusions Remove all logging exclusions from the sink. + --custom-writer-identity=SERVICE_ACCOUNT_EMAIL + Writer identity for the sink. This flag can only be used if the + destination is a log bucket in a different project. The writer identity + is automatically generated when it is not provided for a sink. + --description=DESCRIPTION Description of the sink. diff --git a/gcloud/storage/buckets/add-iam-policy-binding b/gcloud/storage/buckets/add-iam-policy-binding index 8fde82a56..4c25dafa7 100644 --- a/gcloud/storage/buckets/add-iam-policy-binding +++ b/gcloud/storage/buckets/add-iam-policy-binding @@ -23,7 +23,7 @@ EXAMPLES To make objects in BUCKET publicly readable: $ gcloud storage buckets add-iam-policy-binding gs://BUCKET \ - --member=AllUsers --role=roles/storage.objectViewer + --member=allUsers --role=roles/storage.objectViewer To specify a custom role for a principal on BUCKET: