From 29661f002c61b5c6f70769c2b6aed149128faf16 Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 8 Mar 2023 10:34:05 +0000 Subject: [PATCH] gcloud: Wed Mar 8 10:34:05 UTC 2023 --- gcloud/_version | 12 +- gcloud/alloydb/instances/restart | 2 +- gcloud/alpha/alloydb/instances/restart | 2 +- .../builds/connections/add-iam-policy-binding | 41 +---- gcloud/alpha/composer/environments/run | 14 +- gcloud/alpha/compute/diagnose/help | 3 - gcloud/alpha/compute/diagnose/sosreport | 167 ------------------ .../alpha/compute/instance-templates/create | 11 +- gcloud/alpha/compute/instances/bulk/create | 7 + gcloud/alpha/compute/instances/create | 10 +- .../compute/instances/create-with-container | 11 +- .../instances/ops-agents/policies/create | 6 +- .../instances/ops-agents/policies/update | 6 +- gcloud/alpha/compute/instances/set-scheduling | 59 +++++++ .../attachments/dedicated/create | 37 +++- .../interconnects/attachments/partner/create | 37 +++- gcloud/alpha/compute/queued-resources/create | 7 + gcloud/alpha/compute/routers/create | 9 +- gcloud/alpha/compute/routers/nats/create | 14 +- gcloud/alpha/compute/vpn-gateways/create | 16 +- .../container/bare-metal/clusters/delete | 6 +- .../container/bare-metal/clusters/update | 11 +- gcloud/alpha/container/vmware/clusters/create | 7 +- gcloud/alpha/container/vmware/clusters/update | 7 +- gcloud/alpha/logging/help | 2 +- gcloud/alpha/logging/links/create | 24 +-- gcloud/alpha/logging/links/delete | 16 +- gcloud/alpha/logging/links/describe | 17 +- gcloud/alpha/logging/links/help | 14 +- gcloud/alpha/logging/links/list | 16 +- gcloud/alpha/metastore/services/create | 56 ++++-- gcloud/alpha/metastore/services/update | 56 ++++-- gcloud/alpha/monitoring/help | 3 + gcloud/alpha/monitoring/snoozes/cancel | 52 ++++++ gcloud/alpha/monitoring/snoozes/create | 53 ++++++ gcloud/alpha/monitoring/snoozes/describe | 39 ++++ gcloud/alpha/monitoring/snoozes/help | 41 +++++ gcloud/alpha/monitoring/snoozes/list | 86 +++++++++ gcloud/alpha/monitoring/snoozes/update | 78 ++++++++ gcloud/alpha/scc/custom-modules/sha/create | 15 +- gcloud/alpha/scc/custom-modules/sha/delete | 2 +- gcloud/alpha/scc/custom-modules/sha/get | 2 +- .../scc/custom-modules/sha/get-effective | 2 +- gcloud/alpha/scc/custom-modules/sha/list | 7 +- .../scc/custom-modules/sha/list-descendant | 10 +- .../scc/custom-modules/sha/list-effective | 10 +- gcloud/alpha/scc/custom-modules/sha/test | 19 +- gcloud/alpha/scc/custom-modules/sha/update | 44 ++--- gcloud/alpha/services/api-keys/undelete | 65 ++++--- gcloud/alpha/services/api-keys/update | 2 +- gcloud/alpha/spanner/databases/roles/help | 8 +- gcloud/alpha/spanner/databases/roles/list | 8 +- gcloud/alpha/sql/instances/patch | 7 +- gcloud/alpha/terraform/help | 2 +- gcloud/beta/alloydb/instances/restart | 2 +- .../builds/connections/add-iam-policy-binding | 41 +---- gcloud/beta/composer/environments/run | 14 +- .../instances/ops-agents/policies/create | 6 +- .../instances/ops-agents/policies/update | 6 +- gcloud/beta/compute/instances/set-scheduling | 52 ++++++ .../attachments/dedicated/create | 38 +++- .../interconnects/attachments/partner/create | 37 +++- gcloud/beta/compute/routers/create | 9 +- gcloud/beta/compute/routers/nats/create | 15 ++ gcloud/beta/compute/vpn-gateways/create | 16 +- .../beta/filestore/instances/snapshots/create | 13 +- .../beta/filestore/instances/snapshots/delete | 14 +- .../filestore/instances/snapshots/describe | 14 +- .../beta/filestore/instances/snapshots/list | 14 +- .../beta/filestore/instances/snapshots/update | 13 +- gcloud/beta/logging/help | 2 +- gcloud/beta/logging/links/create | 23 +-- gcloud/beta/logging/links/delete | 16 +- gcloud/beta/logging/links/describe | 17 +- gcloud/beta/logging/links/help | 14 +- gcloud/beta/logging/links/list | 15 +- gcloud/beta/metastore/services/create | 56 ++++-- gcloud/beta/metastore/services/update | 56 ++++-- gcloud/beta/services/api-keys/undelete | 65 ++++--- gcloud/beta/services/api-keys/update | 2 +- gcloud/beta/spanner/databases/roles/help | 8 +- gcloud/beta/spanner/databases/roles/list | 11 +- gcloud/beta/sql/instances/patch | 7 +- gcloud/composer/environments/run | 14 +- gcloud/compute/backend-services/create | 7 + gcloud/compute/backend-services/update | 7 + .../attachments/dedicated/create | 38 +++- .../interconnects/attachments/partner/create | 37 +++- gcloud/compute/routers/create | 9 +- gcloud/compute/routers/nats/create | 15 ++ gcloud/compute/vpn-gateways/create | 16 +- gcloud/filestore/instances/snapshots/create | 14 +- gcloud/filestore/instances/snapshots/delete | 12 +- gcloud/filestore/instances/snapshots/describe | 12 +- gcloud/filestore/instances/snapshots/list | 14 +- gcloud/filestore/instances/snapshots/update | 14 +- gcloud/logging/help | 2 +- gcloud/logging/links/create | 23 +-- gcloud/logging/links/delete | 16 +- gcloud/logging/links/describe | 16 +- gcloud/logging/links/help | 14 +- gcloud/logging/links/list | 15 +- gcloud/metastore/services/create | 91 ++++++++-- gcloud/metastore/services/update | 102 +++++++++-- gcloud/spanner/databases/execute-sql | 5 +- gcloud/spanner/databases/help | 3 + gcloud/spanner/databases/roles/help | 27 +++ gcloud/spanner/databases/roles/list | 94 ++++++++++ gcloud/sql/instances/patch | 7 +- gcloud/workflows/execute | 9 +- gcloud/workflows/run | 17 +- 111 files changed, 1800 insertions(+), 704 deletions(-) delete mode 100644 gcloud/alpha/compute/diagnose/sosreport create mode 100644 gcloud/alpha/monitoring/snoozes/cancel create mode 100644 gcloud/alpha/monitoring/snoozes/create create mode 100644 gcloud/alpha/monitoring/snoozes/describe create mode 100644 gcloud/alpha/monitoring/snoozes/help create mode 100644 gcloud/alpha/monitoring/snoozes/list create mode 100644 gcloud/alpha/monitoring/snoozes/update create mode 100644 gcloud/spanner/databases/roles/help create mode 100644 gcloud/spanner/databases/roles/list diff --git a/gcloud/_version b/gcloud/_version index 8ae6f45a6..574f3c71e 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 420.0.0 -alpha 2023.02.24 -beta 2023.02.24 -bq 2.0.86 +Google Cloud SDK 421.0.0 +alpha 2023.03.03 +beta 2023.03.03 +bq 2.0.87 bundled-python3-unix 3.9.16 -core 2023.02.24 +core 2023.03.03 gcloud-crc32c 1.0.0 -gsutil 5.20 +gsutil 5.21 diff --git a/gcloud/alloydb/instances/restart b/gcloud/alloydb/instances/restart index 01557ccdd..790a0768d 100644 --- a/gcloud/alloydb/instances/restart +++ b/gcloud/alloydb/instances/restart @@ -10,7 +10,7 @@ DESCRIPTION Restarts an AlloyDB instance within a given cluster. EXAMPLES - To describe an instance, run: + To restart an instance, run: $ gcloud alloydb instances restart my-instance \ --cluster=my-cluster --region=us-central1 diff --git a/gcloud/alpha/alloydb/instances/restart b/gcloud/alpha/alloydb/instances/restart index aed7fe5a7..503bd08b3 100644 --- a/gcloud/alpha/alloydb/instances/restart +++ b/gcloud/alpha/alloydb/instances/restart @@ -10,7 +10,7 @@ DESCRIPTION (ALPHA) Restarts an AlloyDB instance within a given cluster. EXAMPLES - To describe an instance, run: + To restart an instance, run: $ gcloud alpha alloydb instances restart my-instance \ --cluster=my-cluster --region=us-central1 diff --git a/gcloud/alpha/builds/connections/add-iam-policy-binding b/gcloud/alpha/builds/connections/add-iam-policy-binding index 6c6cf352d..dd9566716 100644 --- a/gcloud/alpha/builds/connections/add-iam-policy-binding +++ b/gcloud/alpha/builds/connections/add-iam-policy-binding @@ -5,8 +5,7 @@ NAME SYNOPSIS gcloud alpha builds connections add-iam-policy-binding (CONNECTION : --region=REGION) --member=PRINCIPAL --role=ROLE - [--condition=[KEY=VALUE,...] - | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Add IAM policy binding to a Cloud Build connection. One binding @@ -70,44 +69,6 @@ REQUIRED FLAGS for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer. -OPTIONAL FLAGS - At most one of these can be specified: - - --condition=[KEY=VALUE,...] - A condition to include in the binding. When the condition is - explicitly specified as None (--condition=None), a binding without a - condition is added. When the condition is specified and is not None, - --role cannot be a basic role. Basic roles are roles/editor, - roles/owner, and roles/viewer. For more on conditions, refer to the - conditions overview guide: - https://cloud.google.com/iam/docs/conditions-overview - - When using the --condition flag, include the following key-value - pairs: - - expression - (Required) Condition expression that evaluates to True or False. - This uses a subset of Common Expression Language syntax. - - If the condition expression includes a comma, use a different - delimiter to separate the key-value pairs. Specify the delimiter - before listing the key-value pairs. For example, to specify a - colon (:) as the delimiter, do the following: - --condition=^:^title=TITLE:expression=EXPRESSION. For more - information, see - https://cloud.google.com/sdk/gcloud/reference/topic/escaping. - - title - (Required) A short string describing the purpose of the - expression. - - description - (Optional) Additional description for the expression. - - --condition-from-file=CONDITION_FROM_FILE - Path to a local JSON or YAML file that defines the condition. To see - available fields, see the help for --condition. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/composer/environments/run b/gcloud/alpha/composer/environments/run index 511ea7e89..2e5343dd7 100644 --- a/gcloud/alpha/composer/environments/run +++ b/gcloud/alpha/composer/environments/run @@ -13,8 +13,20 @@ DESCRIPTION sub-command to complete; its exit code will match the sub-command's exit code. + Note: Airflow CLI sub-command syntax differs between Airflow 1 and Airflow + 2. Refer to the Airflow CLI reference documentation for more details. + EXAMPLES - The following command: + The following command in environments with Airflow 2: + + gcloud alpha composer environments run myenv dags trigger -- some_dag --run_id=foo + + is equivalent to running the following command from a shell inside the + my-environment environment: + + airflow dags trigger --run_id=foo some_dag + + The same command, but for environments with Airflow 1.10.14+: gcloud alpha composer environments run myenv trigger_dag -- some_dag --run_id=foo diff --git a/gcloud/alpha/compute/diagnose/help b/gcloud/alpha/compute/diagnose/help index b7dd864fd..178399798 100644 --- a/gcloud/alpha/compute/diagnose/help +++ b/gcloud/alpha/compute/diagnose/help @@ -23,9 +23,6 @@ COMMANDS routes (ALPHA) Routes to/from Compute Engine virtual machine instances. - sosreport - (ALPHA) Sosreport run from a Compute Engine VM. - 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/diagnose/sosreport b/gcloud/alpha/compute/diagnose/sosreport deleted file mode 100644 index f78614dfb..000000000 --- a/gcloud/alpha/compute/diagnose/sosreport +++ /dev/null @@ -1,167 +0,0 @@ -NAME - gcloud alpha compute diagnose sosreport - sosreport run from a Compute - Engine VM - -SYNOPSIS - gcloud alpha compute diagnose sosreport INSTANCE_NAME - [--download-dir=DOWNLOAD_DIR] [--dry-run] [--force-key-file-overwrite] - [--plain] [--python-path=PYTHON_PATH] - [--reports-path=REPORTS_PATH; default="/tmp/gcloud-sosreport"] - [--sosreport-install-path=SOSREPORT_INSTALL_PATH; - default="/tmp/git-sosreport"] [--ssh-flag=SSH_FLAG] - [--ssh-key-file=SSH_KEY_FILE] - [--strict-host-key-checking=STRICT_HOST_KEY_CHECKING] [--user=USER] - [--zone=ZONE] - [--ssh-key-expiration=SSH_KEY_EXPIRATION - | --ssh-key-expire-after=SSH_KEY_EXPIRE_AFTER] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command is designed to obtain relevant debug information from - a VM in a standard way for expediting support cases. - - The actual information scraping is done by the Sosreport tool - (https://github.com/sosreport/sos). This command is a wrapper that handles - installation, running and (optionally) copying the result. - - The location of the tool download and report generation are defaulted to - the /tmp directory, but can be modified through flags. The user can use the - --download-dir flag to specify a location where the command can download - the resulting from the VM. - - NOTE: For this command to work, git needs to be installed within the VM, in - order to clone the repository and run the code from there. - - NOTE: Sosreport is somewhat geared towards Python 3.x, as it uses APIs that - had to be back-ported to Python 2.7 (notably concurrent). If the default - installation of Python is 2.7, it is possible that the Sosreport run fails. - To fix this either install the dependencies for Python 2.7 or use - python-path to specify the path to another Python installation that works, - normally it being a Python 3.x binary. - -EXAMPLES - To obtain relevant debug information from a VM, run: - - $ gcloud alpha compute diagnose sosreport - -POSITIONAL ARGUMENTS - INSTANCE_NAME - Name of the instance to run Sosreport on. For details on valid instance - names, refer to the criteria documented under the field 'name' at: - https://cloud.google.com/compute/docs/reference/rest/v1/instances - -FLAGS - --download-dir=DOWNLOAD_DIR - Local dir to which to download the report generated in the VM. If not - specified, no download will be done. The download will be done using a - no-configuration gcloud compute scp command. For more complicated - setups, manual download will be required. - - --dry-run - Print the equivalent scp/ssh command that would be run to stdout, - instead of executing it. - - --force-key-file-overwrite - If enabled, the gcloud command-line tool will regenerate and overwrite - the files associated with a broken SSH key without asking for - confirmation in both interactive and non-interactive environments. - - If disabled, the files associated with a broken SSH key will not be - regenerated and will fail in both interactive and non-interactive - environments. - - --plain - Suppress the automatic addition of ssh(1)/scp(1) flags. This flag is - useful if you want to take care of authentication yourself or use - specific ssh/scp features. - - --python-path=PYTHON_PATH - Path to the python binary to be called. Sosreport is a python tool - which is called by default with the default python installation. This - overrides that calls and uses the provided python binary. - - --reports-path=REPORTS_PATH; default="/tmp/gcloud-sosreport" - Remote location (within the VM) to write the reports into. - - --sosreport-install-path=SOSREPORT_INSTALL_PATH; default="/tmp/git-sosreport" - Remote location (within the VM) to clone sosreport into. - - --ssh-flag=SSH_FLAG - Additional flags to be passed to ssh(1). It is recommended that flags - be passed using an assignment operator and quotes. This flag will - replace occurrences of ``%USER%"" and ``%INSTANCE%"" with their - dereferenced values. Example: - - $ gcloud alpha compute diagnose sosreport example-instance \ - --zone us-central1-a --ssh-flag="-vvv" \ - --ssh-flag="-L 80:%INSTANCE%:80" - - is equivalent to passing the flags ``--vvv"" and ``-L - 80:162.222.181.197:80"" to ssh(1) if the external IP address of - "example-instance" is 162.222.181.197. - - --ssh-key-file=SSH_KEY_FILE - The path to the SSH key file. By default, this is - ~/.ssh/google_compute_engine. - - --strict-host-key-checking=STRICT_HOST_KEY_CHECKING - Override the default behavior of StrictHostKeyChecking for the - connection. By default, StrictHostKeyChecking is set to 'no' the first - time you connect to an instance, and will be set to 'yes' for all - subsequent connections. STRICT_HOST_KEY_CHECKING must be one of: yes, - no, ask. - - --user=USER - User for login to the selected VMs. If not specified, the default user - will be used. - - --zone=ZONE - Zone of the instance to run Sosreport on. If not specified, you might - be prompted to select a zone (interactive mode only). gcloud attempts - to identify the appropriate zone by searching for resources in your - currently active project. If the zone cannot be determined, gcloud - prompts you for a selection with all available Google Cloud Platform - zones. - - To avoid prompting when this flag is omitted, the user can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - - At most one of these can be specified: - - --ssh-key-expiration=SSH_KEY_EXPIRATION - The time when the ssh key will be valid until, such as - "2017-08-29T18:52:51.142Z." This is only valid if the instance is not - using OS Login. See $ gcloud topic datetimes for information on time - formats. - - --ssh-key-expire-after=SSH_KEY_EXPIRE_AFTER - The maximum length of time an SSH key is valid for once created and - installed, e.g. 2m for 2 minutes. See $ gcloud topic datetimes for - information on duration formats. - -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/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index edc51d101..1953c7f3d 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -26,8 +26,9 @@ SYNOPSIS [--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]] [--local-nvdimm=[size=SIZE]] [--local-ssd=[device-name=DEVICE-NAME], - [interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE] - [--max-run-duration=MAX_RUN_DURATION] + [interface=INTERFACE],[size=SIZE]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] + [--machine-type=MACHINE_TYPE] [--max-run-duration=MAX_RUN_DURATION] [--mesh=[gke-cluster=GKE-CLUSTER],[workload=WORKLOAD]] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] @@ -488,6 +489,12 @@ FLAGS partitions. You can specify a maximum of 24 local SSDs for a maximum of 9TB attached to an instance. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of available machine types, run 'gcloud compute machine-types list'. If diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index 1a36816a0..852aeb089 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -22,6 +22,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME], [interface=INTERFACE],[size=SIZE]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] [--location-policy=[ZONE=POLICY,...]] [--machine-type=MACHINE_TYPE] [--maintenance-interval=MAINTENANCE_INTERVAL] [--max-count-per-zone=[ZONE=MAX_COUNT_PER_ZONE,...]] @@ -456,6 +457,12 @@ OPTIONAL FLAGS partitions. You can specify a maximum of 24 local SSDs for a maximum of 9TB attached to an instance. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --location-policy=[ZONE=POLICY,...] Policy for which zones to include or exclude during bulk instance creation within a region. Policy is defined as a list of key-value diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 84b61bacf..de4075478 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -29,7 +29,9 @@ SYNOPSIS [--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]] [--local-nvdimm=[size=SIZE]] [--local-ssd=[device-name=DEVICE-NAME], - [interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE] + [interface=INTERFACE],[size=SIZE]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] + [--machine-type=MACHINE_TYPE] [--maintenance-freeze-duration=MAINTENANCE_FREEZE_DURATION] [--maintenance-interval=MAINTENANCE_INTERVAL] [--max-run-duration=MAX_RUN_DURATION] @@ -589,6 +591,12 @@ FLAGS partitions. You can specify a maximum of 24 local SSDs for a maximum of 9TB attached to an instance. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of available machine types, run 'gcloud compute machine-types list'. If diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index b1fff7d3c..3c279104e 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -36,8 +36,9 @@ SYNOPSIS [--ipv6-prefix-length=IPV6_PREFIX_LENGTH] [--labels=[KEY=VALUE,...]] [--local-nvdimm=[size=SIZE]] [--local-ssd=[device-name=DEVICE-NAME], - [interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE] - [--metadata=KEY=VALUE,[KEY=VALUE,...]] + [interface=INTERFACE],[size=SIZE]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] + [--machine-type=MACHINE_TYPE] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] [--min-cpu-platform=PLATFORM] [--network=NETWORK] [--network-interface=[PROPERTY=VALUE,...]] @@ -515,6 +516,12 @@ FLAGS partitions. You can specify a maximum of 24 local SSDs for a maximum of 9TB attached to an instance. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of available machine types, run 'gcloud compute machine-types list'. If diff --git a/gcloud/alpha/compute/instances/ops-agents/policies/create b/gcloud/alpha/compute/instances/ops-agents/policies/create index 062582dbd..337a73e83 100644 --- a/gcloud/alpha/compute/instances/ops-agents/policies/create +++ b/gcloud/alpha/compute/instances/ops-agents/policies/create @@ -229,8 +229,10 @@ REQUIRED FLAGS debian 11 debian 10 debian 9 + rhel 9.* rhel 8.* rhel 7.* + rocky 9.* rocky 8.* sles 12.* sles 15.* @@ -249,8 +251,8 @@ REQUIRED FLAGS short-name Short name of the OS. - Required. Allowed values: centos, debian, rhel, sles, sles_sap, - ubuntu. + Required. Allowed values: centos, debian, rhel, rocky, sles, + sles_sap, ubuntu. To inspect the exact OS short name of an instance, run: diff --git a/gcloud/alpha/compute/instances/ops-agents/policies/update b/gcloud/alpha/compute/instances/ops-agents/policies/update index fe5c6c47c..e3f1477cb 100644 --- a/gcloud/alpha/compute/instances/ops-agents/policies/update +++ b/gcloud/alpha/compute/instances/ops-agents/policies/update @@ -266,8 +266,10 @@ FLAGS debian 11 debian 10 debian 9 + rhel 9.* rhel 8.* rhel 7.* + rocky 9.* rocky 8.* sles 12.* sles 15.* @@ -286,8 +288,8 @@ FLAGS short-name Short name of the OS. - Required. Allowed values: centos, debian, rhel, sles, sles_sap, - ubuntu. + Required. Allowed values: centos, debian, rhel, rocky, sles, + sles_sap, ubuntu. To inspect the exact OS short name of an instance, run: diff --git a/gcloud/alpha/compute/instances/set-scheduling b/gcloud/alpha/compute/instances/set-scheduling index b6ae3dd0a..95ef3768b 100644 --- a/gcloud/alpha/compute/instances/set-scheduling +++ b/gcloud/alpha/compute/instances/set-scheduling @@ -6,13 +6,16 @@ SYNOPSIS gcloud alpha compute instances set-scheduling INSTANCE_NAME [--clear-min-node-cpu] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] [--min-node-cpu=MIN_NODE_CPU] [--[no-]preemptible] [--provisioning-model=PROVISIONING_MODEL] [--[no-]restart-on-failure] [--zone=ZONE] [--clear-instance-termination-action | --instance-termination-action=INSTANCE_TERMINATION_ACTION] + [--clear-max-run-duration | --max-run-duration=MAX_RUN_DURATION] [--clear-node-affinities | --node=NODE | --node-affinity-file=NODE_AFFINITY_FILE | --node-group=NODE_GROUP] + [--clear-termination-time | --termination-time=TERMINATION_TIME] [--maintenance-policy=MAINTENANCE_POLICY | --on-host-maintenance=MAINTENANCE_POLICY] [GCLOUD_WIDE_FLAG ...] @@ -44,6 +47,12 @@ FLAGS with 30 second increments, with a range of 90 to 330 seconds. If unset, the default behavior of the host error recovery is used. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --min-node-cpu=MIN_NODE_CPU Minimum number of virtual CPUs this instance will consume when running on a sole-tenant node. @@ -123,6 +132,33 @@ FLAGS Default. Stop the VM without preserving memory. The VM can be restarted later. + Max Run Duration + + At most one of these can be specified: + + --clear-max-run-duration + Removes the max-run-duration field from the scheduling options. + + --max-run-duration=MAX_RUN_DURATION + Limits how long this VM instance can run, specified as a duration + relative to the VM instance's most-recent start time. Format the + duration, MAX_RUN_DURATION, as the number of days, hours, minutes, + and seconds followed by d, h, m, and s respectively. For example, + specify 30m for a duration of 30 minutes or specify 1d2h3m4s for a + duration of 1 day, 2 hours, 3 minutes, and 4 seconds. Alternatively, + to specify a timestamp, use --termination-time instead. + + If neither --max-run-duration nor --termination-time is specified + (default), the VM instance runs until prompted by a user action or + system event. If either is specified, the VM instance is scheduled to + be automatically terminated using the action specified by + --instance-termination-action. For --max-run-duration, the VM + instance is automatically terminated when the VM's current runtime + reaches MAX_RUN_DURATION. Note: Anytime the VM instance is stopped or + suspended, --max-run-duration and (unless the VM uses + --provisioning-model=SPOT) --instance-termination-action are + automatically removed from the VM. + Sole Tenancy. At most one of these can be specified: @@ -159,6 +195,29 @@ FLAGS --node-group=NODE_GROUP The name of the node group to schedule this instance on. + Termination Time + + At most one of these can be specified: + + --clear-termination-time + Removes the termination-time field from the scheduling options. + + --termination-time=TERMINATION_TIME + Limits how long this VM instance can run, specified as a time. Format + the time, TERMINATION_TIME, as a RFC 3339 timestamp. For more + information, see https://tools.ietf.org/html/rfc3339. Alternatively, + to specify a duration, use --max-run-duration instead. + + If neither --termination-time nor --max-run-duration is specified + (default), the VM instance runs until prompted by a user action or + system event. If either is specified, the VM instance is scheduled to + be automatically terminated using the action specified by + --instance-termination-action. For --termination-time, the VM + instance is automatically terminated at the specified timestamp. + Note: Anytime the VM instance is stopped or suspended, + --termination-time and (unless the VM uses --provisioning-model=SPOT) + --instance-termination-action are automatically removed from the VM. + Maintenance Behavior. At most one of these can be specified: diff --git a/gcloud/alpha/compute/interconnects/attachments/dedicated/create b/gcloud/alpha/compute/interconnects/attachments/dedicated/create index 0ab47cd31..c1d85e889 100644 --- a/gcloud/alpha/compute/interconnects/attachments/dedicated/create +++ b/gcloud/alpha/compute/interconnects/attachments/dedicated/create @@ -9,8 +9,9 @@ SYNOPSIS [--candidate-subnets=[SUBNET,...]] [--cloud-router-ipv6-interface-id=INTERFACE_ID] [--customer-router-ipv6-interface-id=PEER_INTERFACE_ID] - [--description=DESCRIPTION] [--dry-run] [--enable-admin] [--mtu=MTU] - [--region=REGION] [--stack-type=STACK_TYPE] + [--description=DESCRIPTION] [--dry-run] [--enable-admin] + [--encryption=ENCRYPTION] [--ipsec-internal-addresses=[ADDRESSES]] + [--mtu=MTU] [--region=REGION] [--stack-type=STACK_TYPE] [--subnet-length=SUBNET_LENGTH] [--vlan=VLAN] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -104,6 +105,38 @@ OPTIONAL FLAGS is operational and will carry traffic. Use --no-enable-admin to disable it. + --encryption=ENCRYPTION + Indicates the user-supplied encryption option for this interconnect + attachment (VLAN attachment). + + Possible values are: + + NONE - This is the default value, which means the interconnect + attachment carries unencrypted traffic. VMs can send traffic to or + receive traffic from such interconnect attachment. + + IPSEC - The interconnect attachment carries only traffic that is + encrypted by an IPsec device; for example, an HA VPN gateway or + third-party IPsec VPN. VMs cannot directly send traffic to or receive + traffic from such an interconnect attachment. To use HA VPN over Cloud + Interconnect, the interconnect attachment must be created with this + option. + + ENCRYPTION must be one of: IPSEC, NONE. + + --ipsec-internal-addresses=[ADDRESSES] + List of IP address range names that have been reserved for the + interconnect attachment (VLAN attachment). Use this option only for an + interconnect attachment that has its encryption option set as IPSEC. + Currently only one internal IP address range can be specified for each + attachment. When creating an HA VPN gateway for the interconnect + attachment, if the attachment is configured to use a regional internal + IP address, then the VPN gateway's IP address is allocated from the IP + address range specified here. If this field is not specified when + creating the interconnect attachment, then when creating any HA VPN + gateways for this interconnect attachment, the HA VPN gateway's IP + address is allocated from a regional external IP address pool. + --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet passing through this interconnect attachment. Only 1440 and 1500 are diff --git a/gcloud/alpha/compute/interconnects/attachments/partner/create b/gcloud/alpha/compute/interconnects/attachments/partner/create index eb7af657e..9c6b72ef7 100644 --- a/gcloud/alpha/compute/interconnects/attachments/partner/create +++ b/gcloud/alpha/compute/interconnects/attachments/partner/create @@ -5,8 +5,9 @@ NAME SYNOPSIS gcloud alpha compute interconnects attachments partner create NAME --edge-availability-domain=AVAILABILITY_DOMAIN --router=ROUTER - [--description=DESCRIPTION] [--dry-run] [--enable-admin] [--mtu=MTU] - [--region=REGION] [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--dry-run] [--enable-admin] + [--encryption=ENCRYPTION] [--ipsec-internal-addresses=[ADDRESSES]] + [--mtu=MTU] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute interconnects attachments partner create is @@ -56,6 +57,38 @@ OPTIONAL FLAGS is operational and will carry traffic. Use --no-enable-admin to disable it. + --encryption=ENCRYPTION + Indicates the user-supplied encryption option for this interconnect + attachment (VLAN attachment). + + Possible values are: + + NONE - This is the default value, which means the interconnect + attachment carries unencrypted traffic. VMs can send traffic to or + receive traffic from such interconnect attachment. + + IPSEC - The interconnect attachment carries only traffic that is + encrypted by an IPsec device; for example, an HA VPN gateway or + third-party IPsec VPN. VMs cannot directly send traffic to or receive + traffic from such an interconnect attachment. To use HA VPN over Cloud + Interconnect, the interconnect attachment must be created with this + option. + + ENCRYPTION must be one of: IPSEC, NONE. + + --ipsec-internal-addresses=[ADDRESSES] + List of IP address range names that have been reserved for the + interconnect attachment (VLAN attachment). Use this option only for an + interconnect attachment that has its encryption option set as IPSEC. + Currently only one internal IP address range can be specified for each + attachment. When creating an HA VPN gateway for the interconnect + attachment, if the attachment is configured to use a regional internal + IP address, then the VPN gateway's IP address is allocated from the IP + address range specified here. If this field is not specified when + creating the interconnect attachment, then when creating any HA VPN + gateways for this interconnect attachment, the HA VPN gateway's IP + address is allocated from a regional external IP address pool. + --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet passing through this interconnect attachment. Only 1440 and 1500 are diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index 1fed003c1..017d87255 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -23,6 +23,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME], [interface=INTERFACE],[size=SIZE]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] [--location-policy=[ZONE=POLICY,...]] [--machine-type=MACHINE_TYPE] [--maintenance-interval=MAINTENANCE_INTERVAL] [--max-run-duration=MAX_RUN_DURATION] @@ -440,6 +441,12 @@ OPTIONAL FLAGS partitions. You can specify a maximum of 24 local SSDs for a maximum of 9TB attached to an instance. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --location-policy=[ZONE=POLICY,...] Policy for which zones to include or exclude during bulk instance creation within a region. Policy is defined as a list of key-value diff --git a/gcloud/alpha/compute/routers/create b/gcloud/alpha/compute/routers/create index dbb662a5c..e52a7cd53 100644 --- a/gcloud/alpha/compute/routers/create +++ b/gcloud/alpha/compute/routers/create @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha compute routers create NAME --network=NETWORK [--advertisement-mode=MODE] [--asn=ASN] [--async] - [--description=DESCRIPTION] [--keepalive-interval=KEEPALIVE_INTERVAL] - [--region=REGION] [--set-advertisement-groups=[GROUP,...]] + [--description=DESCRIPTION] [--encrypted-interconnect-router] + [--keepalive-interval=KEEPALIVE_INTERVAL] [--region=REGION] + [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] [GCLOUD_WIDE_FLAG ...] @@ -42,6 +43,10 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional description of this router. + --encrypted-interconnect-router + Indicates if a router is dedicated for use with encrypted interconnect + attachments (VLAN attachments). + --keepalive-interval=KEEPALIVE_INTERVAL The interval between BGP keepalive messages that are sent to the peer. If set, this value must be between 20 and 60 seconds. The default is 20 diff --git a/gcloud/alpha/compute/routers/nats/create b/gcloud/alpha/compute/routers/nats/create index 17be07b6f..cf95b89cb 100644 --- a/gcloud/alpha/compute/routers/nats/create +++ b/gcloud/alpha/compute/routers/nats/create @@ -108,9 +108,17 @@ OPTIONAL FLAGS --router ROUTER --region REGION --endpoint-types=[ENDPOINT_TYPE,...] - Endpoint Types supported by the NAT Gateway. Choices are - ENDPOINT_TYPE_VM for VM Endpoints and ENDPOINT_TYPE_SWG for Secure Web - Gateway Endpoints. Defaults to ENDPOINT_TYPE_VM if not specified. + Endpoint Types supported by the NAT Gateway. + + ENDPOINT_TYPE must be one of: + + ENDPOINT_TYPE_VM + For VM Endpoints + ENDPOINT_TYPE_SWG + For Secure Web Gateway Endpoints + + The default is ENDPOINT_TYPE_VM. + ENDPOINT_TYPE must be one of: ENDPOINT_TYPE_VM, ENDPOINT_TYPE_SWG. --icmp-idle-timeout=ICMP_IDLE_TIMEOUT diff --git a/gcloud/alpha/compute/vpn-gateways/create b/gcloud/alpha/compute/vpn-gateways/create index c9ea6c1e8..e4018f784 100644 --- a/gcloud/alpha/compute/vpn-gateways/create +++ b/gcloud/alpha/compute/vpn-gateways/create @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha compute vpn-gateways create NAME --network=NETWORK - [--description=DESCRIPTION] [--region=REGION] [--stack-type=STACK_TYPE] - [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] + [--interconnect-attachments=[INTERCONNECT_ATTACHMENTS,...]] + [--region=REGION] [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute vpn-gateways create creates a new Highly @@ -35,6 +36,17 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional, textual description for the VPN gateway. + --interconnect-attachments=[INTERCONNECT_ATTACHMENTS,...] + Names of interconnect attachments (VLAN attachments) associated with + the VPN gateway interfaces. You must specify this field when using a + VPN gateway for HA VPN over Cloud Interconnect. Otherwise, this field + is optional. + + For example, --interconnect-attachments + attachment-a-zone1,attachment-a-zone2 associates VPN gateway with + attachment from zone1 on interface 0 and with attachment from zone2 on + interface 1. + --region=REGION Region of the VPN Gateway to create. If not specified, you might be prompted to select a region (interactive mode only). diff --git a/gcloud/alpha/container/bare-metal/clusters/delete b/gcloud/alpha/container/bare-metal/clusters/delete index 224510c72..5fc59c01a 100644 --- a/gcloud/alpha/container/bare-metal/clusters/delete +++ b/gcloud/alpha/container/bare-metal/clusters/delete @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha container bare-metal clusters delete (CLUSTER : --location=LOCATION) [--allow-missing] [--async] [--force] - [--validate-only] [GCLOUD_WIDE_FLAG ...] + [--ignore-errors] [--validate-only] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Delete an Anthos cluster on bare metal. @@ -56,6 +56,10 @@ FLAGS If set, the operation will also apply to the child node pools. This flag is required if the cluster has any associated node pools. + --ignore-errors + If set, the deletion of a bare metal user cluster resource will succeed + even if errors occur during deletion. + --validate-only If set, only validate the request, but do not actually perform the operation. diff --git a/gcloud/alpha/container/bare-metal/clusters/update b/gcloud/alpha/container/bare-metal/clusters/update index 2da1a701e..0d6e0c471 100644 --- a/gcloud/alpha/container/bare-metal/clusters/update +++ b/gcloud/alpha/container/bare-metal/clusters/update @@ -6,7 +6,9 @@ SYNOPSIS gcloud alpha container bare-metal clusters update (CLUSTER : --location=LOCATION) [--admin-users=ADMIN_USERS] [--allow-missing] [--async] [--description=DESCRIPTION] - [--enable-application-logs] [--login-user=LOGIN_USER] + [--enable-application-logs] + [--island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...]] + [--login-user=LOGIN_USER] [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS, ...]] [--validate-only] [--version=VERSION] [--api-server-args=[KEY=VALUE,...] @@ -86,6 +88,13 @@ FLAGS Whether collection of application logs/metrics should be enabled (in addition to system logs/metrics). + Populate one of the network configs. + + Island mode CIDR network configuration. + + --island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...] + IPv4 address range for all services in the cluster. + Anthos on bare metal node access related settings for the user cluster. --login-user=LOGIN_USER diff --git a/gcloud/alpha/container/vmware/clusters/create b/gcloud/alpha/container/vmware/clusters/create index d78c4e4b3..f4250efbc 100644 --- a/gcloud/alpha/container/vmware/clusters/create +++ b/gcloud/alpha/container/vmware/clusters/create @@ -220,13 +220,16 @@ REQUIRED FLAGS --static-ip-config-ip-blocks=[gateway=GATEWAY],[ips=IPS],[netmask=NETMASK] Static IP configurations. + Expect an individual IP address, an individual IP address with an + optional hostname, or a CIDR block. + Example: To specify two Static IP blocks, $ gcloud gcloud alpha container vmware clusters create - --static-ip-config-ip-blocks 'gateway=192.168.0.1,netmask=255.255.255.0,ips=hostname-1:1.1.1.1;hostname-2:2.2.2.2' - --static-ip-config-ip-blocks 'gateway=192.168.1.1,netmask=255.255.0.0,ips=hostname-3:3.3.3.3;hostname-4:4.4.4.4' + --static-ip-config-ip-blocks 'gateway=192.168.0.1,netmask=255.255.255.0,ips=192.168.1.1;0.0.0.0 localhost;192.168.1.2/16' + --static-ip-config-ip-blocks 'gateway=192.168.1.1,netmask=255.255.0.0,ips=8.8.8.8;4.4.4.4' Use quote around the flag value to escape semicolon in the terminal. diff --git a/gcloud/alpha/container/vmware/clusters/update b/gcloud/alpha/container/vmware/clusters/update index cf2199a99..2a1f8671f 100644 --- a/gcloud/alpha/container/vmware/clusters/update +++ b/gcloud/alpha/container/vmware/clusters/update @@ -103,13 +103,16 @@ FLAGS --static-ip-config-ip-blocks=[gateway=GATEWAY],[ips=IPS],[netmask=NETMASK] Static IP configurations. + Expect an individual IP address, an individual IP address with an + optional hostname, or a CIDR block. + Example: To specify two Static IP blocks, $ gcloud gcloud alpha container vmware clusters update - --static-ip-config-ip-blocks 'gateway=192.168.0.1,netmask=255.255.255.0,ips=hostname-1:1.1.1.1;hostname-2:2.2.2.2' - --static-ip-config-ip-blocks 'gateway=192.168.1.1,netmask=255.255.0.0,ips=hostname-3:3.3.3.3;hostname-4:4.4.4.4' + --static-ip-config-ip-blocks 'gateway=192.168.0.1,netmask=255.255.255.0,ips=192.168.1.1;0.0.0.0 localhost;192.168.1.2/16' + --static-ip-config-ip-blocks 'gateway=192.168.1.1,netmask=255.255.0.0,ips=8.8.8.8;4.4.4.4' Use quote around the flag value to escape semicolon in the terminal. diff --git a/gcloud/alpha/logging/help b/gcloud/alpha/logging/help index d96c3308f..a8a985e66 100644 --- a/gcloud/alpha/logging/help +++ b/gcloud/alpha/logging/help @@ -19,7 +19,7 @@ GROUPS (ALPHA) Manage Cloud Logging buckets. links - (ALPHA) Manage log links. + (ALPHA) Manage linked datasets. locations (ALPHA) Query Cloud Logging locations. diff --git a/gcloud/alpha/logging/links/create b/gcloud/alpha/logging/links/create index dd6bd50ce..1470a9bca 100644 --- a/gcloud/alpha/logging/links/create +++ b/gcloud/alpha/logging/links/create @@ -1,6 +1,6 @@ NAME - gcloud alpha logging links create - create a link on an analytics log - bucket + gcloud alpha logging links create - create a linked dataset on an analytics + log bucket SYNOPSIS gcloud alpha logging links create LINK_ID --bucket=BUCKET @@ -10,24 +10,24 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create a link for a log bucket. + (ALPHA) Create a linked dataset for a log bucket. EXAMPLES - To create a link in a project, run: + To create a linked dataset in a project, run: $ gcloud alpha logging links create my-link --bucket=my-bucket \ --location=global POSITIONAL ARGUMENTS LINK_ID - ID of the link to create. + ID of the linked dataset to create. REQUIRED FLAGS --bucket=BUCKET - ID of the bucket that will hold the link + ID of the bucket that will hold the linked dataset --location=LOCATION - Location of the bucket that will hold the link. + Location of the bucket that will hold the linked datasert. OPTIONAL FLAGS --async @@ -35,21 +35,21 @@ OPTIONAL FLAGS complete. --description=DESCRIPTION - A textual description for the link. + A textual description for the linked dataset. At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID - Billing account of the link to create. + Billing account of the linked dataset to create. --folder=FOLDER_ID - Folder of the link to create. + Folder of the linked dataset to create. --organization=ORGANIZATION_ID - Organization of the link to create. + Organization of the linked dataset to create. --project=PROJECT_ID - Project of the link to create. + Project of the linked dataset to create. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/alpha/logging/links/delete b/gcloud/alpha/logging/links/delete index 083acbd1a..475b78de1 100644 --- a/gcloud/alpha/logging/links/delete +++ b/gcloud/alpha/logging/links/delete @@ -1,5 +1,5 @@ NAME - gcloud alpha logging links delete - delete a link + gcloud alpha logging links delete - delete a linked dataset SYNOPSIS gcloud alpha logging links delete LINK_ID --bucket=BUCKET @@ -9,17 +9,17 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Deletes a bucket's link. + (ALPHA) Delete a bucket's linked dataset. EXAMPLES - To delete a bucket's link, run: + To delete a bucket's linked dataset, run: $ gcloud alpha logging links delete my-link --bucket=my-bucket \ --location=global POSITIONAL ARGUMENTS LINK_ID - ID of the link to delete. + ID of the linked dataset to delete. REQUIRED FLAGS --bucket=BUCKET @@ -36,16 +36,16 @@ OPTIONAL FLAGS At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID - Billing account of the link to delete. + Billing account of the linked dataset to delete. --folder=FOLDER_ID - Folder of the link to delete. + Folder of the linked dataset to delete. --organization=ORGANIZATION_ID - Organization of the link to delete. + Organization of the linked dataset to delete. --project=PROJECT_ID - Project of the link to delete. + Project of the linked dataset to delete. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/alpha/logging/links/describe b/gcloud/alpha/logging/links/describe index 0b6d3e763..c8397c205 100644 --- a/gcloud/alpha/logging/links/describe +++ b/gcloud/alpha/logging/links/describe @@ -1,5 +1,6 @@ NAME - gcloud alpha logging links describe - display information about a link + gcloud alpha logging links describe - display information about a linked + dataset SYNOPSIS gcloud alpha logging links describe LINK_ID --bucket=BUCKET @@ -9,17 +10,17 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Displays information about a link. + (ALPHA) Display information about a linked dataset. EXAMPLES - To describe a link in a project, run: + To describe a linked dataset in a project, run: $ gcloud alpha logging links describe my-link --bucket=my-bucket \ --location=global POSITIONAL ARGUMENTS LINK_ID - Id of the link to describe. + Id of the linked dataset to describe. REQUIRED FLAGS --bucket=BUCKET @@ -32,16 +33,16 @@ OPTIONAL FLAGS At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID - Billing account of the link to describe. + Billing account of the linked dataset to describe. --folder=FOLDER_ID - Folder of the link to describe. + Folder of the linked dataset to describe. --organization=ORGANIZATION_ID - Organization of the link to describe. + Organization of the linked dataset to describe. --project=PROJECT_ID - Project of the link to describe. + Project of the linked dataset to describe. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/alpha/logging/links/help b/gcloud/alpha/logging/links/help index a29da536c..44d4e87d7 100644 --- a/gcloud/alpha/logging/links/help +++ b/gcloud/alpha/logging/links/help @@ -1,12 +1,12 @@ NAME - gcloud alpha logging links - manage log links + gcloud alpha logging links - manage linked datasets SYNOPSIS gcloud alpha logging links COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Commands for managing links. A log link represents a linked - BigQuery dataset that contains log data for the link's parent log bucket. + (ALPHA) Commands for managing linked datasets. A linked BigQuery dataset + contains log data for the linked dataset's parent log bucket. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,16 +17,16 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create a link on an analytics log bucket. + (ALPHA) Create a linked dataset on an analytics log bucket. delete - (ALPHA) Delete a link. + (ALPHA) Delete a linked dataset. describe - (ALPHA) Display information about a link. + (ALPHA) Display information about a linked dataset. list - (ALPHA) List created links on the specified bucket. + (ALPHA) List created linked datasets on the specified bucket. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/logging/links/list b/gcloud/alpha/logging/links/list index 9c08fe956..43bf926e1 100644 --- a/gcloud/alpha/logging/links/list +++ b/gcloud/alpha/logging/links/list @@ -1,6 +1,6 @@ NAME - gcloud alpha logging links list - list created links on the specified - bucket + gcloud alpha logging links list - list created linked datasets on the + specified bucket SYNOPSIS gcloud alpha logging links list --bucket=BUCKET --location=LOCATION @@ -10,10 +10,10 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Lists the links created for a bucket. + (ALPHA) List the linked datasets created for a bucket. EXAMPLES - To list the links created for a bucket, run: + To list the linked datasets created for a bucket, run: $ gcloud alpha logging links list @@ -28,16 +28,16 @@ FLAGS At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID - Billing account of the links to list. + Billing account of the linked datasets to list. --folder=FOLDER_ID - Folder of the links to list. + Folder of the linked datasets to list. --organization=ORGANIZATION_ID - Organization of the links to list. + Organization of the linked datasets to list. --project=PROJECT_ID - Project of the links to list. + Project of the linked datasets to list. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/alpha/metastore/services/create b/gcloud/alpha/metastore/services/create index 99f6a507b..938dfdb44 100644 --- a/gcloud/alpha/metastore/services/create +++ b/gcloud/alpha/metastore/services/create @@ -10,13 +10,15 @@ SYNOPSIS [--endpoint-protocol=ENDPOINT_PROTOCOL; default="thrift"] [--hive-metastore-version=HIVE_METASTORE_VERSION] [--labels=[KEY=VALUE,...]] [--port=PORT; default=9083] - [--release-channel=RELEASE_CHANNEL; default="stable"] [--tier=TIER] + [--release-channel=RELEASE_CHANNEL; default="stable"] [--auxiliary-versions=[AUXILIARY_VERSIONS,...] | --auxiliary-versions-from-file=AUXILIARY_VERSIONS_FROM_FILE] [--consumer-subnetworks=[CONSUMER_SUBNETWORKS,...] | --network=NETWORK | --network-config-from-file=NETWORK_CONFIG_FROM_FILE] [--hive-metastore-configs=KEY=VALUE | --hive-metastore-configs-from-file=HIVE_METASTORE_CONFIGS_FROM_FILE] + [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR + | --tier=TIER] [--kerberos-principal=KERBEROS_PRINCIPAL --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY @@ -149,18 +151,6 @@ FLAGS The STABLE release channel contains features that are considered stable and have been validated for production use. - --tier=TIER - The tier of the service. TIER must be one of: - - developer - The developer tier provides limited scalability and no fault - tolerance. Good for low-cost proof-of-concept. - - enterprise - The enterprise tier provides multi-zone high availability, and - sufficient scalability for enterprise-level Dataproc Metastore - workloads. - Auxiliary versions configuration for the Dataproc Metastore service. When specified, a secondary Hive metastore service is created along with the primary service. @@ -253,6 +243,46 @@ FLAGS + The instance size of the Dataproc Metastore instance. + + At most one of these can be specified: + + --instance-size=INSTANCE_SIZE + The instance size of the service. INSTANCE_SIZE must be one of: + + extra_large + Extra large instance size, maps to a scaling factor of 6.0. + + extra_small + Extra small instance size, maps to a scaling factor of 0.1. + + large + Large instance size, maps to a scaling factor of 3.0. + + medium + Medium instance size, maps to a scaling factor of 1.0. + + small + Small instance size, maps to a scaling factor of 0.5. + + --scaling-factor=SCALING_FACTOR + The scaling factor of the service. This should be a float in the + range [0.1,6.0]. If the value is less than 1.0, then it should be a + multiple of 0.1. If the value is greater than 1.0, then it should be + a whole number. Float values should be formatted as x.y. + + --tier=TIER + The tier of the service. TIER must be one of: + + developer + The developer tier provides limited scalability and no fault + tolerance. Good for low-cost proof-of-concept. + + enterprise + The enterprise tier provides multi-zone high availability, and + sufficient scalability for enterprise-level Dataproc Metastore + workloads. + Information used to configure the Hive metastore service as a service principal in a Kerberos realm. diff --git a/gcloud/alpha/metastore/services/update b/gcloud/alpha/metastore/services/update index f09a19c16..d171d1d67 100644 --- a/gcloud/alpha/metastore/services/update +++ b/gcloud/alpha/metastore/services/update @@ -5,8 +5,10 @@ NAME SYNOPSIS gcloud alpha metastore services update (SERVICE : --location=LOCATION) [--async] [--data-catalog-sync] [--endpoint-protocol=ENDPOINT_PROTOCOL] - [--port=PORT] [--tier=TIER] [--update-labels=[KEY=VALUE,...]] + [--port=PORT] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] + [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR + | --tier=TIER] [--kerberos-principal=KERBEROS_PRINCIPAL --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY @@ -89,18 +91,6 @@ FLAGS --port=PORT The TCP port on which the Metastore service will listen. - --tier=TIER - The tier of the service. TIER must be one of: - - developer - The developer tier provides limited scalability and no fault - tolerance. Good for low-cost proof-of-concept. - - enterprise - The enterprise tier provides multi-zone high availability, and - sufficient scalability for enterprise-level Dataproc Metastore - workloads. - --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. @@ -130,6 +120,46 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + The instance size of the Dataproc Metastore instance. + + At most one of these can be specified: + + --instance-size=INSTANCE_SIZE + The instance size of the service. INSTANCE_SIZE must be one of: + + extra_large + Extra large instance size, maps to a scaling factor of 6.0. + + extra_small + Extra small instance size, maps to a scaling factor of 0.1. + + large + Large instance size, maps to a scaling factor of 3.0. + + medium + Medium instance size, maps to a scaling factor of 1.0. + + small + Small instance size, maps to a scaling factor of 0.5. + + --scaling-factor=SCALING_FACTOR + The scaling factor of the service. This should be a float in the + range [0.1,6.0]. If the value is less than 1.0, then it should be a + multiple of 0.1. If the value is greater than 1.0, then it should be + a whole number. + + --tier=TIER + The tier of the service. TIER must be one of: + + developer + The developer tier provides limited scalability and no fault + tolerance. Good for low-cost proof-of-concept. + + enterprise + The enterprise tier provides multi-zone high availability, and + sufficient scalability for enterprise-level Dataproc Metastore + workloads. + Information used to configure the Hive metastore service as a service principal in a Kerberos realm. diff --git a/gcloud/alpha/monitoring/help b/gcloud/alpha/monitoring/help index 57e0617c2..a985cc5a5 100644 --- a/gcloud/alpha/monitoring/help +++ b/gcloud/alpha/monitoring/help @@ -38,6 +38,9 @@ GROUPS policies (ALPHA) Manage Cloud Monitoring alerting policies. + snoozes + (ALPHA) Manage Cloud Monitoring snoozes. + 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/monitoring/snoozes/cancel b/gcloud/alpha/monitoring/snoozes/cancel new file mode 100644 index 000000000..3d721e39f --- /dev/null +++ b/gcloud/alpha/monitoring/snoozes/cancel @@ -0,0 +1,52 @@ +NAME + gcloud alpha monitoring snoozes cancel - cancels a snooze + +SYNOPSIS + gcloud alpha monitoring snoozes cancel SNOOZE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancels a snooze. + + If the snooze is upcoming, i.e. the start time is in the future, then this + command is equivalent to: + + ▪ update --start-time="+PT1S" --end-time="+PT1S + + Otherwise, if the snooze is active, i.e. the start time is past and the + ending time is in the future, then this command is equivalent to: + + ▪ update --end-time="+PT1S + + For information about the JSON/YAML format of a snooze: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.snoozes + +POSITIONAL ARGUMENTS + Snooze resource - Name of the Snooze to be canceled. 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 snooze 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. + + SNOOZE + ID of the Snooze or fully qualified identifier for the Snooze. To set + the snooze attribute: + ▸ provide the argument snooze on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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/monitoring/snoozes/create b/gcloud/alpha/monitoring/snoozes/create new file mode 100644 index 000000000..5b2da20be --- /dev/null +++ b/gcloud/alpha/monitoring/snoozes/create @@ -0,0 +1,53 @@ +NAME + gcloud alpha monitoring snoozes create - create a new snooze + +SYNOPSIS + gcloud alpha monitoring snoozes create + [--snooze-from-file=SNOOZE_FROM_FILE] + [--criteria-policies=CRITERIA_POLICIES,[...] + --display-name=DISPLAY_NAME + --end-time=END_TIME --start-time=START_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Creates a new snooze. A snooze can be specified as a JSON/YAML + value passed in as a file through the --snooze-from-file flag. A snooze can + also be specified through command line flags. If a snooze is specified + through --snooze-from-file, and additional flags are supplied, the flags + will override the snooze's settings. + + For information about the JSON/YAML format of a snooze: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.snoozes + +FLAGS + --snooze-from-file=SNOOZE_FROM_FILE + The path to a JSON or YAML file containing the snooze. + + Snooze Settings. If any of these are specified, they will overwrite fields + in the --snooze-from-file flags if specified. + + --criteria-policies=CRITERIA_POLICIES,[...] + The policies that the Snooze applies to. + + --display-name=DISPLAY_NAME + The display name for the Snooze. + + --end-time=END_TIME + The start time for the Snooze. + + --start-time=START_TIME + The start time for the Snooze. + +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/monitoring/snoozes/describe b/gcloud/alpha/monitoring/snoozes/describe new file mode 100644 index 000000000..0f19ad03d --- /dev/null +++ b/gcloud/alpha/monitoring/snoozes/describe @@ -0,0 +1,39 @@ +NAME + gcloud alpha monitoring snoozes describe - describe a snooze + +SYNOPSIS + gcloud alpha monitoring snoozes describe SNOOZE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a snooze. + +POSITIONAL ARGUMENTS + Snooze resource - Name of the Snooze to be described. 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 snooze 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. + + SNOOZE + ID of the Snooze or fully qualified identifier for the Snooze. To set + the snooze attribute: + ▸ provide the argument snooze on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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/monitoring/snoozes/help b/gcloud/alpha/monitoring/snoozes/help new file mode 100644 index 000000000..615a46bc2 --- /dev/null +++ b/gcloud/alpha/monitoring/snoozes/help @@ -0,0 +1,41 @@ +NAME + gcloud alpha monitoring snoozes - manage Cloud Monitoring snoozes + +SYNOPSIS + gcloud alpha monitoring snoozes COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Monitoring snoozes. + + More information can be found here: + https://cloud.google.com/monitoring/api/v3/ + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (ALPHA) Cancels a snooze. + + create + (ALPHA) Create a new snooze. + + describe + (ALPHA) Describe a snooze. + + list + (ALPHA) List snoozes. + + update + (ALPHA) Updates a snooze. + +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/monitoring/snoozes/list b/gcloud/alpha/monitoring/snoozes/list new file mode 100644 index 000000000..38db39ab8 --- /dev/null +++ b/gcloud/alpha/monitoring/snoozes/list @@ -0,0 +1,86 @@ +NAME + gcloud alpha monitoring snoozes list - list snoozes + +SYNOPSIS + gcloud alpha monitoring snoozes list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List snoozes. + +EXAMPLES + To order your results first by the snooze's display name and then the end + time: + + $ gcloud alpha monitoring snoozes list \ + --sort-by=display_name,interval.end_time + + To order your results in reverse order, you can add '~' in front of the + field name: + + $ gcloud alpha monitoring snoozes list --sort-by="~display_name" + + To return results with past, i.e. historical, snoozes only: + + $ gcloud alpha monitoring snoozes list \ + --filter="interval.end_time<+PT1S" + + To return results whose display name contain the word 'cloud': + + $ gcloud alpha monitoring snoozes list \ + --filter="display_name:(cloud)" + + More information can be found at + https://cloud.google.com/sdk/gcloud/reference/topic/filters + +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 monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +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/monitoring/snoozes/update b/gcloud/alpha/monitoring/snoozes/update new file mode 100644 index 000000000..e8dd08c56 --- /dev/null +++ b/gcloud/alpha/monitoring/snoozes/update @@ -0,0 +1,78 @@ +NAME + gcloud alpha monitoring snoozes update - updates a snooze + +SYNOPSIS + gcloud alpha monitoring snoozes update SNOOZE + [--snooze-from-file=SNOOZE_FROM_FILE] + [--fields=[field,...] | --display-name=DISPLAY_NAME + --end-time=END_TIME --start-time=START_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates a snooze. + + If `--snooze-from-file` is specified: + + * If `--fields` is specified, then only the specified fields will be + updated. + * Else, the snooze will be replaced with the provided snooze. The + snooze can be modified further using the flags from the Snooze + Settings group below. + + Otherwise, the snooze will be updated with the values specified in the + flags from the Snooze Settings group. + + For information about the JSON/YAML format of a snooze: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.snoozes + +POSITIONAL ARGUMENTS + Snooze resource - Name of the Snooze to be updated. 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 snooze 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. + + SNOOZE + ID of the Snooze or fully qualified identifier for the Snooze. To set + the snooze attribute: + ▸ provide the argument snooze on the command line. + +FLAGS + --snooze-from-file=SNOOZE_FROM_FILE + The path to a JSON or YAML file containing the snooze. + + At most one of these can be specified: + + --fields=[field,...] + The list of fields to update. Must specify --snooze-from-file if + using this flag. + + Snooze Settings. If any of these are specified, they will overwrite + fields in the --snooze-from-file flags if specified. + + --display-name=DISPLAY_NAME + The display name for the Snooze. + + --end-time=END_TIME + The start time for the Snooze. + + --start-time=START_TIME + The start time for the Snooze. + +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/scc/custom-modules/sha/create b/gcloud/alpha/scc/custom-modules/sha/create index c24b41449..987a82dc4 100644 --- a/gcloud/alpha/scc/custom-modules/sha/create +++ b/gcloud/alpha/scc/custom-modules/sha/create @@ -6,7 +6,6 @@ SYNOPSIS gcloud alpha scc custom-modules sha create --custom-config-from-file=CUSTOM_CONFIG_FROM_FILE --display-name=DISPLAY_NAME --enablement-state=ENABLEMENT_STATE - [--description=DESCRIPTION] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -19,12 +18,10 @@ EXAMPLES $ gcloud alpha scc custom-modules sha create \ --organization=organizations/123 \ - --description="This is a test custom module" \ --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml $ gcloud alpha scc custom-modules sha create --organization=123 \ - --description="This is a test custom module" \ --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml @@ -33,12 +30,10 @@ EXAMPLES run: $ gcloud alpha scc custom-modules sha create --folder=folders/456 \ - --description="This is a test custom module" \ --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml $ gcloud alpha scc custom-modules sha create --folder=456 \ - --description="This is a test custom module" \ --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml @@ -47,14 +42,10 @@ EXAMPLES run: $ gcloud alpha scc custom-modules sha create \ - --project=projects/789 \ - --description="This is a test custom module" \ - --display-name="Test display name" \ + --project=projects/789 --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml - $ gcloud alpha scc custom-modules sha create --project=789 \ - --description="This is a test custom module" \ --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml @@ -74,10 +65,6 @@ REQUIRED FLAGS enablement-state-unspecified, inherited. OPTIONAL FLAGS - --description=DESCRIPTION - The text that will be used to describe a Security Health Analytics - custom module. Description must be at most 1024 characters - At most one of these can be specified: --folder=FOLDER diff --git a/gcloud/alpha/scc/custom-modules/sha/delete b/gcloud/alpha/scc/custom-modules/sha/delete index ee93f0875..6984e590d 100644 --- a/gcloud/alpha/scc/custom-modules/sha/delete +++ b/gcloud/alpha/scc/custom-modules/sha/delete @@ -23,7 +23,7 @@ EXAMPLES customModules/123456 To delete a Security Health Analytics custom module with id 123456 for - folder 456 , run: + folder 456, run: $ gcloud alpha scc custom-modules sha delete 123456 \ --folder=folders/456 diff --git a/gcloud/alpha/scc/custom-modules/sha/get b/gcloud/alpha/scc/custom-modules/sha/get index 6bfaa9a12..8604cf1f4 100644 --- a/gcloud/alpha/scc/custom-modules/sha/get +++ b/gcloud/alpha/scc/custom-modules/sha/get @@ -12,7 +12,7 @@ DESCRIPTION EXAMPLES To get a Security Health Analytics custom module with id 123456 for - organization 123 , run: + organization 123, run: $ gcloud alpha scc custom-modules sha get 123456 \ --organization=organizations/123 diff --git a/gcloud/alpha/scc/custom-modules/sha/get-effective b/gcloud/alpha/scc/custom-modules/sha/get-effective index be4b2b0a5..4482f51d6 100644 --- a/gcloud/alpha/scc/custom-modules/sha/get-effective +++ b/gcloud/alpha/scc/custom-modules/sha/get-effective @@ -12,7 +12,7 @@ DESCRIPTION EXAMPLES To get an effective Security Health Analytics custom module with id 123456 - for organization 123 , run: + for organization 123, run: $ gcloud alpha scc custom-modules sha get-effective 123456 \ --organization=organizations/123 diff --git a/gcloud/alpha/scc/custom-modules/sha/list b/gcloud/alpha/scc/custom-modules/sha/list index 8d4da2478..049838d58 100644 --- a/gcloud/alpha/scc/custom-modules/sha/list +++ b/gcloud/alpha/scc/custom-modules/sha/list @@ -12,18 +12,19 @@ DESCRIPTION (ALPHA) List Security Health Analytics custom modules. EXAMPLES - List Security Health Analytics custom modules under organization 123: + To list Security Health Analytics custom modules under organization 123, + run: $ gcloud alpha scc custom-modules sha list \ --organization=organizations/123 $ gcloud alpha scc custom-modules sha list --organization=123 - List Security Health Analytics custom modules under folder 456: + To list Security Health Analytics custom modules under folder 456, run: $ gcloud alpha scc custom-modules sha list --folder=folders/456 $ gcloud alpha scc custom-modules sha list --folder=456 - List Security Health Analytics custom modules under project 789: + To list Security Health Analytics custom modules under project 789, run: $ gcloud alpha scc custom-modules sha list --project=projects/789 $ gcloud alpha scc custom-modules sha list --project=789 diff --git a/gcloud/alpha/scc/custom-modules/sha/list-descendant b/gcloud/alpha/scc/custom-modules/sha/list-descendant index 0d5659f8f..1de5f17f3 100644 --- a/gcloud/alpha/scc/custom-modules/sha/list-descendant +++ b/gcloud/alpha/scc/custom-modules/sha/list-descendant @@ -12,21 +12,23 @@ DESCRIPTION (ALPHA) List Descendant Security Health Analytics custom modules. EXAMPLES - List Descendant Security Health Analytics custom modules under organization - 123: + To list Descendant Security Health Analytics custom modules under + organization 123, run: $ gcloud alpha scc custom-modules sha list-descendant \ --organization=organizations/123 $ gcloud alpha scc custom-modules sha list-descendant \ --organization=123 - List Descendant Security Health Analytics custom modules under folder 456: + To list Descendant Security Health Analytics custom modules under folder + 456, run: $ gcloud alpha scc custom-modules sha list-descendant \ --folder=folders/456 $ gcloud alpha scc custom-modules sha list-descendant --folder=456 - List Descendant Security Health Analytics custom modules under project 789: + To list Descendant Security Health Analytics custom modules under project + 789, run: $ gcloud alpha scc custom-modules sha list-descendant \ --project=projects/789 diff --git a/gcloud/alpha/scc/custom-modules/sha/list-effective b/gcloud/alpha/scc/custom-modules/sha/list-effective index 212cfe91d..acc9057b7 100644 --- a/gcloud/alpha/scc/custom-modules/sha/list-effective +++ b/gcloud/alpha/scc/custom-modules/sha/list-effective @@ -12,21 +12,23 @@ DESCRIPTION (ALPHA) List Effective Security Health Analytics custom modules. EXAMPLES - List Effective Security Health Analytics custom modules under organization - 123: + To list Effective Security Health Analytics custom modules under + organization 123, run: $ gcloud alpha scc custom-modules sha list-effective \ --organization=organizations/123 $ gcloud alpha scc custom-modules sha list-effective \ --organization=123 - List Effective Security Health Analytics custom modules under folder 456: + To list Effective Security Health Analytics custom modules under folder + 456, run: $ gcloud alpha scc custom-modules sha list-effective \ --folder=folders/456 $ gcloud alpha scc custom-modules sha list-effective --folder=456 - List Effective Security Health Analytics custom modules under project 789: + To list Effective Security Health Analytics custom modules under project + 789, run: $ gcloud alpha scc custom-modules sha list-effective \ --project=projects/789 diff --git a/gcloud/alpha/scc/custom-modules/sha/test b/gcloud/alpha/scc/custom-modules/sha/test index af89ae799..ed1f3839e 100644 --- a/gcloud/alpha/scc/custom-modules/sha/test +++ b/gcloud/alpha/scc/custom-modules/sha/test @@ -6,8 +6,7 @@ SYNOPSIS gcloud alpha scc custom-modules sha test CUSTOM_MODULE --test-data-from-file=TEST_DATA_FROM_FILE [--custom-config-from-file=CUSTOM_CONFIG_FROM_FILE] - [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] - [--enablement-state=ENABLEMENT_STATE] + [--display-name=DISPLAY_NAME] [--enablement-state=ENABLEMENT_STATE] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -20,19 +19,17 @@ EXAMPLES $ gcloud alpha scc custom-modules sha test 123456 \ --organization=organizations/123 \ - --description="This is a test custom module" \ --display-name="Test display name"--enablement-state="ENABLED" \ --custom-config-from-file=/tmp/custom_config.yaml \ --test-data-from-file=/tmp/test_data.yaml $ gcloud alpha scc custom-modules sha test 123456 \ --organization=123 \ - --description="This is a test custom module" \ --display-name="Test display name"--enablement-state="ENABLED" \ --custom-config-from-file=/tmp/custom_config.yaml \ --test-data-from-file=/tmp/test_data.yaml $ gcloud alpha scc custom-modules sha test \ organizations/123/securityHealthAnalyticsSettings/\ - customModules/123456 --description="This is a test custom module" \ + customModules/123456 \ --display-name="Test display name"--enablement-state="ENABLED" \ --custom-config-from-file=/tmp/custom_config.yaml \ --test-data-from-file=/tmp/test_data.yaml @@ -42,18 +39,16 @@ EXAMPLES $ gcloud alpha scc custom-modules sha test 123456 \ --folder=folders/456 \ - --description="This is a test custom module" \ --display-name="Test display name"--enablement-state="ENABLED" \ --custom-config-from-file=/tmp/custom_config.yaml \ --test-data-from-file=/tmp/test_data.yaml $ gcloud alpha scc custom-modules sha test 123456 --folder=456 \ - --description="This is a test custom module" \ --display-name="Test display name"--enablement-state="ENABLED" \ --custom-config-from-file=/tmp/custom_config.yaml \ --test-data-from-file=/tmp/test_data.yaml $ gcloud alpha scc custom-modules sha test \ folders/456/securityHealthAnalyticsSettings/customModules/\ - 123456 --description="This is a test custom module" \ + 123456 \ --display-name="Test display name"--enablement-state="ENABLED" \ --custom-config-from-file=/tmp/custom_config.yaml \ --test-data-from-file=/tmp/test_data.yaml @@ -63,18 +58,16 @@ EXAMPLES $ gcloud alpha scc custom-modules sha test 123456 \ --project=projects/789 \ - --description="This is a test custom module" \ --display-name="Test display name"--enablement-state="ENABLED" \ --custom-config-from-file=/tmp/custom_config.yaml \ --test-data-from-file=/tmp/test_data.yaml $ gcloud alpha scc custom-modules sha test 123456 --project=789 \ - --description="This is a test custom module" \ --display-name="Test display name"--enablement-state="ENABLED" \ --custom-config-from-file=/tmp/custom_config.yaml \ --test-data-from-file=/tmp/test_data.yaml $ gcloud alpha scc custom-modules sha test \ projects/789/securityHealthAnalyticsSettings/customModules/\ - 123456 --description="This is a test custom module" \ + 123456 \ --display-name="Test display name"--enablement-state="ENABLED" \ --custom-config-from-file=/tmp/custom_config.yaml \ --test-data-from-file=/tmp/test_data.yaml @@ -94,10 +87,6 @@ OPTIONAL FLAGS Path to a yaml file containing the custom configuration for the Security Health Analytics custom module. - --description=DESCRIPTION - The text that will be used to describe a Security Health Analytics - custom module. Description must be at most 1024 characters. - --display-name=DISPLAY_NAME The text that will be used to represent a Security Health Analytics custom module display name. Display name must be at most 64 characters. diff --git a/gcloud/alpha/scc/custom-modules/sha/update b/gcloud/alpha/scc/custom-modules/sha/update index 3702b38dd..02d638309 100644 --- a/gcloud/alpha/scc/custom-modules/sha/update +++ b/gcloud/alpha/scc/custom-modules/sha/update @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud alpha scc custom-modules sha update CUSTOM_MODULE [--custom-config-from-file=CUSTOM_CONFIG_FROM_FILE] - [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] - [--enablement-state=ENABLEMENT_STATE] [--update-mask=UPDATE_MASK] + [--display-name=DISPLAY_NAME] [--enablement-state=ENABLEMENT_STATE] + [--update-mask=UPDATE_MASK] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -14,67 +14,55 @@ DESCRIPTION (ALPHA) Update a Security Health Analytics custom module. EXAMPLES - Update a Security Health Analytics custom module with id 123456 for - organization 123: + To update a Security Health Analytics custom module with id 123456 for + organization 123, run: $ gcloud alpha scc custom-modules sha update 123456 \ --organization=organizations/123 \ - --description="This is a test custom module" \ --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml $ gcloud alpha scc custom-modules sha update 123456 \ - --organization=123 \ - --description="This is a test custom module" \ - --display-name="Test display name" \ + --organization=123 --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml $ gcloud alpha scc custom-modules sha update \ organizations/123/securityHealthAnalyticsSettings/\ - customModules/123456 --description="This is a test custom module" \ - --display-name="Test display name" \ + customModules/123456 --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml - Update a Security Health Analytics custom module with id 123456 for folder - 456: + To update a Security Health Analytics custom module with id 123456 for + folder 456, run: $ gcloud alpha scc custom-modules sha update 123456 \ - --folder=folders/456 \ - --description="This is a test custom module" \ - --display-name="Test display name" \ + --folder=folders/456 --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml $ gcloud alpha scc custom-modules sha update 123456 --folder=456 \ - --description="This is a test custom module" \ --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml $ gcloud alpha scc custom-modules sha update \ folders/456/securityHealthAnalyticsSettings/customModules/\ - 123456 --description="This is a test custom module" \ - --display-name="Test display name" \ + 123456 --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml - Update a Security Health Analytics custom module with id 123456 for project - 789: + To update a Security Health Analytics custom module with id 123456 for + project 789, run: $ gcloud alpha scc custom-modules sha update 123456 \ - --project=projects/789 \ - --description="This is a test custom module" \ - --display-name="Test display name" \ + --project=projects/789 --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml $ gcloud alpha scc custom-modules sha update 123456 --project=789 \ - --description="This is a test custom module" \ --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml $ gcloud alpha scc custom-modules sha update \ projects/789/securityHealthAnalyticsSettings/customModules/\ - 123456 --description="This is a test custom module" \ - --display-name="Test display name" \ + 123456 --display-name="Test display name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml @@ -88,10 +76,6 @@ FLAGS Path to a yaml file containing the custom configuration for the Security Health Analytics custom module. - --description=DESCRIPTION - The text that will be used to describe a Security Health Analytics - custom module. Description must be at most 1024 characters - --display-name=DISPLAY_NAME The text that will be used to represent a Security Health Analytics custom module display name. Display name must be at most 64 characters diff --git a/gcloud/alpha/services/api-keys/undelete b/gcloud/alpha/services/api-keys/undelete index 876b37010..4e1f6e6a8 100644 --- a/gcloud/alpha/services/api-keys/undelete +++ b/gcloud/alpha/services/api-keys/undelete @@ -2,8 +2,9 @@ NAME gcloud alpha services api-keys undelete - undelete an API key SYNOPSIS - gcloud alpha services api-keys undelete (KEY : --location=LOCATION) - [--async] [GCLOUD_WIDE_FLAG ...] + gcloud alpha services api-keys undelete + ([KEY : --location=LOCATION] --key-string=KEY_STRING) [--async] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) API Keys that are deleted will be retained in the system for 30 @@ -11,39 +12,51 @@ DESCRIPTION with this command. EXAMPLES - UnDelete an API Key : + UnDelete an API Key (Key or key-string should be specified): - $ gcloud alpha services api-keys undelete \ - projects/myproject/locations/global/keys/1234 + To undelete with key `1234`, run: $ gcloud alpha services api-keys undelete 1234 + To undelete with `1234` in project + `myproject` using the fully qualified API key name, run: + + $ gcloud alpha services api-keys undelete \ + projects/myproject/locations/global/keys/1234 + + To undelete using a Key-string, run: + + $gcloud alpha services api-keys undelete --key-string='my-key-string' + POSITIONAL ARGUMENTS - Key resource - The name of the key to undelete. 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 key on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. + Exactly one of these must be specified: - This must be specified. + Key resource - The name of the key to undelete. 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 key on the command line with a fully specified + name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. - KEY - ID of the key or fully qualified identifier for the key. To set the - key attribute: - ▸ provide the argument key on the command line. + KEY + ID of the key or fully qualified identifier for the key. To set the + key attribute: + ▫ provide the argument key on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. + This positional argument must be specified if any of the other + arguments in this group are specified. - --location=LOCATION - Location of the key. To set the location attribute: - ▸ provide the argument key on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ location will default to global. + --location=LOCATION + Location of the key. To set the location attribute: + ▫ provide the argument key on the command line with a fully + specified name; + ▫ provide the argument --location on the command line; + ▫ location will default to global. + + --key-string=KEY_STRING + Key String of the key. FLAGS --async diff --git a/gcloud/alpha/services/api-keys/update b/gcloud/alpha/services/api-keys/update index 6516a6919..4901dad1f 100644 --- a/gcloud/alpha/services/api-keys/update +++ b/gcloud/alpha/services/api-keys/update @@ -27,7 +27,7 @@ EXAMPLES projects/myproject/keys/my-key-id --display-name="test name" \ --allowed-ips=2620:15c:2c4:203:2776:1f90:6b3b:217,104.133.8.78 - To update annoatations: + To update annotations: $ gcloud alpha services api-keys update \ projects/myproject/keys/my-key-id --annotations=foo=bar,abc=def diff --git a/gcloud/alpha/spanner/databases/roles/help b/gcloud/alpha/spanner/databases/roles/help index a4b2188ff..ca87e6069 100644 --- a/gcloud/alpha/spanner/databases/roles/help +++ b/gcloud/alpha/spanner/databases/roles/help @@ -16,14 +16,16 @@ COMMANDS COMMAND is one of the following: list - (ALPHA) List the Cloud Spanner database roles contained within the - given database. + (ALPHA) List the Cloud Spanner database roles defined in the given + database. 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 spanner databases roles $ gcloud beta spanner databases roles diff --git a/gcloud/alpha/spanner/databases/roles/list b/gcloud/alpha/spanner/databases/roles/list index d95d9827b..b9b42fdd8 100644 --- a/gcloud/alpha/spanner/databases/roles/list +++ b/gcloud/alpha/spanner/databases/roles/list @@ -1,6 +1,6 @@ NAME gcloud alpha spanner databases roles list - list the Cloud Spanner database - roles contained within the given database + roles defined in the given database SYNOPSIS gcloud alpha spanner databases roles list @@ -9,7 +9,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List the Cloud Spanner database roles contained within the given + (ALPHA) List the Cloud Spanner database roles defined in the given database. EXAMPLES @@ -90,7 +90,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 spanner databases roles list $ gcloud beta spanner databases roles list diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index 61bb0fd3d..485acad54 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -17,7 +17,7 @@ SYNOPSIS [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--diff] [--[no-]enable-bin-log] [--[no-]enable-database-replication] - [--enable-google-private-path] [--enable-password-policy] + [--[no-]enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] [--follow-gae-app=FOLLOW_GAE_APP] [--[no-]insights-config-query-insights-enabled] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -169,12 +169,13 @@ FLAGS --enable-database-replication to enable and --no-enable-database-replication to disable. - --enable-google-private-path + --[no-]enable-google-private-path Enable a private path for Google Cloud services. This flag specifies whether the instance is accessible to internal Google Cloud services such as BigQuery. This is only applicable to MySQL and PostgreSQL instances that don't use public IP. Currently, SQL Server isn't - supported. + supported. Use --enable-google-private-path to enable and + --no-enable-google-private-path to disable. --enable-password-policy Enable the password policy, which enforces user password management diff --git a/gcloud/alpha/terraform/help b/gcloud/alpha/terraform/help index d95860d71..4e21a21bb 100644 --- a/gcloud/alpha/terraform/help +++ b/gcloud/alpha/terraform/help @@ -3,7 +3,7 @@ NAME Cloud Platform resources SYNOPSIS - gcloud alpha terraform COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha terraform GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Commands related to Terraform management of Google Cloud Platform diff --git a/gcloud/beta/alloydb/instances/restart b/gcloud/beta/alloydb/instances/restart index 212c7b3ba..6d95546a4 100644 --- a/gcloud/beta/alloydb/instances/restart +++ b/gcloud/beta/alloydb/instances/restart @@ -10,7 +10,7 @@ DESCRIPTION (BETA) Restarts an AlloyDB instance within a given cluster. EXAMPLES - To describe an instance, run: + To restart an instance, run: $ gcloud beta alloydb instances restart my-instance \ --cluster=my-cluster --region=us-central1 diff --git a/gcloud/beta/builds/connections/add-iam-policy-binding b/gcloud/beta/builds/connections/add-iam-policy-binding index 6ce1dd3ec..c4db24ddd 100644 --- a/gcloud/beta/builds/connections/add-iam-policy-binding +++ b/gcloud/beta/builds/connections/add-iam-policy-binding @@ -5,8 +5,7 @@ NAME SYNOPSIS gcloud beta builds connections add-iam-policy-binding (CONNECTION : --region=REGION) --member=PRINCIPAL --role=ROLE - [--condition=[KEY=VALUE,...] - | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Add IAM policy binding to a Cloud Build connection. One binding @@ -70,44 +69,6 @@ REQUIRED FLAGS for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer. -OPTIONAL FLAGS - At most one of these can be specified: - - --condition=[KEY=VALUE,...] - A condition to include in the binding. When the condition is - explicitly specified as None (--condition=None), a binding without a - condition is added. When the condition is specified and is not None, - --role cannot be a basic role. Basic roles are roles/editor, - roles/owner, and roles/viewer. For more on conditions, refer to the - conditions overview guide: - https://cloud.google.com/iam/docs/conditions-overview - - When using the --condition flag, include the following key-value - pairs: - - expression - (Required) Condition expression that evaluates to True or False. - This uses a subset of Common Expression Language syntax. - - If the condition expression includes a comma, use a different - delimiter to separate the key-value pairs. Specify the delimiter - before listing the key-value pairs. For example, to specify a - colon (:) as the delimiter, do the following: - --condition=^:^title=TITLE:expression=EXPRESSION. For more - information, see - https://cloud.google.com/sdk/gcloud/reference/topic/escaping. - - title - (Required) A short string describing the purpose of the - expression. - - description - (Optional) Additional description for the expression. - - --condition-from-file=CONDITION_FROM_FILE - Path to a local JSON or YAML file that defines the condition. To see - available fields, see the help for --condition. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/composer/environments/run b/gcloud/beta/composer/environments/run index 8072a8b77..e2751a969 100644 --- a/gcloud/beta/composer/environments/run +++ b/gcloud/beta/composer/environments/run @@ -13,8 +13,20 @@ DESCRIPTION sub-command to complete; its exit code will match the sub-command's exit code. + Note: Airflow CLI sub-command syntax differs between Airflow 1 and Airflow + 2. Refer to the Airflow CLI reference documentation for more details. + EXAMPLES - The following command: + The following command in environments with Airflow 2: + + gcloud beta composer environments run myenv dags trigger -- some_dag --run_id=foo + + is equivalent to running the following command from a shell inside the + my-environment environment: + + airflow dags trigger --run_id=foo some_dag + + The same command, but for environments with Airflow 1.10.14+: gcloud beta composer environments run myenv trigger_dag -- some_dag --run_id=foo diff --git a/gcloud/beta/compute/instances/ops-agents/policies/create b/gcloud/beta/compute/instances/ops-agents/policies/create index 1690424e8..603e86b2c 100644 --- a/gcloud/beta/compute/instances/ops-agents/policies/create +++ b/gcloud/beta/compute/instances/ops-agents/policies/create @@ -229,8 +229,10 @@ REQUIRED FLAGS debian 11 debian 10 debian 9 + rhel 9.* rhel 8.* rhel 7.* + rocky 9.* rocky 8.* sles 12.* sles 15.* @@ -249,8 +251,8 @@ REQUIRED FLAGS short-name Short name of the OS. - Required. Allowed values: centos, debian, rhel, sles, sles_sap, - ubuntu. + Required. Allowed values: centos, debian, rhel, rocky, sles, + sles_sap, ubuntu. To inspect the exact OS short name of an instance, run: diff --git a/gcloud/beta/compute/instances/ops-agents/policies/update b/gcloud/beta/compute/instances/ops-agents/policies/update index 73218338c..af4614bc7 100644 --- a/gcloud/beta/compute/instances/ops-agents/policies/update +++ b/gcloud/beta/compute/instances/ops-agents/policies/update @@ -266,8 +266,10 @@ FLAGS debian 11 debian 10 debian 9 + rhel 9.* rhel 8.* rhel 7.* + rocky 9.* rocky 8.* sles 12.* sles 15.* @@ -286,8 +288,8 @@ FLAGS short-name Short name of the OS. - Required. Allowed values: centos, debian, rhel, sles, sles_sap, - ubuntu. + Required. Allowed values: centos, debian, rhel, rocky, sles, + sles_sap, ubuntu. To inspect the exact OS short name of an instance, run: diff --git a/gcloud/beta/compute/instances/set-scheduling b/gcloud/beta/compute/instances/set-scheduling index a844e3d1f..ab75877de 100644 --- a/gcloud/beta/compute/instances/set-scheduling +++ b/gcloud/beta/compute/instances/set-scheduling @@ -11,8 +11,10 @@ SYNOPSIS [--[no-]restart-on-failure] [--zone=ZONE] [--clear-instance-termination-action | --instance-termination-action=INSTANCE_TERMINATION_ACTION] + [--clear-max-run-duration | --max-run-duration=MAX_RUN_DURATION] [--clear-node-affinities | --node=NODE | --node-affinity-file=NODE_AFFINITY_FILE | --node-group=NODE_GROUP] + [--clear-termination-time | --termination-time=TERMINATION_TIME] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -135,6 +137,33 @@ FLAGS Default. Stop the VM without preserving memory. The VM can be restarted later. + Max Run Duration + + At most one of these can be specified: + + --clear-max-run-duration + Removes the max-run-duration field from the scheduling options. + + --max-run-duration=MAX_RUN_DURATION + Limits how long this VM instance can run, specified as a duration + relative to the VM instance's most-recent start time. Format the + duration, MAX_RUN_DURATION, as the number of days, hours, minutes, + and seconds followed by d, h, m, and s respectively. For example, + specify 30m for a duration of 30 minutes or specify 1d2h3m4s for a + duration of 1 day, 2 hours, 3 minutes, and 4 seconds. Alternatively, + to specify a timestamp, use --termination-time instead. + + If neither --max-run-duration nor --termination-time is specified + (default), the VM instance runs until prompted by a user action or + system event. If either is specified, the VM instance is scheduled to + be automatically terminated using the action specified by + --instance-termination-action. For --max-run-duration, the VM + instance is automatically terminated when the VM's current runtime + reaches MAX_RUN_DURATION. Note: Anytime the VM instance is stopped or + suspended, --max-run-duration and (unless the VM uses + --provisioning-model=SPOT) --instance-termination-action are + automatically removed from the VM. + Sole Tenancy. At most one of these can be specified: @@ -171,6 +200,29 @@ FLAGS --node-group=NODE_GROUP The name of the node group to schedule this instance on. + Termination Time + + At most one of these can be specified: + + --clear-termination-time + Removes the termination-time field from the scheduling options. + + --termination-time=TERMINATION_TIME + Limits how long this VM instance can run, specified as a time. Format + the time, TERMINATION_TIME, as a RFC 3339 timestamp. For more + information, see https://tools.ietf.org/html/rfc3339. Alternatively, + to specify a duration, use --max-run-duration instead. + + If neither --termination-time nor --max-run-duration is specified + (default), the VM instance runs until prompted by a user action or + system event. If either is specified, the VM instance is scheduled to + be automatically terminated using the action specified by + --instance-termination-action. For --termination-time, the VM + instance is automatically terminated at the specified timestamp. + Note: Anytime the VM instance is stopped or suspended, + --termination-time and (unless the VM uses --provisioning-model=SPOT) + --instance-termination-action are automatically removed from the VM. + 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/interconnects/attachments/dedicated/create b/gcloud/beta/compute/interconnects/attachments/dedicated/create index 6ee9c5a15..9912098e4 100644 --- a/gcloud/beta/compute/interconnects/attachments/dedicated/create +++ b/gcloud/beta/compute/interconnects/attachments/dedicated/create @@ -9,9 +9,9 @@ SYNOPSIS [--candidate-subnets=[SUBNET,...]] [--cloud-router-ipv6-interface-id=INTERFACE_ID] [--customer-router-ipv6-interface-id=PEER_INTERFACE_ID] - [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU] - [--region=REGION] [--stack-type=STACK_TYPE] [--vlan=VLAN] - [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--enable-admin] [--encryption=ENCRYPTION] + [--ipsec-internal-addresses=[ADDRESSES]] [--mtu=MTU] [--region=REGION] + [--stack-type=STACK_TYPE] [--vlan=VLAN] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute interconnects attachments dedicated create is @@ -100,6 +100,38 @@ OPTIONAL FLAGS is operational and will carry traffic. Use --no-enable-admin to disable it. + --encryption=ENCRYPTION + Indicates the user-supplied encryption option for this interconnect + attachment (VLAN attachment). + + Possible values are: + + NONE - This is the default value, which means the interconnect + attachment carries unencrypted traffic. VMs can send traffic to or + receive traffic from such interconnect attachment. + + IPSEC - The interconnect attachment carries only traffic that is + encrypted by an IPsec device; for example, an HA VPN gateway or + third-party IPsec VPN. VMs cannot directly send traffic to or receive + traffic from such an interconnect attachment. To use HA VPN over Cloud + Interconnect, the interconnect attachment must be created with this + option. + + ENCRYPTION must be one of: IPSEC, NONE. + + --ipsec-internal-addresses=[ADDRESSES] + List of IP address range names that have been reserved for the + interconnect attachment (VLAN attachment). Use this option only for an + interconnect attachment that has its encryption option set as IPSEC. + Currently only one internal IP address range can be specified for each + attachment. When creating an HA VPN gateway for the interconnect + attachment, if the attachment is configured to use a regional internal + IP address, then the VPN gateway's IP address is allocated from the IP + address range specified here. If this field is not specified when + creating the interconnect attachment, then when creating any HA VPN + gateways for this interconnect attachment, the HA VPN gateway's IP + address is allocated from a regional external IP address pool. + --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet passing through this interconnect attachment. Only 1440 and 1500 are diff --git a/gcloud/beta/compute/interconnects/attachments/partner/create b/gcloud/beta/compute/interconnects/attachments/partner/create index 8ada7ec03..e2e7662d1 100644 --- a/gcloud/beta/compute/interconnects/attachments/partner/create +++ b/gcloud/beta/compute/interconnects/attachments/partner/create @@ -5,8 +5,9 @@ NAME SYNOPSIS gcloud beta compute interconnects attachments partner create NAME --edge-availability-domain=AVAILABILITY_DOMAIN --router=ROUTER - [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU] - [--region=REGION] [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--enable-admin] [--encryption=ENCRYPTION] + [--ipsec-internal-addresses=[ADDRESSES]] [--mtu=MTU] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute interconnects attachments partner create is used @@ -53,6 +54,38 @@ OPTIONAL FLAGS is operational and will carry traffic. Use --no-enable-admin to disable it. + --encryption=ENCRYPTION + Indicates the user-supplied encryption option for this interconnect + attachment (VLAN attachment). + + Possible values are: + + NONE - This is the default value, which means the interconnect + attachment carries unencrypted traffic. VMs can send traffic to or + receive traffic from such interconnect attachment. + + IPSEC - The interconnect attachment carries only traffic that is + encrypted by an IPsec device; for example, an HA VPN gateway or + third-party IPsec VPN. VMs cannot directly send traffic to or receive + traffic from such an interconnect attachment. To use HA VPN over Cloud + Interconnect, the interconnect attachment must be created with this + option. + + ENCRYPTION must be one of: IPSEC, NONE. + + --ipsec-internal-addresses=[ADDRESSES] + List of IP address range names that have been reserved for the + interconnect attachment (VLAN attachment). Use this option only for an + interconnect attachment that has its encryption option set as IPSEC. + Currently only one internal IP address range can be specified for each + attachment. When creating an HA VPN gateway for the interconnect + attachment, if the attachment is configured to use a regional internal + IP address, then the VPN gateway's IP address is allocated from the IP + address range specified here. If this field is not specified when + creating the interconnect attachment, then when creating any HA VPN + gateways for this interconnect attachment, the HA VPN gateway's IP + address is allocated from a regional external IP address pool. + --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet passing through this interconnect attachment. Only 1440 and 1500 are diff --git a/gcloud/beta/compute/routers/create b/gcloud/beta/compute/routers/create index c4c54ec2b..4ad798664 100644 --- a/gcloud/beta/compute/routers/create +++ b/gcloud/beta/compute/routers/create @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud beta compute routers create NAME --network=NETWORK [--advertisement-mode=MODE] [--asn=ASN] [--async] - [--description=DESCRIPTION] [--keepalive-interval=KEEPALIVE_INTERVAL] - [--region=REGION] [--set-advertisement-groups=[GROUP,...]] + [--description=DESCRIPTION] [--encrypted-interconnect-router] + [--keepalive-interval=KEEPALIVE_INTERVAL] [--region=REGION] + [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] [GCLOUD_WIDE_FLAG ...] @@ -42,6 +43,10 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional description of this router. + --encrypted-interconnect-router + Indicates if a router is dedicated for use with encrypted interconnect + attachments (VLAN attachments). + --keepalive-interval=KEEPALIVE_INTERVAL The interval between BGP keepalive messages that are sent to the peer. If set, this value must be between 20 and 60 seconds. The default is 20 diff --git a/gcloud/beta/compute/routers/nats/create b/gcloud/beta/compute/routers/nats/create index 78d1197a9..159db04c5 100644 --- a/gcloud/beta/compute/routers/nats/create +++ b/gcloud/beta/compute/routers/nats/create @@ -11,6 +11,7 @@ SYNOPSIS | --nat-primary-subnet-ip-ranges) [--async] [--[no-]enable-dynamic-port-allocation] [--enable-endpoint-independent-mapping] [--enable-logging] + [--endpoint-types=[ENDPOINT_TYPE,...]] [--icmp-idle-timeout=ICMP_IDLE_TIMEOUT] [--log-filter=LOG_FILTER] [--max-ports-per-vm=MAX_PORTS_PER_VM] [--min-ports-per-vm=MIN_PORTS_PER_VM] [--region=REGION] [--rules=RULES] @@ -111,6 +112,20 @@ OPTIONAL FLAGS gcloud beta compute routers nats update MY-NAT \ --no-enable-logging --router ROUTER --region REGION + --endpoint-types=[ENDPOINT_TYPE,...] + Endpoint Types supported by the NAT Gateway. + + ENDPOINT_TYPE must be one of: + + ENDPOINT_TYPE_VM + For VM Endpoints + ENDPOINT_TYPE_SWG + For Secure Web Gateway Endpoints + + The default is ENDPOINT_TYPE_VM. + + ENDPOINT_TYPE must be one of: ENDPOINT_TYPE_VM, ENDPOINT_TYPE_SWG. + --icmp-idle-timeout=ICMP_IDLE_TIMEOUT Timeout for ICMP connections. See https://cloud.google.com/sdk/gcloud/reference/topic/datetimes for diff --git a/gcloud/beta/compute/vpn-gateways/create b/gcloud/beta/compute/vpn-gateways/create index 2692bc411..aa63a1b88 100644 --- a/gcloud/beta/compute/vpn-gateways/create +++ b/gcloud/beta/compute/vpn-gateways/create @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud beta compute vpn-gateways create NAME --network=NETWORK - [--description=DESCRIPTION] [--region=REGION] [--stack-type=STACK_TYPE] - [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] + [--interconnect-attachments=[INTERCONNECT_ATTACHMENTS,...]] + [--region=REGION] [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute vpn-gateways create creates a new Highly @@ -35,6 +36,17 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional, textual description for the VPN gateway. + --interconnect-attachments=[INTERCONNECT_ATTACHMENTS,...] + Names of interconnect attachments (VLAN attachments) associated with + the VPN gateway interfaces. You must specify this field when using a + VPN gateway for HA VPN over Cloud Interconnect. Otherwise, this field + is optional. + + For example, --interconnect-attachments + attachment-a-zone1,attachment-a-zone2 associates VPN gateway with + attachment from zone1 on interface 0 and with attachment from zone2 on + interface 1. + --region=REGION Region of the VPN Gateway to create. If not specified, you might be prompted to select a region (interactive mode only). diff --git a/gcloud/beta/filestore/instances/snapshots/create b/gcloud/beta/filestore/instances/snapshots/create index b123ca1e6..b522d0fcf 100644 --- a/gcloud/beta/filestore/instances/snapshots/create +++ b/gcloud/beta/filestore/instances/snapshots/create @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud beta filestore instances snapshots create SNAPSHOT - --instance=INSTANCE --instance-region=INSTANCE_REGION [--async] + --instance=INSTANCE + (--instance-location=INSTANCE_LOCATION + | --instance-region=INSTANCE_REGION) [--async] [--description=DESCRIPTION] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -31,8 +33,13 @@ REQUIRED FLAGS --instance=INSTANCE Name of the Filestore instance that you want to create a snapshot of. - --instance-region=INSTANCE_REGION - Region of the Filestore instance. + Exactly one of these must be specified: + + --instance-location=INSTANCE_LOCATION + Location of the Filestore instance. + + --instance-region=INSTANCE_REGION + Region of the Filestore instance. OPTIONAL FLAGS --async diff --git a/gcloud/beta/filestore/instances/snapshots/delete b/gcloud/beta/filestore/instances/snapshots/delete index 8805aa023..0e2ae92ec 100644 --- a/gcloud/beta/filestore/instances/snapshots/delete +++ b/gcloud/beta/filestore/instances/snapshots/delete @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud beta filestore instances snapshots delete SNAPSHOT - --instance=INSTANCE --instance-region=INSTANCE_REGION [--async] - [GCLOUD_WIDE_FLAG ...] + --instance=INSTANCE + (--instance-location=INSTANCE_LOCATION + | --instance-region=INSTANCE_REGION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Delete a Filestore snapshot. @@ -30,8 +31,13 @@ REQUIRED FLAGS --instance=INSTANCE Name of the Filestore instance the snapshot belongs to. - --instance-region=INSTANCE_REGION - Region of the Filestore instance. + Exactly one of these must be specified: + + --instance-location=INSTANCE_LOCATION + Location of the Filestore instance. + + --instance-region=INSTANCE_REGION + Region of the Filestore instance. OPTIONAL FLAGS --async diff --git a/gcloud/beta/filestore/instances/snapshots/describe b/gcloud/beta/filestore/instances/snapshots/describe index bbd78b898..d7765c3d6 100644 --- a/gcloud/beta/filestore/instances/snapshots/describe +++ b/gcloud/beta/filestore/instances/snapshots/describe @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud beta filestore instances snapshots describe SNAPSHOT - --instance=INSTANCE --instance-region=INSTANCE_REGION - [GCLOUD_WIDE_FLAG ...] + --instance=INSTANCE + (--instance-location=INSTANCE_LOCATION + | --instance-region=INSTANCE_REGION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Displays information about a Filestore snapshot given a valid @@ -31,8 +32,13 @@ REQUIRED FLAGS --instance=INSTANCE Name of the Filestore instance the snapshot belongs to. - --instance-region=INSTANCE_REGION - Region of the Filestore instance. + Exactly one of these must be specified: + + --instance-location=INSTANCE_LOCATION + Location of the Filestore instance. + + --instance-region=INSTANCE_REGION + Region of the Filestore instance. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/filestore/instances/snapshots/list b/gcloud/beta/filestore/instances/snapshots/list index 93b49d8c2..76b4b5f9e 100644 --- a/gcloud/beta/filestore/instances/snapshots/list +++ b/gcloud/beta/filestore/instances/snapshots/list @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud beta filestore instances snapshots list --instance=INSTANCE - --instance-region=INSTANCE_REGION [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + (--instance-location=INSTANCE_LOCATION + | --instance-region=INSTANCE_REGION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -29,8 +30,13 @@ REQUIRED FLAGS --instance=INSTANCE Name of the Filestore instance the snapshot belongs to. - --instance-region=INSTANCE_REGION - Region of the Filestore instance. + Exactly one of these must be specified: + + --instance-location=INSTANCE_LOCATION + Location of the Filestore instance. + + --instance-region=INSTANCE_REGION + Region of the Filestore instance. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/filestore/instances/snapshots/update b/gcloud/beta/filestore/instances/snapshots/update index a45576bd2..eb05f6d1b 100644 --- a/gcloud/beta/filestore/instances/snapshots/update +++ b/gcloud/beta/filestore/instances/snapshots/update @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud beta filestore instances snapshots update SNAPSHOT - --instance=INSTANCE --instance-region=INSTANCE_REGION [--async] + --instance=INSTANCE + (--instance-location=INSTANCE_LOCATION + | --instance-region=INSTANCE_REGION) [--async] [--description=DESCRIPTION] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -32,8 +34,13 @@ REQUIRED FLAGS --instance=INSTANCE Name of the Filestore instance the snapshot belongs to. - --instance-region=INSTANCE_REGION - Region of the Filestore instance. + Exactly one of these must be specified: + + --instance-location=INSTANCE_LOCATION + Location of the Filestore instance. + + --instance-region=INSTANCE_REGION + Region of the Filestore instance. OPTIONAL FLAGS --async diff --git a/gcloud/beta/logging/help b/gcloud/beta/logging/help index 39862295c..eccb6ca7c 100644 --- a/gcloud/beta/logging/help +++ b/gcloud/beta/logging/help @@ -19,7 +19,7 @@ GROUPS (BETA) Manage Cloud Logging buckets. links - (BETA) Manage log links. + (BETA) Manage linked datasets. locations (BETA) Query Cloud Logging locations. diff --git a/gcloud/beta/logging/links/create b/gcloud/beta/logging/links/create index 5feb25496..ab6bb2905 100644 --- a/gcloud/beta/logging/links/create +++ b/gcloud/beta/logging/links/create @@ -1,5 +1,6 @@ NAME - gcloud beta logging links create - create a link on an analytics log bucket + gcloud beta logging links create - create a linked dataset on an analytics + log bucket SYNOPSIS gcloud beta logging links create LINK_ID --bucket=BUCKET @@ -9,24 +10,24 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create a link for a log bucket. + (BETA) Create a linked dataset for a log bucket. EXAMPLES - To create a link in a project, run: + To create a linked dataset in a project, run: $ gcloud beta logging links create my-link --bucket=my-bucket \ --location=global POSITIONAL ARGUMENTS LINK_ID - ID of the link to create. + ID of the linked dataset to create. REQUIRED FLAGS --bucket=BUCKET - ID of the bucket that will hold the link + ID of the bucket that will hold the linked dataset --location=LOCATION - Location of the bucket that will hold the link. + Location of the bucket that will hold the linked datasert. OPTIONAL FLAGS --async @@ -34,21 +35,21 @@ OPTIONAL FLAGS complete. --description=DESCRIPTION - A textual description for the link. + A textual description for the linked dataset. At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID - Billing account of the link to create. + Billing account of the linked dataset to create. --folder=FOLDER_ID - Folder of the link to create. + Folder of the linked dataset to create. --organization=ORGANIZATION_ID - Organization of the link to create. + Organization of the linked dataset to create. --project=PROJECT_ID - Project of the link to create. + Project of the linked dataset to create. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/beta/logging/links/delete b/gcloud/beta/logging/links/delete index 8fd45e1ed..23b9913a8 100644 --- a/gcloud/beta/logging/links/delete +++ b/gcloud/beta/logging/links/delete @@ -1,5 +1,5 @@ NAME - gcloud beta logging links delete - delete a link + gcloud beta logging links delete - delete a linked dataset SYNOPSIS gcloud beta logging links delete LINK_ID --bucket=BUCKET @@ -9,17 +9,17 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Deletes a bucket's link. + (BETA) Delete a bucket's linked dataset. EXAMPLES - To delete a bucket's link, run: + To delete a bucket's linked dataset, run: $ gcloud beta logging links delete my-link --bucket=my-bucket \ --location=global POSITIONAL ARGUMENTS LINK_ID - ID of the link to delete. + ID of the linked dataset to delete. REQUIRED FLAGS --bucket=BUCKET @@ -36,16 +36,16 @@ OPTIONAL FLAGS At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID - Billing account of the link to delete. + Billing account of the linked dataset to delete. --folder=FOLDER_ID - Folder of the link to delete. + Folder of the linked dataset to delete. --organization=ORGANIZATION_ID - Organization of the link to delete. + Organization of the linked dataset to delete. --project=PROJECT_ID - Project of the link to delete. + Project of the linked dataset to delete. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/beta/logging/links/describe b/gcloud/beta/logging/links/describe index 68e5b6495..f0dc1337a 100644 --- a/gcloud/beta/logging/links/describe +++ b/gcloud/beta/logging/links/describe @@ -1,5 +1,6 @@ NAME - gcloud beta logging links describe - display information about a link + gcloud beta logging links describe - display information about a linked + dataset SYNOPSIS gcloud beta logging links describe LINK_ID --bucket=BUCKET @@ -9,17 +10,17 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Displays information about a link. + (BETA) Display information about a linked dataset. EXAMPLES - To describe a link in a project, run: + To describe a linked dataset in a project, run: $ gcloud beta logging links describe my-link --bucket=my-bucket \ --location=global POSITIONAL ARGUMENTS LINK_ID - Id of the link to describe. + Id of the linked dataset to describe. REQUIRED FLAGS --bucket=BUCKET @@ -32,16 +33,16 @@ OPTIONAL FLAGS At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID - Billing account of the link to describe. + Billing account of the linked dataset to describe. --folder=FOLDER_ID - Folder of the link to describe. + Folder of the linked dataset to describe. --organization=ORGANIZATION_ID - Organization of the link to describe. + Organization of the linked dataset to describe. --project=PROJECT_ID - Project of the link to describe. + Project of the linked dataset to describe. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/beta/logging/links/help b/gcloud/beta/logging/links/help index 320d123a9..dd4a0e4b0 100644 --- a/gcloud/beta/logging/links/help +++ b/gcloud/beta/logging/links/help @@ -1,12 +1,12 @@ NAME - gcloud beta logging links - manage log links + gcloud beta logging links - manage linked datasets SYNOPSIS gcloud beta logging links COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Commands for managing links. A log link represents a linked BigQuery - dataset that contains log data for the link's parent log bucket. + (BETA) Commands for managing linked datasets. A linked BigQuery dataset + contains log data for the linked dataset's parent log bucket. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,16 +17,16 @@ COMMANDS COMMAND is one of the following: create - (BETA) Create a link on an analytics log bucket. + (BETA) Create a linked dataset on an analytics log bucket. delete - (BETA) Delete a link. + (BETA) Delete a linked dataset. describe - (BETA) Display information about a link. + (BETA) Display information about a linked dataset. list - (BETA) List created links on the specified bucket. + (BETA) List created linked datasets on the specified bucket. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/logging/links/list b/gcloud/beta/logging/links/list index f2c033684..e1f30dc8a 100644 --- a/gcloud/beta/logging/links/list +++ b/gcloud/beta/logging/links/list @@ -1,5 +1,6 @@ NAME - gcloud beta logging links list - list created links on the specified bucket + gcloud beta logging links list - list created linked datasets on the + specified bucket SYNOPSIS gcloud beta logging links list --bucket=BUCKET --location=LOCATION @@ -9,10 +10,10 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Lists the links created for a bucket. + (BETA) List the linked datasets created for a bucket. EXAMPLES - To list the links created for a bucket, run: + To list the linked datasets created for a bucket, run: $ gcloud beta logging links list @@ -27,16 +28,16 @@ FLAGS At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID - Billing account of the links to list. + Billing account of the linked datasets to list. --folder=FOLDER_ID - Folder of the links to list. + Folder of the linked datasets to list. --organization=ORGANIZATION_ID - Organization of the links to list. + Organization of the linked datasets to list. --project=PROJECT_ID - Project of the links to list. + Project of the linked datasets to list. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/beta/metastore/services/create b/gcloud/beta/metastore/services/create index 13facdc32..c2b7837b6 100644 --- a/gcloud/beta/metastore/services/create +++ b/gcloud/beta/metastore/services/create @@ -9,13 +9,15 @@ SYNOPSIS [--endpoint-protocol=ENDPOINT_PROTOCOL; default="thrift"] [--hive-metastore-version=HIVE_METASTORE_VERSION] [--labels=[KEY=VALUE,...]] [--port=PORT; default=9083] - [--release-channel=RELEASE_CHANNEL; default="stable"] [--tier=TIER] + [--release-channel=RELEASE_CHANNEL; default="stable"] [--auxiliary-versions=[AUXILIARY_VERSIONS,...] | --auxiliary-versions-from-file=AUXILIARY_VERSIONS_FROM_FILE] [--consumer-subnetworks=[CONSUMER_SUBNETWORKS,...] | --network=NETWORK | --network-config-from-file=NETWORK_CONFIG_FROM_FILE] [--hive-metastore-configs=KEY=VALUE | --hive-metastore-configs-from-file=HIVE_METASTORE_CONFIGS_FROM_FILE] + [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR + | --tier=TIER] [--kerberos-principal=KERBEROS_PRINCIPAL --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY @@ -148,18 +150,6 @@ FLAGS The STABLE release channel contains features that are considered stable and have been validated for production use. - --tier=TIER - The tier of the service. TIER must be one of: - - developer - The developer tier provides limited scalability and no fault - tolerance. Good for low-cost proof-of-concept. - - enterprise - The enterprise tier provides multi-zone high availability, and - sufficient scalability for enterprise-level Dataproc Metastore - workloads. - Auxiliary versions configuration for the Dataproc Metastore service. When specified, a secondary Hive metastore service is created along with the primary service. @@ -252,6 +242,46 @@ FLAGS + The instance size of the Dataproc Metastore instance. + + At most one of these can be specified: + + --instance-size=INSTANCE_SIZE + The instance size of the service. INSTANCE_SIZE must be one of: + + extra_large + Extra large instance size, maps to a scaling factor of 6.0. + + extra_small + Extra small instance size, maps to a scaling factor of 0.1. + + large + Large instance size, maps to a scaling factor of 3.0. + + medium + Medium instance size, maps to a scaling factor of 1.0. + + small + Small instance size, maps to a scaling factor of 0.5. + + --scaling-factor=SCALING_FACTOR + The scaling factor of the service. This should be a float in the + range [0.1,6.0]. If the value is less than 1.0, then it should be a + multiple of 0.1. If the value is greater than 1.0, then it should be + a whole number. Float values should be formatted as x.y. + + --tier=TIER + The tier of the service. TIER must be one of: + + developer + The developer tier provides limited scalability and no fault + tolerance. Good for low-cost proof-of-concept. + + enterprise + The enterprise tier provides multi-zone high availability, and + sufficient scalability for enterprise-level Dataproc Metastore + workloads. + Information used to configure the Hive metastore service as a service principal in a Kerberos realm. diff --git a/gcloud/beta/metastore/services/update b/gcloud/beta/metastore/services/update index 7564bb007..4baf03011 100644 --- a/gcloud/beta/metastore/services/update +++ b/gcloud/beta/metastore/services/update @@ -4,8 +4,10 @@ NAME SYNOPSIS gcloud beta metastore services update (SERVICE : --location=LOCATION) [--async] [--data-catalog-sync] [--endpoint-protocol=ENDPOINT_PROTOCOL] - [--port=PORT] [--tier=TIER] [--update-labels=[KEY=VALUE,...]] + [--port=PORT] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] + [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR + | --tier=TIER] [--kerberos-principal=KERBEROS_PRINCIPAL --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY @@ -88,18 +90,6 @@ FLAGS --port=PORT The TCP port on which the Metastore service will listen. - --tier=TIER - The tier of the service. TIER must be one of: - - developer - The developer tier provides limited scalability and no fault - tolerance. Good for low-cost proof-of-concept. - - enterprise - The enterprise tier provides multi-zone high availability, and - sufficient scalability for enterprise-level Dataproc Metastore - workloads. - --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. @@ -129,6 +119,46 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + The instance size of the Dataproc Metastore instance. + + At most one of these can be specified: + + --instance-size=INSTANCE_SIZE + The instance size of the service. INSTANCE_SIZE must be one of: + + extra_large + Extra large instance size, maps to a scaling factor of 6.0. + + extra_small + Extra small instance size, maps to a scaling factor of 0.1. + + large + Large instance size, maps to a scaling factor of 3.0. + + medium + Medium instance size, maps to a scaling factor of 1.0. + + small + Small instance size, maps to a scaling factor of 0.5. + + --scaling-factor=SCALING_FACTOR + The scaling factor of the service. This should be a float in the + range [0.1,6.0]. If the value is less than 1.0, then it should be a + multiple of 0.1. If the value is greater than 1.0, then it should be + a whole number. + + --tier=TIER + The tier of the service. TIER must be one of: + + developer + The developer tier provides limited scalability and no fault + tolerance. Good for low-cost proof-of-concept. + + enterprise + The enterprise tier provides multi-zone high availability, and + sufficient scalability for enterprise-level Dataproc Metastore + workloads. + Information used to configure the Hive metastore service as a service principal in a Kerberos realm. diff --git a/gcloud/beta/services/api-keys/undelete b/gcloud/beta/services/api-keys/undelete index c82ba94fa..1a6b38897 100644 --- a/gcloud/beta/services/api-keys/undelete +++ b/gcloud/beta/services/api-keys/undelete @@ -2,8 +2,9 @@ NAME gcloud beta services api-keys undelete - undelete an API key SYNOPSIS - gcloud beta services api-keys undelete (KEY : --location=LOCATION) - [--async] [GCLOUD_WIDE_FLAG ...] + gcloud beta services api-keys undelete + ([KEY : --location=LOCATION] --key-string=KEY_STRING) [--async] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) API Keys that are deleted will be retained in the system for 30 @@ -11,39 +12,51 @@ DESCRIPTION with this command. EXAMPLES - UnDelete an API Key : + UnDelete an API Key (Key or key-string should be specified): - $ gcloud beta services api-keys undelete \ - projects/myproject/locations/global/keys/1234 + To undelete with key `1234`, run: $ gcloud beta services api-keys undelete 1234 + To undelete with `1234` in project + `myproject` using the fully qualified API key name, run: + + $ gcloud beta services api-keys undelete \ + projects/myproject/locations/global/keys/1234 + + To undelete using a Key-string, run: + + $gcloud beta services api-keys undelete --key-string='my-key-string' + POSITIONAL ARGUMENTS - Key resource - The name of the key to undelete. 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 key on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. + Exactly one of these must be specified: - This must be specified. + Key resource - The name of the key to undelete. 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 key on the command line with a fully specified + name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. - KEY - ID of the key or fully qualified identifier for the key. To set the - key attribute: - ▸ provide the argument key on the command line. + KEY + ID of the key or fully qualified identifier for the key. To set the + key attribute: + ▫ provide the argument key on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. + This positional argument must be specified if any of the other + arguments in this group are specified. - --location=LOCATION - Location of the key. To set the location attribute: - ▸ provide the argument key on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ location will default to global. + --location=LOCATION + Location of the key. To set the location attribute: + ▫ provide the argument key on the command line with a fully + specified name; + ▫ provide the argument --location on the command line; + ▫ location will default to global. + + --key-string=KEY_STRING + Key String of the key. FLAGS --async diff --git a/gcloud/beta/services/api-keys/update b/gcloud/beta/services/api-keys/update index 843444d11..5418e9fcd 100644 --- a/gcloud/beta/services/api-keys/update +++ b/gcloud/beta/services/api-keys/update @@ -27,7 +27,7 @@ EXAMPLES projects/myproject/keys/my-key-id --display-name="test name" \ --allowed-ips=2620:15c:2c4:203:2776:1f90:6b3b:217,104.133.8.78 - To update annoatations: + To update annotations: $ gcloud beta services api-keys update \ projects/myproject/keys/my-key-id --annotations=foo=bar,abc=def diff --git a/gcloud/beta/spanner/databases/roles/help b/gcloud/beta/spanner/databases/roles/help index 2339c3181..c15ad01be 100644 --- a/gcloud/beta/spanner/databases/roles/help +++ b/gcloud/beta/spanner/databases/roles/help @@ -16,12 +16,14 @@ COMMANDS COMMAND is one of the following: list - (BETA) List the Cloud Spanner database roles contained within the given + (BETA) List the Cloud Spanner database roles defined in the given database. 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 spanner databases roles $ gcloud alpha spanner databases roles diff --git a/gcloud/beta/spanner/databases/roles/list b/gcloud/beta/spanner/databases/roles/list index 3b54b337b..7d3eba074 100644 --- a/gcloud/beta/spanner/databases/roles/list +++ b/gcloud/beta/spanner/databases/roles/list @@ -1,6 +1,6 @@ NAME gcloud beta spanner databases roles list - list the Cloud Spanner database - roles contained within the given database + roles defined in the given database SYNOPSIS gcloud beta spanner databases roles list @@ -9,8 +9,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List the Cloud Spanner database roles contained within the given - database. + (BETA) List the Cloud Spanner database roles defined in the given database. EXAMPLES To list the Cloud Spanner database roles in a database, run: @@ -87,8 +86,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 spanner databases roles list $ gcloud alpha spanner databases roles list diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index 86bdb1c13..9103366cc 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -17,7 +17,7 @@ SYNOPSIS [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--diff] [--[no-]enable-bin-log] [--[no-]enable-database-replication] - [--enable-google-private-path] [--enable-password-policy] + [--[no-]enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] [--follow-gae-app=FOLLOW_GAE_APP] [--[no-]insights-config-query-insights-enabled] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -169,12 +169,13 @@ FLAGS --enable-database-replication to enable and --no-enable-database-replication to disable. - --enable-google-private-path + --[no-]enable-google-private-path Enable a private path for Google Cloud services. This flag specifies whether the instance is accessible to internal Google Cloud services such as BigQuery. This is only applicable to MySQL and PostgreSQL instances that don't use public IP. Currently, SQL Server isn't - supported. + supported. Use --enable-google-private-path to enable and + --no-enable-google-private-path to disable. --enable-password-policy Enable the password policy, which enforces user password management diff --git a/gcloud/composer/environments/run b/gcloud/composer/environments/run index 62bedce00..17fd9df20 100644 --- a/gcloud/composer/environments/run +++ b/gcloud/composer/environments/run @@ -12,8 +12,20 @@ DESCRIPTION and its flags with ``--''. This command waits for the sub-command to complete; its exit code will match the sub-command's exit code. + Note: Airflow CLI sub-command syntax differs between Airflow 1 and Airflow + 2. Refer to the Airflow CLI reference documentation for more details. + EXAMPLES - The following command: + The following command in environments with Airflow 2: + + gcloud composer environments run myenv dags trigger -- some_dag --run_id=foo + + is equivalent to running the following command from a shell inside the + my-environment environment: + + airflow dags trigger --run_id=foo some_dag + + The same command, but for environments with Airflow 1.10.14+: gcloud composer environments run myenv trigger_dag -- some_dag --run_id=foo diff --git a/gcloud/compute/backend-services/create b/gcloud/compute/backend-services/create index 6d2f58068..ec2ce6484 100644 --- a/gcloud/compute/backend-services/create +++ b/gcloud/compute/backend-services/create @@ -25,6 +25,7 @@ SYNOPSIS oauth2-client-secret=OAUTH2-CLIENT-SECRET]] [--idle-timeout-sec=IDLE_TIMEOUT_SEC] [--load-balancing-scheme=LOAD_BALANCING_SCHEME; default="EXTERNAL"] + [--locality-lb-policy=LOCALITY_LB_POLICY] [--logging-optional=LOGGING_OPTIONAL] [--logging-optional-fields=[LOGGING_OPTIONAL_FIELDS,...]] [--logging-sample-rate=LOGGING_SAMPLE_RATE] [--max-ttl=MAX_TTL] @@ -327,6 +328,12 @@ FLAGS LOAD_BALANCING_SCHEME must be one of: INTERNAL, EXTERNAL, INTERNAL_SELF_MANAGED, EXTERNAL_MANAGED, INTERNAL_MANAGED. + --locality-lb-policy=LOCALITY_LB_POLICY + The load balancing algorithm used within the scope of the locality. + LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN, + LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV, + WEIGHTED_MAGLEV. + --logging-optional=LOGGING_OPTIONAL This field can only be specified if logging is enabled for the backend service. Configures whether all, none, or a subset of optional fields diff --git a/gcloud/compute/backend-services/update b/gcloud/compute/backend-services/update index 348cdbcce..b9d8e2df9 100644 --- a/gcloud/compute/backend-services/update +++ b/gcloud/compute/backend-services/update @@ -20,6 +20,7 @@ SYNOPSIS [--iap=disabled|enabled,[oauth2-client-id=OAUTH2-CLIENT-ID, oauth2-client-secret=OAUTH2-CLIENT-SECRET]] [--idle-timeout-sec=IDLE_TIMEOUT_SEC] + [--locality-lb-policy=LOCALITY_LB_POLICY] [--logging-optional=LOGGING_OPTIONAL] [--logging-optional-fields=[LOGGING_OPTIONAL_FIELDS,...]] [--logging-sample-rate=LOGGING_SAMPLE_RATE] [--port-name=PORT_NAME] @@ -237,6 +238,12 @@ FLAGS service-based network load balancers and internal TCP/UDP load balancers as part of a connection tracking policy. + --locality-lb-policy=LOCALITY_LB_POLICY + The load balancing algorithm used within the scope of the locality. + LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN, + LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV, + WEIGHTED_MAGLEV. + --logging-optional=LOGGING_OPTIONAL This field can only be specified if logging is enabled for the backend service. Configures whether all, none, or a subset of optional fields diff --git a/gcloud/compute/interconnects/attachments/dedicated/create b/gcloud/compute/interconnects/attachments/dedicated/create index a2e3c7fa2..a43184557 100644 --- a/gcloud/compute/interconnects/attachments/dedicated/create +++ b/gcloud/compute/interconnects/attachments/dedicated/create @@ -9,9 +9,9 @@ SYNOPSIS [--candidate-subnets=[SUBNET,...]] [--cloud-router-ipv6-interface-id=INTERFACE_ID] [--customer-router-ipv6-interface-id=PEER_INTERFACE_ID] - [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU] - [--region=REGION] [--stack-type=STACK_TYPE] [--vlan=VLAN] - [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--enable-admin] [--encryption=ENCRYPTION] + [--ipsec-internal-addresses=[ADDRESSES]] [--mtu=MTU] [--region=REGION] + [--stack-type=STACK_TYPE] [--vlan=VLAN] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute interconnects attachments dedicated create is used to create @@ -100,6 +100,38 @@ OPTIONAL FLAGS is operational and will carry traffic. Use --no-enable-admin to disable it. + --encryption=ENCRYPTION + Indicates the user-supplied encryption option for this interconnect + attachment (VLAN attachment). + + Possible values are: + + NONE - This is the default value, which means the interconnect + attachment carries unencrypted traffic. VMs can send traffic to or + receive traffic from such interconnect attachment. + + IPSEC - The interconnect attachment carries only traffic that is + encrypted by an IPsec device; for example, an HA VPN gateway or + third-party IPsec VPN. VMs cannot directly send traffic to or receive + traffic from such an interconnect attachment. To use HA VPN over Cloud + Interconnect, the interconnect attachment must be created with this + option. + + ENCRYPTION must be one of: IPSEC, NONE. + + --ipsec-internal-addresses=[ADDRESSES] + List of IP address range names that have been reserved for the + interconnect attachment (VLAN attachment). Use this option only for an + interconnect attachment that has its encryption option set as IPSEC. + Currently only one internal IP address range can be specified for each + attachment. When creating an HA VPN gateway for the interconnect + attachment, if the attachment is configured to use a regional internal + IP address, then the VPN gateway's IP address is allocated from the IP + address range specified here. If this field is not specified when + creating the interconnect attachment, then when creating any HA VPN + gateways for this interconnect attachment, the HA VPN gateway's IP + address is allocated from a regional external IP address pool. + --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet passing through this interconnect attachment. Only 1440 and 1500 are diff --git a/gcloud/compute/interconnects/attachments/partner/create b/gcloud/compute/interconnects/attachments/partner/create index 327f2866e..92c9465fd 100644 --- a/gcloud/compute/interconnects/attachments/partner/create +++ b/gcloud/compute/interconnects/attachments/partner/create @@ -5,8 +5,9 @@ NAME SYNOPSIS gcloud compute interconnects attachments partner create NAME --edge-availability-domain=AVAILABILITY_DOMAIN --router=ROUTER - [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU] - [--region=REGION] [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--enable-admin] [--encryption=ENCRYPTION] + [--ipsec-internal-addresses=[ADDRESSES]] [--mtu=MTU] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute interconnects attachments partner create is used to create @@ -53,6 +54,38 @@ OPTIONAL FLAGS is operational and will carry traffic. Use --no-enable-admin to disable it. + --encryption=ENCRYPTION + Indicates the user-supplied encryption option for this interconnect + attachment (VLAN attachment). + + Possible values are: + + NONE - This is the default value, which means the interconnect + attachment carries unencrypted traffic. VMs can send traffic to or + receive traffic from such interconnect attachment. + + IPSEC - The interconnect attachment carries only traffic that is + encrypted by an IPsec device; for example, an HA VPN gateway or + third-party IPsec VPN. VMs cannot directly send traffic to or receive + traffic from such an interconnect attachment. To use HA VPN over Cloud + Interconnect, the interconnect attachment must be created with this + option. + + ENCRYPTION must be one of: IPSEC, NONE. + + --ipsec-internal-addresses=[ADDRESSES] + List of IP address range names that have been reserved for the + interconnect attachment (VLAN attachment). Use this option only for an + interconnect attachment that has its encryption option set as IPSEC. + Currently only one internal IP address range can be specified for each + attachment. When creating an HA VPN gateway for the interconnect + attachment, if the attachment is configured to use a regional internal + IP address, then the VPN gateway's IP address is allocated from the IP + address range specified here. If this field is not specified when + creating the interconnect attachment, then when creating any HA VPN + gateways for this interconnect attachment, the HA VPN gateway's IP + address is allocated from a regional external IP address pool. + --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet passing through this interconnect attachment. Only 1440 and 1500 are diff --git a/gcloud/compute/routers/create b/gcloud/compute/routers/create index e2de7e309..27cb8536f 100644 --- a/gcloud/compute/routers/create +++ b/gcloud/compute/routers/create @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud compute routers create NAME --network=NETWORK [--advertisement-mode=MODE] [--asn=ASN] [--async] - [--description=DESCRIPTION] [--keepalive-interval=KEEPALIVE_INTERVAL] - [--region=REGION] [--set-advertisement-groups=[GROUP,...]] + [--description=DESCRIPTION] [--encrypted-interconnect-router] + [--keepalive-interval=KEEPALIVE_INTERVAL] [--region=REGION] + [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] [GCLOUD_WIDE_FLAG ...] @@ -42,6 +43,10 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional description of this router. + --encrypted-interconnect-router + Indicates if a router is dedicated for use with encrypted interconnect + attachments (VLAN attachments). + --keepalive-interval=KEEPALIVE_INTERVAL The interval between BGP keepalive messages that are sent to the peer. If set, this value must be between 20 and 60 seconds. The default is 20 diff --git a/gcloud/compute/routers/nats/create b/gcloud/compute/routers/nats/create index b81f9d50b..a594f7111 100644 --- a/gcloud/compute/routers/nats/create +++ b/gcloud/compute/routers/nats/create @@ -10,6 +10,7 @@ SYNOPSIS | --nat-primary-subnet-ip-ranges) [--async] [--[no-]enable-dynamic-port-allocation] [--enable-endpoint-independent-mapping] [--enable-logging] + [--endpoint-types=[ENDPOINT_TYPE,...]] [--icmp-idle-timeout=ICMP_IDLE_TIMEOUT] [--log-filter=LOG_FILTER] [--max-ports-per-vm=MAX_PORTS_PER_VM] [--min-ports-per-vm=MIN_PORTS_PER_VM] [--region=REGION] [--rules=RULES] @@ -110,6 +111,20 @@ OPTIONAL FLAGS gcloud compute routers nats update MY-NAT --no-enable-logging \ --router ROUTER --region REGION + --endpoint-types=[ENDPOINT_TYPE,...] + Endpoint Types supported by the NAT Gateway. + + ENDPOINT_TYPE must be one of: + + ENDPOINT_TYPE_VM + For VM Endpoints + ENDPOINT_TYPE_SWG + For Secure Web Gateway Endpoints + + The default is ENDPOINT_TYPE_VM. + + ENDPOINT_TYPE must be one of: ENDPOINT_TYPE_VM, ENDPOINT_TYPE_SWG. + --icmp-idle-timeout=ICMP_IDLE_TIMEOUT Timeout for ICMP connections. See https://cloud.google.com/sdk/gcloud/reference/topic/datetimes for diff --git a/gcloud/compute/vpn-gateways/create b/gcloud/compute/vpn-gateways/create index 40ac1a48c..9cc4c29be 100644 --- a/gcloud/compute/vpn-gateways/create +++ b/gcloud/compute/vpn-gateways/create @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud compute vpn-gateways create NAME --network=NETWORK - [--description=DESCRIPTION] [--region=REGION] [--stack-type=STACK_TYPE] - [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] + [--interconnect-attachments=[INTERCONNECT_ATTACHMENTS,...]] + [--region=REGION] [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute vpn-gateways create creates a new Highly Available VPN @@ -35,6 +36,17 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional, textual description for the VPN gateway. + --interconnect-attachments=[INTERCONNECT_ATTACHMENTS,...] + Names of interconnect attachments (VLAN attachments) associated with + the VPN gateway interfaces. You must specify this field when using a + VPN gateway for HA VPN over Cloud Interconnect. Otherwise, this field + is optional. + + For example, --interconnect-attachments + attachment-a-zone1,attachment-a-zone2 associates VPN gateway with + attachment from zone1 on interface 0 and with attachment from zone2 on + interface 1. + --region=REGION Region of the VPN Gateway to create. If not specified, you might be prompted to select a region (interactive mode only). diff --git a/gcloud/filestore/instances/snapshots/create b/gcloud/filestore/instances/snapshots/create index 52ff98dee..ba5a32cf0 100644 --- a/gcloud/filestore/instances/snapshots/create +++ b/gcloud/filestore/instances/snapshots/create @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud filestore instances snapshots create SNAPSHOT --instance=INSTANCE - --instance-region=INSTANCE_REGION [--async] [--description=DESCRIPTION] - [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...] + (--instance-location=INSTANCE_LOCATION + | --instance-region=INSTANCE_REGION) [--async] + [--description=DESCRIPTION] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a Filestore snapshot of an instance. @@ -30,8 +31,13 @@ REQUIRED FLAGS --instance=INSTANCE Name of the Filestore instance that you want to create a snapshot of. - --instance-region=INSTANCE_REGION - Region of the Filestore instance. + Exactly one of these must be specified: + + --instance-location=INSTANCE_LOCATION + Location of the Filestore instance. + + --instance-region=INSTANCE_REGION + Region of the Filestore instance. OPTIONAL FLAGS --async diff --git a/gcloud/filestore/instances/snapshots/delete b/gcloud/filestore/instances/snapshots/delete index bbfff52fc..fef9bb8de 100644 --- a/gcloud/filestore/instances/snapshots/delete +++ b/gcloud/filestore/instances/snapshots/delete @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud filestore instances snapshots delete SNAPSHOT --instance=INSTANCE - --instance-region=INSTANCE_REGION [--async] [GCLOUD_WIDE_FLAG ...] + (--instance-location=INSTANCE_LOCATION + | --instance-region=INSTANCE_REGION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Delete a Filestore snapshot. @@ -28,8 +29,13 @@ REQUIRED FLAGS --instance=INSTANCE Name of the Filestore instance the snapshot belongs to. - --instance-region=INSTANCE_REGION - Region of the Filestore instance. + Exactly one of these must be specified: + + --instance-location=INSTANCE_LOCATION + Location of the Filestore instance. + + --instance-region=INSTANCE_REGION + Region of the Filestore instance. OPTIONAL FLAGS --async diff --git a/gcloud/filestore/instances/snapshots/describe b/gcloud/filestore/instances/snapshots/describe index 612352b7b..c93785fe7 100644 --- a/gcloud/filestore/instances/snapshots/describe +++ b/gcloud/filestore/instances/snapshots/describe @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud filestore instances snapshots describe SNAPSHOT --instance=INSTANCE - --instance-region=INSTANCE_REGION [GCLOUD_WIDE_FLAG ...] + (--instance-location=INSTANCE_LOCATION + | --instance-region=INSTANCE_REGION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION Displays information about a Filestore snapshot given a valid snapshot @@ -30,8 +31,13 @@ REQUIRED FLAGS --instance=INSTANCE Name of the Filestore instance the snapshot belongs to. - --instance-region=INSTANCE_REGION - Region of the Filestore instance. + Exactly one of these must be specified: + + --instance-location=INSTANCE_LOCATION + Location of the Filestore instance. + + --instance-region=INSTANCE_REGION + Region of the Filestore instance. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/filestore/instances/snapshots/list b/gcloud/filestore/instances/snapshots/list index f6dc0f340..89f1c0a00 100644 --- a/gcloud/filestore/instances/snapshots/list +++ b/gcloud/filestore/instances/snapshots/list @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud filestore instances snapshots list --instance=INSTANCE - --instance-region=INSTANCE_REGION [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + (--instance-location=INSTANCE_LOCATION + | --instance-region=INSTANCE_REGION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -29,8 +30,13 @@ REQUIRED FLAGS --instance=INSTANCE Name of the Filestore instance the snapshot belongs to. - --instance-region=INSTANCE_REGION - Region of the Filestore instance. + Exactly one of these must be specified: + + --instance-location=INSTANCE_LOCATION + Location of the Filestore instance. + + --instance-region=INSTANCE_REGION + Region of the Filestore instance. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/filestore/instances/snapshots/update b/gcloud/filestore/instances/snapshots/update index 74ba051f7..badd9f9b3 100644 --- a/gcloud/filestore/instances/snapshots/update +++ b/gcloud/filestore/instances/snapshots/update @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud filestore instances snapshots update SNAPSHOT --instance=INSTANCE - --instance-region=INSTANCE_REGION [--async] [--description=DESCRIPTION] - [--update-labels=[KEY=VALUE,...]] + (--instance-location=INSTANCE_LOCATION + | --instance-region=INSTANCE_REGION) [--async] + [--description=DESCRIPTION] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -32,8 +33,13 @@ REQUIRED FLAGS --instance=INSTANCE Name of the Filestore instance the snapshot belongs to. - --instance-region=INSTANCE_REGION - Region of the Filestore instance. + Exactly one of these must be specified: + + --instance-location=INSTANCE_LOCATION + Location of the Filestore instance. + + --instance-region=INSTANCE_REGION + Region of the Filestore instance. OPTIONAL FLAGS --async diff --git a/gcloud/logging/help b/gcloud/logging/help index 5ccf4add1..e52d0bdf8 100644 --- a/gcloud/logging/help +++ b/gcloud/logging/help @@ -19,7 +19,7 @@ GROUPS Manage Cloud Logging buckets. links - Manage log links. + Manage linked datasets. locations Query Cloud Logging locations. diff --git a/gcloud/logging/links/create b/gcloud/logging/links/create index e62c76a08..6beb11387 100644 --- a/gcloud/logging/links/create +++ b/gcloud/logging/links/create @@ -1,5 +1,6 @@ NAME - gcloud logging links create - create a link on an analytics log bucket + gcloud logging links create - create a linked dataset on an analytics log + bucket SYNOPSIS gcloud logging links create LINK_ID --bucket=BUCKET --location=LOCATION @@ -9,24 +10,24 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Create a link for a log bucket. + Create a linked dataset for a log bucket. EXAMPLES - To create a link in a project, run: + To create a linked dataset in a project, run: $ gcloud logging links create my-link --bucket=my-bucket \ --location=global POSITIONAL ARGUMENTS LINK_ID - ID of the link to create. + ID of the linked dataset to create. REQUIRED FLAGS --bucket=BUCKET - ID of the bucket that will hold the link + ID of the bucket that will hold the linked dataset --location=LOCATION - Location of the bucket that will hold the link. + Location of the bucket that will hold the linked datasert. OPTIONAL FLAGS --async @@ -34,21 +35,21 @@ OPTIONAL FLAGS complete. --description=DESCRIPTION - A textual description for the link. + A textual description for the linked dataset. At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID - Billing account of the link to create. + Billing account of the linked dataset to create. --folder=FOLDER_ID - Folder of the link to create. + Folder of the linked dataset to create. --organization=ORGANIZATION_ID - Organization of the link to create. + Organization of the linked dataset to create. --project=PROJECT_ID - Project of the link to create. + Project of the linked dataset to create. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/logging/links/delete b/gcloud/logging/links/delete index ebb46dd16..7052d37ba 100644 --- a/gcloud/logging/links/delete +++ b/gcloud/logging/links/delete @@ -1,5 +1,5 @@ NAME - gcloud logging links delete - delete a link + gcloud logging links delete - delete a linked dataset SYNOPSIS gcloud logging links delete LINK_ID --bucket=BUCKET --location=LOCATION @@ -9,17 +9,17 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Deletes a bucket's link. + Delete a bucket's linked dataset. EXAMPLES - To delete a bucket's link, run: + To delete a bucket's linked dataset, run: $ gcloud logging links delete my-link --bucket=my-bucket \ --location=global POSITIONAL ARGUMENTS LINK_ID - ID of the link to delete. + ID of the linked dataset to delete. REQUIRED FLAGS --bucket=BUCKET @@ -36,16 +36,16 @@ OPTIONAL FLAGS At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID - Billing account of the link to delete. + Billing account of the linked dataset to delete. --folder=FOLDER_ID - Folder of the link to delete. + Folder of the linked dataset to delete. --organization=ORGANIZATION_ID - Organization of the link to delete. + Organization of the linked dataset to delete. --project=PROJECT_ID - Project of the link to delete. + Project of the linked dataset to delete. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/logging/links/describe b/gcloud/logging/links/describe index 175e6fac1..d86d1fa90 100644 --- a/gcloud/logging/links/describe +++ b/gcloud/logging/links/describe @@ -1,5 +1,5 @@ NAME - gcloud logging links describe - display information about a link + gcloud logging links describe - display information about a linked dataset SYNOPSIS gcloud logging links describe LINK_ID --bucket=BUCKET --location=LOCATION @@ -8,17 +8,17 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Displays information about a link. + Display information about a linked dataset. EXAMPLES - To describe a link in a project, run: + To describe a linked dataset in a project, run: $ gcloud logging links describe my-link --bucket=my-bucket \ --location=global POSITIONAL ARGUMENTS LINK_ID - Id of the link to describe. + Id of the linked dataset to describe. REQUIRED FLAGS --bucket=BUCKET @@ -31,16 +31,16 @@ OPTIONAL FLAGS At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID - Billing account of the link to describe. + Billing account of the linked dataset to describe. --folder=FOLDER_ID - Folder of the link to describe. + Folder of the linked dataset to describe. --organization=ORGANIZATION_ID - Organization of the link to describe. + Organization of the linked dataset to describe. --project=PROJECT_ID - Project of the link to describe. + Project of the linked dataset to describe. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/logging/links/help b/gcloud/logging/links/help index d579814bd..042aae234 100644 --- a/gcloud/logging/links/help +++ b/gcloud/logging/links/help @@ -1,12 +1,12 @@ NAME - gcloud logging links - manage log links + gcloud logging links - manage linked datasets SYNOPSIS gcloud logging links COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Commands for managing links. A log link represents a linked BigQuery - dataset that contains log data for the link's parent log bucket. + Commands for managing linked datasets. A linked BigQuery dataset contains + log data for the linked dataset's parent log bucket. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,16 +17,16 @@ COMMANDS COMMAND is one of the following: create - Create a link on an analytics log bucket. + Create a linked dataset on an analytics log bucket. delete - Delete a link. + Delete a linked dataset. describe - Display information about a link. + Display information about a linked dataset. list - List created links on the specified bucket. + List created linked datasets on the specified bucket. NOTES These variants are also available: diff --git a/gcloud/logging/links/list b/gcloud/logging/links/list index dbe07acae..99f104872 100644 --- a/gcloud/logging/links/list +++ b/gcloud/logging/links/list @@ -1,5 +1,6 @@ NAME - gcloud logging links list - list created links on the specified bucket + gcloud logging links list - list created linked datasets on the specified + bucket SYNOPSIS gcloud logging links list --bucket=BUCKET --location=LOCATION @@ -9,10 +10,10 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Lists the links created for a bucket. + List the linked datasets created for a bucket. EXAMPLES - To list the links created for a bucket, run: + To list the linked datasets created for a bucket, run: $ gcloud logging links list @@ -27,16 +28,16 @@ FLAGS At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID - Billing account of the links to list. + Billing account of the linked datasets to list. --folder=FOLDER_ID - Folder of the links to list. + Folder of the linked datasets to list. --organization=ORGANIZATION_ID - Organization of the links to list. + Organization of the linked datasets to list. --project=PROJECT_ID - Project of the links to list. + Project of the linked datasets to list. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/metastore/services/create b/gcloud/metastore/services/create index 517921de2..8cdad88c4 100644 --- a/gcloud/metastore/services/create +++ b/gcloud/metastore/services/create @@ -7,11 +7,15 @@ SYNOPSIS [--encryption-kms-key=ENCRYPTION_KMS_KEY] [--hive-metastore-version=HIVE_METASTORE_VERSION] [--labels=[KEY=VALUE,...]] [--port=PORT; default=9083] - [--release-channel=RELEASE_CHANNEL; default="stable"] [--tier=TIER] + [--release-channel=RELEASE_CHANNEL; default="stable"] + [--auxiliary-versions=[AUXILIARY_VERSIONS,...] + | --auxiliary-versions-from-file=AUXILIARY_VERSIONS_FROM_FILE] [--consumer-subnetworks=[CONSUMER_SUBNETWORKS,...] | --network=NETWORK | --network-config-from-file=NETWORK_CONFIG_FROM_FILE] [--hive-metastore-configs=KEY=VALUE | --hive-metastore-configs-from-file=HIVE_METASTORE_CONFIGS_FROM_FILE] + [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR + | --tier=TIER] [--kerberos-principal=KERBEROS_PRINCIPAL --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY @@ -129,17 +133,44 @@ FLAGS The STABLE release channel contains features that are considered stable and have been validated for production use. - --tier=TIER - The tier of the service. TIER must be one of: + Auxiliary versions configuration for the Dataproc Metastore service. When + specified, a secondary Hive metastore service is created along with the + primary service. - developer - The developer tier provides limited scalability and no fault - tolerance. Good for low-cost proof-of-concept. + At most one of these can be specified: - enterprise - The enterprise tier provides multi-zone high availability, and - sufficient scalability for enterprise-level Dataproc Metastore - workloads. + --auxiliary-versions=[AUXILIARY_VERSIONS,...] + Comma-separated list of auxiliary Hive metastore versions to + deploy. Auxiliary Hive metastore versions must be less than the + primary Hive metastore service's version. + + --auxiliary-versions-from-file=AUXILIARY_VERSIONS_FROM_FILE + Path to a YAML file containing the auxiliary versions configuration + for Dataproc Metastore instance. The file should contain a unique + auxiliary service name and auxiliary version that is lower than the + primary service version. The primary version's Hive metastore + configs are applied to the auxiliary version. Additional Hive + metastore configs can be specified for the auxiliary version using + "config_overrides". If a specified config property has already been + overridden in the primary Hive metastore version's configs, the + auxiliary version's override takes precedence. The contents of the + file should be structured as follows: + + YAML: + + - name: aux-service1 + version: x.y.z + config_overrides: + key1: value1 + key2: value2 + ... + - name: aux-service2 + version: x.y.z + config_overrides: + key1: value1 + key2: value2 + ... + ... Network configuration for the metastore service. @@ -194,6 +225,46 @@ FLAGS + The instance size of the Dataproc Metastore instance. + + At most one of these can be specified: + + --instance-size=INSTANCE_SIZE + The instance size of the service. INSTANCE_SIZE must be one of: + + extra_large + Extra large instance size, maps to a scaling factor of 6.0. + + extra_small + Extra small instance size, maps to a scaling factor of 0.1. + + large + Large instance size, maps to a scaling factor of 3.0. + + medium + Medium instance size, maps to a scaling factor of 1.0. + + small + Small instance size, maps to a scaling factor of 0.5. + + --scaling-factor=SCALING_FACTOR + The scaling factor of the service. This should be a float in the + range [0.1,6.0]. If the value is less than 1.0, then it should be a + multiple of 0.1. If the value is greater than 1.0, then it should be + a whole number. Float values should be formatted as x.y. + + --tier=TIER + The tier of the service. TIER must be one of: + + developer + The developer tier provides limited scalability and no fault + tolerance. Good for low-cost proof-of-concept. + + enterprise + The enterprise tier provides multi-zone high availability, and + sufficient scalability for enterprise-level Dataproc Metastore + workloads. + Information used to configure the Hive metastore service as a service principal in a Kerberos realm. diff --git a/gcloud/metastore/services/update b/gcloud/metastore/services/update index 434339f24..ce9a939a0 100644 --- a/gcloud/metastore/services/update +++ b/gcloud/metastore/services/update @@ -3,12 +3,16 @@ NAME SYNOPSIS gcloud metastore services update (SERVICE : --location=LOCATION) [--async] - [--port=PORT] [--tier=TIER] [--update-labels=[KEY=VALUE,...]] + [--port=PORT] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] + [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR + | --tier=TIER] [--kerberos-principal=KERBEROS_PRINCIPAL --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [--update-auxiliary-versions-from-file=UPDATE_AUXILIARY_VERSIONS_FROM_FILE | --add-auxiliary-versions=[ADD_AUXILIARY_VERSIONS, + ...] --clear-auxiliary-versions] [--update-hive-metastore-configs-from-file=UPDATE_HIVE_METASTORE_CONFIGS_FROM_FILE | --update-hive-metastore-configs=[UPDATE_HIVE_METASTORE_CONFIGS, ...] --clear-hive-metastore-configs | --remove-hive-metastore-configs=[REMOVE_HIVE_METASTORE_CONFIGS, @@ -70,18 +74,6 @@ FLAGS --port=PORT The TCP port on which the Metastore service will listen. - --tier=TIER - The tier of the service. TIER must be one of: - - developer - The developer tier provides limited scalability and no fault - tolerance. Good for low-cost proof-of-concept. - - enterprise - The enterprise tier provides multi-zone high availability, and - sufficient scalability for enterprise-level Dataproc Metastore - workloads. - --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. @@ -111,6 +103,46 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + The instance size of the Dataproc Metastore instance. + + At most one of these can be specified: + + --instance-size=INSTANCE_SIZE + The instance size of the service. INSTANCE_SIZE must be one of: + + extra_large + Extra large instance size, maps to a scaling factor of 6.0. + + extra_small + Extra small instance size, maps to a scaling factor of 0.1. + + large + Large instance size, maps to a scaling factor of 3.0. + + medium + Medium instance size, maps to a scaling factor of 1.0. + + small + Small instance size, maps to a scaling factor of 0.5. + + --scaling-factor=SCALING_FACTOR + The scaling factor of the service. This should be a float in the + range [0.1,6.0]. If the value is less than 1.0, then it should be a + multiple of 0.1. If the value is greater than 1.0, then it should be + a whole number. + + --tier=TIER + The tier of the service. TIER must be one of: + + developer + The developer tier provides limited scalability and no fault + tolerance. Good for low-cost proof-of-concept. + + enterprise + The enterprise tier provides multi-zone high availability, and + sufficient scalability for enterprise-level Dataproc Metastore + workloads. + Information used to configure the Hive metastore service as a service principal in a Kerberos realm. @@ -148,6 +180,50 @@ FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + Auxiliary versions configuration for the Dataproc Metastore service. When + specified, a secondary Hive metastore service is created along with the + primary service. + + At most one of these can be specified: + + --update-auxiliary-versions-from-file=UPDATE_AUXILIARY_VERSIONS_FROM_FILE + Path to a YAML file containing the auxiliary versions configuration + for Dataproc Metastore instance. The file should contain a unique + auxiliary service name and auxiliary version that is lower than the + primary service version. The primary version's Hive metastore + configs are applied to the auxiliary version. Additional Hive + metastore configs can be specified for the auxiliary version using + "config_overrides". If a specified config property has already been + overridden in the primary Hive metastore version's configs, the + auxiliary version's override takes precedence. The contents of the + file should be structured as follows: + + YAML: + + - name: aux-service1 + version: x.y.z + config_overrides: + key1: value1 + key2: value2 + ... + - name: aux-service2 + version: x.y.z + config_overrides: + key1: value1 + key2: value2 + ... + ... + + --add-auxiliary-versions=[ADD_AUXILIARY_VERSIONS,...] + Comma-separated list of auxiliary Hive metastore versions to + deploy. Auxiliary Hive metastore versions must be less than the + primary Hive metastore service's version. + + --clear-auxiliary-versions + Clears the existing auxiliary services attached to the primary Hive + metastore services. If --add-auxiliary-versions is also specified, + --clear-auxiliary-versions is applied first. + Configuration properties specific to running Hive metastore software as the metastore service. diff --git a/gcloud/spanner/databases/execute-sql b/gcloud/spanner/databases/execute-sql index dd35f850e..ebc4ef75d 100644 --- a/gcloud/spanner/databases/execute-sql +++ b/gcloud/spanner/databases/execute-sql @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud spanner databases execute-sql (DATABASE : --instance=INSTANCE) - --sql=SQL [--enable-partitioned-dml] + --sql=SQL [--database-role=DATABASE_ROLE] [--enable-partitioned-dml] [--query-mode=QUERY_MODE; default="NORMAL"] [--timeout=TIMEOUT; default="10m"] [--read-timestamp=TIMESTAMP | --strong] [GCLOUD_WIDE_FLAG ...] @@ -54,6 +54,9 @@ REQUIRED FLAGS at https://cloud.google.com/spanner/docs/query-syntax OPTIONAL FLAGS + --database-role=DATABASE_ROLE + Database role user assumes while accessing the database. + --enable-partitioned-dml Execute DML statement using Partitioned DML diff --git a/gcloud/spanner/databases/help b/gcloud/spanner/databases/help index e3116719e..0e371370b 100644 --- a/gcloud/spanner/databases/help +++ b/gcloud/spanner/databases/help @@ -18,6 +18,9 @@ GROUPS ddl Manage the DDL for Cloud Spanner databases. + roles + Manage Cloud Spanner database roles. + sessions Manage the sessions for Cloud Spanner databases. diff --git a/gcloud/spanner/databases/roles/help b/gcloud/spanner/databases/roles/help new file mode 100644 index 000000000..ec87e49d5 --- /dev/null +++ b/gcloud/spanner/databases/roles/help @@ -0,0 +1,27 @@ +NAME + gcloud spanner databases roles - manage Cloud Spanner database roles + +SYNOPSIS + gcloud spanner databases roles COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Cloud Spanner database roles. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + List the Cloud Spanner database roles defined in the given database. + +NOTES + These variants are also available: + + $ gcloud alpha spanner databases roles + + $ gcloud beta spanner databases roles + diff --git a/gcloud/spanner/databases/roles/list b/gcloud/spanner/databases/roles/list new file mode 100644 index 000000000..b4f6daf41 --- /dev/null +++ b/gcloud/spanner/databases/roles/list @@ -0,0 +1,94 @@ +NAME + gcloud spanner databases roles list - list the Cloud Spanner database roles + defined in the given database + +SYNOPSIS + gcloud spanner databases roles list + (--database=DATABASE : --instance=INSTANCE) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List the Cloud Spanner database roles defined in the given database. + +EXAMPLES + To list the Cloud Spanner database roles in a database, run: + + $ gcloud spanner databases roles list --instance=my-instance-id \ + --database=my-database-id + +REQUIRED FLAGS + Database resource - The Cloud Spanner database in which to list database + roles. 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 --database 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. + + --database=DATABASE + ID of the database or fully qualified identifier for the database. To + set the database attribute: + ▸ provide the argument --database on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --instance=INSTANCE + The Cloud Spanner instance for the database. To set the instance + attribute: + ▸ provide the argument --database on the command line with a fully + specified name; + ▸ provide the argument --instance on the command line; + ▸ set the property spanner/instance. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha spanner databases roles list + + $ gcloud beta spanner databases roles list + diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index fc4a9d5c9..a7b968426 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -14,7 +14,7 @@ SYNOPSIS [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--diff] [--[no-]enable-bin-log] [--[no-]enable-database-replication] - [--enable-google-private-path] [--enable-password-policy] + [--[no-]enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] [--follow-gae-app=FOLLOW_GAE_APP] [--[no-]insights-config-query-insights-enabled] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -164,12 +164,13 @@ FLAGS --enable-database-replication to enable and --no-enable-database-replication to disable. - --enable-google-private-path + --[no-]enable-google-private-path Enable a private path for Google Cloud services. This flag specifies whether the instance is accessible to internal Google Cloud services such as BigQuery. This is only applicable to MySQL and PostgreSQL instances that don't use public IP. Currently, SQL Server isn't - supported. + supported. Use --enable-google-private-path to enable and + --no-enable-google-private-path to disable. --enable-password-policy Enable the password policy, which enforces user password management diff --git a/gcloud/workflows/execute b/gcloud/workflows/execute index 5c5b46936..731c7b4dd 100644 --- a/gcloud/workflows/execute +++ b/gcloud/workflows/execute @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud workflows execute (WORKFLOW : --location=LOCATION) [--call-log-level=CALL_LOG_LEVEL; default="none"] [--data=DATA] - [GCLOUD_WIDE_FLAG ...] + [--labels=[LABELS,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Execute a workflow. @@ -64,6 +64,13 @@ FLAGS JSON string with data that will be passed to the workflow as an argument. + --labels=[LABELS,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens, + underscores, lowercase characters, and numbers. Values must contain + only hyphens, underscores, lowercase characters, and numbers. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/workflows/run b/gcloud/workflows/run index e38204383..ebdc8e651 100644 --- a/gcloud/workflows/run +++ b/gcloud/workflows/run @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud workflows run (WORKFLOW : --location=LOCATION) [--call-log-level=CALL_LOG_LEVEL; default="none"] [--data=DATA] - [GCLOUD_WIDE_FLAG ...] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Execute a workflow and wait for the execution to complete. @@ -14,7 +14,12 @@ EXAMPLES To execute a workflow named my-workflow with the data that will be passed to the workflow, run: - $ gcloud workflows run my-workflow --data=my-data + $ gcloud workflows run my-workflow `--data=my-data` + + To add two labels {foo: bar, baz: qux} to the execution, run: + + $ gcloud workflows run my-workflow `--data=my-data` \ + `--labels=foo=bar,baz=qux` POSITIONAL ARGUMENTS Workflow resource - Name of the workflow to execute. The arguments in this @@ -61,6 +66,14 @@ FLAGS JSON string with data that will be passed to the workflow as an argument. + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format,