diff --git a/gcloud/_version b/gcloud/_version index 0235d9f89..0b5d0b408 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 495.0.0 -alpha 2024.09.27 -beta 2024.09.27 -bq 2.1.8 +Google Cloud SDK 496.0.0 +alpha 2024.10.04 +beta 2024.10.04 +bq 2.1.9 bundled-python3-unix 3.11.9 -core 2024.09.27 +core 2024.10.04 gcloud-crc32c 1.0.0 gsutil 5.30 diff --git a/gcloud/alpha/alloydb/clusters/help b/gcloud/alpha/alloydb/clusters/help index 983e48188..1cdbac411 100644 --- a/gcloud/alpha/alloydb/clusters/help +++ b/gcloud/alpha/alloydb/clusters/help @@ -47,6 +47,9 @@ COMMANDS update (ALPHA) Update an AlloyDB cluster within a given project and region. + upgrade + (ALPHA) Upgrade an AlloyDB cluster within a given project and region. + 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/alloydb/clusters/upgrade b/gcloud/alpha/alloydb/clusters/upgrade new file mode 100644 index 000000000..e392b2c61 --- /dev/null +++ b/gcloud/alpha/alloydb/clusters/upgrade @@ -0,0 +1,49 @@ +NAME + gcloud alpha alloydb clusters upgrade - upgrade an AlloyDB cluster within a + given project and region + +SYNOPSIS + gcloud alpha alloydb clusters upgrade CLUSTER --region=REGION + --version=VERSION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Upgrade an AlloyDB cluster within a given project and region. + +EXAMPLES + To upgrade a cluster, run: + + $ gcloud alpha alloydb clusters upgrade my-cluster \ + --region=us-central1 --version=POSTGRES_15 + +POSITIONAL ARGUMENTS + CLUSTER + AlloyDB cluster ID + +REQUIRED FLAGS + --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. + + --version=VERSION + Target database version for the upgrade. VERSION must be one of: + POSTGRES_14, POSTGRES_15, POSTGRES_16. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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/assured/workloads/create b/gcloud/alpha/assured/workloads/create index 2476fb9d3..071293643 100644 --- a/gcloud/alpha/assured/workloads/create +++ b/gcloud/alpha/assured/workloads/create @@ -90,7 +90,7 @@ REQUIRED FLAGS cjis, eu-regions-and-support, fedramp-high, fedramp-moderate, healthcare-and-life-sciences-controls, healthcare-and-life-sciences-controls-us-support, hipaa, hitrust, il2, - il4, il5, isr-regions, isr-regions-and-support, itar, + il4, il5, irs-1075, isr-regions, isr-regions-and-support, itar, jp-regions-and-support, ksa-regions-and-support-with-sovereignty-controls, regional-controls, us-regional-access. diff --git a/gcloud/alpha/bigtable/backups/create b/gcloud/alpha/bigtable/backups/create index 2ce421a59..e56f8121a 100644 --- a/gcloud/alpha/bigtable/backups/create +++ b/gcloud/alpha/bigtable/backups/create @@ -7,7 +7,8 @@ SYNOPSIS (BACKUP : --cluster=CLUSTER --instance=INSTANCE) --table=TABLE (--expiration-date=EXPIRATION_DATE | --retention-period=RETENTION_PERIOD) [--async] - [GCLOUD_WIDE_FLAG ...] + [--backup-type=BACKUP_TYPE] + [--hot-to-standard-time=HOT_TO_STANDARD_TIME] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates a backup of a Cloud Bigtable table. @@ -28,6 +29,31 @@ EXAMPLES --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ --table=TABLE_NAME --retention-period=2w + To create a hot backup 'BACKUP_NAME' from table 'TABLE_NAME' which expires + in 2 weeks from now, run: + + $ gcloud alpha bigtable backups create BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --retention-period=2w --backup-type=HOT + + To create a hot backup 'BACKUP_NAME' from table 'TABLE_NAME' which will be + converted to a standard backup at '2019-03-31T10:49:41Z' and expires in 2 + weeks from now, run: + + $ gcloud alpha bigtable backups create BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --retention-period=2w --backup-type=HOT \ + --hot-to-standard-time=2019-03-31T10:49:41Z + + To create a hot backup 'BACKUP_NAME' from table 'TABLE_NAME' which will be + converted to a standard backup in 1 week from now and expires in 2 weeks + from now, run: + + $ gcloud alpha bigtable backups create BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --retention-period=2w --backup-type=HOT \ + --hot-to-standard-time=+P1w + POSITIONAL ARGUMENTS Backup resource - The Cloud Bigtable backup to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -74,20 +100,38 @@ REQUIRED FLAGS Exactly one of these must be specified: --expiration-date=EXPIRATION_DATE - Absolute expiration time of the backup; must be at least 6 hours and - at most 90 days from the time the request is received. See $ gcloud - topic datetimes for information on date/time formats. + Absolute expiration time of the backup. From the time the request is + received, must be: + ▸ At least 6 hours in the future + ▸ At most 90 days in the future + + See $ gcloud topic datetimes for information on date/time formats. --retention-period=RETENTION_PERIOD - Retention period of the backup relative from now; must be at least 6 - hours and at most 90 days. See $ gcloud topic datetimes for - information on duration formats. + Retention period of the backup relative from now; must be: + ▸ At least 6 hours + ▸ At most 90 days + + See $ gcloud topic datetimes for information on duration formats. OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to complete. + --backup-type=BACKUP_TYPE + Type of the backup; whether the backup is a standard backup or a hot + backup. BACKUP_TYPE must be one of: backup-type-unspecified, hot, + standard. + + --hot-to-standard-time=HOT_TO_STANDARD_TIME + Time at which a hot backup will be converted to a standard backup + relative from now; must be: + ◆ At least 24 hours + + Only applies for hot backups. See $ gcloud topic datetimes for + information on date/time formats. + 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/bigtable/backups/update b/gcloud/alpha/bigtable/backups/update index 7131ee21a..d668164d3 100644 --- a/gcloud/alpha/bigtable/backups/update +++ b/gcloud/alpha/bigtable/backups/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha bigtable backups update (BACKUP : --cluster=CLUSTER --instance=INSTANCE) + [--hot-to-standard-time=HOT_TO_STANDARD_TIME] [--expiration-date=EXPIRATION_DATE | --retention-period=RETENTION_PERIOD] [GCLOUD_WIDE_FLAG ...] @@ -19,6 +20,26 @@ EXAMPLES --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ --retention-period=7d + To update the hot-to-standard time of backup 'BACKUP_NAME' to + '2019-03-31T10:49:41Z', run: + + $ gcloud alpha bigtable backups update BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --hot-to-standard-time=2019-03-31T10:49:41Z + + To update the hot-to-standard time of backup 'BACKUP_NAME' to 7 days from + now, run: + + $ gcloud alpha bigtable backups update BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --hot-to-standard-time=+P7d + + To clear the hot-to-standard time of backup 'BACKUP_NAME', run: + + $ gcloud alpha bigtable backups update BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --hot-to-standard-time='' + POSITIONAL ARGUMENTS Backup resource - Cloud Bigtable backup to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -59,6 +80,12 @@ POSITIONAL ARGUMENTS ▸ provide the argument --instance on the command line. FLAGS + --hot-to-standard-time=HOT_TO_STANDARD_TIME + Time at which a hot backup will be converted to a standard backup; must + be at least 24 hours from backup creation time. Only applies for hot + backups. See $ gcloud topic datetimes for information on date/time + formats. See $ gcloud bigtable backups describe for creation time. + At most one of these can be specified: --expiration-date=EXPIRATION_DATE diff --git a/gcloud/alpha/builds/submit b/gcloud/alpha/builds/submit index 54f777e39..fb4b66cad 100644 --- a/gcloud/alpha/builds/submit +++ b/gcloud/alpha/builds/submit @@ -99,7 +99,8 @@ FLAGS --default-buckets-behavior=DEFAULT_BUCKETS_BEHAVIOR How default buckets are setup. DEFAULT_BUCKETS_BEHAVIOR must be one of: - default-logs-bucket-behavior-unspecified, regional-user-owned-bucket. + default-logs-bucket-behavior-unspecified, legacy-bucket, + regional-user-owned-bucket. --dir=DIR Directory, relative to the source root, in which to run the build. This diff --git a/gcloud/alpha/compute/future-reservations/create b/gcloud/alpha/compute/future-reservations/create index 97d02220a..9793bb3e1 100644 --- a/gcloud/alpha/compute/future-reservations/create +++ b/gcloud/alpha/compute/future-reservations/create @@ -170,18 +170,20 @@ REQUIRED FLAGS OPTIONAL FLAGS --deployment-type=DEPLOYMENT_TYPE - Indicates if the reservation allocation strategy is static or dynamic. - DENSE refers to a fixed size and topology, with deployment expressed in - terms of blocks. FLEXIBLE indicates a non-static distribution of - capacity that can change over time. Deployment is not expressed in - blocks. DEPLOYMENT_TYPE must be one of: DENSE, FLEXIBLE. + The deployment type for the reserved capacity. DEPLOYMENT_TYPE must be + one of: + + DENSE + DENSE mode is for densely deployed reservation blocks. + FLEXIBLE + FLEXIBLE mode is for highly flexible, logical reservation blocks. --description=DESCRIPTION An optional description of the future reservation to create. --[no-]enable-opportunistic-maintenance - Indicates if this group of VMs have opportunistic maintenance enabled. - Applicable only to dense coordinated maintenance. Use + Enable or disable opportunistic maintenance. If enabled, maintenance is + performed on unused reservations whenever possible. Use --enable-opportunistic-maintenance to enable and --no-enable-opportunistic-maintenance to disable. @@ -226,9 +228,14 @@ OPTIONAL FLAGS the reservation_name or a name_prefix. --scheduling-type=SCHEDULING_TYPE - Indicates the maintenance type for this group of VMs. This will be set - on the reservation via FR, and will be inherited for reservation - blocks. SCHEDULING_TYPE must be one of: GROUPED, INDEPENDENT. + Maintenance for the reserved capacity. SCHEDULING_TYPE must be one of: + + GROUPED + In GROUPED mode, maintenance on all reserved instances + issynchronized. + INDEPENDENT + In INDEPENDENT mode, maintenance is not synchronized for this + reservation, and each instance has its own maintenance window. --zone=ZONE Zone of the future reservation to create. If not specified and the diff --git a/gcloud/alpha/compute/future-reservations/update b/gcloud/alpha/compute/future-reservations/update index cac69ac87..eeaf766b0 100644 --- a/gcloud/alpha/compute/future-reservations/update +++ b/gcloud/alpha/compute/future-reservations/update @@ -52,18 +52,20 @@ FLAGS --no-auto-delete-auto-created-reservations to disable. --deployment-type=DEPLOYMENT_TYPE - Indicates if the reservation allocation strategy is static or dynamic. - DENSE refers to a fixed size and topology, with deployment expressed in - terms of blocks. FLEXIBLE indicates a non-static distribution of - capacity that can change over time. Deployment is not expressed in - blocks. DEPLOYMENT_TYPE must be one of: DENSE, FLEXIBLE. + The deployment type for the reserved capacity. DEPLOYMENT_TYPE must be + one of: + + DENSE + DENSE mode is for densely deployed reservation blocks. + FLEXIBLE + FLEXIBLE mode is for highly flexible, logical reservation blocks. --description=DESCRIPTION An optional description of the future reservation to create. --[no-]enable-opportunistic-maintenance - Indicates if this group of VMs have opportunistic maintenance enabled. - Applicable only to dense coordinated maintenance. Use + Enable or disable opportunistic maintenance. If enabled, maintenance is + performed on unused reservations whenever possible. Use --enable-opportunistic-maintenance to enable and --no-enable-opportunistic-maintenance to disable. @@ -103,9 +105,14 @@ FLAGS the reservation_name or a name_prefix. --scheduling-type=SCHEDULING_TYPE - Indicates the maintenance type for this group of VMs. This will be set - on the reservation via FR, and will be inherited for reservation - blocks. SCHEDULING_TYPE must be one of: GROUPED, INDEPENDENT. + Maintenance for the reserved capacity. SCHEDULING_TYPE must be one of: + + GROUPED + In GROUPED mode, maintenance on all reserved instances + issynchronized. + INDEPENDENT + In INDEPENDENT mode, maintenance is not synchronized for this + reservation, and each instance has its own maintenance window. --total-count=TOTAL_COUNT The total number of instances for which capacity assurance is requested diff --git a/gcloud/alpha/compute/instances/network-interfaces/add b/gcloud/alpha/compute/instances/network-interfaces/add index d21c82876..0f8cbd522 100644 --- a/gcloud/alpha/compute/instances/network-interfaces/add +++ b/gcloud/alpha/compute/instances/network-interfaces/add @@ -105,8 +105,7 @@ FLAGS Public internet quality. --parent-nic-name=PARENT_NIC_NAME - Name of the parent network interface of a VLAN based network interface. - If this field is specified, vlan must be set. + Name of the parent network interface of a dynamic network interface. --private-network-ip=PRIVATE_NETWORK_IP Specifies the RFC1918 IP to assign to the network interface. The IP @@ -125,9 +124,8 @@ FLAGS Specifies the subnetwork this network interface belongs to. --vlan=VLAN - VLAN tag of a VLAN based network interface, must be in range from 2 to - 4094 inclusively. This field is mandatory if the parent network - interface name is set. + VLAN tag of a dynamic network interface, must be in range from 2 to + 4094 inclusively. --zone=ZONE Zone of the instance to operate on. If not specified, you might be diff --git a/gcloud/alpha/compute/instant-snapshots/create b/gcloud/alpha/compute/instant-snapshots/create index 7078d091e..57ffe5a54 100644 --- a/gcloud/alpha/compute/instant-snapshots/create +++ b/gcloud/alpha/compute/instant-snapshots/create @@ -9,8 +9,8 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha compute instant-snapshots create creates an instant - snapshot of persistent disk. Instant snapshots are useful for backing up - persistent disk data. + snapshot of a disk. Instant snapshots are useful for backing up the disk + data. EXAMPLES To create an instant snapshot 'my-instant-snap' from a disk 'my-disk' in diff --git a/gcloud/alpha/compute/interconnects/attachments/delete b/gcloud/alpha/compute/interconnects/attachments/delete index ab27dfb5e..d3e79dd3c 100644 --- a/gcloud/alpha/compute/interconnects/attachments/delete +++ b/gcloud/alpha/compute/interconnects/attachments/delete @@ -1,6 +1,6 @@ NAME - gcloud alpha compute interconnects attachments delete - delete - interconnects + gcloud alpha compute interconnects attachments delete - delete Compute + Engine interconnect attachments SYNOPSIS gcloud alpha compute interconnects attachments delete NAME [NAME ...] @@ -8,7 +8,7 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha compute interconnects attachments delete deletes - Compute Engine interconnect attachment. + Compute Engine interconnect attachments. POSITIONAL ARGUMENTS NAME [NAME ...] diff --git a/gcloud/alpha/compute/interconnects/attachments/help b/gcloud/alpha/compute/interconnects/attachments/help index c7af16279..4ef9b6899 100644 --- a/gcloud/alpha/compute/interconnects/attachments/help +++ b/gcloud/alpha/compute/interconnects/attachments/help @@ -27,7 +27,7 @@ COMMANDS COMMAND is one of the following: delete - (ALPHA) Delete interconnects. + (ALPHA) Delete Compute Engine interconnect attachments. describe (ALPHA) Describe a Compute Engine interconnect attachment. diff --git a/gcloud/alpha/compute/networks/subnets/create b/gcloud/alpha/compute/networks/subnets/create index 25e5ed100..31976dc68 100644 --- a/gcloud/alpha/compute/networks/subnets/create +++ b/gcloud/alpha/compute/networks/subnets/create @@ -8,7 +8,8 @@ SYNOPSIS [--description=DESCRIPTION] [--enable-flow-logs] [--enable-private-ip-google-access] [--external-ipv6-prefix=EXTERNAL_IPV6_PREFIX] - [--flow-sampling=FLOW_SAMPLING] [--ipv6-access-type=IPV6_ACCESS_TYPE] + [--flow-sampling=FLOW_SAMPLING] [--ip-collection=IP_COLLECTION] + [--ipv6-access-type=IPV6_ACCESS_TYPE] [--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL] [--logging-filter-expr=LOGGING_FILTER_EXPR] [--logging-flow-sampling=LOGGING_FLOW_SAMPLING] @@ -76,6 +77,11 @@ OPTIONAL FLAGS collected logs are reported and 0.0 means no logs are reported. Default is 0.5 which means half of all collected logs are reported. + --ip-collection=IP_COLLECTION + Resource reference to a public delegated prefix. The + PublicDelegatedPrefix must be a sub-prefix in + EXTERNAL_IPV6_SUBNETWORK_CREATION mode. + --ipv6-access-type=IPV6_ACCESS_TYPE IPv6 access type can be specified only when the subnet is created, or when the subnet is first updated to have a stack type of IPV4_IPV6. diff --git a/gcloud/alpha/compute/networks/subnets/update b/gcloud/alpha/compute/networks/subnets/update index ba960a13c..4d28ca234 100644 --- a/gcloud/alpha/compute/networks/subnets/update +++ b/gcloud/alpha/compute/networks/subnets/update @@ -8,7 +8,8 @@ SYNOPSIS [...]] [--aggregation-interval=AGGREGATION_INTERVAL] [--drain-timeout=DRAIN_TIMEOUT; default="0s"] [--external-ipv6-prefix=EXTERNAL_IPV6_PREFIX] - [--flow-sampling=FLOW_SAMPLING] [--ipv6-access-type=IPV6_ACCESS_TYPE] + [--flow-sampling=FLOW_SAMPLING] [--ip-collection=IP_COLLECTION] + [--ipv6-access-type=IPV6_ACCESS_TYPE] [--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL] [--logging-filter-expr=LOGGING_FILTER_EXPR] [--logging-flow-sampling=LOGGING_FLOW_SAMPLING] @@ -80,6 +81,11 @@ FLAGS reported and 0.0 means no logs are reported. Default is 0.5 which means half of all collected logs are reported. + --ip-collection=IP_COLLECTION + Resource reference to a public delegated prefix. The + PublicDelegatedPrefix must be a sub-prefix in + EXTERNAL_IPV6_SUBNETWORK_CREATION mode. + --ipv6-access-type=IPV6_ACCESS_TYPE IPv6 access type can be specified only when the subnet is created, or when the subnet is first updated to have a stack type of IPV4_IPV6. diff --git a/gcloud/alpha/compute/snapshots/list b/gcloud/alpha/compute/snapshots/list index 76dc13635..a04484bab 100644 --- a/gcloud/alpha/compute/snapshots/list +++ b/gcloud/alpha/compute/snapshots/list @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud alpha compute snapshots list [NAME ...] [--regexp=REGEXP, -r REGEXP] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--global | --regions=[REGION,...]] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute snapshots list displays all Google Compute @@ -35,6 +36,15 @@ FLAGS Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + At most one of these can be specified: + + --global + If provided, only global resources are shown. + + --regions=[REGION,...] + If provided, only regional resources are shown. If arguments are + provided, only resources from the given regions are shown. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/config/get b/gcloud/alpha/config/get index 151706baf..63c4b4206 100644 --- a/gcloud/alpha/config/get +++ b/gcloud/alpha/config/get @@ -568,6 +568,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index 11b74eb56..151ebcc51 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -600,6 +600,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index 6912e6a6f..4d7314e8e 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -612,6 +612,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index bb42c947a..25f9f2dab 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -615,6 +615,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 674b11404..09a633bb8 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -576,6 +576,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/alpha/container/attached/clusters/register b/gcloud/alpha/container/attached/clusters/register index a081da4e2..6f066540b 100644 --- a/gcloud/alpha/container/attached/clusters/register +++ b/gcloud/alpha/container/attached/clusters/register @@ -13,7 +13,6 @@ SYNOPSIS [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE] [--description=DESCRIPTION] [--enable-managed-prometheus] [--logging=COMPONENT,[COMPONENT,...]] [--validate-only] - [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--proxy-secret-name=PROXY_SECRET_NAME --proxy-secret-namespace=PROXY_SECRET_NAMESPACE] [GCLOUD_WIDE_FLAG ...] @@ -184,17 +183,6 @@ OPTIONAL FLAGS --validate-only Validate the cluster to create, but don't actually perform it. - --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING - Sets the mode of the Kubernetes security posture API's workload - vulnerability scanning. To enable Advanced vulnerability insights mode - explicitly set the flag to - --workload-vulnerability-scanning=enterprise. - - To disable in an existing cluster, explicitly set the flag to - --workload-vulnerability-scanning=disabled. - - WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, enterprise. - Proxy config --proxy-secret-name=PROXY_SECRET_NAME diff --git a/gcloud/alpha/container/attached/clusters/update b/gcloud/alpha/container/attached/clusters/update index d6ce6a7a9..c9d3205e6 100644 --- a/gcloud/alpha/container/attached/clusters/update +++ b/gcloud/alpha/container/attached/clusters/update @@ -10,7 +10,6 @@ SYNOPSIS [--clear-description] [--description=DESCRIPTION] [--logging=COMPONENT,[COMPONENT,...]] [--platform-version=PLATFORM_VERSION] [--validate-only] - [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--admin-groups=[GROUP,...] | --clear-admin-groups] [--admin-users=[USER,...] | --clear-admin-users] [--disable-managed-prometheus | --enable-managed-prometheus] @@ -102,17 +101,6 @@ FLAGS --validate-only Validate the update of the cluster, but don't actually perform it. - --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING - Sets the mode of the Kubernetes security posture API's workload - vulnerability scanning. To enable Advanced vulnerability insights mode - explicitly set the flag to - --workload-vulnerability-scanning=enterprise. - - To disable in an existing cluster, explicitly set the flag to - --workload-vulnerability-scanning=disabled. - - WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, enterprise. - Admin groups At most one of these can be specified: diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 30ad2f330..df1acb9e0 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -24,17 +24,19 @@ SYNOPSIS [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--disable-default-snat] [--disable-pod-cidr-overprovision] - [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autorepair] - [--no-enable-autoupgrade] [--enable-cilium-clusterwide-network-policy] - [--enable-cloud-logging] [--enable-cloud-monitoring] - [--enable-cloud-run-alpha] [--enable-confidential-nodes] - [--enable-confidential-storage] [--enable-cost-allocation] - [--enable-dataplane-v2] [--enable-fleet] [--enable-fqdn-network-policy] + [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] + [--enable-authorized-networks-on-private-endpoint] + [--enable-autorepair] [--no-enable-autoupgrade] + [--enable-cilium-clusterwide-network-policy] [--enable-cloud-logging] + [--enable-cloud-monitoring] [--enable-cloud-run-alpha] + [--enable-confidential-nodes] [--enable-confidential-storage] + [--enable-cost-allocation] [--enable-dataplane-v2] + [--enable-dns-access] [--enable-fleet] [--enable-fqdn-network-policy] [--enable-gke-oidc] [--enable-google-cloud-access] [--enable-gvnic] [--enable-identity-service] [--enable-image-streaming] [--enable-insecure-kubelet-readonly-port] - [--enable-intra-node-visibility] [--enable-ip-alias] - [--enable-kubernetes-alpha] + [--enable-intra-node-visibility] [--enable-ip-access] + [--enable-ip-alias] [--enable-kubernetes-alpha] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-l4-ilb-subsetting] [--enable-legacy-authorization] [--enable-logging-monitoring-system-only] [--enable-managed-prometheus] @@ -439,6 +441,10 @@ FLAGS DISK_TYPE must be one of: pd-standard, pd-ssd, pd-balanced, hyperdisk-balanced, hyperdisk-extreme, hyperdisk-throughput. + --enable-authorized-networks-on-private-endpoint + Enable enforcement of --master-authorized-networks CIDR ranges for + traffic reaching cluster's control plane via private IP. + --enable-autorepair Enable node autorepair feature for a cluster's default node pool(s). @@ -519,6 +525,11 @@ FLAGS Enables the new eBPF dataplane for GKE clusters that is required for network security, scalability and visibility features. + --enable-dns-access + Enable access to the cluster's control plane over DNS-based endpoint. + + DNS-based control plane access is recommended. + --enable-fleet Set cluster project as the fleet host project. This will register the cluster to the same project. To register the cluster to a fleet in a @@ -581,6 +592,10 @@ FLAGS Enabling it on an existing cluster causes the cluster master and the cluster nodes to restart, which might cause a disruption. + --enable-ip-access + Enable access to the cluster's control plane over private IP and public + IP if --enable-private-endpoint is not enabled. + --enable-ip-alias Enable use of alias IPs (https://cloud.google.com/compute/docs/alias-ip/) for Pod IPs. This diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index 8d3bfe489..56210ca20 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -14,9 +14,10 @@ SYNOPSIS [--containerd-config-from-file=PATH_TO_FILE] [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] + [--enable-authorized-networks-on-private-endpoint] [--enable-backup-restore] [--enable-cilium-clusterwide-network-policy] - [--enable-fleet] [--enable-google-cloud-access] - [--enable-kubernetes-unstable-apis=API,[API,...]] + [--enable-dns-access] [--enable-fleet] [--enable-google-cloud-access] + [--enable-ip-access] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] [--enable-ray-operator] [--enable-secret-manager] [--fleet-project=PROJECT_ID_OR_NUMBER] @@ -220,6 +221,10 @@ FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. + --enable-authorized-networks-on-private-endpoint + Enable enforcement of --master-authorized-networks CIDR ranges for + traffic reaching cluster's control plane via private IP. + --enable-backup-restore Enable the Backup for GKE add-on. This add-on is disabled by default. To learn more, see the Backup for GKE overview: @@ -229,6 +234,11 @@ FLAGS Enable Cilium Clusterwide Network Policies on the cluster. Disabled by default. + --enable-dns-access + Enable access to the cluster's control plane over DNS-based endpoint. + + DNS-based control plane access is recommended. + --enable-fleet Set cluster project as the fleet host project. This will register the cluster to the same project. To register the cluster to a fleet in a @@ -240,6 +250,10 @@ FLAGS Google Cloud can reach the public control plane endpoint of your cluster. + --enable-ip-access + Enable access to the cluster's control plane over private IP and public + IP if --enable-private-endpoint is not enabled. + --enable-kubernetes-unstable-apis=API,[API,...] Enable Kubernetes beta API features on this cluster. Beta APIs are not expected to be production ready and should be avoided in diff --git a/gcloud/alpha/container/clusters/get-credentials b/gcloud/alpha/container/clusters/get-credentials index 9e2760eb6..673f60375 100644 --- a/gcloud/alpha/container/clusters/get-credentials +++ b/gcloud/alpha/container/clusters/get-credentials @@ -3,7 +3,8 @@ NAME running cluster SYNOPSIS - gcloud alpha container clusters get-credentials NAME [--internal-ip] + gcloud alpha container clusters get-credentials NAME [--dns-endpoint] + [--internal-ip] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...] @@ -46,6 +47,9 @@ POSITIONAL ARGUMENTS container/cluster property value for this command invocation. FLAGS + --dns-endpoint + Whether to use the DNS-based endpoint for the cluster address. + --internal-ip Whether to use the internal IP address of the cluster endpoint. diff --git a/gcloud/alpha/container/clusters/get-upgrade-info b/gcloud/alpha/container/clusters/get-upgrade-info new file mode 100644 index 000000000..e48213cda --- /dev/null +++ b/gcloud/alpha/container/clusters/get-upgrade-info @@ -0,0 +1,58 @@ +NAME + gcloud alpha container clusters get-upgrade-info - get information about + upgrades for existing clusters including auto upgrade status, upgrade + history, upgrade targets, and end of support timelines + +SYNOPSIS + gcloud alpha container clusters get-upgrade-info NAME + [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get information about upgrades for existing clusters including auto + upgrade status, upgrade history, upgrade targets, and end of support + timelines. + +EXAMPLES + To get upgrade information for an existing cluster, run: + + $ gcloud alpha container clusters get-upgrade-info sample-cluster + +POSITIONAL ARGUMENTS + NAME + The name of your existing cluster. + +FLAGS + At most one of these can be specified: + + --location=LOCATION + Compute zone or region (e.g. us-central1-a or us-central1) for the + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. + + --region=REGION + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. + + --zone=ZONE, -z ZONE + Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the + default compute/zone property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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: + + $ gcloud beta container clusters get-upgrade-info + diff --git a/gcloud/alpha/container/clusters/help b/gcloud/alpha/container/clusters/help index 3acb8831b..189f00613 100644 --- a/gcloud/alpha/container/clusters/help +++ b/gcloud/alpha/container/clusters/help @@ -64,6 +64,11 @@ COMMANDS get-credentials (ALPHA) Fetch credentials for a running cluster. + get-upgrade-info + (ALPHA) Get information about upgrades for existing clusters including + auto upgrade status, upgrade history, upgrade targets, and end of + support timelines. + list (ALPHA) List existing clusters for running containers. diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 085b6bec9..0211d4326 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -16,16 +16,14 @@ SYNOPSIS | --[no-]enable-cilium-clusterwide-network-policy | --enable-cost-allocation | --enable-fleet | --enable-fqdn-network-policy | --enable-gke-oidc - | --enable-google-cloud-access | --enable-identity-service - | --enable-image-streaming | --enable-insecure-kubelet-readonly-port + | --enable-identity-service | --enable-image-streaming + | --enable-insecure-kubelet-readonly-port | --enable-intra-node-visibility | --enable-kubernetes-unstable-apis=API,[API,...] | --enable-l4-ilb-subsetting | --enable-legacy-authorization - | --enable-logging-monitoring-system-only - | --enable-master-authorized-networks | --enable-master-global-access - | --enable-multi-networking | --enable-network-policy - | --enable-pod-security-policy | --enable-private-endpoint - | --[no-]enable-ray-cluster-logging + | --enable-logging-monitoring-system-only | --enable-multi-networking + | --enable-network-policy | --enable-pod-security-policy + | --enable-private-nodes | --[no-]enable-ray-cluster-logging | --[no-]enable-ray-cluster-monitoring | --enable-secret-manager | --enable-service-externalips | --enable-shielded-nodes | --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling @@ -78,6 +76,11 @@ SYNOPSIS | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics + | --enable-authorized-networks-on-private-endpoint + --enable-dns-access --enable-google-cloud-access --enable-ip-access + --enable-master-global-access --enable-private-endpoint + --enable-master-authorized-networks + --master-authorized-networks=NETWORK,[NETWORK,...] | [--enable-autoprovisioning : --autoprovisioning-config-file=PATH_TO_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE @@ -103,9 +106,7 @@ SYNOPSIS | --password=PASSWORD --enable-basic-auth | --username=USERNAME, -u USERNAME) [--async] [--cloud-run-config=[load-balancer-type=EXTERNAL,...]] - [--istio-config=[auth=MTLS_PERMISSIVE,...]] - [--master-authorized-networks=NETWORK,[NETWORK,...]] - [--node-pool=NODE_POOL] + [--istio-config=[auth=MTLS_PERMISSIVE,...]] [--node-pool=NODE_POOL] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [--location-policy=LOCATION_POLICY --max-nodes=MAX_NODES --min-nodes=MIN_NODES @@ -321,11 +322,6 @@ REQUIRED FLAGS Thus, flag --enable-gke-oidc is also deprecated. Please use --enable-identity-service to enable the Identity Service component - --enable-google-cloud-access - When you enable Google Cloud Access, any public IP addresses owned by - Google Cloud can reach the public control plane endpoint of your - cluster. - --enable-identity-service Enable Identity Service component on the cluster. @@ -382,26 +378,6 @@ REQUIRED FLAGS and https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. - --enable-master-authorized-networks - Allow only specified set of CIDR blocks (specified by the - --master-authorized-networks flag) to connect to Kubernetes master - through HTTPS. Besides these blocks, the following have access as - well: - - 1) The private network the cluster connects to if - `--enable-private-nodes` is specified. - 2) Google Compute Engine Public IPs if `--enable-private-nodes` is not - specified. - - Use --no-enable-master-authorized-networks to disable. When disabled, - public internet (0.0.0.0/0) is allowed to connect to Kubernetes - master through HTTPS. - - --enable-master-global-access - Use with private clusters to allow access to the master's private - endpoint from any Google Cloud region or on-premises environment - regardless of the private cluster's region. - --enable-multi-networking Enables multi-networking on the cluster. Multi-networking is disabled by default. @@ -419,9 +395,20 @@ REQUIRED FLAGS PodSecurityPolicy API objects. For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/pod-security-policies. - --enable-private-endpoint - Enables cluster's control plane to be accessible using private IP - address only. + --enable-private-nodes + Standard cluster: Enable private nodes as a default behavior for all + newly created node pools, if --enable-private-nodes is not provided + at node pool creation time. + + Modifications to this flag do not affect `--enable-private-nodes` state of the + existing node pools. + + Autopilot cluster: Force new and existing workloads, without explicit + cloud.google.com/private-node=true node selector, to run on nodes + with no public IP address. + + Modifications to this flag trigger a re-schedule operation on all existng + workloads to run on different node VMs. --[no-]enable-ray-cluster-logging Enable automatic log processing sidecar for Ray clusters. Use @@ -1157,6 +1144,57 @@ REQUIRED FLAGS --enable-dataplane-v2-metrics Exposes advanced datapath flow metrics on node port. + --enable-authorized-networks-on-private-endpoint + Enable enforcement of --master-authorized-networks CIDR ranges for + traffic reaching cluster's control plane via private IP. + + --enable-dns-access + Enable access to the cluster's control plane over DNS-based endpoint. + + DNS-based control plane access is recommended. + + --enable-google-cloud-access + When you enable Google Cloud Access, any public IP addresses owned by + Google Cloud can reach the public control plane endpoint of your + cluster. + + --enable-ip-access + Enable access to the cluster's control plane over private IP and + public IP if --enable-private-endpoint is not enabled. + + --enable-master-global-access + Use with private clusters to allow access to the master's private + endpoint from any Google Cloud region or on-premises environment + regardless of the private cluster's region. + + --enable-private-endpoint + Enables cluster's control plane to be accessible using private IP + address only. + + Master Authorized Networks + + --enable-master-authorized-networks + Allow only specified set of CIDR blocks (specified by the + --master-authorized-networks flag) to connect to Kubernetes master + through HTTPS. Besides these blocks, the following have access as + well: + + 1) The private network the cluster connects to if + `--enable-private-nodes` is specified. + 2) Google Compute Engine Public IPs if `--enable-private-nodes` is not + specified. + + Use --no-enable-master-authorized-networks to disable. When + disabled, public internet (0.0.0.0/0) is allowed to connect to + Kubernetes master through HTTPS. + + --master-authorized-networks=NETWORK,[NETWORK,...] + The list of CIDR blocks (up to 100 for private cluster, 50 for + public cluster) that are allowed to connect to Kubernetes master + through HTTPS. Specified in CIDR notation (e.g. 1.2.3.4/30). Cannot + be specified unless --enable-master-authorized-networks is also + specified. + Node autoprovisioning --enable-autoprovisioning @@ -1520,12 +1558,6 @@ OPTIONAL FLAGS information and migration, see https://cloud.google.com/istio/docs/istio-on-gke/migrate-to-anthos-service-mesh. - --master-authorized-networks=NETWORK,[NETWORK,...] - The list of CIDR blocks (up to 100 for private cluster, 50 for public - cluster) that are allowed to connect to Kubernetes master through - HTTPS. Specified in CIDR notation (e.g. 1.2.3.4/30). Cannot be - specified unless --enable-master-authorized-networks is also specified. - --node-pool=NODE_POOL Node pool to be updated. diff --git a/gcloud/alpha/container/fleet/scopes/add-app-operator-binding b/gcloud/alpha/container/fleet/scopes/add-app-operator-binding index d2ef7c443..f1ea0665d 100644 --- a/gcloud/alpha/container/fleet/scopes/add-app-operator-binding +++ b/gcloud/alpha/container/fleet/scopes/add-app-operator-binding @@ -123,5 +123,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta container fleet scopes add-app-operator-binding diff --git a/gcloud/alpha/container/fleet/scopes/list-app-operator-bindings b/gcloud/alpha/container/fleet/scopes/list-app-operator-bindings index f7b37b924..2308a69c6 100644 --- a/gcloud/alpha/container/fleet/scopes/list-app-operator-bindings +++ b/gcloud/alpha/container/fleet/scopes/list-app-operator-bindings @@ -102,5 +102,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta container fleet scopes list-app-operator-bindings diff --git a/gcloud/alpha/container/fleet/scopes/remove-app-operator-binding b/gcloud/alpha/container/fleet/scopes/remove-app-operator-binding index 3cc01642a..906501837 100644 --- a/gcloud/alpha/container/fleet/scopes/remove-app-operator-binding +++ b/gcloud/alpha/container/fleet/scopes/remove-app-operator-binding @@ -118,5 +118,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta container fleet scopes remove-app-operator-binding diff --git a/gcloud/alpha/container/hub/scopes/add-app-operator-binding b/gcloud/alpha/container/hub/scopes/add-app-operator-binding index 177637c1f..74bc8bcb3 100644 --- a/gcloud/alpha/container/hub/scopes/add-app-operator-binding +++ b/gcloud/alpha/container/hub/scopes/add-app-operator-binding @@ -123,5 +123,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta container hub scopes add-app-operator-binding diff --git a/gcloud/alpha/container/hub/scopes/list-app-operator-bindings b/gcloud/alpha/container/hub/scopes/list-app-operator-bindings index 2ecd6f332..298f436a1 100644 --- a/gcloud/alpha/container/hub/scopes/list-app-operator-bindings +++ b/gcloud/alpha/container/hub/scopes/list-app-operator-bindings @@ -102,5 +102,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta container hub scopes list-app-operator-bindings diff --git a/gcloud/alpha/container/hub/scopes/remove-app-operator-binding b/gcloud/alpha/container/hub/scopes/remove-app-operator-binding index a2d6df6fe..ad1f55c71 100644 --- a/gcloud/alpha/container/hub/scopes/remove-app-operator-binding +++ b/gcloud/alpha/container/hub/scopes/remove-app-operator-binding @@ -118,5 +118,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta container hub scopes remove-app-operator-binding diff --git a/gcloud/alpha/container/node-pools/get-upgrade-info b/gcloud/alpha/container/node-pools/get-upgrade-info new file mode 100644 index 000000000..954341922 --- /dev/null +++ b/gcloud/alpha/container/node-pools/get-upgrade-info @@ -0,0 +1,63 @@ +NAME + gcloud alpha container node-pools get-upgrade-info - get information about + upgrades for existing clusters including auto upgrade status, upgrade + history, upgrade targets, and end of support timelines + +SYNOPSIS + gcloud alpha container node-pools get-upgrade-info NAME [--cluster=CLUSTER] + [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get information about upgrades for existing clusters including auto + upgrade status, upgrade history, upgrade targets, and end of support + timelines. + +EXAMPLES + To get upgrade information for a node pool of an existing cluster, run: + + $ gcloud alpha container node-pools get-upgrade-info node-pool-1 \ + --cluster=sample-cluster + +POSITIONAL ARGUMENTS + NAME + The name of the node pool. + +FLAGS + --cluster=CLUSTER + The name of the cluster. Overrides the default container/cluster + property value for this command invocation. + + At most one of these can be specified: + + --location=LOCATION + Compute zone or region (e.g. us-central1-a or us-central1) for the + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. + + --region=REGION + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. + + --zone=ZONE, -z ZONE + Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the + default compute/zone property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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: + + $ gcloud beta container node-pools get-upgrade-info + diff --git a/gcloud/alpha/container/node-pools/help b/gcloud/alpha/container/node-pools/help index 319c1c30c..d50770cf6 100644 --- a/gcloud/alpha/container/node-pools/help +++ b/gcloud/alpha/container/node-pools/help @@ -55,6 +55,11 @@ COMMANDS describe (ALPHA) Describe an existing node pool for a cluster. + get-upgrade-info + (ALPHA) Get information about upgrades for existing clusters including + auto upgrade status, upgrade history, upgrade targets, and end of + support timelines. + list (ALPHA) List existing node pools for a cluster. diff --git a/gcloud/alpha/datastore/indexes/cleanup b/gcloud/alpha/datastore/indexes/cleanup index 4830a2d12..a4d8bbb40 100644 --- a/gcloud/alpha/datastore/indexes/cleanup +++ b/gcloud/alpha/datastore/indexes/cleanup @@ -3,7 +3,8 @@ NAME based on your local index configuration SYNOPSIS - gcloud alpha datastore indexes cleanup INDEX_FILE [GCLOUD_WIDE_FLAG ...] + gcloud alpha datastore indexes cleanup INDEX_FILE [--database=DATABASE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command removes unused datastore indexes based on your local @@ -21,6 +22,15 @@ POSITIONAL ARGUMENTS your index.yaml file, refer to this configuration guide: https://cloud.google.com/datastore/docs/tools/indexconfig#Datastore_About_index_yaml +FLAGS + --database=DATABASE + The database to operate on. If not specified, the CLI refers the + (default) database by default. + + For example, to operate on database testdb: + + $ gcloud alpha datastore indexes cleanup --database='testdb' + 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/dialogflow/agent/query b/gcloud/alpha/dialogflow/agent/query index 706d44dd9..08ebeb61a 100644 --- a/gcloud/alpha/dialogflow/agent/query +++ b/gcloud/alpha/dialogflow/agent/query @@ -44,8 +44,8 @@ REQUIRED FLAGS See here for more information: https://cloud.google.com/dialogflow-enterprise/docs/reference/rest/v2/projects.agent.sessions/detectIntent#AudioEncoding. - AUDIO_ENCODING must be one of: audio-encoding-amr, - audio-encoding-amr-wb, audio-encoding-flac, + AUDIO_ENCODING must be one of: audio-encoding-alaw, + audio-encoding-amr, audio-encoding-amr-wb, audio-encoding-flac, audio-encoding-linear-16, audio-encoding-mulaw, audio-encoding-ogg-opus, audio-encoding-speex-with-header-byte, audio-encoding-unspecified. diff --git a/gcloud/alpha/edge-cloud/container/clusters/create b/gcloud/alpha/edge-cloud/container/clusters/create index dc2744819..c645d2214 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/create +++ b/gcloud/alpha/edge-cloud/container/clusters/create @@ -11,6 +11,7 @@ SYNOPSIS [--control-plane-machine-filter=CONTROL_PLANE_MACHINE_FILTER] [--control-plane-node-count=CONTROL_PLANE_NODE_COUNT] [--control-plane-node-location=CONTROL_PLANE_NODE_LOCATION] + [--control-plane-node-storage-schema=CONTROL_PLANE_NODE_STORAGE_SCHEMA] [--control-plane-shared-deployment-policy=CONTROL_PLANE_SHARED_DEPLOYMENT_POLICY] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--external-lb-address-pools=EXTERNAL_LB_ADDRESS_POOLS] @@ -111,6 +112,9 @@ FLAGS Google Edge Cloud zone where the local control plane nodes will be created. + --control-plane-node-storage-schema=CONTROL_PLANE_NODE_STORAGE_SCHEMA + Name for the storage schema of control plane nodes. + --control-plane-shared-deployment-policy=CONTROL_PLANE_SHARED_DEPLOYMENT_POLICY Policy configuration about how user application is deployed for local control plane cluster. It supports two values, ALLOWED and DISALLOWED. diff --git a/gcloud/alpha/edge-cloud/container/clusters/node-pools/create b/gcloud/alpha/edge-cloud/container/clusters/node-pools/create index 91a65dc45..d69f6776c 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/node-pools/create +++ b/gcloud/alpha/edge-cloud/container/clusters/node-pools/create @@ -8,7 +8,8 @@ SYNOPSIS --node-count=NODE_COUNT --node-location=NODE_LOCATION [--async] [--labels=[KEY=VALUE,...]] [--local-disk-kms-key=LOCAL_DISK_KMS_KEY] [--lro-timeout=LRO_TIMEOUT] [--machine-filter=MACHINE_FILTER] - [--node-labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--node-labels=[KEY=VALUE,...]] + [--node-storage-schema=NODE_STORAGE_SCHEMA] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create an Edge Container node pool. @@ -115,6 +116,9 @@ OPTIONAL FLAGS Comma-delimited list of key-value pairs that comprise labels for the individual nodes in the node pool. + --node-storage-schema=NODE_STORAGE_SCHEMA + Name for the storage schema of worker nodes. + 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/identity/groups/create b/gcloud/alpha/identity/groups/create index 79d2f7599..2fbbf1b6c 100644 --- a/gcloud/alpha/identity/groups/create +++ b/gcloud/alpha/identity/groups/create @@ -5,7 +5,6 @@ SYNOPSIS gcloud alpha identity groups create EMAIL --organization=ORGANIZATION [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--dynamic-user-query=DYNAMIC_USER_QUERY] - [--posix-group=[gid=GID],[name=NAME]] [--with-initial-owner=WITH_INITIAL_OWNER] [--group-type=GROUP_TYPE; default="discussion" | --labels=LABELS] [GCLOUD_WIDE_FLAG ...] @@ -34,11 +33,6 @@ EXAMPLES --display-name="Security Group" \ --description="Description of Security Group" - To create a new POSIX group: - - $ gcloud alpha identity groups create eng-discuss@example.com \ - --organization="example.com" --posix-group=name=eng,gid=1005 - POSITIONAL ARGUMENTS EMAIL The email address of the group to be created. @@ -65,15 +59,6 @@ OPTIONAL FLAGS Example of a query: --dynamic-user-query="user.organizations.exists(org,org.title=='SWE')" - --posix-group=[gid=GID],[name=NAME] - Group ID (gid) and name of the POSIX group that you want to associate - with the specified Cloud Identity group. You can specify multiple POSIX - groups with multiple instances of this flag. - - For example, use '--posix-group=gid=1005,name=eng' to add a single - group, or '--posix-group=gid=1005,name=eng - --posix-group=gid=1006,name=docs' to add multiple groups. - --with-initial-owner=WITH_INITIAL_OWNER If specified the user making the request will be added as the initial owner of the group being created. WITH_INITIAL_OWNER must be one of: diff --git a/gcloud/alpha/identity/groups/update b/gcloud/alpha/identity/groups/update index 484225156..9449193a1 100644 --- a/gcloud/alpha/identity/groups/update +++ b/gcloud/alpha/identity/groups/update @@ -4,8 +4,7 @@ NAME SYNOPSIS gcloud alpha identity groups update EMAIL [--dynamic-user-query=DYNAMIC_USER_QUERY] - [--add-posix-group=[gid=GID],[name=NAME] | --clear-posix-groups - | --remove-posix-groups=[POSIX_GROUP,...]] + [--clear-posix-groups | --remove-posix-groups=[POSIX_GROUP,...]] [--clear-description | --description=DESCRIPTION] [--clear-display-name | --display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] @@ -20,11 +19,6 @@ EXAMPLES --display-name="New Engineer Discuss" \ --description="Group for engineering discussions" - To create a POSIX group from an existing Google Group: - - $ gcloud alpha identity groups update eng-discuss@foo.com \ - --add-posix-group=name=eng,gid=1005 - To remove POSIX information from a Google Group: $ gcloud alpha identity groups update eng-discuss@foo.com \ @@ -43,15 +37,6 @@ FLAGS At most one of these can be specified: - --add-posix-group=[gid=GID],[name=NAME] - Group id (gid) and a name for a POSIX group that you want to add to - the specified Cloud Identity group. You can specify multiple POSIX - groups to add with multiple instances of this flag. - - For example, use '--add-posix-group=gid=1005,name=eng' to add a - single group, or '--add-posix-group=gid=1005,name=eng - --add-posix-group=gid=1006,name=docs' to add multiple groups. - --clear-posix-groups Clear all POSIX groups from the specified Cloud Identity group. diff --git a/gcloud/alpha/ml/speech/recognize b/gcloud/alpha/ml/speech/recognize index e1e30a146..171dc21c8 100644 --- a/gcloud/alpha/ml/speech/recognize +++ b/gcloud/alpha/ml/speech/recognize @@ -71,7 +71,7 @@ OPTIONAL FLAGS --encoding=ENCODING; default="encoding-unspecified" The type of encoding of the file. Required if the file format is not - WAV or FLAC. ENCODING must be one of: amr, amr-wb, + WAV or FLAC. ENCODING must be one of: alaw, amr, amr-wb, encoding-unspecified, flac, linear16, mp3, mulaw, ogg-opus, speex-with-header-byte, webm-opus. diff --git a/gcloud/alpha/ml/speech/recognize-long-running b/gcloud/alpha/ml/speech/recognize-long-running index 41fb534fa..4eb988be9 100644 --- a/gcloud/alpha/ml/speech/recognize-long-running +++ b/gcloud/alpha/ml/speech/recognize-long-running @@ -80,7 +80,7 @@ OPTIONAL FLAGS --encoding=ENCODING; default="encoding-unspecified" The type of encoding of the file. Required if the file format is not - WAV or FLAC. ENCODING must be one of: amr, amr-wb, + WAV or FLAC. ENCODING must be one of: alaw, amr, amr-wb, encoding-unspecified, flac, linear16, mp3, mulaw, ogg-opus, speex-with-header-byte, webm-opus. diff --git a/gcloud/alpha/network-services/multicast-consumer-associations/create b/gcloud/alpha/network-services/multicast-consumer-associations/create index d626a304f..4cddcccd1 100644 --- a/gcloud/alpha/network-services/multicast-consumer-associations/create +++ b/gcloud/alpha/network-services/multicast-consumer-associations/create @@ -24,10 +24,10 @@ EXAMPLES --network=path-to-network --location=zone POSITIONAL ARGUMENTS - Multicast consumer association resource - Name of the multicast group to - be created. 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. + Multicast consumer association resource - Name of the multicast consumer + association to be created. 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 multicast_consumer_association on the command diff --git a/gcloud/alpha/network-services/multicast-consumer-associations/describe b/gcloud/alpha/network-services/multicast-consumer-associations/describe index 1a42509f9..70ee155b6 100644 --- a/gcloud/alpha/network-services/multicast-consumer-associations/describe +++ b/gcloud/alpha/network-services/multicast-consumer-associations/describe @@ -1,6 +1,6 @@ NAME gcloud alpha network-services multicast-consumer-associations describe - - describe a multicast consumer associations + describe a multicast consumer association SYNOPSIS gcloud alpha network-services multicast-consumer-associations describe diff --git a/gcloud/alpha/network-services/multicast-consumer-associations/help b/gcloud/alpha/network-services/multicast-consumer-associations/help index b8af6056c..2b76a2c9e 100644 --- a/gcloud/alpha/network-services/multicast-consumer-associations/help +++ b/gcloud/alpha/network-services/multicast-consumer-associations/help @@ -24,7 +24,7 @@ COMMANDS (ALPHA) Delete a multicast consumer association. describe - (ALPHA) Describe a multicast consumer associations. + (ALPHA) Describe a multicast consumer association. list (ALPHA) List multicast consumer associations. diff --git a/gcloud/alpha/network-services/multicast-consumer-associations/list b/gcloud/alpha/network-services/multicast-consumer-associations/list index 581e5fab3..c365d57c6 100644 --- a/gcloud/alpha/network-services/multicast-consumer-associations/list +++ b/gcloud/alpha/network-services/multicast-consumer-associations/list @@ -13,7 +13,8 @@ DESCRIPTION of the current project. EXAMPLES - To list multicast groups in the current project and location, run: + To list multicast consumer associations in the current project and + location, run: $ gcloud alpha network-services multicast-consumer-associations \ list --location=zone diff --git a/gcloud/alpha/pubsub/topics/create b/gcloud/alpha/pubsub/topics/create index e881dcda0..205502e54 100644 --- a/gcloud/alpha/pubsub/topics/create +++ b/gcloud/alpha/pubsub/topics/create @@ -6,10 +6,10 @@ SYNOPSIS gcloud alpha pubsub topics create TOPIC [TOPIC ...] [--labels=[KEY=VALUE,...]] [--message-retention-duration=MESSAGE_RETENTION_DURATION] - [--kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN - --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN - --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT - --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN] + [--ingestion-log-severity=INGESTION_LOG_SEVERITY + [--cloud-storage-ingestion-bucket=CLOUD_STORAGE_INGESTION_BUCKET + --cloud-storage-ingestion-input-format=INPUT_FORMAT + : --cloud-storage-ingestion-text-delimiter=CLOUD_STORAGE_INGESTION_TEXT_DELIMITER --cloud-storage-ingestion-minimum-object-create-time=CLOUD_STORAGE_INGESTION_MINIMUM_OBJECT_CREATE_TIME --cloud-storage-ingestion-match-glob=CLOUD_STORAGE_INGESTION_MATCH_GLOB] | --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN] [--message-encoding=ENCODING (--schema=SCHEMA : --schema-project=SCHEMA_PROJECT) : --first-revision-id=FIRST_REVISION_ID @@ -70,35 +70,69 @@ FLAGS is one of "s", "m", "h", and "d" for seconds, minutes, hours, and days, respectively. If the unit is omitted, seconds is assumed. - The following flags are for specifying ingestion settings for an import - topic from Amazon Web Services (AWS) Kinesis Data Streams + Following flags are for specifying the data source settings for an import + topic - --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN - The Kinesis data streams consumer Amazon Resource Name (ARN) to use - for ingestion. + --ingestion-log-severity=INGESTION_LOG_SEVERITY + Log severity to use for ingestion. - 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: - --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN - AWS role ARN to be used for Federated Identity authentication with - Kinesis. + Flags that specify settings for an import topic from Cloud Storage - This flag argument must be specified if any of the other arguments in - this group are specified. + --cloud-storage-ingestion-bucket=CLOUD_STORAGE_INGESTION_BUCKET + Cloud Storage bucket from which to ingest data. - --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT - The service account to be used for Federated Identity authentication - with Kinesis. + This flag argument must be specified if any of the other + arguments in this group are specified. - This flag argument must be specified if any of the other arguments in - this group are specified. + --cloud-storage-ingestion-input-format=INPUT_FORMAT + Format of the data in the Cloud Storage bucket. INPUT_FORMAT must + be one of: text, avro, pubsub_avro. - --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN - The Kinesis data stream ARN from which to ingest data. + This flag argument must be specified if any of the other + arguments in this group are specified. - This flag argument must be specified if any of the other arguments in - this group are specified. + --cloud-storage-ingestion-text-delimiter=CLOUD_STORAGE_INGESTION_TEXT_DELIMITER + Delimiter to use with text format when partitioning the object. + + --cloud-storage-ingestion-minimum-object-create-time=CLOUD_STORAGE_INGESTION_MINIMUM_OBJECT_CREATE_TIME + Only Cloud Storage objects with a larger or equal creation + timestamp will be ingested. + + --cloud-storage-ingestion-match-glob=CLOUD_STORAGE_INGESTION_MATCH_GLOB + Glob pattern used to match Cloud Storage objects that will be + ingested. If unset, all objects will be ingested. + + Flags that specify settings for an import topic from Amazon Web + Services (AWS) Kinesis Data Streams + + --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN + Kinesis data streams consumer Amazon Resource Name (ARN) to use + for ingestion. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN + AWS role ARN to be used for Federated Identity authentication + with Kinesis. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT + Service account to be used for Federated Identity authentication + with Kinesis. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN + Kinesis data stream ARN from which to ingest data. + + This flag argument must be specified if any of the other + arguments in this group are specified. Schema settings. The schema that messages published to this topic must conform to and the expected message encoding. diff --git a/gcloud/alpha/pubsub/topics/update b/gcloud/alpha/pubsub/topics/update index 4d6a22aef..b28bf334b 100644 --- a/gcloud/alpha/pubsub/topics/update +++ b/gcloud/alpha/pubsub/topics/update @@ -4,10 +4,10 @@ NAME SYNOPSIS gcloud alpha pubsub topics update TOPIC [--update-labels=[KEY=VALUE,...]] [--clear-ingestion-data-source-settings - | --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN - --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN - --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT - --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN] + | --ingestion-log-severity=INGESTION_LOG_SEVERITY + [--cloud-storage-ingestion-bucket=CLOUD_STORAGE_INGESTION_BUCKET + --cloud-storage-ingestion-input-format=INPUT_FORMAT + : --cloud-storage-ingestion-text-delimiter=CLOUD_STORAGE_INGESTION_TEXT_DELIMITER --cloud-storage-ingestion-minimum-object-create-time=CLOUD_STORAGE_INGESTION_MINIMUM_OBJECT_CREATE_TIME --cloud-storage-ingestion-match-glob=CLOUD_STORAGE_INGESTION_MATCH_GLOB] | --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN] [--clear-labels | --remove-labels=[KEY,...]] [--clear-message-retention-duration | --message-retention-duration=MESSAGE_RETENTION_DURATION] @@ -116,39 +116,81 @@ FLAGS If set, clear the Ingestion Data Source Settings from the topic. Use --no-clear-ingestion-data-source-settings to disable this flag. - The following flags are for specifying ingestion settings for an import - topic from Amazon Web Services (AWS) Kinesis Data Streams + Following flags are for specifying the data source settings for an + import topic - When updating AWSKinesis Source flags, all AWSKinesis Source flags must - be specified. Otherwise, any omitted AWSKinesis Source flags revert to - their default value. + When updating IngestionDataSourceSettings flags, all + IngestionDataSourceSettings flags must be specified. Otherwise, any + omitted IngestionDataSourceSettings flags revert to their default value. - --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN - The Kinesis data streams consumer Amazon Resource Name (ARN) to use - for ingestion. + --ingestion-log-severity=INGESTION_LOG_SEVERITY + Log severity to use for ingestion. - 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: - --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN - AWS role ARN to be used for Federated Identity authentication with - Kinesis. + Flags that specify settings for an import topic from Cloud Storage - This flag argument must be specified if any of the other arguments - in this group are specified. + When updating CloudStorage Source flags, all CloudStorage Source + flags must be specified. Otherwise, any omitted CloudStorage Source + flags revert to their default value. - --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT - The service account to be used for Federated Identity - authentication with Kinesis. + --cloud-storage-ingestion-bucket=CLOUD_STORAGE_INGESTION_BUCKET + Cloud Storage bucket from which to ingest data. - This flag argument must be specified if any of the other arguments - in this group are specified. + This flag argument must be specified if any of the other + arguments in this group are specified. - --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN - The Kinesis data stream ARN from which to ingest data. + --cloud-storage-ingestion-input-format=INPUT_FORMAT + Format of the data in the Cloud Storage bucket. INPUT_FORMAT + must be one of: text, avro, pubsub_avro. - This flag argument must be specified if any of the other arguments - in this group are specified. + This flag argument must be specified if any of the other + arguments in this group are specified. + + --cloud-storage-ingestion-text-delimiter=CLOUD_STORAGE_INGESTION_TEXT_DELIMITER + Delimiter to use with text format when partitioning the object. + + --cloud-storage-ingestion-minimum-object-create-time=CLOUD_STORAGE_INGESTION_MINIMUM_OBJECT_CREATE_TIME + Only Cloud Storage objects with a larger or equal creation + timestamp will be ingested. + + --cloud-storage-ingestion-match-glob=CLOUD_STORAGE_INGESTION_MATCH_GLOB + Glob pattern used to match Cloud Storage objects that will be + ingested. If unset, all objects will be ingested. + + Flags that specify settings for an import topic from Amazon Web + Services (AWS) Kinesis Data Streams + + When updating AWSKinesis Source flags, all AWSKinesis Source flags + must be specified. Otherwise, any omitted AWSKinesis Source flags + revert to their default value. + + --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN + Kinesis data streams consumer Amazon Resource Name (ARN) to use + for ingestion. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN + AWS role ARN to be used for Federated Identity authentication + with Kinesis. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT + Service account to be used for Federated Identity + authentication with Kinesis. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN + Kinesis data stream ARN from which to ingest data. + + 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: diff --git a/gcloud/alpha/resource-manager/tags/keys/create b/gcloud/alpha/resource-manager/tags/keys/create index a426c7c43..247676809 100644 --- a/gcloud/alpha/resource-manager/tags/keys/create +++ b/gcloud/alpha/resource-manager/tags/keys/create @@ -46,8 +46,8 @@ FLAGS --purpose=PURPOSE Purpose specifier of the TagKey that can only be set on creation. Specifying this field adds additional validation from the policy system - that corresponds to the purpose. PURPOSE must be (only one value is - supported): GCE_FIREWALL. + that corresponds to the purpose. PURPOSE must be one of: GCE_FIREWALL, + DATA_GOVERNANCE. --purpose-data=[network=NETWORK] Purpose data of the TagKey that can only be set on creation. This data diff --git a/gcloud/alpha/resource-settings/describe b/gcloud/alpha/resource-settings/describe deleted file mode 100644 index 8994a6c87..000000000 --- a/gcloud/alpha/resource-settings/describe +++ /dev/null @@ -1,65 +0,0 @@ -NAME - gcloud alpha resource-settings describe - show the value of a resource - setting - -SYNOPSIS - gcloud alpha resource-settings describe SETTING_NAME - (--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID) [--effective] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) Show the value of a resource setting. - - Resource Settings is deprecated. As of November 7, 2023, no organizations - will be onboarded for any of the enabled settings, and the service will be - shut down on October 1, 2024. - - Show the value of a resource setting. - -EXAMPLES - To describe the resource settings net-preferredDnsServers with the project - foo-project, run: - - $ gcloud alpha resource-settings describe net-preferredDnsServers \ - --project=foo-project - -POSITIONAL ARGUMENTS - SETTING_NAME - Name of the resource settings. The list of available settings can be - fetched using the list command: $ gcloud resource-settings list - -REQUIRED FLAGS - Resource that is associated with the resource settings. - - Exactly one of these must be specified: - - --folder=FOLDER_ID - Folder ID. - - --organization=ORGANIZATION_ID - Organization ID. - - --project=PROJECT_ID - Project ID. Overrides the default core/project property value for - this command invocation. - -OPTIONAL FLAGS - --effective - Describe the effective setting. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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: - - $ gcloud resource-settings describe - diff --git a/gcloud/alpha/resource-settings/help b/gcloud/alpha/resource-settings/help deleted file mode 100644 index 7d0d913ca..000000000 --- a/gcloud/alpha/resource-settings/help +++ /dev/null @@ -1,56 +0,0 @@ -NAME - gcloud alpha resource-settings - create and manage Resource Settings - -SYNOPSIS - gcloud alpha resource-settings COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) Create and manage Resource Settings. - - Resource Settings is deprecated. As of November 7, 2023, no organizations - will be onboarded for any of the enabled settings, and the service will be - shut down on October 1, 2024. - - The gcloud Resource Settings command group lets you create and manipulate - resource settings. - - The Resource Settings Service is a hierarchy-aware service with a - public-facing API for users to store settings that modify the behavior of - their Google Cloud Platform resources, such as virtual machines, firewalls, - projects, and so forth. Settings can be attached to organizations, folders, - and projects, and can influence these resources as well as service - resources that are descendants of the resource to which the settings are - attached. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - describe - (ALPHA) (DEPRECATED) Show the value of a resource setting. - - list - (ALPHA) (DEPRECATED) List all available resource settings. - - list-values - (ALPHA) (DEPRECATED) List the values for any configured resource - settings. - - set-value - (ALPHA) (DEPRECATED) Update the value of a resource setting. - - unset-value - (ALPHA) (DEPRECATED) Remove the value of a resource setting. - -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: - - $ gcloud resource-settings - diff --git a/gcloud/alpha/resource-settings/list-values b/gcloud/alpha/resource-settings/list-values deleted file mode 100644 index 2c67ec8bc..000000000 --- a/gcloud/alpha/resource-settings/list-values +++ /dev/null @@ -1,88 +0,0 @@ -NAME - gcloud alpha resource-settings list-values - list the values for any - configured resource settings - -SYNOPSIS - gcloud alpha resource-settings list-values - (--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID) [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) List the values for any configured resource settings. - - Resource Settings is deprecated. As of November 7, 2023, no organizations - will be onboarded for any of the enabled settings, and the service will be - shut down on October 1, 2024. - - List the values for any configured resource settings. - -EXAMPLES - To list all setting values on the project foo-project, run: - - $ gcloud alpha resource-settings list-values --project=foo-project - -REQUIRED FLAGS - Resource that is associated with the resource settings. - - Exactly one of these must be specified: - - --folder=FOLDER_ID - Folder ID. - - --organization=ORGANIZATION_ID - Organization ID. - - --project=PROJECT_ID - Project ID. Overrides the default core/project property value for - this command invocation. - -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 - 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: - - $ gcloud resource-settings list-values - diff --git a/gcloud/alpha/resource-settings/set-value b/gcloud/alpha/resource-settings/set-value deleted file mode 100644 index a39326afd..000000000 --- a/gcloud/alpha/resource-settings/set-value +++ /dev/null @@ -1,43 +0,0 @@ -NAME - gcloud alpha resource-settings set-value - update the value of a resource - setting - -SYNOPSIS - gcloud alpha resource-settings set-value --value-file=value-file - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) Update the value of a resource setting. - - Resource Settings is deprecated. As of November 7, 2023, no organizations - will be onboarded for any of the enabled settings, and the service will be - shut down on October 1, 2024. - - Update the value of a resource setting. - -EXAMPLES - To set the resource setting from the file with the path ./sample_path, run: - - $ gcloud alpha resource-settings set-value \ - --value-file="./test_input.json" - -REQUIRED FLAGS - --value-file=value-file - Path to JSON or YAML file that contains the resource setting. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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: - - $ gcloud resource-settings set-value - diff --git a/gcloud/alpha/resource-settings/unset-value b/gcloud/alpha/resource-settings/unset-value deleted file mode 100644 index 155c5e76b..000000000 --- a/gcloud/alpha/resource-settings/unset-value +++ /dev/null @@ -1,63 +0,0 @@ -NAME - gcloud alpha resource-settings unset-value - remove the value of a resource - setting - -SYNOPSIS - gcloud alpha resource-settings unset-value SETTING_NAME - (--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) Remove the value of a resource setting. - - Resource Settings is deprecated. As of November 7, 2023, no organizations - will be onboarded for any of the enabled settings, and the service will be - shut down on October 1, 2024. - - Remove the value of a resource setting. This reverts the resource to - inheriting the resource settings from above it in the resource hierarchy, - if any is set on a resource above it. - -EXAMPLES - To unset the resource settings net-preferredDnsServers with the project - foo-project, run: - - $ gcloud alpha resource-settings unset-value \ - net-preferredDnsServers --project=foo-project - -POSITIONAL ARGUMENTS - SETTING_NAME - Name of the resource settings. The list of available settings can be - fetched using the list command: $ gcloud resource-settings list - -REQUIRED FLAGS - Resource that is associated with the resource settings. - - Exactly one of these must be specified: - - --folder=FOLDER_ID - Folder ID. - - --organization=ORGANIZATION_ID - Organization ID. - - --project=PROJECT_ID - Project ID. Overrides the default core/project property value for - this command invocation. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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: - - $ gcloud resource-settings unset-value - diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index 64d1b6334..ff6c50341 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -606,10 +606,11 @@ FLAGS Run the application in a second generation execution environment. --[no-]invoker-iam-check - Indicates whether an IAM check should occur when invoking the - container. This is Enabled by default. Disabling this flag is not - available in all projects. Use --invoker-iam-check to enable and - --no-invoker-iam-check to disable. + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. --max-surge=MAX_SURGE A maximum percentage of instances that will be moved in each step of diff --git a/gcloud/alpha/run/help b/gcloud/alpha/run/help index 4dce4416a..5941472d9 100644 --- a/gcloud/alpha/run/help +++ b/gcloud/alpha/run/help @@ -32,6 +32,9 @@ GROUPS jobs (ALPHA) View and manage your Cloud Run jobs. + multi-region-services + (ALPHA) Manage your Cloud Run multi-region services. + regions (ALPHA) View available Cloud Run (fully managed) regions. diff --git a/gcloud/alpha/run/multi-region-services/delete b/gcloud/alpha/run/multi-region-services/delete new file mode 100644 index 000000000..41c4f9cbb --- /dev/null +++ b/gcloud/alpha/run/multi-region-services/delete @@ -0,0 +1,152 @@ +NAME + gcloud alpha run multi-region-services delete - deletes a multi-region + service + +SYNOPSIS + gcloud alpha run multi-region-services delete + (SERVICE : --namespace=NAMESPACE) [--[no-]async] + [--platform=PLATFORM; default="managed"] + [--region=REGION + | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION + | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes a multi-region service. + +EXAMPLES + To delete a service: + + $ gcloud alpha run multi-region-services delete + +POSITIONAL ARGUMENTS + Service resource - Service to delete. The arguments in this group can be + used to specify the attributes of this resource. + + This must be specified. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument SERVICE on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --namespace=NAMESPACE + Specific to Cloud Run for Anthos: Kubernetes namespace for the + service. + + To set the namespace attribute: + ▸ provide the argument SERVICE on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line; + ▸ set the property run/namespace; + ▸ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▸ provide the argument project on the command line; + ▸ set the property core/project. + +FLAGS + --[no-]async + Return immediately, without waiting for the operation in progress to + complete. Defaults to --no-async for Cloud Run (fully managed) and + --async for Cloud Run for Anthos. Use --async to enable and --no-async + to disable. + + --platform=PLATFORM; default="managed" + Target platform for running commands. Alternatively, set the property + [run/platform]. PLATFORM must be one of: + + managed + Fully managed version of Cloud Run. Use with the --region flag or + set the [run/region] property to specify a Cloud Run region. + gke + Cloud Run for Anthos on Google Cloud. Use with the --cluster and + --cluster-location flags or set the [run/cluster] and + [run/cluster_location] properties to specify a cluster in a given + zone. + kubernetes + Use a Knative-compatible kubernetes cluster. Use with the + --kubeconfig and --context flags to specify a kubeconfig file and + the context for connecting. + + Arguments to locate resources, depending on the platform used. + + At most one of these can be specified: + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud. Specify --platform=gke to use: + + Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully + specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ◇ provide the argument --cluster on the command line; + ◇ set the property run/cluster; + ◇ specify the cluster from a list of available clusters. + + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. + + To set the location attribute: + ◇ provide the argument --cluster on the command line with a + fully specified name; + ◇ set the property run/cluster with a fully specified name; + ◇ specify the cluster from a list of available clusters with a + fully specified name; + ◇ provide the argument --cluster-location on the command line; + ◇ set the property run/cluster_location; + ◇ specify the cluster location from a list of available zones. + + Only applicable if connecting to Cloud Run for Anthos deployed on + VMware. Specify --platform=kubernetes to use: + + --context=CONTEXT + The name of the context in your kubectl config file to use for + connecting. + + --kubeconfig=KUBECONFIG + The absolute path to your kubectl config file. If not specified, + the colon- or semicolon-delimited list of paths specified by + $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to + ~/.kube/config. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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: + + $ gcloud beta run multi-region-services delete + diff --git a/gcloud/alpha/run/multi-region-services/describe b/gcloud/alpha/run/multi-region-services/describe new file mode 100644 index 000000000..b984c18a1 --- /dev/null +++ b/gcloud/alpha/run/multi-region-services/describe @@ -0,0 +1,157 @@ +NAME + gcloud alpha run multi-region-services describe - command to describe a + multi-region service + +SYNOPSIS + gcloud alpha run multi-region-services describe + (SERVICE : --namespace=NAMESPACE) + [--platform=PLATFORM; default="managed"] + [--region=REGION + | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION + | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Command to describe a multi-region service. + +EXAMPLES + To obtain details about a given service: + + $ gcloud alpha run multi-region-services describe + + To get those details in the YAML format: + + $ gcloud alpha run multi-region-services describe \ + --format=yaml + + To get them in YAML format suited to export (omitting metadata specific to + this deployment and status info): + + $ gcloud alpha run multi-region-services describe \ + --format=export + +POSITIONAL ARGUMENTS + Service resource - Service to describe. The arguments in this group can be + used to specify the attributes of this resource. + + This must be specified. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument SERVICE on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --namespace=NAMESPACE + Specific to Cloud Run for Anthos: Kubernetes namespace for the + service. + + To set the namespace attribute: + ▸ provide the argument SERVICE on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line; + ▸ set the property run/namespace; + ▸ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▸ provide the argument project on the command line; + ▸ set the property core/project. + +FLAGS + --platform=PLATFORM; default="managed" + Target platform for running commands. Alternatively, set the property + [run/platform]. PLATFORM must be one of: + + managed + Fully managed version of Cloud Run. Use with the --region flag or + set the [run/region] property to specify a Cloud Run region. + gke + Cloud Run for Anthos on Google Cloud. Use with the --cluster and + --cluster-location flags or set the [run/cluster] and + [run/cluster_location] properties to specify a cluster in a given + zone. + kubernetes + Use a Knative-compatible kubernetes cluster. Use with the + --kubeconfig and --context flags to specify a kubeconfig file and + the context for connecting. + + Arguments to locate resources, depending on the platform used. + + At most one of these can be specified: + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud. Specify --platform=gke to use: + + Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully + specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ◇ provide the argument --cluster on the command line; + ◇ set the property run/cluster; + ◇ specify the cluster from a list of available clusters. + + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. + + To set the location attribute: + ◇ provide the argument --cluster on the command line with a + fully specified name; + ◇ set the property run/cluster with a fully specified name; + ◇ specify the cluster from a list of available clusters with a + fully specified name; + ◇ provide the argument --cluster-location on the command line; + ◇ set the property run/cluster_location; + ◇ specify the cluster location from a list of available zones. + + Only applicable if connecting to Cloud Run for Anthos deployed on + VMware. Specify --platform=kubernetes to use: + + --context=CONTEXT + The name of the context in your kubectl config file to use for + connecting. + + --kubeconfig=KUBECONFIG + The absolute path to your kubectl config file. If not specified, + the colon- or semicolon-delimited list of paths specified by + $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to + ~/.kube/config. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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: + + $ gcloud beta run multi-region-services describe + diff --git a/gcloud/alpha/run/multi-region-services/help b/gcloud/alpha/run/multi-region-services/help new file mode 100644 index 000000000..a05adc279 --- /dev/null +++ b/gcloud/alpha/run/multi-region-services/help @@ -0,0 +1,137 @@ +NAME + gcloud alpha run multi-region-services - manage your Cloud Run multi-region + services + +SYNOPSIS + gcloud alpha run multi-region-services COMMAND + [--platform=PLATFORM; default="managed"] + [--region=REGION + | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION + | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The gcloud run multi-region-services command group lets you deploy + container images to Google Cloud Run across multiple regions at once. + +EXAMPLES + To deploy your container, use the gcloud run multi-region-services deploy + command: + + $ gcloud alpha run multi-region-services deploy \ + --image --regions [region-list] For more \ + information, run: + $ gcloud run deploy --help + +FLAGS + --platform=PLATFORM; default="managed" + Target platform for running commands. Alternatively, set the property + [run/platform]. PLATFORM must be one of: + + managed + Fully managed version of Cloud Run. Use with the --region flag or + set the [run/region] property to specify a Cloud Run region. + gke + Cloud Run for Anthos on Google Cloud. Use with the --cluster and + --cluster-location flags or set the [run/cluster] and + [run/cluster_location] properties to specify a cluster in a given + zone. + kubernetes + Use a Knative-compatible kubernetes cluster. Use with the + --kubeconfig and --context flags to specify a kubeconfig file and + the context for connecting. + + Arguments to locate resources, depending on the platform used. + + At most one of these can be specified: + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud. Specify --platform=gke to use: + + Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully + specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ◇ provide the argument --cluster on the command line; + ◇ set the property run/cluster; + ◇ specify the cluster from a list of available clusters. + + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. + + To set the location attribute: + ◇ provide the argument --cluster on the command line with a + fully specified name; + ◇ set the property run/cluster with a fully specified name; + ◇ specify the cluster from a list of available clusters with a + fully specified name; + ◇ provide the argument --cluster-location on the command line; + ◇ set the property run/cluster_location; + ◇ specify the cluster location from a list of available zones. + + Only applicable if connecting to Cloud Run for Anthos deployed on + VMware. Specify --platform=kubernetes to use: + + --context=CONTEXT + The name of the context in your kubectl config file to use for + connecting. + + --kubeconfig=KUBECONFIG + The absolute path to your kubectl config file. If not specified, + the colon- or semicolon-delimited list of paths specified by + $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to + ~/.kube/config. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (ALPHA) Deletes a multi-region service. + + describe + (ALPHA) Command to describe a multi-region service. + + list + (ALPHA) List available multi-region services. + + replace + (ALPHA) Create or Update multi-region service from YAML. + + update + (ALPHA) Update environment variables, add/remove regions, and other + configuration settings in Multi-Region Services. + +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: + + $ gcloud beta run multi-region-services + diff --git a/gcloud/alpha/run/multi-region-services/list b/gcloud/alpha/run/multi-region-services/list new file mode 100644 index 000000000..8c7484add --- /dev/null +++ b/gcloud/alpha/run/multi-region-services/list @@ -0,0 +1,169 @@ +NAME + gcloud alpha run multi-region-services list - list available multi-region + services + +SYNOPSIS + gcloud alpha run multi-region-services list [--namespace=NAMESPACE] + [--platform=PLATFORM; default="managed"] + [--region=REGION + | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION + | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List available multi-region services. + +EXAMPLES + To list available services: + + $ gcloud alpha run multi-region-services list + +FLAGS + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke + or --platform=kubernetes to use: + + Namespace resource - Namespace to list services in. This represents a + Cloud resource. + + --namespace=NAMESPACE + ID of the namespace or fully qualified identifier for the + namespace. + + To set the namespace attribute: + ▫ provide the argument --namespace on the command line; + ▫ set the property run/namespace; + ▫ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▫ provide the argument project on the command line; + ▫ set the property core/project. + + --platform=PLATFORM; default="managed" + Target platform for running commands. Alternatively, set the property + [run/platform]. PLATFORM must be one of: + + managed + Fully managed version of Cloud Run. Use with the --region flag or + set the [run/region] property to specify a Cloud Run region. + gke + Cloud Run for Anthos on Google Cloud. Use with the --cluster and + --cluster-location flags or set the [run/cluster] and + [run/cluster_location] properties to specify a cluster in a given + zone. + kubernetes + Use a Knative-compatible kubernetes cluster. Use with the + --kubeconfig and --context flags to specify a kubeconfig file and + the context for connecting. + + Arguments to locate resources, depending on the platform used. + + At most one of these can be specified: + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud. Specify --platform=gke to use: + + Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully + specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ◇ provide the argument --cluster on the command line; + ◇ set the property run/cluster; + ◇ specify the cluster from a list of available clusters. + + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. + + To set the location attribute: + ◇ provide the argument --cluster on the command line with a + fully specified name; + ◇ set the property run/cluster with a fully specified name; + ◇ specify the cluster from a list of available clusters with a + fully specified name; + ◇ provide the argument --cluster-location on the command line; + ◇ set the property run/cluster_location; + ◇ specify the cluster location from a list of available zones. + + Only applicable if connecting to Cloud Run for Anthos deployed on + VMware. Specify --platform=kubernetes to use: + + --context=CONTEXT + The name of the context in your kubectl config file to use for + connecting. + + --kubeconfig=KUBECONFIG + The absolute path to your kubectl config file. If not specified, + the colon- or semicolon-delimited list of paths specified by + $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to + ~/.kube/config. + +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 + 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: + + $ gcloud beta run multi-region-services list + diff --git a/gcloud/alpha/run/multi-region-services/replace b/gcloud/alpha/run/multi-region-services/replace new file mode 100644 index 000000000..4d59fccf6 --- /dev/null +++ b/gcloud/alpha/run/multi-region-services/replace @@ -0,0 +1,148 @@ +NAME + gcloud alpha run multi-region-services replace - create or Update + multi-region service from YAML + +SYNOPSIS + gcloud alpha run multi-region-services replace FILE [--async] [--dry-run] + [--namespace=NAMESPACE] [--platform=PLATFORM; default="managed"] + [--region=REGION + | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION + | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Creates or replaces a service from a YAML service specification. + +EXAMPLES + To replace the specification for a service defined in myservice.yaml + + $ gcloud alpha run multi-region-services replace myservice.yaml + +POSITIONAL ARGUMENTS + FILE + The absolute path to the YAML file with a Knative service definition + for the service to update or deploy. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --dry-run + If set to true, only validates the configuration. The configuration + will not be applied. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke + or --platform=kubernetes to use: + + Namespace resource - Namespace to replace service. This represents a + Cloud resource. + + --namespace=NAMESPACE + ID of the namespace or fully qualified identifier for the + namespace. + + To set the namespace attribute: + ▫ provide the argument --namespace on the command line; + ▫ set the property run/namespace; + ▫ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▫ provide the argument project on the command line; + ▫ set the property core/project. + + --platform=PLATFORM; default="managed" + Target platform for running commands. Alternatively, set the property + [run/platform]. PLATFORM must be one of: + + managed + Fully managed version of Cloud Run. Use with the --region flag or + set the [run/region] property to specify a Cloud Run region. + gke + Cloud Run for Anthos on Google Cloud. Use with the --cluster and + --cluster-location flags or set the [run/cluster] and + [run/cluster_location] properties to specify a cluster in a given + zone. + kubernetes + Use a Knative-compatible kubernetes cluster. Use with the + --kubeconfig and --context flags to specify a kubeconfig file and + the context for connecting. + + Arguments to locate resources, depending on the platform used. + + At most one of these can be specified: + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud. Specify --platform=gke to use: + + Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully + specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ◇ provide the argument --cluster on the command line; + ◇ set the property run/cluster; + ◇ specify the cluster from a list of available clusters. + + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. + + To set the location attribute: + ◇ provide the argument --cluster on the command line with a + fully specified name; + ◇ set the property run/cluster with a fully specified name; + ◇ specify the cluster from a list of available clusters with a + fully specified name; + ◇ provide the argument --cluster-location on the command line; + ◇ set the property run/cluster_location; + ◇ specify the cluster location from a list of available zones. + + Only applicable if connecting to Cloud Run for Anthos deployed on + VMware. Specify --platform=kubernetes to use: + + --context=CONTEXT + The name of the context in your kubectl config file to use for + connecting. + + --kubeconfig=KUBECONFIG + The absolute path to your kubectl config file. If not specified, + the colon- or semicolon-delimited list of paths specified by + $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to + ~/.kube/config. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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: + + $ gcloud beta run multi-region-services replace + diff --git a/gcloud/alpha/run/multi-region-services/update b/gcloud/alpha/run/multi-region-services/update new file mode 100644 index 000000000..11f42861c --- /dev/null +++ b/gcloud/alpha/run/multi-region-services/update @@ -0,0 +1,722 @@ +NAME + gcloud alpha run multi-region-services update - update environment + variables, add/remove regions, and other configuration settings in + Multi-Region Services + +SYNOPSIS + gcloud alpha run multi-region-services update + [[SERVICE] --namespace=NAMESPACE] [--async] [--concurrency=CONCURRENCY] + [--container=CONTAINER] [--ingress=INGRESS; default="all"] + [--max-instances=MAX_INSTANCES] [--min-instances=MIN_INSTANCES] + [--platform=PLATFORM; default="managed"] + [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] + [--no-traffic] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] + --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE --memory=MEMORY + --port=PORT --remove-volume-mount=[MOUNT_PATH,...] + --[no-]use-http2 --clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] + --update-env-vars=[KEY=VALUE,...] --clear-secrets + | --set-secrets=[KEY=VALUE,...] + | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] + [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost + --[no-]cpu-throttling --[no-]default-url --[no-]deploy-health-check + --description=DESCRIPTION + --execution-environment=EXECUTION_ENVIRONMENT + --[no-]invoker-iam-check --max-surge=MAX_SURGE + --max-unavailable=MAX_UNAVAILABLE --mesh=MESH + --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX + --scaling=SCALING --service-max-instances=SERVICE_MAX_INSTANCES + --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity + --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --clear-cloudsql-instances + | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + --add-custom-audiences=[CUSTOM-AUDIENCES,...] + | --clear-custom-audiences + | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + | --set-custom-audiences=[CUSTOM-AUDIENCES,...] + --add-volume=[KEY=VALUE,...] --clear-volumes + --remove-volume=[VOLUME,...] --binary-authorization=POLICY + | --clear-binary-authorization --clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + --clear-key | --key=KEY --clear-network + | --network=NETWORK --subnet=SUBNET --clear-network-tags + | --network-tags=[TAG,...] --clear-post-key-revocation-action-type + | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] + | --update-labels=[KEY=VALUE,...]] + [--connectivity=CONNECTIVITY --clear-config-maps + | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] + --update-config-maps=[KEY=VALUE,...]] + [--region=REGION + | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION + | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update environment variables, add/remove regions, and other + configuration settings in Multi-Region Services. + +EXAMPLES + To update one or more env vars: + + $ gcloud alpha run multi-region-services update myservice \ + --update-env-vars=KEY1=VALUE1,KEY2=VALUE2 + +POSITIONAL ARGUMENTS + Service resource - Service to update the configuration of. The arguments + in this group can be used to specify the attributes of this resource. + + [SERVICE] + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument SERVICE on the command line; + ▸ specify the service name from an interactive prompt. + + --namespace=NAMESPACE + Specific to Cloud Run for Anthos: Kubernetes namespace for the + service. + + To set the namespace attribute: + ▸ provide the argument SERVICE on the command line with a fully + specified name; + ▸ specify the service name from an interactive prompt with a fully + specified name; + ▸ provide the argument --namespace on the command line; + ▸ set the property run/namespace; + ▸ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▸ provide the argument project on the command line; + ▸ set the property core/project. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --concurrency=CONCURRENCY + Set the maximum number of concurrent requests allowed per container + instance. Leave concurrency unspecified or provide the special value + 'default' to receive the server default value. + + --container=CONTAINER + Specifies a container by name. Flags following --container will apply + to the specified container. + + --ingress=INGRESS; default="all" + Set the ingress traffic sources allowed to call the service. For Cloud + Run (fully managed) the --[no-]allow-unauthenticated flag separately + controls the identities allowed to call the service. INGRESS must be + one of: + + all + Inbound requests from all sources are allowed. + internal + For Cloud Run (fully managed), only inbound requests from VPC + networks in the same project or VPC Service Controls perimeter, as + well as Pub/Sub subscriptions and Eventarc events in the same + project or VPC Service Controls perimeter are allowed. All other + requests are rejected. See + https://cloud.google.com/run/docs/securing/ingress for full details + on the definition of internal traffic for Cloud Run (fully + managed). For Cloud Run for Anthos, only inbound requests from the + same cluster are allowed. + + internal-and-cloud-load-balancing + Only supported for Cloud Run (fully managed). Only inbound requests + from Google Cloud Load Balancing or a traffic source allowed by the + internal option are allowed. + + --max-instances=MAX_INSTANCES + The maximum number of container instances of the Service to run. Use + 'default' to unset the limit and use the platform default. + + --min-instances=MIN_INSTANCES + The minimum number of container instances for this Revision of the + Service to run or 'default' to remove any minimum. + + --platform=PLATFORM; default="managed" + Target platform for running commands. Alternatively, set the property + [run/platform]. PLATFORM must be one of: + + managed + Fully managed version of Cloud Run. Use with the --region flag or + set the [run/region] property to specify a Cloud Run region. + gke + Cloud Run for Anthos on Google Cloud. Use with the --cluster and + --cluster-location flags or set the [run/cluster] and + [run/cluster_location] properties to specify a cluster in a given + zone. + kubernetes + Use a Knative-compatible kubernetes cluster. Use with the + --kubeconfig and --context flags to specify a kubeconfig file and + the context for connecting. + + --service-account=SERVICE_ACCOUNT + Service account associated with the revision of the service. The + service account represents the identity of the running revision, and + determines what permissions the revision has. For the managed platform, + this is the email address of an IAM service account. For the + Kubernetes-based platforms (gke, kubernetes), this is the name of a + Kubernetes service account in the same namespace as the service. If not + provided, the revision will use the default service account of the + project, or default Kubernetes namespace service account respectively. + + --tag=TAG + Traffic tag to assign to the newly created revision. + + --timeout=TIMEOUT + Set the maximum request execution time (timeout). It is specified as a + duration; for example, "10m5s" is ten minutes, and five seconds. If you + don't specify a unit, seconds is assumed. For example, "10" is 10 + seconds. + + --no-traffic + True to avoid sending traffic to the revision being deployed. Setting + this flag assigns any traffic assigned to the LATEST revision to the + specific revision bound to LATEST before the deployment. The effect is + that the revision being deployed will not receive traffic. + + After a deployment with this flag the LATEST revision will not receive + traffic on future deployments. To restore sending traffic to the LATEST + revision by default, run the gcloud run services update-traffic command + with --to-latest. + + Container Flags + + If the --container or --remove-containers flag is specified the following + arguments may only be specified after a --container flag. + + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume + on this resource and PATH is the path within the container's + filesystem to mount this volume. + + --args=[ARG,...] + Comma-separated arguments passed to the command run by the + container image. If not specified and no '--command' is provided, + the container image's default Cmd is used. Otherwise, if not + specified, no arguments are passed. To reset this field to its + default, pass an empty string. + + --clear-volume-mounts + Remove all existing mounts from the current container. + + --command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default Entrypoint is run. To reset this field to its + default, pass an empty string. + + --cpu=CPU + Set a CPU limit in Kubernetes cpu units. + + Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run + (fully managed), 4 cpus also requires a minimum 2Gi --memory value. + Examples 2, 2.0, 2000m + + Cloud Run for Anthos and Knative-compatible Kubernetes clusters + support fractional values. Examples .5, 500m, 2 + + --depends-on=[CONTAINER,...] + List of container dependencies to add to the current container. + + --image=IMAGE + Name of the container image to deploy (e.g. + gcr.io/cloudrun/hello:latest). + + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. + + --port=PORT + Container port to receive requests at. Also sets the $PORT + environment variable. Must be a number between 1 and 65535, + inclusive. To unset this field, pass the special value "default". + If updating an existing service with a TCP startup probe pointing + to the previous container port, this will also update the probe + port. + + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + + --[no-]use-http2 + Whether to use HTTP/2 for connections to the service. Use + --use-http2 to enable and --no-use-http2 to disable. + + At most one of these can be specified: + + --clear-env-vars + Remove all environment variables. + + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed + before the new environment variables are added. Example YAML + content: + + KEY_1: "value1" + KEY_2: "value 2" + + --set-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. All + existing environment variables will be removed first. + + Only --update-env-vars and --remove-env-vars can be used together. + If both are specified, --remove-env-vars will be applied first. + + --remove-env-vars=[KEY,...] + List of environment variables to be removed. + + --update-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + Specify secrets to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. Values should be in the form + SECRET_NAME:SECRET_VERSION. For example: + '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' + will mount a volume at '/secrets/api' containing a file 'key' with the + latest version of secret 'mysecret'. An environment variable named ENV + will also be created whose value is version 1 of secret 'othersecret'. + + At most one of these can be specified: + + --clear-secrets + Remove all secrets. + + --set-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. All existing secrets + will be removed first. + + Only --update-secrets and --remove-secrets can be used together. If + both are specified, --remove-secrets will be applied first. + + --remove-secrets=[KEY,...] + List of secrets to be removed. + + --update-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass + for more information. Next update or deploy command will + automatically clear existing breakglass justification. + + --clear-vpc-connector + Remove the VPC connector for this resource. + + --[no-]cpu-boost + Whether to allocate extra CPU to containers on startup to reduce the + perceived latency of a cold start request. Enabled by default when + unspecified on new services. Use --cpu-boost to enable and + --no-cpu-boost to disable. + + --[no-]cpu-throttling + Whether to throttle the CPU when the container is not actively + serving requests. Use --cpu-throttling to enable and + --no-cpu-throttling to disable. + + --[no-]default-url + Toggles the default url for a run service. This is enabled by default + if not specified. Use --default-url to enable and --no-default-url to + disable. + + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. + + --description=DESCRIPTION + Provides an optional, human-readable description of the service. + + --execution-environment=EXECUTION_ENVIRONMENT + Selects the execution environment where the application will run. + EXECUTION_ENVIRONMENT must be one of: + + gen1 + Run the application in a first generation execution environment. + gen2 + Run the application in a second generation execution environment. + + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. + + --max-surge=MAX_SURGE + A maximum percentage of instances that will be moved in each step of + traffic split changes. Use "default" to unset the limit and use the + platform default. + + --max-unavailable=MAX_UNAVAILABLE + A maximum percentage of instances that may be unavailable during + traffic split changes. Use "default" to unset the limit and use the + platform default. + + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. + Mesh resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + + --remove-containers=[CONTAINER,...] + List of containers to remove. + + --revision-suffix=REVISION_SUFFIX + Specify the suffix of the revision name. Revision names always start + with the service name automatically. For example, specifying + [--revision-suffix=v1] for a service named 'helloworld', would lead + to a revision named 'helloworld-v1'. Set empty string to clear the + suffix and resume server-assigned naming. + + --scaling=SCALING + The scaling mode to use for this resource. SCALING must be one of: + + automatic + The number of instances is scaled automatically based on the + usage metrics. + manual + The number of instances is fixed to a provided config value. + + --service-max-instances=SERVICE_MAX_INSTANCES + The maximum number of container instances for this Service to run. + This instance limit will be divided among all Revisions receiving a + percentage of traffic. Once service-max-instances is enabled for a + service, it cannot be disabled. + + --service-min-instances=SERVICE_MIN_INSTANCES + The minimum number of container instances for this Service to run or + 'default' to remove any minimum. These instances will be divided + among all Revisions receiving a percentage of traffic. + + --[no-]session-affinity + Whether to enable session affinity for connections to the service. + Use --session-affinity to enable and --no-session-affinity to + disable. + + --vpc-connector=VPC_CONNECTOR + Set a VPC connector for this resource. + + --vpc-egress=VPC_EGRESS + Specify which of the outbound traffic to send through Direct VPC + egress or the VPC connector for this resource. This resource must + have Direct VPC egress enabled or a VPC connector to set this flag. + VPC_EGRESS must be one of: + + all + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. + all-traffic + Sends all outbound traffic through Direct VPC egress or the VPC + connector. + private-ranges-only + Default option. Sends outbound traffic to private IP addresses + (RFC 1918 and Private Google Access IPs) through Direct VPC + egress or the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. + + These flags modify the Cloud SQL instances this Service connects to. You + can specify a name of a Cloud SQL instance if it's in the same project + and region as your Cloud Run service; otherwise specify + :: for the instance. + + At most one of these can be specified: + + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Append the given values to the current Cloud SQL instances. + + --clear-cloudsql-instances + Empty the current Cloud SQL instances. + + --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Remove the given values from the current Cloud SQL instances. + + --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Completely replace the current Cloud SQL instances with the given + values. + + These flags modify the custom audiences that can be used in the audience + field of ID token for authenticated requests. + + At most one of these can be specified: + + --add-custom-audiences=[CUSTOM-AUDIENCES,...] + Append the given values to the current custom audiences. + + --clear-custom-audiences + Empty the current custom audiences. + + --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + Remove the given values from the current custom audiences. + + --set-custom-audiences=[CUSTOM-AUDIENCES,...] + Completely replace the current custom audiences with the given + values. + + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + + At most one of these can be specified: + + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". + + --clear-binary-authorization + Remove any previously set Binary Authorization policy. + + At most one of these can be specified: + + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. + + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server + after CMEK key revocation is detected. + + At most one of these can be specified: + + --clear-key + Remove any previously set CMEK key reference. + + --key=KEY + CMEK key reference to encrypt the container with. + + At most one of these can be specified: + + --clear-network + Disconnect this Cloud Run service from the VPC network it is + connected to. + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Run service will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. + + --subnet=SUBNET + The VPC subnetwork that the Cloud Run service will get IPs from. + The subnetwork must be /26 or larger. If --network is also + specified, subnet must be a subnetwork of the network specified + by the --network flag. If --network is not specified, network + will be looked up from this subnetwork. To clear existing VPC + network settings, use --clear-network. + + At most one of these can be specified: + + --clear-network-tags + Clears all existing Compute Engine tags from the Cloud Run + service. + + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run service. To clear existing tags, use + --clear-network-tags. + + At most one of these can be specified: + + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. + + --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE + Action type after CMEK key revocation. + POST_KEY_REVOCATION_ACTION_TYPE must be one of: + + prevent-new + No new instances will be started after CMEK key revocation. + shut-down + No new instances will be started and the existing instances + will be shut down after CMEK key revocation. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha run multi-region-services update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha run multi-region-services update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + + At most one of these can be specified: + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + An alias to --update-labels. + + --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. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke + or --platform=kubernetes to use: + + --connectivity=CONNECTIVITY + (DEPRECATED) Defaults to 'external'. If 'external', the service can + be invoked through the internet, in addition to through the cluster + network. + + The --connectivity flag is deprecated but will continue to be + supported. Prefer to use the --ingress flag instead. CONNECTIVITY + must be one of: + + external + Visible from outside the cluster. + internal + Visible only within the cluster. + + Specify config map to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. The values associated with each of + these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may + omit the key within the config map to specify a mount of all keys within + the config map. For example: + '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will + create a volume with config map 'myconfig' and mount that volume at + '/my/path'. Because no config map key was specified, all keys in + 'myconfig' will be included. An environment variable named ENV will also + be created whose value is the value of 'key.json' in 'otherconfig. Not + supported on the fully managed version of Cloud Run. + + At most one of these can be specified: + + --clear-config-maps + Remove all config-maps. + + --set-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. All existing + config-maps will be removed first. + + Only --update-config-maps and --remove-config-maps can be used + together. If both are specified, --remove-config-maps will be applied + first. + + --remove-config-maps=[KEY,...] + List of config-maps to be removed. + + --update-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. + + Arguments to locate resources, depending on the platform used. + + At most one of these can be specified: + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud. Specify --platform=gke to use: + + Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully + specified name; + ▸ set the property run/cluster with a fully specified name; + ▸ specify the cluster from a list of available clusters with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the + cluster. + + To set the cluster attribute: + ▫ provide the argument --cluster on the command line; + ▫ set the property run/cluster; + ▫ specify the cluster from a list of available clusters. + + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. + + To set the location attribute: + ▫ provide the argument --cluster on the command line with a + fully specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --cluster-location on the command line; + ▫ set the property run/cluster_location; + ▫ specify the cluster location from a list of available zones. + + Only applicable if connecting to Cloud Run for Anthos deployed on + VMware. Specify --platform=kubernetes to use: + + --context=CONTEXT + The name of the context in your kubectl config file to use for + connecting. + + --kubeconfig=KUBECONFIG + The absolute path to your kubectl config file. If not specified, + the colon- or semicolon-delimited list of paths specified by + $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to + ~/.kube/config. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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: + + $ gcloud beta run multi-region-services update + diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 7bf1d5772..1f14553e5 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -419,10 +419,11 @@ FLAGS Run the application in a second generation execution environment. --[no-]invoker-iam-check - Indicates whether an IAM check should occur when invoking the - container. This is Enabled by default. Disabling this flag is not - available in all projects. Use --invoker-iam-check to enable and - --no-invoker-iam-check to disable. + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. --max-surge=MAX_SURGE A maximum percentage of instances that will be moved in each step of diff --git a/gcloud/alpha/scc/sources/describe b/gcloud/alpha/scc/sources/describe index c52cd01f5..8ba746c1a 100644 --- a/gcloud/alpha/scc/sources/describe +++ b/gcloud/alpha/scc/sources/describe @@ -62,7 +62,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for + This command uses the securitycenter/v2 API. The full documentation for this API can be found at: https://cloud.google.com/security-command-center NOTES diff --git a/gcloud/alpha/service-extensions/wasm-plugin-versions/create b/gcloud/alpha/service-extensions/wasm-plugin-versions/create index 163f7e6c0..5ecdab29d 100644 --- a/gcloud/alpha/service-extensions/wasm-plugin-versions/create +++ b/gcloud/alpha/service-extensions/wasm-plugin-versions/create @@ -111,5 +111,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta service-extensions wasm-plugin-versions create diff --git a/gcloud/alpha/service-extensions/wasm-plugin-versions/delete b/gcloud/alpha/service-extensions/wasm-plugin-versions/delete index 17c6d7724..0643bf759 100644 --- a/gcloud/alpha/service-extensions/wasm-plugin-versions/delete +++ b/gcloud/alpha/service-extensions/wasm-plugin-versions/delete @@ -78,5 +78,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta service-extensions wasm-plugin-versions delete diff --git a/gcloud/alpha/service-extensions/wasm-plugin-versions/describe b/gcloud/alpha/service-extensions/wasm-plugin-versions/describe index 4fdfbe2fa..6ee8b0f34 100644 --- a/gcloud/alpha/service-extensions/wasm-plugin-versions/describe +++ b/gcloud/alpha/service-extensions/wasm-plugin-versions/describe @@ -73,5 +73,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta service-extensions wasm-plugin-versions describe diff --git a/gcloud/alpha/service-extensions/wasm-plugin-versions/help b/gcloud/alpha/service-extensions/wasm-plugin-versions/help index 893714ef6..9fa8e25dc 100644 --- a/gcloud/alpha/service-extensions/wasm-plugin-versions/help +++ b/gcloud/alpha/service-extensions/wasm-plugin-versions/help @@ -33,5 +33,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta service-extensions wasm-plugin-versions diff --git a/gcloud/alpha/service-extensions/wasm-plugin-versions/list b/gcloud/alpha/service-extensions/wasm-plugin-versions/list index ef7c8b29e..c97c0c44b 100644 --- a/gcloud/alpha/service-extensions/wasm-plugin-versions/list +++ b/gcloud/alpha/service-extensions/wasm-plugin-versions/list @@ -98,5 +98,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta service-extensions wasm-plugin-versions list diff --git a/gcloud/alpha/service-extensions/wasm-plugins/create b/gcloud/alpha/service-extensions/wasm-plugins/create index bd93d462f..6188d223f 100644 --- a/gcloud/alpha/service-extensions/wasm-plugins/create +++ b/gcloud/alpha/service-extensions/wasm-plugins/create @@ -133,5 +133,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta service-extensions wasm-plugins create diff --git a/gcloud/alpha/service-extensions/wasm-plugins/delete b/gcloud/alpha/service-extensions/wasm-plugins/delete index 94204a1d1..d8b8f934c 100644 --- a/gcloud/alpha/service-extensions/wasm-plugins/delete +++ b/gcloud/alpha/service-extensions/wasm-plugins/delete @@ -68,5 +68,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta service-extensions wasm-plugins delete diff --git a/gcloud/alpha/service-extensions/wasm-plugins/describe b/gcloud/alpha/service-extensions/wasm-plugins/describe index a19fc2ca4..87748af95 100644 --- a/gcloud/alpha/service-extensions/wasm-plugins/describe +++ b/gcloud/alpha/service-extensions/wasm-plugins/describe @@ -63,5 +63,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta service-extensions wasm-plugins describe diff --git a/gcloud/alpha/service-extensions/wasm-plugins/help b/gcloud/alpha/service-extensions/wasm-plugins/help index bffc62d53..1c7a23fef 100644 --- a/gcloud/alpha/service-extensions/wasm-plugins/help +++ b/gcloud/alpha/service-extensions/wasm-plugins/help @@ -35,5 +35,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta service-extensions wasm-plugins diff --git a/gcloud/alpha/service-extensions/wasm-plugins/list b/gcloud/alpha/service-extensions/wasm-plugins/list index 99d3f34bb..3f4ebb4f6 100644 --- a/gcloud/alpha/service-extensions/wasm-plugins/list +++ b/gcloud/alpha/service-extensions/wasm-plugins/list @@ -82,5 +82,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta service-extensions wasm-plugins list diff --git a/gcloud/alpha/service-extensions/wasm-plugins/update b/gcloud/alpha/service-extensions/wasm-plugins/update index 4c1ee610b..33b2bc515 100644 --- a/gcloud/alpha/service-extensions/wasm-plugins/update +++ b/gcloud/alpha/service-extensions/wasm-plugins/update @@ -156,5 +156,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta service-extensions wasm-plugins update diff --git a/gcloud/alpha/spanner/instances/get-locations b/gcloud/alpha/spanner/instances/get-locations new file mode 100644 index 000000000..a7ac9fad2 --- /dev/null +++ b/gcloud/alpha/spanner/instances/get-locations @@ -0,0 +1,43 @@ +NAME + gcloud alpha spanner instances get-locations - get the location of every + replica in a Cloud Spanner instance + +SYNOPSIS + gcloud alpha spanner instances get-locations INSTANCE [--verbose] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get the location of every replica in a Cloud Spanner instance. + +EXAMPLES + To get the location of every replica in a Cloud Spanner instance in this + project, run: + + $ gcloud alpha spanner instances get-locations my-instance-id + +POSITIONAL ARGUMENTS + INSTANCE + Cloud Spanner instance ID. + +FLAGS + --verbose + Indicates that both regions and types of replicas be returned. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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 spanner instances get-locations + + $ gcloud beta spanner instances get-locations + diff --git a/gcloud/alpha/spanner/instances/help b/gcloud/alpha/spanner/instances/help index f3de945c3..a57a5f6b4 100644 --- a/gcloud/alpha/spanner/instances/help +++ b/gcloud/alpha/spanner/instances/help @@ -36,6 +36,9 @@ COMMANDS get-iam-policy (ALPHA) Get the IAM policy for a Cloud Spanner instance. + get-locations + (ALPHA) Get the location of every replica in a Cloud Spanner instance. + list (ALPHA) List the Cloud Spanner instances in this project. diff --git a/gcloud/alpha/sql/export/bak b/gcloud/alpha/sql/export/bak index 444ce65f9..ecae03afd 100644 --- a/gcloud/alpha/sql/export/bak +++ b/gcloud/alpha/sql/export/bak @@ -6,6 +6,8 @@ SYNOPSIS gcloud alpha sql export bak INSTANCE URI --database=DATABASE,[DATABASE,...], -d DATABASE,[DATABASE,...] [--async] [--bak-type=BAK_TYPE; default="FULL"] [--differential-base] + [--export-log-end-time=EXPORT_LOG_END_TIME] + [--export-log-start-time=EXPORT_LOG_START_TIME] [--stripe_count=STRIPE_COUNT] [--[no-]striped] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -41,12 +43,24 @@ OPTIONAL FLAGS --bak-type=BAK_TYPE; default="FULL" Type of bak file that will be exported, FULL or DIFF. SQL Server only. - BAK_TYPE must be one of: FULL, DIFF. + BAK_TYPE must be one of: FULL, DIFF, TLOG. --differential-base Whether the bak file export can be used as differential base for future differential backup. SQL Server only + --export-log-end-time=EXPORT_LOG_END_TIME + Optional flag. The end time of the transaction log files that are + included in the export file. Use this flag to export transaction logs + for Cloud SQL for SQL Server only. Format: YYYY-MM-DDTHH:MM:SSZ, UTC + timezone only. + + --export-log-start-time=EXPORT_LOG_START_TIME + Optional flag. The start time of the transaction log files that are + included in the export file. Use this flag to export transaction logs + for Cloud SQL for SQL Server only. Format: YYYY-MM-DDTHH:MM:SSZ, UTC + timezone only. + --stripe_count=STRIPE_COUNT Specifies the number of stripes to use for SQL Server exports. diff --git a/gcloud/alpha/storage/buckets/create b/gcloud/alpha/storage/buckets/create index 30144b4be..5a4fad5f1 100644 --- a/gcloud/alpha/storage/buckets/create +++ b/gcloud/alpha/storage/buckets/create @@ -59,7 +59,8 @@ FLAGS "Standard". --enable-hierarchical-namespace - Enable heirarchical namepsace for the bucket + Enable hierarchical namespace for the bucket. To use this flag, you + must also use --uniform-bucket-level-access --enable-per-object-retention Enables each object in the bucket to have its own retention settings, diff --git a/gcloud/alpha/workstations/configs/create b/gcloud/alpha/workstations/configs/create index 02cfbecfc..9e0371980 100644 --- a/gcloud/alpha/workstations/configs/create +++ b/gcloud/alpha/workstations/configs/create @@ -20,6 +20,7 @@ SYNOPSIS [--enable-ssh-to-vm] [--ephemeral-directory=[PROPERTY=VALUE,...]] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] + [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] [--network-tags=[NETWORK_TAGS,...]] [--pd-disk-size=PD_DISK_SIZE; default=200] [--pd-disk-type=PD_DISK_TYPE; default="pd-standard"] @@ -283,6 +284,13 @@ FLAGS machines that the workstations created under this configuration will run on. + --max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT + Maximum number of workstations under this configuration a user can have + workstations.workstation.use permission on. + + If not specified, defaults to 0, which indicates a user can have + unlimited number of workstations under this configuration. + --network-tags=[NETWORK_TAGS,...] Network tags to add to the Google Compute Engine machines backing the Workstations. diff --git a/gcloud/alpha/workstations/configs/update b/gcloud/alpha/workstations/configs/update index 130676ee6..74175ae3c 100644 --- a/gcloud/alpha/workstations/configs/update +++ b/gcloud/alpha/workstations/configs/update @@ -15,9 +15,10 @@ SYNOPSIS [--disable-public-ip-addresses] [--enable-audit-agent] [--enable-confidential-compute] [--enable-nested-virtualization] [--idle-timeout=IDLE_TIMEOUT] [--labels=[LABELS,...]] - [--machine-type=MACHINE_TYPE] [--network-tags=[NETWORK_TAGS,...]] - [--pool-size=POOL_SIZE] [--running-timeout=RUNNING_TIMEOUT] - [--service-account=SERVICE_ACCOUNT] + [--machine-type=MACHINE_TYPE] + [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] + [--network-tags=[NETWORK_TAGS,...]] [--pool-size=POOL_SIZE] + [--running-timeout=RUNNING_TIMEOUT] [--service-account=SERVICE_ACCOUNT] [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--vm-tags=[VM_TAGS,...]] @@ -244,6 +245,13 @@ FLAGS machines that the workstations created under this configuration will run on. + --max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT + Maximum number of workstations under this configuration a user can have + workstations.workstation.use permission on. + + If not specified, defaults to 0, which indicates a user can have + unlimited number of workstations under this configuration. + --network-tags=[NETWORK_TAGS,...] Network tags to add to the Google Compute Engine machines backing the Workstations. diff --git a/gcloud/artifacts/help b/gcloud/artifacts/help index cefb025b0..b2de8c742 100644 --- a/gcloud/artifacts/help +++ b/gcloud/artifacts/help @@ -48,6 +48,9 @@ GROUPS repositories Manage Artifact Registry repositories. + rules + Manage Artifact Registry rules. + sbom Manage Artifact SBOMs. diff --git a/gcloud/artifacts/rules/create b/gcloud/artifacts/rules/create new file mode 100644 index 000000000..a65907eee --- /dev/null +++ b/gcloud/artifacts/rules/create @@ -0,0 +1,98 @@ +NAME + gcloud artifacts rules create - create an Artifact Registry rule + +SYNOPSIS + gcloud artifacts rules create + (RULE : --location=LOCATION --repository=REPOSITORY) --action=ACTION + [--condition=CONDITION] [--operation=OPERATION; default="DOWNLOAD"] + [--package=PACKAGE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new Artifact Registry rule. + + This command can fail for the following reasons: + ▪ A rule with the same name already exists. + ▪ The active account does not have permission to create repositories. + ▪ A rule with given package already exists. + +EXAMPLES + To create a rule with the name my-rule for package my-pkg with action deny + under the current project, repository, run: + + $ gcloud artifacts rules create my-rule --package=my-pkg \ + --action=deny + +POSITIONAL ARGUMENTS + Rule resource - The Artifact Registry rule to create. 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 rule on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + RULE + ID of the rule or fully qualified identifier for the rule. + + To set the rule attribute: + ▸ provide the argument rule on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the rule. Overrides the default artifacts/location + property value for this command invocation. To configure the default + location, use the command: gcloud config set artifacts/location. + + To set the location attribute: + ▸ provide the argument rule on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + The repository associated with the rule. Overrides the default + artifacts/repository property value for this command invocation. To + configure the default repository, use the command: gcloud config set + artifacts/repository. + + To set the repository attribute: + ▸ provide the argument rule on the command line with a fully + specified name; + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. + +REQUIRED FLAGS + --action=ACTION + The action the rule would make, can only be DENY or ALLOW. ACTION must + be one of: allow, deny. + +OPTIONAL FLAGS + --condition=CONDITION + The CEL expression for the rule. + + --operation=OPERATION; default="DOWNLOAD" + The operation the rule applies to. OPERATION must be (only one value is + supported): download. + + --package=PACKAGE + The package the rule applies to. Empty means the rule is set for the + entire repository. + +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 artifactregistry/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/artifacts/docs/ diff --git a/gcloud/artifacts/rules/delete b/gcloud/artifacts/rules/delete new file mode 100644 index 000000000..43f711521 --- /dev/null +++ b/gcloud/artifacts/rules/delete @@ -0,0 +1,78 @@ +NAME + gcloud artifacts rules delete - delete an Artifact Registry rule + +SYNOPSIS + gcloud artifacts rules delete + (RULE : --location=LOCATION --repository=REPOSITORY) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an Artifact Registry rule. + + This command can fail for the following reasons: + ▪ The specified rule does not exist. + ▪ The active account does not have permission to delete rules. + +EXAMPLES + To delete a rule named my-rule under the current project, repository, and + location, run: + + $ gcloud artifacts rules delete my-repo + +POSITIONAL ARGUMENTS + Rule resource - The Artifact Registry rule to delete. 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 rule on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + RULE + ID of the rule or fully qualified identifier for the rule. + + To set the rule attribute: + ▸ provide the argument rule on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the rule. Overrides the default artifacts/location + property value for this command invocation. To configure the default + location, use the command: gcloud config set artifacts/location. + + To set the location attribute: + ▸ provide the argument rule on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + The repository associated with the rule. Overrides the default + artifacts/repository property value for this command invocation. To + configure the default repository, use the command: gcloud config set + artifacts/repository. + + To set the repository attribute: + ▸ provide the argument rule on the command line with a fully + specified name; + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. + +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 artifactregistry/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/artifacts/docs/ diff --git a/gcloud/artifacts/rules/describe b/gcloud/artifacts/rules/describe new file mode 100644 index 000000000..b3fbf97d3 --- /dev/null +++ b/gcloud/artifacts/rules/describe @@ -0,0 +1,78 @@ +NAME + gcloud artifacts rules describe - describe an Artifact Registry rule + +SYNOPSIS + gcloud artifacts rules describe + (RULE : --location=LOCATION --repository=REPOSITORY) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an Artifact Registry rule. + + This command can fail for the following reasons: + ▪ The specified rule does not exist. + ▪ The active account does not have permission to view rules. + +EXAMPLES + To describe a rule named my-rule under the current project, repository, and + location, run: + + $ gcloud artifacts rules describe my-rule + +POSITIONAL ARGUMENTS + Rule resource - The Artifact Registry rule to describe. 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 rule on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + RULE + ID of the rule or fully qualified identifier for the rule. + + To set the rule attribute: + ▸ provide the argument rule on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the rule. Overrides the default artifacts/location + property value for this command invocation. To configure the default + location, use the command: gcloud config set artifacts/location. + + To set the location attribute: + ▸ provide the argument rule on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + The repository associated with the rule. Overrides the default + artifacts/repository property value for this command invocation. To + configure the default repository, use the command: gcloud config set + artifacts/repository. + + To set the repository attribute: + ▸ provide the argument rule on the command line with a fully + specified name; + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. + +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 artifactregistry/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/artifacts/docs/ diff --git a/gcloud/artifacts/rules/help b/gcloud/artifacts/rules/help new file mode 100644 index 000000000..9b30e87b3 --- /dev/null +++ b/gcloud/artifacts/rules/help @@ -0,0 +1,44 @@ +NAME + gcloud artifacts rules - manage Artifact Registry rules + +SYNOPSIS + gcloud artifacts rules COMMAND [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list all rules in the current project and artifacts/repository and + artifacts/location properties are set, run: + + $ gcloud artifacts rules list + + To list rules under repository my-repo in the current project and location, + run: + + $ gcloud artifacts rules list --repository=my-repo + + To delete rule my-rule under repository my-repo in the current project and + location, run: + + $ gcloud artifacts rules delete my-rule --repository=my-repo + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create an Artifact Registry rule. + + delete + Delete an Artifact Registry rule. + + describe + Describe an Artifact Registry rule. + + list + List Artifact Registry rules. + + update + Update an Artifact Registry rule. diff --git a/gcloud/artifacts/rules/list b/gcloud/artifacts/rules/list new file mode 100644 index 000000000..8835f74d4 --- /dev/null +++ b/gcloud/artifacts/rules/list @@ -0,0 +1,93 @@ +NAME + gcloud artifacts rules list - list Artifact Registry rules + +SYNOPSIS + gcloud artifacts rules list [--location=LOCATION --repository=REPOSITORY] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all Artifact Registry rules for the specified repository. + + This command can fail for the following reasons: + ▪ The specified repository does not exist. + ▪ The active account does not have permission to list rules. + + To specify the maximum number of rules to list, use the --limit flag. + +EXAMPLES + The following command lists a maximum of five rules for repository my-repo: + + $ gcloud artifacts rules list --limit=5 + +FLAGS + Repository resource - The parent repository for the list of rules. 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 --repository on the command line with a fully + specified name; + ◆ set the property artifacts/repository with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + Location of the repository. Overrides the default artifacts/location + property value for this command invocation. To configure the default + location, use the command: gcloud config set artifacts/location. + + To set the location attribute: + ▸ provide the argument --repository on the command line with a + fully specified name; + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. + + To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. + +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. + +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 artifactregistry/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/artifacts/docs/ diff --git a/gcloud/artifacts/rules/update b/gcloud/artifacts/rules/update new file mode 100644 index 000000000..fb41f302b --- /dev/null +++ b/gcloud/artifacts/rules/update @@ -0,0 +1,97 @@ +NAME + gcloud artifacts rules update - update an Artifact Registry rule + +SYNOPSIS + gcloud artifacts rules update + (RULE : --location=LOCATION --repository=REPOSITORY) [--action=ACTION] + [--condition=CONDITION] [--operation=OPERATION] [--package=PACKAGE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an Artifact Registry rule. + + This command can fail for the following reasons: + ▪ The rule does not exist. + ▪ A rule with the same name already exists. + ▪ The active account does not have permission to create repositories. + ▪ A rule with given package already exists. + +EXAMPLES + To create a rule with the name my-rule for package my-pkg with action deny + under the current project, repository, run: + + $ gcloud artifacts rules update my-rule --package=my-pkg \ + --action=deny + +POSITIONAL ARGUMENTS + Rule resource - The Artifact Registry rule to update. 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 rule on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + RULE + ID of the rule or fully qualified identifier for the rule. + + To set the rule attribute: + ▸ provide the argument rule on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the rule. Overrides the default artifacts/location + property value for this command invocation. To configure the default + location, use the command: gcloud config set artifacts/location. + + To set the location attribute: + ▸ provide the argument rule on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + The repository associated with the rule. Overrides the default + artifacts/repository property value for this command invocation. To + configure the default repository, use the command: gcloud config set + artifacts/repository. + + To set the repository attribute: + ▸ provide the argument rule on the command line with a fully + specified name; + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. + +FLAGS + --action=ACTION + The action the rule would make, can only be DENY or ALLOW. ACTION must + be one of: allow, deny. + + --condition=CONDITION + The CEL expression for the rule. + + --operation=OPERATION + The operation the rule applies to. OPERATION must be (only one value is + supported): download. + + --package=PACKAGE + The package the rule applies to. + +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 artifactregistry/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/artifacts/docs/ diff --git a/gcloud/assured/workloads/create b/gcloud/assured/workloads/create index 27fcf38d0..a8978f011 100644 --- a/gcloud/assured/workloads/create +++ b/gcloud/assured/workloads/create @@ -90,7 +90,7 @@ REQUIRED FLAGS cjis, eu-regions-and-support, fedramp-high, fedramp-moderate, healthcare-and-life-sciences-controls, healthcare-and-life-sciences-controls-us-support, hipaa, hitrust, il2, - il4, il5, isr-regions, isr-regions-and-support, itar, + il4, il5, irs-1075, isr-regions, isr-regions-and-support, itar, jp-regions-and-support, ksa-regions-and-support-with-sovereignty-controls, regional-controls, us-regional-access. diff --git a/gcloud/beta/assured/workloads/create b/gcloud/beta/assured/workloads/create index a4e5f1a0f..06fad3e1d 100644 --- a/gcloud/beta/assured/workloads/create +++ b/gcloud/beta/assured/workloads/create @@ -90,7 +90,7 @@ REQUIRED FLAGS cjis, eu-regions-and-support, fedramp-high, fedramp-moderate, healthcare-and-life-sciences-controls, healthcare-and-life-sciences-controls-us-support, hipaa, hitrust, il2, - il4, il5, isr-regions, isr-regions-and-support, itar, + il4, il5, irs-1075, isr-regions, isr-regions-and-support, itar, jp-regions-and-support, ksa-regions-and-support-with-sovereignty-controls, regional-controls, us-regional-access. diff --git a/gcloud/beta/bigtable/backups/create b/gcloud/beta/bigtable/backups/create index 5bb692dc4..864486953 100644 --- a/gcloud/beta/bigtable/backups/create +++ b/gcloud/beta/bigtable/backups/create @@ -7,7 +7,8 @@ SYNOPSIS (BACKUP : --cluster=CLUSTER --instance=INSTANCE) --table=TABLE (--expiration-date=EXPIRATION_DATE | --retention-period=RETENTION_PERIOD) [--async] - [GCLOUD_WIDE_FLAG ...] + [--backup-type=BACKUP_TYPE] + [--hot-to-standard-time=HOT_TO_STANDARD_TIME] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates a backup of a Cloud Bigtable table. @@ -28,6 +29,31 @@ EXAMPLES --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ --table=TABLE_NAME --retention-period=2w + To create a hot backup 'BACKUP_NAME' from table 'TABLE_NAME' which expires + in 2 weeks from now, run: + + $ gcloud beta bigtable backups create BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --retention-period=2w --backup-type=HOT + + To create a hot backup 'BACKUP_NAME' from table 'TABLE_NAME' which will be + converted to a standard backup at '2019-03-31T10:49:41Z' and expires in 2 + weeks from now, run: + + $ gcloud beta bigtable backups create BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --retention-period=2w --backup-type=HOT \ + --hot-to-standard-time=2019-03-31T10:49:41Z + + To create a hot backup 'BACKUP_NAME' from table 'TABLE_NAME' which will be + converted to a standard backup in 1 week from now and expires in 2 weeks + from now, run: + + $ gcloud beta bigtable backups create BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --retention-period=2w --backup-type=HOT \ + --hot-to-standard-time=+P1w + POSITIONAL ARGUMENTS Backup resource - The Cloud Bigtable backup to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -74,20 +100,38 @@ REQUIRED FLAGS Exactly one of these must be specified: --expiration-date=EXPIRATION_DATE - Absolute expiration time of the backup; must be at least 6 hours and - at most 90 days from the time the request is received. See $ gcloud - topic datetimes for information on date/time formats. + Absolute expiration time of the backup. From the time the request is + received, must be: + ▸ At least 6 hours in the future + ▸ At most 90 days in the future + + See $ gcloud topic datetimes for information on date/time formats. --retention-period=RETENTION_PERIOD - Retention period of the backup relative from now; must be at least 6 - hours and at most 90 days. See $ gcloud topic datetimes for - information on duration formats. + Retention period of the backup relative from now; must be: + ▸ At least 6 hours + ▸ At most 90 days + + See $ gcloud topic datetimes for information on duration formats. OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to complete. + --backup-type=BACKUP_TYPE + Type of the backup; whether the backup is a standard backup or a hot + backup. BACKUP_TYPE must be one of: backup-type-unspecified, hot, + standard. + + --hot-to-standard-time=HOT_TO_STANDARD_TIME + Time at which a hot backup will be converted to a standard backup + relative from now; must be: + ◆ At least 24 hours + + Only applies for hot backups. See $ gcloud topic datetimes for + information on date/time formats. + 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/bigtable/backups/update b/gcloud/beta/bigtable/backups/update index 921483bf8..3f3be7e37 100644 --- a/gcloud/beta/bigtable/backups/update +++ b/gcloud/beta/bigtable/backups/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta bigtable backups update (BACKUP : --cluster=CLUSTER --instance=INSTANCE) + [--hot-to-standard-time=HOT_TO_STANDARD_TIME] [--expiration-date=EXPIRATION_DATE | --retention-period=RETENTION_PERIOD] [GCLOUD_WIDE_FLAG ...] @@ -19,6 +20,26 @@ EXAMPLES --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ --retention-period=7d + To update the hot-to-standard time of backup 'BACKUP_NAME' to + '2019-03-31T10:49:41Z', run: + + $ gcloud beta bigtable backups update BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --hot-to-standard-time=2019-03-31T10:49:41Z + + To update the hot-to-standard time of backup 'BACKUP_NAME' to 7 days from + now, run: + + $ gcloud beta bigtable backups update BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --hot-to-standard-time=+P7d + + To clear the hot-to-standard time of backup 'BACKUP_NAME', run: + + $ gcloud beta bigtable backups update BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --hot-to-standard-time='' + POSITIONAL ARGUMENTS Backup resource - Cloud Bigtable backup to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -59,6 +80,12 @@ POSITIONAL ARGUMENTS ▸ provide the argument --instance on the command line. FLAGS + --hot-to-standard-time=HOT_TO_STANDARD_TIME + Time at which a hot backup will be converted to a standard backup; must + be at least 24 hours from backup creation time. Only applies for hot + backups. See $ gcloud topic datetimes for information on date/time + formats. See $ gcloud bigtable backups describe for creation time. + At most one of these can be specified: --expiration-date=EXPIRATION_DATE diff --git a/gcloud/beta/builds/submit b/gcloud/beta/builds/submit index d9074ccbc..ad23a280d 100644 --- a/gcloud/beta/builds/submit +++ b/gcloud/beta/builds/submit @@ -99,7 +99,8 @@ FLAGS --default-buckets-behavior=DEFAULT_BUCKETS_BEHAVIOR How default buckets are setup. DEFAULT_BUCKETS_BEHAVIOR must be one of: - default-logs-bucket-behavior-unspecified, regional-user-owned-bucket. + default-logs-bucket-behavior-unspecified, legacy-bucket, + regional-user-owned-bucket. --dir=DIR Directory, relative to the source root, in which to run the build. This diff --git a/gcloud/beta/compute/instant-snapshots/create b/gcloud/beta/compute/instant-snapshots/create index 487f63819..7bdcbc8c0 100644 --- a/gcloud/beta/compute/instant-snapshots/create +++ b/gcloud/beta/compute/instant-snapshots/create @@ -9,8 +9,8 @@ SYNOPSIS DESCRIPTION (BETA) gcloud beta compute instant-snapshots create creates an instant - snapshot of persistent disk. Instant snapshots are useful for backing up - persistent disk data. + snapshot of a disk. Instant snapshots are useful for backing up the disk + data. EXAMPLES To create an instant snapshot 'my-instant-snap' from a disk 'my-disk' in diff --git a/gcloud/beta/compute/interconnects/attachments/delete b/gcloud/beta/compute/interconnects/attachments/delete index b3395c1b8..76ab21d6f 100644 --- a/gcloud/beta/compute/interconnects/attachments/delete +++ b/gcloud/beta/compute/interconnects/attachments/delete @@ -1,5 +1,6 @@ NAME - gcloud beta compute interconnects attachments delete - delete interconnects + gcloud beta compute interconnects attachments delete - delete Compute + Engine interconnect attachments SYNOPSIS gcloud beta compute interconnects attachments delete NAME [NAME ...] @@ -7,7 +8,7 @@ SYNOPSIS DESCRIPTION (BETA) gcloud beta compute interconnects attachments delete deletes Compute - Engine interconnect attachment. + Engine interconnect attachments. POSITIONAL ARGUMENTS NAME [NAME ...] diff --git a/gcloud/beta/compute/interconnects/attachments/help b/gcloud/beta/compute/interconnects/attachments/help index 0ac49e013..021fe61e9 100644 --- a/gcloud/beta/compute/interconnects/attachments/help +++ b/gcloud/beta/compute/interconnects/attachments/help @@ -27,7 +27,7 @@ COMMANDS COMMAND is one of the following: delete - (BETA) Delete interconnects. + (BETA) Delete Compute Engine interconnect attachments. describe (BETA) Describe a Compute Engine interconnect attachment. diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index 996014821..df1c64ed7 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -568,6 +568,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 16d8da7e8..de8043f50 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -600,6 +600,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index f0b4378ce..ade9c1ff5 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -612,6 +612,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index f599e98ec..31335e1fe 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -615,6 +615,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 377673eec..a31341a41 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -576,6 +576,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 1e767fb2c..58f482567 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -24,17 +24,19 @@ SYNOPSIS [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--disable-default-snat] [--disable-pod-cidr-overprovision] - [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autorepair] - [--no-enable-autoupgrade] [--enable-cilium-clusterwide-network-policy] - [--enable-cloud-logging] [--enable-cloud-monitoring] - [--enable-cloud-run-alpha] [--enable-confidential-nodes] - [--enable-confidential-storage] [--enable-cost-allocation] - [--enable-dataplane-v2] [--enable-fleet] [--enable-fqdn-network-policy] + [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] + [--enable-authorized-networks-on-private-endpoint] + [--enable-autorepair] [--no-enable-autoupgrade] + [--enable-cilium-clusterwide-network-policy] [--enable-cloud-logging] + [--enable-cloud-monitoring] [--enable-cloud-run-alpha] + [--enable-confidential-nodes] [--enable-confidential-storage] + [--enable-cost-allocation] [--enable-dataplane-v2] + [--enable-dns-access] [--enable-fleet] [--enable-fqdn-network-policy] [--enable-gke-oidc] [--enable-google-cloud-access] [--enable-gvnic] [--enable-identity-service] [--enable-image-streaming] [--enable-insecure-kubelet-readonly-port] - [--enable-intra-node-visibility] [--enable-ip-alias] - [--enable-kubernetes-alpha] + [--enable-intra-node-visibility] [--enable-ip-access] + [--enable-ip-alias] [--enable-kubernetes-alpha] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-l4-ilb-subsetting] [--enable-legacy-authorization] [--enable-logging-monitoring-system-only] [--enable-managed-prometheus] @@ -434,6 +436,10 @@ FLAGS DISK_TYPE must be one of: pd-standard, pd-ssd, pd-balanced, hyperdisk-balanced, hyperdisk-extreme, hyperdisk-throughput. + --enable-authorized-networks-on-private-endpoint + Enable enforcement of --master-authorized-networks CIDR ranges for + traffic reaching cluster's control plane via private IP. + --enable-autorepair Enable node autorepair feature for a cluster's default node pool(s). @@ -514,6 +520,11 @@ FLAGS Enables the new eBPF dataplane for GKE clusters that is required for network security, scalability and visibility features. + --enable-dns-access + Enable access to the cluster's control plane over DNS-based endpoint. + + DNS-based control plane access is recommended. + --enable-fleet Set cluster project as the fleet host project. This will register the cluster to the same project. To register the cluster to a fleet in a @@ -576,6 +587,10 @@ FLAGS Enabling it on an existing cluster causes the cluster master and the cluster nodes to restart, which might cause a disruption. + --enable-ip-access + Enable access to the cluster's control plane over private IP and public + IP if --enable-private-endpoint is not enabled. + --enable-ip-alias Enable use of alias IPs (https://cloud.google.com/compute/docs/alias-ip/) for Pod IPs. This diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 46f29b160..63f9acb38 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -14,9 +14,10 @@ SYNOPSIS [--containerd-config-from-file=PATH_TO_FILE] [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] + [--enable-authorized-networks-on-private-endpoint] [--enable-backup-restore] [--enable-cilium-clusterwide-network-policy] - [--enable-fleet] [--enable-google-cloud-access] - [--enable-kubernetes-unstable-apis=API,[API,...]] + [--enable-dns-access] [--enable-fleet] [--enable-google-cloud-access] + [--enable-ip-access] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] [--enable-ray-operator] [--enable-secret-manager] [--fleet-project=PROJECT_ID_OR_NUMBER] @@ -219,6 +220,10 @@ FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. + --enable-authorized-networks-on-private-endpoint + Enable enforcement of --master-authorized-networks CIDR ranges for + traffic reaching cluster's control plane via private IP. + --enable-backup-restore Enable the Backup for GKE add-on. This add-on is disabled by default. To learn more, see the Backup for GKE overview: @@ -228,6 +233,11 @@ FLAGS Enable Cilium Clusterwide Network Policies on the cluster. Disabled by default. + --enable-dns-access + Enable access to the cluster's control plane over DNS-based endpoint. + + DNS-based control plane access is recommended. + --enable-fleet Set cluster project as the fleet host project. This will register the cluster to the same project. To register the cluster to a fleet in a @@ -239,6 +249,10 @@ FLAGS Google Cloud can reach the public control plane endpoint of your cluster. + --enable-ip-access + Enable access to the cluster's control plane over private IP and public + IP if --enable-private-endpoint is not enabled. + --enable-kubernetes-unstable-apis=API,[API,...] Enable Kubernetes beta API features on this cluster. Beta APIs are not expected to be production ready and should be avoided in diff --git a/gcloud/beta/container/clusters/get-credentials b/gcloud/beta/container/clusters/get-credentials index 3c5425e37..159a8f113 100644 --- a/gcloud/beta/container/clusters/get-credentials +++ b/gcloud/beta/container/clusters/get-credentials @@ -3,7 +3,8 @@ NAME running cluster SYNOPSIS - gcloud beta container clusters get-credentials NAME [--internal-ip] + gcloud beta container clusters get-credentials NAME [--dns-endpoint] + [--internal-ip] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...] @@ -46,6 +47,9 @@ POSITIONAL ARGUMENTS container/cluster property value for this command invocation. FLAGS + --dns-endpoint + Whether to use the DNS-based endpoint for the cluster address. + --internal-ip Whether to use the internal IP address of the cluster endpoint. diff --git a/gcloud/beta/container/clusters/get-upgrade-info b/gcloud/beta/container/clusters/get-upgrade-info new file mode 100644 index 000000000..0a9ce3c1a --- /dev/null +++ b/gcloud/beta/container/clusters/get-upgrade-info @@ -0,0 +1,56 @@ +NAME + gcloud beta container clusters get-upgrade-info - get information about + upgrades for existing clusters including auto upgrade status, upgrade + history, upgrade targets, and end of support timelines + +SYNOPSIS + gcloud beta container clusters get-upgrade-info NAME + [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get information about upgrades for existing clusters including auto + upgrade status, upgrade history, upgrade targets, and end of support + timelines. + +EXAMPLES + To get upgrade information for an existing cluster, run: + + $ gcloud beta container clusters get-upgrade-info sample-cluster + +POSITIONAL ARGUMENTS + NAME + The name of your existing cluster. + +FLAGS + At most one of these can be specified: + + --location=LOCATION + Compute zone or region (e.g. us-central1-a or us-central1) for the + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. + + --region=REGION + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. + + --zone=ZONE, -z ZONE + Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the + default compute/zone property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container clusters get-upgrade-info + diff --git a/gcloud/beta/container/clusters/help b/gcloud/beta/container/clusters/help index 3c3ece1cb..b1194ba53 100644 --- a/gcloud/beta/container/clusters/help +++ b/gcloud/beta/container/clusters/help @@ -58,6 +58,11 @@ COMMANDS get-credentials (BETA) Fetch credentials for a running cluster. + get-upgrade-info + (BETA) Get information about upgrades for existing clusters including + auto upgrade status, upgrade history, upgrade targets, and end of + support timelines. + list (BETA) List existing clusters for running containers. diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index 56c1415f9..828f2eec6 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -16,16 +16,14 @@ SYNOPSIS | --[no-]enable-cilium-clusterwide-network-policy | --enable-cost-allocation | --enable-fleet | --enable-fqdn-network-policy | --enable-gke-oidc - | --enable-google-cloud-access | --enable-identity-service - | --enable-image-streaming | --enable-insecure-kubelet-readonly-port + | --enable-identity-service | --enable-image-streaming + | --enable-insecure-kubelet-readonly-port | --enable-intra-node-visibility | --enable-kubernetes-unstable-apis=API,[API,...] | --enable-l4-ilb-subsetting | --enable-legacy-authorization - | --enable-logging-monitoring-system-only - | --enable-master-authorized-networks | --enable-master-global-access - | --enable-multi-networking | --enable-network-policy - | --enable-pod-security-policy | --enable-private-endpoint - | --[no-]enable-ray-cluster-logging + | --enable-logging-monitoring-system-only | --enable-multi-networking + | --enable-network-policy | --enable-pod-security-policy + | --enable-private-nodes | --[no-]enable-ray-cluster-logging | --[no-]enable-ray-cluster-monitoring | --enable-secret-manager | --enable-service-externalips | --enable-shielded-nodes | --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling @@ -76,6 +74,11 @@ SYNOPSIS | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics + | --enable-authorized-networks-on-private-endpoint + --enable-dns-access --enable-google-cloud-access --enable-ip-access + --enable-master-global-access --enable-private-endpoint + --enable-master-authorized-networks + --master-authorized-networks=NETWORK,[NETWORK,...] | [--enable-autoprovisioning : --autoprovisioning-config-file=PATH_TO_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE @@ -101,9 +104,7 @@ SYNOPSIS | --password=PASSWORD --enable-basic-auth | --username=USERNAME, -u USERNAME) [--async] [--cloud-run-config=[load-balancer-type=EXTERNAL,...]] - [--istio-config=[auth=MTLS_PERMISSIVE,...]] - [--master-authorized-networks=NETWORK,[NETWORK,...]] - [--node-pool=NODE_POOL] + [--istio-config=[auth=MTLS_PERMISSIVE,...]] [--node-pool=NODE_POOL] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [--location-policy=LOCATION_POLICY --max-nodes=MAX_NODES --min-nodes=MIN_NODES @@ -319,11 +320,6 @@ REQUIRED FLAGS Thus, flag --enable-gke-oidc is also deprecated. Please use --enable-identity-service to enable the Identity Service component - --enable-google-cloud-access - When you enable Google Cloud Access, any public IP addresses owned by - Google Cloud can reach the public control plane endpoint of your - cluster. - --enable-identity-service Enable Identity Service component on the cluster. @@ -380,26 +376,6 @@ REQUIRED FLAGS and https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. - --enable-master-authorized-networks - Allow only specified set of CIDR blocks (specified by the - --master-authorized-networks flag) to connect to Kubernetes master - through HTTPS. Besides these blocks, the following have access as - well: - - 1) The private network the cluster connects to if - `--enable-private-nodes` is specified. - 2) Google Compute Engine Public IPs if `--enable-private-nodes` is not - specified. - - Use --no-enable-master-authorized-networks to disable. When disabled, - public internet (0.0.0.0/0) is allowed to connect to Kubernetes - master through HTTPS. - - --enable-master-global-access - Use with private clusters to allow access to the master's private - endpoint from any Google Cloud region or on-premises environment - regardless of the private cluster's region. - --enable-multi-networking Enables multi-networking on the cluster. Multi-networking is disabled by default. @@ -417,9 +393,20 @@ REQUIRED FLAGS PodSecurityPolicy API objects. For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/pod-security-policies. - --enable-private-endpoint - Enables cluster's control plane to be accessible using private IP - address only. + --enable-private-nodes + Standard cluster: Enable private nodes as a default behavior for all + newly created node pools, if --enable-private-nodes is not provided + at node pool creation time. + + Modifications to this flag do not affect `--enable-private-nodes` state of the + existing node pools. + + Autopilot cluster: Force new and existing workloads, without explicit + cloud.google.com/private-node=true node selector, to run on nodes + with no public IP address. + + Modifications to this flag trigger a re-schedule operation on all existng + workloads to run on different node VMs. --[no-]enable-ray-cluster-logging Enable automatic log processing sidecar for Ray clusters. Use @@ -1136,6 +1123,57 @@ REQUIRED FLAGS --enable-dataplane-v2-metrics Exposes advanced datapath flow metrics on node port. + --enable-authorized-networks-on-private-endpoint + Enable enforcement of --master-authorized-networks CIDR ranges for + traffic reaching cluster's control plane via private IP. + + --enable-dns-access + Enable access to the cluster's control plane over DNS-based endpoint. + + DNS-based control plane access is recommended. + + --enable-google-cloud-access + When you enable Google Cloud Access, any public IP addresses owned by + Google Cloud can reach the public control plane endpoint of your + cluster. + + --enable-ip-access + Enable access to the cluster's control plane over private IP and + public IP if --enable-private-endpoint is not enabled. + + --enable-master-global-access + Use with private clusters to allow access to the master's private + endpoint from any Google Cloud region or on-premises environment + regardless of the private cluster's region. + + --enable-private-endpoint + Enables cluster's control plane to be accessible using private IP + address only. + + Master Authorized Networks + + --enable-master-authorized-networks + Allow only specified set of CIDR blocks (specified by the + --master-authorized-networks flag) to connect to Kubernetes master + through HTTPS. Besides these blocks, the following have access as + well: + + 1) The private network the cluster connects to if + `--enable-private-nodes` is specified. + 2) Google Compute Engine Public IPs if `--enable-private-nodes` is not + specified. + + Use --no-enable-master-authorized-networks to disable. When + disabled, public internet (0.0.0.0/0) is allowed to connect to + Kubernetes master through HTTPS. + + --master-authorized-networks=NETWORK,[NETWORK,...] + The list of CIDR blocks (up to 100 for private cluster, 50 for + public cluster) that are allowed to connect to Kubernetes master + through HTTPS. Specified in CIDR notation (e.g. 1.2.3.4/30). Cannot + be specified unless --enable-master-authorized-networks is also + specified. + Node autoprovisioning --enable-autoprovisioning @@ -1499,12 +1537,6 @@ OPTIONAL FLAGS information and migration, see https://cloud.google.com/istio/docs/istio-on-gke/migrate-to-anthos-service-mesh. - --master-authorized-networks=NETWORK,[NETWORK,...] - The list of CIDR blocks (up to 100 for private cluster, 50 for public - cluster) that are allowed to connect to Kubernetes master through - HTTPS. Specified in CIDR notation (e.g. 1.2.3.4/30). Cannot be - specified unless --enable-master-authorized-networks is also specified. - --node-pool=NODE_POOL Node pool to be updated. diff --git a/gcloud/beta/container/fleet/scopes/add-app-operator-binding b/gcloud/beta/container/fleet/scopes/add-app-operator-binding new file mode 100644 index 000000000..ecbe45ab7 --- /dev/null +++ b/gcloud/beta/container/fleet/scopes/add-app-operator-binding @@ -0,0 +1,127 @@ +NAME + gcloud beta container fleet scopes add-app-operator-binding - add + project-level and fleet scope-level IAM bindings and create a fleet + scope RBAC role binding for an app operator principal + +SYNOPSIS + gcloud beta container fleet scopes add-app-operator-binding SCOPE + --role=ROLE (--group=GROUP | --user=USER) [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) One binding consists of an app operator principal (user/group) and a + role (view/edit/admin). + + This command sets up the different permissions required for an app + operator, including usage of fleet scopes, connect gateway, logging, and + metrics. The authoritative list for adding the permissions is the existing + RBAC role bindings under the specified scope. + + This command can fail for the following reasons: + ▪ The scope specified does not exist. + ▪ The user does not have access to the specified scope. + ▪ The principal specified already has another binding for the scope. + +EXAMPLES + The following command: + + $ gcloud beta container fleet scopes add-app-operator-binding \ + SCOPE --role=view --group=people@google.com --project=PROJECT_ID + + ▪ adds IAM policy binding: roles/gkehub.scopeViewer on SCOPE + ▪ adds IAM policy binding: roles/gkehub.scopeViewerProjectLevel on + PROJECT_ID + ▪ adds IAM policy binding: roles/logging.viewAccessor on PROJECT_ID + with condition where bucket corresponds to SCOPE + ▪ creates fleet scope RBAC role binding: role view with a random ID for + group people@google.com. + + --- + + The following command: + + $ gcloud beta container fleet scopes add-app-operator-binding \ + SCOPE --role=edit --user=person@google.com --project=PROJECT_ID + + ▪ adds IAM policy binding: roles/gkehub.scopeEditor on SCOPE + ▪ adds IAM policy binding: roles/gkehub.scopeEditorProjectLevel on + PROJECT_ID + ▪ adds IAM policy binding: roles/logging.viewAccessor on PROJECT_ID + with condition where bucket corresponds to SCOPE + ▪ creates fleet scope RBAC role binding: role edit with a random ID for + user person@google.com. + + --- + + The following command: + + $ gcloud beta container fleet scopes add-app-operator-binding \ + SCOPE --role=admin --user=person@google.com --project=PROJECT_ID + + ▪ adds IAM policy binding: roles/gkehub.scopeAdmin on SCOPE + ▪ adds IAM policy binding: roles/gkehub.scopeEditorProjectLevel on + PROJECT_ID + ▪ adds IAM policy binding: roles/logging.viewAccessor on PROJECT_ID + with condition where bucket corresponds to SCOPE + ▪ creates fleet scope RBAC role binding: role admin with a random ID + for user person@google.com. + +POSITIONAL ARGUMENTS + Scope resource - The group of arguments defining the Fleet Scope. 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 SCOPE 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 SCOPE on the command line with a fully specified + name; + ◆ global is the only supported location. + + 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. + +REQUIRED FLAGS + --role=ROLE + Role to assign. ROLE must be one of: admin, edit, view. + + Exactly one of these must be specified: + + --group=GROUP + Group for the role binding. + + --user=USER + User for the role binding. + +OPTIONAL FLAGS + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet scopes add-app-operator-binding + diff --git a/gcloud/beta/container/fleet/scopes/help b/gcloud/beta/container/fleet/scopes/help index f6260f5e3..9446aebd7 100644 --- a/gcloud/beta/container/fleet/scopes/help +++ b/gcloud/beta/container/fleet/scopes/help @@ -25,6 +25,10 @@ GROUPS COMMANDS COMMAND is one of the following: + add-app-operator-binding + (BETA) Add project-level and fleet scope-level IAM bindings and create + a fleet scope RBAC role binding for an app operator principal. + add-iam-policy-binding (BETA) Add IAM policy binding to a Fleet Scope. @@ -44,9 +48,18 @@ COMMANDS (BETA) List fleet scopes in a project permitted to be viewed by the caller. + list-app-operator-bindings + (BETA) List app operator principals corresponding to a fleet scope and + their roles based on project-level IAM bindings, fleet scope-level IAM + bindings, and fleet scope RBAC role bindings. + list-memberships (BETA) List memberships bound to a fleet scope. + remove-app-operator-binding + (BETA) Remove project-level and fleet scope-level IAM bindings and + delete a fleet scope RBAC role binding for an app operator principal. + remove-iam-policy-binding (BETA) Remove IAM policy binding of a Fleet Scope. diff --git a/gcloud/beta/container/fleet/scopes/list-app-operator-bindings b/gcloud/beta/container/fleet/scopes/list-app-operator-bindings new file mode 100644 index 000000000..176d9a8bd --- /dev/null +++ b/gcloud/beta/container/fleet/scopes/list-app-operator-bindings @@ -0,0 +1,106 @@ +NAME + gcloud beta container fleet scopes list-app-operator-bindings - list app + operator principals corresponding to a fleet scope and their roles + based on project-level IAM bindings, fleet scope-level IAM bindings, + and fleet scope RBAC role bindings + +SYNOPSIS + gcloud beta container fleet scopes list-app-operator-bindings SCOPE + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command lists bindings corresponding to a fleet scope. The + bindings, which consist of an app operator principal and a role, grant + permissions required for an app operator, including usage of fleet scopes, + connect gateway, logging, and metrics. The overarching principal role + (view/edit/admin, or custom) is determined by (1) the fleet scope RBAC role + (view, edit, or admin), (2) the fleet scope-level IAM role + (roles/gkehub.scopeViewer, roles/gkehub.scopeEditor, or + roles/gkehub.scopeAdmin), (3) the project-level IAM role + (roles/gkehub.scopeViewerProjectLevel, or + roles/gkehub.scopeEditorProjectLevel), and (4) the conditional log view + access role for the scope bucket. + + This command can fail for the following reasons: + ▪ The scope specified does not exist. + ▪ The user does not have access to the specified scope. + +EXAMPLES + The following command lists app operator principals corresponding to SCOPE + under PROJECT_ID, their roles, and role details (fleet scope RBAC role, + fleet scope-level IAM role, project-level IAM role, and log view access): + + $ gcloud beta container fleet scopes list-app-operator-bindings \ + --scope=SCOPE --project=PROJECT_ID + +POSITIONAL ARGUMENTS + Scope resource - The group of arguments defining the Fleet Scope. 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 SCOPE 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 SCOPE on the command line with a fully specified + name; + ◆ global is the only supported location. + + 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. + +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 + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet scopes list-app-operator-bindings + diff --git a/gcloud/beta/container/fleet/scopes/remove-app-operator-binding b/gcloud/beta/container/fleet/scopes/remove-app-operator-binding new file mode 100644 index 000000000..67f105a44 --- /dev/null +++ b/gcloud/beta/container/fleet/scopes/remove-app-operator-binding @@ -0,0 +1,122 @@ +NAME + gcloud beta container fleet scopes remove-app-operator-binding - remove + project-level and fleet scope-level IAM bindings and delete a fleet + scope RBAC role binding for an app operator principal + +SYNOPSIS + gcloud beta container fleet scopes remove-app-operator-binding SCOPE + (--group=GROUP | --user=USER) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) One binding consists of an app operator principal (user/group) and a + role (view/edit/admin). + + This command unsets the different permissions required for an app operator, + including usage of fleet scopes, connect gateway, logging, and metrics. The + authoritative list for removing the permissions is the existing RBAC role + bindings under the specified scope. + + This command can fail for the following reasons: + ▪ The scope specified does not exist. + ▪ The user does not have access to the specified scope. + ▪ The principal specified does not any binding for the scope. + ▪ The principal specified has bindings with different roles for the + scope. + +EXAMPLES + The following command: + + $ gcloud beta container fleet scopes remove-app-operator-binding \ + SCOPE --group=people@google.com --project=PROJECT_ID + + assuming the group already has the view role: + ▪ removes IAM policy binding: roles/gkehub.scopeViewer from SCOPE + ▪ removes IAM policy binding: roles/gkehub.scopeViewerProjectLevel from + PROJECT_ID if the group does not have the view role for any other scope + under the project + ▪ removes IAM policy binding: roles/logging.viewAccessor from + PROJECT_ID condition where bucket corresponds to SCOPE + ▪ deletes existing fleet scope RBAC role binding: role view for group + people@google.com. + + --- + + The following command: + + $ gcloud beta container fleet scopes remove-app-operator-binding \ + SCOPE --user=person@google.com --project=PROJECT_ID + + assuming the user already has the edit role: + ▪ removes IAM policy binding: roles/gkehub.scopeEditor from SCOPE + ▪ removes IAM policy binding: roles/gkehub.scopeEditorProjectLevel from + PROJECT_ID if the user does not have the edit/admin role for any other + scope under the project + ▪ removes IAM policy binding: roles/logging.viewAccessor from + PROJECT_ID condition where bucket corresponds to SCOPE + ▪ deletes existing fleet scope RBAC role binding: role edit for user + person@google.com. + + --- + + The following command: + + $ gcloud beta container fleet scopes remove-app-operator-binding \ + SCOPE --role=admin --user=person@google.com --project=PROJECT_ID + + assuming the user already has the admin role: + ▪ removes IAM policy binding: roles/gkehub.scopeAdmin from SCOPE + ▪ removes IAM policy binding: roles/gkehub.scopeEditorProjectLevel from + PROJECT_ID if the user does not have the edit/admin role for any other + scope under the project + ▪ removes IAM policy binding: roles/logging.viewAccessor from + PROJECT_ID condition where bucket corresponds to SCOPE + ▪ deletes existing fleet scope RBAC role binding: role admin for user + person@google.com. + +POSITIONAL ARGUMENTS + Scope resource - The group of arguments defining the Fleet Scope. 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 SCOPE 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 SCOPE on the command line with a fully specified + name; + ◆ global is the only supported location. + + 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. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --group=GROUP + Group for the role binding. + + --user=USER + User for the role binding. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet scopes remove-app-operator-binding + diff --git a/gcloud/beta/container/hub/scopes/add-app-operator-binding b/gcloud/beta/container/hub/scopes/add-app-operator-binding new file mode 100644 index 000000000..6f1f71066 --- /dev/null +++ b/gcloud/beta/container/hub/scopes/add-app-operator-binding @@ -0,0 +1,127 @@ +NAME + gcloud beta container hub scopes add-app-operator-binding - add + project-level and fleet scope-level IAM bindings and create a fleet + scope RBAC role binding for an app operator principal + +SYNOPSIS + gcloud beta container hub scopes add-app-operator-binding SCOPE --role=ROLE + (--group=GROUP | --user=USER) [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) One binding consists of an app operator principal (user/group) and a + role (view/edit/admin). + + This command sets up the different permissions required for an app + operator, including usage of fleet scopes, connect gateway, logging, and + metrics. The authoritative list for adding the permissions is the existing + RBAC role bindings under the specified scope. + + This command can fail for the following reasons: + ▪ The scope specified does not exist. + ▪ The user does not have access to the specified scope. + ▪ The principal specified already has another binding for the scope. + +EXAMPLES + The following command: + + $ gcloud beta container hub scopes add-app-operator-binding SCOPE \ + --role=view --group=people@google.com --project=PROJECT_ID + + ▪ adds IAM policy binding: roles/gkehub.scopeViewer on SCOPE + ▪ adds IAM policy binding: roles/gkehub.scopeViewerProjectLevel on + PROJECT_ID + ▪ adds IAM policy binding: roles/logging.viewAccessor on PROJECT_ID + with condition where bucket corresponds to SCOPE + ▪ creates fleet scope RBAC role binding: role view with a random ID for + group people@google.com. + + --- + + The following command: + + $ gcloud beta container hub scopes add-app-operator-binding SCOPE \ + --role=edit --user=person@google.com --project=PROJECT_ID + + ▪ adds IAM policy binding: roles/gkehub.scopeEditor on SCOPE + ▪ adds IAM policy binding: roles/gkehub.scopeEditorProjectLevel on + PROJECT_ID + ▪ adds IAM policy binding: roles/logging.viewAccessor on PROJECT_ID + with condition where bucket corresponds to SCOPE + ▪ creates fleet scope RBAC role binding: role edit with a random ID for + user person@google.com. + + --- + + The following command: + + $ gcloud beta container hub scopes add-app-operator-binding SCOPE \ + --role=admin --user=person@google.com --project=PROJECT_ID + + ▪ adds IAM policy binding: roles/gkehub.scopeAdmin on SCOPE + ▪ adds IAM policy binding: roles/gkehub.scopeEditorProjectLevel on + PROJECT_ID + ▪ adds IAM policy binding: roles/logging.viewAccessor on PROJECT_ID + with condition where bucket corresponds to SCOPE + ▪ creates fleet scope RBAC role binding: role admin with a random ID + for user person@google.com. + +POSITIONAL ARGUMENTS + Scope resource - The group of arguments defining the Fleet Scope. 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 SCOPE 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 SCOPE on the command line with a fully specified + name; + ◆ global is the only supported location. + + 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. + +REQUIRED FLAGS + --role=ROLE + Role to assign. ROLE must be one of: admin, edit, view. + + Exactly one of these must be specified: + + --group=GROUP + Group for the role binding. + + --user=USER + User for the role binding. + +OPTIONAL FLAGS + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub scopes add-app-operator-binding + diff --git a/gcloud/beta/container/hub/scopes/help b/gcloud/beta/container/hub/scopes/help index 4c6c288f8..5b0fbb665 100644 --- a/gcloud/beta/container/hub/scopes/help +++ b/gcloud/beta/container/hub/scopes/help @@ -25,6 +25,10 @@ GROUPS COMMANDS COMMAND is one of the following: + add-app-operator-binding + (BETA) Add project-level and fleet scope-level IAM bindings and create + a fleet scope RBAC role binding for an app operator principal. + add-iam-policy-binding (BETA) Add IAM policy binding to a Fleet Scope. @@ -44,9 +48,18 @@ COMMANDS (BETA) List fleet scopes in a project permitted to be viewed by the caller. + list-app-operator-bindings + (BETA) List app operator principals corresponding to a fleet scope and + their roles based on project-level IAM bindings, fleet scope-level IAM + bindings, and fleet scope RBAC role bindings. + list-memberships (BETA) List memberships bound to a fleet scope. + remove-app-operator-binding + (BETA) Remove project-level and fleet scope-level IAM bindings and + delete a fleet scope RBAC role binding for an app operator principal. + remove-iam-policy-binding (BETA) Remove IAM policy binding of a Fleet Scope. diff --git a/gcloud/beta/container/hub/scopes/list-app-operator-bindings b/gcloud/beta/container/hub/scopes/list-app-operator-bindings new file mode 100644 index 000000000..545c3543c --- /dev/null +++ b/gcloud/beta/container/hub/scopes/list-app-operator-bindings @@ -0,0 +1,106 @@ +NAME + gcloud beta container hub scopes list-app-operator-bindings - list app + operator principals corresponding to a fleet scope and their roles + based on project-level IAM bindings, fleet scope-level IAM bindings, + and fleet scope RBAC role bindings + +SYNOPSIS + gcloud beta container hub scopes list-app-operator-bindings SCOPE + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command lists bindings corresponding to a fleet scope. The + bindings, which consist of an app operator principal and a role, grant + permissions required for an app operator, including usage of fleet scopes, + connect gateway, logging, and metrics. The overarching principal role + (view/edit/admin, or custom) is determined by (1) the fleet scope RBAC role + (view, edit, or admin), (2) the fleet scope-level IAM role + (roles/gkehub.scopeViewer, roles/gkehub.scopeEditor, or + roles/gkehub.scopeAdmin), (3) the project-level IAM role + (roles/gkehub.scopeViewerProjectLevel, or + roles/gkehub.scopeEditorProjectLevel), and (4) the conditional log view + access role for the scope bucket. + + This command can fail for the following reasons: + ▪ The scope specified does not exist. + ▪ The user does not have access to the specified scope. + +EXAMPLES + The following command lists app operator principals corresponding to SCOPE + under PROJECT_ID, their roles, and role details (fleet scope RBAC role, + fleet scope-level IAM role, project-level IAM role, and log view access): + + $ gcloud beta container hub scopes list-app-operator-bindings \ + --scope=SCOPE --project=PROJECT_ID + +POSITIONAL ARGUMENTS + Scope resource - The group of arguments defining the Fleet Scope. 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 SCOPE 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 SCOPE on the command line with a fully specified + name; + ◆ global is the only supported location. + + 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. + +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 + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub scopes list-app-operator-bindings + diff --git a/gcloud/beta/container/hub/scopes/remove-app-operator-binding b/gcloud/beta/container/hub/scopes/remove-app-operator-binding new file mode 100644 index 000000000..18c7db0ac --- /dev/null +++ b/gcloud/beta/container/hub/scopes/remove-app-operator-binding @@ -0,0 +1,122 @@ +NAME + gcloud beta container hub scopes remove-app-operator-binding - remove + project-level and fleet scope-level IAM bindings and delete a fleet + scope RBAC role binding for an app operator principal + +SYNOPSIS + gcloud beta container hub scopes remove-app-operator-binding SCOPE + (--group=GROUP | --user=USER) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) One binding consists of an app operator principal (user/group) and a + role (view/edit/admin). + + This command unsets the different permissions required for an app operator, + including usage of fleet scopes, connect gateway, logging, and metrics. The + authoritative list for removing the permissions is the existing RBAC role + bindings under the specified scope. + + This command can fail for the following reasons: + ▪ The scope specified does not exist. + ▪ The user does not have access to the specified scope. + ▪ The principal specified does not any binding for the scope. + ▪ The principal specified has bindings with different roles for the + scope. + +EXAMPLES + The following command: + + $ gcloud beta container hub scopes remove-app-operator-binding \ + SCOPE --group=people@google.com --project=PROJECT_ID + + assuming the group already has the view role: + ▪ removes IAM policy binding: roles/gkehub.scopeViewer from SCOPE + ▪ removes IAM policy binding: roles/gkehub.scopeViewerProjectLevel from + PROJECT_ID if the group does not have the view role for any other scope + under the project + ▪ removes IAM policy binding: roles/logging.viewAccessor from + PROJECT_ID condition where bucket corresponds to SCOPE + ▪ deletes existing fleet scope RBAC role binding: role view for group + people@google.com. + + --- + + The following command: + + $ gcloud beta container hub scopes remove-app-operator-binding \ + SCOPE --user=person@google.com --project=PROJECT_ID + + assuming the user already has the edit role: + ▪ removes IAM policy binding: roles/gkehub.scopeEditor from SCOPE + ▪ removes IAM policy binding: roles/gkehub.scopeEditorProjectLevel from + PROJECT_ID if the user does not have the edit/admin role for any other + scope under the project + ▪ removes IAM policy binding: roles/logging.viewAccessor from + PROJECT_ID condition where bucket corresponds to SCOPE + ▪ deletes existing fleet scope RBAC role binding: role edit for user + person@google.com. + + --- + + The following command: + + $ gcloud beta container hub scopes remove-app-operator-binding \ + SCOPE --role=admin --user=person@google.com --project=PROJECT_ID + + assuming the user already has the admin role: + ▪ removes IAM policy binding: roles/gkehub.scopeAdmin from SCOPE + ▪ removes IAM policy binding: roles/gkehub.scopeEditorProjectLevel from + PROJECT_ID if the user does not have the edit/admin role for any other + scope under the project + ▪ removes IAM policy binding: roles/logging.viewAccessor from + PROJECT_ID condition where bucket corresponds to SCOPE + ▪ deletes existing fleet scope RBAC role binding: role admin for user + person@google.com. + +POSITIONAL ARGUMENTS + Scope resource - The group of arguments defining the Fleet Scope. 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 SCOPE 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 SCOPE on the command line with a fully specified + name; + ◆ global is the only supported location. + + 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. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --group=GROUP + Group for the role binding. + + --user=USER + User for the role binding. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub scopes remove-app-operator-binding + diff --git a/gcloud/beta/container/node-pools/get-upgrade-info b/gcloud/beta/container/node-pools/get-upgrade-info new file mode 100644 index 000000000..a740a7b64 --- /dev/null +++ b/gcloud/beta/container/node-pools/get-upgrade-info @@ -0,0 +1,61 @@ +NAME + gcloud beta container node-pools get-upgrade-info - get information about + upgrades for existing clusters including auto upgrade status, upgrade + history, upgrade targets, and end of support timelines + +SYNOPSIS + gcloud beta container node-pools get-upgrade-info NAME [--cluster=CLUSTER] + [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get information about upgrades for existing clusters including auto + upgrade status, upgrade history, upgrade targets, and end of support + timelines. + +EXAMPLES + To get upgrade information for a node pool of an existing cluster, run: + + $ gcloud beta container node-pools get-upgrade-info node-pool-1 \ + --cluster=sample-cluster + +POSITIONAL ARGUMENTS + NAME + The name of the node pool. + +FLAGS + --cluster=CLUSTER + The name of the cluster. Overrides the default container/cluster + property value for this command invocation. + + At most one of these can be specified: + + --location=LOCATION + Compute zone or region (e.g. us-central1-a or us-central1) for the + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. + + --region=REGION + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. + + --zone=ZONE, -z ZONE + Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the + default compute/zone property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container node-pools get-upgrade-info + diff --git a/gcloud/beta/container/node-pools/help b/gcloud/beta/container/node-pools/help index 4809ca0f6..66530b9f0 100644 --- a/gcloud/beta/container/node-pools/help +++ b/gcloud/beta/container/node-pools/help @@ -49,6 +49,11 @@ COMMANDS describe (BETA) Describe an existing node pool for a cluster. + get-upgrade-info + (BETA) Get information about upgrades for existing clusters including + auto upgrade status, upgrade history, upgrade targets, and end of + support timelines. + list (BETA) List existing node pools for a cluster. diff --git a/gcloud/beta/dataflow/jobs/cancel b/gcloud/beta/dataflow/jobs/cancel index bc9236cce..0e58b93de 100644 --- a/gcloud/beta/dataflow/jobs/cancel +++ b/gcloud/beta/dataflow/jobs/cancel @@ -15,9 +15,8 @@ POSITIONAL ARGUMENTS FLAGS --force - Forcibly cancels a Dataflow job, leaking any VMs the Dataflow job - created. Regular cancel must have been attempted at least 30 minutes - ago for a job to be force cancelled. + Forcibly cancels a Dataflow job. Regular cancel must have been + attempted at least 30 minutes prior for a job to be force cancelled. --region=REGION_ID Region ID of the jobs' regional endpoint. Defaults to 'us-central1'. diff --git a/gcloud/beta/eventarc/help b/gcloud/beta/eventarc/help new file mode 100644 index 000000000..0a22918c2 --- /dev/null +++ b/gcloud/beta/eventarc/help @@ -0,0 +1,20 @@ +NAME + gcloud beta eventarc - manage Eventarc resources + +SYNOPSIS + gcloud beta eventarc GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Eventarc resources. + +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. This + variant is also available: + + $ gcloud eventarc + diff --git a/gcloud/beta/identity/groups/create b/gcloud/beta/identity/groups/create index d75bd1c3a..10abf3c3d 100644 --- a/gcloud/beta/identity/groups/create +++ b/gcloud/beta/identity/groups/create @@ -5,7 +5,6 @@ SYNOPSIS gcloud beta identity groups create EMAIL --organization=ORGANIZATION [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--dynamic-user-query=DYNAMIC_USER_QUERY] - [--posix-group=[gid=GID],[name=NAME]] [--with-initial-owner=WITH_INITIAL_OWNER] [--group-type=GROUP_TYPE; default="discussion" | --labels=LABELS] [GCLOUD_WIDE_FLAG ...] @@ -34,11 +33,6 @@ EXAMPLES --display-name="Security Group" \ --description="Description of Security Group" - To create a new POSIX group: - - $ gcloud beta identity groups create eng-discuss@example.com \ - --organization="example.com" --posix-group=name=eng,gid=1005 - POSITIONAL ARGUMENTS EMAIL The email address of the group to be created. @@ -65,15 +59,6 @@ OPTIONAL FLAGS Example of a query: --dynamic-user-query="user.organizations.exists(org,org.title=='SWE')" - --posix-group=[gid=GID],[name=NAME] - Group ID (gid) and name of the POSIX group that you want to associate - with the specified Cloud Identity group. You can specify multiple POSIX - groups with multiple instances of this flag. - - For example, use '--posix-group=gid=1005,name=eng' to add a single - group, or '--posix-group=gid=1005,name=eng - --posix-group=gid=1006,name=docs' to add multiple groups. - --with-initial-owner=WITH_INITIAL_OWNER If specified the user making the request will be added as the initial owner of the group being created. WITH_INITIAL_OWNER must be one of: diff --git a/gcloud/beta/identity/groups/update b/gcloud/beta/identity/groups/update index 52f452506..31fa92c8d 100644 --- a/gcloud/beta/identity/groups/update +++ b/gcloud/beta/identity/groups/update @@ -4,8 +4,7 @@ NAME SYNOPSIS gcloud beta identity groups update EMAIL [--dynamic-user-query=DYNAMIC_USER_QUERY] [--labels=LABELS] - [--add-posix-group=[gid=GID],[name=NAME] | --clear-posix-groups - | --remove-posix-groups=[POSIX_GROUP,...]] + [--clear-posix-groups | --remove-posix-groups=[POSIX_GROUP,...]] [--clear-description | --description=DESCRIPTION] [--clear-display-name | --display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] @@ -20,11 +19,6 @@ EXAMPLES --display-name="New Engineer Discuss" \ --description="Group for engineering discussions" - To create a POSIX group from an existing Google Group: - - $ gcloud beta identity groups update eng-discuss@foo.com \ - --add-posix-group=name=eng,gid=1005 - To remove POSIX information from a Google Group: $ gcloud beta identity groups update eng-discuss@foo.com \ @@ -65,15 +59,6 @@ FLAGS At most one of these can be specified: - --add-posix-group=[gid=GID],[name=NAME] - Group id (gid) and a name for a POSIX group that you want to add to - the specified Cloud Identity group. You can specify multiple POSIX - groups to add with multiple instances of this flag. - - For example, use '--add-posix-group=gid=1005,name=eng' to add a - single group, or '--add-posix-group=gid=1005,name=eng - --add-posix-group=gid=1006,name=docs' to add multiple groups. - --clear-posix-groups Clear all POSIX groups from the specified Cloud Identity group. diff --git a/gcloud/beta/ml/speech/recognize b/gcloud/beta/ml/speech/recognize index 4495141a0..edcd59d5e 100644 --- a/gcloud/beta/ml/speech/recognize +++ b/gcloud/beta/ml/speech/recognize @@ -65,7 +65,7 @@ OPTIONAL FLAGS --encoding=ENCODING; default="encoding-unspecified" The type of encoding of the file. Required if the file format is not - WAV or FLAC. ENCODING must be one of: amr, amr-wb, + WAV or FLAC. ENCODING must be one of: alaw, amr, amr-wb, encoding-unspecified, flac, linear16, mp3, mulaw, ogg-opus, speex-with-header-byte, webm-opus. diff --git a/gcloud/beta/ml/speech/recognize-long-running b/gcloud/beta/ml/speech/recognize-long-running index be7f033cf..fb946787c 100644 --- a/gcloud/beta/ml/speech/recognize-long-running +++ b/gcloud/beta/ml/speech/recognize-long-running @@ -74,7 +74,7 @@ OPTIONAL FLAGS --encoding=ENCODING; default="encoding-unspecified" The type of encoding of the file. Required if the file format is not - WAV or FLAC. ENCODING must be one of: amr, amr-wb, + WAV or FLAC. ENCODING must be one of: alaw, amr, amr-wb, encoding-unspecified, flac, linear16, mp3, mulaw, ogg-opus, speex-with-header-byte, webm-opus. diff --git a/gcloud/beta/notebook-executor/help b/gcloud/beta/notebook-executor/help index 754e8708d..78d0a6340 100644 --- a/gcloud/beta/notebook-executor/help +++ b/gcloud/beta/notebook-executor/help @@ -18,6 +18,9 @@ GROUPS executions (BETA) Notebook Executor Executions command group. + schedules + (BETA) Notebook Executor Schedules command group. + NOTES This command is currently in beta and might change without notice. diff --git a/gcloud/beta/notebook-executor/schedules/create b/gcloud/beta/notebook-executor/schedules/create new file mode 100644 index 000000000..e1a0021b4 --- /dev/null +++ b/gcloud/beta/notebook-executor/schedules/create @@ -0,0 +1,243 @@ +NAME + gcloud beta notebook-executor schedules create - create a notebook executor + schedule + +SYNOPSIS + gcloud beta notebook-executor schedules create --region=REGION + (--cron-schedule=CRON_SCHEDULE --display-name=DISPLAY_NAME + (--execution-display-name=EXECUTION_DISPLAY_NAME + --gcs-output-uri=GCS_OUTPUT_URI + --notebook-runtime-template=NOTEBOOK_RUNTIME_TEMPLATE + ([--dataform-repository-name=DATAFORM_REPOSITORY_NAME + : --commit-sha=COMMIT_SHA] | [--gcs-notebook-uri=GCS_NOTEBOOK_URI + : --generation=GENERATION]) (--service-account=SERVICE_ACCOUNT + | --user-email=USER_EMAIL) + : --execution-timeout=EXECUTION_TIMEOUT; default="24h") + : --enable-queueing --end-time=END_TIME + --max-concurrent-runs=MAX_CONCURRENT_RUNS; + default=1 --max-runs=MAX_RUNS --start-time=START_TIME) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a schedule to run a Colab Enterprise notebook execution job. + +EXAMPLES + To create a schedule in region us-central1 with the following schedule + properties: + ▪ display name: my-schedule, + ▪ cron schedule: TZ=America/Los_Angeles * * * * *, + ▪ maximum concurrent runs allowed: 1, + ▪ start time: 2025-01-01T00:00:00-06:00, + + for a notebook execution job: + ▪ with display name my-execution, + ▪ running notebook file from Cloud Storage URI + gs://my-bucket/my-notebook.ipynb, + ▪ compute configured from runtime template my-runtime-template-id, + ▪ running with service account + my-service-account@my-project.iam.gserviceaccount.com, + ▪ with results uploaded to Cloud Storage bucket gs://my-bucket/results + + Run the following command: $ gcloud beta notebook-executor schedules create \ + --region=us-central1 --display-name=my-schedule \ + --cron-schedule='TZ=America/Los_Angeles * * * * *' \ + --max-concurrent-runs=1 --start-time=2025-01-01T00:00:00-06:00 \ + --execution-display-name=my-execution \ + --notebook-runtime-template=my-runtime-template-id \ + --gcs-notebook-uri=gs://my-bucket/my-notebook.ipynb \ + --service-account=my-service-account@my-project.iam.gserviceacco\ + unt.com --gcs-output-uri=gs://my-bucket/results + +REQUIRED FLAGS + Region resource - Cloud region to create. 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 --region on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line. + + Configuration of the schedule. + + This must be specified. + + --cron-schedule=CRON_SCHEDULE + Cron schedule (https://en.wikipedia.org/wiki/Cron) to launch + scheduled runs. To explicitly set a timezone to the cron tab, apply a + prefix in the cron tab: "CRON_TZ=${IANA_TIME_ZONE}" or + "TZ=${IANA_TIME_ZONE}". The ${IANA_TIME_ZONE} may only be a valid + string from IANA time zone database. For example, + "CRON_TZ=America/New_York 1 * * * ", or "TZ=America/New_York 1 * * * + ". + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --display-name=DISPLAY_NAME + The display name of the schedule. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --enable-queueing + Enables new scheduled runs to be queued when max_concurrent_runs + limit is reached. If set to true, new runs will be queued instead of + skipped. + + --end-time=END_TIME + Timestamp after which no new runs can be scheduled. If specified, the + schedule will be completed when either end_time is reached or when + scheduled_run_count >= max_run_count. If neither end time nor + max_run_count is specified, new runs will keep getting scheduled + until this Schedule is paused or deleted. Must be in the RFC 3339 + (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" + + --max-concurrent-runs=MAX_CONCURRENT_RUNS; default=1 + Maximum number of runs that can be started concurrently for this + Schedule. This is the limit for starting the scheduled requests and + not the execution of the notebook execution jobs created by the + requests. + + --max-runs=MAX_RUNS + The max runs for the schedule. + + --start-time=START_TIME + The timestamp after which the first run can be scheduled. Defaults to + the schedule creation time. Must be in the RFC 3339 + (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" + + Configuration of the execution job. + + This must be specified. + + --execution-display-name=EXECUTION_DISPLAY_NAME + The display name of the execution. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --gcs-output-uri=GCS_OUTPUT_URI + The Cloud Storage location to upload notebook execution results to. + Format: gs://bucket-name. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + Notebook runtime template resource - The runtime template specifying + the compute configuration for the notebook execution. The runtime + template should be in the same region as the execution. 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 --notebook-runtime-template 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 region attribute: + ▫ provide the argument --notebook-runtime-template on the command + line with a fully specified name; + ▫ provide the argument --region on the command line. + + This must be specified. + + --notebook-runtime-template=NOTEBOOK_RUNTIME_TEMPLATE + ID of the notebook runtime template or fully qualified identifier + for the notebook runtime template. + + To set the name attribute: + ◇ provide the argument --notebook-runtime-template on the + command line. + + --execution-timeout=EXECUTION_TIMEOUT; default="24h" + The max running time of the execution job, as a duration. See '$ + gcloud topic datetimes' for details on formatting the input + duration. + + Source of the notebook to execute. + + Exactly one of these must be specified: + + The Dataform repository containing the notebook. Any notebook + created from the Colab UI is automatically stored in a Dataform + repository. The repository name can be found via the Dataform API by + listing repositories in the same project and region as the notebook. + + Dataform repository resource - Unique name of the Dataform + repository to source input notebook 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 --dataform-repository-name 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 region attribute: + ▹ provide the argument --dataform-repository-name on the + command line with a fully specified name; + ▹ provide the argument --region on the command line. + + This must be specified. + + --dataform-repository-name=DATAFORM_REPOSITORY_NAME + ID of the dataform repository or fully qualified identifier + for the dataform repository. + + To set the name attribute: + ▪ provide the argument --dataform-repository-name on the + command line. + + --commit-sha=COMMIT_SHA + The commit SHA to read from the Dataform repository. If unset, + the file will be read from HEAD. + + The Cloud Storage notebook source. + + --gcs-notebook-uri=GCS_NOTEBOOK_URI + The Cloud Storage uri pointing to the notebook. Format: + gs://bucket/notebook_file.ipynb + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --generation=GENERATION + The version of the Cloud Storage object to read. If unset, the + current version of the object will be used. + + Identity to run the execution as. + + Exactly one of these must be specified: + + --service-account=SERVICE_ACCOUNT + The service account to run the execution as. + + --user-email=USER_EMAIL + The user email to run the execution as. This requires the + provided runtime template to have end user credentials enabled. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/notebook-executor/schedules/delete b/gcloud/beta/notebook-executor/schedules/delete new file mode 100644 index 000000000..79ae59899 --- /dev/null +++ b/gcloud/beta/notebook-executor/schedules/delete @@ -0,0 +1,63 @@ +NAME + gcloud beta notebook-executor schedules delete - delete a schedule + +SYNOPSIS + gcloud beta notebook-executor schedules delete (SCHEDULE : --region=REGION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a notebook executor schedule. + +EXAMPLES + To delete a schedule with id my-schedule, in region us-central1, run: + + $ gcloud beta notebook-executor schedules delete my-schedule \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Schedule resource - Unique, system-generated resource name of the schedule + to delete. 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 schedule on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + SCHEDULE + ID of the schedule or fully qualified identifier for the schedule. + + To set the name attribute: + ▸ provide the argument schedule on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the schedule. + + To set the region attribute: + ▸ provide the argument schedule on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/notebook-executor/schedules/describe b/gcloud/beta/notebook-executor/schedules/describe new file mode 100644 index 000000000..85810b09f --- /dev/null +++ b/gcloud/beta/notebook-executor/schedules/describe @@ -0,0 +1,58 @@ +NAME + gcloud beta notebook-executor schedules describe - describe a schedule + +SYNOPSIS + gcloud beta notebook-executor schedules describe + (SCHEDULE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a notebook executor schedule. + +EXAMPLES + To describe a schedule with id my-schedule in region us-central1, run: + + $ gcloud beta notebook-executor schedules describe my-schedule \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Schedule resource - Unique, system-generated resource name of the schedule + to describe. 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 schedule on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + SCHEDULE + ID of the schedule or fully qualified identifier for the schedule. + + To set the name attribute: + ▸ provide the argument schedule on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the schedule. + + To set the region attribute: + ▸ provide the argument schedule on the command line with a fully + specified name; + ▸ provide the argument --region 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 + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/notebook-executor/schedules/help b/gcloud/beta/notebook-executor/schedules/help new file mode 100644 index 000000000..bd0c0117d --- /dev/null +++ b/gcloud/beta/notebook-executor/schedules/help @@ -0,0 +1,43 @@ +NAME + gcloud beta notebook-executor schedules - notebook Executor Schedules + command group + +SYNOPSIS + gcloud beta notebook-executor schedules COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) For more information about schedules, see + https://cloud.google.com/colab/docs/schedule-notebook-run. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a notebook executor schedule. + + delete + (BETA) Delete a schedule. + + describe + (BETA) Describe a schedule. + + list + (BETA) List your notebook executor schedules. + + pause + (BETA) Pause a schedule. + + resume + (BETA) Resume a schedule. + + update + (BETA) Update a notebook executor schedule. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/resource-settings/list b/gcloud/beta/notebook-executor/schedules/list similarity index 62% rename from gcloud/resource-settings/list rename to gcloud/beta/notebook-executor/schedules/list index 1092118dd..3af8d9b0b 100644 --- a/gcloud/resource-settings/list +++ b/gcloud/beta/notebook-executor/schedules/list @@ -1,41 +1,38 @@ NAME - gcloud resource-settings list - list all available resource settings + gcloud beta notebook-executor schedules list - list your notebook executor + schedules SYNOPSIS - gcloud resource-settings list - (--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID) [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud beta notebook-executor schedules list --region=REGION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) List all available resource settings. - - Resource Settings is deprecated. As of November 7, 2023, no organizations - will be onboarded for any of the enabled settings, and the service will be - shut down on October 1, 2024. - - List all available resource settings. + (BETA) List your project's Notebook Executor schedules in a given region. EXAMPLES - To list all available resource settings with the project foo-project, run: + To list your schedules in region us-central1, run: - $ gcloud resource-settings list --project=foo-project + $ gcloud beta notebook-executor schedules list --region=us-central1 REQUIRED FLAGS - Resource that is associated with the resource settings. + Region resource - Cloud region for which to list all schedules. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. - Exactly one of these must be specified: + To set the project attribute: + ◆ provide the argument --region on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. - --folder=FOLDER_ID - Folder ID. + This must be specified. - --organization=ORGANIZATION_ID - Organization ID. + --region=REGION + ID of the region or fully qualified identifier for the region. - --project=PROJECT_ID - Project ID. Overrides the default core/project property value for - this command invocation. + To set the region attribute: + ▸ provide the argument --region on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -78,7 +75,5 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This variant is also available: - - $ gcloud alpha resource-settings list + This command is currently in beta and might change without notice. diff --git a/gcloud/beta/notebook-executor/schedules/pause b/gcloud/beta/notebook-executor/schedules/pause new file mode 100644 index 000000000..26f6237f4 --- /dev/null +++ b/gcloud/beta/notebook-executor/schedules/pause @@ -0,0 +1,58 @@ +NAME + gcloud beta notebook-executor schedules pause - pause a schedule + +SYNOPSIS + gcloud beta notebook-executor schedules pause (SCHEDULE : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Pause a notebook executor schedule. + +EXAMPLES + To pause a schedule with id my-schedule, in region us-central1, run: + + $ gcloud beta notebook-executor schedules pause my-schedule \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Schedule resource - Unique, system-generated resource name of the schedule + to pause. 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 schedule on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + SCHEDULE + ID of the schedule or fully qualified identifier for the schedule. + + To set the name attribute: + ▸ provide the argument schedule on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the schedule. + + To set the region attribute: + ▸ provide the argument schedule on the command line with a fully + specified name; + ▸ provide the argument --region 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 + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/notebook-executor/schedules/resume b/gcloud/beta/notebook-executor/schedules/resume new file mode 100644 index 000000000..5351db1e5 --- /dev/null +++ b/gcloud/beta/notebook-executor/schedules/resume @@ -0,0 +1,65 @@ +NAME + gcloud beta notebook-executor schedules resume - resume a schedule + +SYNOPSIS + gcloud beta notebook-executor schedules resume (SCHEDULE : --region=REGION) + [--enable-catch-up] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Resume a notebook executor schedule. + +EXAMPLES + To resume a paused schedule with id my-schedule, in region us-central1, + run: + + $ gcloud beta notebook-executor schedules resume my-schedule \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Schedule resource - Unique, system-generated resource name of the schedule + to resume. 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 schedule on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + SCHEDULE + ID of the schedule or fully qualified identifier for the schedule. + + To set the name attribute: + ▸ provide the argument schedule on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the schedule. + + To set the region attribute: + ▸ provide the argument schedule on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +FLAGS + --enable-catch-up + Enables backfilling missed runs when the schedule is resumed from + PAUSED state. If enabled, all missed runs will be scheduled and new + runs will be scheduled after the backfill is complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/notebook-executor/schedules/update b/gcloud/beta/notebook-executor/schedules/update new file mode 100644 index 000000000..5bbaa5992 --- /dev/null +++ b/gcloud/beta/notebook-executor/schedules/update @@ -0,0 +1,110 @@ +NAME + gcloud beta notebook-executor schedules update - update a notebook executor + schedule + +SYNOPSIS + gcloud beta notebook-executor schedules update (SCHEDULE : --region=REGION) + (--cron-schedule=CRON_SCHEDULE --display-name=DISPLAY_NAME + --enable-queueing --end-time=END_TIME + --max-concurrent-runs=MAX_CONCURRENT_RUNS + --max-runs=MAX_RUNS --start-time=START_TIME) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a notebook executor schedule. + +EXAMPLES + To update the cron schedule and max runs of a schedule with id my-schedule, + in region us-central1, run: + + $ gcloud beta notebook-executor schedules update my-schedule \ + --region=us-central1 \ + --cron-schedule='TZ=America/Los_Angeles 0 0 * * 0' --max-runs=2 + +POSITIONAL ARGUMENTS + Schedule resource - Unique, system-generated resource name of the schedule + to update. 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 schedule on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + SCHEDULE + ID of the schedule or fully qualified identifier for the schedule. + + To set the name attribute: + ▸ provide the argument schedule on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the schedule. + + To set the region attribute: + ▸ provide the argument schedule on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + Configuration of the schedule. + + At least one of these must be specified: + + --cron-schedule=CRON_SCHEDULE + Cron schedule (https://en.wikipedia.org/wiki/Cron) to launch + scheduled runs. To explicitly set a timezone to the cron tab, apply a + prefix in the cron tab: "CRON_TZ=${IANA_TIME_ZONE}" or + "TZ=${IANA_TIME_ZONE}". The ${IANA_TIME_ZONE} may only be a valid + string from IANA time zone database. For example, + "CRON_TZ=America/New_York 1 * * * ", or "TZ=America/New_York 1 * * * + ". + + --display-name=DISPLAY_NAME + The display name of the schedule. + + --enable-queueing + Enables new scheduled runs to be queued when max_concurrent_runs + limit is reached. If set to true, new runs will be queued instead of + skipped. + + --end-time=END_TIME + Timestamp after which no new runs can be scheduled. If specified, the + schedule will be completed when either end_time is reached or when + scheduled_run_count >= max_run_count. If neither end time nor + max_run_count is specified, new runs will keep getting scheduled + until this Schedule is paused or deleted. Must be in the RFC 3339 + (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" + + --max-concurrent-runs=MAX_CONCURRENT_RUNS + Maximum number of runs that can be started concurrently for this + Schedule. This is the limit for starting the scheduled requests and + not the execution of the notebook execution jobs created by the + requests. + + --max-runs=MAX_RUNS + The max runs for the schedule. + + --start-time=START_TIME + The timestamp after which the first run can be scheduled. Defaults to + the schedule creation time. Must be in the RFC 3339 + (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/pubsub/topics/create b/gcloud/beta/pubsub/topics/create index e34ceb5dd..d9e35d690 100644 --- a/gcloud/beta/pubsub/topics/create +++ b/gcloud/beta/pubsub/topics/create @@ -5,10 +5,10 @@ SYNOPSIS gcloud beta pubsub topics create TOPIC [TOPIC ...] [--labels=[KEY=VALUE,...]] [--message-retention-duration=MESSAGE_RETENTION_DURATION] - [--kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN - --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN - --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT - --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN] + [--ingestion-log-severity=INGESTION_LOG_SEVERITY + [--cloud-storage-ingestion-bucket=CLOUD_STORAGE_INGESTION_BUCKET + --cloud-storage-ingestion-input-format=INPUT_FORMAT + : --cloud-storage-ingestion-text-delimiter=CLOUD_STORAGE_INGESTION_TEXT_DELIMITER --cloud-storage-ingestion-minimum-object-create-time=CLOUD_STORAGE_INGESTION_MINIMUM_OBJECT_CREATE_TIME --cloud-storage-ingestion-match-glob=CLOUD_STORAGE_INGESTION_MATCH_GLOB] | --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN] [--message-encoding=ENCODING (--schema=SCHEMA : --schema-project=SCHEMA_PROJECT) : --first-revision-id=FIRST_REVISION_ID @@ -69,35 +69,69 @@ FLAGS is one of "s", "m", "h", and "d" for seconds, minutes, hours, and days, respectively. If the unit is omitted, seconds is assumed. - The following flags are for specifying ingestion settings for an import - topic from Amazon Web Services (AWS) Kinesis Data Streams + Following flags are for specifying the data source settings for an import + topic - --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN - The Kinesis data streams consumer Amazon Resource Name (ARN) to use - for ingestion. + --ingestion-log-severity=INGESTION_LOG_SEVERITY + Log severity to use for ingestion. - 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: - --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN - AWS role ARN to be used for Federated Identity authentication with - Kinesis. + Flags that specify settings for an import topic from Cloud Storage - This flag argument must be specified if any of the other arguments in - this group are specified. + --cloud-storage-ingestion-bucket=CLOUD_STORAGE_INGESTION_BUCKET + Cloud Storage bucket from which to ingest data. - --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT - The service account to be used for Federated Identity authentication - with Kinesis. + This flag argument must be specified if any of the other + arguments in this group are specified. - This flag argument must be specified if any of the other arguments in - this group are specified. + --cloud-storage-ingestion-input-format=INPUT_FORMAT + Format of the data in the Cloud Storage bucket. INPUT_FORMAT must + be one of: text, avro, pubsub_avro. - --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN - The Kinesis data stream ARN from which to ingest data. + This flag argument must be specified if any of the other + arguments in this group are specified. - This flag argument must be specified if any of the other arguments in - this group are specified. + --cloud-storage-ingestion-text-delimiter=CLOUD_STORAGE_INGESTION_TEXT_DELIMITER + Delimiter to use with text format when partitioning the object. + + --cloud-storage-ingestion-minimum-object-create-time=CLOUD_STORAGE_INGESTION_MINIMUM_OBJECT_CREATE_TIME + Only Cloud Storage objects with a larger or equal creation + timestamp will be ingested. + + --cloud-storage-ingestion-match-glob=CLOUD_STORAGE_INGESTION_MATCH_GLOB + Glob pattern used to match Cloud Storage objects that will be + ingested. If unset, all objects will be ingested. + + Flags that specify settings for an import topic from Amazon Web + Services (AWS) Kinesis Data Streams + + --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN + Kinesis data streams consumer Amazon Resource Name (ARN) to use + for ingestion. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN + AWS role ARN to be used for Federated Identity authentication + with Kinesis. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT + Service account to be used for Federated Identity authentication + with Kinesis. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN + Kinesis data stream ARN from which to ingest data. + + This flag argument must be specified if any of the other + arguments in this group are specified. Schema settings. The schema that messages published to this topic must conform to and the expected message encoding. diff --git a/gcloud/beta/pubsub/topics/update b/gcloud/beta/pubsub/topics/update index 7a267cead..3873eaba4 100644 --- a/gcloud/beta/pubsub/topics/update +++ b/gcloud/beta/pubsub/topics/update @@ -4,10 +4,10 @@ NAME SYNOPSIS gcloud beta pubsub topics update TOPIC [--update-labels=[KEY=VALUE,...]] [--clear-ingestion-data-source-settings - | --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN - --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN - --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT - --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN] + | --ingestion-log-severity=INGESTION_LOG_SEVERITY + [--cloud-storage-ingestion-bucket=CLOUD_STORAGE_INGESTION_BUCKET + --cloud-storage-ingestion-input-format=INPUT_FORMAT + : --cloud-storage-ingestion-text-delimiter=CLOUD_STORAGE_INGESTION_TEXT_DELIMITER --cloud-storage-ingestion-minimum-object-create-time=CLOUD_STORAGE_INGESTION_MINIMUM_OBJECT_CREATE_TIME --cloud-storage-ingestion-match-glob=CLOUD_STORAGE_INGESTION_MATCH_GLOB] | --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN] [--clear-labels | --remove-labels=[KEY,...]] [--clear-message-retention-duration | --message-retention-duration=MESSAGE_RETENTION_DURATION] @@ -116,39 +116,81 @@ FLAGS If set, clear the Ingestion Data Source Settings from the topic. Use --no-clear-ingestion-data-source-settings to disable this flag. - The following flags are for specifying ingestion settings for an import - topic from Amazon Web Services (AWS) Kinesis Data Streams + Following flags are for specifying the data source settings for an + import topic - When updating AWSKinesis Source flags, all AWSKinesis Source flags must - be specified. Otherwise, any omitted AWSKinesis Source flags revert to - their default value. + When updating IngestionDataSourceSettings flags, all + IngestionDataSourceSettings flags must be specified. Otherwise, any + omitted IngestionDataSourceSettings flags revert to their default value. - --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN - The Kinesis data streams consumer Amazon Resource Name (ARN) to use - for ingestion. + --ingestion-log-severity=INGESTION_LOG_SEVERITY + Log severity to use for ingestion. - 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: - --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN - AWS role ARN to be used for Federated Identity authentication with - Kinesis. + Flags that specify settings for an import topic from Cloud Storage - This flag argument must be specified if any of the other arguments - in this group are specified. + When updating CloudStorage Source flags, all CloudStorage Source + flags must be specified. Otherwise, any omitted CloudStorage Source + flags revert to their default value. - --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT - The service account to be used for Federated Identity - authentication with Kinesis. + --cloud-storage-ingestion-bucket=CLOUD_STORAGE_INGESTION_BUCKET + Cloud Storage bucket from which to ingest data. - This flag argument must be specified if any of the other arguments - in this group are specified. + This flag argument must be specified if any of the other + arguments in this group are specified. - --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN - The Kinesis data stream ARN from which to ingest data. + --cloud-storage-ingestion-input-format=INPUT_FORMAT + Format of the data in the Cloud Storage bucket. INPUT_FORMAT + must be one of: text, avro, pubsub_avro. - This flag argument must be specified if any of the other arguments - in this group are specified. + This flag argument must be specified if any of the other + arguments in this group are specified. + + --cloud-storage-ingestion-text-delimiter=CLOUD_STORAGE_INGESTION_TEXT_DELIMITER + Delimiter to use with text format when partitioning the object. + + --cloud-storage-ingestion-minimum-object-create-time=CLOUD_STORAGE_INGESTION_MINIMUM_OBJECT_CREATE_TIME + Only Cloud Storage objects with a larger or equal creation + timestamp will be ingested. + + --cloud-storage-ingestion-match-glob=CLOUD_STORAGE_INGESTION_MATCH_GLOB + Glob pattern used to match Cloud Storage objects that will be + ingested. If unset, all objects will be ingested. + + Flags that specify settings for an import topic from Amazon Web + Services (AWS) Kinesis Data Streams + + When updating AWSKinesis Source flags, all AWSKinesis Source flags + must be specified. Otherwise, any omitted AWSKinesis Source flags + revert to their default value. + + --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN + Kinesis data streams consumer Amazon Resource Name (ARN) to use + for ingestion. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN + AWS role ARN to be used for Federated Identity authentication + with Kinesis. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT + Service account to be used for Federated Identity + authentication with Kinesis. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN + Kinesis data stream ARN from which to ingest data. + + 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: diff --git a/gcloud/beta/resource-manager/tags/keys/create b/gcloud/beta/resource-manager/tags/keys/create index e84d82164..d02579033 100644 --- a/gcloud/beta/resource-manager/tags/keys/create +++ b/gcloud/beta/resource-manager/tags/keys/create @@ -46,8 +46,8 @@ FLAGS --purpose=PURPOSE Purpose specifier of the TagKey that can only be set on creation. Specifying this field adds additional validation from the policy system - that corresponds to the purpose. PURPOSE must be (only one value is - supported): GCE_FIREWALL. + that corresponds to the purpose. PURPOSE must be one of: GCE_FIREWALL, + DATA_GOVERNANCE. --purpose-data=[network=NETWORK] Purpose data of the TagKey that can only be set on creation. This data diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index fa1176a0e..8582b542a 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -37,8 +37,8 @@ SYNOPSIS --[no-]default-url --[no-]deploy-health-check --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT --gpu-type=GPU_TYPE - --mesh=MESH --remove-containers=[CONTAINER,...] - --revision-suffix=REVISION_SUFFIX + --[no-]invoker-iam-check --mesh=MESH + --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -551,6 +551,13 @@ FLAGS --gpu-type=GPU_TYPE The GPU type to use. + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. + --mesh=MESH Enables Cloud Service Mesh using the specified mesh resource name. Mesh resource name must be in the format of diff --git a/gcloud/beta/run/help b/gcloud/beta/run/help index 2176c31ac..9059013df 100644 --- a/gcloud/beta/run/help +++ b/gcloud/beta/run/help @@ -32,6 +32,9 @@ GROUPS jobs (BETA) View and manage your Cloud Run jobs. + multi-region-services + (BETA) Manage your Cloud Run multi-region services. + regions (BETA) View available Cloud Run (fully managed) regions. diff --git a/gcloud/beta/run/multi-region-services/delete b/gcloud/beta/run/multi-region-services/delete new file mode 100644 index 000000000..e042d122c --- /dev/null +++ b/gcloud/beta/run/multi-region-services/delete @@ -0,0 +1,150 @@ +NAME + gcloud beta run multi-region-services delete - deletes a multi-region + service + +SYNOPSIS + gcloud beta run multi-region-services delete + (SERVICE : --namespace=NAMESPACE) [--[no-]async] + [--platform=PLATFORM; default="managed"] + [--region=REGION + | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION + | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes a multi-region service. + +EXAMPLES + To delete a service: + + $ gcloud beta run multi-region-services delete + +POSITIONAL ARGUMENTS + Service resource - Service to delete. The arguments in this group can be + used to specify the attributes of this resource. + + This must be specified. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument SERVICE on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --namespace=NAMESPACE + Specific to Cloud Run for Anthos: Kubernetes namespace for the + service. + + To set the namespace attribute: + ▸ provide the argument SERVICE on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line; + ▸ set the property run/namespace; + ▸ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▸ provide the argument project on the command line; + ▸ set the property core/project. + +FLAGS + --[no-]async + Return immediately, without waiting for the operation in progress to + complete. Defaults to --no-async for Cloud Run (fully managed) and + --async for Cloud Run for Anthos. Use --async to enable and --no-async + to disable. + + --platform=PLATFORM; default="managed" + Target platform for running commands. Alternatively, set the property + [run/platform]. PLATFORM must be one of: + + managed + Fully managed version of Cloud Run. Use with the --region flag or + set the [run/region] property to specify a Cloud Run region. + gke + Cloud Run for Anthos on Google Cloud. Use with the --cluster and + --cluster-location flags or set the [run/cluster] and + [run/cluster_location] properties to specify a cluster in a given + zone. + kubernetes + Use a Knative-compatible kubernetes cluster. Use with the + --kubeconfig and --context flags to specify a kubeconfig file and + the context for connecting. + + Arguments to locate resources, depending on the platform used. + + At most one of these can be specified: + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud. Specify --platform=gke to use: + + Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully + specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ◇ provide the argument --cluster on the command line; + ◇ set the property run/cluster; + ◇ specify the cluster from a list of available clusters. + + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. + + To set the location attribute: + ◇ provide the argument --cluster on the command line with a + fully specified name; + ◇ set the property run/cluster with a fully specified name; + ◇ specify the cluster from a list of available clusters with a + fully specified name; + ◇ provide the argument --cluster-location on the command line; + ◇ set the property run/cluster_location; + ◇ specify the cluster location from a list of available zones. + + Only applicable if connecting to Cloud Run for Anthos deployed on + VMware. Specify --platform=kubernetes to use: + + --context=CONTEXT + The name of the context in your kubectl config file to use for + connecting. + + --kubeconfig=KUBECONFIG + The absolute path to your kubectl config file. If not specified, + the colon- or semicolon-delimited list of paths specified by + $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to + ~/.kube/config. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run multi-region-services delete + diff --git a/gcloud/beta/run/multi-region-services/describe b/gcloud/beta/run/multi-region-services/describe new file mode 100644 index 000000000..9067380b1 --- /dev/null +++ b/gcloud/beta/run/multi-region-services/describe @@ -0,0 +1,155 @@ +NAME + gcloud beta run multi-region-services describe - command to describe a + multi-region service + +SYNOPSIS + gcloud beta run multi-region-services describe + (SERVICE : --namespace=NAMESPACE) + [--platform=PLATFORM; default="managed"] + [--region=REGION + | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION + | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Command to describe a multi-region service. + +EXAMPLES + To obtain details about a given service: + + $ gcloud beta run multi-region-services describe + + To get those details in the YAML format: + + $ gcloud beta run multi-region-services describe \ + --format=yaml + + To get them in YAML format suited to export (omitting metadata specific to + this deployment and status info): + + $ gcloud beta run multi-region-services describe \ + --format=export + +POSITIONAL ARGUMENTS + Service resource - Service to describe. The arguments in this group can be + used to specify the attributes of this resource. + + This must be specified. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument SERVICE on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --namespace=NAMESPACE + Specific to Cloud Run for Anthos: Kubernetes namespace for the + service. + + To set the namespace attribute: + ▸ provide the argument SERVICE on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line; + ▸ set the property run/namespace; + ▸ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▸ provide the argument project on the command line; + ▸ set the property core/project. + +FLAGS + --platform=PLATFORM; default="managed" + Target platform for running commands. Alternatively, set the property + [run/platform]. PLATFORM must be one of: + + managed + Fully managed version of Cloud Run. Use with the --region flag or + set the [run/region] property to specify a Cloud Run region. + gke + Cloud Run for Anthos on Google Cloud. Use with the --cluster and + --cluster-location flags or set the [run/cluster] and + [run/cluster_location] properties to specify a cluster in a given + zone. + kubernetes + Use a Knative-compatible kubernetes cluster. Use with the + --kubeconfig and --context flags to specify a kubeconfig file and + the context for connecting. + + Arguments to locate resources, depending on the platform used. + + At most one of these can be specified: + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud. Specify --platform=gke to use: + + Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully + specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ◇ provide the argument --cluster on the command line; + ◇ set the property run/cluster; + ◇ specify the cluster from a list of available clusters. + + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. + + To set the location attribute: + ◇ provide the argument --cluster on the command line with a + fully specified name; + ◇ set the property run/cluster with a fully specified name; + ◇ specify the cluster from a list of available clusters with a + fully specified name; + ◇ provide the argument --cluster-location on the command line; + ◇ set the property run/cluster_location; + ◇ specify the cluster location from a list of available zones. + + Only applicable if connecting to Cloud Run for Anthos deployed on + VMware. Specify --platform=kubernetes to use: + + --context=CONTEXT + The name of the context in your kubectl config file to use for + connecting. + + --kubeconfig=KUBECONFIG + The absolute path to your kubectl config file. If not specified, + the colon- or semicolon-delimited list of paths specified by + $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to + ~/.kube/config. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run multi-region-services describe + diff --git a/gcloud/beta/run/multi-region-services/help b/gcloud/beta/run/multi-region-services/help new file mode 100644 index 000000000..eb077b0ba --- /dev/null +++ b/gcloud/beta/run/multi-region-services/help @@ -0,0 +1,135 @@ +NAME + gcloud beta run multi-region-services - manage your Cloud Run multi-region + services + +SYNOPSIS + gcloud beta run multi-region-services COMMAND + [--platform=PLATFORM; default="managed"] + [--region=REGION + | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION + | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The gcloud run multi-region-services command group lets you deploy + container images to Google Cloud Run across multiple regions at once. + +EXAMPLES + To deploy your container, use the gcloud run multi-region-services deploy + command: + + $ gcloud beta run multi-region-services deploy \ + --image --regions [region-list] For more \ + information, run: + $ gcloud run deploy --help + +FLAGS + --platform=PLATFORM; default="managed" + Target platform for running commands. Alternatively, set the property + [run/platform]. PLATFORM must be one of: + + managed + Fully managed version of Cloud Run. Use with the --region flag or + set the [run/region] property to specify a Cloud Run region. + gke + Cloud Run for Anthos on Google Cloud. Use with the --cluster and + --cluster-location flags or set the [run/cluster] and + [run/cluster_location] properties to specify a cluster in a given + zone. + kubernetes + Use a Knative-compatible kubernetes cluster. Use with the + --kubeconfig and --context flags to specify a kubeconfig file and + the context for connecting. + + Arguments to locate resources, depending on the platform used. + + At most one of these can be specified: + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud. Specify --platform=gke to use: + + Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully + specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ◇ provide the argument --cluster on the command line; + ◇ set the property run/cluster; + ◇ specify the cluster from a list of available clusters. + + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. + + To set the location attribute: + ◇ provide the argument --cluster on the command line with a + fully specified name; + ◇ set the property run/cluster with a fully specified name; + ◇ specify the cluster from a list of available clusters with a + fully specified name; + ◇ provide the argument --cluster-location on the command line; + ◇ set the property run/cluster_location; + ◇ specify the cluster location from a list of available zones. + + Only applicable if connecting to Cloud Run for Anthos deployed on + VMware. Specify --platform=kubernetes to use: + + --context=CONTEXT + The name of the context in your kubectl config file to use for + connecting. + + --kubeconfig=KUBECONFIG + The absolute path to your kubectl config file. If not specified, + the colon- or semicolon-delimited list of paths specified by + $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to + ~/.kube/config. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (BETA) Deletes a multi-region service. + + describe + (BETA) Command to describe a multi-region service. + + list + (BETA) List available multi-region services. + + replace + (BETA) Create or Update multi-region service from YAML. + + update + (BETA) Update environment variables, add/remove regions, and other + configuration settings in Multi-Region Services. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run multi-region-services + diff --git a/gcloud/beta/run/multi-region-services/list b/gcloud/beta/run/multi-region-services/list new file mode 100644 index 000000000..6adb101d7 --- /dev/null +++ b/gcloud/beta/run/multi-region-services/list @@ -0,0 +1,167 @@ +NAME + gcloud beta run multi-region-services list - list available multi-region + services + +SYNOPSIS + gcloud beta run multi-region-services list [--namespace=NAMESPACE] + [--platform=PLATFORM; default="managed"] + [--region=REGION + | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION + | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List available multi-region services. + +EXAMPLES + To list available services: + + $ gcloud beta run multi-region-services list + +FLAGS + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke + or --platform=kubernetes to use: + + Namespace resource - Namespace to list services in. This represents a + Cloud resource. + + --namespace=NAMESPACE + ID of the namespace or fully qualified identifier for the + namespace. + + To set the namespace attribute: + ▫ provide the argument --namespace on the command line; + ▫ set the property run/namespace; + ▫ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▫ provide the argument project on the command line; + ▫ set the property core/project. + + --platform=PLATFORM; default="managed" + Target platform for running commands. Alternatively, set the property + [run/platform]. PLATFORM must be one of: + + managed + Fully managed version of Cloud Run. Use with the --region flag or + set the [run/region] property to specify a Cloud Run region. + gke + Cloud Run for Anthos on Google Cloud. Use with the --cluster and + --cluster-location flags or set the [run/cluster] and + [run/cluster_location] properties to specify a cluster in a given + zone. + kubernetes + Use a Knative-compatible kubernetes cluster. Use with the + --kubeconfig and --context flags to specify a kubeconfig file and + the context for connecting. + + Arguments to locate resources, depending on the platform used. + + At most one of these can be specified: + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud. Specify --platform=gke to use: + + Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully + specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ◇ provide the argument --cluster on the command line; + ◇ set the property run/cluster; + ◇ specify the cluster from a list of available clusters. + + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. + + To set the location attribute: + ◇ provide the argument --cluster on the command line with a + fully specified name; + ◇ set the property run/cluster with a fully specified name; + ◇ specify the cluster from a list of available clusters with a + fully specified name; + ◇ provide the argument --cluster-location on the command line; + ◇ set the property run/cluster_location; + ◇ specify the cluster location from a list of available zones. + + Only applicable if connecting to Cloud Run for Anthos deployed on + VMware. Specify --platform=kubernetes to use: + + --context=CONTEXT + The name of the context in your kubectl config file to use for + connecting. + + --kubeconfig=KUBECONFIG + The absolute path to your kubectl config file. If not specified, + the colon- or semicolon-delimited list of paths specified by + $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to + ~/.kube/config. + +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 + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run multi-region-services list + diff --git a/gcloud/beta/run/multi-region-services/replace b/gcloud/beta/run/multi-region-services/replace new file mode 100644 index 000000000..8ba050cd4 --- /dev/null +++ b/gcloud/beta/run/multi-region-services/replace @@ -0,0 +1,146 @@ +NAME + gcloud beta run multi-region-services replace - create or Update + multi-region service from YAML + +SYNOPSIS + gcloud beta run multi-region-services replace FILE [--async] [--dry-run] + [--namespace=NAMESPACE] [--platform=PLATFORM; default="managed"] + [--region=REGION + | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION + | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Creates or replaces a service from a YAML service specification. + +EXAMPLES + To replace the specification for a service defined in myservice.yaml + + $ gcloud beta run multi-region-services replace myservice.yaml + +POSITIONAL ARGUMENTS + FILE + The absolute path to the YAML file with a Knative service definition + for the service to update or deploy. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --dry-run + If set to true, only validates the configuration. The configuration + will not be applied. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke + or --platform=kubernetes to use: + + Namespace resource - Namespace to replace service. This represents a + Cloud resource. + + --namespace=NAMESPACE + ID of the namespace or fully qualified identifier for the + namespace. + + To set the namespace attribute: + ▫ provide the argument --namespace on the command line; + ▫ set the property run/namespace; + ▫ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▫ provide the argument project on the command line; + ▫ set the property core/project. + + --platform=PLATFORM; default="managed" + Target platform for running commands. Alternatively, set the property + [run/platform]. PLATFORM must be one of: + + managed + Fully managed version of Cloud Run. Use with the --region flag or + set the [run/region] property to specify a Cloud Run region. + gke + Cloud Run for Anthos on Google Cloud. Use with the --cluster and + --cluster-location flags or set the [run/cluster] and + [run/cluster_location] properties to specify a cluster in a given + zone. + kubernetes + Use a Knative-compatible kubernetes cluster. Use with the + --kubeconfig and --context flags to specify a kubeconfig file and + the context for connecting. + + Arguments to locate resources, depending on the platform used. + + At most one of these can be specified: + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud. Specify --platform=gke to use: + + Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully + specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ◇ provide the argument --cluster on the command line; + ◇ set the property run/cluster; + ◇ specify the cluster from a list of available clusters. + + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. + + To set the location attribute: + ◇ provide the argument --cluster on the command line with a + fully specified name; + ◇ set the property run/cluster with a fully specified name; + ◇ specify the cluster from a list of available clusters with a + fully specified name; + ◇ provide the argument --cluster-location on the command line; + ◇ set the property run/cluster_location; + ◇ specify the cluster location from a list of available zones. + + Only applicable if connecting to Cloud Run for Anthos deployed on + VMware. Specify --platform=kubernetes to use: + + --context=CONTEXT + The name of the context in your kubectl config file to use for + connecting. + + --kubeconfig=KUBECONFIG + The absolute path to your kubectl config file. If not specified, + the colon- or semicolon-delimited list of paths specified by + $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to + ~/.kube/config. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run multi-region-services replace + diff --git a/gcloud/beta/run/multi-region-services/update b/gcloud/beta/run/multi-region-services/update new file mode 100644 index 000000000..8c173cc5c --- /dev/null +++ b/gcloud/beta/run/multi-region-services/update @@ -0,0 +1,720 @@ +NAME + gcloud beta run multi-region-services update - update environment + variables, add/remove regions, and other configuration settings in + Multi-Region Services + +SYNOPSIS + gcloud beta run multi-region-services update + [[SERVICE] --namespace=NAMESPACE] [--async] [--concurrency=CONCURRENCY] + [--container=CONTAINER] [--ingress=INGRESS; default="all"] + [--max-instances=MAX_INSTANCES] [--min-instances=MIN_INSTANCES] + [--platform=PLATFORM; default="managed"] + [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] + [--no-traffic] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] + --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE --memory=MEMORY + --port=PORT --remove-volume-mount=[MOUNT_PATH,...] + --[no-]use-http2 --clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] + --update-env-vars=[KEY=VALUE,...] --clear-secrets + | --set-secrets=[KEY=VALUE,...] + | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] + [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost + --[no-]cpu-throttling --[no-]default-url --[no-]deploy-health-check + --description=DESCRIPTION + --execution-environment=EXECUTION_ENVIRONMENT + --[no-]invoker-iam-check --max-surge=MAX_SURGE + --max-unavailable=MAX_UNAVAILABLE --mesh=MESH + --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX + --scaling=SCALING --service-max-instances=SERVICE_MAX_INSTANCES + --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity + --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --clear-cloudsql-instances + | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + --add-custom-audiences=[CUSTOM-AUDIENCES,...] + | --clear-custom-audiences + | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + | --set-custom-audiences=[CUSTOM-AUDIENCES,...] + --add-volume=[KEY=VALUE,...] --clear-volumes + --remove-volume=[VOLUME,...] --binary-authorization=POLICY + | --clear-binary-authorization --clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + --clear-key | --key=KEY --clear-network + | --network=NETWORK --subnet=SUBNET --clear-network-tags + | --network-tags=[TAG,...] --clear-post-key-revocation-action-type + | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] + | --update-labels=[KEY=VALUE,...]] + [--connectivity=CONNECTIVITY --clear-config-maps + | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] + --update-config-maps=[KEY=VALUE,...]] + [--region=REGION + | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION + | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update environment variables, add/remove regions, and other + configuration settings in Multi-Region Services. + +EXAMPLES + To update one or more env vars: + + $ gcloud beta run multi-region-services update myservice \ + --update-env-vars=KEY1=VALUE1,KEY2=VALUE2 + +POSITIONAL ARGUMENTS + Service resource - Service to update the configuration of. The arguments + in this group can be used to specify the attributes of this resource. + + [SERVICE] + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument SERVICE on the command line; + ▸ specify the service name from an interactive prompt. + + --namespace=NAMESPACE + Specific to Cloud Run for Anthos: Kubernetes namespace for the + service. + + To set the namespace attribute: + ▸ provide the argument SERVICE on the command line with a fully + specified name; + ▸ specify the service name from an interactive prompt with a fully + specified name; + ▸ provide the argument --namespace on the command line; + ▸ set the property run/namespace; + ▸ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▸ provide the argument project on the command line; + ▸ set the property core/project. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --concurrency=CONCURRENCY + Set the maximum number of concurrent requests allowed per container + instance. Leave concurrency unspecified or provide the special value + 'default' to receive the server default value. + + --container=CONTAINER + Specifies a container by name. Flags following --container will apply + to the specified container. + + --ingress=INGRESS; default="all" + Set the ingress traffic sources allowed to call the service. For Cloud + Run (fully managed) the --[no-]allow-unauthenticated flag separately + controls the identities allowed to call the service. INGRESS must be + one of: + + all + Inbound requests from all sources are allowed. + internal + For Cloud Run (fully managed), only inbound requests from VPC + networks in the same project or VPC Service Controls perimeter, as + well as Pub/Sub subscriptions and Eventarc events in the same + project or VPC Service Controls perimeter are allowed. All other + requests are rejected. See + https://cloud.google.com/run/docs/securing/ingress for full details + on the definition of internal traffic for Cloud Run (fully + managed). For Cloud Run for Anthos, only inbound requests from the + same cluster are allowed. + + internal-and-cloud-load-balancing + Only supported for Cloud Run (fully managed). Only inbound requests + from Google Cloud Load Balancing or a traffic source allowed by the + internal option are allowed. + + --max-instances=MAX_INSTANCES + The maximum number of container instances of the Service to run. Use + 'default' to unset the limit and use the platform default. + + --min-instances=MIN_INSTANCES + The minimum number of container instances for this Revision of the + Service to run or 'default' to remove any minimum. + + --platform=PLATFORM; default="managed" + Target platform for running commands. Alternatively, set the property + [run/platform]. PLATFORM must be one of: + + managed + Fully managed version of Cloud Run. Use with the --region flag or + set the [run/region] property to specify a Cloud Run region. + gke + Cloud Run for Anthos on Google Cloud. Use with the --cluster and + --cluster-location flags or set the [run/cluster] and + [run/cluster_location] properties to specify a cluster in a given + zone. + kubernetes + Use a Knative-compatible kubernetes cluster. Use with the + --kubeconfig and --context flags to specify a kubeconfig file and + the context for connecting. + + --service-account=SERVICE_ACCOUNT + Service account associated with the revision of the service. The + service account represents the identity of the running revision, and + determines what permissions the revision has. For the managed platform, + this is the email address of an IAM service account. For the + Kubernetes-based platforms (gke, kubernetes), this is the name of a + Kubernetes service account in the same namespace as the service. If not + provided, the revision will use the default service account of the + project, or default Kubernetes namespace service account respectively. + + --tag=TAG + Traffic tag to assign to the newly created revision. + + --timeout=TIMEOUT + Set the maximum request execution time (timeout). It is specified as a + duration; for example, "10m5s" is ten minutes, and five seconds. If you + don't specify a unit, seconds is assumed. For example, "10" is 10 + seconds. + + --no-traffic + True to avoid sending traffic to the revision being deployed. Setting + this flag assigns any traffic assigned to the LATEST revision to the + specific revision bound to LATEST before the deployment. The effect is + that the revision being deployed will not receive traffic. + + After a deployment with this flag the LATEST revision will not receive + traffic on future deployments. To restore sending traffic to the LATEST + revision by default, run the gcloud run services update-traffic command + with --to-latest. + + Container Flags + + If the --container or --remove-containers flag is specified the following + arguments may only be specified after a --container flag. + + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume + on this resource and PATH is the path within the container's + filesystem to mount this volume. + + --args=[ARG,...] + Comma-separated arguments passed to the command run by the + container image. If not specified and no '--command' is provided, + the container image's default Cmd is used. Otherwise, if not + specified, no arguments are passed. To reset this field to its + default, pass an empty string. + + --clear-volume-mounts + Remove all existing mounts from the current container. + + --command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default Entrypoint is run. To reset this field to its + default, pass an empty string. + + --cpu=CPU + Set a CPU limit in Kubernetes cpu units. + + Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run + (fully managed), 4 cpus also requires a minimum 2Gi --memory value. + Examples 2, 2.0, 2000m + + Cloud Run for Anthos and Knative-compatible Kubernetes clusters + support fractional values. Examples .5, 500m, 2 + + --depends-on=[CONTAINER,...] + List of container dependencies to add to the current container. + + --image=IMAGE + Name of the container image to deploy (e.g. + gcr.io/cloudrun/hello:latest). + + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. + + --port=PORT + Container port to receive requests at. Also sets the $PORT + environment variable. Must be a number between 1 and 65535, + inclusive. To unset this field, pass the special value "default". + If updating an existing service with a TCP startup probe pointing + to the previous container port, this will also update the probe + port. + + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + + --[no-]use-http2 + Whether to use HTTP/2 for connections to the service. Use + --use-http2 to enable and --no-use-http2 to disable. + + At most one of these can be specified: + + --clear-env-vars + Remove all environment variables. + + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed + before the new environment variables are added. Example YAML + content: + + KEY_1: "value1" + KEY_2: "value 2" + + --set-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. All + existing environment variables will be removed first. + + Only --update-env-vars and --remove-env-vars can be used together. + If both are specified, --remove-env-vars will be applied first. + + --remove-env-vars=[KEY,...] + List of environment variables to be removed. + + --update-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + Specify secrets to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. Values should be in the form + SECRET_NAME:SECRET_VERSION. For example: + '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' + will mount a volume at '/secrets/api' containing a file 'key' with the + latest version of secret 'mysecret'. An environment variable named ENV + will also be created whose value is version 1 of secret 'othersecret'. + + At most one of these can be specified: + + --clear-secrets + Remove all secrets. + + --set-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. All existing secrets + will be removed first. + + Only --update-secrets and --remove-secrets can be used together. If + both are specified, --remove-secrets will be applied first. + + --remove-secrets=[KEY,...] + List of secrets to be removed. + + --update-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass + for more information. Next update or deploy command will + automatically clear existing breakglass justification. + + --clear-vpc-connector + Remove the VPC connector for this resource. + + --[no-]cpu-boost + Whether to allocate extra CPU to containers on startup to reduce the + perceived latency of a cold start request. Enabled by default when + unspecified on new services. Use --cpu-boost to enable and + --no-cpu-boost to disable. + + --[no-]cpu-throttling + Whether to throttle the CPU when the container is not actively + serving requests. Use --cpu-throttling to enable and + --no-cpu-throttling to disable. + + --[no-]default-url + Toggles the default url for a run service. This is enabled by default + if not specified. Use --default-url to enable and --no-default-url to + disable. + + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. + + --description=DESCRIPTION + Provides an optional, human-readable description of the service. + + --execution-environment=EXECUTION_ENVIRONMENT + Selects the execution environment where the application will run. + EXECUTION_ENVIRONMENT must be one of: + + gen1 + Run the application in a first generation execution environment. + gen2 + Run the application in a second generation execution environment. + + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. + + --max-surge=MAX_SURGE + A maximum percentage of instances that will be moved in each step of + traffic split changes. Use "default" to unset the limit and use the + platform default. + + --max-unavailable=MAX_UNAVAILABLE + A maximum percentage of instances that may be unavailable during + traffic split changes. Use "default" to unset the limit and use the + platform default. + + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. + Mesh resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + + --remove-containers=[CONTAINER,...] + List of containers to remove. + + --revision-suffix=REVISION_SUFFIX + Specify the suffix of the revision name. Revision names always start + with the service name automatically. For example, specifying + [--revision-suffix=v1] for a service named 'helloworld', would lead + to a revision named 'helloworld-v1'. Set empty string to clear the + suffix and resume server-assigned naming. + + --scaling=SCALING + The scaling mode to use for this resource. SCALING must be one of: + + automatic + The number of instances is scaled automatically based on the + usage metrics. + manual + The number of instances is fixed to a provided config value. + + --service-max-instances=SERVICE_MAX_INSTANCES + The maximum number of container instances for this Service to run. + This instance limit will be divided among all Revisions receiving a + percentage of traffic. Once service-max-instances is enabled for a + service, it cannot be disabled. + + --service-min-instances=SERVICE_MIN_INSTANCES + The minimum number of container instances for this Service to run or + 'default' to remove any minimum. These instances will be divided + among all Revisions receiving a percentage of traffic. + + --[no-]session-affinity + Whether to enable session affinity for connections to the service. + Use --session-affinity to enable and --no-session-affinity to + disable. + + --vpc-connector=VPC_CONNECTOR + Set a VPC connector for this resource. + + --vpc-egress=VPC_EGRESS + Specify which of the outbound traffic to send through Direct VPC + egress or the VPC connector for this resource. This resource must + have Direct VPC egress enabled or a VPC connector to set this flag. + VPC_EGRESS must be one of: + + all + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. + all-traffic + Sends all outbound traffic through Direct VPC egress or the VPC + connector. + private-ranges-only + Default option. Sends outbound traffic to private IP addresses + (RFC 1918 and Private Google Access IPs) through Direct VPC + egress or the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. + + These flags modify the Cloud SQL instances this Service connects to. You + can specify a name of a Cloud SQL instance if it's in the same project + and region as your Cloud Run service; otherwise specify + :: for the instance. + + At most one of these can be specified: + + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Append the given values to the current Cloud SQL instances. + + --clear-cloudsql-instances + Empty the current Cloud SQL instances. + + --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Remove the given values from the current Cloud SQL instances. + + --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Completely replace the current Cloud SQL instances with the given + values. + + These flags modify the custom audiences that can be used in the audience + field of ID token for authenticated requests. + + At most one of these can be specified: + + --add-custom-audiences=[CUSTOM-AUDIENCES,...] + Append the given values to the current custom audiences. + + --clear-custom-audiences + Empty the current custom audiences. + + --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + Remove the given values from the current custom audiences. + + --set-custom-audiences=[CUSTOM-AUDIENCES,...] + Completely replace the current custom audiences with the given + values. + + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + + At most one of these can be specified: + + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". + + --clear-binary-authorization + Remove any previously set Binary Authorization policy. + + At most one of these can be specified: + + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. + + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server + after CMEK key revocation is detected. + + At most one of these can be specified: + + --clear-key + Remove any previously set CMEK key reference. + + --key=KEY + CMEK key reference to encrypt the container with. + + At most one of these can be specified: + + --clear-network + Disconnect this Cloud Run service from the VPC network it is + connected to. + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Run service will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. + + --subnet=SUBNET + The VPC subnetwork that the Cloud Run service will get IPs from. + The subnetwork must be /26 or larger. If --network is also + specified, subnet must be a subnetwork of the network specified + by the --network flag. If --network is not specified, network + will be looked up from this subnetwork. To clear existing VPC + network settings, use --clear-network. + + At most one of these can be specified: + + --clear-network-tags + Clears all existing Compute Engine tags from the Cloud Run + service. + + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run service. To clear existing tags, use + --clear-network-tags. + + At most one of these can be specified: + + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. + + --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE + Action type after CMEK key revocation. + POST_KEY_REVOCATION_ACTION_TYPE must be one of: + + prevent-new + No new instances will be started after CMEK key revocation. + shut-down + No new instances will be started and the existing instances + will be shut down after CMEK key revocation. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta run multi-region-services update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta run multi-region-services update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + + At most one of these can be specified: + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + An alias to --update-labels. + + --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. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke + or --platform=kubernetes to use: + + --connectivity=CONNECTIVITY + (DEPRECATED) Defaults to 'external'. If 'external', the service can + be invoked through the internet, in addition to through the cluster + network. + + The --connectivity flag is deprecated but will continue to be + supported. Prefer to use the --ingress flag instead. CONNECTIVITY + must be one of: + + external + Visible from outside the cluster. + internal + Visible only within the cluster. + + Specify config map to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. The values associated with each of + these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may + omit the key within the config map to specify a mount of all keys within + the config map. For example: + '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will + create a volume with config map 'myconfig' and mount that volume at + '/my/path'. Because no config map key was specified, all keys in + 'myconfig' will be included. An environment variable named ENV will also + be created whose value is the value of 'key.json' in 'otherconfig. Not + supported on the fully managed version of Cloud Run. + + At most one of these can be specified: + + --clear-config-maps + Remove all config-maps. + + --set-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. All existing + config-maps will be removed first. + + Only --update-config-maps and --remove-config-maps can be used + together. If both are specified, --remove-config-maps will be applied + first. + + --remove-config-maps=[KEY,...] + List of config-maps to be removed. + + --update-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. + + Arguments to locate resources, depending on the platform used. + + At most one of these can be specified: + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud. Specify --platform=gke to use: + + Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully + specified name; + ▸ set the property run/cluster with a fully specified name; + ▸ specify the cluster from a list of available clusters with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the + cluster. + + To set the cluster attribute: + ▫ provide the argument --cluster on the command line; + ▫ set the property run/cluster; + ▫ specify the cluster from a list of available clusters. + + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. + + To set the location attribute: + ▫ provide the argument --cluster on the command line with a + fully specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --cluster-location on the command line; + ▫ set the property run/cluster_location; + ▫ specify the cluster location from a list of available zones. + + Only applicable if connecting to Cloud Run for Anthos deployed on + VMware. Specify --platform=kubernetes to use: + + --context=CONTEXT + The name of the context in your kubectl config file to use for + connecting. + + --kubeconfig=KUBECONFIG + The absolute path to your kubectl config file. If not specified, + the colon- or semicolon-delimited list of paths specified by + $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to + ~/.kube/config. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run multi-region-services update + diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 497ad23d5..56a586d64 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -22,8 +22,8 @@ SYNOPSIS [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling --[no-]default-url --[no-]deploy-health-check --execution-environment=EXECUTION_ENVIRONMENT --gpu-type=GPU_TYPE - --mesh=MESH --remove-containers=[CONTAINER,...] - --revision-suffix=REVISION_SUFFIX + --[no-]invoker-iam-check --mesh=MESH + --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -350,6 +350,13 @@ FLAGS --gpu-type=GPU_TYPE The GPU type to use. + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. + --mesh=MESH Enables Cloud Service Mesh using the specified mesh resource name. Mesh resource name must be in the format of diff --git a/gcloud/beta/scc/sources/describe b/gcloud/beta/scc/sources/describe index d29686d20..f3d714967 100644 --- a/gcloud/beta/scc/sources/describe +++ b/gcloud/beta/scc/sources/describe @@ -62,7 +62,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for + This command uses the securitycenter/v2 API. The full documentation for this API can be found at: https://cloud.google.com/security-command-center NOTES diff --git a/gcloud/beta/service-extensions/help b/gcloud/beta/service-extensions/help index 77a2c0e7a..b63d1b226 100644 --- a/gcloud/beta/service-extensions/help +++ b/gcloud/beta/service-extensions/help @@ -24,6 +24,12 @@ GROUPS lb-traffic-extensions (BETA) Manage Service Extensions LbTrafficExtension resources. + wasm-plugin-versions + (BETA) Interact with and manage Service Extensions WasmPluginVersions. + + wasm-plugins + (BETA) Interact with and manage Service Extensions WasmPlugins. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/service-extensions/wasm-plugin-versions/create b/gcloud/beta/service-extensions/wasm-plugin-versions/create new file mode 100644 index 000000000..b6cf52295 --- /dev/null +++ b/gcloud/beta/service-extensions/wasm-plugin-versions/create @@ -0,0 +1,115 @@ +NAME + gcloud beta service-extensions wasm-plugin-versions create - create a + WasmPluginVersion resource + +SYNOPSIS + gcloud beta service-extensions wasm-plugin-versions create + (WASM_PLUGIN_VERSION : --location=LOCATION --wasm-plugin=WASM_PLUGIN) + --image=IMAGE [--async] [--description=DESCRIPTION] + [--labels=[KEY=VALUE,...]] + [--plugin-config=PLUGIN_CONFIG | --plugin-config-file=PATH_TO_FILE + | --plugin-config-uri=PLUGIN_CONFIG_URI] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new WasmPluginVersion resource. + +EXAMPLES + To create a WasmPluginVersion called my-plugin-version, run: + + $ gcloud beta service-extensions wasm-plugin-versions create \ + my-plugin-version --wasm-plugin=my-plugin \ + --image=...-docker.pkg.dev/my-project/repository/container:tag + +POSITIONAL ARGUMENTS + WasmPluginVersion resource - The ID of the WasmPluginVersion resource to + create. 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 wasm_plugin_version on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + WASM_PLUGIN_VERSION + ID of the WasmPluginVersion or fully qualified identifier for the + WasmPluginVersion. + + To set the wasm_plugin_version attribute: + ▸ provide the argument wasm_plugin_version 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 ID. + + To set the location attribute: + ▸ provide the argument wasm_plugin_version on the command line with + a fully specified name; + ▸ provide the argument --location on the command line; + ▸ use global location. + + --wasm-plugin=WASM_PLUGIN + The ID of the WasmPlugin. + + To set the wasm-plugin attribute: + ▸ provide the argument wasm_plugin_version on the command line with + a fully specified name; + ▸ provide the argument --wasm-plugin on the command line. + +REQUIRED FLAGS + --image=IMAGE + URI of the container image containing the plugin's Wasm module, stored + in the Artifact Registry. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A human-readable description of the resource. + + --labels=[KEY=VALUE,...] + List of KEY=VALUE labels to attach to this resource. + + Configuration for the plugin, provided at runtime by the on_configure + function (Rust Proxy-Wasm SDK) or the onConfigure method (C++ Proxy-Wasm + SDK). + + At most one of these can be specified: + + --plugin-config=PLUGIN_CONFIG + Plugin configuration in the textual format. + + --plugin-config-file=PATH_TO_FILE + Path to a file containing the plugin configuration. Use a full or + relative path to a local file containing the value of + plugin_config_file. + + --plugin-config-uri=PLUGIN_CONFIG_URI + URI of the container image containing the plugin's configuration, + stored in the Artifact Registry. + +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 networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha service-extensions wasm-plugin-versions create + diff --git a/gcloud/beta/service-extensions/wasm-plugin-versions/delete b/gcloud/beta/service-extensions/wasm-plugin-versions/delete new file mode 100644 index 000000000..e037885cc --- /dev/null +++ b/gcloud/beta/service-extensions/wasm-plugin-versions/delete @@ -0,0 +1,82 @@ +NAME + gcloud beta service-extensions wasm-plugin-versions delete - delete a + WasmPluginVersion resource + +SYNOPSIS + gcloud beta service-extensions wasm-plugin-versions delete + (WASM_PLUGIN_VERSION : --location=LOCATION --wasm-plugin=WASM_PLUGIN) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a WasmPluginVersion resource. + +EXAMPLES + To delete a WasmPluginVersion called 'my-plugin-version', run: + + $ gcloud beta service-extensions wasm-plugin-versions delete \ + my-plugin-version + +POSITIONAL ARGUMENTS + WasmPluginVersion resource - The WasmPluginVersion resource to delete. 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 wasm_plugin_version on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + WASM_PLUGIN_VERSION + ID of the WasmPluginVersion or fully qualified identifier for the + WasmPluginVersion. + + To set the wasm_plugin_version attribute: + ▸ provide the argument wasm_plugin_version 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 ID. + + To set the location attribute: + ▸ provide the argument wasm_plugin_version on the command line with + a fully specified name; + ▸ provide the argument --location on the command line; + ▸ use global location. + + --wasm-plugin=WASM_PLUGIN + The ID of the WasmPlugin. + + To set the wasm-plugin attribute: + ▸ provide the argument wasm_plugin_version on the command line with + a fully specified name; + ▸ provide the argument --wasm-plugin on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha service-extensions wasm-plugin-versions delete + diff --git a/gcloud/beta/service-extensions/wasm-plugin-versions/describe b/gcloud/beta/service-extensions/wasm-plugin-versions/describe new file mode 100644 index 000000000..d6a814717 --- /dev/null +++ b/gcloud/beta/service-extensions/wasm-plugin-versions/describe @@ -0,0 +1,77 @@ +NAME + gcloud beta service-extensions wasm-plugin-versions describe - show details + about a WasmPluginVersion resource + +SYNOPSIS + gcloud beta service-extensions wasm-plugin-versions describe + (WASM_PLUGIN_VERSION : --location=LOCATION --wasm-plugin=WASM_PLUGIN) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show details about a WasmPluginVersion resource. + +EXAMPLES + To show details about a WasmPluginVersion, run: + + $ gcloud beta service-extensions wasm-plugin-versions describe \ + my-plugin-version + +POSITIONAL ARGUMENTS + WasmPluginVersion resource - The WasmPluginVersion resource that you want + to describe. 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 wasm_plugin_version on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + WASM_PLUGIN_VERSION + ID of the WasmPluginVersion or fully qualified identifier for the + WasmPluginVersion. + + To set the wasm_plugin_version attribute: + ▸ provide the argument wasm_plugin_version 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 ID. + + To set the location attribute: + ▸ provide the argument wasm_plugin_version on the command line with + a fully specified name; + ▸ provide the argument --location on the command line; + ▸ use global location. + + --wasm-plugin=WASM_PLUGIN + The ID of the WasmPlugin. + + To set the wasm-plugin attribute: + ▸ provide the argument wasm_plugin_version on the command line with + a fully specified name; + ▸ provide the argument --wasm-plugin 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. + +API REFERENCE + This command uses the networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha service-extensions wasm-plugin-versions describe + diff --git a/gcloud/beta/service-extensions/wasm-plugin-versions/help b/gcloud/beta/service-extensions/wasm-plugin-versions/help new file mode 100644 index 000000000..38e871e84 --- /dev/null +++ b/gcloud/beta/service-extensions/wasm-plugin-versions/help @@ -0,0 +1,37 @@ +NAME + gcloud beta service-extensions wasm-plugin-versions - interact with and + manage Service Extensions WasmPluginVersions + +SYNOPSIS + gcloud beta service-extensions wasm-plugin-versions COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Interact with and manage Service Extensions WasmPluginVersions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a WasmPluginVersion resource. + + delete + (BETA) Delete a WasmPluginVersion resource. + + describe + (BETA) Show details about a WasmPluginVersion resource. + + list + (BETA) List all WasmPluginVersion resources for a WasmPlugin. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha service-extensions wasm-plugin-versions + diff --git a/gcloud/resource-settings/list-values b/gcloud/beta/service-extensions/wasm-plugin-versions/list similarity index 50% rename from gcloud/resource-settings/list-values rename to gcloud/beta/service-extensions/wasm-plugin-versions/list index 3f9c806e3..0d031b562 100644 --- a/gcloud/resource-settings/list-values +++ b/gcloud/beta/service-extensions/wasm-plugin-versions/list @@ -1,42 +1,54 @@ NAME - gcloud resource-settings list-values - list the values for any configured - resource settings + gcloud beta service-extensions wasm-plugin-versions list - list all + WasmPluginVersion resources for a WasmPlugin SYNOPSIS - gcloud resource-settings list-values - (--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID) [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud beta service-extensions wasm-plugin-versions list + (--wasm-plugin=WASM_PLUGIN : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) List the values for any configured resource settings. - - Resource Settings is deprecated. As of November 7, 2023, no organizations - will be onboarded for any of the enabled settings, and the service will be - shut down on October 1, 2024. - - List the values for any configured resource settings. + (BETA) List WasmPluginVersion resources. EXAMPLES - To list all setting values on the project foo-project, run: + To list existing WasmPluginVersion resources, run: - $ gcloud resource-settings list-values --project=foo-project + $ gcloud beta service-extensions wasm-plugin-versions list \ + --wasm-plugin=WASM_PLUGIN REQUIRED FLAGS - Resource that is associated with the resource settings. + WasmPlugin resource - The parent WasmPlugin. 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. - Exactly one of these must be specified: + To set the project attribute: + ◆ provide the argument --wasm-plugin on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. - --folder=FOLDER_ID - Folder ID. + This must be specified. - --organization=ORGANIZATION_ID - Organization ID. + --wasm-plugin=WASM_PLUGIN + ID of the WasmPlugin or fully qualified identifier for the + WasmPlugin. - --project=PROJECT_ID - Project ID. Overrides the default core/project property value for - this command invocation. + To set the wasm-plugin attribute: + ▸ provide the argument --wasm-plugin on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location ID. + + To set the location attribute: + ▸ provide the argument --wasm-plugin on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ use global location. LIST COMMAND FLAGS --filter=EXPRESSION @@ -78,8 +90,13 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + NOTES - This variant is also available: + This command is currently in beta and might change without notice. This + variant is also available: - $ gcloud alpha resource-settings list-values + $ gcloud alpha service-extensions wasm-plugin-versions list diff --git a/gcloud/beta/service-extensions/wasm-plugins/create b/gcloud/beta/service-extensions/wasm-plugins/create new file mode 100644 index 000000000..0acd20279 --- /dev/null +++ b/gcloud/beta/service-extensions/wasm-plugins/create @@ -0,0 +1,137 @@ +NAME + gcloud beta service-extensions wasm-plugins create - create a WasmPlugin + resource + +SYNOPSIS + gcloud beta service-extensions wasm-plugins create + (WASM_PLUGIN : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--log-config=[LOG_CONFIG,...]] + [--image=IMAGE + --main-version=MAIN_VERSION --plugin-config=PLUGIN_CONFIG + | --plugin-config-file=PATH_TO_FILE + | --plugin-config-uri=PLUGIN_CONFIG_URI] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new WasmPlugin resource. + +EXAMPLES + To create a WasmPlugin called my-plugin, run: + + $ gcloud beta service-extensions wasm-plugins create my-plugin + + To create a WasmPlugin called my-plugin, together with a new version called + v1, and set it as main, run: + + $ gcloud beta service-extensions wasm-plugins create my-plugin \ + --main-version=v1 \ + --image=...-docker.pkg.dev/my-project/repository/container:tag + +POSITIONAL ARGUMENTS + WasmPlugin resource - The ID of the WasmPlugin resource to create. 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 wasm_plugin on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + WASM_PLUGIN + ID of the WasmPlugin or fully qualified identifier for the + WasmPlugin. + + To set the wasm_plugin attribute: + ▸ provide the argument wasm_plugin 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 ID. + + To set the location attribute: + ▸ provide the argument wasm_plugin on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ use global location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A human-readable description of the resource. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + --log-config=[LOG_CONFIG,...] + Logging options for the activity performed by this plugin. The + following options can be set: + ◆ enable: whether to enable logging. If log-config flag is set, + enable option is required. + + ◆ sample-rate: configures the sampling rate of activity logs, where + 1.0 means all logged activity is reported and 0.0 means no activity + is reported. The default value is 1.0, and the value of the field + must be in range 0 to 1 (inclusive). + + ◆ min-log-level: specifies the lowest level of the logs that should + be exported to Cloud Logging. The default value is INFO. + + Example usage: + --log-config=enable=True,sample-rate=0.5,min-log-level=INFO + --log_config=enable=False + + --image=IMAGE + URI of the container image containing the plugin's Wasm module, stored + in the Artifact Registry. + + --main-version=MAIN_VERSION + ID of the WasmPluginVersion resource that will be created for that + WasmPlugin and that will be set as the current main version. + + Configuration for the plugin, provided at runtime by the on_configure + function (Rust Proxy-Wasm SDK) or the onConfigure method (C++ Proxy-Wasm + SDK). + + At most one of these can be specified: + + --plugin-config=PLUGIN_CONFIG + Plugin runtime configuration in the textual format. + + --plugin-config-file=PATH_TO_FILE + Path to a local file containing the plugin runtime configuration. + + Use a full or relative path to a local file containing the value of + plugin_config_file. + + --plugin-config-uri=PLUGIN_CONFIG_URI + URI of the container image containing the plugin's runtime + configuration, stored in the Artifact Registry. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha service-extensions wasm-plugins create + diff --git a/gcloud/beta/service-extensions/wasm-plugins/delete b/gcloud/beta/service-extensions/wasm-plugins/delete new file mode 100644 index 000000000..943726e8c --- /dev/null +++ b/gcloud/beta/service-extensions/wasm-plugins/delete @@ -0,0 +1,72 @@ +NAME + gcloud beta service-extensions wasm-plugins delete - delete a WasmPlugin + resource + +SYNOPSIS + gcloud beta service-extensions wasm-plugins delete + (WASM_PLUGIN : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a WasmPlugin resource. + +EXAMPLES + To delete a WasmPlugin called my-plugin, run: + + $ gcloud beta service-extensions wasm-plugins delete my-plugin + +POSITIONAL ARGUMENTS + WasmPlugin resource - The WasmPlugin resource to delete. 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 wasm_plugin on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + WASM_PLUGIN + ID of the WasmPlugin or fully qualified identifier for the + WasmPlugin. + + To set the wasm_plugin attribute: + ▸ provide the argument wasm_plugin 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 ID. + + To set the location attribute: + ▸ provide the argument wasm_plugin on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ use global location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha service-extensions wasm-plugins delete + diff --git a/gcloud/beta/service-extensions/wasm-plugins/describe b/gcloud/beta/service-extensions/wasm-plugins/describe new file mode 100644 index 000000000..0ef668b54 --- /dev/null +++ b/gcloud/beta/service-extensions/wasm-plugins/describe @@ -0,0 +1,67 @@ +NAME + gcloud beta service-extensions wasm-plugins describe - show details about a + WasmPlugin resource + +SYNOPSIS + gcloud beta service-extensions wasm-plugins describe + (WASM_PLUGIN : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show details about a WasmPlugin resource. + +EXAMPLES + To show details about a WasmPlugin, run: + + $ gcloud beta service-extensions wasm-plugins describe my-plugin + +POSITIONAL ARGUMENTS + WasmPlugin resource - The WasmPlugin resource that you want to describe. + 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 wasm_plugin on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + WASM_PLUGIN + ID of the WasmPlugin or fully qualified identifier for the + WasmPlugin. + + To set the wasm_plugin attribute: + ▸ provide the argument wasm_plugin 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 ID. + + To set the location attribute: + ▸ provide the argument wasm_plugin on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ use global location. + +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 networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha service-extensions wasm-plugins describe + diff --git a/gcloud/beta/service-extensions/wasm-plugins/help b/gcloud/beta/service-extensions/wasm-plugins/help new file mode 100644 index 000000000..0f83daf28 --- /dev/null +++ b/gcloud/beta/service-extensions/wasm-plugins/help @@ -0,0 +1,39 @@ +NAME + gcloud beta service-extensions wasm-plugins - interact with and manage + Service Extensions WasmPlugins + +SYNOPSIS + gcloud beta service-extensions wasm-plugins COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Interact with and manage Service Extensions WasmPlugins. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a WasmPlugin resource. + + delete + (BETA) Delete a WasmPlugin resource. + + describe + (BETA) Show details about a WasmPlugin resource. + + list + (BETA) List all WasmPlugin resources. + + update + (BETA) Update a WasmPlugin resource. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha service-extensions wasm-plugins + diff --git a/gcloud/alpha/resource-settings/list b/gcloud/beta/service-extensions/wasm-plugins/list similarity index 57% rename from gcloud/alpha/resource-settings/list rename to gcloud/beta/service-extensions/wasm-plugins/list index 77c52ac1e..5bbcc07bf 100644 --- a/gcloud/alpha/resource-settings/list +++ b/gcloud/beta/service-extensions/wasm-plugins/list @@ -1,41 +1,38 @@ NAME - gcloud alpha resource-settings list - list all available resource settings + gcloud beta service-extensions wasm-plugins list - list all WasmPlugin + resources SYNOPSIS - gcloud alpha resource-settings list - (--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID) [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud beta service-extensions wasm-plugins list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) (DEPRECATED) List all available resource settings. - - Resource Settings is deprecated. As of November 7, 2023, no organizations - will be onboarded for any of the enabled settings, and the service will be - shut down on October 1, 2024. - - List all available resource settings. + (BETA) List WasmPlugin resources. EXAMPLES - To list all available resource settings with the project foo-project, run: + To list existing WasmPlugin resources, run: - $ gcloud alpha resource-settings list --project=foo-project + $ gcloud beta service-extensions wasm-plugins list -REQUIRED FLAGS - Resource that is associated with the resource settings. +FLAGS + Location resource - The parent location. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. - Exactly one of these must be specified: + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ use global location with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. - --folder=FOLDER_ID - Folder ID. + --location=LOCATION + ID of the location or fully qualified identifier for the location. - --organization=ORGANIZATION_ID - Organization ID. - - --project=PROJECT_ID - Project ID. Overrides the default core/project property value for - this command invocation. + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ use global location. LIST COMMAND FLAGS --filter=EXPRESSION @@ -77,11 +74,13 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + 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: + This command is currently in beta and might change without notice. This + variant is also available: - $ gcloud resource-settings list + $ gcloud alpha service-extensions wasm-plugins list diff --git a/gcloud/beta/service-extensions/wasm-plugins/update b/gcloud/beta/service-extensions/wasm-plugins/update new file mode 100644 index 000000000..fbf1b7132 --- /dev/null +++ b/gcloud/beta/service-extensions/wasm-plugins/update @@ -0,0 +1,160 @@ +NAME + gcloud beta service-extensions wasm-plugins update - update a WasmPlugin + resource + +SYNOPSIS + gcloud beta service-extensions wasm-plugins update + (WASM_PLUGIN : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--log-config=[LOG_CONFIG,...]] + [--image=IMAGE + --main-version=MAIN_VERSION --plugin-config=PLUGIN_CONFIG + | --plugin-config-file=PATH_TO_FILE + | --plugin-config-uri=PLUGIN_CONFIG_URI] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an existing WasmPlugin resource and optionally create a + WasmPluginVersion resource and set it as the main (serving) one. + + If --image is not specified: + ▪ the method only updates the WasmPlugin resource without creating a + WasmPluginVersion. + ▪ the --plugin-config*** flags are disallowed. + ▪ if --main-version is set, then the referenced WasmPluginVersion must + already exist and it is set as the main (serving) one. + + If --image is specified: + ▪ the --main-version flag must also be specified. + ▪ the method updates the WasmPlugin resource and creates a new + WasmPluginVersion with --main-version name and sets it as the main + (serving) one. + ▪ the --plugin-config*** flags are allowed. + ▪ the --async flag is disallowed. + +EXAMPLES + To update a WasmPlugin called my-plugin, run: + + $ gcloud beta service-extensions wasm-plugins update my-plugin \ + --main-version=new-version --description="A new description." \ + --labels=label1=value1 + + To update a WasmPlugin called my-plugin and also create a new version + called v1 and set it as main: + + $ gcloud beta service-extensions wasm-plugins update my-plugin \ + --main-version=v1 --description="A new description." \ + --labels=label1=value1 \ + --image=...-docker.pkg.dev/my-project/repository/container:tag + +POSITIONAL ARGUMENTS + WasmPlugin resource - The ID of the WasmPlugin to update. 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 wasm_plugin on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + WASM_PLUGIN + ID of the WasmPlugin or fully qualified identifier for the + WasmPlugin. + + To set the wasm_plugin attribute: + ▸ provide the argument wasm_plugin 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 ID. + + To set the location attribute: + ▸ provide the argument wasm_plugin on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ use global location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A human-readable description of the resource. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + --log-config=[LOG_CONFIG,...] + Logging options for the activity performed by this plugin. The + following options can be set: + ◆ enable: whether to enable logging. If log-config flag is set, + enable option is required. + + ◆ sample-rate: configures the sampling rate of activity logs, where + 1.0 means all logged activity is reported and 0.0 means no activity + is reported. The default value is 1.0, and the value of the field + must be in range 0 to 1 (inclusive). + + ◆ min-log-level: specifies the lowest level of the logs that should + be exported to Cloud Logging. The default value is INFO. + + Example usage: + --log-config=enable=True,sample-rate=0.5,min-log-level=INFO + --log_config=enable=False + + --image=IMAGE + URI of the container image containing the plugin's Wasm module, stored + in the Artifact Registry. + + --main-version=MAIN_VERSION + The ID of the WasmPluginVersion that should be the currently serving + one. The version referred to must be a child of this WasmPlugin. + + If the --image flag was also provided, the WasmPluginVersion will be + created for that WasmPlugin and will be set as the current main + version. + + Configuration for the plugin, provided at runtime by the on_configure + function (Rust Proxy-Wasm SDK) or the onConfigure method (C++ Proxy-Wasm + SDK). + + At most one of these can be specified: + + --plugin-config=PLUGIN_CONFIG + Plugin runtime configuration in the textual format. + + --plugin-config-file=PATH_TO_FILE + Path to a local file containing the plugin runtime configuration. + + Use a full or relative path to a local file containing the value of + plugin_config_file. + + --plugin-config-uri=PLUGIN_CONFIG_URI + URI of the container image containing the plugin's runtime + configuration, stored in the Artifact Registry. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha service-extensions wasm-plugins update + diff --git a/gcloud/beta/spanner/instances/get-locations b/gcloud/beta/spanner/instances/get-locations new file mode 100644 index 000000000..3cfcd3416 --- /dev/null +++ b/gcloud/beta/spanner/instances/get-locations @@ -0,0 +1,41 @@ +NAME + gcloud beta spanner instances get-locations - get the location of every + replica in a Cloud Spanner instance + +SYNOPSIS + gcloud beta spanner instances get-locations INSTANCE [--verbose] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get the location of every replica in a Cloud Spanner instance. + +EXAMPLES + To get the location of every replica in a Cloud Spanner instance in this + project, run: + + $ gcloud beta spanner instances get-locations my-instance-id + +POSITIONAL ARGUMENTS + INSTANCE + Cloud Spanner instance ID. + +FLAGS + --verbose + Indicates that both regions and types of replicas be returned. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud spanner instances get-locations + + $ gcloud alpha spanner instances get-locations + diff --git a/gcloud/beta/spanner/instances/help b/gcloud/beta/spanner/instances/help index 929265bb1..2ff941c6e 100644 --- a/gcloud/beta/spanner/instances/help +++ b/gcloud/beta/spanner/instances/help @@ -30,6 +30,9 @@ COMMANDS get-iam-policy (BETA) Get the IAM policy for a Cloud Spanner instance. + get-locations + (BETA) Get the location of every replica in a Cloud Spanner instance. + list (BETA) List the Cloud Spanner instances in this project. diff --git a/gcloud/beta/sql/export/bak b/gcloud/beta/sql/export/bak index 40c81f447..cf80296bd 100644 --- a/gcloud/beta/sql/export/bak +++ b/gcloud/beta/sql/export/bak @@ -6,6 +6,8 @@ SYNOPSIS gcloud beta sql export bak INSTANCE URI --database=DATABASE,[DATABASE,...], -d DATABASE,[DATABASE,...] [--async] [--bak-type=BAK_TYPE; default="FULL"] [--differential-base] + [--export-log-end-time=EXPORT_LOG_END_TIME] + [--export-log-start-time=EXPORT_LOG_START_TIME] [--stripe_count=STRIPE_COUNT] [--[no-]striped] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -41,12 +43,24 @@ OPTIONAL FLAGS --bak-type=BAK_TYPE; default="FULL" Type of bak file that will be exported, FULL or DIFF. SQL Server only. - BAK_TYPE must be one of: FULL, DIFF. + BAK_TYPE must be one of: FULL, DIFF, TLOG. --differential-base Whether the bak file export can be used as differential base for future differential backup. SQL Server only + --export-log-end-time=EXPORT_LOG_END_TIME + Optional flag. The end time of the transaction log files that are + included in the export file. Use this flag to export transaction logs + for Cloud SQL for SQL Server only. Format: YYYY-MM-DDTHH:MM:SSZ, UTC + timezone only. + + --export-log-start-time=EXPORT_LOG_START_TIME + Optional flag. The start time of the transaction log files that are + included in the export file. Use this flag to export transaction logs + for Cloud SQL for SQL Server only. Format: YYYY-MM-DDTHH:MM:SSZ, UTC + timezone only. + --stripe_count=STRIPE_COUNT Specifies the number of stripes to use for SQL Server exports. diff --git a/gcloud/beta/workstations/configs/create b/gcloud/beta/workstations/configs/create index bc832a315..d13d6597f 100644 --- a/gcloud/beta/workstations/configs/create +++ b/gcloud/beta/workstations/configs/create @@ -20,6 +20,7 @@ SYNOPSIS [--enable-ssh-to-vm] [--ephemeral-directory=[PROPERTY=VALUE,...]] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] + [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] [--network-tags=[NETWORK_TAGS,...]] [--pd-disk-size=PD_DISK_SIZE; default=200] [--pd-disk-type=PD_DISK_TYPE; default="pd-standard"] @@ -283,6 +284,13 @@ FLAGS machines that the workstations created under this configuration will run on. + --max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT + Maximum number of workstations under this configuration a user can have + workstations.workstation.use permission on. + + If not specified, defaults to 0, which indicates a user can have + unlimited number of workstations under this configuration. + --network-tags=[NETWORK_TAGS,...] Network tags to add to the Google Compute Engine machines backing the Workstations. diff --git a/gcloud/beta/workstations/configs/update b/gcloud/beta/workstations/configs/update index 4e90bff49..559c6629f 100644 --- a/gcloud/beta/workstations/configs/update +++ b/gcloud/beta/workstations/configs/update @@ -15,9 +15,10 @@ SYNOPSIS [--disable-public-ip-addresses] [--enable-audit-agent] [--enable-confidential-compute] [--enable-nested-virtualization] [--idle-timeout=IDLE_TIMEOUT] [--labels=[LABELS,...]] - [--machine-type=MACHINE_TYPE] [--network-tags=[NETWORK_TAGS,...]] - [--pool-size=POOL_SIZE] [--running-timeout=RUNNING_TIMEOUT] - [--service-account=SERVICE_ACCOUNT] + [--machine-type=MACHINE_TYPE] + [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] + [--network-tags=[NETWORK_TAGS,...]] [--pool-size=POOL_SIZE] + [--running-timeout=RUNNING_TIMEOUT] [--service-account=SERVICE_ACCOUNT] [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--vm-tags=[VM_TAGS,...]] @@ -244,6 +245,13 @@ FLAGS machines that the workstations created under this configuration will run on. + --max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT + Maximum number of workstations under this configuration a user can have + workstations.workstation.use permission on. + + If not specified, defaults to 0, which indicates a user can have + unlimited number of workstations under this configuration. + --network-tags=[NETWORK_TAGS,...] Network tags to add to the Google Compute Engine machines backing the Workstations. diff --git a/gcloud/bigtable/backups/create b/gcloud/bigtable/backups/create index 1c78efab9..ead23eb13 100644 --- a/gcloud/bigtable/backups/create +++ b/gcloud/bigtable/backups/create @@ -6,7 +6,8 @@ SYNOPSIS (BACKUP : --cluster=CLUSTER --instance=INSTANCE) --table=TABLE (--expiration-date=EXPIRATION_DATE | --retention-period=RETENTION_PERIOD) [--async] - [GCLOUD_WIDE_FLAG ...] + [--backup-type=BACKUP_TYPE] + [--hot-to-standard-time=HOT_TO_STANDARD_TIME] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Creates a backup of a Cloud Bigtable table. @@ -27,6 +28,31 @@ EXAMPLES --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ --table=TABLE_NAME --retention-period=2w + To create a hot backup 'BACKUP_NAME' from table 'TABLE_NAME' which expires + in 2 weeks from now, run: + + $ gcloud bigtable backups create BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --retention-period=2w --backup-type=HOT + + To create a hot backup 'BACKUP_NAME' from table 'TABLE_NAME' which will be + converted to a standard backup at '2019-03-31T10:49:41Z' and expires in 2 + weeks from now, run: + + $ gcloud bigtable backups create BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --retention-period=2w --backup-type=HOT \ + --hot-to-standard-time=2019-03-31T10:49:41Z + + To create a hot backup 'BACKUP_NAME' from table 'TABLE_NAME' which will be + converted to a standard backup in 1 week from now and expires in 2 weeks + from now, run: + + $ gcloud bigtable backups create BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --retention-period=2w --backup-type=HOT \ + --hot-to-standard-time=+P1w + POSITIONAL ARGUMENTS Backup resource - The Cloud Bigtable backup to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -73,20 +99,38 @@ REQUIRED FLAGS Exactly one of these must be specified: --expiration-date=EXPIRATION_DATE - Absolute expiration time of the backup; must be at least 6 hours and - at most 90 days from the time the request is received. See $ gcloud - topic datetimes for information on date/time formats. + Absolute expiration time of the backup. From the time the request is + received, must be: + ▸ At least 6 hours in the future + ▸ At most 90 days in the future + + See $ gcloud topic datetimes for information on date/time formats. --retention-period=RETENTION_PERIOD - Retention period of the backup relative from now; must be at least 6 - hours and at most 90 days. See $ gcloud topic datetimes for - information on duration formats. + Retention period of the backup relative from now; must be: + ▸ At least 6 hours + ▸ At most 90 days + + See $ gcloud topic datetimes for information on duration formats. OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to complete. + --backup-type=BACKUP_TYPE + Type of the backup; whether the backup is a standard backup or a hot + backup. BACKUP_TYPE must be one of: backup-type-unspecified, hot, + standard. + + --hot-to-standard-time=HOT_TO_STANDARD_TIME + Time at which a hot backup will be converted to a standard backup + relative from now; must be: + ◆ At least 24 hours + + Only applies for hot backups. See $ gcloud topic datetimes for + information on date/time formats. + 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/bigtable/backups/update b/gcloud/bigtable/backups/update index 2fe4e27b3..14afbef56 100644 --- a/gcloud/bigtable/backups/update +++ b/gcloud/bigtable/backups/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud bigtable backups update (BACKUP : --cluster=CLUSTER --instance=INSTANCE) + [--hot-to-standard-time=HOT_TO_STANDARD_TIME] [--expiration-date=EXPIRATION_DATE | --retention-period=RETENTION_PERIOD] [GCLOUD_WIDE_FLAG ...] @@ -19,6 +20,26 @@ EXAMPLES --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ --retention-period=7d + To update the hot-to-standard time of backup 'BACKUP_NAME' to + '2019-03-31T10:49:41Z', run: + + $ gcloud bigtable backups update BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --hot-to-standard-time=2019-03-31T10:49:41Z + + To update the hot-to-standard time of backup 'BACKUP_NAME' to 7 days from + now, run: + + $ gcloud bigtable backups update BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --hot-to-standard-time=+P7d + + To clear the hot-to-standard time of backup 'BACKUP_NAME', run: + + $ gcloud bigtable backups update BACKUP_NAME \ + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --hot-to-standard-time='' + POSITIONAL ARGUMENTS Backup resource - Cloud Bigtable backup to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -59,6 +80,12 @@ POSITIONAL ARGUMENTS ▸ provide the argument --instance on the command line. FLAGS + --hot-to-standard-time=HOT_TO_STANDARD_TIME + Time at which a hot backup will be converted to a standard backup; must + be at least 24 hours from backup creation time. Only applies for hot + backups. See $ gcloud topic datetimes for information on date/time + formats. See $ gcloud bigtable backups describe for creation time. + At most one of these can be specified: --expiration-date=EXPIRATION_DATE diff --git a/gcloud/builds/submit b/gcloud/builds/submit index e59d1bdb1..503efdc17 100644 --- a/gcloud/builds/submit +++ b/gcloud/builds/submit @@ -99,7 +99,8 @@ FLAGS --default-buckets-behavior=DEFAULT_BUCKETS_BEHAVIOR How default buckets are setup. DEFAULT_BUCKETS_BEHAVIOR must be one of: - default-logs-bucket-behavior-unspecified, regional-user-owned-bucket. + default-logs-bucket-behavior-unspecified, legacy-bucket, + regional-user-owned-bucket. --dir=DIR Directory, relative to the source root, in which to run the build. This diff --git a/gcloud/compute/backend-services/create b/gcloud/compute/backend-services/create index 4fc8c8563..ff3d946f2 100644 --- a/gcloud/compute/backend-services/create +++ b/gcloud/compute/backend-services/create @@ -623,6 +623,15 @@ FLAGS the backend service's consistent hash specifies the HTTP cookie. NONE Session affinity is disabled. + STRONG_COOKIE_AFFINITY + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or + EXTERNAL_MANAGED) Strong cookie-based affinity, based on an HTTP + cookie named in the --affinity-cookie-name flag (with the optional + --affinity-cookie-ttl flag). Connections bearing the same cookie + will be served by the same backend VM while that VM remains + healthy, as long as the cookie has not expired. If the + --affinity-cookie-ttl flag is set to 0, the cookie will be treated + as a session cookie. --signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE The amount of time up to which the response to a signed URL request diff --git a/gcloud/compute/backend-services/update b/gcloud/compute/backend-services/update index a4aa09968..d78efa4a4 100644 --- a/gcloud/compute/backend-services/update +++ b/gcloud/compute/backend-services/update @@ -422,6 +422,15 @@ FLAGS the backend service's consistent hash specifies the HTTP cookie. NONE Session affinity is disabled. + STRONG_COOKIE_AFFINITY + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or + EXTERNAL_MANAGED) Strong cookie-based affinity, based on an HTTP + cookie named in the --affinity-cookie-name flag (with the optional + --affinity-cookie-ttl flag). Connections bearing the same cookie + will be served by the same backend VM while that VM remains + healthy, as long as the cookie has not expired. If the + --affinity-cookie-ttl flag is set to 0, the cookie will be treated + as a session cookie. --signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE The amount of time up to which the response to a signed URL request diff --git a/gcloud/compute/instant-snapshots/create b/gcloud/compute/instant-snapshots/create index 82b847511..ed011c4c0 100644 --- a/gcloud/compute/instant-snapshots/create +++ b/gcloud/compute/instant-snapshots/create @@ -8,9 +8,8 @@ SYNOPSIS [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - gcloud compute instant-snapshots create creates an instant snapshot of - persistent disk. Instant snapshots are useful for backing up persistent - disk data. + gcloud compute instant-snapshots create creates an instant snapshot of a + disk. Instant snapshots are useful for backing up the disk data. EXAMPLES To create an instant snapshot 'my-instant-snap' from a disk 'my-disk' in diff --git a/gcloud/compute/interconnects/attachments/delete b/gcloud/compute/interconnects/attachments/delete index 1516a92d9..03b405f61 100644 --- a/gcloud/compute/interconnects/attachments/delete +++ b/gcloud/compute/interconnects/attachments/delete @@ -1,5 +1,6 @@ NAME - gcloud compute interconnects attachments delete - delete interconnects + gcloud compute interconnects attachments delete - delete Compute Engine + interconnect attachments SYNOPSIS gcloud compute interconnects attachments delete NAME [NAME ...] @@ -7,7 +8,7 @@ SYNOPSIS DESCRIPTION gcloud compute interconnects attachments delete deletes Compute Engine - interconnect attachment. + interconnect attachments. POSITIONAL ARGUMENTS NAME [NAME ...] diff --git a/gcloud/compute/interconnects/attachments/help b/gcloud/compute/interconnects/attachments/help index ce75d2686..e64b6bd7a 100644 --- a/gcloud/compute/interconnects/attachments/help +++ b/gcloud/compute/interconnects/attachments/help @@ -27,7 +27,7 @@ COMMANDS COMMAND is one of the following: delete - Delete interconnects. + Delete Compute Engine interconnect attachments. describe Describe a Compute Engine interconnect attachment. diff --git a/gcloud/compute/network-endpoint-groups/create b/gcloud/compute/network-endpoint-groups/create index cc6e3950b..3712aca7b 100644 --- a/gcloud/compute/network-endpoint-groups/create +++ b/gcloud/compute/network-endpoint-groups/create @@ -53,7 +53,7 @@ FLAGS This is only supported for NEGs with endpoint type gce-vm-ip-port, non-gcp-private-ip-port, gce-vm-ip, private-service-connect, - internet-ip-port, internet-fqdn-port, or gce-vm-ip-portmap. + internet-ip-port, or internet-fqdn-port. For Private Service Connect NEGs, you can optionally specify --network and --subnet if --psc-target-service points to a published service. If @@ -108,15 +108,9 @@ FLAGS optional. If unspecified, the primary NIC address is used. A port must not be specified. - gce-vm-ip-portmap - Endpoint IP address must be a primary IP of a VM's network - interface in Compute Engine. The --default-port must be specified - or every network endpoint in the network endpoint group must have a - port specified. - NETWORK_ENDPOINT_TYPE must be one of: gce-vm-ip-port, internet-ip-port, internet-fqdn-port, non-gcp-private-ip-port, - serverless, gce-vm-ip, private-service-connect, gce-vm-ip-portmap. + serverless, gce-vm-ip, private-service-connect. --producer-port=PRODUCER_PORT The producer port to use when a consumer PSC NEG connects to a @@ -140,9 +134,9 @@ FLAGS region where the network endpoint group is created. This is only supported for NEGs with endpoint type gce-vm-ip-port, - gce-vm-ip, private-service-connect, or gce-vm-ip-portmap. For Private - Service Connect NEGs, you can optionally specify --network and --subnet - if --psc-target-service points to a published service. If + gce-vm-ip, or private-service-connect. For Private Service Connect + NEGs, you can optionally specify --network and --subnet if + --psc-target-service points to a published service. If --psc-target-service points to the regional service endpoint of a Google API, do not specify --network or --subnet. diff --git a/gcloud/compute/network-endpoint-groups/update b/gcloud/compute/network-endpoint-groups/update index c2dd43778..f12239fe0 100644 --- a/gcloud/compute/network-endpoint-groups/update +++ b/gcloud/compute/network-endpoint-groups/update @@ -4,10 +4,9 @@ NAME SYNOPSIS gcloud compute network-endpoint-groups update NAME - (--add-endpoint=[client-destination-port=CLIENT-DESTINATION-PORT], - [fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT] - | --remove-endpoint=[client-destination-port=CLIENT-DESTINATION-PORT], - [fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT]) + (--add-endpoint=[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT] + | --remove-endpoint=[fqdn=FQDN], + [instance=INSTANCE],[ip=IP],[port=PORT]) [--global | --region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -38,7 +37,7 @@ REQUIRED FLAGS Exactly one of these must be specified: - --add-endpoint=[client-destination-port=CLIENT-DESTINATION-PORT],[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT] + --add-endpoint=[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT] The network endpoint to add to the network endpoint group. Keys used depend on the endpoint type of the NEG. @@ -61,9 +60,6 @@ REQUIRED FLAGS *port* - Required endpoint port unless NEG default port is set. - *client-destination-port* - Required endpoint client destination port only for the port - mapping NEG. - internet-ip-port *ip* - Required IPv4 address of the endpoint to attach. Must be @@ -111,7 +107,7 @@ REQUIRED FLAGS IP address must be the VM's network interface address. If not specified, the primary NIC address is used. - --remove-endpoint=[client-destination-port=CLIENT-DESTINATION-PORT],[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT] + --remove-endpoint=[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT] The network endpoint to detach from the network endpoint group. Keys used depend on the endpoint type of the NEG. @@ -126,8 +122,6 @@ REQUIRED FLAGS *port* - Optional port of the network endpoint to detach. - *client-destination-port* - Optional client destination port, only for port mapping NEGs. - internet-ip-port *ip* - Required IPv4 address of the network endpoint to detach. diff --git a/gcloud/config/get b/gcloud/config/get index d04f3b410..2b57d3b9d 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -568,6 +568,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/config/help b/gcloud/config/help index 3fd0eb24f..416e33849 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -600,6 +600,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/config/list b/gcloud/config/list index c767ac63b..018eeda51 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -612,6 +612,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/config/set b/gcloud/config/set index 4c9bd3aa6..9cb4634ad 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -615,6 +615,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/config/unset b/gcloud/config/unset index e14f7d04a..d57cf97f8 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -576,6 +576,10 @@ AVAILABLE PROPERTIES transfer Overrides API endpoint for gcloud transfer command group. + transferappliance + Overrides API endpoint for gcloud transfer appliances command + group. Defaults to https://transferappliance.googleapis.com/ + vision Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ diff --git a/gcloud/container/attached/clusters/register b/gcloud/container/attached/clusters/register index fa3972995..c41261e28 100644 --- a/gcloud/container/attached/clusters/register +++ b/gcloud/container/attached/clusters/register @@ -12,7 +12,6 @@ SYNOPSIS [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE] [--description=DESCRIPTION] [--enable-managed-prometheus] [--logging=COMPONENT,[COMPONENT,...]] [--validate-only] - [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--proxy-secret-name=PROXY_SECRET_NAME --proxy-secret-namespace=PROXY_SECRET_NAMESPACE] [GCLOUD_WIDE_FLAG ...] @@ -180,17 +179,6 @@ OPTIONAL FLAGS --validate-only Validate the cluster to create, but don't actually perform it. - --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING - Sets the mode of the Kubernetes security posture API's workload - vulnerability scanning. To enable Advanced vulnerability insights mode - explicitly set the flag to - --workload-vulnerability-scanning=enterprise. - - To disable in an existing cluster, explicitly set the flag to - --workload-vulnerability-scanning=disabled. - - WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, enterprise. - Proxy config --proxy-secret-name=PROXY_SECRET_NAME diff --git a/gcloud/container/attached/clusters/update b/gcloud/container/attached/clusters/update index ead04313d..56d8b18cc 100644 --- a/gcloud/container/attached/clusters/update +++ b/gcloud/container/attached/clusters/update @@ -8,7 +8,6 @@ SYNOPSIS [--clear-description] [--description=DESCRIPTION] [--logging=COMPONENT,[COMPONENT,...]] [--platform-version=PLATFORM_VERSION] [--validate-only] - [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--admin-groups=[GROUP,...] | --clear-admin-groups] [--admin-users=[USER,...] | --clear-admin-users] [--disable-managed-prometheus | --enable-managed-prometheus] @@ -99,17 +98,6 @@ FLAGS --validate-only Validate the update of the cluster, but don't actually perform it. - --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING - Sets the mode of the Kubernetes security posture API's workload - vulnerability scanning. To enable Advanced vulnerability insights mode - explicitly set the flag to - --workload-vulnerability-scanning=enterprise. - - To disable in an existing cluster, explicitly set the flag to - --workload-vulnerability-scanning=disabled. - - WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, enterprise. - Admin groups At most one of these can be specified: diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 713d490d5..c1224800d 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -23,16 +23,19 @@ SYNOPSIS [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--disable-default-snat] [--disk-size=DISK_SIZE] - [--disk-type=DISK_TYPE] [--enable-autorepair] [--no-enable-autoupgrade] + [--disk-type=DISK_TYPE] + [--enable-authorized-networks-on-private-endpoint] + [--enable-autorepair] [--no-enable-autoupgrade] [--enable-cilium-clusterwide-network-policy] [--enable-cloud-logging] [--enable-cloud-monitoring] [--enable-cloud-run-alpha] [--enable-confidential-nodes] [--enable-confidential-storage] - [--enable-cost-allocation] [--enable-dataplane-v2] [--enable-fleet] - [--enable-fqdn-network-policy] [--enable-google-cloud-access] - [--enable-gvnic] [--enable-identity-service] [--enable-image-streaming] + [--enable-cost-allocation] [--enable-dataplane-v2] + [--enable-dns-access] [--enable-fleet] [--enable-fqdn-network-policy] + [--enable-google-cloud-access] [--enable-gvnic] + [--enable-identity-service] [--enable-image-streaming] [--enable-insecure-kubelet-readonly-port] - [--enable-intra-node-visibility] [--enable-ip-alias] - [--enable-kubernetes-alpha] + [--enable-intra-node-visibility] [--enable-ip-access] + [--enable-ip-alias] [--enable-kubernetes-alpha] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-l4-ilb-subsetting] [--enable-legacy-authorization] [--enable-managed-prometheus] [--enable-master-global-access] @@ -428,6 +431,10 @@ FLAGS DISK_TYPE must be one of: pd-standard, pd-ssd, pd-balanced, hyperdisk-balanced, hyperdisk-extreme, hyperdisk-throughput. + --enable-authorized-networks-on-private-endpoint + Enable enforcement of --master-authorized-networks CIDR ranges for + traffic reaching cluster's control plane via private IP. + --enable-autorepair Enable node autorepair feature for a cluster's default node pool(s). @@ -508,6 +515,11 @@ FLAGS Enables the new eBPF dataplane for GKE clusters that is required for network security, scalability and visibility features. + --enable-dns-access + Enable access to the cluster's control plane over DNS-based endpoint. + + DNS-based control plane access is recommended. + --enable-fleet Set cluster project as the fleet host project. This will register the cluster to the same project. To register the cluster to a fleet in a @@ -556,6 +568,10 @@ FLAGS Enabling it on an existing cluster causes the cluster master and the cluster nodes to restart, which might cause a disruption. + --enable-ip-access + Enable access to the cluster's control plane over private IP and public + IP if --enable-private-endpoint is not enabled. + --enable-ip-alias Enable use of alias IPs (https://cloud.google.com/compute/docs/alias-ip/) for Pod IPs. This diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 5bd1aede7..8cd01709b 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -15,9 +15,10 @@ SYNOPSIS [--containerd-config-from-file=PATH_TO_FILE] [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] + [--enable-authorized-networks-on-private-endpoint] [--enable-backup-restore] [--enable-cilium-clusterwide-network-policy] - [--enable-fleet] [--enable-google-cloud-access] - [--enable-kubernetes-unstable-apis=API,[API,...]] + [--enable-dns-access] [--enable-fleet] [--enable-google-cloud-access] + [--enable-ip-access] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] [--enable-ray-operator] [--enable-secret-manager] [--fleet-project=PROJECT_ID_OR_NUMBER] @@ -223,6 +224,10 @@ FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. + --enable-authorized-networks-on-private-endpoint + Enable enforcement of --master-authorized-networks CIDR ranges for + traffic reaching cluster's control plane via private IP. + --enable-backup-restore Enable the Backup for GKE add-on. This add-on is disabled by default. To learn more, see the Backup for GKE overview: @@ -232,6 +237,11 @@ FLAGS Enable Cilium Clusterwide Network Policies on the cluster. Disabled by default. + --enable-dns-access + Enable access to the cluster's control plane over DNS-based endpoint. + + DNS-based control plane access is recommended. + --enable-fleet Set cluster project as the fleet host project. This will register the cluster to the same project. To register the cluster to a fleet in a @@ -243,6 +253,10 @@ FLAGS Google Cloud can reach the public control plane endpoint of your cluster. + --enable-ip-access + Enable access to the cluster's control plane over private IP and public + IP if --enable-private-endpoint is not enabled. + --enable-kubernetes-unstable-apis=API,[API,...] Enable Kubernetes beta API features on this cluster. Beta APIs are not expected to be production ready and should be avoided in diff --git a/gcloud/container/clusters/get-credentials b/gcloud/container/clusters/get-credentials index d8aab5edf..27a60136e 100644 --- a/gcloud/container/clusters/get-credentials +++ b/gcloud/container/clusters/get-credentials @@ -3,7 +3,8 @@ NAME cluster SYNOPSIS - gcloud container clusters get-credentials NAME [--internal-ip] + gcloud container clusters get-credentials NAME [--dns-endpoint] + [--internal-ip] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...] @@ -49,6 +50,9 @@ POSITIONAL ARGUMENTS container/cluster property value for this command invocation. FLAGS + --dns-endpoint + Whether to use the DNS-based endpoint for the cluster address. + --internal-ip Whether to use the internal IP address of the cluster endpoint. diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 072cc3570..f9b2644cf 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -15,15 +15,13 @@ SYNOPSIS | --disable-workload-identity | --enable-autoscaling | --[no-]enable-cilium-clusterwide-network-policy | --enable-cost-allocation | --enable-fleet - | --enable-fqdn-network-policy | --enable-google-cloud-access - | --enable-identity-service | --enable-image-streaming - | --enable-insecure-kubelet-readonly-port + | --enable-fqdn-network-policy | --enable-identity-service + | --enable-image-streaming | --enable-insecure-kubelet-readonly-port | --enable-intra-node-visibility | --enable-kubernetes-unstable-apis=API,[API,...] | --enable-l4-ilb-subsetting | --enable-legacy-authorization - | --enable-master-authorized-networks | --enable-master-global-access | --enable-multi-networking | --enable-network-policy - | --enable-private-endpoint | --[no-]enable-ray-cluster-logging + | --enable-private-nodes | --[no-]enable-ray-cluster-logging | --[no-]enable-ray-cluster-monitoring | --enable-secret-manager | --enable-service-externalips | --enable-shielded-nodes | --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling @@ -70,6 +68,11 @@ SYNOPSIS | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics + | --enable-authorized-networks-on-private-endpoint + --enable-dns-access --enable-google-cloud-access --enable-ip-access + --enable-master-global-access --enable-private-endpoint + --enable-master-authorized-networks + --master-authorized-networks=NETWORK,[NETWORK,...] | [--enable-autoprovisioning : --autoprovisioning-config-file=PATH_TO_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE @@ -94,7 +97,6 @@ SYNOPSIS | --password=PASSWORD --enable-basic-auth | --username=USERNAME, -u USERNAME) [--async] [--cloud-run-config=[load-balancer-type=EXTERNAL,...]] - [--master-authorized-networks=NETWORK,[NETWORK,...]] [--node-pool=NODE_POOL] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [--location-policy=LOCATION_POLICY --max-nodes=MAX_NODES @@ -297,11 +299,6 @@ REQUIRED FLAGS Enable FQDN Network Policies on the cluster. FQDN Network Policies are disabled by default. - --enable-google-cloud-access - When you enable Google Cloud Access, any public IP addresses owned by - Google Cloud can reach the public control plane endpoint of your - cluster. - --enable-identity-service Enable Identity Service component on the cluster. @@ -347,26 +344,6 @@ REQUIRED FLAGS use RBAC permissions instead, create or update your cluster with the option --no-enable-legacy-authorization. - --enable-master-authorized-networks - Allow only specified set of CIDR blocks (specified by the - --master-authorized-networks flag) to connect to Kubernetes master - through HTTPS. Besides these blocks, the following have access as - well: - - 1) The private network the cluster connects to if - `--enable-private-nodes` is specified. - 2) Google Compute Engine Public IPs if `--enable-private-nodes` is not - specified. - - Use --no-enable-master-authorized-networks to disable. When disabled, - public internet (0.0.0.0/0) is allowed to connect to Kubernetes - master through HTTPS. - - --enable-master-global-access - Use with private clusters to allow access to the master's private - endpoint from any Google Cloud region or on-premises environment - regardless of the private cluster's region. - --enable-multi-networking Enables multi-networking on the cluster. Multi-networking is disabled by default. @@ -377,9 +354,20 @@ REQUIRED FLAGS addon must first be enabled on the master by using --update-addons=NetworkPolicy=ENABLED flag. - --enable-private-endpoint - Enables cluster's control plane to be accessible using private IP - address only. + --enable-private-nodes + Standard cluster: Enable private nodes as a default behavior for all + newly created node pools, if --enable-private-nodes is not provided + at node pool creation time. + + Modifications to this flag do not affect `--enable-private-nodes` state of the + existing node pools. + + Autopilot cluster: Force new and existing workloads, without explicit + cloud.google.com/private-node=true node selector, to run on nodes + with no public IP address. + + Modifications to this flag trigger a re-schedule operation on all existng + workloads to run on different node VMs. --[no-]enable-ray-cluster-logging Enable automatic log processing sidecar for Ray clusters. Use @@ -1043,6 +1031,57 @@ REQUIRED FLAGS --enable-dataplane-v2-metrics Exposes advanced datapath flow metrics on node port. + --enable-authorized-networks-on-private-endpoint + Enable enforcement of --master-authorized-networks CIDR ranges for + traffic reaching cluster's control plane via private IP. + + --enable-dns-access + Enable access to the cluster's control plane over DNS-based endpoint. + + DNS-based control plane access is recommended. + + --enable-google-cloud-access + When you enable Google Cloud Access, any public IP addresses owned by + Google Cloud can reach the public control plane endpoint of your + cluster. + + --enable-ip-access + Enable access to the cluster's control plane over private IP and + public IP if --enable-private-endpoint is not enabled. + + --enable-master-global-access + Use with private clusters to allow access to the master's private + endpoint from any Google Cloud region or on-premises environment + regardless of the private cluster's region. + + --enable-private-endpoint + Enables cluster's control plane to be accessible using private IP + address only. + + Master Authorized Networks + + --enable-master-authorized-networks + Allow only specified set of CIDR blocks (specified by the + --master-authorized-networks flag) to connect to Kubernetes master + through HTTPS. Besides these blocks, the following have access as + well: + + 1) The private network the cluster connects to if + `--enable-private-nodes` is specified. + 2) Google Compute Engine Public IPs if `--enable-private-nodes` is not + specified. + + Use --no-enable-master-authorized-networks to disable. When + disabled, public internet (0.0.0.0/0) is allowed to connect to + Kubernetes master through HTTPS. + + --master-authorized-networks=NETWORK,[NETWORK,...] + The list of CIDR blocks (up to 100 for private cluster, 50 for + public cluster) that are allowed to connect to Kubernetes master + through HTTPS. Specified in CIDR notation (e.g. 1.2.3.4/30). Cannot + be specified unless --enable-master-authorized-networks is also + specified. + Node autoprovisioning --enable-autoprovisioning @@ -1360,12 +1399,6 @@ OPTIONAL FLAGS $ gcloud container clusters update example-cluster \ --cloud-run-config=load-balancer-type=INTERNAL - --master-authorized-networks=NETWORK,[NETWORK,...] - The list of CIDR blocks (up to 100 for private cluster, 50 for public - cluster) that are allowed to connect to Kubernetes master through - HTTPS. Specified in CIDR notation (e.g. 1.2.3.4/30). Cannot be - specified unless --enable-master-authorized-networks is also specified. - --node-pool=NODE_POOL Node pool to be updated. diff --git a/gcloud/database-migration/migration-jobs/create b/gcloud/database-migration/migration-jobs/create index 78d079b0b..ea7f2e237 100644 --- a/gcloud/database-migration/migration-jobs/create +++ b/gcloud/database-migration/migration-jobs/create @@ -15,8 +15,8 @@ SYNOPSIS [--peer-vpc=PEER_VPC | --static-ip | [--vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC : --vm=VM]] [--sqlserver-databases=databaseName,[...] : --sqlserver-diff-backup - --sqlserver-encrypted-databases=SQLSERVER_ENCRYPTED_DATABASES] - [GCLOUD_WIDE_FLAG ...] + --sqlserver-encrypted-databases=SQLSERVER_ENCRYPTED_DATABASES + --sqlserver-promote-when-ready] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a Database Migration Service migration job. Recommended steps before @@ -321,6 +321,12 @@ OPTIONAL FLAGS This flag accepts "-" for stdin. This flag is used only for SQL Server to Cloud SQL migrations. + --sqlserver-promote-when-ready + Promote the database when it is ready. Use + --sqlserver-promote-when-ready to enable and + --no-sqlserver-promote-when-ready to disable. This flag is used only + for homogeneous SQL Server to Cloud SQL for SQL Server migrations. + 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/database-migration/migration-jobs/update b/gcloud/database-migration/migration-jobs/update index e889c9edb..3f92a0e45 100644 --- a/gcloud/database-migration/migration-jobs/update +++ b/gcloud/database-migration/migration-jobs/update @@ -13,8 +13,8 @@ SYNOPSIS [--peer-vpc=PEER_VPC | --static-ip | --vm=VM --vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC] [--sqlserver-databases=databaseName,[...] --sqlserver-diff-backup - --sqlserver-encrypted-databases=SQLSERVER_ENCRYPTED_DATABASES] - [GCLOUD_WIDE_FLAG ...] + --sqlserver-encrypted-databases=SQLSERVER_ENCRYPTED_DATABASES + --sqlserver-promote-when-ready] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a Database Migration Service migration job. @@ -232,6 +232,12 @@ FLAGS This flag accepts "-" for stdin. This flag is used only for SQL Server to Cloud SQL migrations. + --sqlserver-promote-when-ready + Promote the database when it is ready. Use + --sqlserver-promote-when-ready to enable and + --no-sqlserver-promote-when-ready to disable. This flag is used only + for homogeneous SQL Server to Cloud SQL for SQL Server migrations. + 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/dataflow/jobs/cancel b/gcloud/dataflow/jobs/cancel index 88a154715..db8f4d911 100644 --- a/gcloud/dataflow/jobs/cancel +++ b/gcloud/dataflow/jobs/cancel @@ -15,9 +15,8 @@ POSITIONAL ARGUMENTS FLAGS --force - Forcibly cancels a Dataflow job, leaking any VMs the Dataflow job - created. Regular cancel must have been attempted at least 30 minutes - ago for a job to be force cancelled. + Forcibly cancels a Dataflow job. Regular cancel must have been + attempted at least 30 minutes prior for a job to be force cancelled. --region=REGION_ID Region ID of the jobs' regional endpoint. Defaults to 'us-central1'. diff --git a/gcloud/edge-cloud/container/clusters/create b/gcloud/edge-cloud/container/clusters/create index 81b224453..4562355d5 100644 --- a/gcloud/edge-cloud/container/clusters/create +++ b/gcloud/edge-cloud/container/clusters/create @@ -10,6 +10,7 @@ SYNOPSIS [--control-plane-machine-filter=CONTROL_PLANE_MACHINE_FILTER] [--control-plane-node-count=CONTROL_PLANE_NODE_COUNT] [--control-plane-node-location=CONTROL_PLANE_NODE_LOCATION] + [--control-plane-node-storage-schema=CONTROL_PLANE_NODE_STORAGE_SCHEMA] [--control-plane-shared-deployment-policy=CONTROL_PLANE_SHARED_DEPLOYMENT_POLICY] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--external-lb-ipv4-address-pools=[EXTERNAL_LB_IPV4_ADDRESS,...]] @@ -103,6 +104,9 @@ FLAGS Google Edge Cloud zone where the local control plane nodes will be created. + --control-plane-node-storage-schema=CONTROL_PLANE_NODE_STORAGE_SCHEMA + Name for the storage schema of control plane nodes. + --control-plane-shared-deployment-policy=CONTROL_PLANE_SHARED_DEPLOYMENT_POLICY Policy configuration about how user application is deployed for local control plane cluster. It supports two values, ALLOWED and DISALLOWED. diff --git a/gcloud/edge-cloud/container/clusters/node-pools/create b/gcloud/edge-cloud/container/clusters/node-pools/create index b91ed64bb..bad73c58a 100644 --- a/gcloud/edge-cloud/container/clusters/node-pools/create +++ b/gcloud/edge-cloud/container/clusters/node-pools/create @@ -8,7 +8,8 @@ SYNOPSIS --node-count=NODE_COUNT --node-location=NODE_LOCATION [--async] [--labels=[KEY=VALUE,...]] [--local-disk-kms-key=LOCAL_DISK_KMS_KEY] [--lro-timeout=LRO_TIMEOUT] [--machine-filter=MACHINE_FILTER] - [--node-labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--node-labels=[KEY=VALUE,...]] + [--node-storage-schema=NODE_STORAGE_SCHEMA] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create an Edge Container node pool. @@ -115,6 +116,9 @@ OPTIONAL FLAGS Comma-delimited list of key-value pairs that comprise labels for the individual nodes in the node pool. + --node-storage-schema=NODE_STORAGE_SCHEMA + Name for the storage schema of worker nodes. + 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/eventarc/help b/gcloud/eventarc/help index 356c21976..0f2909079 100644 --- a/gcloud/eventarc/help +++ b/gcloud/eventarc/help @@ -36,3 +36,9 @@ GROUPS triggers Manage Eventarc triggers. + +NOTES + This variant is also available: + + $ gcloud beta eventarc + diff --git a/gcloud/ml/speech/recognize b/gcloud/ml/speech/recognize index c779306bc..635253d29 100644 --- a/gcloud/ml/speech/recognize +++ b/gcloud/ml/speech/recognize @@ -49,7 +49,7 @@ OPTIONAL FLAGS --encoding=ENCODING; default="encoding-unspecified" The type of encoding of the file. Required if the file format is not - WAV or FLAC. ENCODING must be one of: amr, amr-wb, + WAV or FLAC. ENCODING must be one of: alaw, amr, amr-wb, encoding-unspecified, flac, linear16, mp3, mulaw, ogg-opus, speex-with-header-byte, webm-opus. diff --git a/gcloud/ml/speech/recognize-long-running b/gcloud/ml/speech/recognize-long-running index 985da89af..1d1e6afe2 100644 --- a/gcloud/ml/speech/recognize-long-running +++ b/gcloud/ml/speech/recognize-long-running @@ -58,7 +58,7 @@ OPTIONAL FLAGS --encoding=ENCODING; default="encoding-unspecified" The type of encoding of the file. Required if the file format is not - WAV or FLAC. ENCODING must be one of: amr, amr-wb, + WAV or FLAC. ENCODING must be one of: alaw, amr, amr-wb, encoding-unspecified, flac, linear16, mp3, mulaw, ogg-opus, speex-with-header-byte, webm-opus. diff --git a/gcloud/network-connectivity/internal-ranges/create b/gcloud/network-connectivity/internal-ranges/create index 50f7c161b..7bcc858c8 100644 --- a/gcloud/network-connectivity/internal-ranges/create +++ b/gcloud/network-connectivity/internal-ranges/create @@ -153,6 +153,10 @@ OPTIONAL FLAGS cases, like for example, usage on-prem, with dynamic route announcements via interconnect. + for-migration + Ranges created with FOR_MIGRATION are used as locks for migrating + subnetworks between peered VPC networks. + for-vpc A cloud resource can use the reserved CIDR block by associating it with the internal range resource if usage is set to FOR_VPC. diff --git a/gcloud/oracle-database/cloud-exadata-infrastructures/create b/gcloud/oracle-database/cloud-exadata-infrastructures/create index 9af22dc4b..ab316ebb1 100644 --- a/gcloud/oracle-database/cloud-exadata-infrastructures/create +++ b/gcloud/oracle-database/cloud-exadata-infrastructures/create @@ -9,9 +9,10 @@ SYNOPSIS [--labels=[LABELS,...]] [--request-id=REQUEST_ID] [[--properties-shape=PROPERTIES_SHAPE : --properties-compute-count=PROPERTIES_COMPUTE_COUNT - --properties-cpu-count=PROPERTIES_CPU_COUNT --properties-customer-contacts=[email=EMAIL] - --properties-db-node-storage-size-gb=PROPERTIES_DB_NODE_STORAGE_SIZE_GB --properties-memory-size-gb=PROPERTIES_MEMORY_SIZE_GB --properties-storage-count=PROPERTIES_STORAGE_COUNT --properties-total-storage-size-gb=PROPERTIES_TOTAL_STORAGE_SIZE_GB --maintenance-window-custom-action-timeout-mins=MAINTENANCE_WINDOW_CUSTOM_ACTION_TIMEOUT_MINS --maintenance-window-days-of-week=[MAINTENANCE_WINDOW_DAYS_OF_WEEK, + --properties-storage-count=PROPERTIES_STORAGE_COUNT + --properties-total-storage-size-gb=PROPERTIES_TOTAL_STORAGE_SIZE_GB + --maintenance-window-custom-action-timeout-mins=MAINTENANCE_WINDOW_CUSTOM_ACTION_TIMEOUT_MINS --maintenance-window-days-of-week=[MAINTENANCE_WINDOW_DAYS_OF_WEEK, ...] --maintenance-window-hours-of-day=[MAINTENANCE_WINDOW_HOURS_OF_DAY, ...] --maintenance-window-is-custom-action-timeout-enabled @@ -129,9 +130,6 @@ FLAGS --properties-compute-count=PROPERTIES_COMPUTE_COUNT The number of compute servers for the Exadata Infrastructure. - --properties-cpu-count=PROPERTIES_CPU_COUNT - The number of enabled CPU cores. - --properties-customer-contacts=[email=EMAIL] The list of customer contacts. @@ -151,12 +149,6 @@ FLAGS --properties-customer-contacts=path_to_file.(yaml|json) - --properties-db-node-storage-size-gb=PROPERTIES_DB_NODE_STORAGE_SIZE_GB - The local node storage allocated in GBs. - - --properties-memory-size-gb=PROPERTIES_MEMORY_SIZE_GB - The memory allocated in GBs. - --properties-storage-count=PROPERTIES_STORAGE_COUNT The number of Cloud Exadata storage servers for the Exadata Infrastructure. diff --git a/gcloud/pubsub/topics/create b/gcloud/pubsub/topics/create index 4ebc11970..e0ca723ae 100644 --- a/gcloud/pubsub/topics/create +++ b/gcloud/pubsub/topics/create @@ -4,10 +4,10 @@ NAME SYNOPSIS gcloud pubsub topics create TOPIC [TOPIC ...] [--labels=[KEY=VALUE,...]] [--message-retention-duration=MESSAGE_RETENTION_DURATION] - [--kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN - --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN - --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT - --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN] + [--ingestion-log-severity=INGESTION_LOG_SEVERITY + [--cloud-storage-ingestion-bucket=CLOUD_STORAGE_INGESTION_BUCKET + --cloud-storage-ingestion-input-format=INPUT_FORMAT + : --cloud-storage-ingestion-text-delimiter=CLOUD_STORAGE_INGESTION_TEXT_DELIMITER --cloud-storage-ingestion-minimum-object-create-time=CLOUD_STORAGE_INGESTION_MINIMUM_OBJECT_CREATE_TIME --cloud-storage-ingestion-match-glob=CLOUD_STORAGE_INGESTION_MATCH_GLOB] | --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN] [--message-encoding=ENCODING (--schema=SCHEMA : --schema-project=SCHEMA_PROJECT) : --first-revision-id=FIRST_REVISION_ID @@ -68,35 +68,69 @@ FLAGS is one of "s", "m", "h", and "d" for seconds, minutes, hours, and days, respectively. If the unit is omitted, seconds is assumed. - The following flags are for specifying ingestion settings for an import - topic from Amazon Web Services (AWS) Kinesis Data Streams + Following flags are for specifying the data source settings for an import + topic - --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN - The Kinesis data streams consumer Amazon Resource Name (ARN) to use - for ingestion. + --ingestion-log-severity=INGESTION_LOG_SEVERITY + Log severity to use for ingestion. - 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: - --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN - AWS role ARN to be used for Federated Identity authentication with - Kinesis. + Flags that specify settings for an import topic from Cloud Storage - This flag argument must be specified if any of the other arguments in - this group are specified. + --cloud-storage-ingestion-bucket=CLOUD_STORAGE_INGESTION_BUCKET + Cloud Storage bucket from which to ingest data. - --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT - The service account to be used for Federated Identity authentication - with Kinesis. + This flag argument must be specified if any of the other + arguments in this group are specified. - This flag argument must be specified if any of the other arguments in - this group are specified. + --cloud-storage-ingestion-input-format=INPUT_FORMAT + Format of the data in the Cloud Storage bucket. INPUT_FORMAT must + be one of: text, avro, pubsub_avro. - --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN - The Kinesis data stream ARN from which to ingest data. + This flag argument must be specified if any of the other + arguments in this group are specified. - This flag argument must be specified if any of the other arguments in - this group are specified. + --cloud-storage-ingestion-text-delimiter=CLOUD_STORAGE_INGESTION_TEXT_DELIMITER + Delimiter to use with text format when partitioning the object. + + --cloud-storage-ingestion-minimum-object-create-time=CLOUD_STORAGE_INGESTION_MINIMUM_OBJECT_CREATE_TIME + Only Cloud Storage objects with a larger or equal creation + timestamp will be ingested. + + --cloud-storage-ingestion-match-glob=CLOUD_STORAGE_INGESTION_MATCH_GLOB + Glob pattern used to match Cloud Storage objects that will be + ingested. If unset, all objects will be ingested. + + Flags that specify settings for an import topic from Amazon Web + Services (AWS) Kinesis Data Streams + + --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN + Kinesis data streams consumer Amazon Resource Name (ARN) to use + for ingestion. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN + AWS role ARN to be used for Federated Identity authentication + with Kinesis. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT + Service account to be used for Federated Identity authentication + with Kinesis. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN + Kinesis data stream ARN from which to ingest data. + + This flag argument must be specified if any of the other + arguments in this group are specified. Schema settings. The schema that messages published to this topic must conform to and the expected message encoding. diff --git a/gcloud/pubsub/topics/update b/gcloud/pubsub/topics/update index fedf6d19c..0fd682a59 100644 --- a/gcloud/pubsub/topics/update +++ b/gcloud/pubsub/topics/update @@ -4,10 +4,10 @@ NAME SYNOPSIS gcloud pubsub topics update TOPIC [--update-labels=[KEY=VALUE,...]] [--clear-ingestion-data-source-settings - | --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN - --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN - --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT - --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN] + | --ingestion-log-severity=INGESTION_LOG_SEVERITY + [--cloud-storage-ingestion-bucket=CLOUD_STORAGE_INGESTION_BUCKET + --cloud-storage-ingestion-input-format=INPUT_FORMAT + : --cloud-storage-ingestion-text-delimiter=CLOUD_STORAGE_INGESTION_TEXT_DELIMITER --cloud-storage-ingestion-minimum-object-create-time=CLOUD_STORAGE_INGESTION_MINIMUM_OBJECT_CREATE_TIME --cloud-storage-ingestion-match-glob=CLOUD_STORAGE_INGESTION_MATCH_GLOB] | --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN] [--clear-labels | --remove-labels=[KEY,...]] [--clear-message-retention-duration | --message-retention-duration=MESSAGE_RETENTION_DURATION] @@ -116,39 +116,81 @@ FLAGS If set, clear the Ingestion Data Source Settings from the topic. Use --no-clear-ingestion-data-source-settings to disable this flag. - The following flags are for specifying ingestion settings for an import - topic from Amazon Web Services (AWS) Kinesis Data Streams + Following flags are for specifying the data source settings for an + import topic - When updating AWSKinesis Source flags, all AWSKinesis Source flags must - be specified. Otherwise, any omitted AWSKinesis Source flags revert to - their default value. + When updating IngestionDataSourceSettings flags, all + IngestionDataSourceSettings flags must be specified. Otherwise, any + omitted IngestionDataSourceSettings flags revert to their default value. - --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN - The Kinesis data streams consumer Amazon Resource Name (ARN) to use - for ingestion. + --ingestion-log-severity=INGESTION_LOG_SEVERITY + Log severity to use for ingestion. - 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: - --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN - AWS role ARN to be used for Federated Identity authentication with - Kinesis. + Flags that specify settings for an import topic from Cloud Storage - This flag argument must be specified if any of the other arguments - in this group are specified. + When updating CloudStorage Source flags, all CloudStorage Source + flags must be specified. Otherwise, any omitted CloudStorage Source + flags revert to their default value. - --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT - The service account to be used for Federated Identity - authentication with Kinesis. + --cloud-storage-ingestion-bucket=CLOUD_STORAGE_INGESTION_BUCKET + Cloud Storage bucket from which to ingest data. - This flag argument must be specified if any of the other arguments - in this group are specified. + This flag argument must be specified if any of the other + arguments in this group are specified. - --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN - The Kinesis data stream ARN from which to ingest data. + --cloud-storage-ingestion-input-format=INPUT_FORMAT + Format of the data in the Cloud Storage bucket. INPUT_FORMAT + must be one of: text, avro, pubsub_avro. - This flag argument must be specified if any of the other arguments - in this group are specified. + This flag argument must be specified if any of the other + arguments in this group are specified. + + --cloud-storage-ingestion-text-delimiter=CLOUD_STORAGE_INGESTION_TEXT_DELIMITER + Delimiter to use with text format when partitioning the object. + + --cloud-storage-ingestion-minimum-object-create-time=CLOUD_STORAGE_INGESTION_MINIMUM_OBJECT_CREATE_TIME + Only Cloud Storage objects with a larger or equal creation + timestamp will be ingested. + + --cloud-storage-ingestion-match-glob=CLOUD_STORAGE_INGESTION_MATCH_GLOB + Glob pattern used to match Cloud Storage objects that will be + ingested. If unset, all objects will be ingested. + + Flags that specify settings for an import topic from Amazon Web + Services (AWS) Kinesis Data Streams + + When updating AWSKinesis Source flags, all AWSKinesis Source flags + must be specified. Otherwise, any omitted AWSKinesis Source flags + revert to their default value. + + --kinesis-ingestion-consumer-arn=KINESIS_INGESTION_CONSUMER_ARN + Kinesis data streams consumer Amazon Resource Name (ARN) to use + for ingestion. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-role-arn=KINESIS_INGESTION_ROLE_ARN + AWS role ARN to be used for Federated Identity authentication + with Kinesis. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-service-account=KINESIS_INGESTION_SERVICE_ACCOUNT + Service account to be used for Federated Identity + authentication with Kinesis. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --kinesis-ingestion-stream-arn=KINESIS_INGESTION_STREAM_ARN + Kinesis data stream ARN from which to ingest data. + + 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: diff --git a/gcloud/resource-manager/tags/keys/create b/gcloud/resource-manager/tags/keys/create index bb05e7d0f..caa200d62 100644 --- a/gcloud/resource-manager/tags/keys/create +++ b/gcloud/resource-manager/tags/keys/create @@ -46,8 +46,8 @@ FLAGS --purpose=PURPOSE Purpose specifier of the TagKey that can only be set on creation. Specifying this field adds additional validation from the policy system - that corresponds to the purpose. PURPOSE must be (only one value is - supported): GCE_FIREWALL. + that corresponds to the purpose. PURPOSE must be one of: GCE_FIREWALL, + DATA_GOVERNANCE. --purpose-data=[network=NETWORK] Purpose data of the TagKey that can only be set on creation. This data diff --git a/gcloud/resource-settings/describe b/gcloud/resource-settings/describe deleted file mode 100644 index e4f8aadc1..000000000 --- a/gcloud/resource-settings/describe +++ /dev/null @@ -1,61 +0,0 @@ -NAME - gcloud resource-settings describe - show the value of a resource setting - -SYNOPSIS - gcloud resource-settings describe SETTING_NAME - (--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID) [--effective] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Show the value of a resource setting. - - Resource Settings is deprecated. As of November 7, 2023, no organizations - will be onboarded for any of the enabled settings, and the service will be - shut down on October 1, 2024. - - Show the value of a resource setting. - -EXAMPLES - To describe the resource settings net-preferredDnsServers with the project - foo-project, run: - - $ gcloud resource-settings describe net-preferredDnsServers \ - --project=foo-project - -POSITIONAL ARGUMENTS - SETTING_NAME - Name of the resource settings. The list of available settings can be - fetched using the list command: $ gcloud resource-settings list - -REQUIRED FLAGS - Resource that is associated with the resource settings. - - Exactly one of these must be specified: - - --folder=FOLDER_ID - Folder ID. - - --organization=ORGANIZATION_ID - Organization ID. - - --project=PROJECT_ID - Project ID. Overrides the default core/project property value for - this command invocation. - -OPTIONAL FLAGS - --effective - Describe the effective setting. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud alpha resource-settings describe - diff --git a/gcloud/resource-settings/help b/gcloud/resource-settings/help deleted file mode 100644 index dfceeffab..000000000 --- a/gcloud/resource-settings/help +++ /dev/null @@ -1,52 +0,0 @@ -NAME - gcloud resource-settings - create and manage Resource Settings - -SYNOPSIS - gcloud resource-settings COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Create and manage Resource Settings. - - Resource Settings is deprecated. As of November 7, 2023, no organizations - will be onboarded for any of the enabled settings, and the service will be - shut down on October 1, 2024. - - The gcloud Resource Settings command group lets you create and manipulate - resource settings. - - The Resource Settings Service is a hierarchy-aware service with a - public-facing API for users to store settings that modify the behavior of - their Google Cloud Platform resources, such as virtual machines, firewalls, - projects, and so forth. Settings can be attached to organizations, folders, - and projects, and can influence these resources as well as service - resources that are descendants of the resource to which the settings are - attached. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - describe - (DEPRECATED) Show the value of a resource setting. - - list - (DEPRECATED) List all available resource settings. - - list-values - (DEPRECATED) List the values for any configured resource settings. - - set-value - (DEPRECATED) Update the value of a resource setting. - - unset-value - (DEPRECATED) Remove the value of a resource setting. - -NOTES - This variant is also available: - - $ gcloud alpha resource-settings - diff --git a/gcloud/resource-settings/set-value b/gcloud/resource-settings/set-value deleted file mode 100644 index 440287a22..000000000 --- a/gcloud/resource-settings/set-value +++ /dev/null @@ -1,38 +0,0 @@ -NAME - gcloud resource-settings set-value - update the value of a resource setting - -SYNOPSIS - gcloud resource-settings set-value --value-file=value-file - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Update the value of a resource setting. - - Resource Settings is deprecated. As of November 7, 2023, no organizations - will be onboarded for any of the enabled settings, and the service will be - shut down on October 1, 2024. - - Update the value of a resource setting. - -EXAMPLES - To set the resource setting from the file with the path ./sample_path, run: - - $ gcloud resource-settings set-value --value-file="./test_input.json" - -REQUIRED FLAGS - --value-file=value-file - Path to JSON or YAML file that contains the resource setting. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud alpha resource-settings set-value - diff --git a/gcloud/resource-settings/unset-value b/gcloud/resource-settings/unset-value deleted file mode 100644 index 8d0a73ec0..000000000 --- a/gcloud/resource-settings/unset-value +++ /dev/null @@ -1,60 +0,0 @@ -NAME - gcloud resource-settings unset-value - remove the value of a resource - setting - -SYNOPSIS - gcloud resource-settings unset-value SETTING_NAME - (--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Remove the value of a resource setting. - - Resource Settings is deprecated. As of November 7, 2023, no organizations - will be onboarded for any of the enabled settings, and the service will be - shut down on October 1, 2024. - - Remove the value of a resource setting. This reverts the resource to - inheriting the resource settings from above it in the resource hierarchy, - if any is set on a resource above it. - -EXAMPLES - To unset the resource settings net-preferredDnsServers with the project - foo-project, run: - - $ gcloud resource-settings unset-value net-preferredDnsServers \ - --project=foo-project - -POSITIONAL ARGUMENTS - SETTING_NAME - Name of the resource settings. The list of available settings can be - fetched using the list command: $ gcloud resource-settings list - -REQUIRED FLAGS - Resource that is associated with the resource settings. - - Exactly one of these must be specified: - - --folder=FOLDER_ID - Folder ID. - - --organization=ORGANIZATION_ID - Organization ID. - - --project=PROJECT_ID - Project ID. Overrides the default core/project property value for - this command invocation. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud alpha resource-settings unset-value - diff --git a/gcloud/run/deploy b/gcloud/run/deploy index 12c1737fc..cfe96deee 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -27,7 +27,8 @@ SYNOPSIS --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT - --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX + --[no-]invoker-iam-check --remove-containers=[CONTAINER,...] + --revision-suffix=REVISION_SUFFIX --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -445,6 +446,13 @@ FLAGS gen2 Run the application in a second generation execution environment. + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. + --remove-containers=[CONTAINER,...] List of containers to remove. diff --git a/gcloud/run/services/update b/gcloud/run/services/update index e7cfbaa3d..76a879721 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -21,7 +21,8 @@ SYNOPSIS | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling --execution-environment=EXECUTION_ENVIRONMENT - --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX + --[no-]invoker-iam-check --remove-containers=[CONTAINER,...] + --revision-suffix=REVISION_SUFFIX --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -327,6 +328,13 @@ FLAGS gen2 Run the application in a second generation execution environment. + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. + --remove-containers=[CONTAINER,...] List of containers to remove. diff --git a/gcloud/scc/sources/describe b/gcloud/scc/sources/describe index e0a6d0920..5c9d4ee54 100644 --- a/gcloud/scc/sources/describe +++ b/gcloud/scc/sources/describe @@ -62,7 +62,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for + This command uses the securitycenter/v2 API. The full documentation for this API can be found at: https://cloud.google.com/security-command-center NOTES diff --git a/gcloud/spanner/instances/get-locations b/gcloud/spanner/instances/get-locations new file mode 100644 index 000000000..80c299f35 --- /dev/null +++ b/gcloud/spanner/instances/get-locations @@ -0,0 +1,40 @@ +NAME + gcloud spanner instances get-locations - get the location of every replica + in a Cloud Spanner instance + +SYNOPSIS + gcloud spanner instances get-locations INSTANCE [--verbose] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get the location of every replica in a Cloud Spanner instance. + +EXAMPLES + To get the location of every replica in a Cloud Spanner instance in this + project, run: + + $ gcloud spanner instances get-locations my-instance-id + +POSITIONAL ARGUMENTS + INSTANCE + Cloud Spanner instance ID. + +FLAGS + --verbose + Indicates that both regions and types of replicas be returned. + +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 spanner instances get-locations + + $ gcloud beta spanner instances get-locations + diff --git a/gcloud/spanner/instances/help b/gcloud/spanner/instances/help index 42f6570ff..4e0b549bd 100644 --- a/gcloud/spanner/instances/help +++ b/gcloud/spanner/instances/help @@ -30,6 +30,9 @@ COMMANDS get-iam-policy Get the IAM policy for a Cloud Spanner instance. + get-locations + Get the location of every replica in a Cloud Spanner instance. + list List the Cloud Spanner instances in this project. diff --git a/gcloud/sql/export/bak b/gcloud/sql/export/bak index c015a9f1a..5f98aaed0 100644 --- a/gcloud/sql/export/bak +++ b/gcloud/sql/export/bak @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud sql export bak INSTANCE URI --database=DATABASE,[DATABASE,...], -d DATABASE,[DATABASE,...] [--async] [--bak-type=BAK_TYPE; default="FULL"] - [--differential-base] [--stripe_count=STRIPE_COUNT] [--[no-]striped] - [GCLOUD_WIDE_FLAG ...] + [--differential-base] [--export-log-end-time=EXPORT_LOG_END_TIME] + [--export-log-start-time=EXPORT_LOG_START_TIME] + [--stripe_count=STRIPE_COUNT] [--[no-]striped] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Export data from a Cloud SQL instance to a Google Cloud Storage bucket as a @@ -40,12 +41,24 @@ OPTIONAL FLAGS --bak-type=BAK_TYPE; default="FULL" Type of bak file that will be exported, FULL or DIFF. SQL Server only. - BAK_TYPE must be one of: FULL, DIFF. + BAK_TYPE must be one of: FULL, DIFF, TLOG. --differential-base Whether the bak file export can be used as differential base for future differential backup. SQL Server only + --export-log-end-time=EXPORT_LOG_END_TIME + Optional flag. The end time of the transaction log files that are + included in the export file. Use this flag to export transaction logs + for Cloud SQL for SQL Server only. Format: YYYY-MM-DDTHH:MM:SSZ, UTC + timezone only. + + --export-log-start-time=EXPORT_LOG_START_TIME + Optional flag. The start time of the transaction log files that are + included in the export file. Use this flag to export transaction logs + for Cloud SQL for SQL Server only. Format: YYYY-MM-DDTHH:MM:SSZ, UTC + timezone only. + --stripe_count=STRIPE_COUNT Specifies the number of stripes to use for SQL Server exports. diff --git a/gcloud/workstations/configs/create b/gcloud/workstations/configs/create index b3afb7d32..5c4cea146 100644 --- a/gcloud/workstations/configs/create +++ b/gcloud/workstations/configs/create @@ -17,6 +17,7 @@ SYNOPSIS [--enable-ssh-to-vm] [--ephemeral-directory=[PROPERTY=VALUE,...]] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] + [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] [--network-tags=[NETWORK_TAGS,...]] [--pd-disk-size=PD_DISK_SIZE; default=200] [--pd-disk-type=PD_DISK_TYPE; default="pd-standard"] @@ -222,6 +223,13 @@ FLAGS machines that the workstations created under this configuration will run on. + --max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT + Maximum number of workstations under this configuration a user can have + workstations.workstation.use permission on. + + If not specified, defaults to 0, which indicates a user can have + unlimited number of workstations under this configuration. + --network-tags=[NETWORK_TAGS,...] Network tags to add to the Google Compute Engine machines backing the Workstations. diff --git a/gcloud/workstations/configs/update b/gcloud/workstations/configs/update index 4da44e968..488174fcb 100644 --- a/gcloud/workstations/configs/update +++ b/gcloud/workstations/configs/update @@ -14,9 +14,10 @@ SYNOPSIS [--disable-public-ip-addresses] [--enable-audit-agent] [--enable-confidential-compute] [--enable-nested-virtualization] [--idle-timeout=IDLE_TIMEOUT] [--labels=[LABELS,...]] - [--machine-type=MACHINE_TYPE] [--network-tags=[NETWORK_TAGS,...]] - [--pool-size=POOL_SIZE] [--running-timeout=RUNNING_TIMEOUT] - [--service-account=SERVICE_ACCOUNT] + [--machine-type=MACHINE_TYPE] + [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] + [--network-tags=[NETWORK_TAGS,...]] [--pool-size=POOL_SIZE] + [--running-timeout=RUNNING_TIMEOUT] [--service-account=SERVICE_ACCOUNT] [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--vm-tags=[VM_TAGS,...]] @@ -192,6 +193,13 @@ FLAGS machines that the workstations created under this configuration will run on. + --max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT + Maximum number of workstations under this configuration a user can have + workstations.workstation.use permission on. + + If not specified, defaults to 0, which indicates a user can have + unlimited number of workstations under this configuration. + --network-tags=[NETWORK_TAGS,...] Network tags to add to the Google Compute Engine machines backing the Workstations.