diff --git a/gcloud/_version b/gcloud/_version index 973ed6825..08803fbab 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 441.0.0 -alpha 2023.07.28 -beta 2023.07.28 -bq 2.0.95 +Google Cloud SDK 442.0.0 +alpha 2023.08.04 +beta 2023.08.04 +bq 2.0.96 bundled-python3-unix 3.9.16 -core 2023.07.28 +core 2023.08.04 gcloud-crc32c 1.0.0 gsutil 5.25 diff --git a/gcloud/alpha/bms/os-images/help b/gcloud/alpha/bms/os-images/help index 9ea985db2..1a0274ecb 100644 --- a/gcloud/alpha/bms/os-images/help +++ b/gcloud/alpha/bms/os-images/help @@ -23,5 +23,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 bms os-images diff --git a/gcloud/alpha/bms/os-images/list b/gcloud/alpha/bms/os-images/list index effbe640d..ae81b5bab 100644 --- a/gcloud/alpha/bms/os-images/list +++ b/gcloud/alpha/bms/os-images/list @@ -39,5 +39,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 bms os-images list diff --git a/gcloud/alpha/bq/datasets/create b/gcloud/alpha/bq/datasets/create index 0276c6267..e47d91fb8 100644 --- a/gcloud/alpha/bq/datasets/create +++ b/gcloud/alpha/bq/datasets/create @@ -19,7 +19,7 @@ EXAMPLES overwritting destination if it exists: $ gcloud alpha bq datasets create my-other-dataset \ - --description 'My Other Dataset' --if-exists 'overwrite' + --description 'My Other Dataset' --overwrite POSITIONAL ARGUMENTS Dataset resource - ID of the the dataset being created. The ID must diff --git a/gcloud/alpha/compute/commitments/create b/gcloud/alpha/compute/commitments/create index eb82c491a..e08c6b29b 100644 --- a/gcloud/alpha/compute/commitments/create +++ b/gcloud/alpha/compute/commitments/create @@ -15,7 +15,8 @@ SYNOPSIS --machine-type=MACHINE_TYPE --maintenance-interval=MAINTENANCE_INTERVAL --min-cpu-platform=MIN_CPU_PLATFORM --require-specific-reservation - --vm-count=VM_COUNT --share-setting=SHARE_SETTING + --resource-policies=[KEY=VALUE,...] --vm-count=VM_COUNT + --share-setting=SHARE_SETTING --share-with=SHARE_WITH,[SHARE_WITH,...]]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -201,6 +202,12 @@ OPTIONAL FLAGS this reservation by name using --reservation-affinity=specific can consume from this reservation. + --resource-policies=[KEY=VALUE,...] + The resource policies to include in this reservation. If you omit + this flag, no resource policies are added. You can specify any + string as the key, and specify the name of a resource policy as + the value. + --vm-count=VM_COUNT The number of VM instances that are allocated to this reservation. The value of this field must be an int in the range diff --git a/gcloud/alpha/compute/future-reservations/create b/gcloud/alpha/compute/future-reservations/create index 56335f6e0..59851e529 100644 --- a/gcloud/alpha/compute/future-reservations/create +++ b/gcloud/alpha/compute/future-reservations/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha compute future-reservations create FUTURE_RESERVATION - --total-count=TOTAL_COUNT + --auto-delete-auto-created-reservations --total-count=TOTAL_COUNT (--source-instance-template=SOURCE_INSTANCE_TEMPLATE | [--machine-type=MACHINE_TYPE : --accelerator=[count=COUNT],[type=TYPE] @@ -15,6 +15,7 @@ SYNOPSIS (--start-time=START_TIME (--duration=DURATION | --end-time=END_TIME)) [--description=DESCRIPTION] [--name-prefix=NAME_PREFIX] [--planning-status=PLANNING_STATUS] [--zone=ZONE] + [--auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME | --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION] [--share-setting=SHARE_SETTING --share-with=PROJECT,[PROJECT,...]] [GCLOUD_WIDE_FLAG ...] @@ -48,6 +49,10 @@ POSITIONAL ARGUMENTS Name of the future reservation to create. REQUIRED FLAGS + --auto-delete-auto-created-reservations + If specified, the auto-created reservations for a future reservation + are deleted at the end time (default) or at a specified delete time. + --total-count=TOTAL_COUNT The total number of instances for which capacity assurance is requested at a future time period. @@ -197,6 +202,24 @@ OPTIONAL FLAGS Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE. + Manage the auto-delete time properties. + + At most one of these can be specified: + + --auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME + Automatically deletes an auto-created reservations at a specific + time. The specified time must be an RFC3339 timestamp, which must be + formatted as "YYYY-MM-DDTHH:MM:SSZ" where YYYY = year, MM = month, DD + = day, HH = hours, MM = minutes, SS = seconds, and Z = time zone in + Coordinated Universal Time (UTC). For example, specify + 2021-11-20T07:00:00Z. + + --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION + Automatically deletes an auto-created reservations after a specified + number of days, hours, minutes, or seconds. For example, specify 30m + for 30 minutes, or 1d2h3m4s for 1 day, 2 hours, 3 minutes, and 4 + seconds. For more information, see $ gcloud topic datetimes. + Manage the properties of a shared reservation. --share-setting=SHARE_SETTING diff --git a/gcloud/alpha/compute/future-reservations/update b/gcloud/alpha/compute/future-reservations/update index 871455473..e86bebcd3 100644 --- a/gcloud/alpha/compute/future-reservations/update +++ b/gcloud/alpha/compute/future-reservations/update @@ -4,9 +4,11 @@ NAME SYNOPSIS gcloud alpha compute future-reservations update FUTURE_RESERVATION - [--description=DESCRIPTION] [--name-prefix=NAME_PREFIX] + [--auto-delete-auto-created-reservations] [--description=DESCRIPTION] [--planning-status=PLANNING_STATUS] [--total-count=TOTAL_COUNT] [--zone=ZONE] + [--auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME | --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION] + [--clear-name-prefix | --name-prefix=NAME_PREFIX] [--clear-share-settings | --share-setting=SHARE_SETTING --share-with=PROJECT,[PROJECT,...]] [--machine-type=MACHINE_TYPE @@ -35,13 +37,13 @@ POSITIONAL ARGUMENTS Name of the future reservation to update. FLAGS + --auto-delete-auto-created-reservations + If specified, the auto-created reservations for a future reservation + are deleted at the end time (default) or at a specified delete time. + --description=DESCRIPTION An optional description of the reservation to create. - --name-prefix=NAME_PREFIX - User provided name prefix for system generated reservations when - capacity is delivered at start time. - --planning-status=PLANNING_STATUS The planning status of the future reservation. The default value is DRAFT. While in DRAFT, any changes to the future reservation's @@ -81,6 +83,35 @@ FLAGS Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE. + Manage the auto-delete time properties. + + At most one of these can be specified: + + --auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME + Automatically deletes an auto-created reservations at a specific + time. The specified time must be an RFC3339 timestamp, which must be + formatted as "YYYY-MM-DDTHH:MM:SSZ" where YYYY = year, MM = month, DD + = day, HH = hours, MM = minutes, SS = seconds, and Z = time zone in + Coordinated Universal Time (UTC). For example, specify + 2021-11-20T07:00:00Z. + + --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION + Automatically deletes an auto-created reservations after a specified + number of days, hours, minutes, or seconds. For example, specify 30m + for 30 minutes, or 1d2h3m4s for 1 day, 2 hours, 3 minutes, and 4 + seconds. For more information, see $ gcloud topic datetimes. + + Manage the name-prefix of a future reservation. + + At most one of these can be specified: + + --clear-name-prefix + Clears the name prefix for the system generated reservations. + + --name-prefix=NAME_PREFIX + User provided name prefix for system generated reservations when + capacity is delivered at start time. + Manage the properties of a shared future reservation. At most one of these can be specified: diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index 72137ff67..bc5f61b68 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -29,7 +29,9 @@ SYNOPSIS [--local-ssd=[device-name=DEVICE-NAME], [interface=INTERFACE],[size=SIZE]] [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] - [--machine-type=MACHINE_TYPE] [--max-run-duration=MAX_RUN_DURATION] + [--machine-type=MACHINE_TYPE] + [--maintenance-interval=MAINTENANCE_INTERVAL] + [--max-run-duration=MAX_RUN_DURATION] [--mesh=[gke-cluster=GKE-CLUSTER],[workload=WORKLOAD]] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] @@ -518,6 +520,13 @@ FLAGS available machine types, run 'gcloud compute machine-types list'. If unspecified, the default type is n1-standard-1. + --maintenance-interval=MAINTENANCE_INTERVAL + Specifies the frequency of planned maintenance events. + MAINTENANCE_INTERVAL must be (only one value is supported): + + PERIODIC + PERIODIC means the VM is a Stable Fleet VM. + --max-run-duration=MAX_RUN_DURATION Limits how long this VM instance can run, specified as a duration relative to the VM instance's most-recent start time. Format the diff --git a/gcloud/alpha/compute/instances/delete-access-config b/gcloud/alpha/compute/instances/delete-access-config index e0ea73425..21ca55225 100644 --- a/gcloud/alpha/compute/instances/delete-access-config +++ b/gcloud/alpha/compute/instances/delete-access-config @@ -12,7 +12,10 @@ DESCRIPTION (ALPHA) gcloud alpha compute instances delete-access-config is used to delete access configurations from network interfaces of Compute Engine virtual machines. Access configurations let you assign a public, external - IP to a virtual machine. + IP to a virtual machine. The delete-access-config operation removes + external IP from the instance interface. If there is traffic routed to the + external IP, after deleting the access config operation, traffic to the + external IP will not reach the VM anymore. EXAMPLES To remove the externally accessible IP from a virtual machine named diff --git a/gcloud/alpha/compute/instances/ops-agents/policies/create b/gcloud/alpha/compute/instances/ops-agents/policies/create index 28168bd2b..30d3de0bc 100644 --- a/gcloud/alpha/compute/instances/ops-agents/policies/create +++ b/gcloud/alpha/compute/instances/ops-agents/policies/create @@ -226,6 +226,7 @@ REQUIRED FLAGS OS Short Name OS Version centos 8 centos 7 + debian 12 debian 11 debian 10 debian 9 diff --git a/gcloud/alpha/compute/instances/ops-agents/policies/update b/gcloud/alpha/compute/instances/ops-agents/policies/update index 0a39d3975..ca79821d0 100644 --- a/gcloud/alpha/compute/instances/ops-agents/policies/update +++ b/gcloud/alpha/compute/instances/ops-agents/policies/update @@ -263,6 +263,7 @@ FLAGS OS Short Name OS Version centos 8 centos 7 + debian 12 debian 11 debian 10 debian 9 diff --git a/gcloud/alpha/compute/reservations/create b/gcloud/alpha/compute/reservations/create index bcf257761..d4d3c5162 100644 --- a/gcloud/alpha/compute/reservations/create +++ b/gcloud/alpha/compute/reservations/create @@ -14,6 +14,8 @@ SYNOPSIS --min-cpu-platform=MIN_CPU_PLATFORM]) : --require-specific-reservation --resource-policies=[KEY=VALUE,...]) [--description=DESCRIPTION] [--zone=ZONE] + [--delete-after-duration=DELETE_AFTER_DURATION + | --delete-at-time=DELETE_AT_TIME] [--share-setting=SHARE_SETTING --share-with=SHARE_WITH,[SHARE_WITH,...]] [GCLOUD_WIDE_FLAG ...] @@ -165,6 +167,25 @@ OPTIONAL FLAGS Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE. + Manage auto-delete properties for reservations. + + At most one of these can be specified: + + --delete-after-duration=DELETE_AFTER_DURATION + Automatically deletes the reservations after a specified number of + days, hours, minutes, or seconds from its creation. For example, + specify 30m for 30 minutes, or 1d2h3m4s for 1 day, 2 hours, 3 + minutes, and 4 seconds. For more information, see $ gcloud topic + datetimes. + + --delete-at-time=DELETE_AT_TIME + Automatically deletes the reservation at a specific time from its + creation. The specified time must be an RFC3339 timestamp, which must + be formatted as "YYYY-MM-DDTHH:MM:SSZ" where YYYY = year, MM = month, + DD = day, HH = hours, MM = minutes, SS = seconds, and Z = time zone + in Coordinated Universal Time (UTC). For example, specify + 2021-11-20T07:00:00Z. + Manage the properties of a shared reservation. --share-setting=SHARE_SETTING diff --git a/gcloud/alpha/compute/reservations/update b/gcloud/alpha/compute/reservations/update index c8ff8c6fa..40f8cdbe8 100644 --- a/gcloud/alpha/compute/reservations/update +++ b/gcloud/alpha/compute/reservations/update @@ -7,29 +7,36 @@ SYNOPSIS [--add-share-with=PROJECT,[PROJECT,...]] [--remove-share-with=PROJECT,[PROJECT,...]] [--share-with=SHARE_WITH,[SHARE_WITH,...]] [--vm-count=VM_COUNT] - [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--zone=ZONE] + [--delete-after-duration=DELETE_AFTER_DURATION + | --delete-at-time=DELETE_AT_TIME | --disable-auto-delete] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update Compute Engine reservations. EXAMPLES - To add my-project to the list of projects that are shared with a Compute - Engine reservation, my-reservation in zone: us-central1-a, run: + To add project-1,project-2,project-3 to the list of projects that are + shared with a Compute Engine reservation, my-reservation in zone: + us-central1-a, run: $ gcloud alpha compute reservations update my-reservation \ - --add-share-with=my-project --zone=us-central1-a + --add-share-with=project-1,project-2,project-3 \ + --zone=us-central1-a - To remove my-project from the list of projects that are shared with a - Compute Engine reservation, my-reservation in zone: us-central1-a, run: + To remove project-1,project-2,project-3 from the list of projects that are + shared with a Compute Engine reservation, my-reservation in zone: + us-central1-a, run: $ gcloud alpha compute reservations update my-reservation \ - --remove-share-with=my-project --zone=us-central1-a + --remove-share-with=project-1,project-2,project-3 \ + --zone=us-central1-a To update the entire list of projects that are shared with a Compute Engine reservation, my-reservation in zone: us-central1-a, run: $ gcloud alpha compute reservations update my-reservation \ - --share-with=my-project --zone=us-central1-a + --share-with=project-1,project-2,project-3 --zone=us-central1-a To update the number of reserved VM instances to 500 for a Compute Engine reservation, my-reservation in zone: us-central1-a, run: @@ -83,6 +90,28 @@ FLAGS Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE. + Manage auto-delete properties for reservations. + + At most one of these can be specified: + + --delete-after-duration=DELETE_AFTER_DURATION + Automatically deletes the reservations after a specified number of + days, hours, minutes, or seconds from its creation. For example, + specify 30m for 30 minutes, or 1d2h3m4s for 1 day, 2 hours, 3 + minutes, and 4 seconds. For more information, see $ gcloud topic + datetimes. + + --delete-at-time=DELETE_AT_TIME + Automatically deletes the reservation at a specific time from its + creation. The specified time must be an RFC3339 timestamp, which must + be formatted as "YYYY-MM-DDTHH:MM:SSZ" where YYYY = year, MM = month, + DD = day, HH = hours, MM = minutes, SS = seconds, and Z = time zone + in Coordinated Universal Time (UTC). For example, specify + 2021-11-20T07:00:00Z. + + --disable-auto-delete + Disables the auto-delete setting for the reservation. + 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/compute/security-policies/add-layer7-ddos-defense-threshold-config b/gcloud/alpha/compute/security-policies/add-layer7-ddos-defense-threshold-config new file mode 100644 index 000000000..7bc82a110 --- /dev/null +++ b/gcloud/alpha/compute/security-policies/add-layer7-ddos-defense-threshold-config @@ -0,0 +1,74 @@ +NAME + gcloud alpha compute security-policies + add-layer7-ddos-defense-threshold-config - add a layer7 ddos defense + threshold config to a Compute Engine security policy + +SYNOPSIS + gcloud alpha compute security-policies + add-layer7-ddos-defense-threshold-config NAME + --threshold-config-name=THRESHOLD_CONFIG_NAME + [--auto-deploy-confidence-threshold=AUTO_DEPLOY_CONFIDENCE_THRESHOLD] + [--auto-deploy-expiration-sec=AUTO_DEPLOY_EXPIRATION_SEC] + [--auto-deploy-impacted-baseline-threshold=AUTO_DEPLOY_IMPACTED_BASELINE_THRESHOLD] + [--auto-deploy-load-threshold=AUTO_DEPLOY_LOAD_THRESHOLD] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute security-policies + add-layer7-ddos-defense-threshold-config is used to add layer7 ddos defense + threshold configs to security policies. + +EXAMPLES + To add a layer7 ddos defense threshold config run the following command: + + $ gcloud alpha compute security-policies \ + add-layer7-ddos-defense-threshold-config NAME \ + --threshold-config-name=my-threshold-config-name \ + --auto-deploy-load-threshold=0.7 \ + --auto-deploy-confidence-threshold=0.8 \ + --auto-deploy-impacted-baseline-threshold=0.1 \ + --auto-deploy-expiration-sec=4800 + +POSITIONAL ARGUMENTS + NAME + Name of the security policy to update. + +REQUIRED FLAGS + --threshold-config-name=THRESHOLD_CONFIG_NAME + The name for the threshold config. + +OPTIONAL FLAGS + --auto-deploy-confidence-threshold=AUTO_DEPLOY_CONFIDENCE_THRESHOLD + The threshold of the confidence of an identified attack over which + auto-deploy takes action. + + --auto-deploy-expiration-sec=AUTO_DEPLOY_EXPIRATION_SEC + The duration of actions, if any, taken by auto-deploy. + + --auto-deploy-impacted-baseline-threshold=AUTO_DEPLOY_IMPACTED_BASELINE_THRESHOLD + The threshold on the estimated impact to the baseline traffic of a + suggested mitigation, below which auto-deploy takes action. + + --auto-deploy-load-threshold=AUTO_DEPLOY_LOAD_THRESHOLD + The threshold on backend's load over which auto-deploy takes action. + +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 compute security-policies \ + add-layer7-ddos-defense-threshold-config + + $ gcloud beta compute security-policies \ + add-layer7-ddos-defense-threshold-config + diff --git a/gcloud/alpha/compute/security-policies/help b/gcloud/alpha/compute/security-policies/help index 3e22424c1..efb232d48 100644 --- a/gcloud/alpha/compute/security-policies/help +++ b/gcloud/alpha/compute/security-policies/help @@ -33,6 +33,10 @@ GROUPS COMMANDS COMMAND is one of the following: + add-layer7-ddos-defense-threshold-config + (ALPHA) Add a layer7 ddos defense threshold config to a Compute Engine + security policy. + add-user-defined-field (ALPHA) Add a user defined field to a Compute Engine security policy. @@ -57,6 +61,10 @@ COMMANDS list-preconfigured-expression-sets (ALPHA) List all available preconfigured expression sets. + remove-layer7-ddos-defense-threshold-config + (ALPHA) Remove a layer7 ddos defense threshold config from a Compute + Engine security policy. + remove-user-defined-field (ALPHA) Remove a user defined field from a Compute Engine security policy. diff --git a/gcloud/alpha/compute/security-policies/remove-layer7-ddos-defense-threshold-config b/gcloud/alpha/compute/security-policies/remove-layer7-ddos-defense-threshold-config new file mode 100644 index 000000000..352a795e0 --- /dev/null +++ b/gcloud/alpha/compute/security-policies/remove-layer7-ddos-defense-threshold-config @@ -0,0 +1,50 @@ +NAME + gcloud alpha compute security-policies + remove-layer7-ddos-defense-threshold-config - remove a layer7 ddos + defense threshold config from a Compute Engine security policy + +SYNOPSIS + gcloud alpha compute security-policies + remove-layer7-ddos-defense-threshold-config NAME + --threshold-config-name=THRESHOLD_CONFIG_NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute security-policies + remove-layer7-ddos-defense-threshold-config is used to remove layer7 ddos + defense threshold configs from security policies. + +EXAMPLES + To remove a layer7 ddos defense threshold config run the following command: + + $ gcloud alpha compute security-policies \ + remove-layer7-ddos-defense-threshold-config NAME \ + --threshold-config-name=my-threshold-config-name + +POSITIONAL ARGUMENTS + NAME + Name of the security policy to update. + +REQUIRED FLAGS + --threshold-config-name=THRESHOLD_CONFIG_NAME + The name for the threshold 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. These variants are also available: + + $ gcloud compute security-policies \ + remove-layer7-ddos-defense-threshold-config + + $ gcloud beta compute security-policies \ + remove-layer7-ddos-defense-threshold-config + diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 8cb9d3089..a627edd23 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -397,7 +397,8 @@ FLAGS --disk-type=DISK_TYPE Type of the node VM boot disk. For version 1.24.0+, defaults to pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE - must be one of: pd-standard, pd-ssd, pd-balanced. + must be one of: pd-standard, pd-ssd, pd-balanced, hyperdisk-balanced, + hyperdisk-extreme, hyperdisk-throughput. --enable-autorepair Enable node autorepair feature for a cluster's default node pool(s). diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 7b924720f..79dce57be 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -8,7 +8,6 @@ SYNOPSIS | --autoscaling-profile=AUTOSCALING_PROFILE | --clear-fleet-project | --complete-credential-rotation | --complete-ip-rotation | --database-encryption-key=DATABASE_ENCRYPTION_KEY - | --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-database-encryption | --disable-default-snat | --disable-workload-identity | --enable-autoscaling | --enable-cost-allocation | --enable-fleet @@ -61,7 +60,8 @@ SYNOPSIS --resource-usage-bigquery-dataset=RESOURCE_USAGE_BIGQUERY_DATASET | --cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN --cluster-dns-scope=CLUSTER_DNS_SCOPE - | --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics + | --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics | [--enable-autoprovisioning : --autoprovisioning-config-file=AUTOPROVISIONING_CONFIG_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE @@ -168,35 +168,6 @@ REQUIRED FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. - --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - Select Advanced Datapath Observability mode for the cluster. Defaults - to DISABLED. - - Advanced Datapath Observability allows for a real-time view into - pod-to-pod traffic within your cluster. - - Examples: - - $ gcloud alpha container clusters update \ - --dataplane-v2-observability-mode=DISABLED - - $ gcloud alpha container clusters update \ - --dataplane-v2-observability-mode=INTERNAL_VPC_LB - - $ gcloud alpha container clusters update \ - --dataplane-v2-observability-mode=EXTERNAL_LB - - DATAPLANE_V2_OBSERVABILITY_MODE must be one of: - - DISABLED - Disables Advanced Datapath Observability. - EXTERNAL_LB - Makes Advanced Datapath Observability available to the external - network. - INTERNAL_VPC_LB - Makes Advanced Datapath Observability available from the VPC - network. - --disable-database-encryption Disable database encryption. @@ -932,6 +903,35 @@ REQUIRED FLAGS vpc Configures the Cloud DNS zone to be private to the VPC Network. + --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + Select Advanced Datapath Observability mode for the cluster. Defaults + to DISABLED. + + Advanced Datapath Observability allows for a real-time view into + pod-to-pod traffic within your cluster. + + Examples: + + $ gcloud alpha container clusters update \ + --dataplane-v2-observability-mode=DISABLED + + $ gcloud alpha container clusters update \ + --dataplane-v2-observability-mode=INTERNAL_VPC_LB + + $ gcloud alpha container clusters update \ + --dataplane-v2-observability-mode=EXTERNAL_LB + + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: + + DISABLED + Disables Advanced Datapath Observability. + EXTERNAL_LB + Makes Advanced Datapath Observability available to the external + network. + INTERNAL_VPC_LB + Makes Advanced Datapath Observability available from the VPC + network. + At most one of these can be specified: --disable-dataplane-v2-metrics diff --git a/gcloud/alpha/container/fleet/memberships/bindings/create b/gcloud/alpha/container/fleet/memberships/bindings/create index bd2210aa1..f37efd663 100644 --- a/gcloud/alpha/container/fleet/memberships/bindings/create +++ b/gcloud/alpha/container/fleet/memberships/bindings/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha container fleet memberships bindings create (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + (--fleet=FLEET | --scope=SCOPE) [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command can fail for the following reasons: @@ -99,6 +100,15 @@ REQUIRED FLAGS To set the scope attribute: ▫ provide the argument --scope on the command line. +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, diff --git a/gcloud/alpha/container/fleet/memberships/bindings/update b/gcloud/alpha/container/fleet/memberships/bindings/update index ff75d9e26..626ba324d 100644 --- a/gcloud/alpha/container/fleet/memberships/bindings/update +++ b/gcloud/alpha/container/fleet/memberships/bindings/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha container fleet memberships bindings update (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + (--fleet=FLEET | --scope=SCOPE) [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command can fail for the following reasons: @@ -100,6 +101,37 @@ REQUIRED FLAGS To set the scope attribute: ▫ provide the argument --scope on the command line. +OPTIONAL FLAGS + --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. + + 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. + + 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 container fleet memberships bindings update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha container fleet memberships bindings 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. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/container/fleet/scopes/create b/gcloud/alpha/container/fleet/scopes/create index bff98e617..b5bba14b4 100644 --- a/gcloud/alpha/container/fleet/scopes/create +++ b/gcloud/alpha/container/fleet/scopes/create @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud alpha container fleet scopes create SCOPE [--async] + [--labels=[KEY=VALUE,...]] [--namespace-labels=[KEY=VALUE,...]] [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING --upstream-scope=UPSTREAM_SCOPE --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE @@ -45,6 +46,17 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --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. + + --namespace-labels=[KEY=VALUE,...] + List of scope-level label KEY=VALUE pairs to add. + Rollout Sequencing These flags are not compatible with the --async flag. diff --git a/gcloud/alpha/container/fleet/scopes/update b/gcloud/alpha/container/fleet/scopes/update index c1ca24cc6..f51d2a598 100644 --- a/gcloud/alpha/container/fleet/scopes/update +++ b/gcloud/alpha/container/fleet/scopes/update @@ -3,6 +3,10 @@ NAME SYNOPSIS gcloud alpha container fleet scopes update (SCOPE : --location=LOCATION) + [--update-labels=[KEY=VALUE,...]] + [--update-namespace-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] + [--clear-namespace-labels | --remove-namespace-labels=[KEY,...]] [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING --remove-upgrade-soaking-overrides | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE @@ -53,6 +57,65 @@ POSITIONAL ARGUMENTS ▸ global is the only supported location. FLAGS + --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. + + 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. + + --update-namespace-labels=[KEY=VALUE,...] + List of scope-level label KEY=VALUE pairs to update in the cluster + namespace. If a label exists, its value is modified. Otherwise, a new + label is' created. + + 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 container fleet scopes update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha container fleet scopes 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: + + --clear-namespace-labels + Remove all scope-level labels from the cluster namespace. If + --update-namespace-labels is also specified then + --clear-namespace-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha container fleet scopes update scope_name \ + --clear-namespace-labels + + To remove all existing scope-level labels and create two new labels, + foo and baz: + + $ gcloud alpha container fleet scopes update scope_name \ + --clear-namespace-labels \ + --update-namespace-labels foo=bar,baz=qux + + --remove-namespace-labels=[KEY,...] + List of scope-level label keys to remove in the cluster namespace. If + a label does not exist it is silently ignored. If + --update-namespace-labels is also specified then + --update-namespace-labels is applied first. + Rollout Sequencing --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING diff --git a/gcloud/alpha/container/hub/memberships/bindings/create b/gcloud/alpha/container/hub/memberships/bindings/create index fc6654b2b..e310af684 100644 --- a/gcloud/alpha/container/hub/memberships/bindings/create +++ b/gcloud/alpha/container/hub/memberships/bindings/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha container hub memberships bindings create (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + (--fleet=FLEET | --scope=SCOPE) [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command can fail for the following reasons: @@ -99,6 +100,15 @@ REQUIRED FLAGS To set the scope attribute: ▫ provide the argument --scope on the command line. +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, diff --git a/gcloud/alpha/container/hub/memberships/bindings/update b/gcloud/alpha/container/hub/memberships/bindings/update index fc70b96d5..280a4be9f 100644 --- a/gcloud/alpha/container/hub/memberships/bindings/update +++ b/gcloud/alpha/container/hub/memberships/bindings/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha container hub memberships bindings update (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + (--fleet=FLEET | --scope=SCOPE) [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command can fail for the following reasons: @@ -100,6 +101,37 @@ REQUIRED FLAGS To set the scope attribute: ▫ provide the argument --scope on the command line. +OPTIONAL FLAGS + --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. + + 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. + + 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 container hub memberships bindings update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha container hub memberships bindings 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. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/container/hub/scopes/create b/gcloud/alpha/container/hub/scopes/create index 72c53ac42..696c88cce 100644 --- a/gcloud/alpha/container/hub/scopes/create +++ b/gcloud/alpha/container/hub/scopes/create @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud alpha container hub scopes create SCOPE [--async] + [--labels=[KEY=VALUE,...]] [--namespace-labels=[KEY=VALUE,...]] [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING --upstream-scope=UPSTREAM_SCOPE --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE @@ -45,6 +46,17 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --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. + + --namespace-labels=[KEY=VALUE,...] + List of scope-level label KEY=VALUE pairs to add. + Rollout Sequencing These flags are not compatible with the --async flag. diff --git a/gcloud/alpha/container/hub/scopes/update b/gcloud/alpha/container/hub/scopes/update index 290cc2101..a414648bb 100644 --- a/gcloud/alpha/container/hub/scopes/update +++ b/gcloud/alpha/container/hub/scopes/update @@ -3,6 +3,10 @@ NAME SYNOPSIS gcloud alpha container hub scopes update (SCOPE : --location=LOCATION) + [--update-labels=[KEY=VALUE,...]] + [--update-namespace-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] + [--clear-namespace-labels | --remove-namespace-labels=[KEY,...]] [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING --remove-upgrade-soaking-overrides | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE @@ -53,6 +57,65 @@ POSITIONAL ARGUMENTS ▸ global is the only supported location. FLAGS + --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. + + 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. + + --update-namespace-labels=[KEY=VALUE,...] + List of scope-level label KEY=VALUE pairs to update in the cluster + namespace. If a label exists, its value is modified. Otherwise, a new + label is' created. + + 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 container hub scopes update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha container hub scopes 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: + + --clear-namespace-labels + Remove all scope-level labels from the cluster namespace. If + --update-namespace-labels is also specified then + --clear-namespace-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha container hub scopes update scope_name \ + --clear-namespace-labels + + To remove all existing scope-level labels and create two new labels, + foo and baz: + + $ gcloud alpha container hub scopes update scope_name \ + --clear-namespace-labels \ + --update-namespace-labels foo=bar,baz=qux + + --remove-namespace-labels=[KEY,...] + List of scope-level label keys to remove in the cluster namespace. If + a label does not exist it is silently ignored. If + --update-namespace-labels is also specified then + --update-namespace-labels is applied first. + Rollout Sequencing --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index 2206a696c..e7ce337ae 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -192,7 +192,8 @@ FLAGS --disk-type=DISK_TYPE Type of the node VM boot disk. For version 1.24.0+, defaults to pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE - must be one of: pd-standard, pd-ssd, pd-balanced. + must be one of: pd-standard, pd-ssd, pd-balanced, hyperdisk-balanced, + hyperdisk-extreme, hyperdisk-throughput. --enable-autoprovisioning Enables Cluster Autoscaler to treat the node pool as if it was diff --git a/gcloud/alpha/container/vmware/clusters/create b/gcloud/alpha/container/vmware/clusters/create index 5d6a672b8..1e68824f5 100644 --- a/gcloud/alpha/container/vmware/clusters/create +++ b/gcloud/alpha/container/vmware/clusters/create @@ -29,7 +29,8 @@ SYNOPSIS [ips=IPS],[netmask=NETMASK]) [--admin-users=ADMIN_USERS] [--annotations=[KEY=VALUE,...]] [--async] [--description=DESCRIPTION] [--disable-aag-config] [--disable-vsphere-csi] [--enable-auto-repair] - [--enable-vm-tracking] [--validate-only] + [--enable-vm-tracking] [--upgrade-control-plane=UPGRADE_CONTROL_PLANE] + [--validate-only] [--cpus=CPUS --enable-auto-resize --memory=MEMORY --replicas=REPLICAS] [--disable-control-plane-v2 | --enable-control-plane-v2] [--enable-advanced-networking --enable-dataplane-v2] @@ -319,6 +320,24 @@ OPTIONAL FLAGS --enable-vm-tracking If set, enable VM tracking. + Upgrade policy for the cluster. + + --upgrade-control-plane=UPGRADE_CONTROL_PLANE + If not specified, node pools are upgraded together with the control + plane. + + Examples: + + To upgrade control plane only and keep node pools version unchanged, + + $ gcloud alpha container vmware clusters create \ + --upgrade-control-plane=True + + To upgrade both control plane and node pools, + + $ gcloud alpha container vmware clusters create \ + --upgrade-control-plane=False + --validate-only If set, only validate the request, but do not actually perform the operation. diff --git a/gcloud/alpha/container/vmware/clusters/update b/gcloud/alpha/container/vmware/clusters/update index 03ff41a86..0c3c81031 100644 --- a/gcloud/alpha/container/vmware/clusters/update +++ b/gcloud/alpha/container/vmware/clusters/update @@ -10,7 +10,9 @@ SYNOPSIS [avoid-buggy-ips=AVOID-BUGGY-IPS], [manual-assign=MANUAL-ASSIGN],[pool=POOL]] [--static-ip-config-ip-blocks=[gateway=GATEWAY], - [ips=IPS],[netmask=NETMASK]] [--validate-only] [--version=VERSION] + [ips=IPS],[netmask=NETMASK]] + [--upgrade-control-plane=UPGRADE_CONTROL_PLANE] [--validate-only] + [--version=VERSION] [--add-annotations=[KEY1=VALUE1,KEY2=VALUE2,...] | --remove-annotations=[KEY1,KEY2,...]] [--cpus=CPUS --memory=MEMORY --disable-auto-resize @@ -131,6 +133,24 @@ FLAGS Use quote around the flag value to escape semicolon in the terminal. + Upgrade policy for the cluster. + + --upgrade-control-plane=UPGRADE_CONTROL_PLANE + If not specified, node pools are upgraded together with the control + plane. + + Examples: + + To upgrade control plane only and keep node pools version unchanged, + + $ gcloud alpha container vmware clusters update \ + --upgrade-control-plane=True + + To upgrade both control plane and node pools, + + $ gcloud alpha container vmware clusters update \ + --upgrade-control-plane=False + --validate-only If set, only validate the request, but do not actually perform the operation. diff --git a/gcloud/alpha/database-migration/connection-profiles/create/mysql b/gcloud/alpha/database-migration/connection-profiles/create/mysql index 61a89c624..0c17cf33f 100644 --- a/gcloud/alpha/database-migration/connection-profiles/create/mysql +++ b/gcloud/alpha/database-migration/connection-profiles/create/mysql @@ -87,14 +87,14 @@ FLAGS CLOUDSQL. --ca-certificate=CA_CERTIFICATE - x509 PEM-encoded certificate of the CA that signed the source database + x509 PEM-encoded certificate of the CA that signed the database server's certificate. The replica will use this certificate to verify it's connecting to the correct host. Database Migration Service encrypts the value when storing it. --certificate=CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to - authenticate against the source database server. + authenticate against the database server. --private-key=PRIVATE_KEY Unencrypted PKCS#1 or PKCS#8 PEM-encoded private key associated with @@ -102,10 +102,13 @@ FLAGS when storing it. --host=HOST - IP or hostname of the source database. + IP or hostname of the database. When --psc-service-attachment is also + specified, this field value should be: 1. For Cloud SQL PSC enabled + instance - the dns_name field (e.g ..sql.goog.). 2. For + Cloud SQL PSA instance (vpc peering) - the private ip of the instance. --port=PORT - Network port of the source database. + Network port of the database. --username=USERNAME Username that Database Migration Service uses to connect to the @@ -116,8 +119,8 @@ FLAGS --password=PASSWORD Password for the user that Database Migration Service uses to connect - to the source database. Database Migration Service encrypts the value - when storing it, and the field is not returned on request. + to the database. Database Migration Service encrypts the value when + storing it, and the field is not returned on request. --prompt-for-password Prompt for the password used to connect to the database. diff --git a/gcloud/alpha/database-migration/connection-profiles/update b/gcloud/alpha/database-migration/connection-profiles/update index f7799cb7d..57458e9c7 100644 --- a/gcloud/alpha/database-migration/connection-profiles/update +++ b/gcloud/alpha/database-migration/connection-profiles/update @@ -62,14 +62,14 @@ POSITIONAL ARGUMENTS FLAGS --ca-certificate=CA_CERTIFICATE - x509 PEM-encoded certificate of the CA that signed the source database + x509 PEM-encoded certificate of the CA that signed the database server's certificate. The replica will use this certificate to verify it's connecting to the correct host. Database Migration Service encrypts the value when storing it. --certificate=CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to - authenticate against the source database server. + authenticate against the database server. --display-name=DISPLAY_NAME A user-friendly name for the connection profile. The display name can @@ -77,14 +77,17 @@ FLAGS letter. --host=HOST - IP or hostname of the source database. + IP or hostname of the database. When --psc-service-attachment is also + specified, this field value should be: 1. For Cloud SQL PSC enabled + instance - the dns_name field (e.g ..sql.goog.). 2. For + Cloud SQL PSA instance (vpc peering) - the private ip of the instance. --instance=INSTANCE If the source is a Cloud SQL database, use this field to provide the Cloud SQL instance ID of the source. --port=PORT - Network port of the source database. + Network port of the database. --private-key=PRIVATE_KEY Unencrypted PKCS#1 or PKCS#8 PEM-encoded private key associated with @@ -130,8 +133,8 @@ FLAGS --password=PASSWORD Password for the user that Database Migration Service uses to connect - to the source database. Database Migration Service encrypts the value - when storing it, and the field is not returned on request. + to the database. Database Migration Service encrypts the value when + storing it, and the field is not returned on request. --prompt-for-password Prompt for the password used to connect to the database. diff --git a/gcloud/alpha/infra-manager/deployments/apply b/gcloud/alpha/infra-manager/deployments/apply index 769afb86f..6938f2067 100644 --- a/gcloud/alpha/infra-manager/deployments/apply +++ b/gcloud/alpha/infra-manager/deployments/apply @@ -89,10 +89,10 @@ FLAGS complete. --import-existing-resources=IMPORT_EXISTING_RESOURCES - By default, Cloud Config Manager will return a failure when Terraform + By default, Infrastructure Manager will return a failure when Terraform encounters a 409 code (resource conflict error) during actuation. If - this flag is set to true, Cloud Config Manager will instead attempt to - automatically import the resource into the Terraform state (for + this flag is set to true, Infrastructure Manager will instead attempt + to automatically import the resource into the Terraform state (for supported resource types) and continue actuation. --labels=[KEY=VALUE,...] diff --git a/gcloud/alpha/infra-manager/deployments/unlock b/gcloud/alpha/infra-manager/deployments/unlock index 2210c7876..036a7667d 100644 --- a/gcloud/alpha/infra-manager/deployments/unlock +++ b/gcloud/alpha/infra-manager/deployments/unlock @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha infra-manager deployments unlock (DEPLOYMENT : --location=LOCATION) --lock-id=LOCK_ID [--async] - [--disable-validate-update] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command releases the lock on deployment. @@ -59,11 +59,6 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. - --disable-validate-update - If this flag is set to true, the unlock mechanism will only unlock the - deployment instead of validating the state file and triggering an - update deployment workflow. - 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/infra-manager/help b/gcloud/alpha/infra-manager/help index 2ad7f770b..f16e17f68 100644 --- a/gcloud/alpha/infra-manager/help +++ b/gcloud/alpha/infra-manager/help @@ -18,6 +18,9 @@ GROUPS deployments (ALPHA) Manage Deployment resources. + resources + (ALPHA) List or describe resources under a Revision. + revisions (ALPHA) Manage Revision resources. diff --git a/gcloud/alpha/infra-manager/resources/describe b/gcloud/alpha/infra-manager/resources/describe new file mode 100644 index 000000000..c95e97fbb --- /dev/null +++ b/gcloud/alpha/infra-manager/resources/describe @@ -0,0 +1,86 @@ +NAME + gcloud alpha infra-manager resources describe - describe resources + +SYNOPSIS + gcloud alpha infra-manager resources describe + (RESOURCE + : --deployment=DEPLOYMENT --location=LOCATION --revision=REVISION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a resource + +EXAMPLES + To describe a resource compute-resource under revision + projects/p1/locations/us-central1/deployments/example-deployment/revisions/r-0, + run: + + $ gcloud alpha infra-manager resources describe \ + projects/p1/locations/us-central1/deployments/\ + example-deployment/revisions/r-0/resources/compute-resource + +POSITIONAL ARGUMENTS + Resource resource - The resource 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 resource on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + RESOURCE + ID of the resource or fully qualified identifier for the resource. + + To set the resource attribute: + ▸ provide the argument resource on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --deployment=DEPLOYMENT + deployments TBD + + To set the deployment attribute: + ▸ provide the argument resource on the command line with a fully + specified name; + ▸ provide the argument --deployment on the command line. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument resource on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --revision=REVISION + revisions TBD + + To set the revision attribute: + ▸ provide the argument resource on the command line with a fully + specified name; + ▸ provide the argument --revision 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 config/v1alpha2 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +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/infra-manager/resources/help b/gcloud/alpha/infra-manager/resources/help new file mode 100644 index 000000000..e9e31b23c --- /dev/null +++ b/gcloud/alpha/infra-manager/resources/help @@ -0,0 +1,30 @@ +NAME + gcloud alpha infra-manager resources - list or describe resources under a + Revision + +SYNOPSIS + gcloud alpha infra-manager resources COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List or describe resources under a Revision. + +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) Describe resources. + + list + (ALPHA) List resources. + +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/infra-manager/resources/list b/gcloud/alpha/infra-manager/resources/list new file mode 100644 index 000000000..02bf2ba6a --- /dev/null +++ b/gcloud/alpha/infra-manager/resources/list @@ -0,0 +1,108 @@ +NAME + gcloud alpha infra-manager resources list - list resources + +SYNOPSIS + gcloud alpha infra-manager resources list + (--revision=REVISION : --deployment=DEPLOYMENT --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List resources for a deployment revision + +EXAMPLES + To list all resources for a deployment revision, + projects/p1/locations/l1/deployments/d1/revisions/r-0, run: + + $ gcloud alpha infra-manager resources list \ + --revision=projects/p1/locations/l1/deployments/d1/revisions/r-0 + +REQUIRED FLAGS + Revision resource - The deployment revision for which we want to list all + resources. 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 --revision on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --revision=REVISION + ID of the revision or fully qualified identifier for the revision. + + To set the revision attribute: + ▸ provide the argument --revision on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --deployment=DEPLOYMENT + deployments TBD + + To set the deployment attribute: + ▸ provide the argument --revision on the command line with a fully + specified name; + ▸ provide the argument --deployment on the command line. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument --revision on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the config/v1alpha2 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +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/network-security/security-profiles/threat-prevention/add-override b/gcloud/alpha/network-security/security-profiles/threat-prevention/add-override index c73bdd912..6f1bec018 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/add-override +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/add-override @@ -8,7 +8,8 @@ SYNOPSIS (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) --action=ACTION (--severities=[SEVERITY_LEVEL,...] | --threat-ids=[THREAT-ID,...]) - [--async] [GCLOUD_WIDE_FLAG ...] + [--async] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Add severities or threat-ids to existing threat prevention profile @@ -84,6 +85,37 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. The default is False. + --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. + + 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. + + 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 network-security security-profiles \ + threat-prevention add-override --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha network-security security-profiles \ + threat-prevention add-override --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. + 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/network-security/security-profiles/threat-prevention/create b/gcloud/alpha/network-security/security-profiles/threat-prevention/create index 3f2457734..c6cba500d 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/create +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha network-security security-profiles threat-prevention create (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) - [--async] [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a new Security Profile with the given name. @@ -58,6 +59,14 @@ FLAGS --description=DESCRIPTION Brief description of the security profile + --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, diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/delete-override b/gcloud/alpha/network-security/security-profiles/threat-prevention/delete-override index 1b5bddccd..b68837de7 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/delete-override +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/delete-override @@ -7,7 +7,8 @@ SYNOPSIS delete-override (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) (--severities=[SEVERITY_LEVEL,...] | --threat-ids=[THREAT-ID,...]) - [--async] [GCLOUD_WIDE_FLAG ...] + [--async] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) To delete existing severities or threat-ids of threat prevention @@ -79,6 +80,37 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. The default is False. + --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. + + 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. + + 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 network-security security-profiles \ + threat-prevention delete-override --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha network-security security-profiles \ + threat-prevention delete-override --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. + 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/network-security/security-profiles/threat-prevention/update-override b/gcloud/alpha/network-security/security-profiles/threat-prevention/update-override index 89d7e80e5..174fb41de 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/update-override +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/update-override @@ -8,7 +8,8 @@ SYNOPSIS (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) --action=ACTION (--severities=[SEVERITY_LEVEL,...] | --threat-ids=[THREAT-ID,...]) - [--async] [GCLOUD_WIDE_FLAG ...] + [--async] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) To update existing severities or threat-ids of threat prevention @@ -84,6 +85,37 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. The default is False. + --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. + + 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. + + 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 network-security security-profiles \ + threat-prevention update-override --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha network-security security-profiles \ + threat-prevention update-override --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. + 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/run/deploy b/gcloud/alpha/run/deploy index 3f60ff76c..d14993dc6 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -508,35 +508,35 @@ FLAGS At most one of these can be specified: --clear-network - Disconnect this Cloud Run Service from the Google Compute Engine - subnetwork it has connected to. + Disconnect this Cloud Run service from the VPC network it is + connected to. Direct VPC egress setting flags group. --network=NETWORK - The Compute Engine network that the Cloud Run Service will - connect to. If --subnet is also specified, subnet must be a + 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 - reset this field to its default, pass an empty string. + clear existing VPC network settings, use --clear-network. --subnet=SUBNET - The Google Compute Engine subnetwork that the Cloud Run Service - will connect to. 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 reset this field to its default, pass an empty - string. + 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. + service. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) on the - Cloud Run Service. To reset this field to its default, pass an - empty string. + 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: diff --git a/gcloud/alpha/run/jobs/create b/gcloud/alpha/run/jobs/create index 51857423e..0e7ff8869 100644 --- a/gcloud/alpha/run/jobs/create +++ b/gcloud/alpha/run/jobs/create @@ -1,5 +1,5 @@ NAME - gcloud alpha run jobs create - deploy a new job to Cloud Run + gcloud alpha run jobs create - create a Cloud Run job SYNOPSIS gcloud alpha run jobs create [JOB] --image=IMAGE [--args=[ARG,...]] @@ -136,8 +136,8 @@ OPTIONAL FLAGS example, "10" is 10 seconds. --tasks=TASKS; default=1 - Number of tasks that must run to completion for the job to be - considered done. Use this flag to trigger multiple runs of the job. + Number of tasks that must run to completion for the execution to be + considered done. --vpc-connector=VPC_CONNECTOR Set a VPC connector for this resource. @@ -190,21 +190,22 @@ OPTIONAL FLAGS Direct VPC egress setting flags group. --network=NETWORK - The Compute Engine network that the Cloud Run Job will connect to. If - --subnet is also specified, subnet must be a subnetwork of the - network specified by this --network flag. To reset this field to its - default, pass an empty string. + The VPC network that the Cloud Run job 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. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) on the Cloud - Run Job. To reset this field to its default, pass an empty string. + Applies the given Compute Engine tags (comma separated) to the Cloud + Run job. To clear existing tags, use --clear-network-tags. --subnet=SUBNET - The Google Compute Engine subnetwork that the Cloud Run Job will - connect to. 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 reset this field to its default, pass an empty string. + The VPC subnetwork that the Cloud Run job 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. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/jobs/deploy b/gcloud/alpha/run/jobs/deploy index ca9b6c3db..1c58c7853 100644 --- a/gcloud/alpha/run/jobs/deploy +++ b/gcloud/alpha/run/jobs/deploy @@ -135,8 +135,8 @@ FLAGS example, "10" is 10 seconds. --tasks=TASKS; default=1 - Number of tasks that must run to completion for the job to be - considered done. Use this flag to trigger multiple runs of the job. + Number of tasks that must run to completion for the execution to be + considered done. --vpc-connector=VPC_CONNECTOR Set a VPC connector for this resource. @@ -203,34 +203,33 @@ FLAGS At most one of these can be specified: --clear-network - Disconnect this Cloud Run Job from the Google Compute Engine - subnetwork it has connected to. + Disconnect this Cloud Run job from the VPC network it is connected + to. Direct VPC egress setting flags group. --network=NETWORK - The Compute Engine network that the Cloud Run Job will connect to. - If --subnet is also specified, subnet must be a subnetwork of the - network specified by this --network flag. To reset this field to - its default, pass an empty string. + The VPC network that the Cloud Run job 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 Google Compute Engine subnetwork that the Cloud Run Job will - connect to. 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 reset this field to its default, pass an empty - string. + The VPC subnetwork that the Cloud Run job 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 Job. + Clears all existing Compute Engine tags from the Cloud Run job. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) on the - Cloud Run Job. To reset this field to its default, pass an empty - string. + Applies the given Compute Engine tags (comma separated) to the + Cloud Run job. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/alpha/run/jobs/execute b/gcloud/alpha/run/jobs/execute index 889cfe08d..bbc0f9b5a 100644 --- a/gcloud/alpha/run/jobs/execute +++ b/gcloud/alpha/run/jobs/execute @@ -56,10 +56,9 @@ FLAGS seconds. --tasks=TASKS - Number of tasks that must run to completion for the job to be + Number of tasks that must run to completion for the execution to be considered done. If provided, an execution will be created with this - value. Otherwise the existing task count of the job is used. Use this - flag to trigger multiple runs of the job. + value. Otherwise the existing task count of the job is used. --update-env-vars=[KEY=VALUE,...] List of key-value pairs to set as environment variables overrides for diff --git a/gcloud/alpha/run/jobs/help b/gcloud/alpha/run/jobs/help index 03b841488..abfa53fb4 100644 --- a/gcloud/alpha/run/jobs/help +++ b/gcloud/alpha/run/jobs/help @@ -40,7 +40,7 @@ COMMANDS (ALPHA) Add IAM policy binding to a Cloud Run job. create - (ALPHA) Deploy a new job to Cloud Run. + (ALPHA) Create a Cloud Run job. delete (ALPHA) Delete a job. diff --git a/gcloud/alpha/run/jobs/update b/gcloud/alpha/run/jobs/update index 3dcaecebb..c7ccd347d 100644 --- a/gcloud/alpha/run/jobs/update +++ b/gcloud/alpha/run/jobs/update @@ -124,8 +124,8 @@ FLAGS example, "10" is 10 seconds. --tasks=TASKS; default=1 - Number of tasks that must run to completion for the job to be - considered done. Use this flag to trigger multiple runs of the job. + Number of tasks that must run to completion for the execution to be + considered done. --vpc-connector=VPC_CONNECTOR Set a VPC connector for this resource. @@ -252,34 +252,33 @@ FLAGS At most one of these can be specified: --clear-network - Disconnect this Cloud Run Job from the Google Compute Engine - subnetwork it has connected to. + Disconnect this Cloud Run job from the VPC network it is connected + to. Direct VPC egress setting flags group. --network=NETWORK - The Compute Engine network that the Cloud Run Job will connect to. - If --subnet is also specified, subnet must be a subnetwork of the - network specified by this --network flag. To reset this field to - its default, pass an empty string. + The VPC network that the Cloud Run job 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 Google Compute Engine subnetwork that the Cloud Run Job will - connect to. 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 reset this field to its default, pass an empty - string. + The VPC subnetwork that the Cloud Run job 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 Job. + Clears all existing Compute Engine tags from the Cloud Run job. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) on the - Cloud Run Job. To reset this field to its default, pass an empty - string. + Applies the given Compute Engine tags (comma separated) to the + Cloud Run job. To clear existing tags, use --clear-network-tags. Specify secrets to mount or provide as environment variables. Keys starting with a forward slash '/' are mount paths. All other keys diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 15036a143..2fea019a9 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -341,35 +341,35 @@ FLAGS At most one of these can be specified: --clear-network - Disconnect this Cloud Run Service from the Google Compute Engine - subnetwork it has connected to. + Disconnect this Cloud Run service from the VPC network it is + connected to. Direct VPC egress setting flags group. --network=NETWORK - The Compute Engine network that the Cloud Run Service will - connect to. If --subnet is also specified, subnet must be a + 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 - reset this field to its default, pass an empty string. + clear existing VPC network settings, use --clear-network. --subnet=SUBNET - The Google Compute Engine subnetwork that the Cloud Run Service - will connect to. 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 reset this field to its default, pass an empty - string. + 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. + service. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) on the - Cloud Run Service. To reset this field to its default, pass an - empty string. + 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: diff --git a/gcloud/alpha/services/api-keys/lookup b/gcloud/alpha/services/api-keys/lookup index e6297e3a7..685d4c84b 100644 --- a/gcloud/alpha/services/api-keys/lookup +++ b/gcloud/alpha/services/api-keys/lookup @@ -8,6 +8,11 @@ SYNOPSIS DESCRIPTION (ALPHA) Look up resource name of a key string. +EXAMPLES + Look up resource name of a key string named my-key-string: + + $ gcloud alpha services api-keys lookup my-key-string + POSITIONAL ARGUMENTS KEY_STRING Key string of the key @@ -24,7 +29,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud services api-keys lookup $ gcloud beta services api-keys lookup diff --git a/gcloud/alpha/spanner/help b/gcloud/alpha/spanner/help index f7c06f511..63c5246ac 100644 --- a/gcloud/alpha/spanner/help +++ b/gcloud/alpha/spanner/help @@ -27,7 +27,7 @@ GROUPS instances (ALPHA) Manage Cloud Spanner instances. - migration + migrate (ALPHA) Migrate external databases to Cloud Spanner. operations diff --git a/gcloud/alpha/spanner/migration/data b/gcloud/alpha/spanner/migrate/data similarity index 89% rename from gcloud/alpha/spanner/migration/data rename to gcloud/alpha/spanner/migrate/data index 700e05b40..7537fc8e5 100644 --- a/gcloud/alpha/spanner/migration/data +++ b/gcloud/alpha/spanner/migrate/data @@ -1,9 +1,9 @@ NAME - gcloud alpha spanner migration data - migrate data from a source database - to Cloud Spanner given a schema + gcloud alpha spanner migrate data - migrate data from a source database to + Cloud Spanner given a schema SYNOPSIS - gcloud alpha spanner migration data --session=SESSION --source=SOURCE + gcloud alpha spanner migrate data --session=SESSION --source=SOURCE [--dry-run] [--log-level=LOG_LEVEL] [--prefix=PREFIX] [--skip-foreign-keys] [--source-profile=SOURCE_PROFILE] [--target=TARGET] [--target-profile=TARGET_PROFILE] @@ -16,7 +16,7 @@ DESCRIPTION EXAMPLES To copy data to Cloud Spanner given a session file: - $ gcloud alpha spanner migration data --session=./session.json \ + $ gcloud alpha spanner migrate data --session=./session.json \ --source=postgresql < ~/cart.pg_dump \ --target-profile='instance=spanner-instance' diff --git a/gcloud/alpha/spanner/migration/help b/gcloud/alpha/spanner/migrate/help similarity index 85% rename from gcloud/alpha/spanner/migration/help rename to gcloud/alpha/spanner/migrate/help index 4508416cd..b0fe20e83 100644 --- a/gcloud/alpha/spanner/migration/help +++ b/gcloud/alpha/spanner/migrate/help @@ -1,9 +1,8 @@ NAME - gcloud alpha spanner migration - migrate external databases to Cloud - Spanner + gcloud alpha spanner migrate - migrate external databases to Cloud Spanner SYNOPSIS - gcloud alpha spanner migration COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha spanner migrate COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Migrate external databases to Cloud Spanner. diff --git a/gcloud/alpha/spanner/migration/schema b/gcloud/alpha/spanner/migrate/schema similarity index 88% rename from gcloud/alpha/spanner/migration/schema rename to gcloud/alpha/spanner/migrate/schema index 512a128e8..6b04f2ddc 100644 --- a/gcloud/alpha/spanner/migration/schema +++ b/gcloud/alpha/spanner/migrate/schema @@ -1,9 +1,9 @@ NAME - gcloud alpha spanner migration schema - migrate schema from a source - database to Cloud Spanner + gcloud alpha spanner migrate schema - migrate schema from a source database + to Cloud Spanner SYNOPSIS - gcloud alpha spanner migration schema --source=SOURCE [--dry-run] + gcloud alpha spanner migrate schema --source=SOURCE [--dry-run] [--log-level=LOG_LEVEL] [--prefix=PREFIX] [--source-profile=SOURCE_PROFILE] [--target=TARGET] [--target-profile=TARGET_PROFILE] [GCLOUD_WIDE_FLAG ...] @@ -14,7 +14,7 @@ DESCRIPTION EXAMPLES To generate schema file from the source database: - $ gcloud alpha spanner migration schema --source=postgresql < \ + $ gcloud alpha spanner migrate schema --source=postgresql < \ ~/cart.pg_dump REQUIRED FLAGS diff --git a/gcloud/alpha/spanner/migration/schema-and-data b/gcloud/alpha/spanner/migrate/schema-and-data similarity index 86% rename from gcloud/alpha/spanner/migration/schema-and-data rename to gcloud/alpha/spanner/migrate/schema-and-data index d7bd49241..fff9d7e69 100644 --- a/gcloud/alpha/spanner/migration/schema-and-data +++ b/gcloud/alpha/spanner/migrate/schema-and-data @@ -1,9 +1,9 @@ NAME - gcloud alpha spanner migration schema-and-data - migrate data from a source + gcloud alpha spanner migrate schema-and-data - migrate data from a source database to Cloud Spanner given a schema SYNOPSIS - gcloud alpha spanner migration schema-and-data --source=SOURCE [--dry-run] + gcloud alpha spanner migrate schema-and-data --source=SOURCE [--dry-run] [--log-level=LOG_LEVEL] [--prefix=PREFIX] [--skip-foreign-keys] [--source-profile=SOURCE_PROFILE] [--target=TARGET] [--target-profile=TARGET_PROFILE] [--write-limit=WRITE_LIMIT] @@ -16,9 +16,8 @@ DESCRIPTION EXAMPLES To generate schema and copy data to Cloud Spanner from a source database: - $ gcloud alpha spanner migration schema-and-data \ - --source=postgresql < ~/cart.pg_dump \ - --target-profile='instance=spanner-instance' + $ gcloud alpha spanner migrate schema-and-data --source=postgresql \ + < ~/cart.pg_dump --target-profile='instance=spanner-instance' REQUIRED FLAGS --source=SOURCE diff --git a/gcloud/alpha/spanner/migration/web b/gcloud/alpha/spanner/migrate/web similarity index 65% rename from gcloud/alpha/spanner/migration/web rename to gcloud/alpha/spanner/migrate/web index fe0ee4bf1..2583eafb7 100644 --- a/gcloud/alpha/spanner/migration/web +++ b/gcloud/alpha/spanner/migrate/web @@ -1,9 +1,10 @@ NAME - gcloud alpha spanner migration web - run the web UI assistant for schema + gcloud alpha spanner migrate web - run the web UI assistant for schema migrations SYNOPSIS - gcloud alpha spanner migration web [GCLOUD_WIDE_FLAG ...] + gcloud alpha spanner migrate web [--open] [--port=PORT] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Run the web UI assistant for schema migrations. @@ -11,7 +12,14 @@ DESCRIPTION EXAMPLES To run the web UI assistant: - $ gcloud alpha spanner migration web + $ gcloud alpha spanner migrate web + +FLAGS + --open + Open the Spanner migration tool web interface in the default browser. + + --port=PORT + The port in which Spanner migration tool will run, defaults to 8080 GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index 54af2de2b..8e43bca46 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -50,6 +50,8 @@ SYNOPSIS [--storage-size=STORAGE_SIZE] [--storage-type=STORAGE_TYPE] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] [--time-zone=TIME_ZONE] [--timeout=TIMEOUT; default=3600] + [--allowed-psc-projects=PROJECT,[PROJECT,...] + --enable-private-service-connect] [--disk-encryption-key=DISK_ENCRYPTION_KEY : --disk-encryption-key-keyring=DISK_ENCRYPTION_KEY_KEYRING --disk-encryption-key-location=DISK_ENCRYPTION_KEY_LOCATION @@ -444,6 +446,16 @@ FLAGS specified. By default, set to 3600s. To wait indefinitely, set to unlimited. + --allowed-psc-projects=PROJECT,[PROJECT,...] + A comma-separated list of projects. Each project in this list may be + represented by a project number (numeric) or by a project id + (alphanumeric). This will allow PSC connections to be established from + specified consumer projects. This can be set only when PSC is enabled. + + --enable-private-service-connect + When the flag is set, a Cloud SQL instance will be created with PSC + enabled. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the instance. The 'Compute Engine Service Agent' service account must hold permission 'Cloud KMS CryptoKey diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index 780ad1596..67c68c0ea 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -43,6 +43,8 @@ SYNOPSIS [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] [--storage-size=STORAGE_SIZE] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] [--update-labels=[KEY=VALUE,...]] + [--allowed-psc-projects=PROJECT,[PROJECT,...] + | --clear-allowed-psc-projects] [--authorized-gae-apps=APP,[APP,...] | --clear-gae-apps] [--authorized-networks=NETWORK,[NETWORK,...] | --clear-authorized-networks] @@ -372,6 +374,19 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + At most one of these can be specified: + + --allowed-psc-projects=PROJECT,[PROJECT,...] + A comma-separated list of projects. Each project in this list may be + represented by a project number (numeric) or by a project id + (alphanumeric). This will allow PSC connections to be established + from specified consumer projects. This can be set only when PSC is + enabled. + + --clear-allowed-psc-projects + This will clear the project allowlist of PSC, disallowing all + projects from creating new PSC bindings to the instance. + At most one of these can be specified: --authorized-gae-apps=APP,[APP,...] diff --git a/gcloud/alpha/sql/instances/reencrypt b/gcloud/alpha/sql/instances/reencrypt index ca90e854c..40d4d006f 100644 --- a/gcloud/alpha/sql/instances/reencrypt +++ b/gcloud/alpha/sql/instances/reencrypt @@ -34,7 +34,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud sql instances reencrypt $ gcloud beta sql instances reencrypt diff --git a/gcloud/alpha/storage/buckets/update b/gcloud/alpha/storage/buckets/update index 70631a68a..bd71f954e 100644 --- a/gcloud/alpha/storage/buckets/update +++ b/gcloud/alpha/storage/buckets/update @@ -220,27 +220,27 @@ FLAGS At most one of these can be specified: --clear-log-bucket - Clears logging bucket receiving the usage current bucket's data and - disables usage logging. + Disables usage and storage logging for the bucket specified in the + overall update command. --log-bucket=LOG_BUCKET - Enables usage logging of the bucket, outputting log files to the - specified logging_bucket in this flag. Cloud Storage doesn't validate - the existence of the bucket receiving logs. In addition to enabling - logging on your bucket, you will also need to grant - cloud-storage-analytics@google.com write access to the log bucket. + Enables usage and storage logging for the bucket specified in the + overall update command, outputting log files to the bucket specified + in this flag. Cloud Storage does not validate the existence of the + bucket receiving logs. In addition to enabling logging on your + bucket, you also need to grant cloud-storage-analytics@google.com + write access to the log bucket. At most one of these can be specified: --clear-log-object-prefix - Clears prefix used to determine what usage data to send to logging - bucket. + Clears the prefix used to determine the naming of log objects in the + logging bucket. --log-object-prefix=LOG_OBJECT_PREFIX - Specifies the object prefix for logging activity to the log bucket. - The default prefix is the bucket name. All read and write activity to - objects in the bucket will be logged for objects matching the prefix. - If usage logging is not enabled this flag will have no effect. + Specifies a prefix for the names of logs generated in the log bucket. + The default prefix is the bucket name. If logging is not enabled, + this flag has no effect. At most one of these can be specified: diff --git a/gcloud/artifacts/help b/gcloud/artifacts/help index 6f1eb4fcb..b2a4db688 100644 --- a/gcloud/artifacts/help +++ b/gcloud/artifacts/help @@ -42,6 +42,9 @@ GROUPS repositories Manage Artifact Registry repositories. + sbom + Manage Artifact SBOMs. + settings Manage Artifact Registry project settings. @@ -55,6 +58,9 @@ GROUPS Manage Artifact Registry VPC Service Controls configuration for remote repositories. + vulnerabilities + Manage Artifact Vulnerabilities. + yum Manage Artifact Registry RPM packages. diff --git a/gcloud/artifacts/repositories/create b/gcloud/artifacts/repositories/create index b7c82d80e..4c9a41ad4 100644 --- a/gcloud/artifacts/repositories/create +++ b/gcloud/artifacts/repositories/create @@ -12,6 +12,7 @@ SYNOPSIS [--remote-python-repo=REMOTE_PYTHON_REPO] [--remote-repo-config-desc=REMOTE_REPO_CONFIG_DESC] [--upstream-policy-file=FILE] [--version-policy=VERSION_POLICY] + [--allow-sbom-generation | --disable-sbom-generation] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -171,6 +172,14 @@ OPTIONAL FLAGS snapshot (Maven only) The repository accepts snapshot versions only. + At most one of these can be specified: + + --allow-sbom-generation + Allow SBOM generation on the repository. + + --disable-sbom-generation + Disable SBOM generation on the repository. + 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/artifacts/repositories/update b/gcloud/artifacts/repositories/update index 5dd772e51..631ac937e 100644 --- a/gcloud/artifacts/repositories/update +++ b/gcloud/artifacts/repositories/update @@ -6,6 +6,7 @@ SYNOPSIS gcloud artifacts repositories update (REPOSITORY : --location=LOCATION) [--description=DESCRIPTION] [--immutable-tags] [--update-labels=[KEY=VALUE,...]] [--upstream-policy-file=FILE] + [--allow-sbom-generation | --disable-sbom-generation] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -82,6 +83,14 @@ FLAGS "priority": 1 }, { "id": "test2", "repository": "projects/p2/locations/us-west2/repository/repo2", "priority": 2 } ] + At most one of these can be specified: + + --allow-sbom-generation + Allow SBOM generation on the repository. + + --disable-sbom-generation + Disable SBOM generation on the repository. + At most one of these can be specified: --clear-labels diff --git a/gcloud/artifacts/sbom/export b/gcloud/artifacts/sbom/export new file mode 100644 index 000000000..ef25466f9 --- /dev/null +++ b/gcloud/artifacts/sbom/export @@ -0,0 +1,28 @@ +NAME + gcloud artifacts sbom export - export SBOM files + +SYNOPSIS + gcloud artifacts sbom export --uri=URI [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Export SBOM files. + +EXAMPLES + To export an SBOM file for the Artifact Registry image with URI + "us-west1-docker.pkg.dev/my-project/my-repository/busy-box@sha256:abcxyz": + + $ gcloud artifacts sbom export \ + --uri=us-west1-docker.pkg.dev/my-project/my-repository/\ + busy-box@sha256:abcxyz + +REQUIRED FLAGS + --uri=URI + The URI of the Artifact Registry image the SBOM is exported for. + +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. diff --git a/gcloud/artifacts/sbom/help b/gcloud/artifacts/sbom/help new file mode 100644 index 000000000..e928076b1 --- /dev/null +++ b/gcloud/artifacts/sbom/help @@ -0,0 +1,25 @@ +NAME + gcloud artifacts sbom - manage Artifact SBOMs + +SYNOPSIS + gcloud artifacts sbom COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Artifact SBOMs. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + export + Export SBOM files. + + list + List SBOM file references. + + load + Upload an SBOM file and create a reference occurrence. diff --git a/gcloud/artifacts/sbom/list b/gcloud/artifacts/sbom/list new file mode 100644 index 000000000..12949e276 --- /dev/null +++ b/gcloud/artifacts/sbom/list @@ -0,0 +1,93 @@ +NAME + gcloud artifacts sbom list - list SBOM file references + +SYNOPSIS + gcloud artifacts sbom list + [--dependency=DEPENDENCY | --resource=RESOURCE + | --resource-prefix=RESOURCE_PREFIX] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]; default="occ.create_time"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List SBOM file references. + +EXAMPLES + To list SBOM file references: + + $ gcloud artifacts sbom list + + To list SBOM file references related to the image with the tag + "us-east1-docker.pkg.dev/project/repo/my-image:1.0": + + $ gcloud artifacts sbom list \ + --resource="us-east1-docker.pkg.dev/project/repo/my-image:1.0" + + To list SBOM file references related to the image with the digest + "us-east1-docker.pkg.dev/project/repo/my-image@sha256:88b205d7995332e10e836514fbfd59ecaf8976fc15060cd66e85cdcebe7fb356": + + $ gcloud artifacts sbom list \ + --resource="us-east1-docker.pkg.dev/project/repo/my-image@sha256\ + :88b205d7995332e10e836514fbfd59ecaf8976fc15060cd66e85cdcebe7fb356" + + To list SBOM file references related to the images with the resource path + prefix "us-east1-docker.pkg.dev/project/repo": + + $ gcloud artifacts sbom list \ + --resource-prefix="us-east1-docker.pkg.dev/project/repo" + + To list SBOM file references generated when the images were pushed to + Artifact Registry and related to the installed package dependency "perl": + + $ gcloud artifacts sbom list --dependency="perl" + +FLAGS + At most one of these can be specified: + + --dependency=DEPENDENCY + List SBOM file references generated when the images were pushed to + Artifact Registry and related to the installed package dependency. + See https://cloud.google.com/container-analysis/docs/scanning-types + for supported packages. + + --resource=RESOURCE + List SBOM file references related to the image resource uri. + + --resource-prefix=RESOURCE_PREFIX + List SBOM file references related to the resource uri with the + resource path prefix. + +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,...]; default="occ.create_time" + 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. The + default is occ.create_time. + +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. diff --git a/gcloud/artifacts/sbom/load b/gcloud/artifacts/sbom/load new file mode 100644 index 000000000..5055274ea --- /dev/null +++ b/gcloud/artifacts/sbom/load @@ -0,0 +1,66 @@ +NAME + gcloud artifacts sbom load - upload an SBOM file and create a reference + occurrence + +SYNOPSIS + gcloud artifacts sbom load --source=SOURCE --uri=ARTIFACT_URI + [--destination=DESTINATION] [--kms-key-version=KMS_KEY_VERSION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Upload an SBOM file and create a reference occurrence. + +EXAMPLES + To upload an SBOM file at /path/to/sbom.json for a Docker image in Artifact + Registry: + + $ gcloud artifacts sbom load --source=/path/to/sbom.json \ + --uri=us-west1-docker.pkg.dev/my-project/my-repository/\ + busy-box@sha256:abcxyz + + To upload an SBOM file at /path/to/sbom.json for a Docker image with a KMS + key version to sign the created SBOM reference: + + $ gcloud artifacts sbom load --source=/path/to/sbom.json \ + --uri=us-west1-docker.pkg.dev/my-project/my-repository/\ + busy-box@sha256:abcxyz \ + --kms-key-version=projects/my-project/locations/us-west1/\ + keyRings/my-key-ring/cryptoKeys/my-key/cryptoKeyVersions/1 + + To upload an SBOM file at /path/to/sbom.json for a Docker image from a + Docker registry: + + $ gcloud artifacts sbom load --source=/path/to/sbom.json \ + --uri=my-docker-registry/my-image@sha256:abcxyz \ + --destination=gs://my-cloud-storage-bucket + +REQUIRED FLAGS + --source=SOURCE + The SBOM file for uploading. + + --uri=ARTIFACT_URI + The URI of the artifact the SBOM is generated from. The URI can be a + Docker image from any Docker registries. A URI provided with a tag + (e.g. [IMAGE]:[TAG]) will be resolved into a URI with a digest + ([IMAGE]@sha256:[DIGEST]). When passing an image which is not from + Artifact Registry or Container Registry with a tag, only public images + can be resolved. Also, when passing an image which is not from Artifact + Registry or Container Registry, the --destination flag is required. + +OPTIONAL FLAGS + --destination=DESTINATION + The storage path will be used to store the SBOM file. Currently only + supports Cloud Storage paths start with 'gs://'. + + --kms-key-version=KMS_KEY_VERSION + Cloud KMS key version to sign the SBOM reference. The key version + provided should be the resource ID in the format of + projects/[KEY_PROJECT_ID]/locations/[LOCATION]/keyRings/[RING_NAME]/cryptoKeys/[KEY_NAME]/cryptoKeyVersions/[KEY_VERSION]. + +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. diff --git a/gcloud/artifacts/vulnerabilities/help b/gcloud/artifacts/vulnerabilities/help new file mode 100644 index 000000000..be563ec5b --- /dev/null +++ b/gcloud/artifacts/vulnerabilities/help @@ -0,0 +1,23 @@ +NAME + gcloud artifacts vulnerabilities - manage Artifact Vulnerabilities + +SYNOPSIS + gcloud artifacts vulnerabilities COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Artifact Vulnerabilities. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + Command for listing vulnerabilities. To see all fields, use + --format=json. + + load-vex + Load VEX data from a file. diff --git a/gcloud/artifacts/vulnerabilities/list b/gcloud/artifacts/vulnerabilities/list new file mode 100644 index 000000000..5b5cd7e9a --- /dev/null +++ b/gcloud/artifacts/vulnerabilities/list @@ -0,0 +1,70 @@ +NAME + gcloud artifacts vulnerabilities list - command for listing + vulnerabilities. To see all fields, use --format=json + +SYNOPSIS + gcloud artifacts vulnerabilities list URI + [--occurrence-filter=OCCURRENCE_FILTER] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Command for listing vulnerabilities. To see all fields, use --format=json. + +EXAMPLES + To list vulnerabilities for an artifact, run: + + $ gcloud artifacts vulnerabilities list \ + us-east1-docker.pkg.dev/project123/repository123/\ + someimage@sha256:49765698074d6d7baa82f + +POSITIONAL ARGUMENTS + URI + An URI identifying a container image or package in Artifact Registry or + Google Cloud Registry. + +FLAGS + --occurrence-filter=OCCURRENCE_FILTER + A filter for the occurrences which will be summarized. See link for + officially supported filters: + https://cloud.google.com/container-analysis/docs/os-scanning-automatically#filtering + +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. diff --git a/gcloud/artifacts/vulnerabilities/load-vex b/gcloud/artifacts/vulnerabilities/load-vex new file mode 100644 index 000000000..d754920b0 --- /dev/null +++ b/gcloud/artifacts/vulnerabilities/load-vex @@ -0,0 +1,43 @@ +NAME + gcloud artifacts vulnerabilities load-vex - load VEX data from a file + +SYNOPSIS + gcloud artifacts vulnerabilities load-vex --source=SOURCE --uri=URI + [--project=PROJECT] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Load VEX data from a file. + +EXAMPLES + To load a CSAF security advisory file given an artifact in Artifact + Registry and the file on disk, run: + + $ gcloud artifacts vulnerabilities load-vex \ + --uri=us-east1-docker.pkg.dev/project123/repository123/\ + someimage@sha256:49765698074d6d7baa82f --source=/path/to/vex/file + + To load a CSAF security advisory file given an artifact with a tag and a + file on disk, run: + + $ gcloud artifacts vulnerabilities load-vex \ + --uri=us-east1-docker.pkg.dev/project123/repository123/\ + someimage:latest --source=/path/to/vex/file + +REQUIRED FLAGS + --source=SOURCE + The path of the VEX file. + + --uri=URI + The path of the artifact in Artifact Registry. + +OPTIONAL FLAGS + --project=PROJECT + The parent project to load security advisory into. + +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. diff --git a/gcloud/beta/compute/commitments/create b/gcloud/beta/compute/commitments/create index 347271807..04ac5bf85 100644 --- a/gcloud/beta/compute/commitments/create +++ b/gcloud/beta/compute/commitments/create @@ -15,7 +15,8 @@ SYNOPSIS --machine-type=MACHINE_TYPE --maintenance-interval=MAINTENANCE_INTERVAL --min-cpu-platform=MIN_CPU_PLATFORM --require-specific-reservation - --vm-count=VM_COUNT --share-setting=SHARE_SETTING + --resource-policies=[KEY=VALUE,...] --vm-count=VM_COUNT + --share-setting=SHARE_SETTING --share-with=SHARE_WITH,[SHARE_WITH,...]]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -201,6 +202,12 @@ OPTIONAL FLAGS this reservation by name using --reservation-affinity=specific can consume from this reservation. + --resource-policies=[KEY=VALUE,...] + The resource policies to include in this reservation. If you omit + this flag, no resource policies are added. You can specify any + string as the key, and specify the name of a resource policy as + the value. + --vm-count=VM_COUNT The number of VM instances that are allocated to this reservation. The value of this field must be an int in the range diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index 4f004855b..358f910c2 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -25,7 +25,9 @@ SYNOPSIS [--local-ssd=[device-name=DEVICE-NAME], [interface=INTERFACE],[size=SIZE]] [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] - [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] + [--machine-type=MACHINE_TYPE] + [--maintenance-interval=MAINTENANCE_INTERVAL] + [--maintenance-policy=MAINTENANCE_POLICY] [--max-run-duration=MAX_RUN_DURATION] [--mesh=[gke-cluster=GKE-CLUSTER],[workload=WORKLOAD]] [--metadata=KEY=VALUE,[KEY=VALUE,...]] @@ -467,6 +469,13 @@ FLAGS available machine types, run 'gcloud compute machine-types list'. If unspecified, the default type is n1-standard-1. + --maintenance-interval=MAINTENANCE_INTERVAL + Specifies the frequency of planned maintenance events. + MAINTENANCE_INTERVAL must be (only one value is supported): + + PERIODIC + PERIODIC means the VM is a Stable Fleet VM. + --maintenance-policy=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see diff --git a/gcloud/beta/compute/instances/delete-access-config b/gcloud/beta/compute/instances/delete-access-config index 8e813c72c..d612463ed 100644 --- a/gcloud/beta/compute/instances/delete-access-config +++ b/gcloud/beta/compute/instances/delete-access-config @@ -12,7 +12,10 @@ DESCRIPTION (BETA) gcloud beta compute instances delete-access-config is used to delete access configurations from network interfaces of Compute Engine virtual machines. Access configurations let you assign a public, external IP to a - virtual machine. + virtual machine. The delete-access-config operation removes external IP + from the instance interface. If there is traffic routed to the external IP, + after deleting the access config operation, traffic to the external IP will + not reach the VM anymore. EXAMPLES To remove the externally accessible IP from a virtual machine named diff --git a/gcloud/beta/compute/instances/ops-agents/policies/create b/gcloud/beta/compute/instances/ops-agents/policies/create index 7ba3b63c9..0971afe67 100644 --- a/gcloud/beta/compute/instances/ops-agents/policies/create +++ b/gcloud/beta/compute/instances/ops-agents/policies/create @@ -226,6 +226,7 @@ REQUIRED FLAGS OS Short Name OS Version centos 8 centos 7 + debian 12 debian 11 debian 10 debian 9 diff --git a/gcloud/beta/compute/instances/ops-agents/policies/update b/gcloud/beta/compute/instances/ops-agents/policies/update index f859b3db6..d17e98fec 100644 --- a/gcloud/beta/compute/instances/ops-agents/policies/update +++ b/gcloud/beta/compute/instances/ops-agents/policies/update @@ -263,6 +263,7 @@ FLAGS OS Short Name OS Version centos 8 centos 7 + debian 12 debian 11 debian 10 debian 9 diff --git a/gcloud/beta/compute/reservations/update b/gcloud/beta/compute/reservations/update index 57ba2c396..d64c4445e 100644 --- a/gcloud/beta/compute/reservations/update +++ b/gcloud/beta/compute/reservations/update @@ -13,23 +13,27 @@ DESCRIPTION (BETA) Update Compute Engine reservations. EXAMPLES - To add my-project to the list of projects that are shared with a Compute - Engine reservation, my-reservation in zone: us-central1-a, run: + To add project-1,project-2,project-3 to the list of projects that are + shared with a Compute Engine reservation, my-reservation in zone: + us-central1-a, run: $ gcloud beta compute reservations update my-reservation \ - --add-share-with=my-project --zone=us-central1-a + --add-share-with=project-1,project-2,project-3 \ + --zone=us-central1-a - To remove my-project from the list of projects that are shared with a - Compute Engine reservation, my-reservation in zone: us-central1-a, run: + To remove project-1,project-2,project-3 from the list of projects that are + shared with a Compute Engine reservation, my-reservation in zone: + us-central1-a, run: $ gcloud beta compute reservations update my-reservation \ - --remove-share-with=my-project --zone=us-central1-a + --remove-share-with=project-1,project-2,project-3 \ + --zone=us-central1-a To update the entire list of projects that are shared with a Compute Engine reservation, my-reservation in zone: us-central1-a, run: $ gcloud beta compute reservations update my-reservation \ - --share-with=my-project --zone=us-central1-a + --share-with=project-1,project-2,project-3 --zone=us-central1-a To update the number of reserved VM instances to 500 for a Compute Engine reservation, my-reservation in zone: us-central1-a, run: diff --git a/gcloud/beta/compute/security-policies/add-layer7-ddos-defense-threshold-config b/gcloud/beta/compute/security-policies/add-layer7-ddos-defense-threshold-config new file mode 100644 index 000000000..4745275a6 --- /dev/null +++ b/gcloud/beta/compute/security-policies/add-layer7-ddos-defense-threshold-config @@ -0,0 +1,72 @@ +NAME + gcloud beta compute security-policies + add-layer7-ddos-defense-threshold-config - add a layer7 ddos defense + threshold config to a Compute Engine security policy + +SYNOPSIS + gcloud beta compute security-policies + add-layer7-ddos-defense-threshold-config NAME + --threshold-config-name=THRESHOLD_CONFIG_NAME + [--auto-deploy-confidence-threshold=AUTO_DEPLOY_CONFIDENCE_THRESHOLD] + [--auto-deploy-expiration-sec=AUTO_DEPLOY_EXPIRATION_SEC] + [--auto-deploy-impacted-baseline-threshold=AUTO_DEPLOY_IMPACTED_BASELINE_THRESHOLD] + [--auto-deploy-load-threshold=AUTO_DEPLOY_LOAD_THRESHOLD] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute security-policies + add-layer7-ddos-defense-threshold-config is used to add layer7 ddos defense + threshold configs to security policies. + +EXAMPLES + To add a layer7 ddos defense threshold config run the following command: + + $ gcloud beta compute security-policies \ + add-layer7-ddos-defense-threshold-config NAME \ + --threshold-config-name=my-threshold-config-name \ + --auto-deploy-load-threshold=0.7 \ + --auto-deploy-confidence-threshold=0.8 \ + --auto-deploy-impacted-baseline-threshold=0.1 \ + --auto-deploy-expiration-sec=4800 + +POSITIONAL ARGUMENTS + NAME + Name of the security policy to update. + +REQUIRED FLAGS + --threshold-config-name=THRESHOLD_CONFIG_NAME + The name for the threshold config. + +OPTIONAL FLAGS + --auto-deploy-confidence-threshold=AUTO_DEPLOY_CONFIDENCE_THRESHOLD + The threshold of the confidence of an identified attack over which + auto-deploy takes action. + + --auto-deploy-expiration-sec=AUTO_DEPLOY_EXPIRATION_SEC + The duration of actions, if any, taken by auto-deploy. + + --auto-deploy-impacted-baseline-threshold=AUTO_DEPLOY_IMPACTED_BASELINE_THRESHOLD + The threshold on the estimated impact to the baseline traffic of a + suggested mitigation, below which auto-deploy takes action. + + --auto-deploy-load-threshold=AUTO_DEPLOY_LOAD_THRESHOLD + The threshold on backend's load over which auto-deploy takes action. + +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 compute security-policies \ + add-layer7-ddos-defense-threshold-config + + $ gcloud alpha compute security-policies \ + add-layer7-ddos-defense-threshold-config + diff --git a/gcloud/beta/compute/security-policies/help b/gcloud/beta/compute/security-policies/help index a3c40a325..41f987a34 100644 --- a/gcloud/beta/compute/security-policies/help +++ b/gcloud/beta/compute/security-policies/help @@ -33,6 +33,10 @@ GROUPS COMMANDS COMMAND is one of the following: + add-layer7-ddos-defense-threshold-config + (BETA) Add a layer7 ddos defense threshold config to a Compute Engine + security policy. + add-user-defined-field (BETA) Add a user defined field to a Compute Engine security policy. @@ -57,6 +61,10 @@ COMMANDS list-preconfigured-expression-sets (BETA) List all available preconfigured expression sets. + remove-layer7-ddos-defense-threshold-config + (BETA) Remove a layer7 ddos defense threshold config from a Compute + Engine security policy. + remove-user-defined-field (BETA) Remove a user defined field from a Compute Engine security policy. diff --git a/gcloud/beta/compute/security-policies/remove-layer7-ddos-defense-threshold-config b/gcloud/beta/compute/security-policies/remove-layer7-ddos-defense-threshold-config new file mode 100644 index 000000000..3086564e6 --- /dev/null +++ b/gcloud/beta/compute/security-policies/remove-layer7-ddos-defense-threshold-config @@ -0,0 +1,48 @@ +NAME + gcloud beta compute security-policies + remove-layer7-ddos-defense-threshold-config - remove a layer7 ddos + defense threshold config from a Compute Engine security policy + +SYNOPSIS + gcloud beta compute security-policies + remove-layer7-ddos-defense-threshold-config NAME + --threshold-config-name=THRESHOLD_CONFIG_NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute security-policies + remove-layer7-ddos-defense-threshold-config is used to remove layer7 ddos + defense threshold configs from security policies. + +EXAMPLES + To remove a layer7 ddos defense threshold config run the following command: + + $ gcloud beta compute security-policies \ + remove-layer7-ddos-defense-threshold-config NAME \ + --threshold-config-name=my-threshold-config-name + +POSITIONAL ARGUMENTS + NAME + Name of the security policy to update. + +REQUIRED FLAGS + --threshold-config-name=THRESHOLD_CONFIG_NAME + The name for the threshold 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. These + variants are also available: + + $ gcloud compute security-policies \ + remove-layer7-ddos-defense-threshold-config + + $ gcloud alpha compute security-policies \ + remove-layer7-ddos-defense-threshold-config + diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 3d9dbc77f..73217e5db 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -393,7 +393,8 @@ FLAGS --disk-type=DISK_TYPE Type of the node VM boot disk. For version 1.24.0+, defaults to pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE - must be one of: pd-standard, pd-ssd, pd-balanced. + must be one of: pd-standard, pd-ssd, pd-balanced, hyperdisk-balanced, + hyperdisk-extreme, hyperdisk-throughput. --enable-autorepair Enable node autorepair feature for a cluster's default node pool(s). diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index 5052fb67e..1f9699249 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -8,7 +8,6 @@ SYNOPSIS | --autoscaling-profile=AUTOSCALING_PROFILE | --clear-fleet-project | --complete-credential-rotation | --complete-ip-rotation | --database-encryption-key=DATABASE_ENCRYPTION_KEY - | --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-database-encryption | --disable-default-snat | --disable-workload-identity | --enable-autoscaling | --enable-cost-allocation | --enable-fleet @@ -60,7 +59,8 @@ SYNOPSIS --resource-usage-bigquery-dataset=RESOURCE_USAGE_BIGQUERY_DATASET | --cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN --cluster-dns-scope=CLUSTER_DNS_SCOPE - | --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics + | --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics | [--enable-autoprovisioning : --autoprovisioning-config-file=AUTOPROVISIONING_CONFIG_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE @@ -167,35 +167,6 @@ REQUIRED FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. - --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - Select Advanced Datapath Observability mode for the cluster. Defaults - to DISABLED. - - Advanced Datapath Observability allows for a real-time view into - pod-to-pod traffic within your cluster. - - Examples: - - $ gcloud beta container clusters update \ - --dataplane-v2-observability-mode=DISABLED - - $ gcloud beta container clusters update \ - --dataplane-v2-observability-mode=INTERNAL_VPC_LB - - $ gcloud beta container clusters update \ - --dataplane-v2-observability-mode=EXTERNAL_LB - - DATAPLANE_V2_OBSERVABILITY_MODE must be one of: - - DISABLED - Disables Advanced Datapath Observability. - EXTERNAL_LB - Makes Advanced Datapath Observability available to the external - network. - INTERNAL_VPC_LB - Makes Advanced Datapath Observability available from the VPC - network. - --disable-database-encryption Disable database encryption. @@ -921,6 +892,35 @@ REQUIRED FLAGS vpc Configures the Cloud DNS zone to be private to the VPC Network. + --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + Select Advanced Datapath Observability mode for the cluster. Defaults + to DISABLED. + + Advanced Datapath Observability allows for a real-time view into + pod-to-pod traffic within your cluster. + + Examples: + + $ gcloud beta container clusters update \ + --dataplane-v2-observability-mode=DISABLED + + $ gcloud beta container clusters update \ + --dataplane-v2-observability-mode=INTERNAL_VPC_LB + + $ gcloud beta container clusters update \ + --dataplane-v2-observability-mode=EXTERNAL_LB + + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: + + DISABLED + Disables Advanced Datapath Observability. + EXTERNAL_LB + Makes Advanced Datapath Observability available to the external + network. + INTERNAL_VPC_LB + Makes Advanced Datapath Observability available from the VPC + network. + At most one of these can be specified: --disable-dataplane-v2-metrics diff --git a/gcloud/beta/container/fleet/memberships/bindings/create b/gcloud/beta/container/fleet/memberships/bindings/create index e848239ff..c38c2b0ce 100644 --- a/gcloud/beta/container/fleet/memberships/bindings/create +++ b/gcloud/beta/container/fleet/memberships/bindings/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta container fleet memberships bindings create (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + (--fleet=FLEET | --scope=SCOPE) [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -99,6 +100,15 @@ REQUIRED FLAGS To set the scope attribute: ▫ provide the argument --scope on the command line. +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, diff --git a/gcloud/beta/container/fleet/memberships/bindings/update b/gcloud/beta/container/fleet/memberships/bindings/update index 53c436ac9..b560e9ad1 100644 --- a/gcloud/beta/container/fleet/memberships/bindings/update +++ b/gcloud/beta/container/fleet/memberships/bindings/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta container fleet memberships bindings update (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + (--fleet=FLEET | --scope=SCOPE) [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -100,6 +101,37 @@ REQUIRED FLAGS To set the scope attribute: ▫ provide the argument --scope on the command line. +OPTIONAL FLAGS + --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. + + 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. + + 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 container fleet memberships bindings update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta container fleet memberships bindings 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. + 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/container/fleet/scopes/create b/gcloud/beta/container/fleet/scopes/create index ab5041beb..a3811854d 100644 --- a/gcloud/beta/container/fleet/scopes/create +++ b/gcloud/beta/container/fleet/scopes/create @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud beta container fleet scopes create SCOPE [--async] + [--labels=[KEY=VALUE,...]] [--namespace-labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -42,6 +43,17 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --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. + + --namespace-labels=[KEY=VALUE,...] + List of scope-level label KEY=VALUE pairs to add. + 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/container/fleet/scopes/update b/gcloud/beta/container/fleet/scopes/update index 325235423..9bf979625 100644 --- a/gcloud/beta/container/fleet/scopes/update +++ b/gcloud/beta/container/fleet/scopes/update @@ -3,6 +3,10 @@ NAME SYNOPSIS gcloud beta container fleet scopes update (SCOPE : --location=LOCATION) + [--update-labels=[KEY=VALUE,...]] + [--update-namespace-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] + [--clear-namespace-labels | --remove-namespace-labels=[KEY,...]] [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING --remove-upgrade-soaking-overrides | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE @@ -53,6 +57,65 @@ POSITIONAL ARGUMENTS ▸ global is the only supported location. FLAGS + --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. + + 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. + + --update-namespace-labels=[KEY=VALUE,...] + List of scope-level label KEY=VALUE pairs to update in the cluster + namespace. If a label exists, its value is modified. Otherwise, a new + label is' created. + + 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 container fleet scopes update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta container fleet scopes 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: + + --clear-namespace-labels + Remove all scope-level labels from the cluster namespace. If + --update-namespace-labels is also specified then + --clear-namespace-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta container fleet scopes update scope_name \ + --clear-namespace-labels + + To remove all existing scope-level labels and create two new labels, + foo and baz: + + $ gcloud beta container fleet scopes update scope_name \ + --clear-namespace-labels \ + --update-namespace-labels foo=bar,baz=qux + + --remove-namespace-labels=[KEY,...] + List of scope-level label keys to remove in the cluster namespace. If + a label does not exist it is silently ignored. If + --update-namespace-labels is also specified then + --update-namespace-labels is applied first. + Rollout Sequencing --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING diff --git a/gcloud/beta/container/hub/memberships/bindings/create b/gcloud/beta/container/hub/memberships/bindings/create index 53cb4fc67..e9a99390d 100644 --- a/gcloud/beta/container/hub/memberships/bindings/create +++ b/gcloud/beta/container/hub/memberships/bindings/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta container hub memberships bindings create (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + (--fleet=FLEET | --scope=SCOPE) [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -99,6 +100,15 @@ REQUIRED FLAGS To set the scope attribute: ▫ provide the argument --scope on the command line. +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, diff --git a/gcloud/beta/container/hub/memberships/bindings/update b/gcloud/beta/container/hub/memberships/bindings/update index df326b4a8..6a6272b90 100644 --- a/gcloud/beta/container/hub/memberships/bindings/update +++ b/gcloud/beta/container/hub/memberships/bindings/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta container hub memberships bindings update (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + (--fleet=FLEET | --scope=SCOPE) [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -100,6 +101,37 @@ REQUIRED FLAGS To set the scope attribute: ▫ provide the argument --scope on the command line. +OPTIONAL FLAGS + --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. + + 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. + + 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 container hub memberships bindings update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta container hub memberships bindings 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. + 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/container/hub/scopes/create b/gcloud/beta/container/hub/scopes/create index 0e8f987fa..7ccdde03b 100644 --- a/gcloud/beta/container/hub/scopes/create +++ b/gcloud/beta/container/hub/scopes/create @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud beta container hub scopes create SCOPE [--async] + [--labels=[KEY=VALUE,...]] [--namespace-labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -42,6 +43,17 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --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. + + --namespace-labels=[KEY=VALUE,...] + List of scope-level label KEY=VALUE pairs to add. + 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/container/hub/scopes/update b/gcloud/beta/container/hub/scopes/update index 6690cb188..80d32ce12 100644 --- a/gcloud/beta/container/hub/scopes/update +++ b/gcloud/beta/container/hub/scopes/update @@ -3,6 +3,10 @@ NAME SYNOPSIS gcloud beta container hub scopes update (SCOPE : --location=LOCATION) + [--update-labels=[KEY=VALUE,...]] + [--update-namespace-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] + [--clear-namespace-labels | --remove-namespace-labels=[KEY,...]] [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING --remove-upgrade-soaking-overrides | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE @@ -53,6 +57,65 @@ POSITIONAL ARGUMENTS ▸ global is the only supported location. FLAGS + --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. + + 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. + + --update-namespace-labels=[KEY=VALUE,...] + List of scope-level label KEY=VALUE pairs to update in the cluster + namespace. If a label exists, its value is modified. Otherwise, a new + label is' created. + + 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 container hub scopes update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta container hub scopes 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: + + --clear-namespace-labels + Remove all scope-level labels from the cluster namespace. If + --update-namespace-labels is also specified then + --clear-namespace-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta container hub scopes update scope_name \ + --clear-namespace-labels + + To remove all existing scope-level labels and create two new labels, + foo and baz: + + $ gcloud beta container hub scopes update scope_name \ + --clear-namespace-labels \ + --update-namespace-labels foo=bar,baz=qux + + --remove-namespace-labels=[KEY,...] + List of scope-level label keys to remove in the cluster namespace. If + a label does not exist it is silently ignored. If + --update-namespace-labels is also specified then + --update-namespace-labels is applied first. + Rollout Sequencing --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 6818c2928..9de1a6f2e 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -189,7 +189,8 @@ FLAGS --disk-type=DISK_TYPE Type of the node VM boot disk. For version 1.24.0+, defaults to pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE - must be one of: pd-standard, pd-ssd, pd-balanced. + must be one of: pd-standard, pd-ssd, pd-balanced, hyperdisk-balanced, + hyperdisk-extreme, hyperdisk-throughput. --enable-autoprovisioning Enables Cluster Autoscaler to treat the node pool as if it was diff --git a/gcloud/beta/dataflow/jobs/help b/gcloud/beta/dataflow/jobs/help index 0b6a8aebd..b95036ddd 100644 --- a/gcloud/beta/dataflow/jobs/help +++ b/gcloud/beta/dataflow/jobs/help @@ -38,6 +38,9 @@ COMMANDS show (BETA) Shows a short description of the given job. + update-options + (BETA) Update pipeline options on-the-fly for running Dataflow jobs. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/dataflow/jobs/update-options b/gcloud/beta/dataflow/jobs/update-options new file mode 100644 index 000000000..c21a71e9b --- /dev/null +++ b/gcloud/beta/dataflow/jobs/update-options @@ -0,0 +1,63 @@ +NAME + gcloud beta dataflow jobs update-options - update pipeline options + on-the-fly for running Dataflow jobs + +SYNOPSIS + gcloud beta dataflow jobs update-options JOB_ID + [--max-num-workers=MAX_NUM_WORKERS] [--min-num-workers=MIN_NUM_WORKERS] + [--region=REGION_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can modify properties of running Dataflow jobs. + Currently, only updating autoscaling settings for Streaming Engine jobs is + supported. + + Adjust the autoscaling settings for Streaming Engine Dataflow jobs by + providing at-least one of --min-num-workers or --max-num-workers (or both). + Allow a few minutes for the changes to take effect. + + Note that autoscaling settings can only be modified on-the-fly for + Streaming Engine jobs. Attempts to modify batch job or Streaming Appliance + jobs will fail. + +EXAMPLES + Modify autoscaling settings to scale between 5-10 workers: + + $ gcloud beta dataflow jobs update-options --min-num-workers=5 \ + --max-num-workers=10 + + Require a job to use at least 2 workers: + + $ gcloud beta dataflow jobs update-options --min-num-workers=2 + + Require a job to use at most 20 workers: + + $ gcloud beta dataflow jobs update-options --max-num-workers=20 + +POSITIONAL ARGUMENTS + JOB_ID + Job ID to operate on. + +FLAGS + --max-num-workers=MAX_NUM_WORKERS + Upper-bound for autoscaling, between 1-1000. Only supported for + streaming-engine jobs. + + --min-num-workers=MIN_NUM_WORKERS + Lower-bound for autoscaling, between 1-1000. Only supported for + streaming-engine jobs. + + --region=REGION_ID + Region ID of the job's regional endpoint. Defaults to 'us-central1'. + +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/network-management/connectivity-tests/create b/gcloud/beta/network-management/connectivity-tests/create index ede318091..dcbdc9463 100644 --- a/gcloud/beta/network-management/connectivity-tests/create +++ b/gcloud/beta/network-management/connectivity-tests/create @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta network-management connectivity-tests create CONNECTIVITY_TEST (--destination-cloud-sql-instance=DESTINATION_CLOUD_SQL_INSTANCE + --destination-forwarding-rule=DESTINATION_FORWARDING_RULE --destination-gke-master-cluster=DESTINATION_GKE_MASTER_CLUSTER --destination-instance=DESTINATION_INSTANCE --destination-ip-address=DESTINATION_IP_ADDRESS) @@ -63,6 +64,9 @@ REQUIRED FLAGS --destination-cloud-sql-instance=DESTINATION_CLOUD_SQL_INSTANCE A Cloud SQL instance URI as the destination endpoint. + --destination-forwarding-rule=DESTINATION_FORWARDING_RULE + A forwarding rule URI as the destination endpoint. + --destination-gke-master-cluster=DESTINATION_GKE_MASTER_CLUSTER A cluster URI for Google Kubernetes Engine master as the destination endpoint. diff --git a/gcloud/beta/network-management/connectivity-tests/update b/gcloud/beta/network-management/connectivity-tests/update index a1956e9f9..8dce29ed7 100644 --- a/gcloud/beta/network-management/connectivity-tests/update +++ b/gcloud/beta/network-management/connectivity-tests/update @@ -14,6 +14,8 @@ SYNOPSIS [--source-project=SOURCE_PROJECT] [--clear-destination-cloud-sql-instance | --destination-cloud-sql-instance=DESTINATION_CLOUD_SQL_INSTANCE] + [--clear-destination-forwarding-rule + | --destination-forwarding-rule=DESTINATION_FORWARDING_RULE] [--clear-destination-gke-master-cluster | --destination-gke-master-cluster=DESTINATION_GKE_MASTER_CLUSTER] [--clear-destination-instance @@ -116,6 +118,14 @@ FLAGS --destination-cloud-sql-instance=DESTINATION_CLOUD_SQL_INSTANCE A Cloud SQL instance URI as the destination endpoint. + At most one of these can be specified: + + --clear-destination-forwarding-rule + Clear existing destination forwarding rule. + + --destination-forwarding-rule=DESTINATION_FORWARDING_RULE + A forwarding rule URI as the destination endpoint. + At most one of these can be specified: --clear-destination-gke-master-cluster diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/add-override b/gcloud/beta/network-security/security-profiles/threat-prevention/add-override index 47ed46be2..b96f3038e 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/add-override +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/add-override @@ -8,7 +8,8 @@ SYNOPSIS (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) --action=ACTION (--severities=[SEVERITY_LEVEL,...] | --threat-ids=[THREAT-ID,...]) - [--async] [GCLOUD_WIDE_FLAG ...] + [--async] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Add severities or threat-ids to existing threat prevention profile @@ -84,6 +85,36 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. The default is False. + --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. + + 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. + + 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 network-security security-profiles threat-prevention \ + add-override --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta network-security security-profiles threat-prevention \ + add-override --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. + 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/network-security/security-profiles/threat-prevention/create b/gcloud/beta/network-security/security-profiles/threat-prevention/create index 073215f6a..5e3d90d43 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/create +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta network-security security-profiles threat-prevention create (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) - [--async] [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a new Security Profile with the given name. @@ -57,6 +58,14 @@ FLAGS --description=DESCRIPTION Brief description of the security profile + --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, diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/delete-override b/gcloud/beta/network-security/security-profiles/threat-prevention/delete-override index 3342fe1a4..d2e820895 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/delete-override +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/delete-override @@ -7,7 +7,8 @@ SYNOPSIS delete-override (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) (--severities=[SEVERITY_LEVEL,...] | --threat-ids=[THREAT-ID,...]) - [--async] [GCLOUD_WIDE_FLAG ...] + [--async] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) To delete existing severities or threat-ids of threat prevention @@ -78,6 +79,36 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. The default is False. + --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. + + 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. + + 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 network-security security-profiles threat-prevention \ + delete-override --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta network-security security-profiles threat-prevention \ + delete-override --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. + 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/network-security/security-profiles/threat-prevention/update-override b/gcloud/beta/network-security/security-profiles/threat-prevention/update-override index f856dadc9..09f60bb10 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/update-override +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/update-override @@ -8,7 +8,8 @@ SYNOPSIS (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) --action=ACTION (--severities=[SEVERITY_LEVEL,...] | --threat-ids=[THREAT-ID,...]) - [--async] [GCLOUD_WIDE_FLAG ...] + [--async] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) To update existing severities or threat-ids of threat prevention @@ -84,6 +85,36 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. The default is False. + --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. + + 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. + + 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 network-security security-profiles threat-prevention \ + update-override --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta network-security security-profiles threat-prevention \ + update-override --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. + 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/run/deploy b/gcloud/beta/run/deploy index a0e2d5c47..3c53cabd5 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -38,7 +38,9 @@ SYNOPSIS --binary-authorization=POLICY | --clear-binary-authorization --clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - --clear-key | --key=KEY --clear-post-key-revocation-action-type + --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] [--region=REGION | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION @@ -503,6 +505,39 @@ FLAGS --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 diff --git a/gcloud/beta/run/jobs/create b/gcloud/beta/run/jobs/create index 6c43e9bc8..ebd517fb6 100644 --- a/gcloud/beta/run/jobs/create +++ b/gcloud/beta/run/jobs/create @@ -14,6 +14,7 @@ SYNOPSIS [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] [--async | --execute-now --wait] [--env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...]] + [--network=NETWORK --network-tags=[TAG,...] --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -134,8 +135,8 @@ OPTIONAL FLAGS example, "10" is 10 seconds. --tasks=TASKS; default=1 - Number of tasks that must run to completion for the job to be - considered done. Use this flag to trigger multiple runs of the job. + Number of tasks that must run to completion for the execution to be + considered done. --vpc-connector=VPC_CONNECTOR Set a VPC connector for this resource. @@ -185,6 +186,26 @@ OPTIONAL FLAGS --set-env-vars=[KEY=VALUE,...] List of key-value pairs to set as environment variables. + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Run job 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. + + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the Cloud + Run job. To clear existing tags, use --clear-network-tags. + + --subnet=SUBNET + The VPC subnetwork that the Cloud Run job 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. + 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/run/jobs/deploy b/gcloud/beta/run/jobs/deploy index e1c152d52..1649abe58 100644 --- a/gcloud/beta/run/jobs/deploy +++ b/gcloud/beta/run/jobs/deploy @@ -16,7 +16,10 @@ SYNOPSIS [--clear-env-vars | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...]] - [--image=IMAGE | --source=SOURCE] [GCLOUD_WIDE_FLAG ...] + [--clear-network + | --network=NETWORK --subnet=SUBNET --clear-network-tags + | --network-tags=[TAG,...]] [--image=IMAGE | --source=SOURCE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates or updates a Cloud Run job. @@ -131,8 +134,8 @@ FLAGS example, "10" is 10 seconds. --tasks=TASKS; default=1 - Number of tasks that must run to completion for the job to be - considered done. Use this flag to trigger multiple runs of the job. + Number of tasks that must run to completion for the execution to be + considered done. --vpc-connector=VPC_CONNECTOR Set a VPC connector for this resource. @@ -196,6 +199,37 @@ FLAGS --update-env-vars=[KEY=VALUE,...] List of key-value pairs to set as environment variables. + At most one of these can be specified: + + --clear-network + Disconnect this Cloud Run job from the VPC network it is connected + to. + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Run job 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 job 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 job. + + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run job. To clear existing tags, use --clear-network-tags. + At most one of these can be specified: --image=IMAGE diff --git a/gcloud/beta/run/jobs/execute b/gcloud/beta/run/jobs/execute index 35d9eae14..7e9583b3a 100644 --- a/gcloud/beta/run/jobs/execute +++ b/gcloud/beta/run/jobs/execute @@ -2,7 +2,9 @@ NAME gcloud beta run jobs execute - execute a job SYNOPSIS - gcloud beta run jobs execute [JOB] [--region=REGION] [--async | --wait] + gcloud beta run jobs execute [JOB] [--args=[ARG,...]] [--region=REGION] + [--task-timeout=TASK_TIMEOUT] [--tasks=TASKS] + [--update-env-vars=[KEY=VALUE,...]] [--async | --wait] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -34,10 +36,37 @@ POSITIONAL ARGUMENTS ▸ specify the job name from an interactive prompt. FLAGS + --args=[ARG,...] + Comma-separated arguments passed to the command run by the container + image. If provided, an execution will be created with the input values. + Otherwise, the existing arguments of the job are used. + --region=REGION Region in which the resource can be found. Alternatively, set the property [run/region]. + --task-timeout=TASK_TIMEOUT + The existing maximum time (deadline) a job task attempt can run for. If + provided, an execution will be created with this value. Otherwise + existing maximum time of the job is used. In the case of retries, this + deadline applies to each attempt of a task. If the task attempt does + not complete within this time, it will be killed. 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. + + --tasks=TASKS + Number of tasks that must run to completion for the execution to be + considered done. If provided, an execution will be created with this + value. Otherwise the existing task count of the job is used. + + --update-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables overrides for + an execution of a job. If provided, an execution will be created with + the merge result of the input values and the existing environment + variables. New value overrides existing value if they have the same + key. If not provided, existing environment variables are used. + At most one of these can be specified: --async diff --git a/gcloud/beta/run/jobs/update b/gcloud/beta/run/jobs/update index b32e2f49a..24cff2ded 100644 --- a/gcloud/beta/run/jobs/update +++ b/gcloud/beta/run/jobs/update @@ -21,6 +21,9 @@ SYNOPSIS | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] + [--clear-network + | --network=NETWORK --subnet=SUBNET --clear-network-tags + | --network-tags=[TAG,...]] [--clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] @@ -121,8 +124,8 @@ FLAGS example, "10" is 10 seconds. --tasks=TASKS; default=1 - Number of tasks that must run to completion for the job to be - considered done. Use this flag to trigger multiple runs of the job. + Number of tasks that must run to completion for the execution to be + considered done. --vpc-connector=VPC_CONNECTOR Set a VPC connector for this resource. @@ -246,6 +249,37 @@ FLAGS List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. + At most one of these can be specified: + + --clear-network + Disconnect this Cloud Run job from the VPC network it is connected + to. + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Run job 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 job 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 job. + + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run job. To clear existing tags, use --clear-network-tags. + 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 diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 41f959ea9..8c1f71108 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -26,7 +26,9 @@ SYNOPSIS --binary-authorization=POLICY | --clear-binary-authorization --clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - --clear-key | --key=KEY --clear-post-key-revocation-action-type + --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-env-vars | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] @@ -332,6 +334,39 @@ FLAGS --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 diff --git a/gcloud/beta/services/api-keys/lookup b/gcloud/beta/services/api-keys/lookup index b03a96e85..41d87edbb 100644 --- a/gcloud/beta/services/api-keys/lookup +++ b/gcloud/beta/services/api-keys/lookup @@ -5,6 +5,9 @@ NAME SYNOPSIS gcloud beta services api-keys lookup KEY_STRING [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (BETA) Look up resource name of a key string. + EXAMPLES Look up resource name of a key string named my-key-string: @@ -23,8 +26,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud services api-keys lookup $ gcloud alpha services api-keys lookup diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index c9ccad99a..da5e6e0bb 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -50,6 +50,8 @@ SYNOPSIS [--storage-size=STORAGE_SIZE] [--storage-type=STORAGE_TYPE] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] [--time-zone=TIME_ZONE] [--timeout=TIMEOUT; default=3600] + [--allowed-psc-projects=PROJECT,[PROJECT,...] + --enable-private-service-connect] [--disk-encryption-key=DISK_ENCRYPTION_KEY : --disk-encryption-key-keyring=DISK_ENCRYPTION_KEY_KEYRING --disk-encryption-key-location=DISK_ENCRYPTION_KEY_LOCATION @@ -444,6 +446,16 @@ FLAGS specified. By default, set to 3600s. To wait indefinitely, set to unlimited. + --allowed-psc-projects=PROJECT,[PROJECT,...] + A comma-separated list of projects. Each project in this list may be + represented by a project number (numeric) or by a project id + (alphanumeric). This will allow PSC connections to be established from + specified consumer projects. This can be set only when PSC is enabled. + + --enable-private-service-connect + When the flag is set, a Cloud SQL instance will be created with PSC + enabled. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the instance. The 'Compute Engine Service Agent' service account must hold permission 'Cloud KMS CryptoKey diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index 209c9e48b..6569c3988 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -43,6 +43,8 @@ SYNOPSIS [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] [--storage-size=STORAGE_SIZE] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] [--update-labels=[KEY=VALUE,...]] + [--allowed-psc-projects=PROJECT,[PROJECT,...] + | --clear-allowed-psc-projects] [--authorized-gae-apps=APP,[APP,...] | --clear-gae-apps] [--authorized-networks=NETWORK,[NETWORK,...] | --clear-authorized-networks] @@ -372,6 +374,19 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + At most one of these can be specified: + + --allowed-psc-projects=PROJECT,[PROJECT,...] + A comma-separated list of projects. Each project in this list may be + represented by a project number (numeric) or by a project id + (alphanumeric). This will allow PSC connections to be established + from specified consumer projects. This can be set only when PSC is + enabled. + + --clear-allowed-psc-projects + This will clear the project allowlist of PSC, disallowing all + projects from creating new PSC bindings to the instance. + At most one of these can be specified: --authorized-gae-apps=APP,[APP,...] diff --git a/gcloud/beta/sql/instances/reencrypt b/gcloud/beta/sql/instances/reencrypt index b025bd274..e1abfe2ff 100644 --- a/gcloud/beta/sql/instances/reencrypt +++ b/gcloud/beta/sql/instances/reencrypt @@ -31,8 +31,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud sql instances reencrypt $ gcloud alpha sql instances reencrypt diff --git a/gcloud/bms/help b/gcloud/bms/help index f0171ac8f..253eb4b6d 100644 --- a/gcloud/bms/help +++ b/gcloud/bms/help @@ -27,6 +27,9 @@ GROUPS operations Manage operations in Bare Metal Solution. + os-images + Manage bare metal os images in Bare Metal Solution. + ssh-keys Manage SSH keys for Bare Metal Solution. diff --git a/gcloud/bms/os-images/help b/gcloud/bms/os-images/help new file mode 100644 index 000000000..be6c31976 --- /dev/null +++ b/gcloud/bms/os-images/help @@ -0,0 +1,25 @@ +NAME + gcloud bms os-images - manage bare metal os images in Bare Metal Solution + +SYNOPSIS + gcloud bms os-images COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage bare metal os images in Bare Metal Solution. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + List Bare Metal Solution OS images in a project. + +NOTES + This variant is also available: + + $ gcloud alpha bms os-images + diff --git a/gcloud/bms/os-images/list b/gcloud/bms/os-images/list new file mode 100644 index 000000000..f16b2c827 --- /dev/null +++ b/gcloud/bms/os-images/list @@ -0,0 +1,41 @@ +NAME + gcloud bms os-images list - list Bare Metal Solution OS images in a project + +SYNOPSIS + gcloud bms os-images list [--filter=EXPRESSION] [--limit=LIMIT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Bare Metal Solution OS images in a project. + +EXAMPLES + To list all OS images within the project, run: + + $ gcloud bms os-images list + +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, --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, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha bms os-images list + diff --git a/gcloud/compute/commitments/create b/gcloud/compute/commitments/create index ffb36eb6c..c5159304b 100644 --- a/gcloud/compute/commitments/create +++ b/gcloud/compute/commitments/create @@ -13,8 +13,8 @@ SYNOPSIS --accelerator=[count=COUNT],[type=TYPE] --local-ssd=[interface=INTERFACE],[size=SIZE] --machine-type=MACHINE_TYPE --min-cpu-platform=MIN_CPU_PLATFORM - --require-specific-reservation --vm-count=VM_COUNT - --share-setting=SHARE_SETTING + --require-specific-reservation --resource-policies=[KEY=VALUE,...] + --vm-count=VM_COUNT --share-setting=SHARE_SETTING --share-with=SHARE_WITH,[SHARE_WITH,...]]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -96,10 +96,11 @@ OPTIONAL FLAGS --type=TYPE; default="general-purpose" Type of commitment. memory-optimized indicates that the commitment is for memory-optimized VMs. TYPE must be one of: accelerator-optimized, - compute-optimized, compute-optimized-c2d, compute-optimized-c3, - general-purpose, general-purpose-e2, general-purpose-n2, - general-purpose-n2d, general-purpose-t2d, graphics-optimized, - memory-optimized, memory-optimized-m3. + accelerator-optimized-a3, compute-optimized, compute-optimized-c2d, + compute-optimized-c3, compute-optimized-h3, general-purpose, + general-purpose-e2, general-purpose-n2, general-purpose-n2d, + general-purpose-t2d, graphics-optimized, memory-optimized, + memory-optimized-m3. Manage the reservations to be created with the commitment. @@ -179,6 +180,12 @@ OPTIONAL FLAGS this reservation by name using --reservation-affinity=specific can consume from this reservation. + --resource-policies=[KEY=VALUE,...] + The resource policies to include in this reservation. If you omit + this flag, no resource policies are added. You can specify any + string as the key, and specify the name of a resource policy as + the value. + --vm-count=VM_COUNT The number of VM instances that are allocated to this reservation. The value of this field must be an int in the range diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index ca2347c28..dc0d23f93 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -22,8 +22,9 @@ SYNOPSIS [--ipv6-network-tier=IPV6_NETWORK_TIER] [--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME], - [interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE] - [--maintenance-policy=MAINTENANCE_POLICY] + [interface=INTERFACE],[size=SIZE]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] + [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] [--min-cpu-platform=PLATFORM] [--min-node-cpu=MIN_NODE_CPU] @@ -433,6 +434,12 @@ FLAGS partitions. You can specify a maximum of 24 local SSDs for a maximum of 9TB attached to an instance. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of available machine types, run 'gcloud compute machine-types list'. If diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index 3eccac21a..929afd500 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -21,6 +21,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME], [interface=INTERFACE],[size=SIZE]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] [--location-policy=[ZONE=POLICY,...]] [--machine-type=MACHINE_TYPE] [--max-count-per-zone=[ZONE=MAX_COUNT_PER_ZONE,...]] [--metadata=KEY=VALUE,[KEY=VALUE,...]] @@ -443,6 +444,12 @@ OPTIONAL FLAGS partitions. You can specify a maximum of 24 local SSDs for a maximum of 9TB attached to an instance. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --location-policy=[ZONE=POLICY,...] Policy for which zones to include or exclude during bulk instance creation within a region. Policy is defined as a list of key-value diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index 8e60294da..bbc1d0108 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -26,8 +26,9 @@ SYNOPSIS [--ipv6-public-ptr-domain=IPV6_PUBLIC_PTR_DOMAIN] [--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME], - [interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE] - [--maintenance-policy=MAINTENANCE_POLICY] + [interface=INTERFACE],[size=SIZE]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] + [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] [--min-cpu-platform=PLATFORM] [--min-node-cpu=MIN_NODE_CPU] @@ -514,6 +515,12 @@ FLAGS partitions. You can specify a maximum of 24 local SSDs for a maximum of 9TB attached to an instance. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of available machine types, run 'gcloud compute machine-types list'. If diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index 03f4e17ab..0390f00ad 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -29,8 +29,9 @@ SYNOPSIS [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] - [--labels=[KEY=VALUE,...]] [--machine-type=MACHINE_TYPE] - [--maintenance-policy=MAINTENANCE_POLICY] + [--labels=[KEY=VALUE,...]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] + [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] [--min-cpu-platform=PLATFORM] [--network=NETWORK] @@ -441,6 +442,12 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of available machine types, run 'gcloud compute machine-types list'. If diff --git a/gcloud/compute/instances/delete-access-config b/gcloud/compute/instances/delete-access-config index babf21f22..a1dd506f8 100644 --- a/gcloud/compute/instances/delete-access-config +++ b/gcloud/compute/instances/delete-access-config @@ -12,7 +12,10 @@ DESCRIPTION gcloud compute instances delete-access-config is used to delete access configurations from network interfaces of Compute Engine virtual machines. Access configurations let you assign a public, external IP to a virtual - machine. + machine. The delete-access-config operation removes external IP from the + instance interface. If there is traffic routed to the external IP, after + deleting the access config operation, traffic to the external IP will not + reach the VM anymore. EXAMPLES To remove the externally accessible IP from a virtual machine named diff --git a/gcloud/compute/instances/set-scheduling b/gcloud/compute/instances/set-scheduling index 50b98bce3..622ee1a9a 100644 --- a/gcloud/compute/instances/set-scheduling +++ b/gcloud/compute/instances/set-scheduling @@ -4,10 +4,11 @@ NAME SYNOPSIS gcloud compute instances set-scheduling INSTANCE_NAME - [--clear-min-node-cpu] [--maintenance-policy=MAINTENANCE_POLICY] - [--min-node-cpu=MIN_NODE_CPU] [--[no-]preemptible] - [--provisioning-model=PROVISIONING_MODEL] [--[no-]restart-on-failure] - [--zone=ZONE] + [--clear-min-node-cpu] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] + [--maintenance-policy=MAINTENANCE_POLICY] [--min-node-cpu=MIN_NODE_CPU] + [--[no-]preemptible] [--provisioning-model=PROVISIONING_MODEL] + [--[no-]restart-on-failure] [--zone=ZONE] [--clear-instance-termination-action | --instance-termination-action=INSTANCE_TERMINATION_ACTION] [--clear-node-affinities | --node=NODE @@ -37,6 +38,12 @@ FLAGS instance min-node-cpu will be cleared. The instance will not be overcommitted and utilize the full CPU count assigned. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --maintenance-policy=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see diff --git a/gcloud/compute/reservations/update b/gcloud/compute/reservations/update index a0af51e33..d6cf4961d 100644 --- a/gcloud/compute/reservations/update +++ b/gcloud/compute/reservations/update @@ -11,17 +11,21 @@ DESCRIPTION Update Compute Engine reservations. EXAMPLES - To add my-project to the list of projects that are shared with a Compute - Engine reservation, my-reservation in zone: us-central1-a, run: + To add project-1,project-2,project-3 to the list of projects that are + shared with a Compute Engine reservation, my-reservation in zone: + us-central1-a, run: $ gcloud compute reservations update my-reservation \ - --add-share-with=my-project --zone=us-central1-a + --add-share-with=project-1,project-2,project-3 \ + --zone=us-central1-a - To remove my-project from the list of projects that are shared with a - Compute Engine reservation, my-reservation in zone: us-central1-a, run: + To remove project-1,project-2,project-3 from the list of projects that are + shared with a Compute Engine reservation, my-reservation in zone: + us-central1-a, run: $ gcloud compute reservations update my-reservation \ - --remove-share-with=my-project --zone=us-central1-a + --remove-share-with=project-1,project-2,project-3 \ + --zone=us-central1-a To update the number of reserved VM instances to 500 for a Compute Engine reservation, my-reservation in zone: us-central1-a, run: diff --git a/gcloud/compute/routers/nats/create b/gcloud/compute/routers/nats/create index a594f7111..29a2638d8 100644 --- a/gcloud/compute/routers/nats/create +++ b/gcloud/compute/routers/nats/create @@ -8,6 +8,7 @@ SYNOPSIS (--nat-all-subnet-ip-ranges | --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME],[...] | --nat-primary-subnet-ip-ranges) [--async] + [--auto-network-tier=AUTO_NETWORK_TIER] [--[no-]enable-dynamic-port-allocation] [--enable-endpoint-independent-mapping] [--enable-logging] [--endpoint-types=[ENDPOINT_TYPE,...]] @@ -87,6 +88,17 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --auto-network-tier=AUTO_NETWORK_TIER + The network tier to use when automatically reserving NAT IP addresses. + AUTO_NETWORK_TIER must be one of: + + PREMIUM + High quality, Google-grade network tier with support for all + networking products. + STANDARD + Public internet quality, with only limited support for other + networking products. + --[no-]enable-dynamic-port-allocation Enable dynamic port allocation. diff --git a/gcloud/compute/routers/nats/update b/gcloud/compute/routers/nats/update index e66793240..a41f5494c 100644 --- a/gcloud/compute/routers/nats/update +++ b/gcloud/compute/routers/nats/update @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud compute routers nats update NAME --router=ROUTER [--async] + [--auto-network-tier=AUTO_NETWORK_TIER] [--[no-]enable-dynamic-port-allocation] [--enable-endpoint-independent-mapping] [--enable-logging] [--log-filter=LOG_FILTER] [--region=REGION] [--rules=RULES] @@ -70,6 +71,17 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --auto-network-tier=AUTO_NETWORK_TIER + The network tier to use when automatically reserving NAT IP addresses. + AUTO_NETWORK_TIER must be one of: + + PREMIUM + High quality, Google-grade network tier with support for all + networking products. + STANDARD + Public internet quality, with only limited support for other + networking products. + --[no-]enable-dynamic-port-allocation Enable dynamic port allocation. diff --git a/gcloud/compute/security-policies/add-layer7-ddos-defense-threshold-config b/gcloud/compute/security-policies/add-layer7-ddos-defense-threshold-config new file mode 100644 index 000000000..63031a13e --- /dev/null +++ b/gcloud/compute/security-policies/add-layer7-ddos-defense-threshold-config @@ -0,0 +1,69 @@ +NAME + gcloud compute security-policies add-layer7-ddos-defense-threshold-config - + add a layer7 ddos defense threshold config to a Compute Engine security + policy + +SYNOPSIS + gcloud compute security-policies add-layer7-ddos-defense-threshold-config + NAME --threshold-config-name=THRESHOLD_CONFIG_NAME + [--auto-deploy-confidence-threshold=AUTO_DEPLOY_CONFIDENCE_THRESHOLD] + [--auto-deploy-expiration-sec=AUTO_DEPLOY_EXPIRATION_SEC] + [--auto-deploy-impacted-baseline-threshold=AUTO_DEPLOY_IMPACTED_BASELINE_THRESHOLD] + [--auto-deploy-load-threshold=AUTO_DEPLOY_LOAD_THRESHOLD] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute security-policies add-layer7-ddos-defense-threshold-config + is used to add layer7 ddos defense threshold configs to security policies. + +EXAMPLES + To add a layer7 ddos defense threshold config run the following command: + + $ gcloud compute security-policies \ + add-layer7-ddos-defense-threshold-config NAME \ + --threshold-config-name=my-threshold-config-name \ + --auto-deploy-load-threshold=0.7 \ + --auto-deploy-confidence-threshold=0.8 \ + --auto-deploy-impacted-baseline-threshold=0.1 \ + --auto-deploy-expiration-sec=4800 + +POSITIONAL ARGUMENTS + NAME + Name of the security policy to update. + +REQUIRED FLAGS + --threshold-config-name=THRESHOLD_CONFIG_NAME + The name for the threshold config. + +OPTIONAL FLAGS + --auto-deploy-confidence-threshold=AUTO_DEPLOY_CONFIDENCE_THRESHOLD + The threshold of the confidence of an identified attack over which + auto-deploy takes action. + + --auto-deploy-expiration-sec=AUTO_DEPLOY_EXPIRATION_SEC + The duration of actions, if any, taken by auto-deploy. + + --auto-deploy-impacted-baseline-threshold=AUTO_DEPLOY_IMPACTED_BASELINE_THRESHOLD + The threshold on the estimated impact to the baseline traffic of a + suggested mitigation, below which auto-deploy takes action. + + --auto-deploy-load-threshold=AUTO_DEPLOY_LOAD_THRESHOLD + The threshold on backend's load over which auto-deploy takes action. + +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 compute security-policies \ + add-layer7-ddos-defense-threshold-config + + $ gcloud beta compute security-policies \ + add-layer7-ddos-defense-threshold-config + diff --git a/gcloud/compute/security-policies/help b/gcloud/compute/security-policies/help index 2ff60d40e..b4859747f 100644 --- a/gcloud/compute/security-policies/help +++ b/gcloud/compute/security-policies/help @@ -32,6 +32,10 @@ GROUPS COMMANDS COMMAND is one of the following: + add-layer7-ddos-defense-threshold-config + Add a layer7 ddos defense threshold config to a Compute Engine security + policy. + create Create a Compute Engine security policy. @@ -53,6 +57,10 @@ COMMANDS list-preconfigured-expression-sets List all available preconfigured expression sets. + remove-layer7-ddos-defense-threshold-config + Remove a layer7 ddos defense threshold config from a Compute Engine + security policy. + update Update a Compute Engine security policy. diff --git a/gcloud/compute/security-policies/remove-layer7-ddos-defense-threshold-config b/gcloud/compute/security-policies/remove-layer7-ddos-defense-threshold-config new file mode 100644 index 000000000..610b44823 --- /dev/null +++ b/gcloud/compute/security-policies/remove-layer7-ddos-defense-threshold-config @@ -0,0 +1,47 @@ +NAME + gcloud compute security-policies + remove-layer7-ddos-defense-threshold-config - remove a layer7 ddos + defense threshold config from a Compute Engine security policy + +SYNOPSIS + gcloud compute security-policies + remove-layer7-ddos-defense-threshold-config NAME + --threshold-config-name=THRESHOLD_CONFIG_NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute security-policies + remove-layer7-ddos-defense-threshold-config is used to remove layer7 ddos + defense threshold configs from security policies. + +EXAMPLES + To remove a layer7 ddos defense threshold config run the following command: + + $ gcloud compute security-policies \ + remove-layer7-ddos-defense-threshold-config NAME \ + --threshold-config-name=my-threshold-config-name + +POSITIONAL ARGUMENTS + NAME + Name of the security policy to update. + +REQUIRED FLAGS + --threshold-config-name=THRESHOLD_CONFIG_NAME + The name for the threshold 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 + These variants are also available: + + $ gcloud alpha compute security-policies \ + remove-layer7-ddos-defense-threshold-config + + $ gcloud beta compute security-policies \ + remove-layer7-ddos-defense-threshold-config + diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 5aef2f412..81fa19cb5 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -388,7 +388,8 @@ FLAGS --disk-type=DISK_TYPE Type of the node VM boot disk. For version 1.24.0+, defaults to pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE - must be one of: pd-standard, pd-ssd, pd-balanced. + must be one of: pd-standard, pd-ssd, pd-balanced, hyperdisk-balanced, + hyperdisk-extreme, hyperdisk-throughput. --enable-autorepair Enable node autorepair feature for a cluster's default node pool(s). diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 5799fd627..3ae1a6f12 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -8,7 +8,6 @@ SYNOPSIS | --autoscaling-profile=AUTOSCALING_PROFILE | --complete-credential-rotation | --complete-ip-rotation | --database-encryption-key=DATABASE_ENCRYPTION_KEY - | --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-database-encryption | --disable-default-snat | --disable-workload-identity | --enable-autoscaling | --enable-cost-allocation | --enable-google-cloud-access @@ -55,7 +54,8 @@ SYNOPSIS --resource-usage-bigquery-dataset=RESOURCE_USAGE_BIGQUERY_DATASET | --cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN --cluster-dns-scope=CLUSTER_DNS_SCOPE - | --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics + | --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics | [--enable-autoprovisioning : --autoprovisioning-config-file=AUTOPROVISIONING_CONFIG_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE @@ -156,35 +156,6 @@ REQUIRED FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. - --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - Select Advanced Datapath Observability mode for the cluster. Defaults - to DISABLED. - - Advanced Datapath Observability allows for a real-time view into - pod-to-pod traffic within your cluster. - - Examples: - - $ gcloud container clusters update \ - --dataplane-v2-observability-mode=DISABLED - - $ gcloud container clusters update \ - --dataplane-v2-observability-mode=INTERNAL_VPC_LB - - $ gcloud container clusters update \ - --dataplane-v2-observability-mode=EXTERNAL_LB - - DATAPLANE_V2_OBSERVABILITY_MODE must be one of: - - DISABLED - Disables Advanced Datapath Observability. - EXTERNAL_LB - Makes Advanced Datapath Observability available to the external - network. - INTERNAL_VPC_LB - Makes Advanced Datapath Observability available from the VPC - network. - --disable-database-encryption Disable database encryption. @@ -821,6 +792,35 @@ REQUIRED FLAGS vpc Configures the Cloud DNS zone to be private to the VPC Network. + --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + Select Advanced Datapath Observability mode for the cluster. Defaults + to DISABLED. + + Advanced Datapath Observability allows for a real-time view into + pod-to-pod traffic within your cluster. + + Examples: + + $ gcloud container clusters update \ + --dataplane-v2-observability-mode=DISABLED + + $ gcloud container clusters update \ + --dataplane-v2-observability-mode=INTERNAL_VPC_LB + + $ gcloud container clusters update \ + --dataplane-v2-observability-mode=EXTERNAL_LB + + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: + + DISABLED + Disables Advanced Datapath Observability. + EXTERNAL_LB + Makes Advanced Datapath Observability available to the external + network. + INTERNAL_VPC_LB + Makes Advanced Datapath Observability available from the VPC + network. + At most one of these can be specified: --disable-dataplane-v2-metrics diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index 1298de057..10fc50e6b 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -184,7 +184,8 @@ FLAGS --disk-type=DISK_TYPE Type of the node VM boot disk. For version 1.24.0+, defaults to pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE - must be one of: pd-standard, pd-ssd, pd-balanced. + must be one of: pd-standard, pd-ssd, pd-balanced, hyperdisk-balanced, + hyperdisk-extreme, hyperdisk-throughput. --enable-autoprovisioning Enables Cluster Autoscaler to treat the node pool as if it was diff --git a/gcloud/database-migration/connection-profiles/create/cloudsql b/gcloud/database-migration/connection-profiles/create/cloudsql index 3ffc23387..f702e93f5 100644 --- a/gcloud/database-migration/connection-profiles/create/cloudsql +++ b/gcloud/database-migration/connection-profiles/create/cloudsql @@ -12,7 +12,7 @@ SYNOPSIS [--no-auto-storage-increase] [--availability-type=AVAILABILITY_TYPE] [--data-disk-size=DATA_DISK_SIZE] [--data-disk-type=DATA_DISK_TYPE] [--database-flags=[FLAG=VALUE,...]] [--display-name=DISPLAY_NAME] - [--no-enable-ip-v4] [--labels=[KEY=VALUE,...]] + [--edition=EDITION] [--no-enable-ip-v4] [--labels=[KEY=VALUE,...]] [--private-network=PRIVATE_NETWORK] [--provider=PROVIDER] [--require-ssl] [--root-password=ROOT_PASSWORD] [--secondary-zone=SECONDARY_ZONE] @@ -169,6 +169,15 @@ OPTIONAL FLAGS include letters, numbers, spaces, and hyphens, and must start with a letter. + --edition=EDITION + Specifies edition. EDITION must be one of: + + enterprise + Enterprise is the standard option for smaller instances. + enterprise-plus + Enterprise plus option recommended for cpu-intensive workloads. + Offers access to premium features and capabilities. + --enable-ip-v4 Whether the instance should be assigned an IPv4 address or not. Enabled by default, use --no-enable-ip-v4 to disable. diff --git a/gcloud/database-migration/connection-profiles/create/mysql b/gcloud/database-migration/connection-profiles/create/mysql index 592d8bea0..6af13cd9a 100644 --- a/gcloud/database-migration/connection-profiles/create/mysql +++ b/gcloud/database-migration/connection-profiles/create/mysql @@ -87,15 +87,15 @@ FLAGS CLOUDSQL. --ca-certificate=CA_CERTIFICATE - x509 PEM-encoded certificate of the CA that signed the source database + x509 PEM-encoded certificate of the CA that signed the database server's certificate. The replica will use this certificate to verify it's connecting to the correct host. Database Migration Service encrypts the value when storing it. --client-certificate=CLIENT_CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to - authenticate against the source database server. Database Migration - Service encrypts the value when storing it. + authenticate against the database server. Database Migration Service + encrypts the value when storing it. --private-key=PRIVATE_KEY Unencrypted PKCS#1 or PKCS#8 PEM-encoded private key associated with @@ -103,10 +103,13 @@ FLAGS when storing it. --host=HOST - IP or hostname of the source database. + IP or hostname of the database. When --psc-service-attachment is also + specified, this field value should be: 1. For Cloud SQL PSC enabled + instance - the dns_name field (e.g ..sql.goog.). 2. For + Cloud SQL PSA instance (vpc peering) - the private ip of the instance. --port=PORT - Network port of the source database. + Network port of the database. --username=USERNAME Username that Database Migration Service uses to connect to the @@ -117,8 +120,8 @@ FLAGS --password=PASSWORD Password for the user that Database Migration Service uses to connect - to the source database. Database Migration Service encrypts the value - when storing it, and the field is not returned on request. + to the database. Database Migration Service encrypts the value when + storing it, and the field is not returned on request. --prompt-for-password Prompt for the password used to connect to the database. diff --git a/gcloud/database-migration/connection-profiles/create/oracle b/gcloud/database-migration/connection-profiles/create/oracle index 0dead8ad5..a994dc3dc 100644 --- a/gcloud/database-migration/connection-profiles/create/oracle +++ b/gcloud/database-migration/connection-profiles/create/oracle @@ -63,10 +63,13 @@ REQUIRED FLAGS database service for the oracle connection profile. --host=HOST - IP or hostname of the source database. + IP or hostname of the database. When --psc-service-attachment is also + specified, this field value should be: 1. For Cloud SQL PSC enabled + instance - the dns_name field (e.g ..sql.goog.). 2. For + Cloud SQL PSA instance (vpc peering) - the private ip of the instance. --port=PORT - Network port of the source database. + Network port of the database. --username=USERNAME Username that Database Migration Service uses to connect to the @@ -77,8 +80,8 @@ REQUIRED FLAGS --password=PASSWORD Password for the user that Database Migration Service uses to connect - to the source database. Database Migration Service encrypts the value - when storing it, and the field is not returned on request. + to the database. Database Migration Service encrypts the value when + storing it, and the field is not returned on request. --prompt-for-password Prompt for the password used to connect to the database. diff --git a/gcloud/database-migration/connection-profiles/create/postgresql b/gcloud/database-migration/connection-profiles/create/postgresql index 9dea40f3d..fb03450c0 100644 --- a/gcloud/database-migration/connection-profiles/create/postgresql +++ b/gcloud/database-migration/connection-profiles/create/postgresql @@ -85,15 +85,15 @@ FLAGS numbers. --ca-certificate=CA_CERTIFICATE - x509 PEM-encoded certificate of the CA that signed the source database + x509 PEM-encoded certificate of the CA that signed the database server's certificate. The replica will use this certificate to verify it's connecting to the correct host. Database Migration Service encrypts the value when storing it. --client-certificate=CLIENT_CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to - authenticate against the source database server. Database Migration - Service encrypts the value when storing it. + authenticate against the database server. Database Migration Service + encrypts the value when storing it. --private-key=PRIVATE_KEY Unencrypted PKCS#1 or PKCS#8 PEM-encoded private key associated with @@ -101,10 +101,13 @@ FLAGS when storing it. --host=HOST - IP or hostname of the source database. + IP or hostname of the database. When --psc-service-attachment is also + specified, this field value should be: 1. For Cloud SQL PSC enabled + instance - the dns_name field (e.g ..sql.goog.). 2. For + Cloud SQL PSA instance (vpc peering) - the private ip of the instance. --port=PORT - Network port of the source database. + Network port of the database. --username=USERNAME Username that Database Migration Service uses to connect to the @@ -115,8 +118,8 @@ FLAGS --password=PASSWORD Password for the user that Database Migration Service uses to connect - to the source database. Database Migration Service encrypts the value - when storing it, and the field is not returned on request. + to the database. Database Migration Service encrypts the value when + storing it, and the field is not returned on request. --prompt-for-password Prompt for the password used to connect to the database. diff --git a/gcloud/database-migration/connection-profiles/update b/gcloud/database-migration/connection-profiles/update index b15b99997..24d05a6de 100644 --- a/gcloud/database-migration/connection-profiles/update +++ b/gcloud/database-migration/connection-profiles/update @@ -63,15 +63,15 @@ POSITIONAL ARGUMENTS FLAGS --ca-certificate=CA_CERTIFICATE - x509 PEM-encoded certificate of the CA that signed the source database + x509 PEM-encoded certificate of the CA that signed the database server's certificate. The replica will use this certificate to verify it's connecting to the correct host. Database Migration Service encrypts the value when storing it. --client-certificate=CLIENT_CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to - authenticate against the source database server. Database Migration - Service encrypts the value when storing it. + authenticate against the database server. Database Migration Service + encrypts the value when storing it. --cloudsql-instance=CLOUDSQL_INSTANCE If the source or destination is a Cloud SQL database, then use this @@ -83,10 +83,13 @@ FLAGS letter. --host=HOST - IP or hostname of the source database. + IP or hostname of the database. When --psc-service-attachment is also + specified, this field value should be: 1. For Cloud SQL PSC enabled + instance - the dns_name field (e.g ..sql.goog.). 2. For + Cloud SQL PSA instance (vpc peering) - the private ip of the instance. --port=PORT - Network port of the source database. + Network port of the database. --private-key=PRIVATE_KEY Unencrypted PKCS#1 or PKCS#8 PEM-encoded private key associated with @@ -131,8 +134,8 @@ FLAGS --password=PASSWORD Password for the user that Database Migration Service uses to connect - to the source database. Database Migration Service encrypts the value - when storing it, and the field is not returned on request. + to the database. Database Migration Service encrypts the value when + storing it, and the field is not returned on request. --prompt-for-password Prompt for the password used to connect to the database. diff --git a/gcloud/database-migration/migration-jobs/restart b/gcloud/database-migration/migration-jobs/restart index 71bdc57d6..c0c3d4608 100644 --- a/gcloud/database-migration/migration-jobs/restart +++ b/gcloud/database-migration/migration-jobs/restart @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud database-migration migration-jobs restart - (MIGRATION_JOB : --region=REGION) [GCLOUD_WIDE_FLAG ...] + (MIGRATION_JOB : --region=REGION) [--skip-validation] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Restart a Database Migration Service migration job. @@ -47,6 +48,11 @@ POSITIONAL ARGUMENTS fully specified name; ▸ provide the argument --region on the command line. +FLAGS + --skip-validation + Restart the migration job without running prior configuration + verification. + 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/start b/gcloud/database-migration/migration-jobs/start index 43e03990e..2651c2099 100644 --- a/gcloud/database-migration/migration-jobs/start +++ b/gcloud/database-migration/migration-jobs/start @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud database-migration migration-jobs start - (MIGRATION_JOB : --region=REGION) [GCLOUD_WIDE_FLAG ...] + (MIGRATION_JOB : --region=REGION) [--skip-validation] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Start a Database Migration Service migration job. @@ -47,6 +48,11 @@ POSITIONAL ARGUMENTS fully specified name; ▸ provide the argument --region on the command line. +FLAGS + --skip-validation + Start the migration job without running prior configuration + verification. + 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/network-management/connectivity-tests/create b/gcloud/network-management/connectivity-tests/create index 65b3f06eb..71887e234 100644 --- a/gcloud/network-management/connectivity-tests/create +++ b/gcloud/network-management/connectivity-tests/create @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud network-management connectivity-tests create CONNECTIVITY_TEST (--destination-cloud-sql-instance=DESTINATION_CLOUD_SQL_INSTANCE + --destination-forwarding-rule=DESTINATION_FORWARDING_RULE --destination-gke-master-cluster=DESTINATION_GKE_MASTER_CLUSTER --destination-instance=DESTINATION_INSTANCE --destination-ip-address=DESTINATION_IP_ADDRESS) @@ -63,6 +64,9 @@ REQUIRED FLAGS --destination-cloud-sql-instance=DESTINATION_CLOUD_SQL_INSTANCE A Cloud SQL instance URI as the destination endpoint. + --destination-forwarding-rule=DESTINATION_FORWARDING_RULE + A forwarding rule URI as the destination endpoint. + --destination-gke-master-cluster=DESTINATION_GKE_MASTER_CLUSTER A cluster URI for Google Kubernetes Engine master as the destination endpoint. diff --git a/gcloud/network-management/connectivity-tests/update b/gcloud/network-management/connectivity-tests/update index 8e6108a9d..e92c38927 100644 --- a/gcloud/network-management/connectivity-tests/update +++ b/gcloud/network-management/connectivity-tests/update @@ -14,6 +14,8 @@ SYNOPSIS [--source-project=SOURCE_PROJECT] [--clear-destination-cloud-sql-instance | --destination-cloud-sql-instance=DESTINATION_CLOUD_SQL_INSTANCE] + [--clear-destination-forwarding-rule + | --destination-forwarding-rule=DESTINATION_FORWARDING_RULE] [--clear-destination-gke-master-cluster | --destination-gke-master-cluster=DESTINATION_GKE_MASTER_CLUSTER] [--clear-destination-instance @@ -116,6 +118,14 @@ FLAGS --destination-cloud-sql-instance=DESTINATION_CLOUD_SQL_INSTANCE A Cloud SQL instance URI as the destination endpoint. + At most one of these can be specified: + + --clear-destination-forwarding-rule + Clear existing destination forwarding rule. + + --destination-forwarding-rule=DESTINATION_FORWARDING_RULE + A forwarding rule URI as the destination endpoint. + At most one of these can be specified: --clear-destination-gke-master-cluster diff --git a/gcloud/run/jobs/create b/gcloud/run/jobs/create index eab3a1488..473bcc806 100644 --- a/gcloud/run/jobs/create +++ b/gcloud/run/jobs/create @@ -134,8 +134,8 @@ OPTIONAL FLAGS example, "10" is 10 seconds. --tasks=TASKS; default=1 - Number of tasks that must run to completion for the job to be - considered done. Use this flag to trigger multiple runs of the job. + Number of tasks that must run to completion for the execution to be + considered done. --vpc-connector=VPC_CONNECTOR Set a VPC connector for this resource. diff --git a/gcloud/run/jobs/deploy b/gcloud/run/jobs/deploy index e67ea6f16..e508075f5 100644 --- a/gcloud/run/jobs/deploy +++ b/gcloud/run/jobs/deploy @@ -131,8 +131,8 @@ FLAGS example, "10" is 10 seconds. --tasks=TASKS; default=1 - Number of tasks that must run to completion for the job to be - considered done. Use this flag to trigger multiple runs of the job. + Number of tasks that must run to completion for the execution to be + considered done. --vpc-connector=VPC_CONNECTOR Set a VPC connector for this resource. diff --git a/gcloud/run/jobs/update b/gcloud/run/jobs/update index 72d0e95b8..387931f71 100644 --- a/gcloud/run/jobs/update +++ b/gcloud/run/jobs/update @@ -121,8 +121,8 @@ FLAGS example, "10" is 10 seconds. --tasks=TASKS; default=1 - Number of tasks that must run to completion for the job to be - considered done. Use this flag to trigger multiple runs of the job. + Number of tasks that must run to completion for the execution to be + considered done. --vpc-connector=VPC_CONNECTOR Set a VPC connector for this resource. diff --git a/gcloud/services/api-keys/help b/gcloud/services/api-keys/help index ecc878f48..1055394f6 100644 --- a/gcloud/services/api-keys/help +++ b/gcloud/services/api-keys/help @@ -21,6 +21,9 @@ COMMANDS list Lists API keys. + lookup + Look up resource name of a key string. + NOTES These variants are also available: diff --git a/gcloud/services/api-keys/lookup b/gcloud/services/api-keys/lookup new file mode 100644 index 000000000..b6c70e667 --- /dev/null +++ b/gcloud/services/api-keys/lookup @@ -0,0 +1,33 @@ +NAME + gcloud services api-keys lookup - look up resource name of a key string + +SYNOPSIS + gcloud services api-keys lookup KEY_STRING [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Look up resource name of a key string. + +EXAMPLES + Look up resource name of a key string named my-key-string: + + $ gcloud services api-keys lookup my-key-string + +POSITIONAL ARGUMENTS + KEY_STRING + Key string of the key + +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 services api-keys lookup + + $ gcloud beta services api-keys lookup + diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index 7f9151567..cc4b9432f 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -46,6 +46,8 @@ SYNOPSIS [--storage-size=STORAGE_SIZE] [--storage-type=STORAGE_TYPE] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] [--time-zone=TIME_ZONE] [--timeout=TIMEOUT; default=3600] + [--allowed-psc-projects=PROJECT,[PROJECT,...] + --enable-private-service-connect] [--disk-encryption-key=DISK_ENCRYPTION_KEY : --disk-encryption-key-keyring=DISK_ENCRYPTION_KEY_KEYRING --disk-encryption-key-location=DISK_ENCRYPTION_KEY_LOCATION @@ -417,6 +419,16 @@ FLAGS specified. By default, set to 3600s. To wait indefinitely, set to unlimited. + --allowed-psc-projects=PROJECT,[PROJECT,...] + A comma-separated list of projects. Each project in this list may be + represented by a project number (numeric) or by a project id + (alphanumeric). This will allow PSC connections to be established from + specified consumer projects. This can be set only when PSC is enabled. + + --enable-private-service-connect + When the flag is set, a Cloud SQL instance will be created with PSC + enabled. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the instance. The 'Compute Engine Service Agent' service account must hold permission 'Cloud KMS CryptoKey diff --git a/gcloud/sql/instances/help b/gcloud/sql/instances/help index a069d9621..97b66adec 100644 --- a/gcloud/sql/instances/help +++ b/gcloud/sql/instances/help @@ -51,6 +51,9 @@ COMMANDS promote-replica Promotes Cloud SQL read replica to a stand-alone instance. + reencrypt + Reencrypts a Cloud SQL CMEK instance. + reset-ssl-config Deletes all client certificates and generates a new server certificate. diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index d079889e7..88acdfcf4 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -38,6 +38,8 @@ SYNOPSIS [--[no-]require-ssl] [--[no-]storage-auto-increase] [--storage-size=STORAGE_SIZE] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] + [--allowed-psc-projects=PROJECT,[PROJECT,...] + | --clear-allowed-psc-projects] [--authorized-gae-apps=APP,[APP,...] | --clear-gae-apps] [--authorized-networks=NETWORK,[NETWORK,...] | --clear-authorized-networks] @@ -350,6 +352,19 @@ FLAGS https://cloud.google.com/sql/pricing. WARNING: Instance will be restarted. + At most one of these can be specified: + + --allowed-psc-projects=PROJECT,[PROJECT,...] + A comma-separated list of projects. Each project in this list may be + represented by a project number (numeric) or by a project id + (alphanumeric). This will allow PSC connections to be established + from specified consumer projects. This can be set only when PSC is + enabled. + + --clear-allowed-psc-projects + This will clear the project allowlist of PSC, disallowing all + projects from creating new PSC bindings to the instance. + At most one of these can be specified: --authorized-gae-apps=APP,[APP,...] diff --git a/gcloud/sql/instances/reencrypt b/gcloud/sql/instances/reencrypt new file mode 100644 index 000000000..8b1faa766 --- /dev/null +++ b/gcloud/sql/instances/reencrypt @@ -0,0 +1,38 @@ +NAME + gcloud sql instances reencrypt - reencrypts a Cloud SQL CMEK instance + +SYNOPSIS + gcloud sql instances reencrypt INSTANCE [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Reencrypt a Cloud SQL CMEK instance with the primary key version. + +EXAMPLES + To reencrypt a Cloud SQL CMEK instance with the primary key version: + + $ gcloud sql instances reencrypt instance-foo + +POSITIONAL ARGUMENTS + INSTANCE + Cloud SQL instance ID. + +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 + These variants are also available: + + $ gcloud alpha sql instances reencrypt + + $ gcloud beta sql instances reencrypt + diff --git a/gcloud/storage/buckets/update b/gcloud/storage/buckets/update index 71e78a497..dc35dd5d4 100644 --- a/gcloud/storage/buckets/update +++ b/gcloud/storage/buckets/update @@ -226,27 +226,27 @@ FLAGS At most one of these can be specified: --clear-log-bucket - Clears logging bucket receiving the usage current bucket's data and - disables usage logging. + Disables usage and storage logging for the bucket specified in the + overall update command. --log-bucket=LOG_BUCKET - Enables usage logging of the bucket, outputting log files to the - specified logging_bucket in this flag. Cloud Storage doesn't validate - the existence of the bucket receiving logs. In addition to enabling - logging on your bucket, you will also need to grant - cloud-storage-analytics@google.com write access to the log bucket. + Enables usage and storage logging for the bucket specified in the + overall update command, outputting log files to the bucket specified + in this flag. Cloud Storage does not validate the existence of the + bucket receiving logs. In addition to enabling logging on your + bucket, you also need to grant cloud-storage-analytics@google.com + write access to the log bucket. At most one of these can be specified: --clear-log-object-prefix - Clears prefix used to determine what usage data to send to logging - bucket. + Clears the prefix used to determine the naming of log objects in the + logging bucket. --log-object-prefix=LOG_OBJECT_PREFIX - Specifies the object prefix for logging activity to the log bucket. - The default prefix is the bucket name. All read and write activity to - objects in the bucket will be logged for objects matching the prefix. - If usage logging is not enabled this flag will have no effect. + Specifies a prefix for the names of logs generated in the log bucket. + The default prefix is the bucket name. If logging is not enabled, + this flag has no effect. At most one of these can be specified: diff --git a/gcloud/transcoder/jobs/create b/gcloud/transcoder/jobs/create index 2c68f541e..71bc0b646 100644 --- a/gcloud/transcoder/jobs/create +++ b/gcloud/transcoder/jobs/create @@ -2,9 +2,10 @@ NAME gcloud transcoder jobs create - create Transcoder jobs SYNOPSIS - gcloud transcoder jobs create [--input-uri=INPUT_URI] - [--labels=[KEY=VALUE,...]] [--location=LOCATION] [--mode=MODE] - [--optimization=OPTIMIZATION] [--output-uri=OUTPUT_URI] + gcloud transcoder jobs create [--batch-mode-priority=BATCH_MODE_PRIORITY] + [--input-uri=INPUT_URI] [--labels=[KEY=VALUE,...]] + [--location=LOCATION] [--mode=MODE] [--optimization=OPTIMIZATION] + [--output-uri=OUTPUT_URI] [--file=FILE | --json=JSON | --template-id=TEMPLATE_ID] [GCLOUD_WIDE_FLAG ...] @@ -45,12 +46,22 @@ EXAMPLES $ gcloud transcoder jobs create --location=us-central1 \ --file="config.json" --mode=PROCESSING_MODE_BATCH + To create a transcoder job in batch mode with priority: + + $ gcloud transcoder jobs create --location=us-central1 \ + --file="config.json" --mode=PROCESSING_MODE_BATCH \ + --batch-mode-priority=3 + To create a transcoder job with optimizations disabled: $ gcloud transcoder jobs create --location=us-central1 \ --file="config.json" --optimization=DISABLED FLAGS + --batch-mode-priority=BATCH_MODE_PRIORITY + Processing priority of a batch mode transcoder job. This value will + override batch mode priority in job config. + --input-uri=INPUT_URI Google Cloud Storage URI. This value will override input URI in job config. diff --git a/gcloud/workbench/instances/help b/gcloud/workbench/instances/help index 5e0011623..eb94c3d39 100644 --- a/gcloud/workbench/instances/help +++ b/gcloud/workbench/instances/help @@ -45,6 +45,9 @@ COMMANDS reset Request for resetting instances. + rollback + Request for rolling back instances. + set-iam-policy Set the IAM policy for an Instance. diff --git a/gcloud/workbench/instances/rollback b/gcloud/workbench/instances/rollback new file mode 100644 index 000000000..2d05bbe20 --- /dev/null +++ b/gcloud/workbench/instances/rollback @@ -0,0 +1,69 @@ +NAME + gcloud workbench instances rollback - request for rolling back instances + +SYNOPSIS + gcloud workbench instances rollback (INSTANCE : --location=LOCATION) + --target-snapshot=TARGET_SNAPSHOT [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Request for rolling back workbench instances. + +EXAMPLES + To rollback an instance, run: + + $ gcloud workbench instances rollback example-instance \ + target-snapshot=projects/example-project/global/snapshots/\ + aorlbjvpavvf --location=us-central1-a + +POSITIONAL ARGUMENTS + Instance resource - User-defined unique name of this instance. The + instance name must be 1 to 63 characters long and contain only lowercase + letters, numeric characters, and dashes. The first character must be a + lowercase letter and the last character cannot be a dash. 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 instance 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. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location of this environment + https://cloud.google.com/compute/docs/regions-zones/#locations. + + To set the location attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property notebooks/location. + +REQUIRED FLAGS + --target-snapshot=TARGET_SNAPSHOT + The saved snapshot to rollback to. + +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.