From 5a9f5ff67e9f9aaf01cdc54a3aae84130f02ecc4 Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 8 Jan 2025 10:03:00 +0000 Subject: [PATCH] gcloud: Wed Jan 8 10:03:00 UTC 2025 --- gcloud/_version | 8 +- gcloud/ai/endpoints/deploy-model | 6 +- gcloud/alpha/alloydb/instances/create | 47 ++++ gcloud/alpha/alloydb/instances/update | 51 +++- gcloud/alpha/assured/workloads/create | 4 +- gcloud/alpha/auth/application-default/login | 4 +- gcloud/alpha/auth/login | 4 +- gcloud/alpha/billing/budgets/create | 34 ++- gcloud/alpha/billing/budgets/update | 34 ++- gcloud/alpha/builds/worker-pools/create | 2 +- gcloud/alpha/builds/worker-pools/update | 2 +- .../alpha/compute/future-reservations/create | 14 + .../instance-groups/managed/resume-instances | 4 +- .../instance-groups/managed/start-instances | 4 +- .../instance-groups/managed/stop-instances | 4 +- .../instance-groups/managed/suspend-instances | 4 +- gcloud/alpha/compute/instances/bulk/create | 14 +- .../compute/instances/create-with-container | 13 + .../attachments/dedicated/create | 2 + .../attachments/dedicated/update | 2 + .../interconnects/cross-site-networks/create | 10 +- .../interconnects/cross-site-networks/delete | 30 +++ .../interconnects/cross-site-networks/help | 9 + .../interconnects/cross-site-networks/list | 68 +++++ .../interconnects/cross-site-networks/update | 35 +++ gcloud/alpha/compute/interconnects/help | 3 + .../compute/interconnects/wire-groups/create | 106 ++++++++ .../compute/interconnects/wire-groups/help | 28 ++ .../org-security-policies/associations/create | 22 +- gcloud/alpha/compute/project-info/update | 5 +- gcloud/alpha/compute/queued-resources/create | 14 +- gcloud/alpha/compute/ssh | 4 +- .../container/fleet/policycontroller/enable | 6 +- .../container/hub/policycontroller/enable | 6 +- .../edge-cloud/container/clusters/create | 25 +- .../alpha/firestore/indexes/composite/create | 4 +- gcloud/alpha/iam/list-grantable-roles | 6 +- gcloud/alpha/iam/policies/delete | 7 +- gcloud/alpha/iam/policies/update | 17 +- gcloud/alpha/iap/settings/get | 13 +- gcloud/alpha/iap/settings/set | 12 +- gcloud/alpha/managed-flink/deployments/create | 6 +- gcloud/alpha/managed-flink/jobs/create | 7 +- .../vms/machine-image-imports/create | 9 +- .../intercept-deployment-groups/create | 13 +- .../intercept-deployment-groups/update | 12 +- .../intercept-deployments/create | 16 +- .../intercept-deployments/update | 12 +- .../mirroring-deployment-groups/create | 13 +- .../mirroring-deployment-groups/update | 12 +- .../mirroring-deployments/create | 16 +- .../mirroring-deployments/update | 12 +- .../network-security/security-profiles/export | 79 ++++++ .../network-security/security-profiles/help | 6 + .../network-security/security-profiles/list | 93 +++++++ .../threat-prevention/add-override | 21 +- .../threat-prevention/delete-override | 15 +- .../threat-prevention/list-overrides | 4 +- .../threat-prevention/update-override | 21 +- .../network-services/multicast-domains/create | 4 + .../get-cluster-certificate-authority | 2 +- gcloud/alpha/run/deploy | 43 ++-- gcloud/alpha/workstations/configs/create | 16 +- gcloud/alpha/workstations/configs/update | 15 ++ gcloud/assured/workloads/create | 4 +- gcloud/auth/application-default/login | 4 +- gcloud/auth/login | 4 +- gcloud/beta/assured/workloads/create | 4 +- gcloud/beta/auth/application-default/login | 4 +- gcloud/beta/auth/login | 4 +- gcloud/beta/billing/budgets/create | 34 ++- gcloud/beta/billing/budgets/update | 34 ++- gcloud/beta/builds/worker-pools/create | 2 +- gcloud/beta/builds/worker-pools/update | 2 +- .../instance-groups/managed/resume-instances | 6 +- .../instance-groups/managed/start-instances | 6 +- .../instance-groups/managed/stop-instances | 6 +- .../instance-groups/managed/suspend-instances | 6 +- gcloud/beta/compute/instances/bulk/create | 13 + .../compute/instances/create-with-container | 13 + .../attachments/dedicated/create | 2 + .../attachments/dedicated/update | 2 + .../org-security-policies/associations/create | 22 +- gcloud/beta/compute/project-info/update | 5 +- gcloud/beta/compute/routers/nats/create | 68 +++-- gcloud/beta/compute/routers/nats/update | 71 ++++-- gcloud/beta/compute/ssh | 4 +- .../container/fleet/policycontroller/enable | 6 +- .../container/hub/policycontroller/enable | 6 +- .../beta/firestore/indexes/composite/create | 4 +- gcloud/beta/iam/list-grantable-roles | 6 +- gcloud/beta/iam/policies/delete | 7 +- gcloud/beta/iam/policies/update | 17 +- gcloud/beta/iap/settings/get | 13 +- gcloud/beta/iap/settings/set | 12 +- .../connectivity-tests/create | 7 +- .../connectivity-tests/update | 8 +- .../vpc-flow-logs-configs/create | 5 +- .../vpc-flow-logs-configs/delete | 5 +- .../vpc-flow-logs-configs/describe | 5 +- .../vpc-flow-logs-configs/help | 5 +- .../vpc-flow-logs-configs/list | 5 +- .../vpc-flow-logs-configs/update | 5 +- .../intercept-deployment-groups/create | 13 +- .../intercept-deployment-groups/update | 12 +- .../intercept-deployments/create | 16 +- .../intercept-deployments/update | 12 +- .../mirroring-deployment-groups/create | 8 + .../mirroring-deployment-groups/update | 6 + .../mirroring-deployments/create | 11 + .../mirroring-deployments/update | 6 + .../get-cluster-certificate-authority | 2 +- gcloud/beta/run/deploy | 43 ++-- gcloud/beta/run/services/update | 20 +- gcloud/beta/workbench/help | 20 ++ gcloud/beta/workstations/configs/create | 16 +- gcloud/beta/workstations/configs/update | 15 ++ gcloud/billing/budgets/create | 34 ++- gcloud/billing/budgets/update | 34 ++- gcloud/builds/worker-pools/create | 2 +- gcloud/builds/worker-pools/update | 2 +- gcloud/compute/instance-groups/managed/create | 26 ++ gcloud/compute/instance-groups/managed/help | 12 + .../instance-groups/managed/resume-instances | 75 ++++++ .../instance-groups/managed/start-instances | 75 ++++++ .../instance-groups/managed/stop-instances | 73 ++++++ .../instance-groups/managed/suspend-instances | 79 ++++++ gcloud/compute/instance-groups/managed/update | 26 ++ .../attachments/dedicated/create | 2 + .../attachments/dedicated/update | 2 + gcloud/compute/project-info/update | 2 +- gcloud/compute/ssh | 4 +- .../container/fleet/policycontroller/enable | 6 +- gcloud/container/hub/policycontroller/enable | 6 +- .../connection-profiles/create/alloydb | 6 +- .../connection-profiles/create/cloudsql | 6 +- .../connection-profiles/create/mysql | 6 +- .../connection-profiles/create/oracle | 6 +- .../connection-profiles/create/postgresql | 6 +- .../connection-profiles/create/sqlserver | 6 +- .../connection-profiles/update | 6 +- gcloud/firestore/indexes/composite/create | 4 +- gcloud/iam/list-grantable-roles | 6 +- gcloud/iam/policies/delete | 7 +- gcloud/iam/policies/update | 18 +- gcloud/iap/settings/get | 13 +- gcloud/iap/settings/set | 13 +- .../vms/machine-image-imports/create | 9 +- .../connectivity-tests/create | 7 +- .../connectivity-tests/update | 8 +- gcloud/network-management/help | 3 + .../vpc-flow-logs-configs/create | 195 ++++++++++++++ .../vpc-flow-logs-configs/delete | 74 ++++++ .../vpc-flow-logs-configs/describe | 68 +++++ .../vpc-flow-logs-configs/help | 39 +++ .../vpc-flow-logs-configs/list | 93 +++++++ .../vpc-flow-logs-configs/update | 241 ++++++++++++++++++ .../get-cluster-certificate-authority | 2 +- gcloud/workbench/help | 6 + gcloud/workbench/instances/create | 11 +- gcloud/workbench/instances/update | 3 +- 161 files changed, 2678 insertions(+), 414 deletions(-) create mode 100644 gcloud/alpha/compute/interconnects/cross-site-networks/delete create mode 100644 gcloud/alpha/compute/interconnects/cross-site-networks/list create mode 100644 gcloud/alpha/compute/interconnects/cross-site-networks/update create mode 100644 gcloud/alpha/compute/interconnects/wire-groups/create create mode 100644 gcloud/alpha/compute/interconnects/wire-groups/help create mode 100644 gcloud/alpha/network-security/security-profiles/export create mode 100644 gcloud/alpha/network-security/security-profiles/list create mode 100644 gcloud/beta/workbench/help create mode 100644 gcloud/compute/instance-groups/managed/resume-instances create mode 100644 gcloud/compute/instance-groups/managed/start-instances create mode 100644 gcloud/compute/instance-groups/managed/stop-instances create mode 100644 gcloud/compute/instance-groups/managed/suspend-instances create mode 100644 gcloud/network-management/vpc-flow-logs-configs/create create mode 100644 gcloud/network-management/vpc-flow-logs-configs/delete create mode 100644 gcloud/network-management/vpc-flow-logs-configs/describe create mode 100644 gcloud/network-management/vpc-flow-logs-configs/help create mode 100644 gcloud/network-management/vpc-flow-logs-configs/list create mode 100644 gcloud/network-management/vpc-flow-logs-configs/update diff --git a/gcloud/_version b/gcloud/_version index 536e1c6b4..b7abfd6b2 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 504.0.1 -alpha 2024.12.19 -beta 2024.12.19 +Google Cloud SDK 505.0.0 +alpha 2025.01.03 +beta 2025.01.03 bq 2.1.11 bundled-python3-unix 3.11.9 -core 2024.12.19 +core 2025.01.03 gcloud-crc32c 1.0.0 gsutil 5.33 diff --git a/gcloud/ai/endpoints/deploy-model b/gcloud/ai/endpoints/deploy-model index b37333362..d5aabe063 100644 --- a/gcloud/ai/endpoints/deploy-model +++ b/gcloud/ai/endpoints/deploy-model @@ -72,9 +72,9 @@ OPTIONAL FLAGS type The type of the accelerator. Choices are 'nvidia-a100-80gb', - 'nvidia-h100-80gb', 'nvidia-l4', 'nvidia-tesla-a100', - 'nvidia-tesla-k80', 'nvidia-tesla-p100', 'nvidia-tesla-p4', - 'nvidia-tesla-t4', 'nvidia-tesla-v100'. + 'nvidia-h100-80gb', 'nvidia-h100-mega-80gb', 'nvidia-l4', + 'nvidia-tesla-a100', 'nvidia-tesla-k80', 'nvidia-tesla-p100', + 'nvidia-tesla-p4', 'nvidia-tesla-t4', 'nvidia-tesla-v100'. count The number of accelerators to attach to each machine running the diff --git a/gcloud/alpha/alloydb/instances/create b/gcloud/alpha/alloydb/instances/create index d9a15bd1a..258bc086d 100644 --- a/gcloud/alpha/alloydb/instances/create +++ b/gcloud/alpha/alloydb/instances/create @@ -9,7 +9,17 @@ SYNOPSIS [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async] [--authorized-external-networks=[AUTHORIZED_NETWORK,...]] [--availability-type=AVAILABILITY_TYPE] + [--connection-pooling-ignore-startup-parameters=[STARTUP_PARAMETERS, + ...]] + [--connection-pooling-max-client-connections=CONNECTION_POOLING_MAX_CLIENT_CONNECTIONS] + [--connection-pooling-max-pool-size=CONNECTION_POOLING_MAX_POOL_SIZE] + [--connection-pooling-min-pool-size=CONNECTION_POOLING_MIN_POOL_SIZE] + [--connection-pooling-pool-mode=CONNECTION_POOLING_POOL_MODE] + [--connection-pooling-query-wait-timeout=CONNECTION_POOLING_QUERY_WAIT_TIMEOUT] + [--connection-pooling-server-idle-timeout=CONNECTION_POOLING_SERVER_IDLE_TIMEOUT] + [--connection-pooling-stats-users=[STATS_USERS,...]] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] + [--[no-]enable-connection-pooling] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] @@ -111,6 +121,38 @@ OPTIONAL FLAGS production instances; instance does not automatically fail over to another zone. + --connection-pooling-ignore-startup-parameters=[STARTUP_PARAMETERS,...] + Comma-separated list of startup parameters that should be ignored by + the connection pool. + + --connection-pooling-max-client-connections=CONNECTION_POOLING_MAX_CLIENT_CONNECTIONS + The max client connections for managed connection pooling. + + --connection-pooling-max-pool-size=CONNECTION_POOLING_MAX_POOL_SIZE + The max pool size for managed connection pooling. + + --connection-pooling-min-pool-size=CONNECTION_POOLING_MIN_POOL_SIZE + The min pool size for managed connection pooling. + + --connection-pooling-pool-mode=CONNECTION_POOLING_POOL_MODE + The pool mode for managed connection pooling. + CONNECTION_POOLING_POOL_MODE must be one of: + + SESSION + Session mode for managed connection pooling. + TRANSACTION + Transaction mode for managed connection pooling. + + --connection-pooling-query-wait-timeout=CONNECTION_POOLING_QUERY_WAIT_TIMEOUT + The query wait timeout for managed connection pooling. + + --connection-pooling-server-idle-timeout=CONNECTION_POOLING_SERVER_IDLE_TIMEOUT + The server idle timeout for managed connection pooling. + + --connection-pooling-stats-users=[STATS_USERS,...] + Comma-separated list of database users to access connection pooling + stats. + --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an equals sign to separate flag name and value. Flags without values, like @@ -119,6 +161,11 @@ OPTIONAL FLAGS API for allowed flags. (e.g., --database-flags max_allowed_packet=55555,skip_grant_tables=,log_output=1) + --[no-]enable-connection-pooling + Enable connection pooling for the instance. Use + --enable-connection-pooling to enable and + --no-enable-connection-pooling to disable. + --insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE Number of query plans to sample every minute. Default value is 5. Allowed range: 0 to 20. diff --git a/gcloud/alpha/alloydb/instances/update b/gcloud/alpha/alloydb/instances/update index 6b5649a41..0b0abe7bc 100644 --- a/gcloud/alpha/alloydb/instances/update +++ b/gcloud/alpha/alloydb/instances/update @@ -8,8 +8,18 @@ SYNOPSIS [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async] [--authorized-external-networks=[AUTHORIZED_NETWORK,...]] [--availability-type=AVAILABILITY_TYPE] - [--clear-psc-network-attachment-url] [--cpu-count=CPU_COUNT] - [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] + [--clear-psc-network-attachment-url] + [--connection-pooling-ignore-startup-parameters=[STARTUP_PARAMETERS, + ...]] + [--connection-pooling-max-client-connections=CONNECTION_POOLING_MAX_CLIENT_CONNECTIONS] + [--connection-pooling-max-pool-size=CONNECTION_POOLING_MAX_POOL_SIZE] + [--connection-pooling-min-pool-size=CONNECTION_POOLING_MIN_POOL_SIZE] + [--connection-pooling-pool-mode=CONNECTION_POOLING_POOL_MODE] + [--connection-pooling-query-wait-timeout=CONNECTION_POOLING_QUERY_WAIT_TIMEOUT] + [--connection-pooling-server-idle-timeout=CONNECTION_POOLING_SERVER_IDLE_TIMEOUT] + [--connection-pooling-stats-users=[STATS_USERS,...]] + [--cpu-count=CPU_COUNT] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] + [--[no-]enable-connection-pooling] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] @@ -92,6 +102,38 @@ OPTIONAL FLAGS Disable outbound connectivity from an AlloyDB instance which uses Private Service Connect (PSC). + --connection-pooling-ignore-startup-parameters=[STARTUP_PARAMETERS,...] + Comma-separated list of startup parameters that should be ignored by + the connection pool. + + --connection-pooling-max-client-connections=CONNECTION_POOLING_MAX_CLIENT_CONNECTIONS + The max client connections for managed connection pooling. + + --connection-pooling-max-pool-size=CONNECTION_POOLING_MAX_POOL_SIZE + The max pool size for managed connection pooling. + + --connection-pooling-min-pool-size=CONNECTION_POOLING_MIN_POOL_SIZE + The min pool size for managed connection pooling. + + --connection-pooling-pool-mode=CONNECTION_POOLING_POOL_MODE + The pool mode for managed connection pooling. + CONNECTION_POOLING_POOL_MODE must be one of: + + SESSION + Session mode for managed connection pooling. + TRANSACTION + Transaction mode for managed connection pooling. + + --connection-pooling-query-wait-timeout=CONNECTION_POOLING_QUERY_WAIT_TIMEOUT + The query wait timeout for managed connection pooling. + + --connection-pooling-server-idle-timeout=CONNECTION_POOLING_SERVER_IDLE_TIMEOUT + The server idle timeout for managed connection pooling. + + --connection-pooling-stats-users=[STATS_USERS,...] + Comma-separated list of database users to access connection pooling + stats. + --cpu-count=CPU_COUNT Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: @@ -106,6 +148,11 @@ OPTIONAL FLAGS API for allowed flags. (e.g., --database-flags max_allowed_packet=55555,skip_grant_tables=,log_output=1) + --[no-]enable-connection-pooling + Enable connection pooling for the instance. Use + --enable-connection-pooling to enable and + --no-enable-connection-pooling to disable. + --insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE Number of query plans to sample every minute. Default value is 5. Allowed range: 0 to 20. diff --git a/gcloud/alpha/assured/workloads/create b/gcloud/alpha/assured/workloads/create index 071293643..718a932be 100644 --- a/gcloud/alpha/assured/workloads/create +++ b/gcloud/alpha/assured/workloads/create @@ -87,8 +87,8 @@ REQUIRED FLAGS The compliance regime of the new Assured Workloads environment. COMPLIANCE_REGIME must be one of: assured-workloads-for-partners, au-regions-and-us-support, ca-protected-b, ca-regions-and-support, - cjis, eu-regions-and-support, fedramp-high, fedramp-moderate, - healthcare-and-life-sciences-controls, + canada-controlled-goods, cjis, eu-regions-and-support, fedramp-high, + fedramp-moderate, healthcare-and-life-sciences-controls, healthcare-and-life-sciences-controls-us-support, hipaa, hitrust, il2, il4, il5, irs-1075, isr-regions, isr-regions-and-support, itar, jp-regions-and-support, diff --git a/gcloud/alpha/auth/application-default/login b/gcloud/alpha/auth/application-default/login index f6f91e0f5..d333f3518 100644 --- a/gcloud/alpha/auth/application-default/login +++ b/gcloud/alpha/auth/application-default/login @@ -52,7 +52,7 @@ POSITIONAL ARGUMENTS credentials. FLAGS - --no-browser + --browser If you want to authorize the client libraries on a machine that doesn't have a browser and you can install the gcloud CLI on another machine with a browser, use the --no-browser flag. @@ -74,6 +74,8 @@ FLAGS "Enter the output of the above command", and press Enter to complete the authorization. + Enabled by default, use --no-browser to disable. + --client-id-file=CLIENT_ID_FILE A file containing your own client id to use to login. If --client-id-file is specified, the quota project will not be written to diff --git a/gcloud/alpha/auth/login b/gcloud/alpha/auth/login index 862f15c5c..9ae064aa8 100644 --- a/gcloud/alpha/auth/login +++ b/gcloud/alpha/auth/login @@ -77,7 +77,7 @@ FLAGS --brief Minimal user output. - --no-browser + --browser If you want to authorize the gcloud CLI on a machine that doesn't have a browser and you can install the gcloud CLI on another machine with a browser, use the --no-browser flag. @@ -99,6 +99,8 @@ FLAGS "Enter the output of the above command", and press Enter to complete the authorization. + Enabled by default, use --no-browser to disable. + --cred-file=CRED_FILE Path to the external account configuration file (workload identity pool, generated by the Cloud Console or gcloud iam diff --git a/gcloud/alpha/billing/budgets/create b/gcloud/alpha/billing/budgets/create index f9ef6ff0c..135e934eb 100644 --- a/gcloud/alpha/billing/budgets/create +++ b/gcloud/alpha/billing/budgets/create @@ -164,25 +164,31 @@ OPTIONAL FLAGS Must be one of: 'current-spend' or 'forecasted-spend'. Behavior defaults to 'current-spend' if not set. + Specify either the calendar-period or custom-period, not both. + At most one of these can be specified: - --calendar-period=CALENDAR_PERIOD - Specifies to track usage over recurring calendar period. If you're - creating a budget with a custom time period, omit this flag. - CALENDAR_PERIOD must be one of: calendar-period-unspecified, month, - quarter, year. + Calendar Period - --start-date=START_DATE - Specifies to track usage after any start date. This time period is - static, it does not recur. + --calendar-period=CALENDAR_PERIOD + Specified to track usage over recurring calendar period. If you're + creating a budget with a custom time period, omit this flag. + CALENDAR_PERIOD must be one of: calendar-period-unspecified, month, + quarter, year. - This flag argument must be specified if any of the other arguments in - this group are specified. + Custom Period - --end-date=END_DATE - Specifies to track usage before any end date. This time period is - static, it does not recur. If specified, --start-date must also be - specified. + --start-date=START_DATE + Specified to track usage after any start date. This time period is + static, it does not recur. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --end-date=END_DATE + Specified to track usage before any end date. This time period is + static, it does not recur. If specified, --start-date must also be + specified. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/billing/budgets/update b/gcloud/alpha/billing/budgets/update index 408b34e52..48fd85cb7 100644 --- a/gcloud/alpha/billing/budgets/update +++ b/gcloud/alpha/billing/budgets/update @@ -158,25 +158,31 @@ FLAGS --last-period-amount Use the amount of last period's budget. + Specify either the calendar-period or custom-period, not both. + At most one of these can be specified: - --calendar-period=CALENDAR_PERIOD - Specifies to track usage over recurring calendar period. If you're - creating a budget with a custom time period, omit this flag. - CALENDAR_PERIOD must be one of: calendar-period-unspecified, month, - quarter, year. + Calendar Period - --start-date=START_DATE - Specifies to track usage after any start date. This time period is - static, it does not recur. + --calendar-period=CALENDAR_PERIOD + Specified to track usage over recurring calendar period. If you're + creating a budget with a custom time period, omit this flag. + CALENDAR_PERIOD must be one of: calendar-period-unspecified, month, + quarter, year. - This flag argument must be specified if any of the other arguments in - this group are specified. + Custom Period - --end-date=END_DATE - Specifies to track usage before any end date. This time period is - static, it does not recur. If specified, --start-date must also be - specified. + --start-date=START_DATE + Specified to track usage after any start date. This time period is + static, it does not recur. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --end-date=END_DATE + Specified to track usage before any end date. This time period is + static, it does not recur. If specified, --start-date must also be + specified. At most one of these can be specified: diff --git a/gcloud/alpha/builds/worker-pools/create b/gcloud/alpha/builds/worker-pools/create index fae6a9a01..6c96e5656 100644 --- a/gcloud/alpha/builds/worker-pools/create +++ b/gcloud/alpha/builds/worker-pools/create @@ -135,7 +135,7 @@ FLAGS --worker-disk-size=WORKER_DISK_SIZE Size of the disk attached to the worker. - If not given, Cloud Build will use a standard disk size. + If unspecified, Cloud Build uses a standard disk size. --worker-machine-type=WORKER_MACHINE_TYPE Compute Engine machine type for a worker pool. diff --git a/gcloud/alpha/builds/worker-pools/update b/gcloud/alpha/builds/worker-pools/update index ceecea577..0ae38038a 100644 --- a/gcloud/alpha/builds/worker-pools/update +++ b/gcloud/alpha/builds/worker-pools/update @@ -53,7 +53,7 @@ REQUIRED FLAGS --worker-disk-size=WORKER_DISK_SIZE Size of the disk attached to the worker. - If not given, Cloud Build will use a standard disk size. + If unspecified, Cloud Build uses a standard disk size. --worker-machine-type=WORKER_MACHINE_TYPE Compute Engine machine type for a worker pool. diff --git a/gcloud/alpha/compute/future-reservations/create b/gcloud/alpha/compute/future-reservations/create index 4c9a9a0c5..5fd5469e6 100644 --- a/gcloud/alpha/compute/future-reservations/create +++ b/gcloud/alpha/compute/future-reservations/create @@ -16,6 +16,7 @@ SYNOPSIS [--deployment-type=DEPLOYMENT_TYPE] [--description=DESCRIPTION] [--name-prefix=NAME_PREFIX] [--planning-status=PLANNING_STATUS] [--[no-]require-specific-reservation] + [--reservation-mode=RESERVATION_MODE] [--reservation-name=RESERVATION_NAME] [--scheduling-type=SCHEDULING_TYPE] [--zone=ZONE] [--auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME | --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION] @@ -207,6 +208,19 @@ OPTIONAL FLAGS the name of the future reservation. Use --require-specific-reservation to enable and --no-require-specific-reservation to disable. + --reservation-mode=RESERVATION_MODE + The mode of the reservation. RESERVATION_MODE must be one of: + + CALENDAR + This indicates to create a future reservation in calendar mode, + which is ideal for reserving GPU VMs. The auto-created reservations + for the future reservation are automatically deleted at the end of + the reservation period. + DEFAULT + This indicates to create a standard future reservation. If you want + to automatically delete the auto-created reservations, then you + must use the --auto-delete-auto-created-reservations flag. + --reservation-name=RESERVATION_NAME Name of reservations where the capacity is provisioned at the time of delivery of future reservations. If the reservation with the given name diff --git a/gcloud/alpha/compute/instance-groups/managed/resume-instances b/gcloud/alpha/compute/instance-groups/managed/resume-instances index 08e39be75..1dcbe11fd 100644 --- a/gcloud/alpha/compute/instance-groups/managed/resume-instances +++ b/gcloud/alpha/compute/instance-groups/managed/resume-instances @@ -71,7 +71,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 instance-groups managed resume-instances $ gcloud beta compute instance-groups managed resume-instances diff --git a/gcloud/alpha/compute/instance-groups/managed/start-instances b/gcloud/alpha/compute/instance-groups/managed/start-instances index 7f25e83a7..df6344f43 100644 --- a/gcloud/alpha/compute/instance-groups/managed/start-instances +++ b/gcloud/alpha/compute/instance-groups/managed/start-instances @@ -70,7 +70,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instance-groups managed start-instances $ gcloud beta compute instance-groups managed start-instances diff --git a/gcloud/alpha/compute/instance-groups/managed/stop-instances b/gcloud/alpha/compute/instance-groups/managed/stop-instances index cd71dde28..51da50efe 100644 --- a/gcloud/alpha/compute/instance-groups/managed/stop-instances +++ b/gcloud/alpha/compute/instance-groups/managed/stop-instances @@ -68,7 +68,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 instance-groups managed stop-instances $ gcloud beta compute instance-groups managed stop-instances diff --git a/gcloud/alpha/compute/instance-groups/managed/suspend-instances b/gcloud/alpha/compute/instance-groups/managed/suspend-instances index 12bec541d..857669347 100644 --- a/gcloud/alpha/compute/instance-groups/managed/suspend-instances +++ b/gcloud/alpha/compute/instance-groups/managed/suspend-instances @@ -75,7 +75,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 instance-groups managed suspend-instances $ gcloud beta compute instance-groups managed suspend-instances diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index 063b80cde..a99819d85 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -20,7 +20,8 @@ SYNOPSIS [device-name=DEVICE-NAME],[name=NAME],[scope=SCOPE]] [--enable-display-device] [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] [--enable-watchdog-timer] - [--erase-windows-vss-signature] + [--erase-windows-vss-signature] [--graceful-shutdown] + [--graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--labels=[KEY=VALUE,...]] @@ -453,6 +454,17 @@ OPTIONAL FLAGS machine image should erase Windows specific VSS signature. See https://cloud.google.com/sdk/gcloud/reference/compute/disks/snapshot#--guest-flush + --graceful-shutdown + Enables graceful shutdown for the instance. + + --graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION + Specifies the maximum time for the graceful shutdown. After this time, + the instance is set to STOPPING even if tasks are still running. + Specify the time as the number of hours, minutes, or seconds followed + by h, m, and s respectively. For example, specify 30m for 30 minutes or + 20m10s for 20 minutes and 10 seconds. The value must be between 1 + second and 1 hour. + --host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS The timeout in seconds for host error detection. The value must be set with 30 second increments, with a range of 90 to 330 seconds. If unset, diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index c0aca7fcc..199eeafd9 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -32,6 +32,8 @@ SYNOPSIS [--[no-]enable-nested-virtualization] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] + [--graceful-shutdown] + [--graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] @@ -497,6 +499,17 @@ FLAGS be used together with --external-ipv6-address. Only the /96 IP address range is supported, and the default value is 96. + --graceful-shutdown + Enables graceful shutdown for the instance. + + --graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION + Specifies the maximum time for the graceful shutdown. After this time, + the instance is set to STOPPING even if tasks are still running. + Specify the time as the number of hours, minutes, or seconds followed + by h, m, and s respectively. For example, specify 30m for 30 minutes or + 20m10s for 20 minutes and 10 seconds. The value must be between 1 + second and 1 hour. + --host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS The timeout in seconds for host error detection. The value must be set with 30 second increments, with a range of 90 to 330 seconds. If unset, diff --git a/gcloud/alpha/compute/interconnects/attachments/dedicated/create b/gcloud/alpha/compute/interconnects/attachments/dedicated/create index 9a6fb5854..c2e2975b3 100644 --- a/gcloud/alpha/compute/interconnects/attachments/dedicated/create +++ b/gcloud/alpha/compute/interconnects/attachments/dedicated/create @@ -60,6 +60,8 @@ OPTIONAL FLAGS 20 Gbit/s 50g 50 Gbit/s + 100g + 100 Gbit/s --candidate-ipv6-subnets=[IPV6_SUBNET,...] The candididate-ipv6-subnets field is not available. diff --git a/gcloud/alpha/compute/interconnects/attachments/dedicated/update b/gcloud/alpha/compute/interconnects/attachments/dedicated/update index 223553a83..5e74a51b8 100644 --- a/gcloud/alpha/compute/interconnects/attachments/dedicated/update +++ b/gcloud/alpha/compute/interconnects/attachments/dedicated/update @@ -50,6 +50,8 @@ FLAGS 20 Gbit/s 50g 50 Gbit/s + 100g + 100 Gbit/s --candidate-ipv6-subnets=[IPV6_SUBNET,...] The candididate-ipv6-subnets field is not available. diff --git a/gcloud/alpha/compute/interconnects/cross-site-networks/create b/gcloud/alpha/compute/interconnects/cross-site-networks/create index af845a8ae..0087a1a4d 100644 --- a/gcloud/alpha/compute/interconnects/cross-site-networks/create +++ b/gcloud/alpha/compute/interconnects/cross-site-networks/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha compute interconnects cross-site-networks create NAME - --project=PROJECT [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute interconnects cross-site-networks create is @@ -22,13 +22,9 @@ EXAMPLES POSITIONAL ARGUMENTS NAME - Name of the cross site network to create. + Name of the crossSiteNetwork to create. -REQUIRED FLAGS - --project=PROJECT - A project for the cross site network. - -OPTIONAL FLAGS +FLAGS --description=DESCRIPTION An optional, textual description for the cross site network. diff --git a/gcloud/alpha/compute/interconnects/cross-site-networks/delete b/gcloud/alpha/compute/interconnects/cross-site-networks/delete new file mode 100644 index 000000000..8fc7aff0e --- /dev/null +++ b/gcloud/alpha/compute/interconnects/cross-site-networks/delete @@ -0,0 +1,30 @@ +NAME + gcloud alpha compute interconnects cross-site-networks delete - delete + Compute Engine cross site networks + +SYNOPSIS + gcloud alpha compute interconnects cross-site-networks delete NAME + [NAME ...] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects cross-site-networks delete + deletes Compute Engine cross site networks. + +POSITIONAL ARGUMENTS + NAME [NAME ...] + Names of the crossSiteNetworks to delete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/cross-site-networks/help b/gcloud/alpha/compute/interconnects/cross-site-networks/help index 8300fbba0..0c838d060 100644 --- a/gcloud/alpha/compute/interconnects/cross-site-networks/help +++ b/gcloud/alpha/compute/interconnects/cross-site-networks/help @@ -20,6 +20,15 @@ COMMANDS create (ALPHA) Create a Compute Engine cross site network. + delete + (ALPHA) Delete Compute Engine cross site networks. + + list + (ALPHA) List Google Compute Engine cross site networks. + + update + (ALPHA) Update a Compute Engine cross site network. + 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/compute/interconnects/cross-site-networks/list b/gcloud/alpha/compute/interconnects/cross-site-networks/list new file mode 100644 index 000000000..0973e002e --- /dev/null +++ b/gcloud/alpha/compute/interconnects/cross-site-networks/list @@ -0,0 +1,68 @@ +NAME + gcloud alpha compute interconnects cross-site-networks list - list Google + Compute Engine cross site networks + +SYNOPSIS + gcloud alpha compute interconnects cross-site-networks list + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects cross-site-networks list + displays all Google Compute Engine cross site networks in a project. + +EXAMPLES + To list all cross site networks in a project in table form, run: + + $ gcloud alpha compute interconnects cross-site-networks list + + To list the URIs of all cross site networks in a project, run: + + $ gcloud alpha compute interconnects cross-site-networks list --uri + +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. + diff --git a/gcloud/alpha/compute/interconnects/cross-site-networks/update b/gcloud/alpha/compute/interconnects/cross-site-networks/update new file mode 100644 index 000000000..5f838cc29 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/cross-site-networks/update @@ -0,0 +1,35 @@ +NAME + gcloud alpha compute interconnects cross-site-networks update - update a + Compute Engine cross site network + +SYNOPSIS + gcloud alpha compute interconnects cross-site-networks update NAME + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects cross-site-networks update is + used to update cross site networks. A cross site network encapsulates wire + groups. + +POSITIONAL ARGUMENTS + NAME + Name of the crossSiteNetwork to update. + +FLAGS + --description=DESCRIPTION + An optional, textual description for the cross site network. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/help b/gcloud/alpha/compute/interconnects/help index 95b34fd2f..5cbc0db0a 100644 --- a/gcloud/alpha/compute/interconnects/help +++ b/gcloud/alpha/compute/interconnects/help @@ -43,6 +43,9 @@ GROUPS (ALPHA) Read and manipulate Google Compute Engine interconnect remote locations. + wire-groups + (ALPHA) Create or manipulate wire groups. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/alpha/compute/interconnects/wire-groups/create b/gcloud/alpha/compute/interconnects/wire-groups/create new file mode 100644 index 000000000..c11c4dbc5 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/wire-groups/create @@ -0,0 +1,106 @@ +NAME + gcloud alpha compute interconnects wire-groups create - create a Compute + Engine wire group + +SYNOPSIS + gcloud alpha compute interconnects wire-groups create NAME + --bandwidth-unmetered=BANDWIDTH_UNMETERED + --cross-site-network=CROSS_SITE_NETWORK --type=TYPE + [--admin-enabled=ADMIN_ENABLED] + [--bandwidth-allocation=BANDWIDTH_ALLOCATION] + [--bandwidth-metered=BANDWIDTH_METERED] [--description=DESCRIPTION] + [--fault-response=FAULT_RESPONSE] + [--network-service-class=NETWORK_SERVICE_CLASS] + [--validate-only=VALIDATE_ONLY] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects wire-groups create is used to + create wire groups. A wire group represents a group of redundant wires + between interconnects in two different metros. Each WireGroup belongs to a + CrossSiteNetwork. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To create a wire group, run: + + $ gcloud alpha compute interconnects wire-groups create \ + example-wire-group --project my-project \ + --cross-site-network example-cross-site-network --type WIRE \ + --bandwidth-unmetered 10g --network-service-class BRONZE \ + --bandwidth-allocation ALLOCATE_PER_WIRE + +POSITIONAL ARGUMENTS + NAME + Name of the wire group to create. + +REQUIRED FLAGS + --bandwidth-unmetered=BANDWIDTH_UNMETERED + The amount of unmetered bandwidth to assign to the wire group. + + --cross-site-network=CROSS_SITE_NETWORK + Name of the crossSiteNetwork to operate on. + + --type=TYPE + The type for the wire group. TYPE must be one of: + + BOX_AND_CROSS + Box and cross + REDUNDANT + Redundant + WIRE + Wire + +OPTIONAL FLAGS + --admin-enabled=ADMIN_ENABLED + Set admin-enabled on the wire group. + + --bandwidth-allocation=BANDWIDTH_ALLOCATION + The bandwidth allocation for the wire group. BANDWIDTH_ALLOCATION must + be one of: + + ALLOCATE_PER_WIRE + Allocate per wire. + SHARED_WITH_WIRE_GROUP + Shared with wire group. + + --bandwidth-metered=BANDWIDTH_METERED + The amount of metered bandwidth to assign to the wire group. + + --description=DESCRIPTION + An optional, textual description for the wire group. + + --fault-response=FAULT_RESPONSE + The fault response for the wire group. FAULT_RESPONSE must be one of: + + DISABLED_PORT + Disabled port + NONE + None + + --network-service-class=NETWORK_SERVICE_CLASS + The network service class for the wire group. NETWORK_SERVICE_CLASS + must be one of: + + BRONZE + Bronze. + GOLD + Gold. + + --validate-only=VALIDATE_ONLY + Only validates the configuration, but does not create it. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/wire-groups/help b/gcloud/alpha/compute/interconnects/wire-groups/help new file mode 100644 index 000000000..c2233f262 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/wire-groups/help @@ -0,0 +1,28 @@ +NAME + gcloud alpha compute interconnects wire-groups - create or manipulate wire + groups + +SYNOPSIS + gcloud alpha compute interconnects wire-groups COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create or manipulate wire groups. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a Compute Engine wire group. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/org-security-policies/associations/create b/gcloud/alpha/compute/org-security-policies/associations/create index 79e9fb6af..8795b9d46 100644 --- a/gcloud/alpha/compute/org-security-policies/associations/create +++ b/gcloud/alpha/compute/org-security-policies/associations/create @@ -7,9 +7,10 @@ SYNOPSIS gcloud alpha compute org-security-policies associations create --security-policy=SECURITY_POLICY [--excluded-folders=[EXCLUDED_FOLDERS,...]] - [--excluded-projects=[EXCLUDED_PROJECTS,...]] [--folder=FOLDER] - [--name=NAME] [--organization=ORGANIZATION] - [--replace-association-on-target] [GCLOUD_WIDE_FLAG ...] + [--excluded-projects=[EXCLUDED_PROJECTS,...]] [--name=NAME] + [--organization=ORGANIZATION] [--replace-association-on-target] + [--folder=FOLDER | --project-number=PROJECT_NUMBER] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute org-security-policies associations create is @@ -37,16 +38,13 @@ OPTIONAL FLAGS List of projects to exclude from the application of this security policy. Projects should be specified in the form "projects/123". - --folder=FOLDER - ID of the folder with which the association is created. - --name=NAME Name to identify this association. If unspecified, the name will be set to "organization-{ORGANIZATION_ID}" or "folder-{FOLDER_ID}". --organization=ORGANIZATION - ID of the organization in which the security policy is to be - associated. Must be set if SECURITY_POLICY is short name. + ID of the organization to associate the security policy with. Must be + set if SECURITY_POLICY is short name. --replace-association-on-target By default, if you attempt to insert an association to an organization @@ -54,6 +52,14 @@ OPTIONAL FLAGS the method will fail. If this is set, the existing association will be deleted at the same time that the new association is created. + At most one of these can be specified: + + --folder=FOLDER + ID of the folder to associate the security policy with. + + --project-number=PROJECT_NUMBER + Project number to associate the security policy with. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/project-info/update b/gcloud/alpha/compute/project-info/update index 6fa96151b..3328cd653 100644 --- a/gcloud/alpha/compute/project-info/update +++ b/gcloud/alpha/compute/project-info/update @@ -16,7 +16,7 @@ DESCRIPTION FLAGS --cloud-armor-tier=CLOUD_ARMOR_TIER Cloud armor tier to assign to the project. CLOUD_ARMOR_TIER must be one - of: CA_STANDARD, CA_ENTERPRISE_PAYGO. + of: CA_STANDARD, CA_ENTERPRISE_PAYGO, CA_ENTERPRISE_ANNUAL. --default-network-tier=DEFAULT_NETWORK_TIER The default network tier to assign to the project. DEFAULT_NETWORK_TIER @@ -24,7 +24,8 @@ FLAGS --managed-protection-tier=MANAGED_PROTECTION_TIER Managed protection tier to assign to the project. - MANAGED_PROTECTION_TIER must be one of: CA_STANDARD, CAMP_PLUS_PAYGO. + MANAGED_PROTECTION_TIER must be one of: CA_STANDARD, CAMP_PLUS_PAYGO, + CAMP_PLUS_ANNUAL. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index 1c090cff7..a84eae6ac 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -21,7 +21,8 @@ SYNOPSIS [device-name=DEVICE-NAME],[name=NAME],[scope=SCOPE]] [--enable-display-device] [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] [--enable-watchdog-timer] - [--erase-windows-vss-signature] + [--erase-windows-vss-signature] [--graceful-shutdown] + [--graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--labels=[KEY=VALUE,...]] @@ -437,6 +438,17 @@ OPTIONAL FLAGS machine image should erase Windows specific VSS signature. See https://cloud.google.com/sdk/gcloud/reference/compute/disks/snapshot#--guest-flush + --graceful-shutdown + Enables graceful shutdown for the instance. + + --graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION + Specifies the maximum time for the graceful shutdown. After this time, + the instance is set to STOPPING even if tasks are still running. + Specify the time as the number of hours, minutes, or seconds followed + by h, m, and s respectively. For example, specify 30m for 30 minutes or + 20m10s for 20 minutes and 10 seconds. The value must be between 1 + second and 1 hour. + --host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS The timeout in seconds for host error detection. The value must be set with 30 second increments, with a range of 90 to 330 seconds. If unset, diff --git a/gcloud/alpha/compute/ssh b/gcloud/alpha/compute/ssh index d964584d4..7a24b73e0 100644 --- a/gcloud/alpha/compute/ssh +++ b/gcloud/alpha/compute/ssh @@ -166,8 +166,8 @@ FLAGS $ gcloud alpha compute ssh VM_NAME --zone=ZONE \ --troubleshoot [--tunnel-through-iap] - The troubleshoot flag runs tests and returns recommendations for four - types of issues: + The troubleshoot flag runs tests and returns recommendations for the + following types of issues: ◆ VM status ◆ Network connectivity ◆ User permissions diff --git a/gcloud/alpha/container/fleet/policycontroller/enable b/gcloud/alpha/container/fleet/policycontroller/enable index 4efc229dc..3bedc0b13 100644 --- a/gcloud/alpha/container/fleet/policycontroller/enable +++ b/gcloud/alpha/container/fleet/policycontroller/enable @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha container fleet policycontroller enable [--all-memberships | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION] --audit-interval=AUDIT_INTERVAL - --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT --no-content --no-default-bundles --version=VERSION --clear-exemptable-namespaces | --exemptable-namespaces=EXEMPTABLE_NAMESPACES --log-denies | --no-log-denies --monitoring=MONITORING @@ -71,6 +71,10 @@ FLAGS The number of violations stored on the constraint resource. Must be greater than 0. + --no-content + If set, Policy content, including the template library and policy + bundles, will not be installed. + --no-default-bundles If set, skip installing the default bundle of policy-essentials. diff --git a/gcloud/alpha/container/hub/policycontroller/enable b/gcloud/alpha/container/hub/policycontroller/enable index f33031316..3437b8f04 100644 --- a/gcloud/alpha/container/hub/policycontroller/enable +++ b/gcloud/alpha/container/hub/policycontroller/enable @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha container hub policycontroller enable [--all-memberships | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION] --audit-interval=AUDIT_INTERVAL - --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT --no-content --no-default-bundles --version=VERSION --clear-exemptable-namespaces | --exemptable-namespaces=EXEMPTABLE_NAMESPACES --log-denies | --no-log-denies --monitoring=MONITORING @@ -71,6 +71,10 @@ FLAGS The number of violations stored on the constraint resource. Must be greater than 0. + --no-content + If set, Policy content, including the template library and policy + bundles, will not be installed. + --no-default-bundles If set, skip installing the default bundle of policy-essentials. diff --git a/gcloud/alpha/edge-cloud/container/clusters/create b/gcloud/alpha/edge-cloud/container/clusters/create index c645d2214..bf5e89e0a 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/create +++ b/gcloud/alpha/edge-cloud/container/clusters/create @@ -137,26 +137,17 @@ FLAGS For example, - { - - "externalLoadBalancerAddressPools": [ - { - - "addressPool": "MyLoadBalancerPool", - - "ipv4Range": ["10.200.0.200-10.200.0.204","10.200.0.300/30"], - - "avoidBuggyIps": "false", - - "manualAssign": "true" - + "externalLoadBalancerAddressPools": [ + { + "addressPool": "MyLoadBalancerPool", + "ipv4Range": ["10.200.0.200-10.200.0.204","10.200.0.300/30"], + "avoidBuggyIps": "false", + "manualAssign": "true" + } + ] } - ] - - } - address_pool Optional. A name that identifies an address pool. If a name is not specified, an auto-generated one will be used. diff --git a/gcloud/alpha/firestore/indexes/composite/create b/gcloud/alpha/firestore/indexes/composite/create index 1a5f5f425..8c88000db 100644 --- a/gcloud/alpha/firestore/indexes/composite/create +++ b/gcloud/alpha/firestore/indexes/composite/create @@ -58,11 +58,11 @@ REQUIRED FLAGS Shorthand Example: - --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {"string"}}' --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {"string"}}' + --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {}}' --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {}}' JSON Example: - --field-config='[{"array-config": "string", "field-path": "string", "order": "string", "vector-config": {"dimension": int, "flat": {"string"}}}]' + --field-config='[{"array-config": "string", "field-path": "string", "order": "string", "vector-config": {"dimension": int, "flat": {}}}]' File Example: diff --git a/gcloud/alpha/iam/list-grantable-roles b/gcloud/alpha/iam/list-grantable-roles index 664947461..30895b295 100644 --- a/gcloud/alpha/iam/list-grantable-roles +++ b/gcloud/alpha/iam/list-grantable-roles @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha iam list-grantable-roles RESOURCE [--filter=EXPRESSION] - [--page-size=PAGE_SIZE; default=100] [GCLOUD_WIDE_FLAG ...] + [--page-size=PAGE_SIZE; default=300] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command displays the list of grantable roles for a resource. @@ -50,9 +50,9 @@ LIST COMMAND FLAGS This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. - --page-size=PAGE_SIZE; default=100 + --page-size=PAGE_SIZE; default=300 Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is 100. + specifies the maximum number of resources per page. The default is 300. Paging may be applied before or after --filter and --limit depending on the service. diff --git a/gcloud/alpha/iam/policies/delete b/gcloud/alpha/iam/policies/delete index 7e60a187f..cd25c4de5 100644 --- a/gcloud/alpha/iam/policies/delete +++ b/gcloud/alpha/iam/policies/delete @@ -33,8 +33,11 @@ REQUIRED FLAGS OPTIONAL FLAGS --etag=ETAG - Etag that identifies the version of the existing policy. If omitted, - the policy is deleted regardless of its current etag. + Etag that identifies the version of the existing policy. It can be + obtained by running gcloud iam policies get. When deleting a policy, if + the etag is omitted, the policy is deleted regardless of its current + etag. When updating a policy, if the etag is omitted, the update uses + the etag provided in the policy file. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/iam/policies/update b/gcloud/alpha/iam/policies/update index fbc9d44df..2c818d6be 100644 --- a/gcloud/alpha/iam/policies/update +++ b/gcloud/alpha/iam/policies/update @@ -5,19 +5,20 @@ NAME SYNOPSIS gcloud alpha iam policies update POLICY_ID --attachment-point=ATTACHMENT_POINT --kind=KIND - --policy-file=POLICY_FILE [GCLOUD_WIDE_FLAG ...] + --policy-file=POLICY_FILE [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update the policy on the given attachment point with the given name. EXAMPLES - The following command updates the IAM policy defined at the resource - project 123 of kind denypolicies and id my-deny-policy: + The following command updates the IAM policy my-deny-policy, which is + attached to the resource project 123 and has the etag abc: $ gcloud alpha iam policies update my-deny-policy \ --attachment-point=cloudresourcemanager.googleapis.com/\ - projects/123 --kind=denypolicies --policy-file=policy.json + projects/123 --kind=denypolicies --policy-file=policy.json \ + --etag=abc POSITIONAL ARGUMENTS POLICY_ID @@ -36,6 +37,14 @@ REQUIRED FLAGS Path to the file that contains the policy, in JSON or YAML format. For valid syntax, see https://cloud.google.com/iam/help/deny/policy-syntax. +OPTIONAL FLAGS + --etag=ETAG + Etag that identifies the version of the existing policy. It can be + obtained by running gcloud iam policies get. When deleting a policy, if + the etag is omitted, the policy is deleted regardless of its current + etag. When updating a policy, if the etag is omitted, the update uses + the etag provided in the policy file. + 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/iap/settings/get b/gcloud/alpha/iap/settings/get index 96ff11449..dd1fcff5f 100644 --- a/gcloud/alpha/iap/settings/get +++ b/gcloud/alpha/iap/settings/get @@ -49,18 +49,19 @@ EXAMPLES To get the IAP setting for all backend services within a project, run: $ gcloud alpha iap settings get --project=PROJECT_ID \ - --resource-type=compute + --resource-type=backend-services To get the IAP setting for a backend service within a project, run: $ gcloud alpha iap settings get --project=PROJECT_ID \ - --resource-type=compute --service=SERVICE_ID + --resource-type=backend-services --service=SERVICE_ID To get the IAP setting for a regional backend service within a project, run: $ gcloud alpha iap settings get --project=PROJECT_ID \ - --resource-type=compute --service=SERVICE_ID --region=REGION_ID + --resource-type=backend-services --service=SERVICE_ID \ + --region=REGION_ID FLAGS --folder=FOLDER @@ -80,8 +81,10 @@ FLAGS --resource-type=RESOURCE_TYPE Resource type of the IAP resource. --resource-type=cloud-run is private priview feature and reach out to cloud-run team if you want to test it. - RESOURCE_TYPE must be one of: app-engine, iap_web, compute, - organization, folder, forwarding-rule, cloud-run. + For Backend Services, you can use both compute and backend-services as + resource type. RESOURCE_TYPE must be one of: app-engine, iap_web, + compute, organization, folder, forwarding-rule, cloud-run, + backend-services. --service=SERVICE Service name. Optional when resource-type is compute or app-engine. diff --git a/gcloud/alpha/iap/settings/set b/gcloud/alpha/iap/settings/set index d37e3f543..df7d84b5f 100644 --- a/gcloud/alpha/iap/settings/set +++ b/gcloud/alpha/iap/settings/set @@ -52,18 +52,18 @@ EXAMPLES To set the IAP setting for all backend services within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=compute + --project=PROJECT_ID --resource-type=backend-services To set the IAP setting for a backend service within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=compute \ + --project=PROJECT_ID --resource-type=backend-services \ --service=SERVICE_ID To set the IAP setting for a region backend service within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=compute \ + --project=PROJECT_ID --resource-type=backend-services \ --service=SERVICE_ID --region=REGION_ID POSITIONAL ARGUMENTS @@ -132,8 +132,10 @@ FLAGS --resource-type=RESOURCE_TYPE Resource type of the IAP resource. --resource-type=cloud-run is private priview feature and reach out to cloud-run team if you want to test it. - RESOURCE_TYPE must be one of: app-engine, iap_web, compute, - organization, folder, forwarding-rule, cloud-run. + For Backend Services, you can use both compute and backend-services as + resource type. RESOURCE_TYPE must be one of: app-engine, iap_web, + compute, organization, folder, forwarding-rule, cloud-run, + backend-services. --service=SERVICE Service name. Optional when resource-type is compute or app-engine. diff --git a/gcloud/alpha/managed-flink/deployments/create b/gcloud/alpha/managed-flink/deployments/create index 1a7ae028d..adeba185f 100644 --- a/gcloud/alpha/managed-flink/deployments/create +++ b/gcloud/alpha/managed-flink/deployments/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha managed-flink deployments create (DEPLOYMENT : --location=LOCATION) --max-slots=MAX_SLOTS [--async] - [--display-name=DISPLAY_NAME] + [--display-name=DISPLAY_NAME] [--workload-identity=WORKLOAD_IDENTITY] [--network-config-subnetwork=NETWORK_CONFIG_SUBNETWORK --network-config-vpc=NETWORK_CONFIG_VPC] [GCLOUD_WIDE_FLAG ...] @@ -72,6 +72,10 @@ OPTIONAL FLAGS --display-name=DISPLAY_NAME display name of the Flink deployment. + --workload-identity=WORKLOAD_IDENTITY + The workload identity to use for the deployment. Managed Flink Default + Workload Identity will be used if not specified. + --network-config-subnetwork=NETWORK_CONFIG_SUBNETWORK subnetwork for the Flink deployment network config. diff --git a/gcloud/alpha/managed-flink/jobs/create b/gcloud/alpha/managed-flink/jobs/create index a9461e79d..cc942095f 100644 --- a/gcloud/alpha/managed-flink/jobs/create +++ b/gcloud/alpha/managed-flink/jobs/create @@ -11,7 +11,8 @@ SYNOPSIS [--max-parallelism=MAX_PARALLELISM] [--min-parallelism=MIN_PARALLELISM] [--name=NAME] [--network-config-subnetwork=SUBNETWORK] [--network-config-vpc=NETWORK] [--parallelism=PARALLELISM] - [--python-venv=ZIP] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] + [--python-venv=ZIP] [--workload-identity=WORKLOAD_IDENTITY] + [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] DESCRIPTION (ALPHA) Create a Flink job from a Java jar. @@ -108,6 +109,10 @@ OTHER FLAGS dependencies. Required if the job type is python. Must start with gs://. + --workload-identity=WORKLOAD_IDENTITY + The workload identity to use for the job. Managed Flink Default + Workload Identity will be used if not specified. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/migration/vms/machine-image-imports/create b/gcloud/alpha/migration/vms/machine-image-imports/create index 168d5fe26..2953c5ed0 100644 --- a/gcloud/alpha/migration/vms/machine-image-imports/create +++ b/gcloud/alpha/migration/vms/machine-image-imports/create @@ -6,8 +6,9 @@ SYNOPSIS gcloud alpha migration vms machine-image-imports create (IMAGE_IMPORT_NAME : --location=LOCATION) --source-file=SOURCE_FILE [--additional-licenses=[ADDITIONAL_LICENSES,...]] - [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--machine-image-name=MACHINE_IMAGE_NAME] [--machine-type=MACHINE_TYPE] + [--description=DESCRIPTION] [--kms-key=KMS_KEY] + [--labels=[KEY=VALUE,...]] [--machine-image-name=MACHINE_IMAGE_NAME] + [--machine-type=MACHINE_TYPE] [--network-interface=[network=NETWORK], [networkTier=NETWORKTIER],[subnetwork=SUBNETWORK]] [--single-region-storage] [--tags=[TAGS,...]] @@ -83,6 +84,10 @@ OPTIONAL FLAGS --description=DESCRIPTION A description of the machine image. + --kms-key=KMS_KEY + Fully qualified identifier for the Cloud KMS (Key Management Service) + cryptokey that will be used to protect the image. + --labels=[KEY=VALUE,...] A map of labels to associate with the machine image. diff --git a/gcloud/alpha/network-security/intercept-deployment-groups/create b/gcloud/alpha/network-security/intercept-deployment-groups/create index f8e54dc45..14e7b1a68 100644 --- a/gcloud/alpha/network-security/intercept-deployment-groups/create +++ b/gcloud/alpha/network-security/intercept-deployment-groups/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha network-security intercept-deployment-groups create (INTERCEPT_DEPLOYMENT_GROUP : --location=LOCATION) --network=NETWORK - [--async] [--labels=[KEY=VALUE,...]] + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -35,6 +35,14 @@ EXAMPLES my-deployment-group \ --network=projects/my-project/global/networks/my-network + OR + + $ gcloud alpha network-security intercept-deployment-groups create \ + projects/my-project/locations/global/interceptDeploymentGroups/\ + my-deployment-group \ + --network=projects/my-project/global/networks/my-network \ + --description='new description' + POSITIONAL ARGUMENTS Intercept deployment group resource - Intercept Deployment Group. The arguments in this group can be used to specify the attributes of this @@ -93,6 +101,9 @@ OPTIONAL FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --description=DESCRIPTION + Description of the deployment group. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/alpha/network-security/intercept-deployment-groups/update b/gcloud/alpha/network-security/intercept-deployment-groups/update index 40517c0bc..5a12b773a 100644 --- a/gcloud/alpha/network-security/intercept-deployment-groups/update +++ b/gcloud/alpha/network-security/intercept-deployment-groups/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha network-security intercept-deployment-groups update (INTERCEPT_DEPLOYMENT_GROUP : --location=LOCATION) [--async] - [--max-wait=MAX_WAIT; default="20m"] [--update-labels=[KEY=VALUE,...]] + [--description=DESCRIPTION] [--max-wait=MAX_WAIT; default="20m"] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -34,6 +35,12 @@ EXAMPLES my-deployment-group --project=my-project --location=global \ --clear-labels + To update description to 'new description', run: + + $ gcloud alpha network-security intercept-deployment-groups update \ + my-deployment-group --project=my-project --location=global \ + --description='new description' + POSITIONAL ARGUMENTS Intercept deployment group resource - Intercept Deployment Group. The arguments in this group can be used to specify the attributes of this @@ -73,6 +80,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --description=DESCRIPTION + Description of the deployment group. + --max-wait=MAX_WAIT; default="20m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/alpha/network-security/intercept-deployments/create b/gcloud/alpha/network-security/intercept-deployments/create index 2630da387..cbb152e89 100644 --- a/gcloud/alpha/network-security/intercept-deployments/create +++ b/gcloud/alpha/network-security/intercept-deployments/create @@ -9,7 +9,7 @@ SYNOPSIS : --forwarding-rule-location=FORWARDING_RULE_LOCATION) (--intercept-deployment-group=INTERCEPT_DEPLOYMENT_GROUP : --intercept-deployment-group-location=INTERCEPT_DEPLOYMENT_GROUP_LOCATION) - [--async] [--labels=[KEY=VALUE,...]] + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -47,6 +47,17 @@ EXAMPLES --intercept-deployment-group=projects/my-project/locations/\ global/interceptDeploymentGroups/my-deployment-group + OR + + $ gcloud alpha network-security intercept-deployments create \ + projects/my-project/locations/us-central1/interceptDeployments/\ + my-deployment \ + --forwarding-rule=projects/my-project/regions/us-central1/\ + forwardingRules/my-forwarding-rule \ + --intercept-deployment-group=projects/my-project/locations/\ + global/interceptDeploymentGroups/my-deployment-group \ + --description="my-description" + POSITIONAL ARGUMENTS Intercept deployment resource - Intercept Deployment. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -155,6 +166,9 @@ OPTIONAL FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --description=DESCRIPTION + Description of the deployment. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/alpha/network-security/intercept-deployments/update b/gcloud/alpha/network-security/intercept-deployments/update index e9abcb8b9..9b1402b95 100644 --- a/gcloud/alpha/network-security/intercept-deployments/update +++ b/gcloud/alpha/network-security/intercept-deployments/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha network-security intercept-deployments update (INTERCEPT_DEPLOYMENT : --location=LOCATION) [--async] - [--max-wait=MAX_WAIT; default="20m"] [--update-labels=[KEY=VALUE,...]] + [--description=DESCRIPTION] [--max-wait=MAX_WAIT; default="20m"] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -33,6 +34,12 @@ EXAMPLES my-deploymen --project=my-project --location=us-central1-a \ --clear-labels + To update description to 'new description', run: + + $ gcloud alpha network-security intercept-deployments update \ + my-deploymen --project=my-project --location=us-central1-a \ + --description="new description" + POSITIONAL ARGUMENTS Intercept deployment resource - Intercept Deployment. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -71,6 +78,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --description=DESCRIPTION + Description of the deployment. + --max-wait=MAX_WAIT; default="20m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/alpha/network-security/mirroring-deployment-groups/create b/gcloud/alpha/network-security/mirroring-deployment-groups/create index 8b5f4bb9c..130c53d7b 100644 --- a/gcloud/alpha/network-security/mirroring-deployment-groups/create +++ b/gcloud/alpha/network-security/mirroring-deployment-groups/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha network-security mirroring-deployment-groups create (MIRRORING_DEPLOYMENT_GROUP : --location=LOCATION) --network=NETWORK - [--async] [--labels=[KEY=VALUE,...]] + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -35,6 +35,14 @@ EXAMPLES my-deployment-group \ --network=projects/my-project/global/networks/my-network + OR + + $ gcloud alpha network-security mirroring-deployment-groups create \ + projects/my-project/locations/global/mirroringDeploymentGroups/\ + my-deployment-group \ + --network=projects/my-project/global/networks/my-network \ + --description="my-description" + POSITIONAL ARGUMENTS Mirroring deployment group resource - Mirroring Deployment Group. The arguments in this group can be used to specify the attributes of this @@ -93,6 +101,9 @@ OPTIONAL FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --description=DESCRIPTION + Description of the mirroring deployment group + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/alpha/network-security/mirroring-deployment-groups/update b/gcloud/alpha/network-security/mirroring-deployment-groups/update index fe6d0a617..115244a87 100644 --- a/gcloud/alpha/network-security/mirroring-deployment-groups/update +++ b/gcloud/alpha/network-security/mirroring-deployment-groups/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha network-security mirroring-deployment-groups update (MIRRORING_DEPLOYMENT_GROUP : --location=LOCATION) [--async] - [--max-wait=MAX_WAIT; default="20m"] [--update-labels=[KEY=VALUE,...]] + [--description=DESCRIPTION] [--max-wait=MAX_WAIT; default="20m"] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -34,6 +35,12 @@ EXAMPLES my-deployment-group --project=my-project --location=global \ --clear-labels + To update description to 'new description', run: + + $ gcloud alpha network-security mirroring-deployment-groups update \ + my-deployment-group --project=my-project --location=global \ + --description="new description" + POSITIONAL ARGUMENTS Mirroring deployment group resource - Mirroring Deployment Group. The arguments in this group can be used to specify the attributes of this @@ -73,6 +80,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --description=DESCRIPTION + Description of the mirroring deployment group + --max-wait=MAX_WAIT; default="20m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/alpha/network-security/mirroring-deployments/create b/gcloud/alpha/network-security/mirroring-deployments/create index 5b3902de4..a7487959d 100644 --- a/gcloud/alpha/network-security/mirroring-deployments/create +++ b/gcloud/alpha/network-security/mirroring-deployments/create @@ -9,7 +9,7 @@ SYNOPSIS : --forwarding-rule-location=FORWARDING_RULE_LOCATION) (--mirroring-deployment-group=MIRRORING_DEPLOYMENT_GROUP : --mirroring-deployment-group-location=MIRRORING_DEPLOYMENT_GROUP_LOCATION) - [--async] [--labels=[KEY=VALUE,...]] + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -47,6 +47,17 @@ EXAMPLES --mirroring-deployment-group=projects/my-project/locations/\ global/mirroringDeploymentGroups/my-deployment-group + OR + + $ gcloud alpha network-security mirroring-deployments create \ + projects/my-project/locations/us-central1/mirroringDeployments/\ + my-deployment \ + --forwarding-rule=projects/my-project/regions/us-central1/\ + forwardingRules/my-forwarding-rule \ + --mirroring-deployment-group=projects/my-project/locations/\ + global/mirroringDeploymentGroups/my-deployment-group \ + --description="my-description" + POSITIONAL ARGUMENTS Mirroring deployment resource - Mirroring Deployment. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -155,6 +166,9 @@ OPTIONAL FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --description=DESCRIPTION + Description of the mirroring deployment + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/alpha/network-security/mirroring-deployments/update b/gcloud/alpha/network-security/mirroring-deployments/update index 73f13dffd..62d9c6aba 100644 --- a/gcloud/alpha/network-security/mirroring-deployments/update +++ b/gcloud/alpha/network-security/mirroring-deployments/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha network-security mirroring-deployments update (MIRRORING_DEPLOYMENT : --location=LOCATION) [--async] - [--max-wait=MAX_WAIT; default="20m"] [--update-labels=[KEY=VALUE,...]] + [--description=DESCRIPTION] [--max-wait=MAX_WAIT; default="20m"] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -33,6 +34,12 @@ EXAMPLES my-deploymen --project=my-project --location=us-central1-a \ --clear-labels + To update description to 'new description', run: + + $ gcloud alpha network-security mirroring-deployments update \ + my-deploymen --project=my-project --location=us-central1-a \ + --description="new description" + POSITIONAL ARGUMENTS Mirroring deployment resource - Mirroring Deployment. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -71,6 +78,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --description=DESCRIPTION + Description of the mirroring deployment + --max-wait=MAX_WAIT; default="20m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/alpha/network-security/security-profiles/export b/gcloud/alpha/network-security/security-profiles/export new file mode 100644 index 000000000..f704bb47d --- /dev/null +++ b/gcloud/alpha/network-security/security-profiles/export @@ -0,0 +1,79 @@ +NAME + gcloud alpha network-security security-profiles export - export Security + Profile + +SYNOPSIS + gcloud alpha network-security security-profiles export + (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) + [--destination=DESTINATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Export a Security Profile. + +EXAMPLES + To export a Security Profile, run: + + $ gcloud alpha network-security security-profiles export \ + my-security-profile --organization=1234 --location=global \ + --destination=my-security-profile.yaml + +POSITIONAL ARGUMENTS + Security profile resource - Name of the Security Profile to export. The + arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + SECURITY_PROFILE + ID of the security_profile or fully qualified identifier for the + security_profile. + + To set the security_profile attribute: + ▸ provide the argument security_profile on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ use default global location . + + --organization=ORGANIZATION + Organization number. + + To set the organization attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. + +FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. The + exported data will not contain any output-only fields. Alternatively, + you may omit this flag to write to standard output. For a schema + describing the export/import format, see + $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + +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 networksecurity/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/network-security/security-profiles/help b/gcloud/alpha/network-security/security-profiles/help index d6e3a0421..ca75c260c 100644 --- a/gcloud/alpha/network-security/security-profiles/help +++ b/gcloud/alpha/network-security/security-profiles/help @@ -32,6 +32,12 @@ COMMANDS describe (ALPHA) Describe a Security Profile. + export + (ALPHA) Export Security Profile. + + list + (ALPHA) List Security Profiles. + 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/network-security/security-profiles/list b/gcloud/alpha/network-security/security-profiles/list new file mode 100644 index 000000000..4b6f5503e --- /dev/null +++ b/gcloud/alpha/network-security/security-profiles/list @@ -0,0 +1,93 @@ +NAME + gcloud alpha network-security security-profiles list - list Security + Profiles + +SYNOPSIS + gcloud alpha network-security security-profiles list + (--location=LOCATION : --organization=ORGANIZATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all Security Profiles in the specified location. + +EXAMPLES + To list Security Profiles in specifed location, run: + + $ gcloud alpha network-security security-profiles list \ + --location=global + +REQUIRED FLAGS + Location resource - The location of Security Profiles to display. The + arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --organization=ORGANIZATION + Organization number. + + To set the organization attribute: + ▸ provide the argument --location on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networksecurity/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/add-override b/gcloud/alpha/network-security/security-profiles/threat-prevention/add-override index 95e57bfae..ae3d29895 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/add-override +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/add-override @@ -7,15 +7,16 @@ SYNOPSIS add-override (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) --action=ACTION - (--severities=[SEVERITY_LEVEL,...] | --threat-ids=[THREAT-ID,...]) - [--async] [--update-labels=[KEY=VALUE,...]] + (--antivirus=[PROTOCOL,...] | --severities=[SEVERITY_LEVEL,...] + | --threat-ids=[THREAT-ID,...]) [--async] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Add severities or threat-ids to existing threat prevention profile - with intended action on each specified. Check the updates of add-override - command by using gcloud network-security security-profiles - threat-prevention list-override my-security-profile. + (ALPHA) Add antivirus, severities, or threat-ids to existing threat + prevention profile with intended action on each specified. Check the + updates of add-override command by using gcloud network-security + security-profiles threat-prevention list-override my-security-profile. For more examples, refer to the EXAMPLES section below. @@ -66,11 +67,15 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --action=ACTION - Action associated with severity or threat-id. ACTION must be one of: - DEFAULT_ACTION, ALLOW, ALERT, DENY. + Action associated with antivirus, severity, or threat-id. ACTION must + be one of: DEFAULT_ACTION, ALLOW, ALERT, DENY. Exactly one of these must be specified: + --antivirus=[PROTOCOL,...] + List of comma-separated protocols where each value in the list + indicates the protocol of the antivirus threat. + --severities=[SEVERITY_LEVEL,...] List of comma-separated severities where each value in the list indicates the severity of the threat. diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/delete-override b/gcloud/alpha/network-security/security-profiles/threat-prevention/delete-override index c9796871f..80fa7a210 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/delete-override +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/delete-override @@ -6,14 +6,15 @@ SYNOPSIS gcloud alpha network-security security-profiles threat-prevention delete-override (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) - (--severities=[SEVERITY_LEVEL,...] | --threat-ids=[THREAT-ID,...]) - [--async] [--update-labels=[KEY=VALUE,...]] + (--antivirus=[PROTOCOL,...] | --severities=[SEVERITY_LEVEL,...] + | --threat-ids=[THREAT-ID,...]) [--async] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) To delete existing severities or threat-ids of threat prevention - profile. Check the updates of update-override command by using gcloud - network-security security-profiles threat-prevention list-override + (ALPHA) To delete existing antivirus, severities, or threat-ids of threat + prevention profile. Check the updates of update-override command by using + gcloud network-security security-profiles threat-prevention list-override my-security-profile. For more examples, refer to the EXAMPLES section below. @@ -66,6 +67,10 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Exactly one of these must be specified: + --antivirus=[PROTOCOL,...] + List of comma-separated protocols where each value in the list + indicates the protocol of the antivirus threat. + --severities=[SEVERITY_LEVEL,...] List of comma-separated severities where each value in the list indicates the severity of the threat. diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/list-overrides b/gcloud/alpha/network-security/security-profiles/threat-prevention/list-overrides index f495d24bb..d4c046d02 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/list-overrides +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/list-overrides @@ -9,8 +9,8 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) To list existing severities or threat-ids of threat prevention - profile. + (ALPHA) To list existing antivirus, severities, or threat-ids of threat + prevention profile. For more examples, refer to the EXAMPLES section below. diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/update-override b/gcloud/alpha/network-security/security-profiles/threat-prevention/update-override index b9933ff3d..326839520 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/update-override +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/update-override @@ -7,15 +7,16 @@ SYNOPSIS update-override (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) --action=ACTION - (--severities=[SEVERITY_LEVEL,...] | --threat-ids=[THREAT-ID,...]) - [--async] [--update-labels=[KEY=VALUE,...]] + (--antivirus=[PROTOCOL,...] | --severities=[SEVERITY_LEVEL,...] + | --threat-ids=[THREAT-ID,...]) [--async] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) To update existing severities or threat-ids of threat prevention - profile with intended action on each specified. Check the updates of - update-override command by using gcloud network-security security-profiles - threat-prevention list-override my-security-profile. + (ALPHA) To update existing antivirus, severities, or threat-ids of threat + prevention profile with intended action on each specified. Check the + updates of update-override command by using gcloud network-security + security-profiles threat-prevention list-override my-security-profile. For more examples, refer to the EXAMPLES section below. @@ -66,11 +67,15 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --action=ACTION - Action associated with severity or threat-id. ACTION must be one of: - DEFAULT_ACTION, ALLOW, ALERT, DENY. + Action associated with antivirus, severity, or threat-id. ACTION must + be one of: DEFAULT_ACTION, ALLOW, ALERT, DENY. Exactly one of these must be specified: + --antivirus=[PROTOCOL,...] + List of comma-separated protocols where each value in the list + indicates the protocol of the antivirus threat. + --severities=[SEVERITY_LEVEL,...] List of comma-separated severities where each value in the list indicates the severity of the threat. diff --git a/gcloud/alpha/network-services/multicast-domains/create b/gcloud/alpha/network-services/multicast-domains/create index f97061d2c..71b52b1f6 100644 --- a/gcloud/alpha/network-services/multicast-domains/create +++ b/gcloud/alpha/network-services/multicast-domains/create @@ -8,6 +8,7 @@ SYNOPSIS (--connection-type=CONNECTION_TYPE; default="CONNECTION_TYPE_UNSPECIFIED" --ncc-hub=NCC_HUB) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--multicast-domain-group=MULTICAST_DOMAIN_GROUP] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -94,6 +95,9 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --multicast-domain-group=MULTICAST_DOMAIN_GROUP + The URI of the multicast domain group to be used. + 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/redis/clusters/get-cluster-certificate-authority b/gcloud/alpha/redis/clusters/get-cluster-certificate-authority index f666146f3..ee4cc8390 100644 --- a/gcloud/alpha/redis/clusters/get-cluster-certificate-authority +++ b/gcloud/alpha/redis/clusters/get-cluster-certificate-authority @@ -17,7 +17,7 @@ DESCRIPTION cluster. EXAMPLES - To get the metadata for a cluster with the name my-redie-cluster in the + To get the metadata for a cluster with the name my-redis-cluster in the default region, run: $ gcloud alpha redis clusters get-cluster-certificate-authority \ diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index d066d5029..cb177ba3e 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -47,7 +47,7 @@ SYNOPSIS --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...] --command=[COMMAND,...] - | --function=FUNCTION --image=IMAGE | --source=SOURCE] + | --function=FUNCTION --image=IMAGE --source=SOURCE] [--binary-authorization=POLICY | --clear-binary-authorization] [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] @@ -654,27 +654,28 @@ FLAGS Specifies that the deployed object is a function. If a value is provided, that value is used as the entrypoint. - At most one of these can be specified: + --image=IMAGE + Name of the container image to deploy (e.g. + us-docker.pkg.dev/cloudrun/container/hello:latest). When used with + --source, the image must be the URI of an Artifact Registry Docker + repository in the Docker format + ($REGION-docker.pkg.dev/$PROJECT/$REPOSITORY"). - --image=IMAGE - Name of the container image to deploy (e.g. - us-docker.pkg.dev/cloudrun/container/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. + --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: diff --git a/gcloud/alpha/workstations/configs/create b/gcloud/alpha/workstations/configs/create index a208459ab..a8f58dbaa 100644 --- a/gcloud/alpha/workstations/configs/create +++ b/gcloud/alpha/workstations/configs/create @@ -14,10 +14,11 @@ SYNOPSIS [--container-env=[CONTAINER_ENV,...]] [--container-run-as-user=CONTAINER_RUN_AS_USER] [--container-working-dir=CONTAINER_WORKING_DIR] - [--disable-public-ip-addresses] [--disable-ssh-to-vm] - [--disable-tcp-connections] [--enable-audit-agent] - [--enable-confidential-compute] [--enable-nested-virtualization] - [--enable-ssh-to-vm] [--ephemeral-directory=[PROPERTY=VALUE,...]] + [--disable-localhost-replacement] [--disable-public-ip-addresses] + [--disable-ssh-to-vm] [--disable-tcp-connections] + [--enable-audit-agent] [--enable-confidential-compute] + [--enable-nested-virtualization] [--enable-ssh-to-vm] + [--ephemeral-directory=[PROPERTY=VALUE,...]] [--grant-workstation-admin-role-on-create] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] @@ -231,6 +232,13 @@ FLAGS --container-working-dir=CONTAINER_WORKING_DIR If set, overrides the default DIR specified by the image. + --disable-localhost-replacement + By default, the workstations service replaces references to localhost, + 127.0.0.1, and 0.0.0.0 with the workstation's hostname in http + responses from the workstation so that applications under development + run properly on the workstation. This may intefere with some + applications, and so this option allows that behavior to be disabled. + --disable-public-ip-addresses Default value is false. If set, instances will have no public IP address. diff --git a/gcloud/alpha/workstations/configs/update b/gcloud/alpha/workstations/configs/update index 6eeab0abe..cacfe9258 100644 --- a/gcloud/alpha/workstations/configs/update +++ b/gcloud/alpha/workstations/configs/update @@ -29,6 +29,7 @@ SYNOPSIS | --disallow-unauthenticated-cors-preflight-requests] [--container-custom-image=CONTAINER_CUSTOM_IMAGE | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE] + [--disable-localhost-replacement | --enable-localhost-replacement] [--disable-ssh-to-vm | --enable-ssh-to-vm] [--disable-tcp-connections | --enable-tcp-connections] [GCLOUD_WIDE_FLAG ...] @@ -370,6 +371,20 @@ FLAGS webstorm WebStorm + At most one of these can be specified: + + --disable-localhost-replacement + By default, the workstations service replaces references to + localhost, 127.0.0.1, and 0.0.0.0 with the workstation's hostname in + http responses from the workstation so that applications under + development run properly on the workstation. This may intefere with + some applications, and so this option allows that behavior to be + disabled. + + --enable-localhost-replacement + If set, requires that all requests to the workstation are + authenticated. + At most one of these can be specified: --disable-ssh-to-vm diff --git a/gcloud/assured/workloads/create b/gcloud/assured/workloads/create index a8978f011..e838a91c9 100644 --- a/gcloud/assured/workloads/create +++ b/gcloud/assured/workloads/create @@ -87,8 +87,8 @@ REQUIRED FLAGS The compliance regime of the new Assured Workloads environment. COMPLIANCE_REGIME must be one of: assured-workloads-for-partners, au-regions-and-us-support, ca-protected-b, ca-regions-and-support, - cjis, eu-regions-and-support, fedramp-high, fedramp-moderate, - healthcare-and-life-sciences-controls, + canada-controlled-goods, cjis, eu-regions-and-support, fedramp-high, + fedramp-moderate, healthcare-and-life-sciences-controls, healthcare-and-life-sciences-controls-us-support, hipaa, hitrust, il2, il4, il5, irs-1075, isr-regions, isr-regions-and-support, itar, jp-regions-and-support, diff --git a/gcloud/auth/application-default/login b/gcloud/auth/application-default/login index aab9e6647..24f5c489f 100644 --- a/gcloud/auth/application-default/login +++ b/gcloud/auth/application-default/login @@ -52,7 +52,7 @@ POSITIONAL ARGUMENTS credentials. FLAGS - --no-browser + --browser If you want to authorize the client libraries on a machine that doesn't have a browser and you can install the gcloud CLI on another machine with a browser, use the --no-browser flag. @@ -74,6 +74,8 @@ FLAGS "Enter the output of the above command", and press Enter to complete the authorization. + Enabled by default, use --no-browser to disable. + --client-id-file=CLIENT_ID_FILE A file containing your own client id to use to login. If --client-id-file is specified, the quota project will not be written to diff --git a/gcloud/auth/login b/gcloud/auth/login index 69fac3bcb..9a0634ab8 100644 --- a/gcloud/auth/login +++ b/gcloud/auth/login @@ -77,7 +77,7 @@ FLAGS --brief Minimal user output. - --no-browser + --browser If you want to authorize the gcloud CLI on a machine that doesn't have a browser and you can install the gcloud CLI on another machine with a browser, use the --no-browser flag. @@ -99,6 +99,8 @@ FLAGS "Enter the output of the above command", and press Enter to complete the authorization. + Enabled by default, use --no-browser to disable. + --cred-file=CRED_FILE Path to the external account configuration file (workload identity pool, generated by the Cloud Console or gcloud iam diff --git a/gcloud/beta/assured/workloads/create b/gcloud/beta/assured/workloads/create index 06fad3e1d..1cf18171a 100644 --- a/gcloud/beta/assured/workloads/create +++ b/gcloud/beta/assured/workloads/create @@ -87,8 +87,8 @@ REQUIRED FLAGS The compliance regime of the new Assured Workloads environment. COMPLIANCE_REGIME must be one of: assured-workloads-for-partners, au-regions-and-us-support, ca-protected-b, ca-regions-and-support, - cjis, eu-regions-and-support, fedramp-high, fedramp-moderate, - healthcare-and-life-sciences-controls, + canada-controlled-goods, cjis, eu-regions-and-support, fedramp-high, + fedramp-moderate, healthcare-and-life-sciences-controls, healthcare-and-life-sciences-controls-us-support, hipaa, hitrust, il2, il4, il5, irs-1075, isr-regions, isr-regions-and-support, itar, jp-regions-and-support, diff --git a/gcloud/beta/auth/application-default/login b/gcloud/beta/auth/application-default/login index eaeec0018..4d6d26b7a 100644 --- a/gcloud/beta/auth/application-default/login +++ b/gcloud/beta/auth/application-default/login @@ -52,7 +52,7 @@ POSITIONAL ARGUMENTS credentials. FLAGS - --no-browser + --browser If you want to authorize the client libraries on a machine that doesn't have a browser and you can install the gcloud CLI on another machine with a browser, use the --no-browser flag. @@ -74,6 +74,8 @@ FLAGS "Enter the output of the above command", and press Enter to complete the authorization. + Enabled by default, use --no-browser to disable. + --client-id-file=CLIENT_ID_FILE A file containing your own client id to use to login. If --client-id-file is specified, the quota project will not be written to diff --git a/gcloud/beta/auth/login b/gcloud/beta/auth/login index faca12aae..b4ce06373 100644 --- a/gcloud/beta/auth/login +++ b/gcloud/beta/auth/login @@ -77,7 +77,7 @@ FLAGS --brief Minimal user output. - --no-browser + --browser If you want to authorize the gcloud CLI on a machine that doesn't have a browser and you can install the gcloud CLI on another machine with a browser, use the --no-browser flag. @@ -99,6 +99,8 @@ FLAGS "Enter the output of the above command", and press Enter to complete the authorization. + Enabled by default, use --no-browser to disable. + --cred-file=CRED_FILE Path to the external account configuration file (workload identity pool, generated by the Cloud Console or gcloud iam diff --git a/gcloud/beta/billing/budgets/create b/gcloud/beta/billing/budgets/create index 93f1695dc..db259ec13 100644 --- a/gcloud/beta/billing/budgets/create +++ b/gcloud/beta/billing/budgets/create @@ -164,25 +164,31 @@ OPTIONAL FLAGS Must be one of: 'current-spend' or 'forecasted-spend'. Behavior defaults to 'current-spend' if not set. + Specify either the calendar-period or custom-period, not both. + At most one of these can be specified: - --calendar-period=CALENDAR_PERIOD - Specifies to track usage over recurring calendar period. If you're - creating a budget with a custom time period, omit this flag. - CALENDAR_PERIOD must be one of: calendar-period-unspecified, month, - quarter, year. + Calendar Period - --start-date=START_DATE - Specifies to track usage after any start date. This time period is - static, it does not recur. + --calendar-period=CALENDAR_PERIOD + Specified to track usage over recurring calendar period. If you're + creating a budget with a custom time period, omit this flag. + CALENDAR_PERIOD must be one of: calendar-period-unspecified, month, + quarter, year. - This flag argument must be specified if any of the other arguments in - this group are specified. + Custom Period - --end-date=END_DATE - Specifies to track usage before any end date. This time period is - static, it does not recur. If specified, --start-date must also be - specified. + --start-date=START_DATE + Specified to track usage after any start date. This time period is + static, it does not recur. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --end-date=END_DATE + Specified to track usage before any end date. This time period is + static, it does not recur. If specified, --start-date must also be + specified. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/billing/budgets/update b/gcloud/beta/billing/budgets/update index 34a2adabf..f1317b85e 100644 --- a/gcloud/beta/billing/budgets/update +++ b/gcloud/beta/billing/budgets/update @@ -158,25 +158,31 @@ FLAGS --last-period-amount Use the amount of last period's budget. + Specify either the calendar-period or custom-period, not both. + At most one of these can be specified: - --calendar-period=CALENDAR_PERIOD - Specifies to track usage over recurring calendar period. If you're - creating a budget with a custom time period, omit this flag. - CALENDAR_PERIOD must be one of: calendar-period-unspecified, month, - quarter, year. + Calendar Period - --start-date=START_DATE - Specifies to track usage after any start date. This time period is - static, it does not recur. + --calendar-period=CALENDAR_PERIOD + Specified to track usage over recurring calendar period. If you're + creating a budget with a custom time period, omit this flag. + CALENDAR_PERIOD must be one of: calendar-period-unspecified, month, + quarter, year. - This flag argument must be specified if any of the other arguments in - this group are specified. + Custom Period - --end-date=END_DATE - Specifies to track usage before any end date. This time period is - static, it does not recur. If specified, --start-date must also be - specified. + --start-date=START_DATE + Specified to track usage after any start date. This time period is + static, it does not recur. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --end-date=END_DATE + Specified to track usage before any end date. This time period is + static, it does not recur. If specified, --start-date must also be + specified. At most one of these can be specified: diff --git a/gcloud/beta/builds/worker-pools/create b/gcloud/beta/builds/worker-pools/create index 8df67d4ec..60de6a6f9 100644 --- a/gcloud/beta/builds/worker-pools/create +++ b/gcloud/beta/builds/worker-pools/create @@ -121,7 +121,7 @@ FLAGS --worker-disk-size=WORKER_DISK_SIZE Size of the disk attached to the worker. - If not given, Cloud Build will use a standard disk size. + If unspecified, Cloud Build uses a standard disk size. --worker-machine-type=WORKER_MACHINE_TYPE Compute Engine machine type for a worker pool. diff --git a/gcloud/beta/builds/worker-pools/update b/gcloud/beta/builds/worker-pools/update index 2da938e7b..8b467de76 100644 --- a/gcloud/beta/builds/worker-pools/update +++ b/gcloud/beta/builds/worker-pools/update @@ -53,7 +53,7 @@ REQUIRED FLAGS --worker-disk-size=WORKER_DISK_SIZE Size of the disk attached to the worker. - If not given, Cloud Build will use a standard disk size. + If unspecified, Cloud Build uses a standard disk size. --worker-machine-type=WORKER_MACHINE_TYPE Compute Engine machine type for a worker pool. diff --git a/gcloud/beta/compute/instance-groups/managed/resume-instances b/gcloud/beta/compute/instance-groups/managed/resume-instances index 25c3ceebc..235706dd1 100644 --- a/gcloud/beta/compute/instance-groups/managed/resume-instances +++ b/gcloud/beta/compute/instance-groups/managed/resume-instances @@ -67,8 +67,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instance-groups managed resume-instances $ gcloud alpha compute instance-groups managed resume-instances diff --git a/gcloud/beta/compute/instance-groups/managed/start-instances b/gcloud/beta/compute/instance-groups/managed/start-instances index c506e73be..49c6248dd 100644 --- a/gcloud/beta/compute/instance-groups/managed/start-instances +++ b/gcloud/beta/compute/instance-groups/managed/start-instances @@ -67,8 +67,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instance-groups managed start-instances $ gcloud alpha compute instance-groups managed start-instances diff --git a/gcloud/beta/compute/instance-groups/managed/stop-instances b/gcloud/beta/compute/instance-groups/managed/stop-instances index dbf601239..1f67a2968 100644 --- a/gcloud/beta/compute/instance-groups/managed/stop-instances +++ b/gcloud/beta/compute/instance-groups/managed/stop-instances @@ -65,8 +65,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instance-groups managed stop-instances $ gcloud alpha compute instance-groups managed stop-instances diff --git a/gcloud/beta/compute/instance-groups/managed/suspend-instances b/gcloud/beta/compute/instance-groups/managed/suspend-instances index 5d2f8ab65..51964b31b 100644 --- a/gcloud/beta/compute/instance-groups/managed/suspend-instances +++ b/gcloud/beta/compute/instance-groups/managed/suspend-instances @@ -72,8 +72,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instance-groups managed suspend-instances $ gcloud alpha compute instance-groups managed suspend-instances diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index 1088c8b50..0b9a3f681 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -20,6 +20,8 @@ SYNOPSIS [device-name=DEVICE-NAME],[name=NAME],[scope=SCOPE]] [--enable-display-device] [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] [--erase-windows-vss-signature] + [--graceful-shutdown] + [--graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--labels=[KEY=VALUE,...]] @@ -447,6 +449,17 @@ OPTIONAL FLAGS machine image should erase Windows specific VSS signature. See https://cloud.google.com/sdk/gcloud/reference/compute/disks/snapshot#--guest-flush + --graceful-shutdown + Enables graceful shutdown for the instance. + + --graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION + Specifies the maximum time for the graceful shutdown. After this time, + the instance is set to STOPPING even if tasks are still running. + Specify the time as the number of hours, minutes, or seconds followed + by h, m, and s respectively. For example, specify 30m for 30 minutes or + 20m10s for 20 minutes and 10 seconds. The value must be between 1 + second and 1 hour. + --host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS The timeout in seconds for host error detection. The value must be set with 30 second increments, with a range of 90 to 330 seconds. If unset, diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index 6410ed86a..a93350211 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -32,6 +32,8 @@ SYNOPSIS [--[no-]enable-nested-virtualization] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] + [--graceful-shutdown] + [--graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] @@ -491,6 +493,17 @@ FLAGS be used together with --external-ipv6-address. Only the /96 IP address range is supported, and the default value is 96. + --graceful-shutdown + Enables graceful shutdown for the instance. + + --graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION + Specifies the maximum time for the graceful shutdown. After this time, + the instance is set to STOPPING even if tasks are still running. + Specify the time as the number of hours, minutes, or seconds followed + by h, m, and s respectively. For example, specify 30m for 30 minutes or + 20m10s for 20 minutes and 10 seconds. The value must be between 1 + second and 1 hour. + --host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS The timeout in seconds for host error detection. The value must be set with 30 second increments, with a range of 90 to 330 seconds. If unset, diff --git a/gcloud/beta/compute/interconnects/attachments/dedicated/create b/gcloud/beta/compute/interconnects/attachments/dedicated/create index 9c6a81216..ac60854b7 100644 --- a/gcloud/beta/compute/interconnects/attachments/dedicated/create +++ b/gcloud/beta/compute/interconnects/attachments/dedicated/create @@ -59,6 +59,8 @@ OPTIONAL FLAGS 20 Gbit/s 50g 50 Gbit/s + 100g + 100 Gbit/s --candidate-ipv6-subnets=[IPV6_SUBNET,...] The candididate-ipv6-subnets field is not available. diff --git a/gcloud/beta/compute/interconnects/attachments/dedicated/update b/gcloud/beta/compute/interconnects/attachments/dedicated/update index 42e71fe23..506e605c7 100644 --- a/gcloud/beta/compute/interconnects/attachments/dedicated/update +++ b/gcloud/beta/compute/interconnects/attachments/dedicated/update @@ -50,6 +50,8 @@ FLAGS 20 Gbit/s 50g 50 Gbit/s + 100g + 100 Gbit/s --candidate-ipv6-subnets=[IPV6_SUBNET,...] The candididate-ipv6-subnets field is not available. diff --git a/gcloud/beta/compute/org-security-policies/associations/create b/gcloud/beta/compute/org-security-policies/associations/create index ec69d90d0..3f3911f64 100644 --- a/gcloud/beta/compute/org-security-policies/associations/create +++ b/gcloud/beta/compute/org-security-policies/associations/create @@ -7,9 +7,10 @@ SYNOPSIS gcloud beta compute org-security-policies associations create --security-policy=SECURITY_POLICY [--excluded-folders=[EXCLUDED_FOLDERS,...]] - [--excluded-projects=[EXCLUDED_PROJECTS,...]] [--folder=FOLDER] - [--name=NAME] [--organization=ORGANIZATION] - [--replace-association-on-target] [GCLOUD_WIDE_FLAG ...] + [--excluded-projects=[EXCLUDED_PROJECTS,...]] [--name=NAME] + [--organization=ORGANIZATION] [--replace-association-on-target] + [--folder=FOLDER | --project-number=PROJECT_NUMBER] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute org-security-policies associations create is @@ -37,16 +38,13 @@ OPTIONAL FLAGS List of projects to exclude from the application of this security policy. Projects should be specified in the form "projects/123". - --folder=FOLDER - ID of the folder with which the association is created. - --name=NAME Name to identify this association. If unspecified, the name will be set to "organization-{ORGANIZATION_ID}" or "folder-{FOLDER_ID}". --organization=ORGANIZATION - ID of the organization in which the security policy is to be - associated. Must be set if SECURITY_POLICY is short name. + ID of the organization to associate the security policy with. Must be + set if SECURITY_POLICY is short name. --replace-association-on-target By default, if you attempt to insert an association to an organization @@ -54,6 +52,14 @@ OPTIONAL FLAGS the method will fail. If this is set, the existing association will be deleted at the same time that the new association is created. + At most one of these can be specified: + + --folder=FOLDER + ID of the folder to associate the security policy with. + + --project-number=PROJECT_NUMBER + Project number to associate the security policy with. + 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/compute/project-info/update b/gcloud/beta/compute/project-info/update index 24a599faa..6ca94619d 100644 --- a/gcloud/beta/compute/project-info/update +++ b/gcloud/beta/compute/project-info/update @@ -16,7 +16,7 @@ DESCRIPTION FLAGS --cloud-armor-tier=CLOUD_ARMOR_TIER Cloud armor tier to assign to the project. CLOUD_ARMOR_TIER must be one - of: CA_STANDARD, CA_ENTERPRISE_PAYGO. + of: CA_STANDARD, CA_ENTERPRISE_PAYGO, CA_ENTERPRISE_ANNUAL. --default-network-tier=DEFAULT_NETWORK_TIER The default network tier to assign to the project. DEFAULT_NETWORK_TIER @@ -24,7 +24,8 @@ FLAGS --managed-protection-tier=MANAGED_PROTECTION_TIER Managed protection tier to assign to the project. - MANAGED_PROTECTION_TIER must be one of: CA_STANDARD, CAMP_PLUS_PAYGO. + MANAGED_PROTECTION_TIER must be one of: CA_STANDARD, CAMP_PLUS_PAYGO, + CAMP_PLUS_ANNUAL. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/compute/routers/nats/create b/gcloud/beta/compute/routers/nats/create index 8493da700..540f28d1d 100644 --- a/gcloud/beta/compute/routers/nats/create +++ b/gcloud/beta/compute/routers/nats/create @@ -3,10 +3,7 @@ NAME router SYNOPSIS - gcloud beta compute routers nats create NAME --router=ROUTER - (--nat-all-subnet-ip-ranges - | --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] - | --nat-primary-subnet-ip-ranges) [--async] + gcloud beta compute routers nats create NAME --router=ROUTER [--async] [--auto-network-tier=AUTO_NETWORK_TIER] [--[no-]enable-dynamic-port-allocation] [--enable-endpoint-independent-mapping] [--enable-logging] @@ -20,6 +17,11 @@ SYNOPSIS [--type=TYPE] [--udp-idle-timeout=UDP_IDLE_TIMEOUT] [--auto-allocate-nat-external-ips | --nat-external-ip-pool=IP_ADDRESS,[IP_ADDRESS,...]] + [--nat-all-subnet-ip-ranges + | --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] + | --nat-primary-subnet-ip-ranges] + [--nat64-all-v6-subnet-ip-ranges + | --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -57,28 +59,6 @@ REQUIRED FLAGS --router=ROUTER The Router to use for NAT. - Exactly one of these must be specified: - - --nat-all-subnet-ip-ranges - Allow all IP ranges of all subnetworks in the region, including - primary and secondary ranges, to use NAT. - - --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] - List of subnetwork primary and secondary IP ranges to be allowed to - use NAT. - - ▸ SUBNETWORK:ALL - specifying a subnetwork name with ALL includes - the primary range and all secondary ranges of the subnet. - ▸ SUBNETWORK - including a subnetwork name includes only the - primary subnet range of the subnetwork. - ▸ SUBNETWORK:RANGE_NAME - specifying a subnetwork and secondary - range name includes only that secondary range. It does not include - the primary range of the subnet. - - --nat-primary-subnet-ip-ranges - Allow only primary IP ranges of all subnetworks in the region to use - NAT. - OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to @@ -241,6 +221,42 @@ OPTIONAL FLAGS --nat-external-ip-pool=IP_ADDRESS,[IP_ADDRESS,...] External IP Addresses to use for Cloud NAT + IPv4 subnetwork range options. If they are not specified, one of IPv6 + subnetwork range option has to be provided. + + At most one of these can be specified: + + --nat-all-subnet-ip-ranges + Allow all IP ranges of all subnetworks in the region, including + primary and secondary ranges, to use NAT. + + --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] + List of subnetwork primary and secondary IP ranges to be allowed to + use NAT. + + ▸ SUBNETWORK:ALL - specifying a subnetwork name with ALL includes + the primary range and all secondary ranges of the subnet. + ▸ SUBNETWORK - including a subnetwork name includes only the + primary subnet range of the subnetwork. + ▸ SUBNETWORK:RANGE_NAME - specifying a subnetwork and secondary + range name includes only that secondary range. It does not include + the primary range of the subnet. + + --nat-primary-subnet-ip-ranges + Allow only primary IP ranges of all subnetworks in the region to use + NAT. + + IPv6 subnetwork range options. If they are not specified, one of IPv4 + subnetwork range option has to be provided. + + At most one of these can be specified: + + --nat64-all-v6-subnet-ip-ranges + Allow all ip ranges of ipv6 subnetworks in the region to use NAT. + + --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...] + List of ipv6 subnetworks to be allowed tp use NAT. + 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/compute/routers/nats/update b/gcloud/beta/compute/routers/nats/update index c9c8d25e3..cf24917ac 100644 --- a/gcloud/beta/compute/routers/nats/update +++ b/gcloud/beta/compute/routers/nats/update @@ -15,6 +15,11 @@ SYNOPSIS [--clear-min-ports-per-vm | --min-ports-per-vm=MIN_PORTS_PER_VM] [--clear-nat-external-drain-ip-pool | --nat-external-drain-ip-pool=NAT_EXTERNAL_DRAIN_IP_POOL,[...]] + [--clear-nat-subnet-ip-ranges | --nat-all-subnet-ip-ranges + | --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] + | --nat-primary-subnet-ip-ranges] + [--clear-nat64-subnet-ip-ranges | --nat64-all-v6-subnet-ip-ranges + | --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...]] [--clear-tcp-established-idle-timeout | --tcp-established-idle-timeout=TCP_ESTABLISHED_IDLE_TIMEOUT] [--clear-tcp-time-wait-timeout @@ -22,9 +27,7 @@ SYNOPSIS [--clear-tcp-transitory-idle-timeout | --tcp-transitory-idle-timeout=TCP_TRANSITORY_IDLE_TIMEOUT] [--clear-udp-idle-timeout | --udp-idle-timeout=UDP_IDLE_TIMEOUT] - [--nat-all-subnet-ip-ranges - | --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] - | --nat-primary-subnet-ip-ranges] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute routers nats update is used to update a NAT in a @@ -206,6 +209,46 @@ OPTIONAL FLAGS These IPs must be valid external IPs that have been used as NAT IPs + IPv4 subnetwork range options. + + At most one of these can be specified: + + --clear-nat-subnet-ip-ranges + Clear options related to the NAT's subnet ranges. + + --nat-all-subnet-ip-ranges + Allow all IP ranges of all subnetworks in the region, including + primary and secondary ranges, to use NAT. + + --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] + List of subnetwork primary and secondary IP ranges to be allowed to + use NAT. + + ▸ SUBNETWORK:ALL - specifying a subnetwork name with ALL includes + the primary range and all secondary ranges of the subnet. + ▸ SUBNETWORK - including a subnetwork name includes only the + primary subnet range of the subnetwork. + ▸ SUBNETWORK:RANGE_NAME - specifying a subnetwork and secondary + range name includes only that secondary range. It does not include + the primary range of the subnet. + + --nat-primary-subnet-ip-ranges + Allow only primary IP ranges of all subnetworks in the region to use + NAT. + + IPv6 subnetwork range options. + + At most one of these can be specified: + + --clear-nat64-subnet-ip-ranges + Clear options related to the NAT64's subnet ranges. + + --nat64-all-v6-subnet-ip-ranges + Allow all ip ranges of ipv6 subnetworks in the region to use NAT. + + --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...] + List of ipv6 subnetworks to be allowed tp use NAT. + At most one of these can be specified: --clear-tcp-established-idle-timeout @@ -246,28 +289,6 @@ OPTIONAL FLAGS https://cloud.google.com/sdk/gcloud/reference/topic/datetimes for information on duration formats. - At most one of these can be specified: - - --nat-all-subnet-ip-ranges - Allow all IP ranges of all subnetworks in the region, including - primary and secondary ranges, to use NAT. - - --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] - List of subnetwork primary and secondary IP ranges to be allowed to - use NAT. - - ▸ SUBNETWORK:ALL - specifying a subnetwork name with ALL includes - the primary range and all secondary ranges of the subnet. - ▸ SUBNETWORK - including a subnetwork name includes only the - primary subnet range of the subnetwork. - ▸ SUBNETWORK:RANGE_NAME - specifying a subnetwork and secondary - range name includes only that secondary range. It does not include - the primary range of the subnet. - - --nat-primary-subnet-ip-ranges - Allow only primary IP ranges of all subnetworks in the region to use - NAT. - 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/compute/ssh b/gcloud/beta/compute/ssh index 62339414d..f0eb9eaa9 100644 --- a/gcloud/beta/compute/ssh +++ b/gcloud/beta/compute/ssh @@ -166,8 +166,8 @@ FLAGS $ gcloud beta compute ssh VM_NAME --zone=ZONE \ --troubleshoot [--tunnel-through-iap] - The troubleshoot flag runs tests and returns recommendations for four - types of issues: + The troubleshoot flag runs tests and returns recommendations for the + following types of issues: ◆ VM status ◆ Network connectivity ◆ User permissions diff --git a/gcloud/beta/container/fleet/policycontroller/enable b/gcloud/beta/container/fleet/policycontroller/enable index 01ad9fca8..09362c085 100644 --- a/gcloud/beta/container/fleet/policycontroller/enable +++ b/gcloud/beta/container/fleet/policycontroller/enable @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta container fleet policycontroller enable [--all-memberships | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION] --audit-interval=AUDIT_INTERVAL - --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT --no-content --no-default-bundles --version=VERSION --clear-exemptable-namespaces | --exemptable-namespaces=EXEMPTABLE_NAMESPACES --log-denies | --no-log-denies --monitoring=MONITORING @@ -71,6 +71,10 @@ FLAGS The number of violations stored on the constraint resource. Must be greater than 0. + --no-content + If set, Policy content, including the template library and policy + bundles, will not be installed. + --no-default-bundles If set, skip installing the default bundle of policy-essentials. diff --git a/gcloud/beta/container/hub/policycontroller/enable b/gcloud/beta/container/hub/policycontroller/enable index f9b39fdae..661f3b4c8 100644 --- a/gcloud/beta/container/hub/policycontroller/enable +++ b/gcloud/beta/container/hub/policycontroller/enable @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta container hub policycontroller enable [--all-memberships | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION] --audit-interval=AUDIT_INTERVAL - --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT --no-content --no-default-bundles --version=VERSION --clear-exemptable-namespaces | --exemptable-namespaces=EXEMPTABLE_NAMESPACES --log-denies | --no-log-denies --monitoring=MONITORING @@ -71,6 +71,10 @@ FLAGS The number of violations stored on the constraint resource. Must be greater than 0. + --no-content + If set, Policy content, including the template library and policy + bundles, will not be installed. + --no-default-bundles If set, skip installing the default bundle of policy-essentials. diff --git a/gcloud/beta/firestore/indexes/composite/create b/gcloud/beta/firestore/indexes/composite/create index 245a391e7..1cef12cfa 100644 --- a/gcloud/beta/firestore/indexes/composite/create +++ b/gcloud/beta/firestore/indexes/composite/create @@ -58,11 +58,11 @@ REQUIRED FLAGS Shorthand Example: - --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {"string"}}' --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {"string"}}' + --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {}}' --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {}}' JSON Example: - --field-config='[{"array-config": "string", "field-path": "string", "order": "string", "vector-config": {"dimension": int, "flat": {"string"}}}]' + --field-config='[{"array-config": "string", "field-path": "string", "order": "string", "vector-config": {"dimension": int, "flat": {}}}]' File Example: diff --git a/gcloud/beta/iam/list-grantable-roles b/gcloud/beta/iam/list-grantable-roles index 5ba01f5cc..2beceebbc 100644 --- a/gcloud/beta/iam/list-grantable-roles +++ b/gcloud/beta/iam/list-grantable-roles @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta iam list-grantable-roles RESOURCE [--filter=EXPRESSION] - [--page-size=PAGE_SIZE; default=100] [GCLOUD_WIDE_FLAG ...] + [--page-size=PAGE_SIZE; default=300] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command displays the list of grantable roles for a resource. @@ -50,9 +50,9 @@ LIST COMMAND FLAGS This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. - --page-size=PAGE_SIZE; default=100 + --page-size=PAGE_SIZE; default=300 Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is 100. + specifies the maximum number of resources per page. The default is 300. Paging may be applied before or after --filter and --limit depending on the service. diff --git a/gcloud/beta/iam/policies/delete b/gcloud/beta/iam/policies/delete index 01dd71984..d6353076a 100644 --- a/gcloud/beta/iam/policies/delete +++ b/gcloud/beta/iam/policies/delete @@ -33,8 +33,11 @@ REQUIRED FLAGS OPTIONAL FLAGS --etag=ETAG - Etag that identifies the version of the existing policy. If omitted, - the policy is deleted regardless of its current etag. + Etag that identifies the version of the existing policy. It can be + obtained by running gcloud iam policies get. When deleting a policy, if + the etag is omitted, the policy is deleted regardless of its current + etag. When updating a policy, if the etag is omitted, the update uses + the etag provided in the policy file. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/iam/policies/update b/gcloud/beta/iam/policies/update index 72a9322f8..91b336c95 100644 --- a/gcloud/beta/iam/policies/update +++ b/gcloud/beta/iam/policies/update @@ -5,18 +5,19 @@ NAME SYNOPSIS gcloud beta iam policies update POLICY_ID --attachment-point=ATTACHMENT_POINT --kind=KIND - --policy-file=POLICY_FILE [GCLOUD_WIDE_FLAG ...] + --policy-file=POLICY_FILE [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update the policy on the given attachment point with the given name. EXAMPLES - The following command updates the IAM policy defined at the resource - project 123 of kind denypolicies and id my-deny-policy: + The following command updates the IAM policy my-deny-policy, which is + attached to the resource project 123 and has the etag abc: $ gcloud beta iam policies update my-deny-policy \ --attachment-point=cloudresourcemanager.googleapis.com/\ - projects/123 --kind=denypolicies --policy-file=policy.json + projects/123 --kind=denypolicies --policy-file=policy.json \ + --etag=abc POSITIONAL ARGUMENTS POLICY_ID @@ -35,6 +36,14 @@ REQUIRED FLAGS Path to the file that contains the policy, in JSON or YAML format. For valid syntax, see https://cloud.google.com/iam/help/deny/policy-syntax. +OPTIONAL FLAGS + --etag=ETAG + Etag that identifies the version of the existing policy. It can be + obtained by running gcloud iam policies get. When deleting a policy, if + the etag is omitted, the policy is deleted regardless of its current + etag. When updating a policy, if the etag is omitted, the update uses + the etag provided in the policy file. + 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/iap/settings/get b/gcloud/beta/iap/settings/get index d8eaa8153..7c0f88af5 100644 --- a/gcloud/beta/iap/settings/get +++ b/gcloud/beta/iap/settings/get @@ -49,18 +49,19 @@ EXAMPLES To get the IAP setting for all backend services within a project, run: $ gcloud beta iap settings get --project=PROJECT_ID \ - --resource-type=compute + --resource-type=backend-services To get the IAP setting for a backend service within a project, run: $ gcloud beta iap settings get --project=PROJECT_ID \ - --resource-type=compute --service=SERVICE_ID + --resource-type=backend-services --service=SERVICE_ID To get the IAP setting for a regional backend service within a project, run: $ gcloud beta iap settings get --project=PROJECT_ID \ - --resource-type=compute --service=SERVICE_ID --region=REGION_ID + --resource-type=backend-services --service=SERVICE_ID \ + --region=REGION_ID FLAGS --folder=FOLDER @@ -78,8 +79,10 @@ FLAGS scoped compute. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, iap_web, compute, organization, folder, forwarding-rule. + Resource type of the IAP resource. For Backend Services, you can use + both compute and backend-services as resource type. RESOURCE_TYPE must + be one of: app-engine, iap_web, compute, organization, folder, + forwarding-rule, backend-services. --service=SERVICE Service name. Optional when resource-type is compute or app-engine. diff --git a/gcloud/beta/iap/settings/set b/gcloud/beta/iap/settings/set index f1276b334..556f86a25 100644 --- a/gcloud/beta/iap/settings/set +++ b/gcloud/beta/iap/settings/set @@ -51,18 +51,18 @@ EXAMPLES To set the IAP setting for all backend services within a project, run: $ gcloud beta iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=compute + --project=PROJECT_ID --resource-type=backend-services To set the IAP setting for a backend service within a project, run: $ gcloud beta iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=compute \ + --project=PROJECT_ID --resource-type=backend-services \ --service=SERVICE_ID To set the IAP setting for a region backend service within a project, run: $ gcloud beta iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=compute \ + --project=PROJECT_ID --resource-type=backend-services \ --service=SERVICE_ID --region=REGION_ID POSITIONAL ARGUMENTS @@ -129,8 +129,10 @@ FLAGS scoped compute. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, iap_web, compute, organization, folder, forwarding-rule. + Resource type of the IAP resource. For Backend Services, you can use + both compute and backend-services as resource type. RESOURCE_TYPE must + be one of: app-engine, iap_web, compute, organization, folder, + forwarding-rule, backend-services. --service=SERVICE Service name. Optional when resource-type is compute or app-engine. diff --git a/gcloud/beta/network-management/connectivity-tests/create b/gcloud/beta/network-management/connectivity-tests/create index ec4300a5b..b2123e6c4 100644 --- a/gcloud/beta/network-management/connectivity-tests/create +++ b/gcloud/beta/network-management/connectivity-tests/create @@ -23,7 +23,7 @@ SYNOPSIS [--destination-port=DESTINATION_PORT] [--destination-project=DESTINATION_PROJECT] [--labels=[KEY=VALUE,...]] [--other-projects=[OTHER_PROJECTS,...]] [--protocol=PROTOCOL] - [--source-network=SOURCE_NETWORK] + [--round-trip] [--source-network=SOURCE_NETWORK] [--source-network-type=SOURCE_NETWORK_TYPE; default="gcp-network"] [--source-project=SOURCE_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -143,6 +143,11 @@ OPTIONAL FLAGS --protocol=PROTOCOL Type of protocol for the test. When not provided, "TCP" is assumed. + --round-trip + This boolean controls whether return traces (from the destination to + the source) will be additionally calculated if packet successfully + reaches the destination from the source. + --source-network=SOURCE_NETWORK A VPC network URI where the source is located. diff --git a/gcloud/beta/network-management/connectivity-tests/update b/gcloud/beta/network-management/connectivity-tests/update index 61daee143..e8fd0ea7a 100644 --- a/gcloud/beta/network-management/connectivity-tests/update +++ b/gcloud/beta/network-management/connectivity-tests/update @@ -10,7 +10,7 @@ SYNOPSIS [--destination-port=DESTINATION_PORT] [--destination-project=DESTINATION_PROJECT] [--labels=[KEY=VALUE,...]] [--other-projects=[OTHER_PROJECTS,...]] [--protocol=PROTOCOL] - [--source-network=SOURCE_NETWORK] + [--round-trip] [--source-network=SOURCE_NETWORK] [--source-network-type=SOURCE_NETWORK_TYPE; default="gcp-network"] [--source-project=SOURCE_PROJECT] [--clear-destination-cloud-sql-instance @@ -104,6 +104,12 @@ FLAGS --protocol=PROTOCOL Type of protocol for the test. When not provided, "TCP" is assumed. + --round-trip + This boolean controls whether return traces (from the destination to + the source) will be additionally calculated if packet successfully + reaches the destination from the source. Use --no-round-trip to + disable. + --source-network=SOURCE_NETWORK A VPC network URI where the source is located. diff --git a/gcloud/beta/network-management/vpc-flow-logs-configs/create b/gcloud/beta/network-management/vpc-flow-logs-configs/create index 85168b55a..c0724d94b 100644 --- a/gcloud/beta/network-management/vpc-flow-logs-configs/create +++ b/gcloud/beta/network-management/vpc-flow-logs-configs/create @@ -188,5 +188,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-management vpc-flow-logs-configs create diff --git a/gcloud/beta/network-management/vpc-flow-logs-configs/delete b/gcloud/beta/network-management/vpc-flow-logs-configs/delete index 197752fe5..6804e93ce 100644 --- a/gcloud/beta/network-management/vpc-flow-logs-configs/delete +++ b/gcloud/beta/network-management/vpc-flow-logs-configs/delete @@ -68,5 +68,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-management vpc-flow-logs-configs delete diff --git a/gcloud/beta/network-management/vpc-flow-logs-configs/describe b/gcloud/beta/network-management/vpc-flow-logs-configs/describe index 0389c2c52..5b7db24d5 100644 --- a/gcloud/beta/network-management/vpc-flow-logs-configs/describe +++ b/gcloud/beta/network-management/vpc-flow-logs-configs/describe @@ -62,5 +62,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-management vpc-flow-logs-configs describe diff --git a/gcloud/beta/network-management/vpc-flow-logs-configs/help b/gcloud/beta/network-management/vpc-flow-logs-configs/help index c6d123715..94e05896d 100644 --- a/gcloud/beta/network-management/vpc-flow-logs-configs/help +++ b/gcloud/beta/network-management/vpc-flow-logs-configs/help @@ -35,5 +35,8 @@ COMMANDS configuration. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-management vpc-flow-logs-configs diff --git a/gcloud/beta/network-management/vpc-flow-logs-configs/list b/gcloud/beta/network-management/vpc-flow-logs-configs/list index 04bee45b5..865424249 100644 --- a/gcloud/beta/network-management/vpc-flow-logs-configs/list +++ b/gcloud/beta/network-management/vpc-flow-logs-configs/list @@ -88,5 +88,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-management vpc-flow-logs-configs list diff --git a/gcloud/beta/network-management/vpc-flow-logs-configs/update b/gcloud/beta/network-management/vpc-flow-logs-configs/update index 45d42a71c..86347906f 100644 --- a/gcloud/beta/network-management/vpc-flow-logs-configs/update +++ b/gcloud/beta/network-management/vpc-flow-logs-configs/update @@ -236,5 +236,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-management vpc-flow-logs-configs update diff --git a/gcloud/beta/network-security/intercept-deployment-groups/create b/gcloud/beta/network-security/intercept-deployment-groups/create index e2c41bf13..0e169356f 100644 --- a/gcloud/beta/network-security/intercept-deployment-groups/create +++ b/gcloud/beta/network-security/intercept-deployment-groups/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud beta network-security intercept-deployment-groups create (INTERCEPT_DEPLOYMENT_GROUP : --location=LOCATION) --network=NETWORK - [--async] [--labels=[KEY=VALUE,...]] + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -35,6 +35,14 @@ EXAMPLES my-deployment-group \ --network=projects/my-project/global/networks/my-network + OR + + $ gcloud beta network-security intercept-deployment-groups create \ + projects/my-project/locations/global/interceptDeploymentGroups/\ + my-deployment-group \ + --network=projects/my-project/global/networks/my-network \ + --description='new description' + POSITIONAL ARGUMENTS Intercept deployment group resource - Intercept Deployment Group. The arguments in this group can be used to specify the attributes of this @@ -93,6 +101,9 @@ OPTIONAL FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --description=DESCRIPTION + Description of the deployment group. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/beta/network-security/intercept-deployment-groups/update b/gcloud/beta/network-security/intercept-deployment-groups/update index a2817e9ab..5bc06ada5 100644 --- a/gcloud/beta/network-security/intercept-deployment-groups/update +++ b/gcloud/beta/network-security/intercept-deployment-groups/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta network-security intercept-deployment-groups update (INTERCEPT_DEPLOYMENT_GROUP : --location=LOCATION) [--async] - [--max-wait=MAX_WAIT; default="20m"] [--update-labels=[KEY=VALUE,...]] + [--description=DESCRIPTION] [--max-wait=MAX_WAIT; default="20m"] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -34,6 +35,12 @@ EXAMPLES my-deployment-group --project=my-project --location=global \ --clear-labels + To update description to 'new description', run: + + $ gcloud beta network-security intercept-deployment-groups update \ + my-deployment-group --project=my-project --location=global \ + --description='new description' + POSITIONAL ARGUMENTS Intercept deployment group resource - Intercept Deployment Group. The arguments in this group can be used to specify the attributes of this @@ -73,6 +80,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --description=DESCRIPTION + Description of the deployment group. + --max-wait=MAX_WAIT; default="20m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/beta/network-security/intercept-deployments/create b/gcloud/beta/network-security/intercept-deployments/create index 9bbde4087..a96e688ab 100644 --- a/gcloud/beta/network-security/intercept-deployments/create +++ b/gcloud/beta/network-security/intercept-deployments/create @@ -9,7 +9,7 @@ SYNOPSIS : --forwarding-rule-location=FORWARDING_RULE_LOCATION) (--intercept-deployment-group=INTERCEPT_DEPLOYMENT_GROUP : --intercept-deployment-group-location=INTERCEPT_DEPLOYMENT_GROUP_LOCATION) - [--async] [--labels=[KEY=VALUE,...]] + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -47,6 +47,17 @@ EXAMPLES --intercept-deployment-group=projects/my-project/locations/\ global/interceptDeploymentGroups/my-deployment-group + OR + + $ gcloud beta network-security intercept-deployments create \ + projects/my-project/locations/us-central1/interceptDeployments/\ + my-deployment \ + --forwarding-rule=projects/my-project/regions/us-central1/\ + forwardingRules/my-forwarding-rule \ + --intercept-deployment-group=projects/my-project/locations/\ + global/interceptDeploymentGroups/my-deployment-group \ + --description="my-description" + POSITIONAL ARGUMENTS Intercept deployment resource - Intercept Deployment. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -155,6 +166,9 @@ OPTIONAL FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --description=DESCRIPTION + Description of the deployment. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/beta/network-security/intercept-deployments/update b/gcloud/beta/network-security/intercept-deployments/update index 5cfac0a43..86c6a6ccd 100644 --- a/gcloud/beta/network-security/intercept-deployments/update +++ b/gcloud/beta/network-security/intercept-deployments/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta network-security intercept-deployments update (INTERCEPT_DEPLOYMENT : --location=LOCATION) [--async] - [--max-wait=MAX_WAIT; default="20m"] [--update-labels=[KEY=VALUE,...]] + [--description=DESCRIPTION] [--max-wait=MAX_WAIT; default="20m"] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -33,6 +34,12 @@ EXAMPLES my-deploymen --project=my-project --location=us-central1-a \ --clear-labels + To update description to 'new description', run: + + $ gcloud beta network-security intercept-deployments update \ + my-deploymen --project=my-project --location=us-central1-a \ + --description="new description" + POSITIONAL ARGUMENTS Intercept deployment resource - Intercept Deployment. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -71,6 +78,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --description=DESCRIPTION + Description of the deployment. + --max-wait=MAX_WAIT; default="20m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/beta/network-security/mirroring-deployment-groups/create b/gcloud/beta/network-security/mirroring-deployment-groups/create index 5e1aabf55..fd4c6018d 100644 --- a/gcloud/beta/network-security/mirroring-deployment-groups/create +++ b/gcloud/beta/network-security/mirroring-deployment-groups/create @@ -35,6 +35,14 @@ EXAMPLES my-deployment-group \ --network=projects/my-project/global/networks/my-network + OR + + $ gcloud beta network-security mirroring-deployment-groups create \ + projects/my-project/locations/global/mirroringDeploymentGroups/\ + my-deployment-group \ + --network=projects/my-project/global/networks/my-network \ + --description="my-description" + POSITIONAL ARGUMENTS Mirroring deployment group resource - Mirroring Deployment Group. The arguments in this group can be used to specify the attributes of this diff --git a/gcloud/beta/network-security/mirroring-deployment-groups/update b/gcloud/beta/network-security/mirroring-deployment-groups/update index f42a43ecf..eae4ec9ee 100644 --- a/gcloud/beta/network-security/mirroring-deployment-groups/update +++ b/gcloud/beta/network-security/mirroring-deployment-groups/update @@ -34,6 +34,12 @@ EXAMPLES my-deployment-group --project=my-project --location=global \ --clear-labels + To update description to 'new description', run: + + $ gcloud beta network-security mirroring-deployment-groups update \ + my-deployment-group --project=my-project --location=global \ + --description="new description" + POSITIONAL ARGUMENTS Mirroring deployment group resource - Mirroring Deployment Group. The arguments in this group can be used to specify the attributes of this diff --git a/gcloud/beta/network-security/mirroring-deployments/create b/gcloud/beta/network-security/mirroring-deployments/create index e22b53b8d..e270b418c 100644 --- a/gcloud/beta/network-security/mirroring-deployments/create +++ b/gcloud/beta/network-security/mirroring-deployments/create @@ -47,6 +47,17 @@ EXAMPLES --mirroring-deployment-group=projects/my-project/locations/\ global/mirroringDeploymentGroups/my-deployment-group + OR + + $ gcloud beta network-security mirroring-deployments create \ + projects/my-project/locations/us-central1/mirroringDeployments/\ + my-deployment \ + --forwarding-rule=projects/my-project/regions/us-central1/\ + forwardingRules/my-forwarding-rule \ + --mirroring-deployment-group=projects/my-project/locations/\ + global/mirroringDeploymentGroups/my-deployment-group \ + --description="my-description" + POSITIONAL ARGUMENTS Mirroring deployment resource - Mirroring Deployment. The arguments in this group can be used to specify the attributes of this resource. (NOTE) diff --git a/gcloud/beta/network-security/mirroring-deployments/update b/gcloud/beta/network-security/mirroring-deployments/update index 92fdf574b..7d38f6c7b 100644 --- a/gcloud/beta/network-security/mirroring-deployments/update +++ b/gcloud/beta/network-security/mirroring-deployments/update @@ -33,6 +33,12 @@ EXAMPLES my-deploymen --project=my-project --location=us-central1-a \ --clear-labels + To update description to 'new description', run: + + $ gcloud beta network-security mirroring-deployments update \ + my-deploymen --project=my-project --location=us-central1-a \ + --description="new description" + POSITIONAL ARGUMENTS Mirroring deployment resource - Mirroring Deployment. The arguments in this group can be used to specify the attributes of this resource. (NOTE) diff --git a/gcloud/beta/redis/clusters/get-cluster-certificate-authority b/gcloud/beta/redis/clusters/get-cluster-certificate-authority index 7ec77f430..c2118c191 100644 --- a/gcloud/beta/redis/clusters/get-cluster-certificate-authority +++ b/gcloud/beta/redis/clusters/get-cluster-certificate-authority @@ -17,7 +17,7 @@ DESCRIPTION cluster. EXAMPLES - To get the metadata for a cluster with the name my-redie-cluster in the + To get the metadata for a cluster with the name my-redis-cluster in the default region, run: $ gcloud beta redis clusters get-cluster-certificate-authority \ diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 4a93d5015..49604de9f 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -46,7 +46,7 @@ SYNOPSIS --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...] --command=[COMMAND,...] - | --function=FUNCTION --image=IMAGE | --source=SOURCE] + | --function=FUNCTION --image=IMAGE --source=SOURCE] [--binary-authorization=POLICY | --clear-binary-authorization] [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] @@ -617,27 +617,28 @@ FLAGS Specifies that the deployed object is a function. If a value is provided, that value is used as the entrypoint. - At most one of these can be specified: + --image=IMAGE + Name of the container image to deploy (e.g. + us-docker.pkg.dev/cloudrun/container/hello:latest). When used with + --source, the image must be the URI of an Artifact Registry Docker + repository in the Docker format + ($REGION-docker.pkg.dev/$PROJECT/$REPOSITORY"). - --image=IMAGE - Name of the container image to deploy (e.g. - us-docker.pkg.dev/cloudrun/container/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. + --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: diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 4cf68e7f9..8bb01ee14 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -32,9 +32,10 @@ SYNOPSIS --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --image=IMAGE --liveness-probe=[KEY=VALUE,...] --memory=MEMORY --port=PORT --remove-volume-mount=[MOUNT_PATH,...] - --startup-probe=[KEY=VALUE,...] --[no-]use-http2 --clear-env-vars - | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] - | --remove-env-vars=[KEY,...] + --startup-probe=[KEY=VALUE,...] + --[no-]use-http2 --base-image=BASE_IMAGE + | --clear-base-image --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,...]] @@ -461,6 +462,19 @@ FLAGS 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: + + --base-image=BASE_IMAGE + Specifies the base image to be used for automatic base image + updates. When deploying from source using the Google Cloud + buildpacks, this flag will also override the base image used for + the application image. See + https://cloud.google.com/run/docs/deploying-source-code for more + details. + + --clear-base-image + Opts out of automatic base image updates. + At most one of these can be specified: --clear-env-vars diff --git a/gcloud/beta/workbench/help b/gcloud/beta/workbench/help new file mode 100644 index 000000000..975dce8c4 --- /dev/null +++ b/gcloud/beta/workbench/help @@ -0,0 +1,20 @@ +NAME + gcloud beta workbench - workbench Command Group + +SYNOPSIS + gcloud beta workbench GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Workbench Command Group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud workbench + diff --git a/gcloud/beta/workstations/configs/create b/gcloud/beta/workstations/configs/create index 02003fe9b..1d76ee871 100644 --- a/gcloud/beta/workstations/configs/create +++ b/gcloud/beta/workstations/configs/create @@ -14,10 +14,11 @@ SYNOPSIS [--container-env=[CONTAINER_ENV,...]] [--container-run-as-user=CONTAINER_RUN_AS_USER] [--container-working-dir=CONTAINER_WORKING_DIR] - [--disable-public-ip-addresses] [--disable-ssh-to-vm] - [--disable-tcp-connections] [--enable-audit-agent] - [--enable-confidential-compute] [--enable-nested-virtualization] - [--enable-ssh-to-vm] [--ephemeral-directory=[PROPERTY=VALUE,...]] + [--disable-localhost-replacement] [--disable-public-ip-addresses] + [--disable-ssh-to-vm] [--disable-tcp-connections] + [--enable-audit-agent] [--enable-confidential-compute] + [--enable-nested-virtualization] [--enable-ssh-to-vm] + [--ephemeral-directory=[PROPERTY=VALUE,...]] [--grant-workstation-admin-role-on-create] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] @@ -231,6 +232,13 @@ FLAGS --container-working-dir=CONTAINER_WORKING_DIR If set, overrides the default DIR specified by the image. + --disable-localhost-replacement + By default, the workstations service replaces references to localhost, + 127.0.0.1, and 0.0.0.0 with the workstation's hostname in http + responses from the workstation so that applications under development + run properly on the workstation. This may intefere with some + applications, and so this option allows that behavior to be disabled. + --disable-public-ip-addresses Default value is false. If set, instances will have no public IP address. diff --git a/gcloud/beta/workstations/configs/update b/gcloud/beta/workstations/configs/update index fb0d3c040..29c719b47 100644 --- a/gcloud/beta/workstations/configs/update +++ b/gcloud/beta/workstations/configs/update @@ -29,6 +29,7 @@ SYNOPSIS | --disallow-unauthenticated-cors-preflight-requests] [--container-custom-image=CONTAINER_CUSTOM_IMAGE | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE] + [--disable-localhost-replacement | --enable-localhost-replacement] [--disable-ssh-to-vm | --enable-ssh-to-vm] [--disable-tcp-connections | --enable-tcp-connections] [GCLOUD_WIDE_FLAG ...] @@ -370,6 +371,20 @@ FLAGS webstorm WebStorm + At most one of these can be specified: + + --disable-localhost-replacement + By default, the workstations service replaces references to + localhost, 127.0.0.1, and 0.0.0.0 with the workstation's hostname in + http responses from the workstation so that applications under + development run properly on the workstation. This may intefere with + some applications, and so this option allows that behavior to be + disabled. + + --enable-localhost-replacement + If set, requires that all requests to the workstation are + authenticated. + At most one of these can be specified: --disable-ssh-to-vm diff --git a/gcloud/billing/budgets/create b/gcloud/billing/budgets/create index e316d55f2..1d33289c6 100644 --- a/gcloud/billing/budgets/create +++ b/gcloud/billing/budgets/create @@ -165,25 +165,31 @@ OPTIONAL FLAGS Must be one of: 'current-spend' or 'forecasted-spend'. Behavior defaults to 'current-spend' if not set. + Specify either the calendar-period or custom-period, not both. + At most one of these can be specified: - --calendar-period=CALENDAR_PERIOD - Specifies to track usage over recurring calendar period. If you're - creating a budget with a custom time period, omit this flag. - CALENDAR_PERIOD must be one of: calendar-period-unspecified, month, - quarter, year. + Calendar Period - --start-date=START_DATE - Specifies to track usage after any start date. This time period is - static, it does not recur. + --calendar-period=CALENDAR_PERIOD + Specified to track usage over recurring calendar period. If you're + creating a budget with a custom time period, omit this flag. + CALENDAR_PERIOD must be one of: calendar-period-unspecified, month, + quarter, year. - This flag argument must be specified if any of the other arguments in - this group are specified. + Custom Period - --end-date=END_DATE - Specifies to track usage before any end date. This time period is - static, it does not recur. If specified, --start-date must also be - specified. + --start-date=START_DATE + Specified to track usage after any start date. This time period is + static, it does not recur. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --end-date=END_DATE + Specified to track usage before any end date. This time period is + static, it does not recur. If specified, --start-date must also be + specified. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/billing/budgets/update b/gcloud/billing/budgets/update index 494e33fe4..5e3df26f8 100644 --- a/gcloud/billing/budgets/update +++ b/gcloud/billing/budgets/update @@ -158,25 +158,31 @@ FLAGS --last-period-amount Use the amount of last period's budget. + Specify either the calendar-period or custom-period, not both. + At most one of these can be specified: - --calendar-period=CALENDAR_PERIOD - Specifies to track usage over recurring calendar period. If you're - creating a budget with a custom time period, omit this flag. - CALENDAR_PERIOD must be one of: calendar-period-unspecified, month, - quarter, year. + Calendar Period - --start-date=START_DATE - Specifies to track usage after any start date. This time period is - static, it does not recur. + --calendar-period=CALENDAR_PERIOD + Specified to track usage over recurring calendar period. If you're + creating a budget with a custom time period, omit this flag. + CALENDAR_PERIOD must be one of: calendar-period-unspecified, month, + quarter, year. - This flag argument must be specified if any of the other arguments in - this group are specified. + Custom Period - --end-date=END_DATE - Specifies to track usage before any end date. This time period is - static, it does not recur. If specified, --start-date must also be - specified. + --start-date=START_DATE + Specified to track usage after any start date. This time period is + static, it does not recur. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --end-date=END_DATE + Specified to track usage before any end date. This time period is + static, it does not recur. If specified, --start-date must also be + specified. At most one of these can be specified: diff --git a/gcloud/builds/worker-pools/create b/gcloud/builds/worker-pools/create index a4c83356b..a9d2ca236 100644 --- a/gcloud/builds/worker-pools/create +++ b/gcloud/builds/worker-pools/create @@ -55,7 +55,7 @@ FLAGS --worker-disk-size=WORKER_DISK_SIZE Size of the disk attached to the worker. - If not given, Cloud Build will use a standard disk size. + If unspecified, Cloud Build uses a standard disk size. --worker-machine-type=WORKER_MACHINE_TYPE Compute Engine machine type for a worker pool. diff --git a/gcloud/builds/worker-pools/update b/gcloud/builds/worker-pools/update index 0b05b6f58..b42b2b4d3 100644 --- a/gcloud/builds/worker-pools/update +++ b/gcloud/builds/worker-pools/update @@ -50,7 +50,7 @@ REQUIRED FLAGS --worker-disk-size=WORKER_DISK_SIZE Size of the disk attached to the worker. - If not given, Cloud Build will use a standard disk size. + If unspecified, Cloud Build uses a standard disk size. --worker-machine-type=WORKER_MACHINE_TYPE Compute Engine machine type for a worker pool. diff --git a/gcloud/compute/instance-groups/managed/create b/gcloud/compute/instance-groups/managed/create index 70ff927a1..48e65362d 100644 --- a/gcloud/compute/instance-groups/managed/create +++ b/gcloud/compute/instance-groups/managed/create @@ -12,11 +12,14 @@ SYNOPSIS machine-type=MACHINE_TYPE[,machine-type=MACHINE_TYPE...][,rank=RANK]] [--instance-selection-machine-types=[MACHINE_TYPE,...]] [--list-managed-instances-results=MODE] + [--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY] + [--standby-policy-mode=STANDBY_POLICY_MODE] [--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]] [--stateful-external-ip=[enabled], [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] [--stateful-internal-ip=[enabled], [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] + [--stopped-size=STOPPED_SIZE] [--suspended-size=SUSPENDED_SIZE] [--target-distribution-shape=SHAPE] [--target-pool=[TARGET_POOL,...]] [--zones=ZONE,[ZONE,...]] [--health-check=HEALTH_CHECK | --http-health-check=HTTP_HEALTH_CHECK @@ -151,6 +154,23 @@ OPTIONAL FLAGS Pagination is enabled for the group's listManagedInstances API method. maxResults and pageToken query parameters are respected. + --standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY + Specifies the number of seconds that the MIG should wait before + suspending or stopping a VM. The initial delay gives the initialization + script the time to prepare your VM for a quick scale out. + + --standby-policy-mode=STANDBY_POLICY_MODE + Defines how a MIG resumes or starts VMs from a standby pool when the + group scales out. The default mode is manual. STANDBY_POLICY_MODE must + be one of: + + manual + MIG does not automatically resume or start VMs in the standby pool + when the group scales out. + scale-out-pool + MIG automatically resumes or starts VMs in the standby pool when + the group scales out, and replenishes the standby pool afterwards. + --stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME] Disks considered stateful by the instance group. Managed instance groups preserve and reattach stateful disks on VM autohealing, update, @@ -241,6 +261,12 @@ OPTIONAL FLAGS the instance is deleted manually or when the group size is decreased. + --stopped-size=STOPPED_SIZE + Specifies the target size of stopped VMs in the group. + + --suspended-size=SUSPENDED_SIZE + Specifies the target size of suspended VMs in the group. + --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its instances across zones within the region. The default shape is even. diff --git a/gcloud/compute/instance-groups/managed/help b/gcloud/compute/instance-groups/managed/help index c21089672..6c899880e 100644 --- a/gcloud/compute/instance-groups/managed/help +++ b/gcloud/compute/instance-groups/managed/help @@ -73,6 +73,9 @@ COMMANDS resize Set managed instance group size. + resume-instances + Resume the suspended instances in a managed instance group. + set-autoscaling Set autoscaling parameters of a managed instance group. @@ -85,9 +88,18 @@ COMMANDS set-target-pools Set target pools of managed instance group. + start-instances + Start the stopped instances in a managed instance group. + stop-autoscaling Stop autoscaling a managed instance group. + stop-instances + Stop instances owned by a managed instance group. + + suspend-instances + Suspend instances owned by a managed instance group. + update Update a Compute Engine managed instance group. diff --git a/gcloud/compute/instance-groups/managed/resume-instances b/gcloud/compute/instance-groups/managed/resume-instances new file mode 100644 index 000000000..dd18186a5 --- /dev/null +++ b/gcloud/compute/instance-groups/managed/resume-instances @@ -0,0 +1,75 @@ +NAME + gcloud compute instance-groups managed resume-instances - resume the + suspended instances in a managed instance group + +SYNOPSIS + gcloud compute instance-groups managed resume-instances NAME + --instances=INSTANCE,[INSTANCE,...] [--region=REGION | --zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instance-groups managed resume-instances resumes one or more + instances from a managed instance group, thereby increasing the targetSize + and reducing the targetSuspendedSize of the group. + + The command returns the operation status per instance, which might be FAIL, + SUCCESS, or MEMBER_NOT_FOUND. MEMBER_NOT_FOUND is returned only for + regional groups when the gcloud command-line tool wasn't able to resolve + the zone from the instance name. + +EXAMPLES + To resume an instance from a managed instance group in the us-central1-a + zone, run: + + $ gcloud compute instance-groups managed resume-instances \ + example-managed-instance-group --zone=us-central1-a \ + --instances=example-instance + +POSITIONAL ARGUMENTS + NAME + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --instances=INSTANCE,[INSTANCE,...] + Names of instances to resume. + +OPTIONAL FLAGS + At most one of these can be specified: + + --region=REGION + Region of the managed instance group to operate on. If not specified, + you might be prompted to select a region (interactive mode only). + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + Overrides the default compute/region property value for this command + invocation. + + --zone=ZONE + Zone of the managed instance group to operate on. If not specified, + you might be prompted to select a zone (interactive mode only). + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instance-groups managed resume-instances + + $ gcloud beta compute instance-groups managed resume-instances + diff --git a/gcloud/compute/instance-groups/managed/start-instances b/gcloud/compute/instance-groups/managed/start-instances new file mode 100644 index 000000000..496109f92 --- /dev/null +++ b/gcloud/compute/instance-groups/managed/start-instances @@ -0,0 +1,75 @@ +NAME + gcloud compute instance-groups managed start-instances - start the stopped + instances in a managed instance group + +SYNOPSIS + gcloud compute instance-groups managed start-instances NAME + --instances=INSTANCE,[INSTANCE,...] [--region=REGION | --zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instance-groups managed start-instances starts one or more + instances from a managed instance group, thereby increasing the targetSize + and reducing the targetStoppedSize of the group. + + The command returns the operation status per instance, which might be FAIL, + SUCCESS, or MEMBER_NOT_FOUND. MEMBER_NOT_FOUND is returned only for + regional groups when the gcloud command-line tool wasn't able to resolve + the zone from the instance name. + +EXAMPLES + To start an instance from a managed instance group in the us-central1-a + zone, run: + + $ gcloud compute instance-groups managed start-instances \ + example-managed-instance-group --zone=us-central1-a \ + --instances=example-instance + +POSITIONAL ARGUMENTS + NAME + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --instances=INSTANCE,[INSTANCE,...] + Names of instances to start. + +OPTIONAL FLAGS + At most one of these can be specified: + + --region=REGION + Region of the managed instance group to operate on. If not specified, + you might be prompted to select a region (interactive mode only). + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + Overrides the default compute/region property value for this command + invocation. + + --zone=ZONE + Zone of the managed instance group to operate on. If not specified, + you might be prompted to select a zone (interactive mode only). + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instance-groups managed start-instances + + $ gcloud beta compute instance-groups managed start-instances + diff --git a/gcloud/compute/instance-groups/managed/stop-instances b/gcloud/compute/instance-groups/managed/stop-instances new file mode 100644 index 000000000..674a10439 --- /dev/null +++ b/gcloud/compute/instance-groups/managed/stop-instances @@ -0,0 +1,73 @@ +NAME + gcloud compute instance-groups managed stop-instances - stop instances + owned by a managed instance group + +SYNOPSIS + gcloud compute instance-groups managed stop-instances NAME + --instances=INSTANCE,[INSTANCE,...] [--force] + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instance-groups managed stop-instances stops one or more + instances from a managed instance group + +EXAMPLES + To stop an instance from a managed instance group in the us-central1-a + zone, run: + + $ gcloud compute instance-groups managed stop-instances \ + example-managed-instance-group --zone=us-central1-a \ + --instances=example-instance + +POSITIONAL ARGUMENTS + NAME + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --instances=INSTANCE,[INSTANCE,...] + Names of instances to stop. + +OPTIONAL FLAGS + --force + Immediately stop the specified instances, skipping the initial delay, + if one is specified in the standby policy. + + At most one of these can be specified: + + --region=REGION + Region of the managed instance group to operate on. If not specified, + you might be prompted to select a region (interactive mode only). + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + Overrides the default compute/region property value for this command + invocation. + + --zone=ZONE + Zone of the managed instance group to operate on. If not specified, + you might be prompted to select a zone (interactive mode only). + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instance-groups managed stop-instances + + $ gcloud beta compute instance-groups managed stop-instances + diff --git a/gcloud/compute/instance-groups/managed/suspend-instances b/gcloud/compute/instance-groups/managed/suspend-instances new file mode 100644 index 000000000..46b69077c --- /dev/null +++ b/gcloud/compute/instance-groups/managed/suspend-instances @@ -0,0 +1,79 @@ +NAME + gcloud compute instance-groups managed suspend-instances - suspend + instances owned by a managed instance group + +SYNOPSIS + gcloud compute instance-groups managed suspend-instances NAME + --instances=INSTANCE,[INSTANCE,...] [--force] + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instance-groups managed suspend-instances suspends one or + more instances from a managed instance group, thereby reducing the + targetSize and increasing the targetSuspendedSize of the group. + + The command returns the operation status per instance, which might be FAIL, + SUCCESS, or MEMBER_NOT_FOUND. MEMBER_NOT_FOUND is returned only for + regional groups when the gcloud command-line tool wasn't able to resolve + the zone from the instance name. + +EXAMPLES + To suspend an instance from a managed instance group in the us-central1-a + zone, run: + + $ gcloud compute instance-groups managed suspend-instances \ + example-managed-instance-group --zone=us-central1-a \ + --instances=example-instance + +POSITIONAL ARGUMENTS + NAME + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --instances=INSTANCE,[INSTANCE,...] + Names of instances to suspend. + +OPTIONAL FLAGS + --force + Immediately suspend the specified instances, skipping the initial + delay, if one is specified in the standby policy. + + At most one of these can be specified: + + --region=REGION + Region of the managed instance group to operate on. If not specified, + you might be prompted to select a region (interactive mode only). + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + Overrides the default compute/region property value for this command + invocation. + + --zone=ZONE + Zone of the managed instance group to operate on. If not specified, + you might be prompted to select a zone (interactive mode only). + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instance-groups managed suspend-instances + + $ gcloud beta compute instance-groups managed suspend-instances + diff --git a/gcloud/compute/instance-groups/managed/update b/gcloud/compute/instance-groups/managed/update index c72603350..2fcd57583 100644 --- a/gcloud/compute/instance-groups/managed/update +++ b/gcloud/compute/instance-groups/managed/update @@ -16,11 +16,14 @@ SYNOPSIS [--remove-stateful-disks=DEVICE_NAME,[DEVICE_NAME,...]] [--remove-stateful-external-ips=INTERFACE_NAME,[...]] [--remove-stateful-internal-ips=INTERFACE_NAME,[...]] [--size=SIZE] + [--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY] + [--standby-policy-mode=STANDBY_POLICY_MODE] [--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]] [--stateful-external-ip=[enabled], [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] [--stateful-internal-ip=[enabled], [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] + [--stopped-size=STOPPED_SIZE] [--suspended-size=SUSPENDED_SIZE] [--target-distribution-shape=SHAPE] [--clear-autohealing | --initial-delay=INITIAL_DELAY --health-check=HEALTH_CHECK @@ -153,6 +156,23 @@ FLAGS --size=SIZE Target number of running instances in managed instance group. + --standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY + Specifies the number of seconds that the MIG should wait before + suspending or stopping a VM. The initial delay gives the initialization + script the time to prepare your VM for a quick scale out. + + --standby-policy-mode=STANDBY_POLICY_MODE + Defines how a MIG resumes or starts VMs from a standby pool when the + group scales out. The default mode is manual. STANDBY_POLICY_MODE must + be one of: + + manual + MIG does not automatically resume or start VMs in the standby pool + when the group scales out. + scale-out-pool + MIG automatically resumes or starts VMs in the standby pool when + the group scales out, and replenishes the standby pool afterwards. + --stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME] Disks considered stateful by the instance group. Managed instance groups preserve and reattach stateful disks on VM autohealing, update, @@ -256,6 +276,12 @@ FLAGS the instance is deleted manually or when the group size is decreased. + --stopped-size=STOPPED_SIZE + Specifies the target size of stopped VMs in the group. + + --suspended-size=SUSPENDED_SIZE + Specifies the target size of suspended VMs in the group. + --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its instances across zones within the region. The default shape is even. diff --git a/gcloud/compute/interconnects/attachments/dedicated/create b/gcloud/compute/interconnects/attachments/dedicated/create index c31e93dbc..f0cdf2aa6 100644 --- a/gcloud/compute/interconnects/attachments/dedicated/create +++ b/gcloud/compute/interconnects/attachments/dedicated/create @@ -59,6 +59,8 @@ OPTIONAL FLAGS 20 Gbit/s 50g 50 Gbit/s + 100g + 100 Gbit/s --candidate-ipv6-subnets=[IPV6_SUBNET,...] The candididate-ipv6-subnets field is not available. diff --git a/gcloud/compute/interconnects/attachments/dedicated/update b/gcloud/compute/interconnects/attachments/dedicated/update index 865d244a7..fb85fc506 100644 --- a/gcloud/compute/interconnects/attachments/dedicated/update +++ b/gcloud/compute/interconnects/attachments/dedicated/update @@ -48,6 +48,8 @@ FLAGS 20 Gbit/s 50g 50 Gbit/s + 100g + 100 Gbit/s --candidate-ipv6-subnets=[IPV6_SUBNET,...] The candididate-ipv6-subnets field is not available. diff --git a/gcloud/compute/project-info/update b/gcloud/compute/project-info/update index 62052518e..601276275 100644 --- a/gcloud/compute/project-info/update +++ b/gcloud/compute/project-info/update @@ -13,7 +13,7 @@ DESCRIPTION FLAGS --cloud-armor-tier=CLOUD_ARMOR_TIER Cloud armor tier to assign to the project. CLOUD_ARMOR_TIER must be one - of: CA_STANDARD, CA_ENTERPRISE_PAYGO. + of: CA_STANDARD, CA_ENTERPRISE_PAYGO, CA_ENTERPRISE_ANNUAL. --default-network-tier=DEFAULT_NETWORK_TIER The default network tier to assign to the project. DEFAULT_NETWORK_TIER diff --git a/gcloud/compute/ssh b/gcloud/compute/ssh index 17f8bfe31..fc748c3bc 100644 --- a/gcloud/compute/ssh +++ b/gcloud/compute/ssh @@ -165,8 +165,8 @@ FLAGS $ gcloud compute ssh VM_NAME --zone=ZONE \ --troubleshoot [--tunnel-through-iap] - The troubleshoot flag runs tests and returns recommendations for four - types of issues: + The troubleshoot flag runs tests and returns recommendations for the + following types of issues: ◆ VM status ◆ Network connectivity ◆ User permissions diff --git a/gcloud/container/fleet/policycontroller/enable b/gcloud/container/fleet/policycontroller/enable index 7512460aa..7483284c2 100644 --- a/gcloud/container/fleet/policycontroller/enable +++ b/gcloud/container/fleet/policycontroller/enable @@ -6,7 +6,7 @@ SYNOPSIS gcloud container fleet policycontroller enable [--all-memberships | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION] --audit-interval=AUDIT_INTERVAL - --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT --no-content --no-default-bundles --version=VERSION --clear-exemptable-namespaces | --exemptable-namespaces=EXEMPTABLE_NAMESPACES --log-denies | --no-log-denies --monitoring=MONITORING @@ -71,6 +71,10 @@ FLAGS The number of violations stored on the constraint resource. Must be greater than 0. + --no-content + If set, Policy content, including the template library and policy + bundles, will not be installed. + --no-default-bundles If set, skip installing the default bundle of policy-essentials. diff --git a/gcloud/container/hub/policycontroller/enable b/gcloud/container/hub/policycontroller/enable index cd243e56b..3326d46fc 100644 --- a/gcloud/container/hub/policycontroller/enable +++ b/gcloud/container/hub/policycontroller/enable @@ -6,7 +6,7 @@ SYNOPSIS gcloud container hub policycontroller enable [--all-memberships | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION] --audit-interval=AUDIT_INTERVAL - --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT --no-content --no-default-bundles --version=VERSION --clear-exemptable-namespaces | --exemptable-namespaces=EXEMPTABLE_NAMESPACES --log-denies | --no-log-denies --monitoring=MONITORING @@ -71,6 +71,10 @@ FLAGS The number of violations stored on the constraint resource. Must be greater than 0. + --no-content + If set, Policy content, including the template library and policy + bundles, will not be installed. + --no-default-bundles If set, skip installing the default bundle of policy-essentials. diff --git a/gcloud/database-migration/connection-profiles/create/alloydb b/gcloud/database-migration/connection-profiles/create/alloydb index 2d00b5190..2fba8148d 100644 --- a/gcloud/database-migration/connection-profiles/create/alloydb +++ b/gcloud/database-migration/connection-profiles/create/alloydb @@ -11,7 +11,7 @@ SYNOPSIS [--database-version=DATABASE_VERSION] [--display-name=DISPLAY_NAME] [--enable-outbound-public-ip] [--enable-public-ip] [--labels=[KEY=VALUE,...]] [--network=NETWORK] - [--primary-labels=[KEY=VALUE,...]] + [--primary-labels=[KEY=VALUE,...]] [--role=ROLE] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -125,6 +125,10 @@ OPTIONAL FLAGS The resource labels for an AlloyDB primary instance. An object containing a list of "key": "value" pairs. + --role=ROLE + The role of the connection profile. ROLE must be one of: SOURCE, + DESTINATION. + Kms key resource - Name of the CMEK (customer-managed encryption key) used for this AlloyDB cluster. For example, projects/myProject/locations/us-central1/keyRings/myKeyRing/cryptoKeys/myKey. diff --git a/gcloud/database-migration/connection-profiles/create/cloudsql b/gcloud/database-migration/connection-profiles/create/cloudsql index e45a9b1d8..dbfece5e5 100644 --- a/gcloud/database-migration/connection-profiles/create/cloudsql +++ b/gcloud/database-migration/connection-profiles/create/cloudsql @@ -16,7 +16,7 @@ SYNOPSIS [--database-flags=[FLAG=VALUE,...]] [--display-name=DISPLAY_NAME] [--edition=EDITION] [--no-enable-ip-v4] [--labels=[KEY=VALUE,...]] [--private-network=PRIVATE_NETWORK] [--provider=PROVIDER] - [--require-ssl] [--root-password=ROOT_PASSWORD] + [--require-ssl] [--role=ROLE] [--root-password=ROOT_PASSWORD] [--secondary-zone=SECONDARY_ZONE] [--storage-auto-resize-limit=STORAGE_AUTO_RESIZE_LIMIT] [--user-labels=[KEY=VALUE,...]] [--zone=ZONE] @@ -213,6 +213,10 @@ OPTIONAL FLAGS --require-ssl Whether SSL connections over IP should be enforced or not. + --role=ROLE + The role of the connection profile. ROLE must be one of: SOURCE, + DESTINATION. + --root-password=ROOT_PASSWORD Root Cloud SQL user's password. diff --git a/gcloud/database-migration/connection-profiles/create/mysql b/gcloud/database-migration/connection-profiles/create/mysql index cdeba2abb..585b16ae2 100644 --- a/gcloud/database-migration/connection-profiles/create/mysql +++ b/gcloud/database-migration/connection-profiles/create/mysql @@ -6,7 +6,7 @@ SYNOPSIS gcloud database-migration connection-profiles create mysql (CONNECTION_PROFILE : --region=REGION) [--no-async] [--cloudsql-instance=CLOUDSQL_INSTANCE] [--display-name=DISPLAY_NAME] - [--labels=[KEY=VALUE,...]] [--provider=PROVIDER] + [--labels=[KEY=VALUE,...]] [--provider=PROVIDER] [--role=ROLE] [--ca-certificate=CA_CERTIFICATE : --client-certificate=CLIENT_CERTIFICATE --private-key=PRIVATE_KEY] [--host=HOST --port=PORT --username=USERNAME : --password=PASSWORD @@ -86,6 +86,10 @@ FLAGS Database provider, for managed databases. PROVIDER must be one of: RDS, CLOUDSQL. + --role=ROLE + The role of the connection profile. ROLE must be one of: SOURCE, + DESTINATION. + --ca-certificate=CA_CERTIFICATE x509 PEM-encoded certificate of the CA that signed the database server's certificate. The value for this flag needs to be the content diff --git a/gcloud/database-migration/connection-profiles/create/oracle b/gcloud/database-migration/connection-profiles/create/oracle index 3e9fc4af2..172904554 100644 --- a/gcloud/database-migration/connection-profiles/create/oracle +++ b/gcloud/database-migration/connection-profiles/create/oracle @@ -8,7 +8,7 @@ SYNOPSIS --database-service=DATABASE_SERVICE --host=HOST --port=PORT --username=USERNAME (--password=PASSWORD | --prompt-for-password) [--no-async] [--ca-certificate=CA_CERTIFICATE] - [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--role=ROLE] [--private-connection=PRIVATE_CONNECTION | --static-ip-connectivity | [--forward-ssh-hostname=FORWARD_SSH_HOSTNAME --forward-ssh-username=FORWARD_SSH_USERNAME @@ -114,6 +114,10 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --role=ROLE + The role of the connection profile. ROLE must be one of: SOURCE, + DESTINATION. + At most one of these can be specified: Private connection resource - Resource ID of the private connection. diff --git a/gcloud/database-migration/connection-profiles/create/postgresql b/gcloud/database-migration/connection-profiles/create/postgresql index a4a48d773..4ce7aea25 100644 --- a/gcloud/database-migration/connection-profiles/create/postgresql +++ b/gcloud/database-migration/connection-profiles/create/postgresql @@ -7,7 +7,7 @@ SYNOPSIS (CONNECTION_PROFILE : --region=REGION) [--alloydb-cluster=ALLOYDB_CLUSTER] [--no-async] [--cloudsql-instance=CLOUDSQL_INSTANCE] [--display-name=DISPLAY_NAME] - [--labels=[KEY=VALUE,...]] + [--labels=[KEY=VALUE,...]] [--role=ROLE] [--ca-certificate=CA_CERTIFICATE : --client-certificate=CLIENT_CERTIFICATE --private-key=PRIVATE_KEY] [--host=HOST --port=PORT --username=USERNAME (--password=PASSWORD @@ -89,6 +89,10 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --role=ROLE + The role of the connection profile. ROLE must be one of: SOURCE, + DESTINATION. + --ca-certificate=CA_CERTIFICATE x509 PEM-encoded certificate of the CA that signed the database server's certificate. The value for this flag needs to be the content diff --git a/gcloud/database-migration/connection-profiles/create/sqlserver b/gcloud/database-migration/connection-profiles/create/sqlserver index bf0e63831..1e03ba12d 100644 --- a/gcloud/database-migration/connection-profiles/create/sqlserver +++ b/gcloud/database-migration/connection-profiles/create/sqlserver @@ -9,7 +9,7 @@ SYNOPSIS --username=USERNAME (--password=PASSWORD | --prompt-for-password) | [--gcs-bucket=GCS_BUCKET : --gcs-prefix=GCS_PREFIX --provider=PROVIDER]) [--no-async] - [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--role=ROLE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -123,6 +123,10 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --role=ROLE + The role of the connection profile. ROLE must be one of: SOURCE, + DESTINATION. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/database-migration/connection-profiles/update b/gcloud/database-migration/connection-profiles/update index bfa3ed6de..0cabb8ee2 100644 --- a/gcloud/database-migration/connection-profiles/update +++ b/gcloud/database-migration/connection-profiles/update @@ -7,7 +7,8 @@ SYNOPSIS (CONNECTION_PROFILE : --region=REGION) [--alloydb-cluster=ALLOYDB_CLUSTER] [--ca-certificate=CA_CERTIFICATE] [--client-certificate=CLIENT_CERTIFICATE] - [--cloudsql-instance=CLOUDSQL_INSTANCE] [--display-name=DISPLAY_NAME] + [--cloudsql-instance=CLOUDSQL_INSTANCE] + [--database-service=DATABASE_SERVICE] [--display-name=DISPLAY_NAME] [--host=HOST] [--port=PORT] [--private-key=PRIVATE_KEY] [--update-labels=[KEY=VALUE,...]] [--username=USERNAME] [--clear-labels | --remove-labels=[KEY,...]] @@ -89,6 +90,9 @@ FLAGS If the source or destination is a Cloud SQL database, then use this field to provide the respective Cloud SQL instance ID. + --database-service=DATABASE_SERVICE + database service for the oracle connection profile. + --display-name=DISPLAY_NAME A user-friendly name for the connection profile. The display name can include letters, numbers, spaces, and hyphens, and must start with a diff --git a/gcloud/firestore/indexes/composite/create b/gcloud/firestore/indexes/composite/create index 09ea1b601..40c872b52 100644 --- a/gcloud/firestore/indexes/composite/create +++ b/gcloud/firestore/indexes/composite/create @@ -57,11 +57,11 @@ REQUIRED FLAGS Shorthand Example: - --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {"string"}}' --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {"string"}}' + --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {}}' --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {}}' JSON Example: - --field-config='[{"array-config": "string", "field-path": "string", "order": "string", "vector-config": {"dimension": int, "flat": {"string"}}}]' + --field-config='[{"array-config": "string", "field-path": "string", "order": "string", "vector-config": {"dimension": int, "flat": {}}}]' File Example: diff --git a/gcloud/iam/list-grantable-roles b/gcloud/iam/list-grantable-roles index fd025a6e7..0ca0a94da 100644 --- a/gcloud/iam/list-grantable-roles +++ b/gcloud/iam/list-grantable-roles @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud iam list-grantable-roles RESOURCE [--filter=EXPRESSION] - [--page-size=PAGE_SIZE; default=100] [GCLOUD_WIDE_FLAG ...] + [--page-size=PAGE_SIZE; default=300] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command displays the list of grantable roles for a resource. The @@ -49,9 +49,9 @@ LIST COMMAND FLAGS This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. - --page-size=PAGE_SIZE; default=100 + --page-size=PAGE_SIZE; default=300 Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is 100. + specifies the maximum number of resources per page. The default is 300. Paging may be applied before or after --filter and --limit depending on the service. diff --git a/gcloud/iam/policies/delete b/gcloud/iam/policies/delete index 973a767ec..e7279b331 100644 --- a/gcloud/iam/policies/delete +++ b/gcloud/iam/policies/delete @@ -32,8 +32,11 @@ REQUIRED FLAGS OPTIONAL FLAGS --etag=ETAG - Etag that identifies the version of the existing policy. If omitted, - the policy is deleted regardless of its current etag. + Etag that identifies the version of the existing policy. It can be + obtained by running gcloud iam policies get. When deleting a policy, if + the etag is omitted, the policy is deleted regardless of its current + etag. When updating a policy, if the etag is omitted, the update uses + the etag provided in the policy file. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/iam/policies/update b/gcloud/iam/policies/update index 2f002d5be..e9d56d4c7 100644 --- a/gcloud/iam/policies/update +++ b/gcloud/iam/policies/update @@ -4,18 +4,20 @@ NAME SYNOPSIS gcloud iam policies update POLICY_ID --attachment-point=ATTACHMENT_POINT - --kind=KIND --policy-file=POLICY_FILE [GCLOUD_WIDE_FLAG ...] + --kind=KIND --policy-file=POLICY_FILE [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update the policy on the given attachment point with the given name. EXAMPLES - The following command updates the IAM policy defined at the resource - project 123 of kind denypolicies and id my-deny-policy: + The following command updates the IAM policy my-deny-policy, which is + attached to the resource project 123 and has the etag abc: $ gcloud iam policies update my-deny-policy \ --attachment-point=cloudresourcemanager.googleapis.com/\ - projects/123 --kind=denypolicies --policy-file=policy.json + projects/123 --kind=denypolicies --policy-file=policy.json \ + --etag=abc POSITIONAL ARGUMENTS POLICY_ID @@ -34,6 +36,14 @@ REQUIRED FLAGS Path to the file that contains the policy, in JSON or YAML format. For valid syntax, see https://cloud.google.com/iam/help/deny/policy-syntax. +OPTIONAL FLAGS + --etag=ETAG + Etag that identifies the version of the existing policy. It can be + obtained by running gcloud iam policies get. When deleting a policy, if + the etag is omitted, the policy is deleted regardless of its current + etag. When updating a policy, if the etag is omitted, the update uses + the etag provided in the policy file. + 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/iap/settings/get b/gcloud/iap/settings/get index 5a6e8abfe..607f9ebb1 100644 --- a/gcloud/iap/settings/get +++ b/gcloud/iap/settings/get @@ -49,18 +49,19 @@ EXAMPLES To get the IAP setting for all backend services within a project, run: $ gcloud iap settings get --project=PROJECT_ID \ - --resource-type=compute + --resource-type=backend-services To get the IAP setting for a backend service within a project, run: $ gcloud iap settings get --project=PROJECT_ID \ - --resource-type=compute --service=SERVICE_ID + --resource-type=backend-services --service=SERVICE_ID To get the IAP setting for a regional backend service within a project, run: $ gcloud iap settings get --project=PROJECT_ID \ - --resource-type=compute --service=SERVICE_ID --region=REGION_ID + --resource-type=backend-services --service=SERVICE_ID \ + --region=REGION_ID FLAGS --folder=FOLDER @@ -78,8 +79,10 @@ FLAGS scoped compute. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, iap_web, compute, organization, folder. + Resource type of the IAP resource. For Backend Services, you can use + both compute and backend-services as resource type. RESOURCE_TYPE must + be one of: app-engine, iap_web, compute, organization, folder, + backend-services. --service=SERVICE Service name. Optional when resource-type is compute or app-engine. diff --git a/gcloud/iap/settings/set b/gcloud/iap/settings/set index dd097936c..1b43dac20 100644 --- a/gcloud/iap/settings/set +++ b/gcloud/iap/settings/set @@ -50,17 +50,18 @@ EXAMPLES To set the IAP setting for all backend services within a project, run: $ gcloud iap settings set iap_settings.yaml --project=PROJECT_ID \ - --resource-type=compute + --resource-type=backend-services To set the IAP setting for a backend service within a project, run: $ gcloud iap settings set iap_settings.yaml --project=PROJECT_ID \ - --resource-type=compute --service=SERVICE_ID + --resource-type=backend-services --service=SERVICE_ID To set the IAP setting for a region backend service within a project, run: $ gcloud iap settings set iap_settings.yaml --project=PROJECT_ID \ - --resource-type=compute --service=SERVICE_ID --region=REGION_ID + --resource-type=backend-services --service=SERVICE_ID \ + --region=REGION_ID POSITIONAL ARGUMENTS SETTING_FILE @@ -126,8 +127,10 @@ FLAGS scoped compute. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, iap_web, compute, organization, folder. + Resource type of the IAP resource. For Backend Services, you can use + both compute and backend-services as resource type. RESOURCE_TYPE must + be one of: app-engine, iap_web, compute, organization, folder, + backend-services. --service=SERVICE Service name. Optional when resource-type is compute or app-engine. diff --git a/gcloud/migration/vms/machine-image-imports/create b/gcloud/migration/vms/machine-image-imports/create index f9f5a35dd..0da0bb775 100644 --- a/gcloud/migration/vms/machine-image-imports/create +++ b/gcloud/migration/vms/machine-image-imports/create @@ -6,8 +6,9 @@ SYNOPSIS gcloud migration vms machine-image-imports create (IMAGE_IMPORT_NAME : --location=LOCATION) --source-file=SOURCE_FILE [--additional-licenses=[ADDITIONAL_LICENSES,...]] - [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--machine-image-name=MACHINE_IMAGE_NAME] [--machine-type=MACHINE_TYPE] + [--description=DESCRIPTION] [--kms-key=KMS_KEY] + [--labels=[KEY=VALUE,...]] [--machine-image-name=MACHINE_IMAGE_NAME] + [--machine-type=MACHINE_TYPE] [--network-interface=[network=NETWORK], [networkTier=NETWORKTIER],[subnetwork=SUBNETWORK]] [--single-region-storage] [--tags=[TAGS,...]] @@ -83,6 +84,10 @@ OPTIONAL FLAGS --description=DESCRIPTION A description of the machine image. + --kms-key=KMS_KEY + Fully qualified identifier for the Cloud KMS (Key Management Service) + cryptokey that will be used to protect the image. + --labels=[KEY=VALUE,...] A map of labels to associate with the machine image. diff --git a/gcloud/network-management/connectivity-tests/create b/gcloud/network-management/connectivity-tests/create index e279f0983..5a5b66256 100644 --- a/gcloud/network-management/connectivity-tests/create +++ b/gcloud/network-management/connectivity-tests/create @@ -23,7 +23,7 @@ SYNOPSIS [--destination-port=DESTINATION_PORT] [--destination-project=DESTINATION_PROJECT] [--labels=[KEY=VALUE,...]] [--other-projects=[OTHER_PROJECTS,...]] [--protocol=PROTOCOL] - [--source-network=SOURCE_NETWORK] + [--round-trip] [--source-network=SOURCE_NETWORK] [--source-network-type=SOURCE_NETWORK_TYPE; default="gcp-network"] [--source-project=SOURCE_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -143,6 +143,11 @@ OPTIONAL FLAGS --protocol=PROTOCOL Type of protocol for the test. When not provided, "TCP" is assumed. + --round-trip + This boolean controls whether return traces (from the destination to + the source) will be additionally calculated if packet successfully + reaches the destination from the source. + --source-network=SOURCE_NETWORK A VPC network URI where the source is located. diff --git a/gcloud/network-management/connectivity-tests/update b/gcloud/network-management/connectivity-tests/update index 576d4f70b..7dea1b969 100644 --- a/gcloud/network-management/connectivity-tests/update +++ b/gcloud/network-management/connectivity-tests/update @@ -10,7 +10,7 @@ SYNOPSIS [--destination-port=DESTINATION_PORT] [--destination-project=DESTINATION_PROJECT] [--labels=[KEY=VALUE,...]] [--other-projects=[OTHER_PROJECTS,...]] [--protocol=PROTOCOL] - [--source-network=SOURCE_NETWORK] + [--round-trip] [--source-network=SOURCE_NETWORK] [--source-network-type=SOURCE_NETWORK_TYPE; default="gcp-network"] [--source-project=SOURCE_PROJECT] [--clear-destination-cloud-sql-instance @@ -104,6 +104,12 @@ FLAGS --protocol=PROTOCOL Type of protocol for the test. When not provided, "TCP" is assumed. + --round-trip + This boolean controls whether return traces (from the destination to + the source) will be additionally calculated if packet successfully + reaches the destination from the source. Use --no-round-trip to + disable. + --source-network=SOURCE_NETWORK A VPC network URI where the source is located. diff --git a/gcloud/network-management/help b/gcloud/network-management/help index fde17cb52..0ecf4f322 100644 --- a/gcloud/network-management/help +++ b/gcloud/network-management/help @@ -21,6 +21,9 @@ GROUPS operations Manage Network Management operations. + vpc-flow-logs-configs + Manage the VPC Flow Logs configurations. + NOTES These variants are also available: diff --git a/gcloud/network-management/vpc-flow-logs-configs/create b/gcloud/network-management/vpc-flow-logs-configs/create new file mode 100644 index 000000000..b8eb096ad --- /dev/null +++ b/gcloud/network-management/vpc-flow-logs-configs/create @@ -0,0 +1,195 @@ +NAME + gcloud network-management vpc-flow-logs-configs create - creates a new VPC + Flow Logs configuration in the specified project + +SYNOPSIS + gcloud network-management vpc-flow-logs-configs create + (VPC_FLOW_LOGS_CONFIG : --location=LOCATION) + [--aggregation-interval=AGGREGATION_INTERVAL] [--async] + [--description=DESCRIPTION] [--filter-expr=FILTER_EXPR] + [--flow-sampling=FLOW_SAMPLING] [--labels=[LABELS,...]] + [--metadata=METADATA] [--metadata-fields=[METADATA_FIELDS,...]] + [--state=STATE] + [--interconnect-attachment=INTERCONNECT_ATTACHMENT + | --vpn-tunnel=VPN_TUNNEL] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Creates a new VPC Flow Logs configuration in the specified project. The + target-resource project must be the same as the configuration project. + +EXAMPLES + To create a new VPC Flow Logs configuration my-config in project my-project + for a VLAN attachment for Cloud Interconnect, run: + + $ gcloud network-management vpc-flow-logs-configs create my-config \ + --location=global \ + --interconnect-attachment="projects/my-project/regions/{region}/\ + interconnectAttachments/{interconnect_attachment_id}" + + To create a new VPC Flow Logs configuration my-config in project my-project + for a Cloud VPN tunnel, run: + + $ gcloud network-management vpc-flow-logs-configs create my-config \ + --location=global \ + --vpn-tunnel="projects/my-project/regions/{region}/vpnTunnels/{v\ + pn_tunnel_id}" + +POSITIONAL ARGUMENTS + VpcFlowLogsConfig resource - Identifier. Unique name of the configuration + using the form: + projects/{project_id}/locations/global/vpcFlowLogsConfigs/{vpc_flow_logs_config_id} + 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 vpc_flow_logs_config 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. + + VPC_FLOW_LOGS_CONFIG + ID of the vpcFlowLogsConfig or fully qualified identifier for the + vpcFlowLogsConfig. + + To set the vpc_flow_logs_config attribute: + ▸ provide the argument vpc_flow_logs_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the vpcFlowLogsConfig resource. + + To set the location attribute: + ▸ provide the argument vpc_flow_logs_config on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + Arguments for the aggregation interval. + + --aggregation-interval=AGGREGATION_INTERVAL + The aggregation interval for the logs. Default value is + INTERVAL_5_SEC. AGGREGATION_INTERVAL must be one of: + + interval-1-min + Aggregate logs in 1m intervals. + interval-10-min + Aggregate logs in 10m intervals. + interval-15-min + Aggregate logs in 15m intervals. + interval-30-sec + Aggregate logs in 30s intervals. + interval-5-min + Aggregate logs in 5m intervals. + interval-5-sec + Aggregate logs in 5s intervals. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + Arguments for the description. + + --description=DESCRIPTION + The user-supplied description of the VPC Flow Logs configuration. + Maximum of 512 characters. + + Arguments for the filter expr. + + --filter-expr=FILTER_EXPR + Export filter used to define which VPC Flow Logs should be logged. + + Arguments for the flow sampling. + + --flow-sampling=FLOW_SAMPLING + The value of the field must be in (0, 1]. The sampling rate of VPC + Flow Logs where 1.0 means all collected logs are reported. Setting + the sampling rate to 0.0 is not allowed. If you want to disable VPC + Flow Logs, use the state field instead. Default value is 1.0. + + --labels=[LABELS,...] + Resource labels to represent user-provided metadata. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + Arguments for the metadata. + + --metadata=METADATA + Configures whether all, none or a subset of metadata fields should be + added to the reported VPC flow logs. Default value is + INCLUDE_ALL_METADATA. METADATA must be one of: + + custom-metadata + Include only custom fields (specified in metadata_fields). + exclude-all-metadata + Exclude all metadata fields. + include-all-metadata + Include all metadata fields. + + --metadata-fields=[METADATA_FIELDS,...] + Custom metadata fields to include in the reported VPC flow logs. Can + only be specified if "metadata" was set to CUSTOM_METADATA. + + Arguments for the state. + + --state=STATE + The state of the VPC Flow Log configuration. Default value is + ENABLED. When creating a new configuration, it must be enabled. STATE + must be one of: + + disabled + When DISABLED, this configuration will not generate logs. + enabled + When ENABLED, this configuration will generate logs. + + Arguments for the target resource. + + At most one of these can be specified: + + --interconnect-attachment=INTERCONNECT_ATTACHMENT + Traffic will be logged from the Interconnect Attachment. Format: + projects/{project_id}/regions/{region}/interconnectAttachments/{name} + + --vpn-tunnel=VPN_TUNNEL + Traffic will be logged from the VPN Tunnel. Format: + projects/{project_id}/regions/{region}/vpnTunnels/{name} + +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 networkmanagement/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta network-management vpc-flow-logs-configs create + diff --git a/gcloud/network-management/vpc-flow-logs-configs/delete b/gcloud/network-management/vpc-flow-logs-configs/delete new file mode 100644 index 000000000..eb48406f0 --- /dev/null +++ b/gcloud/network-management/vpc-flow-logs-configs/delete @@ -0,0 +1,74 @@ +NAME + gcloud network-management vpc-flow-logs-configs delete - deletes the + specified VPC Flow Logs configuration + +SYNOPSIS + gcloud network-management vpc-flow-logs-configs delete + (VPC_FLOW_LOGS_CONFIG : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Deletes the specified VPC Flow Logs configuration. + +EXAMPLES + To delete a VPC Flow Logs configuration my-config, run: + + $ gcloud network-management vpc-flow-logs-configs delete my-config \ + --location=global + +POSITIONAL ARGUMENTS + VpcFlowLogsConfig resource - VpcFlowLogsConfig resource name using the + form: + projects/{project_id}/locations/global/vpcFlowLogsConfigs/{vpc_flow_logs_config} + 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 vpc_flow_logs_config 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. + + VPC_FLOW_LOGS_CONFIG + ID of the vpcFlowLogsConfig or fully qualified identifier for the + vpcFlowLogsConfig. + + To set the vpc_flow_logs_config attribute: + ▸ provide the argument vpc_flow_logs_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the vpcFlowLogsConfig resource. + + To set the location attribute: + ▸ provide the argument vpc_flow_logs_config on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkmanagement/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta network-management vpc-flow-logs-configs delete + diff --git a/gcloud/network-management/vpc-flow-logs-configs/describe b/gcloud/network-management/vpc-flow-logs-configs/describe new file mode 100644 index 000000000..c87b45573 --- /dev/null +++ b/gcloud/network-management/vpc-flow-logs-configs/describe @@ -0,0 +1,68 @@ +NAME + gcloud network-management vpc-flow-logs-configs describe - describe the + details of a specific VPC Flow Logs configuration + +SYNOPSIS + gcloud network-management vpc-flow-logs-configs describe + (VPC_FLOW_LOGS_CONFIG : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describes the details of a specific VPC Flow Logs configuration. + +EXAMPLES + To get the details of a VPC Flow Logs configuration my-config, run: + + $ gcloud network-management vpc-flow-logs-configs describe \ + my-config --location=global + +POSITIONAL ARGUMENTS + VpcFlowLogsConfig resource - VpcFlowLogsConfig resource name using the + form: + projects/{project_id}/locations/global/vpcFlowLogsConfigs/{vpc_flow_logs_config} + 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 vpc_flow_logs_config 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. + + VPC_FLOW_LOGS_CONFIG + ID of the vpcFlowLogsConfig or fully qualified identifier for the + vpcFlowLogsConfig. + + To set the vpc_flow_logs_config attribute: + ▸ provide the argument vpc_flow_logs_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the vpcFlowLogsConfig resource. + + To set the location attribute: + ▸ provide the argument vpc_flow_logs_config 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. + +API REFERENCE + This command uses the networkmanagement/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta network-management vpc-flow-logs-configs describe + diff --git a/gcloud/network-management/vpc-flow-logs-configs/help b/gcloud/network-management/vpc-flow-logs-configs/help new file mode 100644 index 000000000..bf8f659fd --- /dev/null +++ b/gcloud/network-management/vpc-flow-logs-configs/help @@ -0,0 +1,39 @@ +NAME + gcloud network-management vpc-flow-logs-configs - manage the VPC Flow Logs + configurations + +SYNOPSIS + gcloud network-management vpc-flow-logs-configs COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The flag --location=global is required for all the commands. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Creates a new VPC Flow Logs configuration in the specified project. + + delete + Deletes the specified VPC Flow Logs configuration. + + describe + Describe the details of a specific VPC Flow Logs configuration. + + list + List all VPC Flow Logs configurations in the project. + + update + Updates one or more fields in an existing VPC Flow Logs configuration. + +NOTES + This variant is also available: + + $ gcloud beta network-management vpc-flow-logs-configs + diff --git a/gcloud/network-management/vpc-flow-logs-configs/list b/gcloud/network-management/vpc-flow-logs-configs/list new file mode 100644 index 000000000..11d7a2cff --- /dev/null +++ b/gcloud/network-management/vpc-flow-logs-configs/list @@ -0,0 +1,93 @@ +NAME + gcloud network-management vpc-flow-logs-configs list - list all VPC Flow + Logs configurations in the project + +SYNOPSIS + gcloud network-management vpc-flow-logs-configs list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Lists all VPC Flow Logs configurations in the project. + +EXAMPLES + To list all the VPC Flow Logs configurations within the project, run: + + $ gcloud network-management vpc-flow-logs-configs list \ + --location=global + + To list all the VPC Flow Logs configurations within the project with state + 'ENABLED', run: + + $ gcloud network-management vpc-flow-logs-configs list \ + --location=global --filter="state:ENABLED" + +REQUIRED FLAGS + Location resource - The parent resource of the VpcFlowLogsConfig: + projects/{project_id}/locations/global This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument --location 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. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkmanagement/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta network-management vpc-flow-logs-configs list + diff --git a/gcloud/network-management/vpc-flow-logs-configs/update b/gcloud/network-management/vpc-flow-logs-configs/update new file mode 100644 index 000000000..381ae5df3 --- /dev/null +++ b/gcloud/network-management/vpc-flow-logs-configs/update @@ -0,0 +1,241 @@ +NAME + gcloud network-management vpc-flow-logs-configs update - updates one or + more fields in an existing VPC Flow Logs configuration + +SYNOPSIS + gcloud network-management vpc-flow-logs-configs update + (VPC_FLOW_LOGS_CONFIG : --location=LOCATION) + [--aggregation-interval=AGGREGATION_INTERVAL] [--async] + [--description=DESCRIPTION] [--filter-expr=FILTER_EXPR] + [--flow-sampling=FLOW_SAMPLING] [--metadata=METADATA] [--state=STATE] + [--interconnect-attachment=INTERCONNECT_ATTACHMENT + | --vpn-tunnel=VPN_TUNNEL] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] + [--metadata-fields=[METADATA_FIELDS,...] + | --add-metadata-fields=[ADD_METADATA_FIELDS,...] + --clear-metadata-fields + | --remove-metadata-fields=[REMOVE_METADATA_FIELDS,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates one or more fields in an existing VPC Flow Logs configuration. + +EXAMPLES + To update the state field to be 'DISABLED' in the VPC Flow Logs + configuration my-config, run: + + $ gcloud network-management vpc-flow-logs-configs update my-config \ + --location=global --state=DISABLED + +POSITIONAL ARGUMENTS + VpcFlowLogsConfig resource - Identifier. Unique name of the configuration + using the form: + projects/{project_id}/locations/global/vpcFlowLogsConfigs/{vpc_flow_logs_config_id} + 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 vpc_flow_logs_config 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. + + VPC_FLOW_LOGS_CONFIG + ID of the vpcFlowLogsConfig or fully qualified identifier for the + vpcFlowLogsConfig. + + To set the vpc_flow_logs_config attribute: + ▸ provide the argument vpc_flow_logs_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the vpcFlowLogsConfig resource. + + To set the location attribute: + ▸ provide the argument vpc_flow_logs_config on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + Arguments for the aggregation interval. + + --aggregation-interval=AGGREGATION_INTERVAL + The aggregation interval for the logs. Default value is + INTERVAL_5_SEC. AGGREGATION_INTERVAL must be one of: + + interval-1-min + Aggregate logs in 1m intervals. + interval-10-min + Aggregate logs in 10m intervals. + interval-15-min + Aggregate logs in 15m intervals. + interval-30-sec + Aggregate logs in 30s intervals. + interval-5-min + Aggregate logs in 5m intervals. + interval-5-sec + Aggregate logs in 5s intervals. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + Arguments for the description. + + --description=DESCRIPTION + The user-supplied description of the VPC Flow Logs configuration. + Maximum of 512 characters. + + Arguments for the filter expr. + + --filter-expr=FILTER_EXPR + Export filter used to define which VPC Flow Logs should be logged. + + Arguments for the flow sampling. + + --flow-sampling=FLOW_SAMPLING + The value of the field must be in (0, 1]. The sampling rate of VPC + Flow Logs where 1.0 means all collected logs are reported. Setting + the sampling rate to 0.0 is not allowed. If you want to disable VPC + Flow Logs, use the state field instead. Default value is 1.0. + + Arguments for the metadata. + + --metadata=METADATA + Configures whether all, none or a subset of metadata fields should be + added to the reported VPC flow logs. Default value is + INCLUDE_ALL_METADATA. METADATA must be one of: + + custom-metadata + Include only custom fields (specified in metadata_fields). + exclude-all-metadata + Exclude all metadata fields. + include-all-metadata + Include all metadata fields. + + Arguments for the state. + + --state=STATE + The state of the VPC Flow Log configuration. Default value is + ENABLED. When creating a new configuration, it must be enabled. STATE + must be one of: + + disabled + When DISABLED, this configuration will not generate logs. + enabled + When ENABLED, this configuration will generate logs. + + Arguments for the target resource. + + At most one of these can be specified: + + --interconnect-attachment=INTERCONNECT_ATTACHMENT + Traffic will be logged from the Interconnect Attachment. Format: + projects/{project_id}/regions/{region}/interconnectAttachments/{name} + + --vpn-tunnel=VPN_TUNNEL + Traffic will be logged from the VPN Tunnel. Format: + projects/{project_id}/regions/{region}/vpnTunnels/{name} + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Resource labels to represent user-provided + metadata. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Resource labels to + represent user-provided metadata. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + + Update metadata_fields. + + At most one of these can be specified: + + --metadata-fields=[METADATA_FIELDS,...] + Set metadata_fields to new value. + + --add-metadata-fields=[ADD_METADATA_FIELDS,...] + Add new value to metadata_fields list. + + At most one of these can be specified: + + --clear-metadata-fields + Clear metadata_fields value and set to empty list. + + --remove-metadata-fields=[REMOVE_METADATA_FIELDS,...] + Remove existing value from metadata_fields list. + +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 networkmanagement/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta network-management vpc-flow-logs-configs update + diff --git a/gcloud/redis/clusters/get-cluster-certificate-authority b/gcloud/redis/clusters/get-cluster-certificate-authority index d67e4a9c5..3830f2d5d 100644 --- a/gcloud/redis/clusters/get-cluster-certificate-authority +++ b/gcloud/redis/clusters/get-cluster-certificate-authority @@ -17,7 +17,7 @@ DESCRIPTION cluster. EXAMPLES - To get the metadata for a cluster with the name my-redie-cluster in the + To get the metadata for a cluster with the name my-redis-cluster in the default region, run: $ gcloud redis clusters get-cluster-certificate-authority \ diff --git a/gcloud/workbench/help b/gcloud/workbench/help index 382652f37..877106323 100644 --- a/gcloud/workbench/help +++ b/gcloud/workbench/help @@ -17,3 +17,9 @@ GROUPS instances Workbench Instances command group. + +NOTES + This variant is also available: + + $ gcloud beta workbench + diff --git a/gcloud/workbench/instances/create b/gcloud/workbench/instances/create index d4731232e..18182e982 100644 --- a/gcloud/workbench/instances/create +++ b/gcloud/workbench/instances/create @@ -3,8 +3,8 @@ NAME SYNOPSIS gcloud workbench instances create (INSTANCE : --location=LOCATION) - [--async] [--disable-proxy-access] [--instance-owners=INSTANCE_OWNERS] - [--labels=[KEY=VALUE,...]] + [--async] [--disable-proxy-access] [--enable-third-party-identity] + [--instance-owners=INSTANCE_OWNERS] [--labels=[KEY=VALUE,...]] [--disable-public-ip --enable-ip-forwarding --machine-type=MACHINE_TYPE; default="n1-standard-4" --metadata=[KEY=VALUE,...] --min-cpu-platform=MIN_CPU_PLATFORM @@ -113,6 +113,10 @@ FLAGS --disable-proxy-access If true, the notebook instance will not register with the proxy. + --enable-third-party-identity + If true, the notebook instance provide a proxy endpoint which allows + for third party identity. + --instance-owners=INSTANCE_OWNERS The owners of this instance after creation. Format: alias@example.com. Currently supports one owner only. If not specified, all of the service @@ -172,7 +176,8 @@ FLAGS NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_A100, NVIDIA_A100_80GB, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, - NVIDIA_TESLA_P4_VWS, NVIDIA_L4. + NVIDIA_TESLA_P4_VWS, NVIDIA_L4, NVIDIA_H100_80GB, + NVIDIA_H100_MEGA_80GB. Boot disk configurations. diff --git a/gcloud/workbench/instances/update b/gcloud/workbench/instances/update index 70a8a9251..51a3201e1 100644 --- a/gcloud/workbench/instances/update +++ b/gcloud/workbench/instances/update @@ -92,7 +92,8 @@ FLAGS NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_A100, NVIDIA_A100_80GB, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, - NVIDIA_TESLA_P4_VWS, NVIDIA_L4. + NVIDIA_TESLA_P4_VWS, NVIDIA_L4, NVIDIA_H100_80GB, + NVIDIA_H100_MEGA_80GB. GPU driver configurations.