From 3efce28165b8014336fec1dbcd76b4caae6588ef Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 7 Feb 2024 10:26:58 +0000 Subject: [PATCH] gcloud: Wed Feb 7 10:26:58 UTC 2024 --- gcloud/_version | 8 +- gcloud/alloydb/clusters/create | 5 +- gcloud/alloydb/instances/create | 2 +- gcloud/alloydb/instances/update | 2 +- gcloud/alpha/alloydb/clusters/create | 5 +- gcloud/alpha/alloydb/instances/create | 2 +- gcloud/alpha/alloydb/instances/update | 2 +- .../{find-discovered => find} | 9 +- gcloud/alpha/apphub/discovered-services/help | 2 +- .../{find-discovered => find} | 14 +- gcloud/alpha/apphub/discovered-workloads/help | 2 +- gcloud/alpha/compute/commitments/create | 16 +- .../compute/instance-groups/managed/help | 3 + .../managed/resize-requests/cancel | 75 +++++ .../managed/resize-requests/create | 79 +++++ .../managed/resize-requests/delete | 69 ++++ .../managed/resize-requests/describe | 69 ++++ .../managed/resize-requests/help | 43 +++ .../managed/resize-requests/list | 97 ++++++ .../alpha/compute/instances/ops-agents/help | 4 +- .../instances/ops-agents/policies/help | 4 +- .../add-layer7-ddos-defense-threshold-config | 30 +- .../container/attached/clusters/register | 10 +- gcloud/alpha/container/aws/clusters/create | 10 +- gcloud/alpha/container/azure/clusters/create | 10 +- gcloud/alpha/container/clusters/create | 10 +- gcloud/alpha/container/clusters/update | 10 +- .../alpha/container/fleet/operations/describe | 6 +- gcloud/alpha/container/fleet/operations/help | 6 +- gcloud/alpha/container/fleet/operations/list | 6 +- gcloud/alpha/container/fleet/operations/wait | 6 +- .../alpha/container/hub/operations/describe | 6 +- gcloud/alpha/container/hub/operations/help | 6 +- gcloud/alpha/container/hub/operations/list | 6 +- gcloud/alpha/container/hub/operations/wait | 6 +- .../add-iam-policy-binding | 141 +++++++++ .../deploy/custom-target-types/get-iam-policy | 106 +++++++ gcloud/alpha/deploy/custom-target-types/help | 13 + .../remove-iam-policy-binding | 146 +++++++++ .../deploy/custom-target-types/set-iam-policy | 89 ++++++ gcloud/alpha/run/deploy | 11 +- gcloud/alpha/run/jobs/create | 152 ++++++--- gcloud/alpha/run/services/update | 11 +- gcloud/alpha/spanner/operations/list | 4 + gcloud/alpha/sql/export/sql | 12 +- gcloud/alpha/sql/import/sql | 12 +- gcloud/beta/alloydb/clusters/create | 5 +- gcloud/beta/alloydb/instances/create | 2 +- gcloud/beta/alloydb/instances/update | 2 +- gcloud/beta/compute/commitments/create | 17 +- .../beta/compute/instance-groups/managed/help | 3 + .../managed/resize-requests/cancel | 66 ++++ .../managed/resize-requests/create | 76 +++++ .../managed/resize-requests/delete | 67 ++++ .../managed/resize-requests/describe | 66 ++++ .../managed/resize-requests/help | 41 +++ .../managed/resize-requests/list | 97 ++++++ gcloud/beta/compute/instances/ops-agents/help | 6 +- .../instances/ops-agents/policies/help | 6 +- .../add-layer7-ddos-defense-threshold-config | 30 +- gcloud/beta/container/clusters/create | 10 +- gcloud/beta/container/clusters/update | 10 +- gcloud/beta/container/fleet/help | 3 + .../beta/container/fleet/operations/describe | 65 ++++ gcloud/beta/container/fleet/operations/help | 35 ++ gcloud/beta/container/fleet/operations/list | 69 ++++ gcloud/beta/container/fleet/operations/wait | 64 ++++ gcloud/beta/container/hub/help | 3 + gcloud/beta/container/hub/operations/describe | 65 ++++ gcloud/beta/container/hub/operations/help | 35 ++ gcloud/beta/container/hub/operations/list | 69 ++++ gcloud/beta/container/hub/operations/wait | 64 ++++ .../add-iam-policy-binding | 139 ++++++++ .../deploy/custom-target-types/get-iam-policy | 104 ++++++ gcloud/beta/deploy/custom-target-types/help | 13 + .../remove-iam-policy-binding | 144 +++++++++ .../deploy/custom-target-types/set-iam-policy | 87 +++++ gcloud/beta/sql/export/sql | 12 +- gcloud/beta/sql/import/sql | 12 +- gcloud/compute/commitments/create | 17 +- gcloud/compute/instances/help | 3 + gcloud/compute/instances/ops-agents/help | 29 ++ .../instances/ops-agents/policies/help | 24 ++ .../add-layer7-ddos-defense-threshold-config | 6 +- gcloud/container/attached/clusters/register | 10 +- gcloud/container/aws/clusters/create | 10 +- gcloud/container/azure/clusters/create | 10 +- gcloud/container/clusters/create | 10 +- gcloud/container/clusters/update | 10 +- gcloud/container/fleet/help | 3 + gcloud/container/fleet/operations/describe | 64 ++++ gcloud/container/fleet/operations/help | 34 ++ gcloud/container/fleet/operations/list | 67 ++++ gcloud/container/fleet/operations/wait | 63 ++++ gcloud/container/hub/help | 3 + gcloud/container/hub/operations/describe | 64 ++++ gcloud/container/hub/operations/help | 34 ++ gcloud/container/hub/operations/list | 67 ++++ gcloud/container/hub/operations/wait | 62 ++++ .../add-iam-policy-binding | 138 ++++++++ .../deploy/custom-target-types/get-iam-policy | 103 ++++++ gcloud/deploy/custom-target-types/help | 12 + .../remove-iam-policy-binding | 143 +++++++++ .../deploy/custom-target-types/set-iam-policy | 85 +++++ gcloud/run/deploy | 298 ++++++++++-------- gcloud/run/services/update | 276 ++++++++-------- gcloud/sql/export/sql | 12 +- gcloud/sql/import/sql | 12 +- gcloud/workflows/run | 6 + 109 files changed, 4100 insertions(+), 399 deletions(-) rename gcloud/alpha/apphub/discovered-services/{find-discovered => find} (91%) rename gcloud/alpha/apphub/discovered-workloads/{find-discovered => find} (87%) create mode 100644 gcloud/alpha/compute/instance-groups/managed/resize-requests/cancel create mode 100644 gcloud/alpha/compute/instance-groups/managed/resize-requests/create create mode 100644 gcloud/alpha/compute/instance-groups/managed/resize-requests/delete create mode 100644 gcloud/alpha/compute/instance-groups/managed/resize-requests/describe create mode 100644 gcloud/alpha/compute/instance-groups/managed/resize-requests/help create mode 100644 gcloud/alpha/compute/instance-groups/managed/resize-requests/list create mode 100644 gcloud/alpha/deploy/custom-target-types/add-iam-policy-binding create mode 100644 gcloud/alpha/deploy/custom-target-types/get-iam-policy create mode 100644 gcloud/alpha/deploy/custom-target-types/remove-iam-policy-binding create mode 100644 gcloud/alpha/deploy/custom-target-types/set-iam-policy create mode 100644 gcloud/beta/compute/instance-groups/managed/resize-requests/cancel create mode 100644 gcloud/beta/compute/instance-groups/managed/resize-requests/create create mode 100644 gcloud/beta/compute/instance-groups/managed/resize-requests/delete create mode 100644 gcloud/beta/compute/instance-groups/managed/resize-requests/describe create mode 100644 gcloud/beta/compute/instance-groups/managed/resize-requests/help create mode 100644 gcloud/beta/compute/instance-groups/managed/resize-requests/list create mode 100644 gcloud/beta/container/fleet/operations/describe create mode 100644 gcloud/beta/container/fleet/operations/help create mode 100644 gcloud/beta/container/fleet/operations/list create mode 100644 gcloud/beta/container/fleet/operations/wait create mode 100644 gcloud/beta/container/hub/operations/describe create mode 100644 gcloud/beta/container/hub/operations/help create mode 100644 gcloud/beta/container/hub/operations/list create mode 100644 gcloud/beta/container/hub/operations/wait create mode 100644 gcloud/beta/deploy/custom-target-types/add-iam-policy-binding create mode 100644 gcloud/beta/deploy/custom-target-types/get-iam-policy create mode 100644 gcloud/beta/deploy/custom-target-types/remove-iam-policy-binding create mode 100644 gcloud/beta/deploy/custom-target-types/set-iam-policy create mode 100644 gcloud/compute/instances/ops-agents/help create mode 100644 gcloud/compute/instances/ops-agents/policies/help create mode 100644 gcloud/container/fleet/operations/describe create mode 100644 gcloud/container/fleet/operations/help create mode 100644 gcloud/container/fleet/operations/list create mode 100644 gcloud/container/fleet/operations/wait create mode 100644 gcloud/container/hub/operations/describe create mode 100644 gcloud/container/hub/operations/help create mode 100644 gcloud/container/hub/operations/list create mode 100644 gcloud/container/hub/operations/wait create mode 100644 gcloud/deploy/custom-target-types/add-iam-policy-binding create mode 100644 gcloud/deploy/custom-target-types/get-iam-policy create mode 100644 gcloud/deploy/custom-target-types/remove-iam-policy-binding create mode 100644 gcloud/deploy/custom-target-types/set-iam-policy diff --git a/gcloud/_version b/gcloud/_version index b0c5c13bb..51cb33f77 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 462.0.1 -alpha 2024.01.31 -beta 2024.01.31 +Google Cloud SDK 463.0.0 +alpha 2024.02.02 +beta 2024.02.02 bq 2.0.101 bundled-python3-unix 3.11.7 -core 2024.01.31 +core 2024.02.02 gcloud-crc32c 1.0.0 gsutil 5.27 diff --git a/gcloud/alloydb/clusters/create b/gcloud/alloydb/clusters/create index d6f1db8cb..06de3139e 100644 --- a/gcloud/alloydb/clusters/create +++ b/gcloud/alloydb/clusters/create @@ -65,7 +65,8 @@ OPTIONAL FLAGS network, 'testsharednetwork', this would be of the form:--network=projects/testproject/global/networks/testsharednetwork - Continuous Backup configuration. + Continuous Backup configuration. If unspecified, continuous backups are + enabled. --continuous-backup-recovery-window-days=RECOVERY_PERIOD Recovery window of the log files and backups saved to support @@ -118,7 +119,7 @@ OPTIONAL FLAGS on the command line; ▫ set the property core/project. - Automated backup policy. If unspecified, automated backups are enabled. + Automated backup policy. If unspecified, automated backups are disabled. At most one of these can be specified: diff --git a/gcloud/alloydb/instances/create b/gcloud/alloydb/instances/create index a08d17ba1..6212e2c93 100644 --- a/gcloud/alloydb/instances/create +++ b/gcloud/alloydb/instances/create @@ -42,7 +42,7 @@ REQUIRED FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96, 128. --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: diff --git a/gcloud/alloydb/instances/update b/gcloud/alloydb/instances/update index 7cac80143..05a9f8604 100644 --- a/gcloud/alloydb/instances/update +++ b/gcloud/alloydb/instances/update @@ -58,7 +58,7 @@ OPTIONAL FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96, 128. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an diff --git a/gcloud/alpha/alloydb/clusters/create b/gcloud/alpha/alloydb/clusters/create index e7fe01322..3fdc9ce51 100644 --- a/gcloud/alpha/alloydb/clusters/create +++ b/gcloud/alpha/alloydb/clusters/create @@ -69,7 +69,8 @@ OPTIONAL FLAGS network, 'testsharednetwork', this would be of the form:--network=projects/testproject/global/networks/testsharednetwork - Continuous Backup configuration. + Continuous Backup configuration. If unspecified, continuous backups are + enabled. --continuous-backup-recovery-window-days=RECOVERY_PERIOD Recovery window of the log files and backups saved to support @@ -122,7 +123,7 @@ OPTIONAL FLAGS on the command line; ▫ set the property core/project. - Automated backup policy. If unspecified, automated backups are enabled. + Automated backup policy. If unspecified, automated backups are disabled. At most one of these can be specified: diff --git a/gcloud/alpha/alloydb/instances/create b/gcloud/alpha/alloydb/instances/create index 588fe1d24..5999c0e50 100644 --- a/gcloud/alpha/alloydb/instances/create +++ b/gcloud/alpha/alloydb/instances/create @@ -44,7 +44,7 @@ REQUIRED FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96, 128. --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: diff --git a/gcloud/alpha/alloydb/instances/update b/gcloud/alpha/alloydb/instances/update index 98928859a..67249ae0f 100644 --- a/gcloud/alpha/alloydb/instances/update +++ b/gcloud/alpha/alloydb/instances/update @@ -76,7 +76,7 @@ OPTIONAL FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96, 128. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an diff --git a/gcloud/alpha/apphub/discovered-services/find-discovered b/gcloud/alpha/apphub/discovered-services/find similarity index 91% rename from gcloud/alpha/apphub/discovered-services/find-discovered rename to gcloud/alpha/apphub/discovered-services/find index ac91f4de5..880489828 100644 --- a/gcloud/alpha/apphub/discovered-services/find-discovered +++ b/gcloud/alpha/apphub/discovered-services/find @@ -1,9 +1,9 @@ NAME - gcloud alpha apphub discovered-services find-discovered - find Apphub - discovered services that could be added to an application + gcloud alpha apphub discovered-services find - find Apphub discovered + services that could be added to an application SYNOPSIS - gcloud alpha apphub discovered-services find-discovered --location=LOCATION + gcloud alpha apphub discovered-services find --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -15,8 +15,7 @@ EXAMPLES To find DiscoveredServices that could be added to an application in location us-east1, run: - $ gcloud alpha apphub discovered-services find-discovered \ - --location=us-east1 + $ gcloud alpha apphub discovered-services find --location=us-east1 REQUIRED FLAGS Location resource - Location. This represents a Cloud resource. (NOTE) diff --git a/gcloud/alpha/apphub/discovered-services/help b/gcloud/alpha/apphub/discovered-services/help index 75d38fe2e..553477367 100644 --- a/gcloud/alpha/apphub/discovered-services/help +++ b/gcloud/alpha/apphub/discovered-services/help @@ -19,7 +19,7 @@ COMMANDS describe (ALPHA) Describe an Apphub discovered service. - find-discovered + find (ALPHA) Find Apphub discovered services that could be added to an application. diff --git a/gcloud/alpha/apphub/discovered-workloads/find-discovered b/gcloud/alpha/apphub/discovered-workloads/find similarity index 87% rename from gcloud/alpha/apphub/discovered-workloads/find-discovered rename to gcloud/alpha/apphub/discovered-workloads/find index eb477dcdd..dee1262bb 100644 --- a/gcloud/alpha/apphub/discovered-workloads/find-discovered +++ b/gcloud/alpha/apphub/discovered-workloads/find @@ -1,12 +1,11 @@ NAME - gcloud alpha apphub discovered-workloads find-discovered - find discovered - Apphub workloads that could be added to an application + gcloud alpha apphub discovered-workloads find - find discovered Apphub + workloads that could be added to an application SYNOPSIS - gcloud alpha apphub discovered-workloads find-discovered - --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha apphub discovered-workloads find --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Find discovered Apphub workloads that could be added to an @@ -16,8 +15,7 @@ EXAMPLES To find DiscoveredWorkloads that could be added to an application location us-east1, run: - $ gcloud alpha apphub discovered-workloads find-discovered \ - --location=us-east1 + $ gcloud alpha apphub discovered-workloads find --location=us-east1 REQUIRED FLAGS Location resource - Location. This represents a Cloud resource. (NOTE) diff --git a/gcloud/alpha/apphub/discovered-workloads/help b/gcloud/alpha/apphub/discovered-workloads/help index 5835ea9a6..658210684 100644 --- a/gcloud/alpha/apphub/discovered-workloads/help +++ b/gcloud/alpha/apphub/discovered-workloads/help @@ -19,7 +19,7 @@ COMMANDS describe (ALPHA) Describe an Apphub discovered workload. - find-discovered + find (ALPHA) Find discovered Apphub workloads that could be added to an application. diff --git a/gcloud/alpha/compute/commitments/create b/gcloud/alpha/compute/commitments/create index 3c8cba10b..ae6c874d1 100644 --- a/gcloud/alpha/compute/commitments/create +++ b/gcloud/alpha/compute/commitments/create @@ -111,10 +111,18 @@ OPTIONAL FLAGS At most one of these can be specified: --existing-reservation=[name=NAME],[zone=ZONE] - Name and Zone of a reservation to attach to the commitment on - creation. These reservations must be in the same region as the CUD. - example: - --existing-reservation=name=reservation-name,zone=reservation-zone + Details of the existing on-demand reservation or auto-created future + reservation that you want to attach to your commitment. Specify a new + instance of this flag for every existing reservation that you want to + attach. The reservations must be in the same region as the + commitment. + name + The name of the reservation. + zone + The zone of the reservation. For example, to attach an existing + reservation named reservation-name in the zone reservation-zone, + use the following text: + --existing-reservation=name=reservation-name,zone=reservation-zone --reservations-from-file=RESERVATIONS_FROM_FILE Path to a YAML file of multiple reservations' configuration. diff --git a/gcloud/alpha/compute/instance-groups/managed/help b/gcloud/alpha/compute/instance-groups/managed/help index 7969bb14d..d6940b388 100644 --- a/gcloud/alpha/compute/instance-groups/managed/help +++ b/gcloud/alpha/compute/instance-groups/managed/help @@ -24,6 +24,9 @@ GROUPS instance-configs (ALPHA) Manage instance-specific settings in a managed instance group. + resize-requests + (ALPHA) List, create, delete, cancel, and describe ResizeRequests. + rolling-action (ALPHA) Manipulate rolling actions on Compute Engine managed instance groups. diff --git a/gcloud/alpha/compute/instance-groups/managed/resize-requests/cancel b/gcloud/alpha/compute/instance-groups/managed/resize-requests/cancel new file mode 100644 index 000000000..1d4edaefe --- /dev/null +++ b/gcloud/alpha/compute/instance-groups/managed/resize-requests/cancel @@ -0,0 +1,75 @@ +NAME + gcloud alpha compute instance-groups managed resize-requests cancel - + cancel a Compute Engine managed instance group resize request + +SYNOPSIS + gcloud alpha compute instance-groups managed resize-requests cancel + INSTANCE_GROUP_MANAGER + (--resize-request=RESIZE_REQUEST_NAME + | --resize-requests=RESIZE_REQUEST_NAMES,[...]) [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute instance-groups managed resize-requests cancel + cancels one or more Compute Engine managed instance group resize requests. + + You can only cancel a resize request when it is in the ACCEPTED state. + +EXAMPLES + To cancel a resize request for a managed instance group, run the following + command: + + $ gcloud alpha compute instance-groups managed resize-requests \ + cancel my-mig --resize-requests=resize-request-1 + +POSITIONAL ARGUMENTS + INSTANCE_GROUP_MANAGER + Name of the managed instance group to operate on. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --resize-request=RESIZE_REQUEST_NAME + (ALPHA only) The name of the resize request to cancel. + + --resize-requests=RESIZE_REQUEST_NAMES,[...] + A list of comma-separated names of resize requests to cancel. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the managed instance group to operate on. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute instance-groups managed resize-requests cancel + diff --git a/gcloud/alpha/compute/instance-groups/managed/resize-requests/create b/gcloud/alpha/compute/instance-groups/managed/resize-requests/create new file mode 100644 index 000000000..c5516c84b --- /dev/null +++ b/gcloud/alpha/compute/instance-groups/managed/resize-requests/create @@ -0,0 +1,79 @@ +NAME + gcloud alpha compute instance-groups managed resize-requests create - + create a Compute Engine managed instance group resize request + +SYNOPSIS + gcloud alpha compute instance-groups managed resize-requests create + INSTANCE_GROUP_MANAGER --resize-by=RESIZE_BY + --resize-request=RESIZE_REQUEST_NAME + [--requested-run-duration=REQUESTED_RUN_DURATION] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Compute Engine managed instance group resize request. + +EXAMPLES + To create a resize request for a managed instance group, run the following + command: + + $ gcloud alpha compute instance-groups managed resize-requests \ + create my-mig --resize-request=resize-request-1 --resize-by=1 \ + --requested-run-duration=3d1h30s + +POSITIONAL ARGUMENTS + INSTANCE_GROUP_MANAGER + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --resize-by=RESIZE_BY + The number of VMs to resize managed instance group by. + + --resize-request=RESIZE_REQUEST_NAME + The name of the resize request to create. + +OPTIONAL FLAGS + --requested-run-duration=REQUESTED_RUN_DURATION + The time you need the requested VMs to run before being automatically + deleted. The value must be formatted as the number of days, hours, + minutes, or seconds followed by d, h, m, and s respectively. For + example, specify 30m for a duration of 30 minutes or 1d2h3m4s for 1 + day, 2 hours, 3 minutes, and 4 seconds. The value must be between 10m + (10 minutes) and 7d (7 days). + + --zone=ZONE + Zone of the managed instance group to operate on. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute instance-groups managed resize-requests create + diff --git a/gcloud/alpha/compute/instance-groups/managed/resize-requests/delete b/gcloud/alpha/compute/instance-groups/managed/resize-requests/delete new file mode 100644 index 000000000..22b4cb2e8 --- /dev/null +++ b/gcloud/alpha/compute/instance-groups/managed/resize-requests/delete @@ -0,0 +1,69 @@ +NAME + gcloud alpha compute instance-groups managed resize-requests delete - + delete a Compute Engine managed instance group resize request + +SYNOPSIS + gcloud alpha compute instance-groups managed resize-requests delete + INSTANCE_GROUP_MANAGER --resize-requests=RESIZE_REQUEST_NAMES,[...] + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute instance-groups managed resize-requests delete + deletes one or more Compute Engine managed instance group resize requests. + + You can only delete a request when it is in a state SUCCEEDED, FAILED, or + CANCELLED. + +EXAMPLES + To delete a resize request for a managed instance group, run the following + command: + + $ gcloud alpha compute instance-groups managed resize-requests \ + delete my-mig --resize-requests=resize-request-1 + +POSITIONAL ARGUMENTS + INSTANCE_GROUP_MANAGER + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --resize-requests=RESIZE_REQUEST_NAMES,[...] + A list of comma-separated names of resize requests to delete. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the managed instance group to operate on. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute instance-groups managed resize-requests delete + diff --git a/gcloud/alpha/compute/instance-groups/managed/resize-requests/describe b/gcloud/alpha/compute/instance-groups/managed/resize-requests/describe new file mode 100644 index 000000000..e0de86271 --- /dev/null +++ b/gcloud/alpha/compute/instance-groups/managed/resize-requests/describe @@ -0,0 +1,69 @@ +NAME + gcloud alpha compute instance-groups managed resize-requests describe - + describe a Compute Engine managed instance group resize request + resource + +SYNOPSIS + gcloud alpha compute instance-groups managed resize-requests describe + INSTANCE_GROUP_MANAGER --resize-request=RESIZE_REQUEST_NAME + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute instance-groups managed resize-requests + describe describes a Compute Engine managed instance group resize request + resource. + +EXAMPLES + To describe a resize request for a managed instance group, run the + following command: + + $ gcloud alpha compute instance-groups managed resize-requests \ + describe my-mig --resize-request=resize-request-1 + +POSITIONAL ARGUMENTS + INSTANCE_GROUP_MANAGER + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --resize-request=RESIZE_REQUEST_NAME + The name of the resize request to describe. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the managed instance group to operate on. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute instance-groups managed resize-requests \ + describe + diff --git a/gcloud/alpha/compute/instance-groups/managed/resize-requests/help b/gcloud/alpha/compute/instance-groups/managed/resize-requests/help new file mode 100644 index 000000000..3bbdb1cae --- /dev/null +++ b/gcloud/alpha/compute/instance-groups/managed/resize-requests/help @@ -0,0 +1,43 @@ +NAME + gcloud alpha compute instance-groups managed resize-requests - list, + create, delete, cancel, and describe ResizeRequests + +SYNOPSIS + gcloud alpha compute instance-groups managed resize-requests COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List, create, delete, cancel, and describe ResizeRequests. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (ALPHA) Cancel a Compute Engine managed instance group resize request. + + create + (ALPHA) Create a Compute Engine managed instance group resize request. + + delete + (ALPHA) Delete a Compute Engine managed instance group resize request. + + describe + (ALPHA) Describe a Compute Engine managed instance group resize request + resource. + + list + (ALPHA) List Compute Engine managed instance group resize requests. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute instance-groups managed resize-requests + diff --git a/gcloud/alpha/compute/instance-groups/managed/resize-requests/list b/gcloud/alpha/compute/instance-groups/managed/resize-requests/list new file mode 100644 index 000000000..ad51d4e36 --- /dev/null +++ b/gcloud/alpha/compute/instance-groups/managed/resize-requests/list @@ -0,0 +1,97 @@ +NAME + gcloud alpha compute instance-groups managed resize-requests list - list + Compute Engine managed instance group resize requests + +SYNOPSIS + gcloud alpha compute instance-groups managed resize-requests list + INSTANCE_GROUP_MANAGER [--zone=ZONE] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute instance-groups managed resize-requests list + displays all Compute Engine resize requests in a managed instance group. + +EXAMPLES + To list all resize requests in a managed instance group in table form, run: + + $ gcloud alpha compute instance-groups managed resize-requests \ list example-managed-instance-group --zone=us-central1-a + + To list the URIs of all resize requests in a managed instance group, run: + + $ gcloud alpha compute instance-groups managed resize-requests \ list example-managed-instance-group --zone=us-central1-a --uri + +POSITIONAL ARGUMENTS + INSTANCE_GROUP_MANAGER + Name of the managed instance group to operate on. + +FLAGS + --zone=ZONE + Zone of the managed instance group to operate on. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute instance-groups managed resize-requests list + diff --git a/gcloud/alpha/compute/instances/ops-agents/help b/gcloud/alpha/compute/instances/ops-agents/help index 825da5779..40a3873c6 100644 --- a/gcloud/alpha/compute/instances/ops-agents/help +++ b/gcloud/alpha/compute/instances/ops-agents/help @@ -25,7 +25,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 compute instances ops-agents $ gcloud beta compute instances ops-agents diff --git a/gcloud/alpha/compute/instances/ops-agents/policies/help b/gcloud/alpha/compute/instances/ops-agents/policies/help index 15eed786f..179746719 100644 --- a/gcloud/alpha/compute/instances/ops-agents/policies/help +++ b/gcloud/alpha/compute/instances/ops-agents/policies/help @@ -43,7 +43,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 compute instances ops-agents policies $ gcloud beta compute instances ops-agents policies 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 index 7bc82a110..57f06e37d 100644 --- a/gcloud/alpha/compute/security-policies/add-layer7-ddos-defense-threshold-config +++ b/gcloud/alpha/compute/security-policies/add-layer7-ddos-defense-threshold-config @@ -11,6 +11,11 @@ SYNOPSIS [--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] + [--detection-absolute-qps=DETECTION_ABSOLUTE_QPS] + [--detection-load-threshold=DETECTION_LOAD_THRESHOLD] + [--detection-relative-to-baseline-qps=DETECTION_RELATIVE_TO_BASELINE_QPS] + [--traffic-granularity-configs=[type=TYPE[,value=VALUE][, + enableEachUniqueValue=ENABLE_EACH_UNIQUE_VALUE];...;...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -27,7 +32,11 @@ EXAMPLES --auto-deploy-load-threshold=0.7 \ --auto-deploy-confidence-threshold=0.8 \ --auto-deploy-impacted-baseline-threshold=0.1 \ - --auto-deploy-expiration-sec=4800 + --auto-deploy-expiration-sec=4800 \ + --detection-load-threshold=0.4 --detection-absolute-qps=1000 \ + --detection-relative-to-baseline-qps=2.0 \ + --traffic-granularity-configs=type=HTTP_HEADER_HOST,\ + value=www.my-test-host.com;type=HTTP_PATH,enableEachUniqueValue=true POSITIONAL ARGUMENTS NAME @@ -39,7 +48,7 @@ REQUIRED FLAGS OPTIONAL FLAGS --auto-deploy-confidence-threshold=AUTO_DEPLOY_CONFIDENCE_THRESHOLD - The threshold of the confidence of an identified attack over which + The threshold of the confidence of an identified attack, over which auto-deploy takes action. --auto-deploy-expiration-sec=AUTO_DEPLOY_EXPIRATION_SEC @@ -50,7 +59,22 @@ OPTIONAL FLAGS 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. + The threshold on backend's load, over which auto-deploy takes action. + + --detection-absolute-qps=DETECTION_ABSOLUTE_QPS + The absolute QPS of the incoming traffic, over which adaptive + protection detects an attack. + + --detection-load-threshold=DETECTION_LOAD_THRESHOLD + The threshold on backend's load, over which adaptive protection detects + an attack. + + --detection-relative-to-baseline-qps=DETECTION_RELATIVE_TO_BASELINE_QPS + The QPS of the incoming traffic relative to the average baseline QPS, + over which adaptive protection detects an attack. + + --traffic-granularity-configs=[type=TYPE[,value=VALUE][,enableEachUniqueValue=ENABLE_EACH_UNIQUE_VALUE];...;...] + Specify up to 2 configs matching a specifc type/value of traffic. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/attached/clusters/register b/gcloud/alpha/container/attached/clusters/register index e8bec38cd..4f7600cf8 100644 --- a/gcloud/alpha/container/attached/clusters/register +++ b/gcloud/alpha/container/attached/clusters/register @@ -156,7 +156,15 @@ OPTIONAL FLAGS Description for the cluster. --enable-managed-prometheus - Enable managed collection for Managed Service for Prometheus. + Enables managed collection for Managed Service for Prometheus in the + cluster. + + See + https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-managed#enable-mgdcoll-gke + for more info. + + Enabled by default for cluster versions 1.27 or greater, use + --no-enable-managed-prometheus to disable. --logging=COMPONENT,[COMPONENT,...] Set the components that have logging enabled. diff --git a/gcloud/alpha/container/aws/clusters/create b/gcloud/alpha/container/aws/clusters/create index b868b8cc0..30384ccd5 100644 --- a/gcloud/alpha/container/aws/clusters/create +++ b/gcloud/alpha/container/aws/clusters/create @@ -151,7 +151,15 @@ OPTIONAL FLAGS ports TCP/443 and TCP/8132 must be provided. --enable-managed-prometheus - Enable managed collection for Managed Service for Prometheus. + Enables managed collection for Managed Service for Prometheus in the + cluster. + + See + https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-managed#enable-mgdcoll-gke + for more info. + + Enabled by default for cluster versions 1.27 or greater, use + --no-enable-managed-prometheus to disable. --instance-placement=INSTANCE_PLACEMENT Type of the tenancy. INSTANCE_PLACEMENT must be one of: dedicated, diff --git a/gcloud/alpha/container/azure/clusters/create b/gcloud/alpha/container/azure/clusters/create index 829e4035d..47654ac20 100644 --- a/gcloud/alpha/container/azure/clusters/create +++ b/gcloud/alpha/container/azure/clusters/create @@ -174,7 +174,15 @@ OPTIONAL FLAGS Description for the cluster. --enable-managed-prometheus - Enable managed collection for Managed Service for Prometheus. + Enables managed collection for Managed Service for Prometheus in the + cluster. + + See + https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-managed#enable-mgdcoll-gke + for more info. + + Enabled by default for cluster versions 1.27 or greater, use + --no-enable-managed-prometheus to disable. --endpoint-subnet-id=ENDPOINT_SUBNET_ID ARM ID of the subnet where the control plane load balancer is deployed. diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index df5c9fad8..d16753421 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -573,7 +573,15 @@ FLAGS https://cloud.google.com/stackdriver/docs/solutions/gke/installing. --enable-managed-prometheus - Enable managed collection for Managed Service for Prometheus. + Enables managed collection for Managed Service for Prometheus in the + cluster. + + See + https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-managed#enable-mgdcoll-gke + for more info. + + Enabled by default for cluster versions 1.27 or greater, use + --no-enable-managed-prometheus to disable. --enable-master-global-access Use with private clusters to allow access to the master's private diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 4e7624075..0f6c143f5 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -1305,7 +1305,15 @@ REQUIRED FLAGS Disable managed collection for Managed Service for Prometheus. --enable-managed-prometheus - Enable managed collection for Managed Service for Prometheus. + Enables managed collection for Managed Service for Prometheus in + the cluster. + + See + https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-managed#enable-mgdcoll-gke + for more info. + + Enabled by default for cluster versions 1.27 or greater, use + --no-enable-managed-prometheus to disable. --logging-service=LOGGING_SERVICE (DEPRECATED) Logging service to use for the cluster. Options are: diff --git a/gcloud/alpha/container/fleet/operations/describe b/gcloud/alpha/container/fleet/operations/describe index b23466d59..55680114c 100644 --- a/gcloud/alpha/container/fleet/operations/describe +++ b/gcloud/alpha/container/fleet/operations/describe @@ -59,5 +59,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. + access allowlist. These variants are also available: + + $ gcloud container fleet operations describe + + $ gcloud beta container fleet operations describe diff --git a/gcloud/alpha/container/fleet/operations/help b/gcloud/alpha/container/fleet/operations/help index 2671d36f1..7fdd31e46 100644 --- a/gcloud/alpha/container/fleet/operations/help +++ b/gcloud/alpha/container/fleet/operations/help @@ -29,5 +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. + access allowlist. These variants are also available: + + $ gcloud container fleet operations + + $ gcloud beta container fleet operations diff --git a/gcloud/alpha/container/fleet/operations/list b/gcloud/alpha/container/fleet/operations/list index 44719c42a..fc25c546a 100644 --- a/gcloud/alpha/container/fleet/operations/list +++ b/gcloud/alpha/container/fleet/operations/list @@ -63,5 +63,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud container fleet operations list + + $ gcloud beta container fleet operations list diff --git a/gcloud/alpha/container/fleet/operations/wait b/gcloud/alpha/container/fleet/operations/wait index ffc8b7e90..6ed2400d1 100644 --- a/gcloud/alpha/container/fleet/operations/wait +++ b/gcloud/alpha/container/fleet/operations/wait @@ -58,5 +58,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. + access allowlist. These variants are also available: + + $ gcloud container fleet operations wait + + $ gcloud beta container fleet operations wait diff --git a/gcloud/alpha/container/hub/operations/describe b/gcloud/alpha/container/hub/operations/describe index a1a2eed19..c04879d47 100644 --- a/gcloud/alpha/container/hub/operations/describe +++ b/gcloud/alpha/container/hub/operations/describe @@ -59,5 +59,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. + access allowlist. These variants are also available: + + $ gcloud container hub operations describe + + $ gcloud beta container hub operations describe diff --git a/gcloud/alpha/container/hub/operations/help b/gcloud/alpha/container/hub/operations/help index c207c56e3..f0070675b 100644 --- a/gcloud/alpha/container/hub/operations/help +++ b/gcloud/alpha/container/hub/operations/help @@ -29,5 +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. + access allowlist. These variants are also available: + + $ gcloud container hub operations + + $ gcloud beta container hub operations diff --git a/gcloud/alpha/container/hub/operations/list b/gcloud/alpha/container/hub/operations/list index aeac451c4..35fb4814e 100644 --- a/gcloud/alpha/container/hub/operations/list +++ b/gcloud/alpha/container/hub/operations/list @@ -63,5 +63,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud container hub operations list + + $ gcloud beta container hub operations list diff --git a/gcloud/alpha/container/hub/operations/wait b/gcloud/alpha/container/hub/operations/wait index 9e185b938..a4fcacb63 100644 --- a/gcloud/alpha/container/hub/operations/wait +++ b/gcloud/alpha/container/hub/operations/wait @@ -58,5 +58,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. + access allowlist. These variants are also available: + + $ gcloud container hub operations wait + + $ gcloud beta container hub operations wait diff --git a/gcloud/alpha/deploy/custom-target-types/add-iam-policy-binding b/gcloud/alpha/deploy/custom-target-types/add-iam-policy-binding new file mode 100644 index 000000000..a897d8fcf --- /dev/null +++ b/gcloud/alpha/deploy/custom-target-types/add-iam-policy-binding @@ -0,0 +1,141 @@ +NAME + gcloud alpha deploy custom-target-types add-iam-policy-binding - add IAM + policy binding for a Cloud Deploy Custom Target Type + +SYNOPSIS + gcloud alpha deploy custom-target-types add-iam-policy-binding + (CUSTOM_TARGET_TYPE : --region=REGION) --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Adds a policy binding to the IAM policy of a Cloud Deploy Custom + Target Type. One binding consists of a member and a role. + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +EXAMPLES + To add an IAM policy binding for the role of + roles/clouddeploy.customTargetTypeAdmin for the user test-user@gmail.com on + my-custom-target-type with the region us-central1, run: + + $ gcloud alpha deploy custom-target-types add-iam-policy-binding \ + my-custom-target-type --region='us-central1' \ + --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.customTargetTypeAdmin' + +POSITIONAL ARGUMENTS + Custom target type resource - The custom target type for which to add the + IAM policy binding. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +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 clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +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 deploy custom-target-types add-iam-policy-binding + + $ gcloud beta deploy custom-target-types add-iam-policy-binding + diff --git a/gcloud/alpha/deploy/custom-target-types/get-iam-policy b/gcloud/alpha/deploy/custom-target-types/get-iam-policy new file mode 100644 index 000000000..a371ff5b1 --- /dev/null +++ b/gcloud/alpha/deploy/custom-target-types/get-iam-policy @@ -0,0 +1,106 @@ +NAME + gcloud alpha deploy custom-target-types get-iam-policy - get the IAM policy + for a Cloud Deploy Custom Target Type + +SYNOPSIS + gcloud alpha deploy custom-target-types get-iam-policy + (CUSTOM_TARGET_TYPE : --region=REGION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha deploy custom-target-types get-iam-policy displays the + IAM policy associated with a Cloud Deploy Custom Target Type. If formatted + as JSON, the output can be edited and used as a policy file for + set-iam-policy. The output includes an "etag" field identifying the version + emitted and allowing detection of concurrent policy updates; see $ gcloud + alpha deploy custom-target-types set-iam-policy for additional details. + +EXAMPLES + To print the IAM policy for a custom target type my-custom-target-type in + region us-central1, run: + + $ gcloud alpha deploy custom-target-types get-iam-policy \ + my-custom-target-type --region=us-central1 + +POSITIONAL ARGUMENTS + Custom target type resource - The custom target type for which to display + the IAM policy. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +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 deploy custom-target-types get-iam-policy + + $ gcloud beta deploy custom-target-types get-iam-policy + diff --git a/gcloud/alpha/deploy/custom-target-types/help b/gcloud/alpha/deploy/custom-target-types/help index 4ec03cce0..4750b09b2 100644 --- a/gcloud/alpha/deploy/custom-target-types/help +++ b/gcloud/alpha/deploy/custom-target-types/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add-iam-policy-binding + (ALPHA) Add IAM policy binding for a Cloud Deploy Custom Target Type. + delete (ALPHA) Delete a custom target type. @@ -26,9 +29,19 @@ COMMANDS (ALPHA) Returns the .yaml definition of the specified custom target type. + get-iam-policy + (ALPHA) Get the IAM policy for a Cloud Deploy Custom Target Type. + list (ALPHA) List the custom target types. + remove-iam-policy-binding + (ALPHA) Remove an IAM policy binding for a Cloud Deploy Custom Target + Type. + + set-iam-policy + (ALPHA) Set the IAM policy for a Cloud Deploy Custom Target Type. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/deploy/custom-target-types/remove-iam-policy-binding b/gcloud/alpha/deploy/custom-target-types/remove-iam-policy-binding new file mode 100644 index 000000000..c141d423c --- /dev/null +++ b/gcloud/alpha/deploy/custom-target-types/remove-iam-policy-binding @@ -0,0 +1,146 @@ +NAME + gcloud alpha deploy custom-target-types remove-iam-policy-binding - remove + an IAM policy binding for a Cloud Deploy Custom Target Type + +SYNOPSIS + gcloud alpha deploy custom-target-types remove-iam-policy-binding + (CUSTOM_TARGET_TYPE : --region=REGION) --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Removes a policy binding to the IAM policy of a Cloud Deploy Custom + Target Type. One binding consists of a member and a role. + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +EXAMPLES + To remove an IAM policy binding for the role of + roles/clouddeploy.customTargetTypeAdmin for the user test-user@gmail.com on + my-custom-target-type with the region us-central1, run: + + $ gcloud alpha deploy custom-target-types \ + remove-iam-policy-binding my-custom-target-type \ + --region='us-central1' --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.customTargetTypeAdmin' + +POSITIONAL ARGUMENTS + Custom target type resource - The custom target type for which to remove + the IAM policy binding. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +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 clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +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 deploy custom-target-types remove-iam-policy-binding + + $ gcloud beta deploy custom-target-types remove-iam-policy-binding + diff --git a/gcloud/alpha/deploy/custom-target-types/set-iam-policy b/gcloud/alpha/deploy/custom-target-types/set-iam-policy new file mode 100644 index 000000000..fa5444cad --- /dev/null +++ b/gcloud/alpha/deploy/custom-target-types/set-iam-policy @@ -0,0 +1,89 @@ +NAME + gcloud alpha deploy custom-target-types set-iam-policy - set the IAM policy + for a Cloud Deploy Custom Target Type + +SYNOPSIS + gcloud alpha deploy custom-target-types set-iam-policy + (CUSTOM_TARGET_TYPE : --region=REGION) POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Set the IAM policy associated with a Cloud Deploy Custom Target + Type. + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +EXAMPLES + The following command will read an IAM policy defined in a JSON file + policy.json and set it for a custom target type with identifier + my-custom-target-type in region us-central1: + + $ gcloud alpha deploy custom-target-types set-iam-policy \ + my-custom-target-type policy.json --region=us-central1 + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +POSITIONAL ARGUMENTS + Custom target type resource - The custom target type for which to set the + IAM policy. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +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 clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +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 deploy custom-target-types set-iam-policy + + $ gcloud beta deploy custom-target-types set-iam-policy + diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index 617dbe421..c0fb0e55b 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -25,7 +25,8 @@ SYNOPSIS --update-config-maps=[KEY=VALUE,...]] [--[no-]allow-unauthenticated --breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling - --[no-]default-url --description=DESCRIPTION + --[no-]default-url --[no-]deploy-health-check + --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT --[no-]invoker-iam-check --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX @@ -436,9 +437,15 @@ FLAGS --no-cpu-throttling to disable. --[no-]default-url - enables the default url for a run service. Use --default-url to + toggles the default url for a run service. Use --default-url to enable and --no-default-url to disable. + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to start + listening on its port for the deployment to succeed. This check is + enabled by default if unspecified. Use --deploy-health-check to + enable and --no-deploy-health-check to disable. + --description=DESCRIPTION Provides an optional, human-readable description of the service. diff --git a/gcloud/alpha/run/jobs/create b/gcloud/alpha/run/jobs/create index 59a1aec36..40595cba3 100644 --- a/gcloud/alpha/run/jobs/create +++ b/gcloud/alpha/run/jobs/create @@ -2,18 +2,22 @@ NAME gcloud alpha run jobs create - create a Cloud Run job SYNOPSIS - gcloud alpha run jobs create [JOB] --image=IMAGE [--args=[ARG,...]] - [--binary-authorization=POLICY] [--breakglass=JUSTIFICATION] - [--command=[COMMAND,...]] [--cpu=CPU] [--key=KEY] + gcloud alpha run jobs create [JOB] [--binary-authorization=POLICY] + [--breakglass=JUSTIFICATION] [--container=CONTAINER] [--key=KEY] [--labels=[KEY=VALUE,...]] [--max-retries=MAX_RETRIES] - [--memory=MEMORY] [--parallelism=PARALLELISM] [--region=REGION] + [--parallelism=PARALLELISM] [--region=REGION] [--service-account=SERVICE_ACCOUNT] [--set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] - [--set-secrets=[KEY=SECRET_NAME:SECRET_VERSION,...]] [--task-timeout=TASK_TIMEOUT] [--tasks=TASKS; default=1] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] + [--args=[ARG,...] --command=[COMMAND,...] + --cpu=CPU --image=IMAGE --memory=MEMORY --clear-env-vars + | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] + | --remove-env-vars=[KEY,...] + --update-env-vars=[KEY=VALUE,...] --clear-secrets + | --set-secrets=[KEY=VALUE,...] + | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--async | --execute-now --wait] - [--env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...]] [--network=NETWORK --network-tags=[TAG,...] --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] @@ -52,18 +56,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument JOB on the command line; ▸ specify the job name from an interactive prompt. -REQUIRED FLAGS - --image=IMAGE - Name of the container image to deploy (e.g. - us-docker.pkg.dev/cloudrun/container/job:latest). - -OPTIONAL FLAGS - --args=[ARG,...] - Comma-separated arguments passed to the command run by the container - image. If not specified and no '--command' is provided, the container - image's default Cmd is used. Otherwise, if not specified, no arguments - are passed. To reset this field to its default, pass an empty string. - +FLAGS --binary-authorization=POLICY Binary Authorization policy to check against. This must be set to "default". @@ -75,17 +68,9 @@ OPTIONAL FLAGS more information. Next update or deploy command will automatically clear existing breakglass justification. - --command=[COMMAND,...] - Entrypoint for the container image. If not specified, the container - image's default Entrypoint is run. To reset this field to its default, - pass an empty string. - - --cpu=CPU - Set a CPU limit in Kubernetes cpu units. - - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m + --container=CONTAINER + Specifies a container by name. Flags following --container will apply + to the specified container. --key=KEY CMEK key reference to encrypt the container with. @@ -98,9 +83,6 @@ OPTIONAL FLAGS being failed permanently. This applies per-task, not per-job. If set to 0, tasks will only run once and never be retried on failure. - --memory=MEMORY - Set a memory limit. Ex: 1024Mi, 4Gi. - --parallelism=PARALLELISM Number of tasks that may run concurrently. Must be less than or equal to the number of tasks. Set to 0 to unset. @@ -120,13 +102,6 @@ OPTIONAL FLAGS project and region as your Cloud Run resource; otherwise specify :: for the instance. - --set-secrets=[KEY=SECRET_NAME:SECRET_VERSION,...] - Specify secrets to provide as environment variables. For example: - '--set-secrets=ENV=mysecret:latest,OTHER_ENV=othersecret:1' will create - an environment variable named ENV whose value is the latest version of - secret 'mysecret' and an environment variable OTHER_ENV whose value is - version of 1 of secret 'othersecret'. - --task-timeout=TASK_TIMEOUT Set the maximum time (deadline) a job task attempt can run for. In the case of retries, this deadline applies to each attempt of a task. If @@ -165,6 +140,93 @@ OPTIONAL FLAGS https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services for more information. + Container Flags + + If the --container is specified the following arguments may only be specified after a --container flag. + + --args=[ARG,...] + Comma-separated arguments passed to the command run by the + container image. If not specified and no '--command' is provided, + the container image's default Cmd is used. Otherwise, if not + specified, no arguments are passed. To reset this field to its + default, pass an empty string. + + --command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default Entrypoint is run. To reset this field to its + default, pass an empty string. + + --cpu=CPU + Set a CPU limit in Kubernetes cpu units. + + Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run + (fully managed), 4 cpus also requires a minimum 2Gi --memory value. + Examples 2, 2.0, 2000m + + Cloud Run for Anthos and Knative-compatible Kubernetes clusters + support fractional values. Examples .5, 500m, 2 + + --image=IMAGE + Name of the container image to deploy (e.g. + us-docker.pkg.dev/cloudrun/container/job:latest). + + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. + + At most one of these can be specified: + + --clear-env-vars + Remove all environment variables. + + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed + before the new environment variables are added. Example YAML + content: + + KEY_1: "value1" + KEY_2: "value 2" + + --set-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. All + existing environment variables will be removed first. + + Only --update-env-vars and --remove-env-vars can be used together. + If both are specified, --remove-env-vars will be applied first. + + --remove-env-vars=[KEY,...] + List of environment variables to be removed. + + --update-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + Specify secrets to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. Values should be in the form + SECRET_NAME:SECRET_VERSION. For example: + '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' + will mount a volume at '/secrets/api' containing a file 'key' with the + latest version of secret 'mysecret'. An environment variable named ENV + will also be created whose value is version 1 of secret 'othersecret'. + + At most one of these can be specified: + + --clear-secrets + Remove all secrets. + + --set-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. All existing secrets + will be removed first. + + Only --update-secrets and --remove-secrets can be used together. If + both are specified, --remove-secrets will be applied first. + + --remove-secrets=[KEY,...] + List of secrets to be removed. + + --update-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. + At most one of these can be specified: --async @@ -183,18 +245,6 @@ OPTIONAL FLAGS not set, gcloud exits successfully when the execution has started. Implies --execute-now. - At most one of these can be specified: - - --env-vars-file=FILE_PATH - Path to a local YAML file with definitions for all environment - variables. Example YAML content: - - KEY_1: "value1" - KEY_2: "value 2" - - --set-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. - Direct VPC egress setting flags group. --network=NETWORK diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 59b7d339a..104bfa563 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -20,7 +20,8 @@ SYNOPSIS | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost - --[no-]cpu-throttling --[no-]default-url --description=DESCRIPTION + --[no-]cpu-throttling --[no-]default-url --[no-]deploy-health-check + --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT --[no-]invoker-iam-check --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX @@ -320,9 +321,15 @@ FLAGS --no-cpu-throttling to disable. --[no-]default-url - enables the default url for a run service. Use --default-url to + toggles the default url for a run service. Use --default-url to enable and --no-default-url to disable. + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to start + listening on its port for the deployment to succeed. This check is + enabled by default if unspecified. Use --deploy-health-check to + enable and --no-deploy-health-check to disable. + --description=DESCRIPTION Provides an optional, human-readable description of the service. diff --git a/gcloud/alpha/spanner/operations/list b/gcloud/alpha/spanner/operations/list index e8a74691b..3824156f0 100644 --- a/gcloud/alpha/spanner/operations/list +++ b/gcloud/alpha/spanner/operations/list @@ -76,6 +76,10 @@ FLAGS database operations associated with the databases in the instance. When a database is specified (--database), the command would return database operations for the given database. + DATABASE_CHANGE_QUORUM + Database change quorum operations are returned for all databases in + the given instance (--instance only) or only those associated with + the given database (--database). DATABASE_CREATE Database create operations are returned for all databases in the given instance (--instance only) or only those associated with the diff --git a/gcloud/alpha/sql/export/sql b/gcloud/alpha/sql/export/sql index cea73dc84..39b691977 100644 --- a/gcloud/alpha/sql/export/sql +++ b/gcloud/alpha/sql/export/sql @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha sql export sql INSTANCE URI [--async] [--database=DATABASE,[DATABASE,...], -d DATABASE,[DATABASE,...]] - [--offload] [--table=TABLE,[TABLE,...], -t TABLE,[TABLE,...]] + [--offload] [--parallel] + [--table=TABLE,[TABLE,...], -t TABLE,[TABLE,...]] [--threads=THREADS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -42,11 +43,20 @@ FLAGS source instances and allows other operations to be performed while the export is in progress. + --parallel + Perform a parallel export. This flag is only applicable to MySQL and + Postgres. + --table=TABLE,[TABLE,...], -t TABLE,[TABLE,...] Tables to export from the specified database. If you specify tables, specify one and only one database. For PostgreSQL instances, only one table can be exported at a time. + --threads=THREADS + Specifies the number of threads to use for the parallel export. If + --parallel is specified and this flag is not provided, Cloud SQL uses a + default thread count to optimize performance. + 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/sql/import/sql b/gcloud/alpha/sql/import/sql index b82c82dfb..057b4f715 100644 --- a/gcloud/alpha/sql/import/sql +++ b/gcloud/alpha/sql/import/sql @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha sql import sql INSTANCE URI [--async] - [--database=DATABASE, -d DATABASE] [--user=USER] [GCLOUD_WIDE_FLAG ...] + [--database=DATABASE, -d DATABASE] [--parallel] [--threads=THREADS] + [--user=USER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha sql import sql imports data into a Cloud SQL instance @@ -45,6 +46,15 @@ FLAGS specified in the file to be imported. If your SQL dump file includes a database statement, it will override the database set in this flag. + --parallel + Perform a parallel import. This flag is only applicable to MySQL and + Postgres. + + --threads=THREADS + Specifies the number of threads to use for the parallel import. If + --parallel is specified and this flag is not provided, Cloud SQL uses a + default thread count to optimize performance. + --user=USER PostgreSQL user for this import operation. diff --git a/gcloud/beta/alloydb/clusters/create b/gcloud/beta/alloydb/clusters/create index 550b8e3b0..dd0f9d9dd 100644 --- a/gcloud/beta/alloydb/clusters/create +++ b/gcloud/beta/alloydb/clusters/create @@ -65,7 +65,8 @@ OPTIONAL FLAGS network, 'testsharednetwork', this would be of the form:--network=projects/testproject/global/networks/testsharednetwork - Continuous Backup configuration. + Continuous Backup configuration. If unspecified, continuous backups are + enabled. --continuous-backup-recovery-window-days=RECOVERY_PERIOD Recovery window of the log files and backups saved to support @@ -118,7 +119,7 @@ OPTIONAL FLAGS on the command line; ▫ set the property core/project. - Automated backup policy. If unspecified, automated backups are enabled. + Automated backup policy. If unspecified, automated backups are disabled. At most one of these can be specified: diff --git a/gcloud/beta/alloydb/instances/create b/gcloud/beta/alloydb/instances/create index 2d3234d41..832da2a43 100644 --- a/gcloud/beta/alloydb/instances/create +++ b/gcloud/beta/alloydb/instances/create @@ -44,7 +44,7 @@ REQUIRED FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96, 128. --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: diff --git a/gcloud/beta/alloydb/instances/update b/gcloud/beta/alloydb/instances/update index 60e57a34a..acbc395c4 100644 --- a/gcloud/beta/alloydb/instances/update +++ b/gcloud/beta/alloydb/instances/update @@ -76,7 +76,7 @@ OPTIONAL FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96, 128. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an diff --git a/gcloud/beta/compute/commitments/create b/gcloud/beta/compute/commitments/create index 4be9b2f47..fec2edb21 100644 --- a/gcloud/beta/compute/commitments/create +++ b/gcloud/beta/compute/commitments/create @@ -8,7 +8,8 @@ SYNOPSIS [--merge-source-commitments=MERGE_SOURCE_COMMITMENTS] [--region=REGION] [--split-source-commitment=SPLIT_SOURCE_COMMITMENT] [--type=TYPE; default="general-purpose"] - [--reservations-from-file=RESERVATIONS_FROM_FILE + [--existing-reservation=[name=NAME],[zone=ZONE] + | --reservations-from-file=RESERVATIONS_FROM_FILE | [--reservation=RESERVATION : --reservation-zone=RESERVATION_ZONE --accelerator=[count=COUNT],[type=TYPE] --local-ssd=[interface=INTERFACE],[size=SIZE] @@ -109,6 +110,20 @@ OPTIONAL FLAGS At most one of these can be specified: + --existing-reservation=[name=NAME],[zone=ZONE] + Details of the existing on-demand reservation or auto-created future + reservation that you want to attach to your commitment. Specify a new + instance of this flag for every existing reservation that you want to + attach. The reservations must be in the same region as the + commitment. + name + The name of the reservation. + zone + The zone of the reservation. For example, to attach an existing + reservation named reservation-name in the zone reservation-zone, + use the following text: + --existing-reservation=name=reservation-name,zone=reservation-zone + --reservations-from-file=RESERVATIONS_FROM_FILE Path to a YAML file of multiple reservations' configuration. diff --git a/gcloud/beta/compute/instance-groups/managed/help b/gcloud/beta/compute/instance-groups/managed/help index 64d8327be..b58a4606b 100644 --- a/gcloud/beta/compute/instance-groups/managed/help +++ b/gcloud/beta/compute/instance-groups/managed/help @@ -24,6 +24,9 @@ GROUPS instance-configs (BETA) Manage instance-specific settings in a managed instance group. + resize-requests + (BETA) List, create, delete, cancel, and describe ResizeRequests. + rolling-action (BETA) Manipulate rolling actions on Compute Engine managed instance groups. diff --git a/gcloud/beta/compute/instance-groups/managed/resize-requests/cancel b/gcloud/beta/compute/instance-groups/managed/resize-requests/cancel new file mode 100644 index 000000000..bedc92da4 --- /dev/null +++ b/gcloud/beta/compute/instance-groups/managed/resize-requests/cancel @@ -0,0 +1,66 @@ +NAME + gcloud beta compute instance-groups managed resize-requests cancel - cancel + a Compute Engine managed instance group resize request + +SYNOPSIS + gcloud beta compute instance-groups managed resize-requests cancel + INSTANCE_GROUP_MANAGER --resize-requests=RESIZE_REQUEST_NAMES,[...] + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute instance-groups managed resize-requests cancel + cancels one or more Compute Engine managed instance group resize requests. + + You can only cancel a resize request when it is in the ACCEPTED state. + +EXAMPLES + To cancel a resize request for a managed instance group, run the following + command: + + $ gcloud beta compute instance-groups managed resize-requests \ + cancel my-mig --resize-requests=resize-request-1 + +POSITIONAL ARGUMENTS + INSTANCE_GROUP_MANAGER + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --resize-requests=RESIZE_REQUEST_NAMES,[...] + A list of comma-separated names of resize requests to cancel. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the managed instance group to operate on. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute instance-groups managed resize-requests cancel + diff --git a/gcloud/beta/compute/instance-groups/managed/resize-requests/create b/gcloud/beta/compute/instance-groups/managed/resize-requests/create new file mode 100644 index 000000000..d34a11e1a --- /dev/null +++ b/gcloud/beta/compute/instance-groups/managed/resize-requests/create @@ -0,0 +1,76 @@ +NAME + gcloud beta compute instance-groups managed resize-requests create - create + a Compute Engine managed instance group resize request + +SYNOPSIS + gcloud beta compute instance-groups managed resize-requests create + INSTANCE_GROUP_MANAGER --requested-run-duration=REQUESTED_RUN_DURATION + --resize-by=RESIZE_BY --resize-request=RESIZE_REQUEST_NAME + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Compute Engine managed instance group resize request. + +EXAMPLES + To create a resize request for a managed instance group, run the following + command: + + $ gcloud beta compute instance-groups managed resize-requests \ + create my-mig --resize-request=resize-request-1 --resize-by=1 \ + --requested-run-duration=3d1h30s + +POSITIONAL ARGUMENTS + INSTANCE_GROUP_MANAGER + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --requested-run-duration=REQUESTED_RUN_DURATION + The time you need the requested VMs to run before being automatically + deleted. The value must be formatted as the number of days, hours, + minutes, or seconds followed by d, h, m, and s respectively. For + example, specify 30m for a duration of 30 minutes or 1d2h3m4s for 1 + day, 2 hours, 3 minutes, and 4 seconds. The value must be between 10m + (10 minutes) and 7d (7 days). + + --resize-by=RESIZE_BY + The number of VMs to resize managed instance group by. + + --resize-request=RESIZE_REQUEST_NAME + The name of the resize request to create. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the managed instance group to operate on. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute instance-groups managed resize-requests create + diff --git a/gcloud/beta/compute/instance-groups/managed/resize-requests/delete b/gcloud/beta/compute/instance-groups/managed/resize-requests/delete new file mode 100644 index 000000000..7456d4cf6 --- /dev/null +++ b/gcloud/beta/compute/instance-groups/managed/resize-requests/delete @@ -0,0 +1,67 @@ +NAME + gcloud beta compute instance-groups managed resize-requests delete - delete + a Compute Engine managed instance group resize request + +SYNOPSIS + gcloud beta compute instance-groups managed resize-requests delete + INSTANCE_GROUP_MANAGER --resize-requests=RESIZE_REQUEST_NAMES,[...] + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute instance-groups managed resize-requests delete + deletes one or more Compute Engine managed instance group resize requests. + + You can only delete a request when it is in a state SUCCEEDED, FAILED, or + CANCELLED. + +EXAMPLES + To delete a resize request for a managed instance group, run the following + command: + + $ gcloud beta compute instance-groups managed resize-requests \ + delete my-mig --resize-requests=resize-request-1 + +POSITIONAL ARGUMENTS + INSTANCE_GROUP_MANAGER + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --resize-requests=RESIZE_REQUEST_NAMES,[...] + A list of comma-separated names of resize requests to delete. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the managed instance group to operate on. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute instance-groups managed resize-requests delete + diff --git a/gcloud/beta/compute/instance-groups/managed/resize-requests/describe b/gcloud/beta/compute/instance-groups/managed/resize-requests/describe new file mode 100644 index 000000000..39bf4e0f2 --- /dev/null +++ b/gcloud/beta/compute/instance-groups/managed/resize-requests/describe @@ -0,0 +1,66 @@ +NAME + gcloud beta compute instance-groups managed resize-requests describe - + describe a Compute Engine managed instance group resize request + resource + +SYNOPSIS + gcloud beta compute instance-groups managed resize-requests describe + INSTANCE_GROUP_MANAGER --resize-request=RESIZE_REQUEST_NAME + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute instance-groups managed resize-requests describe + describes a Compute Engine managed instance group resize request resource. + +EXAMPLES + To describe a resize request for a managed instance group, run the + following command: + + $ gcloud beta compute instance-groups managed resize-requests \ + describe my-mig --resize-request=resize-request-1 + +POSITIONAL ARGUMENTS + INSTANCE_GROUP_MANAGER + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --resize-request=RESIZE_REQUEST_NAME + The name of the resize request to describe. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the managed instance group to operate on. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute instance-groups managed resize-requests \ + describe + diff --git a/gcloud/beta/compute/instance-groups/managed/resize-requests/help b/gcloud/beta/compute/instance-groups/managed/resize-requests/help new file mode 100644 index 000000000..1adc52904 --- /dev/null +++ b/gcloud/beta/compute/instance-groups/managed/resize-requests/help @@ -0,0 +1,41 @@ +NAME + gcloud beta compute instance-groups managed resize-requests - list, create, + delete, cancel, and describe ResizeRequests + +SYNOPSIS + gcloud beta compute instance-groups managed resize-requests COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List, create, delete, cancel, and describe ResizeRequests. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (BETA) Cancel a Compute Engine managed instance group resize request. + + create + (BETA) Create a Compute Engine managed instance group resize request. + + delete + (BETA) Delete a Compute Engine managed instance group resize request. + + describe + (BETA) Describe a Compute Engine managed instance group resize request + resource. + + list + (BETA) List Compute Engine managed instance group resize requests. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute instance-groups managed resize-requests + diff --git a/gcloud/beta/compute/instance-groups/managed/resize-requests/list b/gcloud/beta/compute/instance-groups/managed/resize-requests/list new file mode 100644 index 000000000..190f18a4f --- /dev/null +++ b/gcloud/beta/compute/instance-groups/managed/resize-requests/list @@ -0,0 +1,97 @@ +NAME + gcloud beta compute instance-groups managed resize-requests list - list + Compute Engine managed instance group resize requests + +SYNOPSIS + gcloud beta compute instance-groups managed resize-requests list + INSTANCE_GROUP_MANAGER [--zone=ZONE] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute instance-groups managed resize-requests list + displays all Compute Engine resize requests in a managed instance group. + +EXAMPLES + To list all resize requests in a managed instance group in table form, run: + + $ gcloud beta compute instance-groups managed resize-requests list \ + example-managed-instance-group --zone=us-central1-a + + To list the URIs of all resize requests in a managed instance group, run: + + $ gcloud beta compute instance-groups managed resize-requests list \ + example-managed-instance-group --zone=us-central1-a --uri + +POSITIONAL ARGUMENTS + INSTANCE_GROUP_MANAGER + Name of the managed instance group to operate on. + +FLAGS + --zone=ZONE + Zone of the managed instance group to operate on. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute instance-groups managed resize-requests list + diff --git a/gcloud/beta/compute/instances/ops-agents/help b/gcloud/beta/compute/instances/ops-agents/help index 5d440ac13..68080f71c 100644 --- a/gcloud/beta/compute/instances/ops-agents/help +++ b/gcloud/beta/compute/instances/ops-agents/help @@ -21,8 +21,10 @@ GROUPS update, and uninstall agents for Compute Engine VM instances. 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 compute instances ops-agents $ gcloud alpha compute instances ops-agents diff --git a/gcloud/beta/compute/instances/ops-agents/policies/help b/gcloud/beta/compute/instances/ops-agents/policies/help index 3557b11ac..056487425 100644 --- a/gcloud/beta/compute/instances/ops-agents/policies/help +++ b/gcloud/beta/compute/instances/ops-agents/policies/help @@ -40,8 +40,10 @@ COMMANDS policy. 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 compute instances ops-agents policies $ gcloud alpha compute instances ops-agents policies 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 index 4745275a6..7d73833ab 100644 --- a/gcloud/beta/compute/security-policies/add-layer7-ddos-defense-threshold-config +++ b/gcloud/beta/compute/security-policies/add-layer7-ddos-defense-threshold-config @@ -11,6 +11,11 @@ SYNOPSIS [--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] + [--detection-absolute-qps=DETECTION_ABSOLUTE_QPS] + [--detection-load-threshold=DETECTION_LOAD_THRESHOLD] + [--detection-relative-to-baseline-qps=DETECTION_RELATIVE_TO_BASELINE_QPS] + [--traffic-granularity-configs=[type=TYPE[,value=VALUE][, + enableEachUniqueValue=ENABLE_EACH_UNIQUE_VALUE];...;...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -27,7 +32,11 @@ EXAMPLES --auto-deploy-load-threshold=0.7 \ --auto-deploy-confidence-threshold=0.8 \ --auto-deploy-impacted-baseline-threshold=0.1 \ - --auto-deploy-expiration-sec=4800 + --auto-deploy-expiration-sec=4800 \ + --detection-load-threshold=0.4 --detection-absolute-qps=1000 \ + --detection-relative-to-baseline-qps=2.0 \ + --traffic-granularity-configs=type=HTTP_HEADER_HOST,\ + value=www.my-test-host.com;type=HTTP_PATH,enableEachUniqueValue=true POSITIONAL ARGUMENTS NAME @@ -39,7 +48,7 @@ REQUIRED FLAGS OPTIONAL FLAGS --auto-deploy-confidence-threshold=AUTO_DEPLOY_CONFIDENCE_THRESHOLD - The threshold of the confidence of an identified attack over which + The threshold of the confidence of an identified attack, over which auto-deploy takes action. --auto-deploy-expiration-sec=AUTO_DEPLOY_EXPIRATION_SEC @@ -50,7 +59,22 @@ OPTIONAL FLAGS 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. + The threshold on backend's load, over which auto-deploy takes action. + + --detection-absolute-qps=DETECTION_ABSOLUTE_QPS + The absolute QPS of the incoming traffic, over which adaptive + protection detects an attack. + + --detection-load-threshold=DETECTION_LOAD_THRESHOLD + The threshold on backend's load, over which adaptive protection detects + an attack. + + --detection-relative-to-baseline-qps=DETECTION_RELATIVE_TO_BASELINE_QPS + The QPS of the incoming traffic relative to the average baseline QPS, + over which adaptive protection detects an attack. + + --traffic-granularity-configs=[type=TYPE[,value=VALUE][,enableEachUniqueValue=ENABLE_EACH_UNIQUE_VALUE];...;...] + Specify up to 2 configs matching a specifc type/value of traffic. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index c3c9be58b..124a09585 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -569,7 +569,15 @@ FLAGS https://cloud.google.com/stackdriver/docs/solutions/gke/installing. --enable-managed-prometheus - Enable managed collection for Managed Service for Prometheus. + Enables managed collection for Managed Service for Prometheus in the + cluster. + + See + https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-managed#enable-mgdcoll-gke + for more info. + + Enabled by default for cluster versions 1.27 or greater, use + --no-enable-managed-prometheus to disable. --enable-master-global-access Use with private clusters to allow access to the master's private diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index a9b7eebc8..88012c48f 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -1294,7 +1294,15 @@ REQUIRED FLAGS Disable managed collection for Managed Service for Prometheus. --enable-managed-prometheus - Enable managed collection for Managed Service for Prometheus. + Enables managed collection for Managed Service for Prometheus in + the cluster. + + See + https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-managed#enable-mgdcoll-gke + for more info. + + Enabled by default for cluster versions 1.27 or greater, use + --no-enable-managed-prometheus to disable. --logging-service=LOGGING_SERVICE (DEPRECATED) Logging service to use for the cluster. Options are: diff --git a/gcloud/beta/container/fleet/help b/gcloud/beta/container/fleet/help index de9076999..36ca89cdc 100644 --- a/gcloud/beta/container/fleet/help +++ b/gcloud/beta/container/fleet/help @@ -79,6 +79,9 @@ GROUPS multi-cluster-services (BETA) Manage Multi-cluster Services Feature. + operations + (BETA) Manage Anthos fleet long-running operations. + policycontroller (BETA) Manage Policy Controller Feature. diff --git a/gcloud/beta/container/fleet/operations/describe b/gcloud/beta/container/fleet/operations/describe new file mode 100644 index 000000000..8027442ef --- /dev/null +++ b/gcloud/beta/container/fleet/operations/describe @@ -0,0 +1,65 @@ +NAME + gcloud beta container fleet operations describe - describe a long-running + operation + +SYNOPSIS + gcloud beta container fleet operations describe + (OPERATION : --location=LOCATION; default="global") + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a long-running operation. + +EXAMPLES + To describe a long-running operation in location us-west1, run: + + $ gcloud beta container fleet operations describe OPERATION \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Operation resource - operation 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the name attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION; default="global" + Google Cloud location for the operation. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet operations describe + + $ gcloud alpha container fleet operations describe + diff --git a/gcloud/beta/container/fleet/operations/help b/gcloud/beta/container/fleet/operations/help new file mode 100644 index 000000000..58a0222bb --- /dev/null +++ b/gcloud/beta/container/fleet/operations/help @@ -0,0 +1,35 @@ +NAME + gcloud beta container fleet operations - manage Anthos fleet long-running + operations + +SYNOPSIS + gcloud beta container fleet operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Anthos fleet long-running operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describe a long-running operation. + + list + (BETA) List long-running operations. + + wait + (BETA) Poll a long-running operation for completion. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet operations + + $ gcloud alpha container fleet operations + diff --git a/gcloud/beta/container/fleet/operations/list b/gcloud/beta/container/fleet/operations/list new file mode 100644 index 000000000..22d76e5e4 --- /dev/null +++ b/gcloud/beta/container/fleet/operations/list @@ -0,0 +1,69 @@ +NAME + gcloud beta container fleet operations list - list long-running operations + +SYNOPSIS + gcloud beta container fleet operations list + [--location=LOCATION; default="-"] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List long-running operations. + +EXAMPLES + To list all operations in location us-west1, run: + + $ gcloud beta container fleet operations list --location=us-west1 + +FLAGS + --location=LOCATION; default="-" + The location name. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet operations list + + $ gcloud alpha container fleet operations list + diff --git a/gcloud/beta/container/fleet/operations/wait b/gcloud/beta/container/fleet/operations/wait new file mode 100644 index 000000000..327da25c3 --- /dev/null +++ b/gcloud/beta/container/fleet/operations/wait @@ -0,0 +1,64 @@ +NAME + gcloud beta container fleet operations wait - poll a long-running operation + for completion + +SYNOPSIS + gcloud beta container fleet operations wait + (OPERATION : --location=LOCATION; default="global") + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Poll a long-running operation for completion. + +EXAMPLES + To wait for an operation in location us-west1 to complete, run: + + $ gcloud beta container fleet operations wait OPERATION \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Operation resource - operation to wait. 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the name attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION; default="global" + Google Cloud location for the operation. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet operations wait + + $ gcloud alpha container fleet operations wait + diff --git a/gcloud/beta/container/hub/help b/gcloud/beta/container/hub/help index d25dd8e36..dd292f646 100644 --- a/gcloud/beta/container/hub/help +++ b/gcloud/beta/container/hub/help @@ -79,6 +79,9 @@ GROUPS multi-cluster-services (BETA) Manage Multi-cluster Services Feature. + operations + (BETA) Manage Anthos fleet long-running operations. + policycontroller (BETA) Manage Policy Controller Feature. diff --git a/gcloud/beta/container/hub/operations/describe b/gcloud/beta/container/hub/operations/describe new file mode 100644 index 000000000..d892c03d0 --- /dev/null +++ b/gcloud/beta/container/hub/operations/describe @@ -0,0 +1,65 @@ +NAME + gcloud beta container hub operations describe - describe a long-running + operation + +SYNOPSIS + gcloud beta container hub operations describe + (OPERATION : --location=LOCATION; default="global") + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a long-running operation. + +EXAMPLES + To describe a long-running operation in location us-west1, run: + + $ gcloud beta container hub operations describe OPERATION \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Operation resource - operation 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the name attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION; default="global" + Google Cloud location for the operation. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub operations describe + + $ gcloud alpha container hub operations describe + diff --git a/gcloud/beta/container/hub/operations/help b/gcloud/beta/container/hub/operations/help new file mode 100644 index 000000000..3a3d90ea5 --- /dev/null +++ b/gcloud/beta/container/hub/operations/help @@ -0,0 +1,35 @@ +NAME + gcloud beta container hub operations - manage Anthos fleet long-running + operations + +SYNOPSIS + gcloud beta container hub operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Anthos fleet long-running operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describe a long-running operation. + + list + (BETA) List long-running operations. + + wait + (BETA) Poll a long-running operation for completion. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub operations + + $ gcloud alpha container hub operations + diff --git a/gcloud/beta/container/hub/operations/list b/gcloud/beta/container/hub/operations/list new file mode 100644 index 000000000..d02eadc26 --- /dev/null +++ b/gcloud/beta/container/hub/operations/list @@ -0,0 +1,69 @@ +NAME + gcloud beta container hub operations list - list long-running operations + +SYNOPSIS + gcloud beta container hub operations list + [--location=LOCATION; default="-"] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List long-running operations. + +EXAMPLES + To list all operations in location us-west1, run: + + $ gcloud beta container hub operations list --location=us-west1 + +FLAGS + --location=LOCATION; default="-" + The location name. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub operations list + + $ gcloud alpha container hub operations list + diff --git a/gcloud/beta/container/hub/operations/wait b/gcloud/beta/container/hub/operations/wait new file mode 100644 index 000000000..e71a942f9 --- /dev/null +++ b/gcloud/beta/container/hub/operations/wait @@ -0,0 +1,64 @@ +NAME + gcloud beta container hub operations wait - poll a long-running operation + for completion + +SYNOPSIS + gcloud beta container hub operations wait + (OPERATION : --location=LOCATION; default="global") + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Poll a long-running operation for completion. + +EXAMPLES + To wait for an operation in location us-west1 to complete, run: + + $ gcloud beta container hub operations wait OPERATION \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Operation resource - operation to wait. 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the name attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION; default="global" + Google Cloud location for the operation. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub operations wait + + $ gcloud alpha container hub operations wait + diff --git a/gcloud/beta/deploy/custom-target-types/add-iam-policy-binding b/gcloud/beta/deploy/custom-target-types/add-iam-policy-binding new file mode 100644 index 000000000..1c181762a --- /dev/null +++ b/gcloud/beta/deploy/custom-target-types/add-iam-policy-binding @@ -0,0 +1,139 @@ +NAME + gcloud beta deploy custom-target-types add-iam-policy-binding - add IAM + policy binding for a Cloud Deploy Custom Target Type + +SYNOPSIS + gcloud beta deploy custom-target-types add-iam-policy-binding + (CUSTOM_TARGET_TYPE : --region=REGION) --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Adds a policy binding to the IAM policy of a Cloud Deploy Custom + Target Type. One binding consists of a member and a role. + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +EXAMPLES + To add an IAM policy binding for the role of + roles/clouddeploy.customTargetTypeAdmin for the user test-user@gmail.com on + my-custom-target-type with the region us-central1, run: + + $ gcloud beta deploy custom-target-types add-iam-policy-binding \ + my-custom-target-type --region='us-central1' \ + --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.customTargetTypeAdmin' + +POSITIONAL ARGUMENTS + Custom target type resource - The custom target type for which to add the + IAM policy binding. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +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 clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy custom-target-types add-iam-policy-binding + + $ gcloud alpha deploy custom-target-types add-iam-policy-binding + diff --git a/gcloud/beta/deploy/custom-target-types/get-iam-policy b/gcloud/beta/deploy/custom-target-types/get-iam-policy new file mode 100644 index 000000000..8c63ae77a --- /dev/null +++ b/gcloud/beta/deploy/custom-target-types/get-iam-policy @@ -0,0 +1,104 @@ +NAME + gcloud beta deploy custom-target-types get-iam-policy - get the IAM policy + for a Cloud Deploy Custom Target Type + +SYNOPSIS + gcloud beta deploy custom-target-types get-iam-policy + (CUSTOM_TARGET_TYPE : --region=REGION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta deploy custom-target-types get-iam-policy displays the + IAM policy associated with a Cloud Deploy Custom Target Type. If formatted + as JSON, the output can be edited and used as a policy file for + set-iam-policy. The output includes an "etag" field identifying the version + emitted and allowing detection of concurrent policy updates; see $ gcloud + beta deploy custom-target-types set-iam-policy for additional details. + +EXAMPLES + To print the IAM policy for a custom target type my-custom-target-type in + region us-central1, run: + + $ gcloud beta deploy custom-target-types get-iam-policy \ + my-custom-target-type --region=us-central1 + +POSITIONAL ARGUMENTS + Custom target type resource - The custom target type for which to display + the IAM policy. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy custom-target-types get-iam-policy + + $ gcloud alpha deploy custom-target-types get-iam-policy + diff --git a/gcloud/beta/deploy/custom-target-types/help b/gcloud/beta/deploy/custom-target-types/help index 24a55e809..ceda96bbd 100644 --- a/gcloud/beta/deploy/custom-target-types/help +++ b/gcloud/beta/deploy/custom-target-types/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add-iam-policy-binding + (BETA) Add IAM policy binding for a Cloud Deploy Custom Target Type. + delete (BETA) Delete a custom target type. @@ -26,9 +29,19 @@ COMMANDS (BETA) Returns the .yaml definition of the specified custom target type. + get-iam-policy + (BETA) Get the IAM policy for a Cloud Deploy Custom Target Type. + list (BETA) List the custom target types. + remove-iam-policy-binding + (BETA) Remove an IAM policy binding for a Cloud Deploy Custom Target + Type. + + set-iam-policy + (BETA) Set the IAM policy for a Cloud Deploy Custom Target Type. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/deploy/custom-target-types/remove-iam-policy-binding b/gcloud/beta/deploy/custom-target-types/remove-iam-policy-binding new file mode 100644 index 000000000..f4f11d56a --- /dev/null +++ b/gcloud/beta/deploy/custom-target-types/remove-iam-policy-binding @@ -0,0 +1,144 @@ +NAME + gcloud beta deploy custom-target-types remove-iam-policy-binding - remove + an IAM policy binding for a Cloud Deploy Custom Target Type + +SYNOPSIS + gcloud beta deploy custom-target-types remove-iam-policy-binding + (CUSTOM_TARGET_TYPE : --region=REGION) --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Removes a policy binding to the IAM policy of a Cloud Deploy Custom + Target Type. One binding consists of a member and a role. + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +EXAMPLES + To remove an IAM policy binding for the role of + roles/clouddeploy.customTargetTypeAdmin for the user test-user@gmail.com on + my-custom-target-type with the region us-central1, run: + + $ gcloud beta deploy custom-target-types remove-iam-policy-binding \ + my-custom-target-type --region='us-central1' \ + --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.customTargetTypeAdmin' + +POSITIONAL ARGUMENTS + Custom target type resource - The custom target type for which to remove + the IAM policy binding. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +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 clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy custom-target-types remove-iam-policy-binding + + $ gcloud alpha deploy custom-target-types remove-iam-policy-binding + diff --git a/gcloud/beta/deploy/custom-target-types/set-iam-policy b/gcloud/beta/deploy/custom-target-types/set-iam-policy new file mode 100644 index 000000000..7d8270ce5 --- /dev/null +++ b/gcloud/beta/deploy/custom-target-types/set-iam-policy @@ -0,0 +1,87 @@ +NAME + gcloud beta deploy custom-target-types set-iam-policy - set the IAM policy + for a Cloud Deploy Custom Target Type + +SYNOPSIS + gcloud beta deploy custom-target-types set-iam-policy + (CUSTOM_TARGET_TYPE : --region=REGION) POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Set the IAM policy associated with a Cloud Deploy Custom Target + Type. + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +EXAMPLES + The following command will read an IAM policy defined in a JSON file + policy.json and set it for a custom target type with identifier + my-custom-target-type in region us-central1: + + $ gcloud beta deploy custom-target-types set-iam-policy \ + my-custom-target-type policy.json --region=us-central1 + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +POSITIONAL ARGUMENTS + Custom target type resource - The custom target type for which to set the + IAM policy. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +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 clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy custom-target-types set-iam-policy + + $ gcloud alpha deploy custom-target-types set-iam-policy + diff --git a/gcloud/beta/sql/export/sql b/gcloud/beta/sql/export/sql index 73ef69f9b..173fec189 100644 --- a/gcloud/beta/sql/export/sql +++ b/gcloud/beta/sql/export/sql @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta sql export sql INSTANCE URI [--async] [--database=DATABASE,[DATABASE,...], -d DATABASE,[DATABASE,...]] - [--offload] [--table=TABLE,[TABLE,...], -t TABLE,[TABLE,...]] + [--offload] [--parallel] + [--table=TABLE,[TABLE,...], -t TABLE,[TABLE,...]] [--threads=THREADS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -42,11 +43,20 @@ FLAGS source instances and allows other operations to be performed while the export is in progress. + --parallel + Perform a parallel export. This flag is only applicable to MySQL and + Postgres. + --table=TABLE,[TABLE,...], -t TABLE,[TABLE,...] Tables to export from the specified database. If you specify tables, specify one and only one database. For PostgreSQL instances, only one table can be exported at a time. + --threads=THREADS + Specifies the number of threads to use for the parallel export. If + --parallel is specified and this flag is not provided, Cloud SQL uses a + default thread count to optimize performance. + 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/sql/import/sql b/gcloud/beta/sql/import/sql index bf1d8d327..1c32d8c2e 100644 --- a/gcloud/beta/sql/import/sql +++ b/gcloud/beta/sql/import/sql @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta sql import sql INSTANCE URI [--async] - [--database=DATABASE, -d DATABASE] [--user=USER] [GCLOUD_WIDE_FLAG ...] + [--database=DATABASE, -d DATABASE] [--parallel] [--threads=THREADS] + [--user=USER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta sql import sql imports data into a Cloud SQL instance @@ -45,6 +46,15 @@ FLAGS specified in the file to be imported. If your SQL dump file includes a database statement, it will override the database set in this flag. + --parallel + Perform a parallel import. This flag is only applicable to MySQL and + Postgres. + + --threads=THREADS + Specifies the number of threads to use for the parallel import. If + --parallel is specified and this flag is not provided, Cloud SQL uses a + default thread count to optimize performance. + --user=USER PostgreSQL user for this import operation. diff --git a/gcloud/compute/commitments/create b/gcloud/compute/commitments/create index 5a5f42986..99a932dce 100644 --- a/gcloud/compute/commitments/create +++ b/gcloud/compute/commitments/create @@ -8,7 +8,8 @@ SYNOPSIS [--merge-source-commitments=MERGE_SOURCE_COMMITMENTS] [--region=REGION] [--split-source-commitment=SPLIT_SOURCE_COMMITMENT] [--type=TYPE; default="general-purpose"] - [--reservations-from-file=RESERVATIONS_FROM_FILE + [--existing-reservation=[name=NAME],[zone=ZONE] + | --reservations-from-file=RESERVATIONS_FROM_FILE | [--reservation=RESERVATION : --reservation-zone=RESERVATION_ZONE --accelerator=[count=COUNT],[type=TYPE] --local-ssd=[interface=INTERFACE],[size=SIZE] @@ -106,6 +107,20 @@ OPTIONAL FLAGS At most one of these can be specified: + --existing-reservation=[name=NAME],[zone=ZONE] + Details of the existing on-demand reservation or auto-created future + reservation that you want to attach to your commitment. Specify a new + instance of this flag for every existing reservation that you want to + attach. The reservations must be in the same region as the + commitment. + name + The name of the reservation. + zone + The zone of the reservation. For example, to attach an existing + reservation named reservation-name in the zone reservation-zone, + use the following text: + --existing-reservation=name=reservation-name,zone=reservation-zone + --reservations-from-file=RESERVATIONS_FROM_FILE Path to a YAML file of multiple reservations' configuration. diff --git a/gcloud/compute/instances/help b/gcloud/compute/instances/help index 4f6ea7cfd..e8ad877b9 100644 --- a/gcloud/compute/instances/help +++ b/gcloud/compute/instances/help @@ -30,6 +30,9 @@ GROUPS network-interfaces Read and manipulate Compute Engine VM instance network interfaces. + ops-agents + Manage Operation Suite (Ops) agents for Compute Engine VM instances. + os-inventory Read Compute Engine OS Inventory Data and Related Resources. diff --git a/gcloud/compute/instances/ops-agents/help b/gcloud/compute/instances/ops-agents/help new file mode 100644 index 000000000..cba430dd9 --- /dev/null +++ b/gcloud/compute/instances/ops-agents/help @@ -0,0 +1,29 @@ +NAME + gcloud compute instances ops-agents - manage Operation Suite (Ops) agents + for Compute Engine VM instances + +SYNOPSIS + gcloud compute instances ops-agents GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Operation Suite (Ops) agents for Compute Engine VM instances. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + policies + Manage Operation Suite (Ops) agents policies that install, update, and + uninstall agents for Compute Engine VM instances. + +NOTES + These variants are also available: + + $ gcloud alpha compute instances ops-agents + + $ gcloud beta compute instances ops-agents + diff --git a/gcloud/compute/instances/ops-agents/policies/help b/gcloud/compute/instances/ops-agents/policies/help new file mode 100644 index 000000000..df624f27b --- /dev/null +++ b/gcloud/compute/instances/ops-agents/policies/help @@ -0,0 +1,24 @@ +NAME + gcloud compute instances ops-agents policies - manage Operation Suite (Ops) + agents policies that install, update, and uninstall agents for Compute + Engine VM instances + +SYNOPSIS + gcloud compute instances ops-agents policies COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Operation Suite (Ops) agents policies that install, update, and + uninstall agents for Compute Engine VM instances. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instances ops-agents policies + + $ gcloud beta compute instances ops-agents policies + diff --git a/gcloud/compute/security-policies/add-layer7-ddos-defense-threshold-config b/gcloud/compute/security-policies/add-layer7-ddos-defense-threshold-config index 63031a13e..5ddd117f0 100644 --- a/gcloud/compute/security-policies/add-layer7-ddos-defense-threshold-config +++ b/gcloud/compute/security-policies/add-layer7-ddos-defense-threshold-config @@ -17,7 +17,7 @@ DESCRIPTION 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: + To add a layer7 ddos defense threshold config, run the following command: $ gcloud compute security-policies \ add-layer7-ddos-defense-threshold-config NAME \ @@ -37,7 +37,7 @@ REQUIRED FLAGS OPTIONAL FLAGS --auto-deploy-confidence-threshold=AUTO_DEPLOY_CONFIDENCE_THRESHOLD - The threshold of the confidence of an identified attack over which + The threshold of the confidence of an identified attack, over which auto-deploy takes action. --auto-deploy-expiration-sec=AUTO_DEPLOY_EXPIRATION_SEC @@ -48,7 +48,7 @@ OPTIONAL FLAGS 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. + 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, diff --git a/gcloud/container/attached/clusters/register b/gcloud/container/attached/clusters/register index 5f0b094a4..368f27565 100644 --- a/gcloud/container/attached/clusters/register +++ b/gcloud/container/attached/clusters/register @@ -153,7 +153,15 @@ OPTIONAL FLAGS Description for the cluster. --enable-managed-prometheus - Enable managed collection for Managed Service for Prometheus. + Enables managed collection for Managed Service for Prometheus in the + cluster. + + See + https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-managed#enable-mgdcoll-gke + for more info. + + Enabled by default for cluster versions 1.27 or greater, use + --no-enable-managed-prometheus to disable. --logging=COMPONENT,[COMPONENT,...] Set the components that have logging enabled. diff --git a/gcloud/container/aws/clusters/create b/gcloud/container/aws/clusters/create index 387431485..fd64b5261 100644 --- a/gcloud/container/aws/clusters/create +++ b/gcloud/container/aws/clusters/create @@ -150,7 +150,15 @@ OPTIONAL FLAGS ports TCP/443 and TCP/8132 must be provided. --enable-managed-prometheus - Enable managed collection for Managed Service for Prometheus. + Enables managed collection for Managed Service for Prometheus in the + cluster. + + See + https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-managed#enable-mgdcoll-gke + for more info. + + Enabled by default for cluster versions 1.27 or greater, use + --no-enable-managed-prometheus to disable. --instance-type=INSTANCE_TYPE AWS EC2 instance type for the control plane's nodes. diff --git a/gcloud/container/azure/clusters/create b/gcloud/container/azure/clusters/create index cb138f115..10845cf7e 100644 --- a/gcloud/container/azure/clusters/create +++ b/gcloud/container/azure/clusters/create @@ -173,7 +173,15 @@ OPTIONAL FLAGS Description for the cluster. --enable-managed-prometheus - Enable managed collection for Managed Service for Prometheus. + Enables managed collection for Managed Service for Prometheus in the + cluster. + + See + https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-managed#enable-mgdcoll-gke + for more info. + + Enabled by default for cluster versions 1.27 or greater, use + --no-enable-managed-prometheus to disable. --endpoint-subnet-id=ENDPOINT_SUBNET_ID ARM ID of the subnet where the control plane load balancer is deployed. diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 34a540eea..a3ae5a1cb 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -536,7 +536,15 @@ FLAGS --no-enable-legacy-authorization. --enable-managed-prometheus - Enable managed collection for Managed Service for Prometheus. + Enables managed collection for Managed Service for Prometheus in the + cluster. + + See + https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-managed#enable-mgdcoll-gke + for more info. + + Enabled by default for cluster versions 1.27 or greater, use + --no-enable-managed-prometheus to disable. --enable-master-global-access Use with private clusters to allow access to the master's private diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 1303309ad..235e2d562 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -1178,7 +1178,15 @@ REQUIRED FLAGS Disable managed collection for Managed Service for Prometheus. --enable-managed-prometheus - Enable managed collection for Managed Service for Prometheus. + Enables managed collection for Managed Service for Prometheus in + the cluster. + + See + https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-managed#enable-mgdcoll-gke + for more info. + + Enabled by default for cluster versions 1.27 or greater, use + --no-enable-managed-prometheus to disable. --logging-service=LOGGING_SERVICE (DEPRECATED) Logging service to use for the cluster. Options are: diff --git a/gcloud/container/fleet/help b/gcloud/container/fleet/help index c40737f94..5d8320c60 100644 --- a/gcloud/container/fleet/help +++ b/gcloud/container/fleet/help @@ -76,6 +76,9 @@ GROUPS multi-cluster-services Manage Multi-cluster Services Feature. + operations + Manage Anthos fleet long-running operations. + policycontroller Manage Policy Controller Feature. diff --git a/gcloud/container/fleet/operations/describe b/gcloud/container/fleet/operations/describe new file mode 100644 index 000000000..50f5a8fac --- /dev/null +++ b/gcloud/container/fleet/operations/describe @@ -0,0 +1,64 @@ +NAME + gcloud container fleet operations describe - describe a long-running + operation + +SYNOPSIS + gcloud container fleet operations describe + (OPERATION : --location=LOCATION; default="global") + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a long-running operation. + +EXAMPLES + To describe a long-running operation in location us-west1, run: + + $ gcloud container fleet operations describe OPERATION \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Operation resource - operation 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the name attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION; default="global" + Google Cloud location for the operation. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet operations describe + + $ gcloud beta container fleet operations describe + diff --git a/gcloud/container/fleet/operations/help b/gcloud/container/fleet/operations/help new file mode 100644 index 000000000..bf39b207b --- /dev/null +++ b/gcloud/container/fleet/operations/help @@ -0,0 +1,34 @@ +NAME + gcloud container fleet operations - manage Anthos fleet long-running + operations + +SYNOPSIS + gcloud container fleet operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Anthos fleet long-running operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe a long-running operation. + + list + List long-running operations. + + wait + Poll a long-running operation for completion. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet operations + + $ gcloud beta container fleet operations + diff --git a/gcloud/container/fleet/operations/list b/gcloud/container/fleet/operations/list new file mode 100644 index 000000000..380bba649 --- /dev/null +++ b/gcloud/container/fleet/operations/list @@ -0,0 +1,67 @@ +NAME + gcloud container fleet operations list - list long-running operations + +SYNOPSIS + gcloud container fleet operations list [--location=LOCATION; default="-"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List long-running operations. + +EXAMPLES + To list all operations in location us-west1, run: + + $ gcloud container fleet operations list --location=us-west1 + +FLAGS + --location=LOCATION; default="-" + The location name. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet operations list + + $ gcloud beta container fleet operations list + diff --git a/gcloud/container/fleet/operations/wait b/gcloud/container/fleet/operations/wait new file mode 100644 index 000000000..9c8043d7b --- /dev/null +++ b/gcloud/container/fleet/operations/wait @@ -0,0 +1,63 @@ +NAME + gcloud container fleet operations wait - poll a long-running operation for + completion + +SYNOPSIS + gcloud container fleet operations wait + (OPERATION : --location=LOCATION; default="global") + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Poll a long-running operation for completion. + +EXAMPLES + To wait for an operation in location us-west1 to complete, run: + + $ gcloud container fleet operations wait OPERATION \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Operation resource - operation to wait. 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the name attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION; default="global" + Google Cloud location for the operation. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet operations wait + + $ gcloud beta container fleet operations wait + diff --git a/gcloud/container/hub/help b/gcloud/container/hub/help index fbfed349e..c78efff6e 100644 --- a/gcloud/container/hub/help +++ b/gcloud/container/hub/help @@ -76,6 +76,9 @@ GROUPS multi-cluster-services Manage Multi-cluster Services Feature. + operations + Manage Anthos fleet long-running operations. + policycontroller Manage Policy Controller Feature. diff --git a/gcloud/container/hub/operations/describe b/gcloud/container/hub/operations/describe new file mode 100644 index 000000000..734b1d56a --- /dev/null +++ b/gcloud/container/hub/operations/describe @@ -0,0 +1,64 @@ +NAME + gcloud container hub operations describe - describe a long-running + operation + +SYNOPSIS + gcloud container hub operations describe + (OPERATION : --location=LOCATION; default="global") + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a long-running operation. + +EXAMPLES + To describe a long-running operation in location us-west1, run: + + $ gcloud container hub operations describe OPERATION \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Operation resource - operation 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the name attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION; default="global" + Google Cloud location for the operation. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container hub operations describe + + $ gcloud beta container hub operations describe + diff --git a/gcloud/container/hub/operations/help b/gcloud/container/hub/operations/help new file mode 100644 index 000000000..b40ae60f3 --- /dev/null +++ b/gcloud/container/hub/operations/help @@ -0,0 +1,34 @@ +NAME + gcloud container hub operations - manage Anthos fleet long-running + operations + +SYNOPSIS + gcloud container hub operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Anthos fleet long-running operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe a long-running operation. + + list + List long-running operations. + + wait + Poll a long-running operation for completion. + +NOTES + These variants are also available: + + $ gcloud alpha container hub operations + + $ gcloud beta container hub operations + diff --git a/gcloud/container/hub/operations/list b/gcloud/container/hub/operations/list new file mode 100644 index 000000000..82f59a8d3 --- /dev/null +++ b/gcloud/container/hub/operations/list @@ -0,0 +1,67 @@ +NAME + gcloud container hub operations list - list long-running operations + +SYNOPSIS + gcloud container hub operations list [--location=LOCATION; default="-"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List long-running operations. + +EXAMPLES + To list all operations in location us-west1, run: + + $ gcloud container hub operations list --location=us-west1 + +FLAGS + --location=LOCATION; default="-" + The location name. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container hub operations list + + $ gcloud beta container hub operations list + diff --git a/gcloud/container/hub/operations/wait b/gcloud/container/hub/operations/wait new file mode 100644 index 000000000..561230434 --- /dev/null +++ b/gcloud/container/hub/operations/wait @@ -0,0 +1,62 @@ +NAME + gcloud container hub operations wait - poll a long-running operation for + completion + +SYNOPSIS + gcloud container hub operations wait + (OPERATION : --location=LOCATION; default="global") + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Poll a long-running operation for completion. + +EXAMPLES + To wait for an operation in location us-west1 to complete, run: + + $ gcloud container hub operations wait OPERATION --location=us-west1 + +POSITIONAL ARGUMENTS + Operation resource - operation to wait. 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the name attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION; default="global" + Google Cloud location for the operation. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container hub operations wait + + $ gcloud beta container hub operations wait + diff --git a/gcloud/deploy/custom-target-types/add-iam-policy-binding b/gcloud/deploy/custom-target-types/add-iam-policy-binding new file mode 100644 index 000000000..89fd8be50 --- /dev/null +++ b/gcloud/deploy/custom-target-types/add-iam-policy-binding @@ -0,0 +1,138 @@ +NAME + gcloud deploy custom-target-types add-iam-policy-binding - add IAM policy + binding for a Cloud Deploy Custom Target Type + +SYNOPSIS + gcloud deploy custom-target-types add-iam-policy-binding + (CUSTOM_TARGET_TYPE : --region=REGION) --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Adds a policy binding to the IAM policy of a Cloud Deploy Custom Target + Type. One binding consists of a member and a role. + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +EXAMPLES + To add an IAM policy binding for the role of + roles/clouddeploy.customTargetTypeAdmin for the user test-user@gmail.com on + my-custom-target-type with the region us-central1, run: + + $ gcloud deploy custom-target-types add-iam-policy-binding \ + my-custom-target-type --region='us-central1' \ + --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.customTargetTypeAdmin' + +POSITIONAL ARGUMENTS + Custom target type resource - The custom target type for which to add the + IAM policy binding. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +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 clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + These variants are also available: + + $ gcloud alpha deploy custom-target-types add-iam-policy-binding + + $ gcloud beta deploy custom-target-types add-iam-policy-binding + diff --git a/gcloud/deploy/custom-target-types/get-iam-policy b/gcloud/deploy/custom-target-types/get-iam-policy new file mode 100644 index 000000000..d65afb2b1 --- /dev/null +++ b/gcloud/deploy/custom-target-types/get-iam-policy @@ -0,0 +1,103 @@ +NAME + gcloud deploy custom-target-types get-iam-policy - get the IAM policy for a + Cloud Deploy Custom Target Type + +SYNOPSIS + gcloud deploy custom-target-types get-iam-policy + (CUSTOM_TARGET_TYPE : --region=REGION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud deploy custom-target-types get-iam-policy displays the IAM policy + associated with a Cloud Deploy Custom Target Type. If formatted as JSON, + the output can be edited and used as a policy file for set-iam-policy. The + output includes an "etag" field identifying the version emitted and + allowing detection of concurrent policy updates; see $ gcloud deploy + custom-target-types set-iam-policy for additional details. + +EXAMPLES + To print the IAM policy for a custom target type my-custom-target-type in + region us-central1, run: + + $ gcloud deploy custom-target-types get-iam-policy \ + my-custom-target-type --region=us-central1 + +POSITIONAL ARGUMENTS + Custom target type resource - The custom target type for which to display + the IAM policy. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + These variants are also available: + + $ gcloud alpha deploy custom-target-types get-iam-policy + + $ gcloud beta deploy custom-target-types get-iam-policy + diff --git a/gcloud/deploy/custom-target-types/help b/gcloud/deploy/custom-target-types/help index ecb03c1f4..304f64c46 100644 --- a/gcloud/deploy/custom-target-types/help +++ b/gcloud/deploy/custom-target-types/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add-iam-policy-binding + Add IAM policy binding for a Cloud Deploy Custom Target Type. + delete Delete a custom target type. @@ -25,9 +28,18 @@ COMMANDS export Returns the .yaml definition of the specified custom target type. + get-iam-policy + Get the IAM policy for a Cloud Deploy Custom Target Type. + list List the custom target types. + remove-iam-policy-binding + Remove an IAM policy binding for a Cloud Deploy Custom Target Type. + + set-iam-policy + Set the IAM policy for a Cloud Deploy Custom Target Type. + NOTES These variants are also available: diff --git a/gcloud/deploy/custom-target-types/remove-iam-policy-binding b/gcloud/deploy/custom-target-types/remove-iam-policy-binding new file mode 100644 index 000000000..991fbd10b --- /dev/null +++ b/gcloud/deploy/custom-target-types/remove-iam-policy-binding @@ -0,0 +1,143 @@ +NAME + gcloud deploy custom-target-types remove-iam-policy-binding - remove an IAM + policy binding for a Cloud Deploy Custom Target Type + +SYNOPSIS + gcloud deploy custom-target-types remove-iam-policy-binding + (CUSTOM_TARGET_TYPE : --region=REGION) --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Removes a policy binding to the IAM policy of a Cloud Deploy Custom Target + Type. One binding consists of a member and a role. + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +EXAMPLES + To remove an IAM policy binding for the role of + roles/clouddeploy.customTargetTypeAdmin for the user test-user@gmail.com on + my-custom-target-type with the region us-central1, run: + + $ gcloud deploy custom-target-types remove-iam-policy-binding \ + my-custom-target-type --region='us-central1' \ + --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.customTargetTypeAdmin' + +POSITIONAL ARGUMENTS + Custom target type resource - The custom target type for which to remove + the IAM policy binding. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +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 clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + These variants are also available: + + $ gcloud alpha deploy custom-target-types remove-iam-policy-binding + + $ gcloud beta deploy custom-target-types remove-iam-policy-binding + diff --git a/gcloud/deploy/custom-target-types/set-iam-policy b/gcloud/deploy/custom-target-types/set-iam-policy new file mode 100644 index 000000000..28d0f5269 --- /dev/null +++ b/gcloud/deploy/custom-target-types/set-iam-policy @@ -0,0 +1,85 @@ +NAME + gcloud deploy custom-target-types set-iam-policy - set the IAM policy for a + Cloud Deploy Custom Target Type + +SYNOPSIS + gcloud deploy custom-target-types set-iam-policy + (CUSTOM_TARGET_TYPE : --region=REGION) POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Set the IAM policy associated with a Cloud Deploy Custom Target Type. + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +EXAMPLES + The following command will read an IAM policy defined in a JSON file + policy.json and set it for a custom target type with identifier + my-custom-target-type in region us-central1: + + $ gcloud deploy custom-target-types set-iam-policy \ + my-custom-target-type policy.json --region=us-central1 + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +POSITIONAL ARGUMENTS + Custom target type resource - The custom target type for which to set the + IAM policy. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +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 clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + These variants are also available: + + $ gcloud alpha deploy custom-target-types set-iam-policy + + $ gcloud beta deploy custom-target-types set-iam-policy + diff --git a/gcloud/run/deploy b/gcloud/run/deploy index 008c06a6e..9bdbc985f 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -2,31 +2,33 @@ NAME gcloud run deploy - create or update a Cloud Run service SYNOPSIS - gcloud run deploy [[SERVICE] --namespace=NAMESPACE] [--args=[ARG,...]] - [--async] [--command=[COMMAND,...]] [--concurrency=CONCURRENCY] - [--cpu=CPU] [--ingress=INGRESS; default="all"] - [--max-instances=MAX_INSTANCES] [--memory=MEMORY] + gcloud run deploy [[SERVICE] --namespace=NAMESPACE] [--async] + [--concurrency=CONCURRENCY] [--container=CONTAINER] + [--ingress=INGRESS; default="all"] [--max-instances=MAX_INSTANCES] [--min-instances=MIN_INSTANCES] - [--platform=PLATFORM; default="managed"] [--port=PORT] + [--platform=PLATFORM; default="managed"] [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] - [--no-traffic] [--[no-]use-http2] - [--clear-env-vars | --env-vars-file=FILE_PATH - | --set-env-vars=[KEY=VALUE,...] - | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...]] + [--no-traffic] + [--args=[ARG,...] --command=[COMMAND,...] --cpu=CPU + --depends-on=[CONTAINER,...] + --memory=MEMORY --port=PORT --[no-]use-http2 --clear-env-vars + | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] + | --remove-env-vars=[KEY,...] + --update-env-vars=[KEY=VALUE,...] --clear-secrets + | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] + --update-secrets=[KEY=VALUE,...] --image=IMAGE | --source=SOURCE] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] - [--clear-secrets | --set-secrets=[KEY=VALUE,...] - | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--connectivity=CONNECTIVITY --clear-config-maps | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] --update-config-maps=[KEY=VALUE,...]] - [--image=IMAGE | --source=SOURCE] [--[no-]allow-unauthenticated --breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT - --revision-suffix=REVISION_SUFFIX --[no-]session-affinity - --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS + --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX + --[no-]session-affinity --vpc-connector=VPC_CONNECTOR + --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -91,35 +93,18 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --args=[ARG,...] - Comma-separated arguments passed to the command run by the container - image. If not specified and no '--command' is provided, the container - image's default Cmd is used. Otherwise, if not specified, no arguments - are passed. To reset this field to its default, pass an empty string. - --async Return immediately, without waiting for the operation in progress to complete. - --command=[COMMAND,...] - Entrypoint for the container image. If not specified, the container - image's default Entrypoint is run. To reset this field to its default, - pass an empty string. - --concurrency=CONCURRENCY Set the maximum number of concurrent requests allowed per container instance. Leave concurrency unspecified or provide the special value 'default' to receive the server default value. - --cpu=CPU - Set a CPU limit in Kubernetes cpu units. - - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters support - fractional values. Examples .5, 500m, 2 + --container=CONTAINER + Specifies a container by name. Flags following --container will apply + to the specified container. --ingress=INGRESS; default="all" Set the ingress traffic sources allowed to call the service. For Cloud @@ -149,9 +134,6 @@ FLAGS The maximum number of container instances of the Service to run. Use 'default' to unset the limit and use the platform default. - --memory=MEMORY - Set a memory limit. Ex: 1024Mi, 4Gi. - --min-instances=MIN_INSTANCES The minimum number of container instances for this Revision of the Service to run or 'default' to remove any minimum. @@ -173,13 +155,6 @@ FLAGS --kubeconfig and --context flags to specify a kubeconfig file and the context for connecting. - --port=PORT - Container port to receive requests at. Also sets the $PORT environment - variable. Must be a number between 1 and 65535, inclusive. To unset - this field, pass the special value "default". If updating an existing - service with a TCP startup probe pointing to the previous container - port, this will also update the probe port. - --service-account=SERVICE_ACCOUNT Service account associated with the revision of the service. The service account represents the identity of the running revision, and @@ -210,35 +185,126 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. - --[no-]use-http2 - Whether to use HTTP/2 for connections to the service. Use --use-http2 - to enable and --no-use-http2 to disable. + Container Flags - At most one of these can be specified: + The following flags apply to a single container. If the --container flag is specified these flags may only be + specified after a --container flag. Otherwise they will apply to the primary ingress container. - --clear-env-vars - Remove all environment variables. + --args=[ARG,...] + Comma-separated arguments passed to the command run by the + container image. If not specified and no '--command' is provided, + the container image's default Cmd is used. Otherwise, if not + specified, no arguments are passed. To reset this field to its + default, pass an empty string. - --env-vars-file=FILE_PATH - Path to a local YAML file with definitions for all environment - variables. All existing environment variables will be removed before - the new environment variables are added. Example YAML content: + --command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default Entrypoint is run. To reset this field to its + default, pass an empty string. - KEY_1: "value1" - KEY_2: "value 2" + --cpu=CPU + Set a CPU limit in Kubernetes cpu units. - --set-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. All existing - environment variables will be removed first. + Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run + (fully managed), 4 cpus also requires a minimum 2Gi --memory value. + Examples 2, 2.0, 2000m - Only --update-env-vars and --remove-env-vars can be used together. If - both are specified, --remove-env-vars will be applied first. + Cloud Run for Anthos and Knative-compatible Kubernetes clusters + support fractional values. Examples .5, 500m, 2 - --remove-env-vars=[KEY,...] - List of environment variables to be removed. + --depends-on=[CONTAINER,...] + List of container dependencies to add to the current container. - --update-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. + + --port=PORT + Container port to receive requests at. Also sets the $PORT + environment variable. Must be a number between 1 and 65535, + inclusive. To unset this field, pass the special value "default". + If updating an existing service with a TCP startup probe pointing + to the previous container port, this will also update the probe + port. + + --[no-]use-http2 + Whether to use HTTP/2 for connections to the service. Use + --use-http2 to enable and --no-use-http2 to disable. + + At most one of these can be specified: + + --clear-env-vars + Remove all environment variables. + + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed + before the new environment variables are added. Example YAML + content: + + KEY_1: "value1" + KEY_2: "value 2" + + --set-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. All + existing environment variables will be removed first. + + Only --update-env-vars and --remove-env-vars can be used together. + If both are specified, --remove-env-vars will be applied first. + + --remove-env-vars=[KEY,...] + List of environment variables to be removed. + + --update-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + Specify secrets to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. Values should be in the form + SECRET_NAME:SECRET_VERSION. For example: + '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' + will mount a volume at '/secrets/api' containing a file 'key' with the + latest version of secret 'mysecret'. An environment variable named ENV + will also be created whose value is version 1 of secret 'othersecret'. + + At most one of these can be specified: + + --clear-secrets + Remove all secrets. + + --set-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. All existing secrets + will be removed first. + + Only --update-secrets and --remove-secrets can be used together. If + both are specified, --remove-secrets will be applied first. + + --remove-secrets=[KEY,...] + List of secrets to be removed. + + --update-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. + + At most one of these can be specified: + + --image=IMAGE + Name of the container image to deploy (e.g. + gcr.io/cloudrun/hello:latest). + + --source=SOURCE + The location of the source to build. If a Dockerfile is present + in the source code directory, it will be built using that + Dockerfile, otherwise it will use Google Cloud buildpacks. See + https://cloud.google.com/run/docs/deploying-source-code for more + details. The location can be a directory on a local disk or a + gzipped archive file (.tar.gz) in Google Cloud Storage. If the + source is a local directory, this command skips the files + specified in the --ignore-file. If --ignore-file is not + specified, use .gcloudignore file. If a .gcloudignore file is + absent and a .gitignore file is present in the local source + directory, gcloud will use a generated Git-compatible + .gcloudignore file that respects your .gitignored files. The + global .gitignore is not respected. For more information on + .gcloudignore, see gcloud topic gcloudignore. At most one of these can be specified: @@ -270,33 +336,6 @@ FLAGS List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. - Specify secrets to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. Values should be in the form - SECRET_NAME:SECRET_VERSION. For example: - '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' will - mount a volume at '/secrets/api' containing a file 'key' with the latest - version of secret 'mysecret'. An environment variable named ENV will also - be created whose value is version 1 of secret 'othersecret'. - - At most one of these can be specified: - - --clear-secrets - Remove all secrets. - - --set-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. All existing secrets will - be removed first. - - Only --update-secrets and --remove-secrets can be used together. If both - are specified, --remove-secrets will be applied first. - - --remove-secrets=[KEY,...] - List of secrets to be removed. - - --update-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. - Only applicable if connecting to Cloud Run for Anthos deployed on Google Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke or --platform=kubernetes to use: @@ -347,27 +386,6 @@ FLAGS --update-config-maps=[KEY=VALUE,...] List of key-value pairs to set as config-maps. - At most one of these can be specified: - - --image=IMAGE - Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). - - --source=SOURCE - The location of the source to build. If a Dockerfile is present in - the source code directory, it will be built using that Dockerfile, - otherwise it will use Google Cloud buildpacks. See - https://cloud.google.com/run/docs/deploying-source-code for more - details. The location can be a directory on a local disk or a gzipped - archive file (.tar.gz) in Google Cloud Storage. If the source is a - local directory, this command skips the files specified in the - --ignore-file. If --ignore-file is not specified, use .gcloudignore - file. If a .gcloudignore file is absent and a .gitignore file is - present in the local source directory, gcloud will use a generated - Git-compatible .gcloudignore file that respects your .gitignored - files. The global .gitignore is not respected. For more information - on .gcloudignore, see gcloud topic gcloudignore. - Only applicable if connecting to Cloud Run (fully managed). Specify --platform=managed to use: @@ -410,6 +428,9 @@ FLAGS gen2 Run the application in a second generation execution environment. + --remove-containers=[CONTAINER,...] + List of containers to remove. + --revision-suffix=REVISION_SUFFIX Specify the suffix of the revision name. Revision names always start with the service name automatically. For example, specifying @@ -546,35 +567,36 @@ FLAGS but can be set in other ways. To set the project attribute: - ▫ provide the argument --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. + ▸ provide the argument --cluster on the command line with a fully + specified name; + ▸ set the property run/cluster with a fully specified name; + ▸ specify the cluster from a list of available clusters with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the + cluster. - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. + To set the cluster attribute: + ▫ provide the argument --cluster on the command line; + ▫ set the property run/cluster; + ▫ specify the cluster from a list of available clusters. - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. + To set the location attribute: + ▫ provide the argument --cluster on the command line with a + fully specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --cluster-location on the command line; + ▫ set the property run/cluster_location; + ▫ specify the cluster location from a list of available zones. Only applicable if connecting to Cloud Run for Anthos deployed on VMware. Specify --platform=kubernetes to use: diff --git a/gcloud/run/services/update b/gcloud/run/services/update index cc42289e5..21eddba54 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -3,18 +3,26 @@ NAME other configuration settings SYNOPSIS - gcloud run services update [[SERVICE] --namespace=NAMESPACE] - [--args=[ARG,...]] [--async] [--command=[COMMAND,...]] - [--concurrency=CONCURRENCY] [--cpu=CPU] [--image=IMAGE] + gcloud run services update [[SERVICE] --namespace=NAMESPACE] [--async] + [--concurrency=CONCURRENCY] [--container=CONTAINER] [--ingress=INGRESS; default="all"] [--max-instances=MAX_INSTANCES] - [--memory=MEMORY] [--min-instances=MIN_INSTANCES] - [--platform=PLATFORM; default="managed"] [--port=PORT] + [--min-instances=MIN_INSTANCES] + [--platform=PLATFORM; default="managed"] [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] - [--no-traffic] [--[no-]use-http2] + [--no-traffic] + [--args=[ARG,...] --command=[COMMAND,...] --cpu=CPU + --depends-on=[CONTAINER,...] --image=IMAGE + --memory=MEMORY --port=PORT --[no-]use-http2 --clear-env-vars + | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] + | --remove-env-vars=[KEY,...] + --update-env-vars=[KEY=VALUE,...] --clear-secrets + | --set-secrets=[KEY=VALUE,...] + | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling --execution-environment=EXECUTION_ENVIRONMENT - --revision-suffix=REVISION_SUFFIX --[no-]session-affinity - --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS + --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX + --[no-]session-affinity --vpc-connector=VPC_CONNECTOR + --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -28,13 +36,8 @@ SYNOPSIS | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS --clear-key | --key=KEY --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,...] - | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] - [--clear-secrets | --set-secrets=[KEY=VALUE,...] - | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--connectivity=CONNECTIVITY --clear-config-maps | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] --update-config-maps=[KEY=VALUE,...]] @@ -79,39 +82,18 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --args=[ARG,...] - Comma-separated arguments passed to the command run by the container - image. If not specified and no '--command' is provided, the container - image's default Cmd is used. Otherwise, if not specified, no arguments - are passed. To reset this field to its default, pass an empty string. - --async Return immediately, without waiting for the operation in progress to complete. - --command=[COMMAND,...] - Entrypoint for the container image. If not specified, the container - image's default Entrypoint is run. To reset this field to its default, - pass an empty string. - --concurrency=CONCURRENCY Set the maximum number of concurrent requests allowed per container instance. Leave concurrency unspecified or provide the special value 'default' to receive the server default value. - --cpu=CPU - Set a CPU limit in Kubernetes cpu units. - - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters support - fractional values. Examples .5, 500m, 2 - - --image=IMAGE - Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + --container=CONTAINER + Specifies a container by name. Flags following --container will apply + to the specified container. --ingress=INGRESS; default="all" Set the ingress traffic sources allowed to call the service. For Cloud @@ -141,9 +123,6 @@ FLAGS The maximum number of container instances of the Service to run. Use 'default' to unset the limit and use the platform default. - --memory=MEMORY - Set a memory limit. Ex: 1024Mi, 4Gi. - --min-instances=MIN_INSTANCES The minimum number of container instances for this Revision of the Service to run or 'default' to remove any minimum. @@ -165,13 +144,6 @@ FLAGS --kubeconfig and --context flags to specify a kubeconfig file and the context for connecting. - --port=PORT - Container port to receive requests at. Also sets the $PORT environment - variable. Must be a number between 1 and 65535, inclusive. To unset - this field, pass the special value "default". If updating an existing - service with a TCP startup probe pointing to the previous container - port, this will also update the probe port. - --service-account=SERVICE_ACCOUNT Service account associated with the revision of the service. The service account represents the identity of the running revision, and @@ -202,9 +174,106 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. - --[no-]use-http2 - Whether to use HTTP/2 for connections to the service. Use --use-http2 - to enable and --no-use-http2 to disable. + If the --container or --remove-containers flag is specified the following + arguments may only be specified after a --container flag. + + --args=[ARG,...] + Comma-separated arguments passed to the command run by the + container image. If not specified and no '--command' is provided, + the container image's default Cmd is used. Otherwise, if not + specified, no arguments are passed. To reset this field to its + default, pass an empty string. + + --command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default Entrypoint is run. To reset this field to its + default, pass an empty string. + + --cpu=CPU + Set a CPU limit in Kubernetes cpu units. + + Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run + (fully managed), 4 cpus also requires a minimum 2Gi --memory value. + Examples 2, 2.0, 2000m + + Cloud Run for Anthos and Knative-compatible Kubernetes clusters + support fractional values. Examples .5, 500m, 2 + + --depends-on=[CONTAINER,...] + List of container dependencies to add to the current container. + + --image=IMAGE + Name of the container image to deploy (e.g. + gcr.io/cloudrun/hello:latest). + + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. + + --port=PORT + Container port to receive requests at. Also sets the $PORT + environment variable. Must be a number between 1 and 65535, + inclusive. To unset this field, pass the special value "default". + If updating an existing service with a TCP startup probe pointing + to the previous container port, this will also update the probe + port. + + --[no-]use-http2 + Whether to use HTTP/2 for connections to the service. Use + --use-http2 to enable and --no-use-http2 to disable. + + At most one of these can be specified: + + --clear-env-vars + Remove all environment variables. + + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed + before the new environment variables are added. Example YAML + content: + + KEY_1: "value1" + KEY_2: "value 2" + + --set-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. All + existing environment variables will be removed first. + + Only --update-env-vars and --remove-env-vars can be used together. + If both are specified, --remove-env-vars will be applied first. + + --remove-env-vars=[KEY,...] + List of environment variables to be removed. + + --update-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + Specify secrets to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. Values should be in the form + SECRET_NAME:SECRET_VERSION. For example: + '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' + will mount a volume at '/secrets/api' containing a file 'key' with the + latest version of secret 'mysecret'. An environment variable named ENV + will also be created whose value is version 1 of secret 'othersecret'. + + At most one of these can be specified: + + --clear-secrets + Remove all secrets. + + --set-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. All existing secrets + will be removed first. + + Only --update-secrets and --remove-secrets can be used together. If + both are specified, --remove-secrets will be applied first. + + --remove-secrets=[KEY,...] + List of secrets to be removed. + + --update-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. Only applicable if connecting to Cloud Run (fully managed). Specify --platform=managed to use: @@ -239,6 +308,9 @@ FLAGS gen2 Run the application in a second generation execution environment. + --remove-containers=[CONTAINER,...] + List of containers to remove. + --revision-suffix=REVISION_SUFFIX Specify the suffix of the revision name. Revision names always start with the service name automatically. For example, specifying @@ -355,32 +427,6 @@ FLAGS No new instances will be started and the existing instances will be shut down after CMEK key revocation. - At most one of these can be specified: - - --clear-env-vars - Remove all environment variables. - - --env-vars-file=FILE_PATH - Path to a local YAML file with definitions for all environment - variables. All existing environment variables will be removed before - the new environment variables are added. Example YAML content: - - KEY_1: "value1" - KEY_2: "value 2" - - --set-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. All existing - environment variables will be removed first. - - Only --update-env-vars and --remove-env-vars can be used together. If - both are specified, --remove-env-vars will be applied first. - - --remove-env-vars=[KEY,...] - List of environment variables to be removed. - - --update-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. - At most one of these can be specified: --clear-labels @@ -412,33 +458,6 @@ FLAGS List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. - Specify secrets to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. Values should be in the form - SECRET_NAME:SECRET_VERSION. For example: - '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' will - mount a volume at '/secrets/api' containing a file 'key' with the latest - version of secret 'mysecret'. An environment variable named ENV will also - be created whose value is version 1 of secret 'othersecret'. - - At most one of these can be specified: - - --clear-secrets - Remove all secrets. - - --set-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. All existing secrets will - be removed first. - - Only --update-secrets and --remove-secrets can be used together. If both - are specified, --remove-secrets will be applied first. - - --remove-secrets=[KEY,...] - List of secrets to be removed. - - --update-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. - Only applicable if connecting to Cloud Run for Anthos deployed on Google Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke or --platform=kubernetes to use: @@ -509,35 +528,36 @@ FLAGS but can be set in other ways. To set the project attribute: - ▫ provide the argument --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. + ▸ provide the argument --cluster on the command line with a fully + specified name; + ▸ set the property run/cluster with a fully specified name; + ▸ specify the cluster from a list of available clusters with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the + cluster. - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. + To set the cluster attribute: + ▫ provide the argument --cluster on the command line; + ▫ set the property run/cluster; + ▫ specify the cluster from a list of available clusters. - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. + To set the location attribute: + ▫ provide the argument --cluster on the command line with a + fully specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --cluster-location on the command line; + ▫ set the property run/cluster_location; + ▫ specify the cluster location from a list of available zones. Only applicable if connecting to Cloud Run for Anthos deployed on VMware. Specify --platform=kubernetes to use: diff --git a/gcloud/sql/export/sql b/gcloud/sql/export/sql index 3755768d1..0e19aa026 100644 --- a/gcloud/sql/export/sql +++ b/gcloud/sql/export/sql @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud sql export sql INSTANCE URI [--async] [--database=DATABASE,[DATABASE,...], -d DATABASE,[DATABASE,...]] - [--offload] [--table=TABLE,[TABLE,...], -t TABLE,[TABLE,...]] + [--offload] [--parallel] + [--table=TABLE,[TABLE,...], -t TABLE,[TABLE,...]] [--threads=THREADS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -42,11 +43,20 @@ FLAGS source instances and allows other operations to be performed while the export is in progress. + --parallel + Perform a parallel export. This flag is only applicable to MySQL and + Postgres. + --table=TABLE,[TABLE,...], -t TABLE,[TABLE,...] Tables to export from the specified database. If you specify tables, specify one and only one database. For PostgreSQL instances, only one table can be exported at a time. + --threads=THREADS + Specifies the number of threads to use for the parallel export. If + --parallel is specified and this flag is not provided, Cloud SQL uses a + default thread count to optimize performance. + 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/sql/import/sql b/gcloud/sql/import/sql index eac5f3347..ffdb56df1 100644 --- a/gcloud/sql/import/sql +++ b/gcloud/sql/import/sql @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud sql import sql INSTANCE URI [--async] - [--database=DATABASE, -d DATABASE] [--user=USER] [GCLOUD_WIDE_FLAG ...] + [--database=DATABASE, -d DATABASE] [--parallel] [--threads=THREADS] + [--user=USER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud sql import sql imports data into a Cloud SQL instance from a SQL @@ -45,6 +46,15 @@ FLAGS specified in the file to be imported. If your SQL dump file includes a database statement, it will override the database set in this flag. + --parallel + Perform a parallel import. This flag is only applicable to MySQL and + Postgres. + + --threads=THREADS + Specifies the number of threads to use for the parallel import. If + --parallel is specified and this flag is not provided, Cloud SQL uses a + default thread count to optimize performance. + --user=USER PostgreSQL user for this import operation. diff --git a/gcloud/workflows/run b/gcloud/workflows/run index f4df200df..1ec6f7599 100644 --- a/gcloud/workflows/run +++ b/gcloud/workflows/run @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud workflows run (WORKFLOW : --location=LOCATION) [--call-log-level=CALL_LOG_LEVEL; default="none"] [--data=DATA] + [--disable-concurrency-quota-overflow-buffering] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -73,6 +74,11 @@ FLAGS JSON string with data that will be passed to the workflow as an argument. + --disable-concurrency-quota-overflow-buffering + If set, the execution will not be backlogged when the concurrency quota + is exhausted. Backlogged executions start when the concurrency quota + becomes available. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add.