diff --git a/gcloud/_version b/gcloud/_version index 302ec281d..b71dcde89 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,6 +1,6 @@ -Google Cloud SDK 388.0.0 -alpha 2022.05.27 -beta 2022.05.27 +Google Cloud SDK 389.0.0 +alpha 2022.06.03 +beta 2022.06.03 bq 2.0.74 -core 2022.05.27 +core 2022.06.03 gsutil 5.10 diff --git a/gcloud/alpha/anthos/config/controller/create b/gcloud/alpha/anthos/config/controller/create index 15288f65e..c450f85bf 100644 --- a/gcloud/alpha/anthos/config/controller/create +++ b/gcloud/alpha/anthos/config/controller/create @@ -44,9 +44,9 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Config Controller instance location. Currently, only us-central1, us-east1, northamerica-northeast1, - northamerica-northeast2, europe-north1, australia-southeast1, - asia-northeast1, and asia-northeast2 are supported. To set the - location attribute: + northamerica-northeast2, europe-north1, europe-west1, europe-west3, + australia-southeast1, australia-southeast2, asia-northeast1, and + asia-northeast2 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/alpha/anthos/config/controller/delete b/gcloud/alpha/anthos/config/controller/delete index cf887d1c4..b255ce504 100644 --- a/gcloud/alpha/anthos/config/controller/delete +++ b/gcloud/alpha/anthos/config/controller/delete @@ -39,9 +39,9 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. Currently, only us-central1, us-east1, northamerica-northeast1, - northamerica-northeast2, europe-north1, australia-southeast1, - asia-northeast1 and asia-northeast2 are supported. To set the - location attribute: + northamerica-northeast2, europe-north1, europe-west1, europe-west3, + australia-southeast1, australia-southeast2, asia-northeast1 and + asia-northeast2 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/alpha/anthos/config/controller/describe b/gcloud/alpha/anthos/config/controller/describe index 0f873b37e..8239be8e0 100644 --- a/gcloud/alpha/anthos/config/controller/describe +++ b/gcloud/alpha/anthos/config/controller/describe @@ -40,9 +40,9 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. Currently, only us-central1, us-east1, northamerica-northeast1, - northamerica-northeast2, europe-north1, australia-southeast1, - asia-northeast1 and asia-northeast2 are supported. To set the - location attribute: + northamerica-northeast2, europe-north1, europe-west1, europe-west3, + australia-southeast1, australia-southeast2, asia-northeast1 and + asia-northeast2 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/alpha/anthos/config/controller/help b/gcloud/alpha/anthos/config/controller/help index 870d6dba6..05aa1a0d1 100644 --- a/gcloud/alpha/anthos/config/controller/help +++ b/gcloud/alpha/anthos/config/controller/help @@ -34,6 +34,9 @@ COMMANDS list (ALPHA) List Anthos Config Controller instances. + update + (ALPHA) Update an Anthos Config Controller instance. + 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/anthos/config/controller/update b/gcloud/alpha/anthos/config/controller/update new file mode 100644 index 000000000..45bd081c8 --- /dev/null +++ b/gcloud/alpha/anthos/config/controller/update @@ -0,0 +1,71 @@ +NAME + gcloud alpha anthos config controller update - update an Anthos Config + Controller instance + +SYNOPSIS + gcloud alpha anthos config controller update (NAME : --location=LOCATION) + [--async] [--man-block=MAN_BLOCK] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an Anthos Config Controller instance. + +EXAMPLES + To update the master authorized network for an existing Anthos Config + Controller instance, run: + + $ gcloud alpha anthos config controller update sample-instance \ + --man-block=MAN_BLOCK + +POSITIONAL ARGUMENTS + Instance resource - The identifier for a Config Controller instance. 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 name 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. + + NAME + ID of the instance or fully qualified identifier for the instance. To + set the name attribute: + ▸ provide the argument name on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The name of the Config Controller instance location. Currently, only + us-central1, us-east1, northamerica-northeast1, + northamerica-northeast2, europe-north1, europe-west1, europe-west3, + australia-southeast1, australia-southeast2, asia-northeast1, and + asia-northeast2 are supported. To set the location attribute: + ▸ provide the argument name on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --man-block=MAN_BLOCK + Master Authorized Network. Allows access to the Kubernetes control + plane from this block. Defaults to '0.0.0.0/0' if flag is not provided. + +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/anthos/config/operations/describe b/gcloud/alpha/anthos/config/operations/describe index 5a1f28948..7ab53cc54 100644 --- a/gcloud/alpha/anthos/config/operations/describe +++ b/gcloud/alpha/anthos/config/operations/describe @@ -40,9 +40,9 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. Currently, only us-central1, us-east1, northamerica-northeast1, - northamerica-northeast2, europe-north1, australia-southeast1, - asia-northeast1 and asia-northeast2 are supported. To set the - location attribute: + northamerica-northeast2, europe-north1, europe-west1, europe-west3, + australia-southeast1, australia-southeast2, asia-northeast1 and + asia-northeast2 are supported. To set the location attribute: ▸ provide the argument operation on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/alpha/artifacts/files/help b/gcloud/alpha/artifacts/files/help new file mode 100644 index 000000000..9c837a3d8 --- /dev/null +++ b/gcloud/alpha/artifacts/files/help @@ -0,0 +1,38 @@ +NAME + gcloud alpha artifacts files - manage Artifact Registry files + +SYNOPSIS + gcloud alpha artifacts files COMMAND [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list all files in the current project and artifacts/repository and + artifacts/location properties are set, run: + + $ gcloud alpha artifacts files list + + To list files under repository my-repo in the current project and location, + run: + + $ gcloud alpha artifacts files list --repository=my-repo + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (ALPHA) List Artifact Registry files. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud artifacts files + + $ gcloud beta artifacts files + diff --git a/gcloud/alpha/artifacts/files/list b/gcloud/alpha/artifacts/files/list new file mode 100644 index 000000000..5be14b49a --- /dev/null +++ b/gcloud/alpha/artifacts/files/list @@ -0,0 +1,128 @@ +NAME + gcloud alpha artifacts files list - list Artifact Registry files + +SYNOPSIS + gcloud alpha artifacts files list [--package=PACKAGE] [--tag=TAG] + [--version=VERSION] [--repository=REPOSITORY : --location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all Artifact Registry files in the specified repository and + location. + + To specify the maximum number of files to list, use the --limit flag. + +EXAMPLES + To list files in the current project under repository my-repo in + us-central1: + + $ gcloud alpha artifacts files list --repository=my-repo \ + --location=us-central1 + + The following command lists a maximum of five files: + + $ gcloud alpha artifacts files list --repository=my-repo \ + --location=us-central1 --limit=5 + + To list files in the current project under repository my-repo in + us-central1 owned by package my-package: + + $ gcloud alpha artifacts files list --repository=my-repo \ + --location=us-central1 --package=my-package + + To list files in the current project under repository my-repo in + us-central1 owned by package my-package and version 1.0.0: + + $ gcloud alpha artifacts files list --repository=my-repo \ + --location=us-central1 --package=my-package --version=1.0.0 + + To list files in the current project under repository my-repo in + us-central1 owned by package my-package and tag name my-tag: + + $ gcloud alpha artifacts files list --repository=my-repo \ + --location=us-central1 --package=my-package --tag=my-tag + +FLAGS + --package=PACKAGE + List all files in a specified artifact, such as a container image or a + language package. If you do not use --tag or --version in the command, + the command lists files in all versions of the artifact. + + --tag=TAG + List all files in the artifact version with the specified tag. This + flag only works with formats that use tags, such as container images. + Use the --package flag to specify the artifact. + + --version=VERSION + List all files in the specified artifact version. Use the --package + flag to specify the artifact. + + Repository resource - The Artifact Registry repository. If not specified, + the current artifacts/repository is used. The arguments in this group can + be used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. To set + the project attribute: + ◆ provide the argument --repository on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --location=LOCATION + Location of the repository. To set the location attribute: + ▸ provide the argument --repository on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud artifacts files list + + $ gcloud beta artifacts files list + diff --git a/gcloud/alpha/artifacts/help b/gcloud/alpha/artifacts/help index 7942b7dae..13c97b61e 100644 --- a/gcloud/alpha/artifacts/help +++ b/gcloud/alpha/artifacts/help @@ -21,6 +21,9 @@ GROUPS docker (ALPHA) Manage Artifact Registry container images and tags. + files + (ALPHA) Manage Artifact Registry files. + locations (ALPHA) Manage Artifact Registry resource locations. diff --git a/gcloud/alpha/assured/workloads/violations/describe b/gcloud/alpha/assured/workloads/violations/describe new file mode 100644 index 000000000..5c7888396 --- /dev/null +++ b/gcloud/alpha/assured/workloads/violations/describe @@ -0,0 +1,70 @@ +NAME + gcloud alpha assured workloads violations describe - describe Assured + Workloads Compliance Violation + +SYNOPSIS + gcloud alpha assured workloads violations describe + (VIOLATION : --location=LOCATION + --organization=ORGANIZATION --workload=WORKLOAD) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Obtain details about a given Compliance Violation. + +EXAMPLES + To describe an Assured Workloads Violation in the us-central1 region, + belonging to an organization with ID 123, with workload ID 456, with + violation ID 789, run: + + $ gcloud alpha assured workloads violations describe \ + organizations/123/locations/us-central1/workloads/456/\ + violations/789 + +POSITIONAL ARGUMENTS + Violation resource - The Assured Workloads violation resource to describe. + The arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + VIOLATION + ID of the violation or fully qualified identifier for the violation. + To set the violation attribute: + ▸ provide the argument violation on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location for the violation. To set the location attribute: + ▸ provide the argument violation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + The parent organization for the violation. To set the organization + attribute: + ▸ provide the argument violation on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. + + --workload=WORKLOAD + The workload for the violation. To set the workload attribute: + ▸ provide the argument violation on the command line with a fully + specified name; + ▸ provide the argument --workload 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/assured/workloads/violations/help b/gcloud/alpha/assured/workloads/violations/help index 31617bfe0..6af037aab 100644 --- a/gcloud/alpha/assured/workloads/violations/help +++ b/gcloud/alpha/assured/workloads/violations/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + describe + (ALPHA) Describe Assured Workloads Compliance Violation. + list (ALPHA) List all Assured Workloads violations that belong to a assured workloads environment. diff --git a/gcloud/alpha/auth/login b/gcloud/alpha/auth/login index b317c9e96..68c3d7616 100644 --- a/gcloud/alpha/auth/login +++ b/gcloud/alpha/auth/login @@ -93,14 +93,9 @@ FLAGS credentials. --launch-browser - (DEPRECATED) Launch a browser for authorization. If not enabled or if - it is not possible to launch a browser, prints a URL to standard output - to be copied. - - The --[no-]launch-browser flags are deprecated and will be removed on - June 7th 2022 (Release 389.0.0). Use --no-browser to replace - --no-launch-browser. Enabled by default, use --no-launch-browser to - disable. + Launch a browser for authorization. If not enabled or if it is not + possible to launch a browser, prints a URL to standard output to be + copied. Enabled by default, use --no-launch-browser to disable. --update-adc Write the obtained credentials to the well-known location for diff --git a/gcloud/alpha/composer/environments/create b/gcloud/alpha/composer/environments/create index 102289d18..b5c2cc00f 100644 --- a/gcloud/alpha/composer/environments/create +++ b/gcloud/alpha/composer/environments/create @@ -6,8 +6,7 @@ SYNOPSIS gcloud alpha composer environments create (ENVIRONMENT : --location=LOCATION) [--airflow-configs=[KEY=VALUE,...]] [--async] [--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE] - [--disk-size=DISK_SIZE] [--enable-ip-masq-agent] - [--env-variables=[NAME=VALUE,...]] + [--disk-size=DISK_SIZE] [--env-variables=[NAME=VALUE,...]] [--environment-size=ENVIRONMENT_SIZE] [--labels=[KEY=VALUE,...]] [--machine-type=MACHINE_TYPE] [--node-count=NODE_COUNT] [--oauth-scopes=[SCOPE,...]] [--python-version=PYTHON_VERSION] @@ -23,7 +22,8 @@ SYNOPSIS --web-server-ipv4-cidr=WEB_SERVER_IPV4_CIDR] [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR --cluster-secondary-range-name=CLUSTER_SECONDARY_RANGE_NAME - --enable-ip-alias --max-pods-per-node=MAX_PODS_PER_NODE + --enable-ip-alias --enable-ip-masq-agent + --max-pods-per-node=MAX_PODS_PER_NODE --services-ipv4-cidr=SERVICES_IPV4_CIDR --services-secondary-range-name=SERVICES_SECONDARY_RANGE_NAME] [--enable-master-authorized-networks @@ -111,12 +111,6 @@ FLAGS multiple of gigabytes. Cannot be updated after the environment has been created. If units are not provided, defaults to GB. - --enable-ip-masq-agent - When enabled the IP Masq Agent is deployed to the cluster with - configuration to masquarade all traffic except between pods. - - Cannot be specified unless --enable-ip-alias is also specified. - --env-variables=[NAME=VALUE,...] A comma-delimited list of environment variable NAME=VALUE pairs to provide to the Airflow scheduler, worker, and webserver processes. NAME @@ -297,6 +291,16 @@ FLAGS will require at least two secondary ranges in the subnetwork, one for the pod IPs and another to reserve space for the services range. + --enable-ip-masq-agent + When enabled, the IP Masquarade Agent + (https://cloud.google.com/composer/docs/enable-ip-masquerade-agent) + is deployed to your environment's cluster. It performs many-to-one IP + address translations to hide a pod's IP address behind the cluster + node's IP address. This is done when sending traffic to destinations + outside the cluster's pod CIDR range. + + Cannot be specified unless --enable-ip-alias is also specified. + --max-pods-per-node=MAX_PODS_PER_NODE Maximum number of pods that can be assigned to a single node, can be used to limit the size of IP range assigned to the node in VPC native diff --git a/gcloud/alpha/compute/backend-services/create b/gcloud/alpha/compute/backend-services/create index 9bede59d3..e98b88dae 100644 --- a/gcloud/alpha/compute/backend-services/create +++ b/gcloud/alpha/compute/backend-services/create @@ -266,8 +266,8 @@ FLAGS The logging options for the load balancer traffic served by this backend service. If logging is enabled, logs will be exported to Cloud Logging. This can only be specified if the protocol is HTTP, HTTPS, - HTTP2, TCP, or SSL. Disabled by default. Use --enable-logging to enable - and --no-enable-logging to disable. + HTTP2, TCP, SSL, UDP, or UNSPECIFIED. Disabled by default. Use + --enable-logging to enable and --no-enable-logging to disable. --[no-]enable-strong-affinity Enable or disable strong session affinity. This is only available for @@ -343,7 +343,8 @@ FLAGS This configures the sampling rate of requests to the load balancer where 1.0 means all logged requests are reported and 0.0 means no logged requests are reported. This can only be specified if the - protocol is HTTP, HTTPS, HTTP2, TCP, or SSL. The default value is 1.0. + protocol is HTTP, HTTPS, HTTP2, TCP, SSL, UDP, or UNSPECIFIED. The + default value is 0.0. --max-ttl=MAX_TTL Specifies the maximum allowed TTL for cached content served by this diff --git a/gcloud/alpha/compute/backend-services/update b/gcloud/alpha/compute/backend-services/update index dfb461d70..27fb05acb 100644 --- a/gcloud/alpha/compute/backend-services/update +++ b/gcloud/alpha/compute/backend-services/update @@ -179,8 +179,8 @@ FLAGS The logging options for the load balancer traffic served by this backend service. If logging is enabled, logs will be exported to Cloud Logging. This can only be specified if the protocol is HTTP, HTTPS, - HTTP2, TCP, or SSL. Disabled by default. Use --enable-logging to enable - and --no-enable-logging to disable. + HTTP2, TCP, SSL, UDP, or UNSPECIFIED. Disabled by default. Use + --enable-logging to enable and --no-enable-logging to disable. --[no-]enable-strong-affinity Enable or disable strong session affinity. This is only available for @@ -250,7 +250,8 @@ FLAGS This configures the sampling rate of requests to the load balancer where 1.0 means all logged requests are reported and 0.0 means no logged requests are reported. This can only be specified if the - protocol is HTTP, HTTPS, HTTP2, TCP, or SSL. The default value is 1.0. + protocol is HTTP, HTTPS, HTTP2, TCP, SSL, UDP, or UNSPECIFIED. The + default value is 0.0. --port-name=PORT_NAME Backend services for external HTTP(S) load balancing, internal HTTP(S) diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index f293dab5d..e37c830a1 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -918,7 +918,7 @@ FLAGS (DEPRECATED) Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. The --maintenance-policy flag is now deprecated. Please use --on-host-maintenance instead. MAINTENANCE_POLICY must be one of: @@ -933,7 +933,7 @@ FLAGS --on-host-maintenance=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index 4ffa7aac6..cd57757f9 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -750,7 +750,7 @@ FLAGS (DEPRECATED) Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. The --maintenance-policy flag is now deprecated. Please use --on-host-maintenance instead. MAINTENANCE_POLICY must be one of: @@ -765,7 +765,7 @@ FLAGS --on-host-maintenance=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index df3f3815f..17f045b8f 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -853,7 +853,7 @@ OPTIONAL FLAGS (DEPRECATED) Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. The --maintenance-policy flag is now deprecated. Please use --on-host-maintenance instead. MAINTENANCE_POLICY must be one of: @@ -868,7 +868,7 @@ OPTIONAL FLAGS --on-host-maintenance=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 5684e354d..2be8a7190 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -1040,7 +1040,7 @@ FLAGS (DEPRECATED) Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. The --maintenance-policy flag is now deprecated. Please use --on-host-maintenance instead. MAINTENANCE_POLICY must be one of: @@ -1055,7 +1055,7 @@ FLAGS --on-host-maintenance=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index 129cf5f4c..35c4789fd 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -856,7 +856,7 @@ FLAGS (DEPRECATED) Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. The --maintenance-policy flag is now deprecated. Please use --on-host-maintenance instead. MAINTENANCE_POLICY must be one of: @@ -871,7 +871,7 @@ FLAGS --on-host-maintenance=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/alpha/compute/instances/set-scheduling b/gcloud/alpha/compute/instances/set-scheduling index 2fbee5ab7..4052fee14 100644 --- a/gcloud/alpha/compute/instances/set-scheduling +++ b/gcloud/alpha/compute/instances/set-scheduling @@ -163,7 +163,7 @@ FLAGS (DEPRECATED) Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. The --maintenance-policy flag is now deprecated. Please use --on-host-maintenance instead. MAINTENANCE_POLICY must be one of: @@ -178,7 +178,7 @@ FLAGS --on-host-maintenance=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/alpha/compute/networks/create b/gcloud/alpha/compute/networks/create index e42253136..4ed4b9c52 100644 --- a/gcloud/alpha/compute/networks/create +++ b/gcloud/alpha/compute/networks/create @@ -56,9 +56,9 @@ FLAGS --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet - that can be transmitted on this network. Default value is 1460 bytes, - and the maximum is 1500 bytes. The MTU advertised via DHCP to all - instances attached to this network. + that can be transmitted on this network. Default value is 1460 bytes. + The minimum value is 1300 bytes and the maximum value is 8896 bytes. + The MTU advertised via DHCP to all instances attached to this network. --network-firewall-policy-enforcement-order=NETWORK_FIREWALL_POLICY_ENFORCEMENT_ORDER The Network Firewall Policy enforcement order of this network. If not diff --git a/gcloud/alpha/compute/networks/update b/gcloud/alpha/compute/networks/update index b2f4ad012..45d449437 100644 --- a/gcloud/alpha/compute/networks/update +++ b/gcloud/alpha/compute/networks/update @@ -39,9 +39,9 @@ FLAGS --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet - that can be transmitted on this network. Default value is 1460 bytes, - and the maximum is 1500 bytes. The MTU advertised via DHCP to all - instances attached to this network. + that can be transmitted on this network. Default value is 1460 bytes. + The minimum value is 1300 bytes and the maximum value is 8896 bytes. + The MTU advertised via DHCP to all instances attached to this network. --network-firewall-policy-enforcement-order=NETWORK_FIREWALL_POLICY_ENFORCEMENT_ORDER The Network Firewall Policy enforcement order of this network. If not diff --git a/gcloud/alpha/compute/reservations/create b/gcloud/alpha/compute/reservations/create index 0b1caf735..337148f8d 100644 --- a/gcloud/alpha/compute/reservations/create +++ b/gcloud/alpha/compute/reservations/create @@ -9,7 +9,8 @@ SYNOPSIS --local-ssd=[interface=INTERFACE],[size=SIZE] --maintenance-freeze-duration=MAINTENANCE_FREEZE_DURATION --maintenance-interval=MAINTENANCE_INTERVAL - --min-cpu-platform=MIN_CPU_PLATFORM --require-specific-reservation) + --min-cpu-platform=MIN_CPU_PLATFORM + --require-specific-reservation --resource-policies=[KEY=VALUE,...]) [--description=DESCRIPTION] [--zone=ZONE] [--share-setting=SHARE_SETTING --share-with=SHARE_WITH,[SHARE_WITH,...]] [GCLOUD_WIDE_FLAG ...] @@ -97,6 +98,10 @@ REQUIRED FLAGS reservation by name using --reservation-affinity=specific can consume from this reservation. + --resource-policies=[KEY=VALUE,...] + Specify if this is reservation with resource policy. If you omit this + flag, no resource policy will be added to this reservation. + OPTIONAL FLAGS --description=DESCRIPTION An optional description of the reservation to create. diff --git a/gcloud/alpha/compute/target-https-proxies/create b/gcloud/alpha/compute/target-https-proxies/create index 4b4570cdc..f31bd7fd0 100644 --- a/gcloud/alpha/compute/target-https-proxies/create +++ b/gcloud/alpha/compute/target-https-proxies/create @@ -31,12 +31,12 @@ EXAMPLES pointing to this map by running: $ gcloud alpha compute target-https-proxies create PROXY_NAME \ - --url-map=URL_MAP --ssl-certificates=SSL_CERTIFIFCATE + --url-map=URL_MAP --ssl-certificates=SSL_CERTIFICATE Create a regional target HTTPS proxy by running: $ gcloud alpha compute target-https-proxies create PROXY_NAME \ - --url-map=URL_MAP --ssl-certificates=SSL_CERTIFIFCATE \ + --url-map=URL_MAP --ssl-certificates=SSL_CERTIFICATE \ --region=REGION_NAME POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index 831f8fe94..f02d1a033 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -476,7 +476,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -516,39 +516,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index 7aefdb22b..5d8e4792d 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -481,7 +481,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -521,39 +521,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index f3cf6e2bb..bb3becc9e 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -49,7 +49,7 @@ EXAMPLES $ gcloud alpha config set proxy/port 8080 For a full list of accepted values, see the Google Cloud CLI properties - page: https://cloud.google.com/sdk/docs/properties + page: https://cloud.google.com/sdk/docs/properties. POSITIONAL ARGUMENTS SECTION/PROPERTY @@ -494,7 +494,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -534,39 +534,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 4c981840f..adba40846 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -455,7 +455,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -495,39 +495,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/alpha/container/aws/node-pools/update b/gcloud/alpha/container/aws/node-pools/update index ba208b213..eefc099e5 100644 --- a/gcloud/alpha/container/aws/node-pools/update +++ b/gcloud/alpha/container/aws/node-pools/update @@ -6,7 +6,8 @@ SYNOPSIS gcloud alpha container aws node-pools update (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] [--config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN] - [--node-version=NODE_VERSION] [--root-volume-iops=ROOT_VOLUME_IOPS] + [--instance-type=INSTANCE_TYPE] [--node-version=NODE_VERSION] + [--root-volume-iops=ROOT_VOLUME_IOPS] [--root-volume-kms-key-arn=ROOT_VOLUME_KMS_KEY_ARN] [--root-volume-size=ROOT_VOLUME_SIZE] [--root-volume-type=ROOT_VOLUME_TYPE] [--validate-only] @@ -71,6 +72,9 @@ FLAGS --config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN Amazon Resource Name (ARN) of the AWS KMS key to encrypt the user data. + --instance-type=INSTANCE_TYPE + AWS EC2 instance type for the node pool's nodes. + --node-version=NODE_VERSION Kubernetes version to use for the node pool. diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 6a7437550..d4ef00c94 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -314,8 +314,9 @@ FLAGS Size for node VM boot disks in GB. Defaults to 100GB. --disk-type=DISK_TYPE - Type of the node VM boot disk. Defaults to pd-standard. DISK_TYPE must - be one of: pd-standard, pd-ssd, pd-balanced. + Type of the node VM boot disk. For version 1.24.0+, defaults to + pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE + must be one of: pd-standard, pd-ssd, pd-balanced. --enable-autorepair Enable node autorepair feature for a cluster's default node pool(s). diff --git a/gcloud/alpha/container/fleet/config-management/apply b/gcloud/alpha/container/fleet/config-management/apply index 77fc48f1e..eb3058c00 100644 --- a/gcloud/alpha/container/fleet/config-management/apply +++ b/gcloud/alpha/container/fleet/config-management/apply @@ -18,7 +18,7 @@ EXAMPLES then run: $ gcloud alpha container fleet config-management apply \ - --membership=CLUSTER_NAME --config=APPLY-SPEC.YAML \ + --membership=MEMBERSHIP_NAME --config=APPLY-SPEC.YAML \ --version=VERSION REQUIRED FLAGS diff --git a/gcloud/alpha/container/fleet/config-management/delete b/gcloud/alpha/container/fleet/config-management/delete index e451aa488..a4da5af0e 100644 --- a/gcloud/alpha/container/fleet/config-management/delete +++ b/gcloud/alpha/container/fleet/config-management/delete @@ -16,10 +16,10 @@ DESCRIPTION existing ConfigManagement resources in the clusters will become unmanaged. EXAMPLES - To remove the Config Management Feature spec for a Membership, run: + To remove the Config Management Feature spec for a membership, run: $ gcloud alpha container fleet config-management delete \ - --membership=CLUSTER_NAME + --membership=MEMBERSHIP_NAME FLAGS --membership=MEMBERSHIP diff --git a/gcloud/alpha/container/fleet/config-management/unmanage b/gcloud/alpha/container/fleet/config-management/unmanage index 270156aee..c4b5bfb18 100644 --- a/gcloud/alpha/container/fleet/config-management/unmanage +++ b/gcloud/alpha/container/fleet/config-management/unmanage @@ -12,10 +12,10 @@ DESCRIPTION unmanaged. EXAMPLES - To remove the Config Management Feature spec for a Membership, run: + To remove the Config Management Feature spec for a membership, run: $ gcloud alpha container fleet config-management unmanage \ - --membership=CLUSTER_NAME + --membership=MEMBERSHIP_NAME FLAGS --membership=MEMBERSHIP diff --git a/gcloud/alpha/container/fleet/config-management/upgrade b/gcloud/alpha/container/fleet/config-management/upgrade index 4e46bb215..04f02a648 100644 --- a/gcloud/alpha/container/fleet/config-management/upgrade +++ b/gcloud/alpha/container/fleet/config-management/upgrade @@ -11,10 +11,10 @@ DESCRIPTION Config Management Feature. EXAMPLES - To upgrade a membership named CLUSTER_NAME, run: + To upgrade a membership named MEMBERSHIP_NAME, run: $ gcloud alpha container fleet config-management upgrade \ - --membership=CLUSTER_NAME --version=VERSION + --membership=MEMBERSHIP_NAME --version=VERSION REQUIRED FLAGS --version=VERSION diff --git a/gcloud/alpha/container/fleet/help b/gcloud/alpha/container/fleet/help index 260584ae0..7bfd32948 100644 --- a/gcloud/alpha/container/fleet/help +++ b/gcloud/alpha/container/fleet/help @@ -62,7 +62,7 @@ GROUPS memberships (ALPHA) Manage memberships of all your GKE and other Kubernetes cluster - with Fleet. + with fleets. mesh (ALPHA) Manage Service Mesh Feature. diff --git a/gcloud/alpha/container/fleet/identity-service/apply b/gcloud/alpha/container/fleet/identity-service/apply index ec241f191..b15dad2cb 100644 --- a/gcloud/alpha/container/fleet/identity-service/apply +++ b/gcloud/alpha/container/fleet/identity-service/apply @@ -18,7 +18,7 @@ EXAMPLES To apply an Identity Service configuration for a membership, run: $ gcloud alpha container fleet identity-service apply \ - --membership=CLUSTER_NAME \ + --membership=MEMBERSHIP_NAME \ --config=/path/to/identity-service.yaml REQUIRED FLAGS diff --git a/gcloud/alpha/container/fleet/identity-service/delete b/gcloud/alpha/container/fleet/identity-service/delete index 1e6617bcb..df15dc1c7 100644 --- a/gcloud/alpha/container/fleet/identity-service/delete +++ b/gcloud/alpha/container/fleet/identity-service/delete @@ -13,7 +13,7 @@ EXAMPLES To delete an Identity Service configuration for a membership, run: $ gcloud alpha container fleet identity-service delete \ - --membership=CLUSTER_NAME + --membership=MEMBERSHIP_NAME FLAGS --membership=MEMBERSHIP diff --git a/gcloud/alpha/container/fleet/memberships/delete b/gcloud/alpha/container/fleet/memberships/delete index 2e3033a48..38dcae25e 100644 --- a/gcloud/alpha/container/fleet/memberships/delete +++ b/gcloud/alpha/container/fleet/memberships/delete @@ -6,7 +6,7 @@ SYNOPSIS (MEMBERSHIP : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command deletes the Fleet membership resource corresponding to + (ALPHA) This command deletes the Fleet Membership resource corresponding to the cluster. This command is intended to delete stale Fleet Membership resources as @@ -22,7 +22,7 @@ EXAMPLES $ gcloud alpha container fleet memberships list - Delete a membership from Fleet: + Delete a membership from the active project's fleet: $ gcloud alpha container fleet memberships delete MEMBERSHIP_NAME diff --git a/gcloud/alpha/container/fleet/memberships/get-credentials b/gcloud/alpha/container/fleet/memberships/get-credentials index b53448805..9c7640286 100644 --- a/gcloud/alpha/container/fleet/memberships/get-credentials +++ b/gcloud/alpha/container/fleet/memberships/get-credentials @@ -1,6 +1,6 @@ NAME gcloud alpha container fleet memberships get-credentials - fetch - credentials for a Fleet-registered cluster to be used in Connect + credentials for a fleet-registered cluster to be used in Connect Gateway SYNOPSIS @@ -10,7 +10,7 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha container fleet memberships get-credentials updates the kubeconfig file with the appropriate credentials and endpoint - information to send kubectl commands to a Fleet-registered and connected + information to send kubectl commands to a fleet-registered and connected cluster through Connect Gateway Service. It takes a project, passed through by set defaults or flags. By default, diff --git a/gcloud/alpha/container/fleet/memberships/help b/gcloud/alpha/container/fleet/memberships/help index 30e9e8a64..0731fc37b 100644 --- a/gcloud/alpha/container/fleet/memberships/help +++ b/gcloud/alpha/container/fleet/memberships/help @@ -1,13 +1,13 @@ NAME gcloud alpha container fleet memberships - manage memberships of all your - GKE and other Kubernetes cluster with Fleet + GKE and other Kubernetes cluster with fleets SYNOPSIS gcloud alpha container fleet memberships COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Manage memberships of all your GKE and other Kubernetes cluster - with Fleet. + with fleets. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -27,14 +27,14 @@ COMMANDS (ALPHA) Generate RBAC policy files for connected clusters by the user. get-credentials - (ALPHA) Fetch credentials for a Fleet-registered cluster to be used in + (ALPHA) Fetch credentials for a fleet-registered cluster to be used in Connect Gateway. list (ALPHA) List memberships. register - (ALPHA) Register a cluster with Fleet. + (ALPHA) Register a cluster with a fleet. unregister (ALPHA) Unregister a cluster from Fleet. diff --git a/gcloud/alpha/container/fleet/memberships/list b/gcloud/alpha/container/fleet/memberships/list index 26a5c83c2..dd3341d18 100644 --- a/gcloud/alpha/container/fleet/memberships/list +++ b/gcloud/alpha/container/fleet/memberships/list @@ -7,10 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List memberships in Fleet. + (ALPHA) List memberships in a fleet. EXAMPLES - List memberships in Fleet: + List memberships in the active project's fleet: $ gcloud alpha container fleet memberships list diff --git a/gcloud/alpha/container/fleet/memberships/register b/gcloud/alpha/container/fleet/memberships/register index 7520ee6bf..e39493ec0 100644 --- a/gcloud/alpha/container/fleet/memberships/register +++ b/gcloud/alpha/container/fleet/memberships/register @@ -1,9 +1,9 @@ NAME gcloud alpha container fleet memberships register - register a cluster with - Fleet + a fleet SYNOPSIS - gcloud alpha container fleet memberships register CLUSTER_NAME + gcloud alpha container fleet memberships register MEMBERSHIP_NAME (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) (--service-account-key-file=SERVICE_ACCOUNT_KEY_FILE @@ -13,15 +13,15 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command registers a cluster with the Fleet by: + (ALPHA) This command registers a cluster with the fleet by: 1. Creating a Fleet Membership resource corresponding to the cluster. 2. Adding in-cluster Kubernetes Resources that make the cluster exclusive - to one Fleet. + to one fleet. 3. Installing the Connect Agent into this cluster. A successful registration implies that the cluster is now exclusive to a - single Fleet. + single fleet. For more information about Connect Agent, go to: https://cloud.google.com/anthos/multicluster-management/connect/overview/ @@ -40,9 +40,9 @@ DESCRIPTION If the cluster is already registered to another Fleet, the registration is not successful. - Rerunning this command against the same cluster with the same CLUSTER_NAME - and target GKEFleet is successful and upgrades the Connect Agent if a new - agent is available. + Rerunning this command against the same cluster with the same + MEMBERSHIP_NAME and target GKEFleet is successful and upgrades the Connect + Agent if a new agent is available. EXAMPLES Register a non-GKE or GKE On-Prem cluster referenced from a specific @@ -117,9 +117,9 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json POSITIONAL ARGUMENTS - CLUSTER_NAME + MEMBERSHIP_NAME The membership name that you choose to uniquely represents the cluster - being registered on the Fleet. + being registered on the fleet. REQUIRED FLAGS Cluster identifier. @@ -171,7 +171,7 @@ REQUIRED FLAGS Workload Identity --enable-workload-identity - Enable Workload Identity when registering the cluster with Fleet. + Enable Workload Identity when registering the cluster with a fleet. Ensure that GKE Workload Identity is enabled on your GKE cluster, it is a requirement for using Workload Identity with memberships. Refer to the Registering a cluster using Workload Identity section diff --git a/gcloud/alpha/container/fleet/memberships/unregister b/gcloud/alpha/container/fleet/memberships/unregister index bfe1bdd2c..bd28043ca 100644 --- a/gcloud/alpha/container/fleet/memberships/unregister +++ b/gcloud/alpha/container/fleet/memberships/unregister @@ -3,18 +3,18 @@ NAME from Fleet SYNOPSIS - gcloud alpha container fleet memberships unregister CLUSTER_NAME + gcloud alpha container fleet memberships unregister MEMBERSHIP_NAME (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command unregisters a cluster with the Fleet by: + (ALPHA) This command unregisters a cluster with the fleet by: 1. Deleting the Fleet Membership resource for this cluster (a.k.a `gcloud alpha container fleet memberships delete`). 2. Removing the corresponding in-cluster Kubernetes Resources that make the - cluster exclusive to one Fleet (a.k.a `kubectl delete memberships + cluster exclusive to one fleet (a.k.a `kubectl delete memberships membership`). 3. Uninstalling the Connect Agent from this cluster (a.k.a `kubectl delete on the gke-connect namespace`). @@ -58,7 +58,7 @@ EXAMPLES my-membership --gke-cluster=my-cluster-region-or-zone/my-cluster POSITIONAL ARGUMENTS - CLUSTER_NAME + MEMBERSHIP_NAME The membership name that corresponds to the cluster being unregistered. To get list of all the memberships on the Fleet, consider using the command: gcloud alpha container fleet memberships list. diff --git a/gcloud/alpha/container/hub/config-management/apply b/gcloud/alpha/container/hub/config-management/apply index 8fd4d9de0..680ea78ae 100644 --- a/gcloud/alpha/container/hub/config-management/apply +++ b/gcloud/alpha/container/hub/config-management/apply @@ -18,7 +18,7 @@ EXAMPLES then run: $ gcloud alpha container hub config-management apply \ - --membership=CLUSTER_NAME --config=APPLY-SPEC.YAML \ + --membership=MEMBERSHIP_NAME --config=APPLY-SPEC.YAML \ --version=VERSION REQUIRED FLAGS diff --git a/gcloud/alpha/container/hub/config-management/delete b/gcloud/alpha/container/hub/config-management/delete index ec3833f58..d3f16d241 100644 --- a/gcloud/alpha/container/hub/config-management/delete +++ b/gcloud/alpha/container/hub/config-management/delete @@ -16,10 +16,10 @@ DESCRIPTION existing ConfigManagement resources in the clusters will become unmanaged. EXAMPLES - To remove the Config Management Feature spec for a Membership, run: + To remove the Config Management Feature spec for a membership, run: $ gcloud alpha container hub config-management delete \ - --membership=CLUSTER_NAME + --membership=MEMBERSHIP_NAME FLAGS --membership=MEMBERSHIP diff --git a/gcloud/alpha/container/hub/config-management/unmanage b/gcloud/alpha/container/hub/config-management/unmanage index 776622533..192b056ee 100644 --- a/gcloud/alpha/container/hub/config-management/unmanage +++ b/gcloud/alpha/container/hub/config-management/unmanage @@ -12,10 +12,10 @@ DESCRIPTION unmanaged. EXAMPLES - To remove the Config Management Feature spec for a Membership, run: + To remove the Config Management Feature spec for a membership, run: $ gcloud alpha container hub config-management unmanage \ - --membership=CLUSTER_NAME + --membership=MEMBERSHIP_NAME FLAGS --membership=MEMBERSHIP diff --git a/gcloud/alpha/container/hub/config-management/upgrade b/gcloud/alpha/container/hub/config-management/upgrade index c2e1421e7..9fffe0883 100644 --- a/gcloud/alpha/container/hub/config-management/upgrade +++ b/gcloud/alpha/container/hub/config-management/upgrade @@ -11,10 +11,10 @@ DESCRIPTION Config Management Feature. EXAMPLES - To upgrade a membership named CLUSTER_NAME, run: + To upgrade a membership named MEMBERSHIP_NAME, run: $ gcloud alpha container hub config-management upgrade \ - --membership=CLUSTER_NAME --version=VERSION + --membership=MEMBERSHIP_NAME --version=VERSION REQUIRED FLAGS --version=VERSION diff --git a/gcloud/alpha/container/hub/help b/gcloud/alpha/container/hub/help index fb0dd1dbd..f93ed617f 100644 --- a/gcloud/alpha/container/hub/help +++ b/gcloud/alpha/container/hub/help @@ -62,7 +62,7 @@ GROUPS memberships (ALPHA) Manage memberships of all your GKE and other Kubernetes cluster - with Fleet. + with fleets. mesh (ALPHA) Manage Service Mesh Feature. diff --git a/gcloud/alpha/container/hub/identity-service/apply b/gcloud/alpha/container/hub/identity-service/apply index 0b98d617d..4bc0246ef 100644 --- a/gcloud/alpha/container/hub/identity-service/apply +++ b/gcloud/alpha/container/hub/identity-service/apply @@ -18,7 +18,7 @@ EXAMPLES To apply an Identity Service configuration for a membership, run: $ gcloud alpha container hub identity-service apply \ - --membership=CLUSTER_NAME \ + --membership=MEMBERSHIP_NAME \ --config=/path/to/identity-service.yaml REQUIRED FLAGS diff --git a/gcloud/alpha/container/hub/identity-service/delete b/gcloud/alpha/container/hub/identity-service/delete index df592399d..b2a771b7b 100644 --- a/gcloud/alpha/container/hub/identity-service/delete +++ b/gcloud/alpha/container/hub/identity-service/delete @@ -13,7 +13,7 @@ EXAMPLES To delete an Identity Service configuration for a membership, run: $ gcloud alpha container hub identity-service delete \ - --membership=CLUSTER_NAME + --membership=MEMBERSHIP_NAME FLAGS --membership=MEMBERSHIP diff --git a/gcloud/alpha/container/hub/memberships/delete b/gcloud/alpha/container/hub/memberships/delete index 4a92f96d9..c0d57c3e8 100644 --- a/gcloud/alpha/container/hub/memberships/delete +++ b/gcloud/alpha/container/hub/memberships/delete @@ -6,7 +6,7 @@ SYNOPSIS (MEMBERSHIP : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command deletes the Fleet membership resource corresponding to + (ALPHA) This command deletes the Fleet Membership resource corresponding to the cluster. This command is intended to delete stale Fleet Membership resources as @@ -22,7 +22,7 @@ EXAMPLES $ gcloud alpha container hub memberships list - Delete a membership from Fleet: + Delete a membership from the active project's fleet: $ gcloud alpha container hub memberships delete MEMBERSHIP_NAME diff --git a/gcloud/alpha/container/hub/memberships/get-credentials b/gcloud/alpha/container/hub/memberships/get-credentials index 6bb8bd84a..705a9f089 100644 --- a/gcloud/alpha/container/hub/memberships/get-credentials +++ b/gcloud/alpha/container/hub/memberships/get-credentials @@ -1,6 +1,6 @@ NAME gcloud alpha container hub memberships get-credentials - fetch credentials - for a Fleet-registered cluster to be used in Connect Gateway + for a fleet-registered cluster to be used in Connect Gateway SYNOPSIS gcloud alpha container hub memberships get-credentials MEMBERSHIP @@ -9,7 +9,7 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha container hub memberships get-credentials updates the kubeconfig file with the appropriate credentials and endpoint information - to send kubectl commands to a Fleet-registered and connected cluster + to send kubectl commands to a fleet-registered and connected cluster through Connect Gateway Service. It takes a project, passed through by set defaults or flags. By default, diff --git a/gcloud/alpha/container/hub/memberships/help b/gcloud/alpha/container/hub/memberships/help index e9f941ffd..59fcb5f3d 100644 --- a/gcloud/alpha/container/hub/memberships/help +++ b/gcloud/alpha/container/hub/memberships/help @@ -1,13 +1,13 @@ NAME gcloud alpha container hub memberships - manage memberships of all your GKE - and other Kubernetes cluster with Fleet + and other Kubernetes cluster with fleets SYNOPSIS gcloud alpha container hub memberships COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Manage memberships of all your GKE and other Kubernetes cluster - with Fleet. + with fleets. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -27,14 +27,14 @@ COMMANDS (ALPHA) Generate RBAC policy files for connected clusters by the user. get-credentials - (ALPHA) Fetch credentials for a Fleet-registered cluster to be used in + (ALPHA) Fetch credentials for a fleet-registered cluster to be used in Connect Gateway. list (ALPHA) List memberships. register - (ALPHA) Register a cluster with Fleet. + (ALPHA) Register a cluster with a fleet. unregister (ALPHA) Unregister a cluster from Fleet. diff --git a/gcloud/alpha/container/hub/memberships/list b/gcloud/alpha/container/hub/memberships/list index 373fb0de1..cfb0009c7 100644 --- a/gcloud/alpha/container/hub/memberships/list +++ b/gcloud/alpha/container/hub/memberships/list @@ -7,10 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List memberships in Fleet. + (ALPHA) List memberships in a fleet. EXAMPLES - List memberships in Fleet: + List memberships in the active project's fleet: $ gcloud alpha container hub memberships list diff --git a/gcloud/alpha/container/hub/memberships/register b/gcloud/alpha/container/hub/memberships/register index 50dc2b4f9..5afa5576d 100644 --- a/gcloud/alpha/container/hub/memberships/register +++ b/gcloud/alpha/container/hub/memberships/register @@ -1,9 +1,9 @@ NAME - gcloud alpha container hub memberships register - register a cluster with - Fleet + gcloud alpha container hub memberships register - register a cluster with a + fleet SYNOPSIS - gcloud alpha container hub memberships register CLUSTER_NAME + gcloud alpha container hub memberships register MEMBERSHIP_NAME (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) (--service-account-key-file=SERVICE_ACCOUNT_KEY_FILE @@ -13,15 +13,15 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command registers a cluster with the Fleet by: + (ALPHA) This command registers a cluster with the fleet by: 1. Creating a Fleet Membership resource corresponding to the cluster. 2. Adding in-cluster Kubernetes Resources that make the cluster exclusive - to one Fleet. + to one fleet. 3. Installing the Connect Agent into this cluster. A successful registration implies that the cluster is now exclusive to a - single Fleet. + single fleet. For more information about Connect Agent, go to: https://cloud.google.com/anthos/multicluster-management/connect/overview/ @@ -40,9 +40,9 @@ DESCRIPTION If the cluster is already registered to another Fleet, the registration is not successful. - Rerunning this command against the same cluster with the same CLUSTER_NAME - and target GKEFleet is successful and upgrades the Connect Agent if a new - agent is available. + Rerunning this command against the same cluster with the same + MEMBERSHIP_NAME and target GKEFleet is successful and upgrades the Connect + Agent if a new agent is available. EXAMPLES Register a non-GKE or GKE On-Prem cluster referenced from a specific @@ -117,9 +117,9 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json POSITIONAL ARGUMENTS - CLUSTER_NAME + MEMBERSHIP_NAME The membership name that you choose to uniquely represents the cluster - being registered on the Fleet. + being registered on the fleet. REQUIRED FLAGS Cluster identifier. @@ -171,7 +171,7 @@ REQUIRED FLAGS Workload Identity --enable-workload-identity - Enable Workload Identity when registering the cluster with Fleet. + Enable Workload Identity when registering the cluster with a fleet. Ensure that GKE Workload Identity is enabled on your GKE cluster, it is a requirement for using Workload Identity with memberships. Refer to the Registering a cluster using Workload Identity section diff --git a/gcloud/alpha/container/hub/memberships/unregister b/gcloud/alpha/container/hub/memberships/unregister index 113dec2c1..5658adfb1 100644 --- a/gcloud/alpha/container/hub/memberships/unregister +++ b/gcloud/alpha/container/hub/memberships/unregister @@ -3,18 +3,18 @@ NAME from Fleet SYNOPSIS - gcloud alpha container hub memberships unregister CLUSTER_NAME + gcloud alpha container hub memberships unregister MEMBERSHIP_NAME (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command unregisters a cluster with the Fleet by: + (ALPHA) This command unregisters a cluster with the fleet by: 1. Deleting the Fleet Membership resource for this cluster (a.k.a `gcloud alpha container hub memberships delete`). 2. Removing the corresponding in-cluster Kubernetes Resources that make the - cluster exclusive to one Fleet (a.k.a `kubectl delete memberships + cluster exclusive to one fleet (a.k.a `kubectl delete memberships membership`). 3. Uninstalling the Connect Agent from this cluster (a.k.a `kubectl delete on the gke-connect namespace`). @@ -58,7 +58,7 @@ EXAMPLES --gke-cluster=my-cluster-region-or-zone/my-cluster POSITIONAL ARGUMENTS - CLUSTER_NAME + MEMBERSHIP_NAME The membership name that corresponds to the cluster being unregistered. To get list of all the memberships on the Fleet, consider using the command: gcloud alpha container hub memberships list. diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index ffb811d69..99ffef951 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -99,8 +99,9 @@ FLAGS Size for node VM boot disks in GB. Defaults to 100GB. --disk-type=DISK_TYPE - Type of the node VM boot disk. Defaults to pd-standard. DISK_TYPE must - be one of: pd-standard, pd-ssd, pd-balanced. + Type of the node VM boot disk. For version 1.24.0+, defaults to + pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE + must be one of: pd-standard, pd-ssd, pd-balanced. --enable-autoprovisioning Enables Cluster Autoscaler to treat the node pool as if it was diff --git a/gcloud/alpha/database-migration/connection-profiles/create/cloudsql b/gcloud/alpha/database-migration/connection-profiles/create/cloudsql index a126bec0c..56cd7e429 100644 --- a/gcloud/alpha/database-migration/connection-profiles/create/cloudsql +++ b/gcloud/alpha/database-migration/connection-profiles/create/cloudsql @@ -6,27 +6,36 @@ SYNOPSIS gcloud alpha database-migration connection-profiles create cloudsql (CONNECTION_PROFILE : --region=REGION) --database-version=DATABASE_VERSION --source-id=SOURCE_ID --tier=TIER - [--activation-policy=ACTIVATION_POLICY] + [--activation-policy=ACTIVATION_POLICY] [--no-async] [--authorized-networks=NETWORK,[NETWORK,...]] [--no-auto-storage-increase] [--data-disk-size=DATA_DISK_SIZE] - [--data-disk-type=DATA_DISK_TYPE] [--database-flags=[KEY=VALUE,...]] + [--data-disk-type=DATA_DISK_TYPE] [--database-flags=[FLAG=VALUE,...]] [--display-name=DISPLAY_NAME] [--no-enable-ip-v4] [--labels=[KEY=VALUE,...]] [--private-network=PRIVATE_NETWORK] - [--provider=PROVIDER] [--require-ssl] + [--provider=PROVIDER] [--require-ssl] [--root-password=ROOT_PASSWORD] [--storage-auto-resize-limit=STORAGE_AUTO_RESIZE_LIMIT] [--user-labels=[KEY=VALUE,...]] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create a Database Migration Service connection profile for Cloud - SQL. + (ALPHA) Create a Database Migration Service destination connection profile + for Cloud SQL. This will create a Cloud SQL replica. EXAMPLES To create a connection profile for Cloud SQL with database version MySQL 5.6: $ gcloud alpha database-migration connection-profiles create \ - cloudsql CONNECTION_PROFILE --region=us-central1 \ - --display-name=my-profile --database-version=MYSQL_5_6 + cloudsql my-profile --region=us-central1 \ + --database-version=MYSQL_5_6 --source-id=cp1 \ + --tier=db-n1-standard-1 + + To create a connection profile for Cloud SQL and a Cloud SQL replica with + database version PostgreSQL 10: + + $ gcloud alpha database-migration connection-profiles create \ + cloudsql my-profile --region=us-central1 \ + --database-version=POSTGRES_10 --source-id=cp1 \ + --tier=db-custom-1-3840 --zone=us-central1-a POSITIONAL ARGUMENTS Connection profile resource - The connection profile to create. The @@ -57,10 +66,9 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --database-version=DATABASE_VERSION - Database engine type and version (MYSQL_5_7, MYSQL_5_6, MYSQL_8_0, - POSTGRES_9_6, POSTGRES_10, POSTGRES_11, POSTGRES_12, POSTGRES_13). - DATABASE_VERSION must be one of: MYSQL_5_7, MYSQL_5_6, MYSQL_8_0, - POSTGRES_9_6, POSTGRES_10, POSTGRES_11, POSTGRES_12, POSTGRES_13. + Database engine type and version. DATABASE_VERSION must be one of: + MYSQL_5_7, MYSQL_5_6, MYSQL_8_0, POSTGRES_9_6, POSTGRES_10, + POSTGRES_11, POSTGRES_12, POSTGRES_13, POSTGRES_14. Connection profile resource - Database Migration Service source connection profile ID. This represents a Cloud resource. (NOTE) Some attributes are @@ -83,7 +91,7 @@ REQUIRED FLAGS --tier=TIER Tier (or machine type) for this instance, for example: db-n1-standard-1 - (MySQL instances) of db-custom-1-3840 (PostgreSQL instances). For more + (MySQL instances) or db-custom-1-3840 (PostgreSQL instances). For more information, see Cloud SQL Instance Settings (https://cloud.google.com/sql/docs/mysql/instance-settings). @@ -100,18 +108,20 @@ OPTIONAL FLAGS ACTIVATION_POLICY must be one of: ALWAYS, NEVER. + --no-async + Waits for the operation in progress to complete before returning. + --authorized-networks=NETWORK,[NETWORK,...] - List of external networks that are allowed to connect to the instance - using the IP. See - https://en.wikipedia.org/wiki/CIDR_notation#CIDR_notation, also known - as 'slash' notation (e.g.192.168.100.0/24). + List of external networks that are allowed to connect to the instance. + Specify values in CIDR notation, also known as 'slash' notation + (e.g.192.168.100.0/24). --auto-storage-increase If you enable this setting, Cloud SQL checks your available storage every 30 seconds. If the available storage falls below a threshold size, Cloud SQL automatically adds additional storage capacity. If the available storage repeatedly falls below the threshold size, Cloud SQL - continues to add storage until it reaches the maximum of 30 TB. + continues to add storage until it reaches the maximum of 64 TB. Default: ON. Enabled by default, use --no-auto-storage-increase to disable. @@ -120,16 +130,20 @@ OPTIONAL FLAGS default) size is 10GB. --data-disk-type=DATA_DISK_TYPE - Type of storage: PD_SSD (default) or PD_HDD. DATA_DISK_TYPE must be one - of: PD_SSD, PD_HDD. + Type of storage. DATA_DISK_TYPE must be one of: PD_SSD, PD_HDD. - --database-flags=[KEY=VALUE,...] - Database flags passed to the Cloud SQL instance at startup. An object - containing a list of "key": value pairs. Example: { "name": "wrench", - "mass": "1.3kg", "count": "3" }. + --database-flags=[FLAG=VALUE,...] + Comma-separated list of database flags to set on the instance. Use an + equals sign to separate the flag name and value. Flags without values, + like skip_grant_tables, can be written out without a value, e.g., + skip_grant_tables=. Use on/off values for booleans. View the Instance + Resource API for allowed flags. (e.g., --database-flags + max_allowed_packet=55555 skip_grant_tables=,log_output=1). --display-name=DISPLAY_NAME - Friendly name for the connection profile. + A user-friendly name for the connection profile. The display name can + include letters, numbers, spaces, and hyphens, and must start with a + letter. --enable-ip-v4 Whether the instance should be assigned an IPv4 address or not. Enabled @@ -150,12 +164,15 @@ OPTIONAL FLAGS updated, but it cannot be removed after it is set. --provider=PROVIDER - Database provider (CLOUDSQL or RDS). PROVIDER must be one of: RDS, + Database provider, for managed databases. PROVIDER must be one of: RDS, CLOUDSQL. --require-ssl Whether SSL connections over IP should be enforced or not. + --root-password=ROOT_PASSWORD + Root Cloud SQL user's password. + --storage-auto-resize-limit=STORAGE_AUTO_RESIZE_LIMIT Maximum size to which storage capacity can be automatically increased. The default value is 0, which specifies that there is no limit. diff --git a/gcloud/alpha/database-migration/connection-profiles/create/help b/gcloud/alpha/database-migration/connection-profiles/create/help index 6403da506..d39979f5f 100644 --- a/gcloud/alpha/database-migration/connection-profiles/create/help +++ b/gcloud/alpha/database-migration/connection-profiles/create/help @@ -9,6 +9,11 @@ SYNOPSIS DESCRIPTION (ALPHA) Commands for creating Database Migration Service connection profiles. + ▪ Create a source connection profile with the mysql or postgresql + commands. + ▪ Create a destination connection profile for a Cloud SQL instance with + the cloudsql command. For Cloud SQL instance as a source, use the + create command for the relevant engine type (e.g. mysql). GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/database-migration/connection-profiles/create/mysql b/gcloud/alpha/database-migration/connection-profiles/create/mysql index e98942f0e..c84209cb1 100644 --- a/gcloud/alpha/database-migration/connection-profiles/create/mysql +++ b/gcloud/alpha/database-migration/connection-profiles/create/mysql @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha database-migration connection-profiles create mysql (CONNECTION_PROFILE : --region=REGION) --host=HOST --port=PORT --username=USERNAME (--password=PASSWORD | --prompt-for-password) - [--display-name=DISPLAY_NAME] [--instance=INSTANCE] + [--no-async] [--display-name=DISPLAY_NAME] [--instance=INSTANCE] [--labels=[KEY=VALUE,...]] [--provider=PROVIDER] [--ca-certificate=CA_CERTIFICATE : --certificate=CERTIFICATE --private-key=PRIVATE_KEY] @@ -19,16 +19,15 @@ EXAMPLES To create a connection profile for MySQL: $ gcloud alpha database-migration connection-profiles create mysql \ - CONNECTION_PROFILE --region=us-central1 --password=123456 \ - --username=fakeuser --display-name=my-profile --host=1.2.3.4 \ - --port=1111 + my-profile --region=us-central1 --password=123456 \ + --username=my-user --host=1.2.3.4 --port=3306 If the source is a Cloud SQL database, run: $ gcloud alpha database-migration connection-profiles create mysql \ - CONNECTION_PROFILE --region=us-central1 --password=123456 \ - --username=fakeuser --display-name=my-profile --host=1.2.3.4 \ - --port=1111 --instance=my-instance + my-profile --region=us-central1 --password=123456 \ + --username=my-user --host=1.2.3.4 --port=3306 \ + --instance=my-instance --provider=CLOUDSQL POSITIONAL ARGUMENTS Connection profile resource - The connection profile to create. The @@ -65,23 +64,28 @@ REQUIRED FLAGS Network port of the source database. --username=USERNAME - Username that Database Migration Service will use to connect to the - database. The value is encrypted when stored in Database Migration - Service. + Username that Database Migration Service uses to connect to the + database. Database Migration Service encrypts the value when storing + it. Exactly one of these must be specified: --password=PASSWORD - Password for the user that Database Migration Service will be using - to connect to the database. This field is not returned on request, - and the value is encrypted when stored in Database Migration Service. + Password for the user that Database Migration Service uses to connect + to the source database. Database Migration Service encrypts the value + when storing it, and the field is not returned on request. --prompt-for-password Prompt for the password used to connect to the database. OPTIONAL FLAGS + --no-async + Waits for the operation in progress to complete before returning. + --display-name=DISPLAY_NAME - Friendly name for the connection profile. + A user-friendly name for the connection profile. The display name can + include letters, numbers, spaces, and hyphens, and must start with a + letter. --instance=INSTANCE If the source is a Cloud SQL database, use this field to provide the @@ -96,13 +100,14 @@ OPTIONAL FLAGS numbers. --provider=PROVIDER - Database provider (CLOUDSQL or RDS). PROVIDER must be one of: RDS, + Database provider, for managed databases. PROVIDER must be one of: RDS, CLOUDSQL. --ca-certificate=CA_CERTIFICATE x509 PEM-encoded certificate of the CA that signed the source database server's certificate. The replica will use this certificate to verify - it's connecting to the right host. + it's connecting to the correct host. Database Migration Service + encrypts the value when storing it. --certificate=CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to @@ -110,7 +115,8 @@ OPTIONAL FLAGS --private-key=PRIVATE_KEY Unencrypted PKCS#1 or PKCS#8 PEM-encoded private key associated with - the Client Certificate. + the Client Certificate. Database Migration Service encrypts the value + when storing it. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/database-migration/connection-profiles/update b/gcloud/alpha/database-migration/connection-profiles/update index ad7aa75d3..06e7610f3 100644 --- a/gcloud/alpha/database-migration/connection-profiles/update +++ b/gcloud/alpha/database-migration/connection-profiles/update @@ -14,12 +14,19 @@ SYNOPSIS DESCRIPTION (ALPHA) Update a Database Migration Service connection profile. + ▪ Draft connection profile: the user can update all flags available in + connection-profiles create command. + ▪ Existing connection profile: the user can update a limited list of + flags, see connection-profiles update Synopsis. + ▪ If a migration job is using the connection profile, then updates to + fields host, port, username, and password will propagate to the + destination instance. EXAMPLES - To update the display name of a connection profile: + To update the username of a connection profile: $ gcloud alpha database-migration connection-profiles update \ - CONNECTION_PROFILE --region=us-central1 --display-name=new-name + my-profile --region=us-central1 --username=new-user POSITIONAL ARGUMENTS Connection profile resource - The connection profile to update. The @@ -52,14 +59,17 @@ FLAGS --ca-certificate=CA_CERTIFICATE x509 PEM-encoded certificate of the CA that signed the source database server's certificate. The replica will use this certificate to verify - it's connecting to the right host. + it's connecting to the correct host. Database Migration Service + encrypts the value when storing it. --certificate=CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to authenticate against the source database server. --display-name=DISPLAY_NAME - Friendly name for the connection profile. + A user-friendly name for the connection profile. The display name can + include letters, numbers, spaces, and hyphens, and must start with a + letter. --host=HOST IP or hostname of the source database. @@ -73,7 +83,8 @@ FLAGS --private-key=PRIVATE_KEY Unencrypted PKCS#1 or PKCS#8 PEM-encoded private key associated with - the Client Certificate. + the Client Certificate. Database Migration Service encrypts the value + when storing it. --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value @@ -85,9 +96,9 @@ FLAGS numbers. --username=USERNAME - Username that Database Migration Service will use to connect to the - database. The value is encrypted when stored in Database Migration - Service. + Username that Database Migration Service uses to connect to the + database. Database Migration Service encrypts the value when storing + it. At most one of these can be specified: @@ -113,9 +124,9 @@ FLAGS At most one of these can be specified: --password=PASSWORD - Password for the user that Database Migration Service will be using - to connect to the database. This field is not returned on request, - and the value is encrypted when stored in Database Migration Service. + Password for the user that Database Migration Service uses to connect + to the source database. Database Migration Service encrypts the value + when storing it, and the field is not returned on request. --prompt-for-password Prompt for the password used to connect to the database. diff --git a/gcloud/alpha/database-migration/migration-jobs/create b/gcloud/alpha/database-migration/migration-jobs/create index a59f9e2cf..a910c3494 100644 --- a/gcloud/alpha/database-migration/migration-jobs/create +++ b/gcloud/alpha/database-migration/migration-jobs/create @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud alpha database-migration migration-jobs create (MIGRATION_JOB : --region=REGION) --destination=DESTINATION - --source=SOURCE --type=TYPE [--display-name=DISPLAY_NAME] - [--dump-path=DUMP_PATH] [--labels=[KEY=VALUE,...]] [--sync] + --source=SOURCE --type=TYPE [--no-async] [--display-name=DISPLAY_NAME] + [--dump-path=DUMP_PATH] [--labels=[KEY=VALUE,...]] [--peer-vpc=PEER_VPC | --static-ip | [--vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC : --vm=VM]] [GCLOUD_WIDE_FLAG ...] @@ -91,6 +91,9 @@ REQUIRED FLAGS of: ONE_TIME, CONTINUOUS. OPTIONAL FLAGS + --no-async + Waits for the operation in progress to complete before returning. + --display-name=DISPLAY_NAME Friendly name for the migration job. @@ -106,9 +109,6 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - --sync - Waits for the operation in progress to complete before returning. - The connectivity method used by the migration job. If a connectivity method isn't specified, then it isn't added to the migration job. diff --git a/gcloud/alpha/database-migration/migration-jobs/update b/gcloud/alpha/database-migration/migration-jobs/update index 8d66d5cbc..b087a6508 100644 --- a/gcloud/alpha/database-migration/migration-jobs/update +++ b/gcloud/alpha/database-migration/migration-jobs/update @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud alpha database-migration migration-jobs update (MIGRATION_JOB : --region=REGION) --destination=DESTINATION - --source=SOURCE [--display-name=DISPLAY_NAME] [--dump-path=DUMP_PATH] - [--type=TYPE] [--update-labels=[KEY=VALUE,...]] + --source=SOURCE [--no-async] [--display-name=DISPLAY_NAME] + [--dump-path=DUMP_PATH] [--type=TYPE] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [--peer-vpc=PEER_VPC | --static-ip | --vm=VM --vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC] @@ -84,6 +84,9 @@ FLAGS connection_profile. To set the connection_profile attribute: ▸ provide the argument --source on the command line. + --no-async + Waits for the operation in progress to complete before returning. + --display-name=DISPLAY_NAME Friendly name for the migration job. diff --git a/gcloud/alpha/dns/managed-zones/get-iam-policy b/gcloud/alpha/dns/managed-zones/get-iam-policy index e0062d071..08bbf76b6 100644 --- a/gcloud/alpha/dns/managed-zones/get-iam-policy +++ b/gcloud/alpha/dns/managed-zones/get-iam-policy @@ -6,16 +6,16 @@ SYNOPSIS gcloud alpha dns managed-zones get-iam-policy ZONE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command displays the IAM Policy of the specified managed-zone. + (ALPHA) This command displays the IAM policy of the specified managed-zone. EXAMPLES - To display the details of your managed-zone IAM Policy , run: + To view the details of your managed-zone IAM policy , run: $ gcloud alpha dns managed-zones get-iam-policy my-zone POSITIONAL ARGUMENTS - Zone resource - The name of the managed-zone to get IAM policy. This - represents a Cloud resource. (NOTE) Some attributes are not given + Zone resource - The name of the managed-zone to get the IAM policy for. + 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 zone on the command line with a fully specified @@ -42,5 +42,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta dns managed-zones get-iam-policy diff --git a/gcloud/alpha/dns/managed-zones/set-iam-policy b/gcloud/alpha/dns/managed-zones/set-iam-policy index 64a1ff05f..26bd9ca6d 100644 --- a/gcloud/alpha/dns/managed-zones/set-iam-policy +++ b/gcloud/alpha/dns/managed-zones/set-iam-policy @@ -7,7 +7,7 @@ SYNOPSIS --policy-file=POLICY_FILE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command sets the IAM Policy of the specified managed-zone. + (ALPHA) This command sets the IAM policy of the specified managed-zone. EXAMPLES To set the IAM policy of your managed-zone , run: @@ -16,8 +16,8 @@ EXAMPLES --policy-file=policy.json POSITIONAL ARGUMENTS - Zone resource - The name of the managed-zone to set IAM policy. This - represents a Cloud resource. (NOTE) Some attributes are not given + Zone resource - The name of the managed-zone to set the IAM policy for. + 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 zone on the command line with a fully specified @@ -48,5 +48,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta dns managed-zones set-iam-policy diff --git a/gcloud/alpha/iap/tcp/dest-groups/add-iam-policy-binding b/gcloud/alpha/iap/tcp/dest-groups/add-iam-policy-binding index ced4e679e..498477009 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/add-iam-policy-binding +++ b/gcloud/alpha/iap/tcp/dest-groups/add-iam-policy-binding @@ -124,5 +124,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta iap tcp dest-groups add-iam-policy-binding diff --git a/gcloud/alpha/iap/tcp/dest-groups/create b/gcloud/alpha/iap/tcp/dest-groups/create index 09e4397ec..9c6cdacb9 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/create +++ b/gcloud/alpha/iap/tcp/dest-groups/create @@ -64,5 +64,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta iap tcp dest-groups create diff --git a/gcloud/alpha/iap/tcp/dest-groups/delete b/gcloud/alpha/iap/tcp/dest-groups/delete index 3147bfd50..e4e7c6cc0 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/delete +++ b/gcloud/alpha/iap/tcp/dest-groups/delete @@ -42,5 +42,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta iap tcp dest-groups delete diff --git a/gcloud/alpha/iap/tcp/dest-groups/describe b/gcloud/alpha/iap/tcp/dest-groups/describe index ee9dde340..da88281c7 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/describe +++ b/gcloud/alpha/iap/tcp/dest-groups/describe @@ -42,5 +42,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta iap tcp dest-groups describe diff --git a/gcloud/alpha/iap/tcp/dest-groups/get-iam-policy b/gcloud/alpha/iap/tcp/dest-groups/get-iam-policy index 938e46f4b..368ab07f3 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/get-iam-policy +++ b/gcloud/alpha/iap/tcp/dest-groups/get-iam-policy @@ -75,5 +75,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta iap tcp dest-groups get-iam-policy diff --git a/gcloud/alpha/iap/tcp/dest-groups/help b/gcloud/alpha/iap/tcp/dest-groups/help index 58dbb1c54..1b987d5b1 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/help +++ b/gcloud/alpha/iap/tcp/dest-groups/help @@ -49,5 +49,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta iap tcp dest-groups diff --git a/gcloud/alpha/iap/tcp/dest-groups/list b/gcloud/alpha/iap/tcp/dest-groups/list index d25f42ed1..718f66735 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/list +++ b/gcloud/alpha/iap/tcp/dest-groups/list @@ -86,5 +86,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta iap tcp dest-groups list diff --git a/gcloud/alpha/iap/tcp/dest-groups/remove-iam-policy-binding b/gcloud/alpha/iap/tcp/dest-groups/remove-iam-policy-binding index 14e1de853..175784d68 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/remove-iam-policy-binding +++ b/gcloud/alpha/iap/tcp/dest-groups/remove-iam-policy-binding @@ -140,5 +140,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta iap tcp dest-groups remove-iam-policy-binding diff --git a/gcloud/alpha/iap/tcp/dest-groups/set-iam-policy b/gcloud/alpha/iap/tcp/dest-groups/set-iam-policy index c2d9f6fc9..93616412b 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/set-iam-policy +++ b/gcloud/alpha/iap/tcp/dest-groups/set-iam-policy @@ -53,5 +53,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta iap tcp dest-groups set-iam-policy diff --git a/gcloud/alpha/iap/tcp/dest-groups/update b/gcloud/alpha/iap/tcp/dest-groups/update index 16c78ca14..931b23c70 100644 --- a/gcloud/alpha/iap/tcp/dest-groups/update +++ b/gcloud/alpha/iap/tcp/dest-groups/update @@ -70,5 +70,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta iap tcp dest-groups update diff --git a/gcloud/alpha/iap/tcp/help b/gcloud/alpha/iap/tcp/help index 86269b9f4..1926bb664 100644 --- a/gcloud/alpha/iap/tcp/help +++ b/gcloud/alpha/iap/tcp/help @@ -22,5 +22,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta iap tcp diff --git a/gcloud/alpha/immersive-stream/xr/operations/help b/gcloud/alpha/immersive-stream/xr/operations/help index 210396572..28431ad16 100644 --- a/gcloud/alpha/immersive-stream/xr/operations/help +++ b/gcloud/alpha/immersive-stream/xr/operations/help @@ -20,6 +20,9 @@ COMMANDS (ALPHA) Get description of a long-running Immersive Stream for XR operation. + list + (ALPHA) List Immersive Stream for XR operations. + wait (ALPHA) Poll long-running Immersive Stream for XR operation until it completes. diff --git a/gcloud/alpha/immersive-stream/xr/operations/list b/gcloud/alpha/immersive-stream/xr/operations/list new file mode 100644 index 000000000..03534430a --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/operations/list @@ -0,0 +1,84 @@ +NAME + gcloud alpha immersive-stream xr operations list - list Immersive Stream + for XR operations + +SYNOPSIS + gcloud alpha immersive-stream xr operations list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Immersive Stream for XR operations. + +EXAMPLES + To list Immersive Stream for XR operations, run: + + $ gcloud alpha immersive-stream xr operations list + +FLAGS + Location resource - Location to list all Immersive Stream for XR + operations, defaults to global. This represents a Cloud resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ global is the only supported location with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +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 stream/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/run/jobs/help b/gcloud/alpha/run/jobs/help index 2879a7972..efb9b1fc5 100644 --- a/gcloud/alpha/run/jobs/help +++ b/gcloud/alpha/run/jobs/help @@ -57,6 +57,9 @@ COMMANDS remove-iam-policy-binding (ALPHA) Remove IAM policy binding of a Cloud Run job. + replace + (ALPHA) Creates or replaces a job from a YAML Job specification. + set-iam-policy (ALPHA) Set the IAM policy for a job. diff --git a/gcloud/alpha/run/jobs/replace b/gcloud/alpha/run/jobs/replace new file mode 100644 index 000000000..332ab178f --- /dev/null +++ b/gcloud/alpha/run/jobs/replace @@ -0,0 +1,44 @@ +NAME + gcloud alpha run jobs replace - creates or replaces a job from a YAML Job + specification + +SYNOPSIS + gcloud alpha run jobs replace FILE [--async] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Creates or replaces a job from a YAML Job specification. + +EXAMPLES + To replace the specification for myjob + + $ gcloud alpha run jobs replace myjob.yaml + +POSITIONAL ARGUMENTS + FILE + The absolute path to the YAML file with a Cloud Run job definition for + the job to update or create. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +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/sql/generate-login-token b/gcloud/alpha/sql/generate-login-token new file mode 100644 index 000000000..33e5c9657 --- /dev/null +++ b/gcloud/alpha/sql/generate-login-token @@ -0,0 +1,58 @@ +NAME + gcloud alpha sql generate-login-token - generate an IAM login token for + Cloud SQL + +SYNOPSIS + gcloud alpha sql generate-login-token [--application-default-credential] + [--instance=INSTANCE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha sql generate-login-token generates an IAM token to use + for logging in to Cloud SQL instances. + +EXAMPLES + To generate an IAM login token using gcloud credentials, run: + + $ gcloud alpha sql generate-login-token + + To generate an IAM login token using application default credentials, run: + + $ gcloud alpha sql generate-login-token \ + --application-default-credential + + To generate an IAM login token using gcloud credentials for instance + my-instance, run: + + $ gcloud alpha sql generate-login-token --instance=my-instance + + To generate an IAM login token using application default credentials for + instance my-instance, run: + + $ gcloud alpha sql generate-login-token --instance=my-instance \ + --application-default-credential + +FLAGS + --application-default-credential + Use application default credentials to generate the login token. + + --instance=INSTANCE + Cloud SQL instance ID. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud sql generate-login-token + + $ gcloud beta sql generate-login-token + diff --git a/gcloud/alpha/sql/help b/gcloud/alpha/sql/help index dbf6ee2ff..86e18dae7 100644 --- a/gcloud/alpha/sql/help +++ b/gcloud/alpha/sql/help @@ -66,6 +66,9 @@ COMMANDS connect (ALPHA) Connects to a Cloud SQL instance. + generate-login-token + (ALPHA) Generate an IAM login token for Cloud SQL. + reschedule-maintenance (ALPHA) Reschedule a Cloud SQL instance's maintenance. diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index 6b98a1b9d..60efaf155 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -183,7 +183,8 @@ FLAGS --enable-password-policy Enable the password policy, which enforces user password management - with the policies configured for the instance. + with the policies configured for the instance. This flag is only + available for Postgres. --enable-point-in-time-recovery Allows for data recovery from a specific point in time, down to a @@ -271,8 +272,8 @@ FLAGS --network=projects/testproject/global/networks/testsharednetwork --password-policy-complexity=PASSWORD_POLICY_COMPLEXITY - The complexity of the password. PASSWORD_POLICY_COMPLEXITY must be one - of: + The complexity of the password. This flag is available only for + PostgreSQL. PASSWORD_POLICY_COMPLEXITY must be one of: COMPLEXITY_DEFAULT A combination of lowercase, uppercase, numeric, and @@ -282,21 +283,24 @@ FLAGS implies that complexity check is not enabled. --[no-]password-policy-disallow-username-substring - Disallow username as a part of the password. Use - --password-policy-disallow-username-substring to enable and - --no-password-policy-disallow-username-substring to disable. + Disallow username as a part of the password. This flag is available + only for PostgreSQL. Use --password-policy-disallow-username-substring + to enable and --no-password-policy-disallow-username-substring to + disable. --password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH - Minimum number of characters allowed in the password. + Minimum number of characters allowed in the password. This flag is + available only for PostgreSQL. --password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL Minimum interval after which the password can be changed, for example, 2m for 2 minutes. See - $ gcloud topic datetimes for information on duration formats. + $ gcloud topic datetimes for information on duration formats. This + flag is available only for PostgreSQL. --password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL Number of previous passwords that cannot be reused. The valid range is - between 0 and 100. + 0 to 100. This flag is available only for PostgreSQL. --replica-type=REPLICA_TYPE The type of replica to create. REPLICA_TYPE must be one of: READ, diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index 6dce7cba7..13a21d666 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -97,7 +97,8 @@ FLAGS Provides no failover capability. This is the default. --clear-password-policy - Clear the existing password policy. + Clear the existing password policy. This flag is only available for + Postgres. --cpu=CPU Whole number value indicating how many cores are desired in the @@ -135,7 +136,8 @@ FLAGS --enable-password-policy Enable the password policy, which enforces user password management - with the policies configured for the instance. + with the policies configured for the instance. This flag is only + available for Postgres. --enable-point-in-time-recovery Allows for data recovery from a specific point in time, down to a @@ -218,8 +220,8 @@ FLAGS --network=projects/testproject/global/networks/testsharednetwork --password-policy-complexity=PASSWORD_POLICY_COMPLEXITY - The complexity of the password. PASSWORD_POLICY_COMPLEXITY must be one - of: + The complexity of the password. This flag is available only for + PostgreSQL. PASSWORD_POLICY_COMPLEXITY must be one of: COMPLEXITY_DEFAULT A combination of lowercase, uppercase, numeric, and @@ -229,21 +231,24 @@ FLAGS implies that complexity check is not enabled. --[no-]password-policy-disallow-username-substring - Disallow username as a part of the password. Use - --password-policy-disallow-username-substring to enable and - --no-password-policy-disallow-username-substring to disable. + Disallow username as a part of the password. This flag is available + only for PostgreSQL. Use --password-policy-disallow-username-substring + to enable and --no-password-policy-disallow-username-substring to + disable. --password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH - Minimum number of characters allowed in the password. + Minimum number of characters allowed in the password. This flag is + available only for PostgreSQL. --password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL Minimum interval after which the password can be changed, for example, 2m for 2 minutes. See - $ gcloud topic datetimes for information on duration formats. + $ gcloud topic datetimes for information on duration formats. This + flag is available only for PostgreSQL. --password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL Number of previous passwords that cannot be reused. The valid range is - between 0 and 100. + 0 to 100. This flag is available only for PostgreSQL. --pricing-plan=PRICING_PLAN, -p PRICING_PLAN First Generation instances only. The pricing plan for this instance. diff --git a/gcloud/alpha/sql/users/create b/gcloud/alpha/sql/users/create index dde7b49e8..58a15264f 100644 --- a/gcloud/alpha/sql/users/create +++ b/gcloud/alpha/sql/users/create @@ -40,16 +40,18 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. + This flag is currently not available. --[no-]password-policy-enable-failed-attempts-check - Enables the failed login attempts check if set to true. Use + Enables the failed login attempts check if set to true. This flag is + currently not available. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION Expiration duration after a password is updated, for example, 2m for 2 minutes. See gcloud topic datetimes for information on duration - formats. + formats. This flag is currently not available. --type=TYPE Cloud SQL user's type. It determines the method to authenticate the diff --git a/gcloud/alpha/sql/users/set-password-policy b/gcloud/alpha/sql/users/set-password-policy index c55e7a4d3..f42506aa4 100644 --- a/gcloud/alpha/sql/users/set-password-policy +++ b/gcloud/alpha/sql/users/set-password-policy @@ -42,7 +42,8 @@ OPTIONAL FLAGS complete. --clear-password-policy - Clear the existing password policy. + Clear the existing password policy. This flag is only available for + Postgres. --host=HOST Cloud SQL user's host name expressed as a specific IP address or @@ -55,16 +56,18 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. + This flag is currently not available. --[no-]password-policy-enable-failed-attempts-check - Enables the failed login attempts check if set to true. Use + Enables the failed login attempts check if set to true. This flag is + currently not available. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION Expiration duration after a password is updated, for example, 2m for 2 minutes. See gcloud topic datetimes for information on duration - formats. + formats. This flag is currently not available. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/storage/cp b/gcloud/alpha/storage/cp index 06b85e400..5c70f16b3 100644 --- a/gcloud/alpha/storage/cp +++ b/gcloud/alpha/storage/cp @@ -2,8 +2,8 @@ NAME gcloud alpha storage cp - upload, download, and copy Cloud Storage objects SYNOPSIS - gcloud alpha storage cp SOURCE [SOURCE ...] DESTINATION - [--all-versions, -A] [--cache-control=CACHE_CONTROL] [--no-clobber, -n] + gcloud alpha storage cp [SOURCE ...] DESTINATION [--all-versions, -A] + [--cache-control=CACHE_CONTROL] [--no-clobber, -n] [--content-disposition=CONTENT_DISPOSITION] [--content-encoding=CONTENT_ENCODING] [--content-language=CONTENT_LANGUAGE] [--content-md5=MD5_DIGEST] @@ -13,7 +13,8 @@ SYNOPSIS [--if-metageneration-match=METAGENERATION] [--ignore-symlinks] [--manifest-path=MANIFEST_PATH, -L MANIFEST_PATH] [--preserve-posix, -P] [--print-created-message, -v] - [--recursive, -R, -r] [--skip-unsupported, -U] + [--read-paths-from-stdin, -I] [--recursive, -R, -r] + [--skip-unsupported, -U] [--storage-class=STORAGE_CLASS, -s STORAGE_CLASS] [--canned-acl=PREDEFINED_ACL, --predefined-acl=PREDEFINED_ACL, -a PREDEFINED_ACL @@ -49,7 +50,7 @@ EXAMPLES $ gcloud alpha storage cp --recursive dir gs://my-bucket POSITIONAL ARGUMENTS - SOURCE [SOURCE ...] + [SOURCE ...] The source path(s) to copy. DESTINATION @@ -156,6 +157,13 @@ FLAGS --print-created-message, -v Prints the version-specific URL for each copied object. + --read-paths-from-stdin, -I + Read the list of resources to copy from stdin. No need to enter a + source argument if this flag is present. Example: "storage cp -I + gs://bucket/destination" Note: To copy the contents of one file + directly from stdin, use "-" as the source argument without the "-I" + flag. + --recursive, -R, -r Recursively copy the contents of any directories that match the source path expression. diff --git a/gcloud/alpha/storage/rm b/gcloud/alpha/storage/rm index 24a0cb0b9..0549714b1 100644 --- a/gcloud/alpha/storage/rm +++ b/gcloud/alpha/storage/rm @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha storage rm [URLS ...] [--all-versions, -a] [--continue-on-error, -c] [--if-generation-match=GENERATION] - [--if-metageneration-match=METAGENERATION] [--recursive, -R, -r] - [--stdin, -I] [GCLOUD_WIDE_FLAG ...] + [--if-metageneration-match=METAGENERATION] + [--read-paths-from-stdin, -I] [--recursive, -R, -r] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Delete objects and buckets. @@ -69,6 +70,9 @@ FLAGS Execute only if the metageneration matches the metageneration of the requested object. + --read-paths-from-stdin, -I + Read the list of resources to remove from stdin. + --recursive, -R, -r Recursively delete the contents of buckets or directories that match the path expression. If the path is set to a bucket, like gs://bucket, @@ -76,9 +80,6 @@ FLAGS option. If you want to delete only live object versions, use the ``**'' wildcard instead. - --stdin, -I - Read the list of resources to remove from stdin. - 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/web-security-scanner/scan-configs/create b/gcloud/alpha/web-security-scanner/scan-configs/create index cf2b1dd91..56a911f97 100644 --- a/gcloud/alpha/web-security-scanner/scan-configs/create +++ b/gcloud/alpha/web-security-scanner/scan-configs/create @@ -54,7 +54,7 @@ OPTIONAL FLAGS --target-platforms=[TARGET_PLATFORMS,...]; default="app_engine,compute" List of platforms the site is running on. Defaults to 'app_engine,compute'. TARGET_PLATFORMS must be one of: app-engine, - cloud-run, compute, target-platform-unspecified. + cloud-functions, cloud-run, compute, target-platform-unspecified. --user-agent=USER_AGENT List of user agents to use when crawling. Defaults to 'chrome_linux'. diff --git a/gcloud/alpha/web-security-scanner/scan-configs/update b/gcloud/alpha/web-security-scanner/scan-configs/update index 523f68130..61ce5794a 100644 --- a/gcloud/alpha/web-security-scanner/scan-configs/update +++ b/gcloud/alpha/web-security-scanner/scan-configs/update @@ -87,7 +87,7 @@ FLAGS --target-platforms=[TARGET_PLATFORMS,...]; default="app_engine,compute" List of platforms the site is running on. Defaults to 'app_engine,compute'. TARGET_PLATFORMS must be one of: app-engine, - cloud-run, compute, target-platform-unspecified. + cloud-functions, cloud-run, compute, target-platform-unspecified. --user-agent=USER_AGENT List of user agents to use when crawling. Defaults to 'chrome_linux'. diff --git a/gcloud/anthos/config/controller/create b/gcloud/anthos/config/controller/create index 87ec9ec95..d952c1f4b 100644 --- a/gcloud/anthos/config/controller/create +++ b/gcloud/anthos/config/controller/create @@ -44,9 +44,9 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Config Controller instance location. Currently, only us-central1, us-east1, northamerica-northeast1, - northamerica-northeast2, europe-north1, australia-southeast1, - asia-northeast1, and asia-northeast2 are supported. To set the - location attribute: + northamerica-northeast2, europe-north1, europe-west1, europe-west3, + australia-southeast1, australia-southeast2, asia-northeast1, and + asia-northeast2 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/anthos/config/controller/delete b/gcloud/anthos/config/controller/delete index 9d9d6bd47..7252de7f3 100644 --- a/gcloud/anthos/config/controller/delete +++ b/gcloud/anthos/config/controller/delete @@ -38,9 +38,9 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. Currently, only us-central1, us-east1, northamerica-northeast1, - northamerica-northeast2, europe-north1, australia-southeast1, - asia-northeast1 and asia-northeast2 are supported. To set the - location attribute: + northamerica-northeast2, europe-north1, europe-west1, europe-west3, + australia-southeast1, australia-southeast2, asia-northeast1 and + asia-northeast2 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/anthos/config/controller/describe b/gcloud/anthos/config/controller/describe index dda0d7b50..038754dfd 100644 --- a/gcloud/anthos/config/controller/describe +++ b/gcloud/anthos/config/controller/describe @@ -40,9 +40,9 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. Currently, only us-central1, us-east1, northamerica-northeast1, - northamerica-northeast2, europe-north1, australia-southeast1, - asia-northeast1 and asia-northeast2 are supported. To set the - location attribute: + northamerica-northeast2, europe-north1, europe-west1, europe-west3, + australia-southeast1, australia-southeast2, asia-northeast1 and + asia-northeast2 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/anthos/config/operations/describe b/gcloud/anthos/config/operations/describe index 65e1003c9..c49e8370a 100644 --- a/gcloud/anthos/config/operations/describe +++ b/gcloud/anthos/config/operations/describe @@ -40,9 +40,9 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. Currently, only us-central1, us-east1, northamerica-northeast1, - northamerica-northeast2, europe-north1, australia-southeast1, - asia-northeast1 and asia-northeast2 are supported. To set the - location attribute: + northamerica-northeast2, europe-north1, europe-west1, europe-west3, + australia-southeast1, australia-southeast2, asia-northeast1 and + asia-northeast2 are supported. To set the location attribute: ▸ provide the argument operation on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/artifacts/files/help b/gcloud/artifacts/files/help new file mode 100644 index 000000000..6dbaada4d --- /dev/null +++ b/gcloud/artifacts/files/help @@ -0,0 +1,35 @@ +NAME + gcloud artifacts files - manage Artifact Registry files + +SYNOPSIS + gcloud artifacts files COMMAND [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list all files in the current project and artifacts/repository and + artifacts/location properties are set, run: + + $ gcloud artifacts files list + + To list files under repository my-repo in the current project and location, + run: + + $ gcloud artifacts files list --repository=my-repo + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + List Artifact Registry files. + +NOTES + These variants are also available: + + $ gcloud alpha artifacts files + + $ gcloud beta artifacts files + diff --git a/gcloud/artifacts/files/list b/gcloud/artifacts/files/list new file mode 100644 index 000000000..d97e8044c --- /dev/null +++ b/gcloud/artifacts/files/list @@ -0,0 +1,124 @@ +NAME + gcloud artifacts files list - list Artifact Registry files + +SYNOPSIS + gcloud artifacts files list [--package=PACKAGE] [--tag=TAG] + [--version=VERSION] [--repository=REPOSITORY : --location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all Artifact Registry files in the specified repository and location. + + To specify the maximum number of files to list, use the --limit flag. + +EXAMPLES + To list files in the current project under repository my-repo in + us-central1: + + $ gcloud artifacts files list --repository=my-repo \ + --location=us-central1 + + The following command lists a maximum of five files: + + $ gcloud artifacts files list --repository=my-repo \ + --location=us-central1 --limit=5 + + To list files in the current project under repository my-repo in + us-central1 owned by package my-package: + + $ gcloud artifacts files list --repository=my-repo \ + --location=us-central1 --package=my-package + + To list files in the current project under repository my-repo in + us-central1 owned by package my-package and version 1.0.0: + + $ gcloud artifacts files list --repository=my-repo \ + --location=us-central1 --package=my-package --version=1.0.0 + + To list files in the current project under repository my-repo in + us-central1 owned by package my-package and tag name my-tag: + + $ gcloud artifacts files list --repository=my-repo \ + --location=us-central1 --package=my-package --tag=my-tag + +FLAGS + --package=PACKAGE + List all files in a specified artifact, such as a container image or a + language package. If you do not use --tag or --version in the command, + the command lists files in all versions of the artifact. + + --tag=TAG + List all files in the artifact version with the specified tag. This + flag only works with formats that use tags, such as container images. + Use the --package flag to specify the artifact. + + --version=VERSION + List all files in the specified artifact version. Use the --package + flag to specify the artifact. + + Repository resource - The Artifact Registry repository. If not specified, + the current artifacts/repository is used. The arguments in this group can + be used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. To set + the project attribute: + ◆ provide the argument --repository on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --location=LOCATION + Location of the repository. To set the location attribute: + ▸ provide the argument --repository on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +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 artifacts files list + + $ gcloud beta artifacts files list + diff --git a/gcloud/artifacts/help b/gcloud/artifacts/help index cda4e6812..d7c4443dd 100644 --- a/gcloud/artifacts/help +++ b/gcloud/artifacts/help @@ -21,6 +21,9 @@ GROUPS docker Manage Artifact Registry container images and tags. + files + Manage Artifact Registry files. + locations Manage Artifact Registry resource locations. diff --git a/gcloud/auth/application-default/login b/gcloud/auth/application-default/login index 02a6ccb6c..072208385 100644 --- a/gcloud/auth/application-default/login +++ b/gcloud/auth/application-default/login @@ -92,14 +92,9 @@ FLAGS ◆ You always want to bill the project owning the resources. --launch-browser - (DEPRECATED) Launch a browser for authorization. If not enabled or if - it is not possible to launch a browser, prints a URL to standard output - to be copied. - - The --[no-]launch-browser flags are deprecated and will be removed on - June 7th 2022 (Release 389.0.0). Use --no-browser to replace - --no-launch-browser. Enabled by default, use --no-launch-browser to - disable. + Launch a browser for authorization. If not enabled or if it is not + possible to launch a browser, prints a URL to standard output to be + copied. Enabled by default, use --no-launch-browser to disable. --scopes=SCOPES,[SCOPES,...] The names of the scopes to authorize for. By default openid, diff --git a/gcloud/auth/login b/gcloud/auth/login index 1e802b6cc..29850b688 100644 --- a/gcloud/auth/login +++ b/gcloud/auth/login @@ -92,14 +92,9 @@ FLAGS credentials. --launch-browser - (DEPRECATED) Launch a browser for authorization. If not enabled or if - it is not possible to launch a browser, prints a URL to standard output - to be copied. - - The --[no-]launch-browser flags are deprecated and will be removed on - June 7th 2022 (Release 389.0.0). Use --no-browser to replace - --no-launch-browser. Enabled by default, use --no-launch-browser to - disable. + Launch a browser for authorization. If not enabled or if it is not + possible to launch a browser, prints a URL to standard output to be + copied. Enabled by default, use --no-launch-browser to disable. --update-adc Write the obtained credentials to the well-known location for diff --git a/gcloud/beta/artifacts/files/help b/gcloud/beta/artifacts/files/help new file mode 100644 index 000000000..638c1e448 --- /dev/null +++ b/gcloud/beta/artifacts/files/help @@ -0,0 +1,36 @@ +NAME + gcloud beta artifacts files - manage Artifact Registry files + +SYNOPSIS + gcloud beta artifacts files COMMAND [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list all files in the current project and artifacts/repository and + artifacts/location properties are set, run: + + $ gcloud beta artifacts files list + + To list files under repository my-repo in the current project and location, + run: + + $ gcloud beta artifacts files list --repository=my-repo + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (BETA) List Artifact Registry files. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud artifacts files + + $ gcloud alpha artifacts files + diff --git a/gcloud/beta/artifacts/files/list b/gcloud/beta/artifacts/files/list new file mode 100644 index 000000000..bc4bcf159 --- /dev/null +++ b/gcloud/beta/artifacts/files/list @@ -0,0 +1,126 @@ +NAME + gcloud beta artifacts files list - list Artifact Registry files + +SYNOPSIS + gcloud beta artifacts files list [--package=PACKAGE] [--tag=TAG] + [--version=VERSION] [--repository=REPOSITORY : --location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all Artifact Registry files in the specified repository and + location. + + To specify the maximum number of files to list, use the --limit flag. + +EXAMPLES + To list files in the current project under repository my-repo in + us-central1: + + $ gcloud beta artifacts files list --repository=my-repo \ + --location=us-central1 + + The following command lists a maximum of five files: + + $ gcloud beta artifacts files list --repository=my-repo \ + --location=us-central1 --limit=5 + + To list files in the current project under repository my-repo in + us-central1 owned by package my-package: + + $ gcloud beta artifacts files list --repository=my-repo \ + --location=us-central1 --package=my-package + + To list files in the current project under repository my-repo in + us-central1 owned by package my-package and version 1.0.0: + + $ gcloud beta artifacts files list --repository=my-repo \ + --location=us-central1 --package=my-package --version=1.0.0 + + To list files in the current project under repository my-repo in + us-central1 owned by package my-package and tag name my-tag: + + $ gcloud beta artifacts files list --repository=my-repo \ + --location=us-central1 --package=my-package --tag=my-tag + +FLAGS + --package=PACKAGE + List all files in a specified artifact, such as a container image or a + language package. If you do not use --tag or --version in the command, + the command lists files in all versions of the artifact. + + --tag=TAG + List all files in the artifact version with the specified tag. This + flag only works with formats that use tags, such as container images. + Use the --package flag to specify the artifact. + + --version=VERSION + List all files in the specified artifact version. Use the --package + flag to specify the artifact. + + Repository resource - The Artifact Registry repository. If not specified, + the current artifacts/repository is used. The arguments in this group can + be used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. To set + the project attribute: + ◆ provide the argument --repository on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --location=LOCATION + Location of the repository. To set the location attribute: + ▸ provide the argument --repository on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud artifacts files list + + $ gcloud alpha artifacts files list + diff --git a/gcloud/beta/artifacts/help b/gcloud/beta/artifacts/help index 538e2d5c1..56d49c79b 100644 --- a/gcloud/beta/artifacts/help +++ b/gcloud/beta/artifacts/help @@ -21,6 +21,9 @@ GROUPS docker (BETA) Manage Artifact Registry container images and tags. + files + (BETA) Manage Artifact Registry files. + locations (BETA) Manage Artifact Registry resource locations. diff --git a/gcloud/beta/auth/application-default/login b/gcloud/beta/auth/application-default/login index 8c8468759..171b7a990 100644 --- a/gcloud/beta/auth/application-default/login +++ b/gcloud/beta/auth/application-default/login @@ -92,14 +92,9 @@ FLAGS ◆ You always want to bill the project owning the resources. --launch-browser - (DEPRECATED) Launch a browser for authorization. If not enabled or if - it is not possible to launch a browser, prints a URL to standard output - to be copied. - - The --[no-]launch-browser flags are deprecated and will be removed on - June 7th 2022 (Release 389.0.0). Use --no-browser to replace - --no-launch-browser. Enabled by default, use --no-launch-browser to - disable. + Launch a browser for authorization. If not enabled or if it is not + possible to launch a browser, prints a URL to standard output to be + copied. Enabled by default, use --no-launch-browser to disable. --scopes=SCOPES,[SCOPES,...] The names of the scopes to authorize for. By default openid, diff --git a/gcloud/beta/auth/login b/gcloud/beta/auth/login index 467e83d86..c282d95c4 100644 --- a/gcloud/beta/auth/login +++ b/gcloud/beta/auth/login @@ -93,14 +93,9 @@ FLAGS credentials. --launch-browser - (DEPRECATED) Launch a browser for authorization. If not enabled or if - it is not possible to launch a browser, prints a URL to standard output - to be copied. - - The --[no-]launch-browser flags are deprecated and will be removed on - June 7th 2022 (Release 389.0.0). Use --no-browser to replace - --no-launch-browser. Enabled by default, use --no-launch-browser to - disable. + Launch a browser for authorization. If not enabled or if it is not + possible to launch a browser, prints a URL to standard output to be + copied. Enabled by default, use --no-launch-browser to disable. --update-adc Write the obtained credentials to the well-known location for diff --git a/gcloud/beta/composer/environments/create b/gcloud/beta/composer/environments/create index ea9b23cc5..5c88b6db6 100644 --- a/gcloud/beta/composer/environments/create +++ b/gcloud/beta/composer/environments/create @@ -6,8 +6,7 @@ SYNOPSIS gcloud beta composer environments create (ENVIRONMENT : --location=LOCATION) [--airflow-configs=[KEY=VALUE,...]] [--async] [--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE] - [--disk-size=DISK_SIZE] [--enable-ip-masq-agent] - [--env-variables=[NAME=VALUE,...]] + [--disk-size=DISK_SIZE] [--env-variables=[NAME=VALUE,...]] [--environment-size=ENVIRONMENT_SIZE] [--labels=[KEY=VALUE,...]] [--machine-type=MACHINE_TYPE] [--node-count=NODE_COUNT] [--oauth-scopes=[SCOPE,...]] [--python-version=PYTHON_VERSION] @@ -23,7 +22,8 @@ SYNOPSIS --web-server-ipv4-cidr=WEB_SERVER_IPV4_CIDR] [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR --cluster-secondary-range-name=CLUSTER_SECONDARY_RANGE_NAME - --enable-ip-alias --max-pods-per-node=MAX_PODS_PER_NODE + --enable-ip-alias --enable-ip-masq-agent + --max-pods-per-node=MAX_PODS_PER_NODE --services-ipv4-cidr=SERVICES_IPV4_CIDR --services-secondary-range-name=SERVICES_SECONDARY_RANGE_NAME] [--enable-master-authorized-networks @@ -111,12 +111,6 @@ FLAGS multiple of gigabytes. Cannot be updated after the environment has been created. If units are not provided, defaults to GB. - --enable-ip-masq-agent - When enabled the IP Masq Agent is deployed to the cluster with - configuration to masquarade all traffic except between pods. - - Cannot be specified unless --enable-ip-alias is also specified. - --env-variables=[NAME=VALUE,...] A comma-delimited list of environment variable NAME=VALUE pairs to provide to the Airflow scheduler, worker, and webserver processes. NAME @@ -297,6 +291,16 @@ FLAGS will require at least two secondary ranges in the subnetwork, one for the pod IPs and another to reserve space for the services range. + --enable-ip-masq-agent + When enabled, the IP Masquarade Agent + (https://cloud.google.com/composer/docs/enable-ip-masquerade-agent) + is deployed to your environment's cluster. It performs many-to-one IP + address translations to hide a pod's IP address behind the cluster + node's IP address. This is done when sending traffic to destinations + outside the cluster's pod CIDR range. + + Cannot be specified unless --enable-ip-alias is also specified. + --max-pods-per-node=MAX_PODS_PER_NODE Maximum number of pods that can be assigned to a single node, can be used to limit the size of IP range assigned to the node in VPC native diff --git a/gcloud/beta/compute/backend-services/create b/gcloud/beta/compute/backend-services/create index b2d26572b..f504d49c4 100644 --- a/gcloud/beta/compute/backend-services/create +++ b/gcloud/beta/compute/backend-services/create @@ -265,8 +265,8 @@ FLAGS The logging options for the load balancer traffic served by this backend service. If logging is enabled, logs will be exported to Cloud Logging. This can only be specified if the protocol is HTTP, HTTPS, - HTTP2, TCP, or SSL. Disabled by default. Use --enable-logging to enable - and --no-enable-logging to disable. + HTTP2, TCP, SSL, UDP, or UNSPECIFIED. Disabled by default. Use + --enable-logging to enable and --no-enable-logging to disable. --[no-]enable-strong-affinity Enable or disable strong session affinity. This is only available for @@ -342,7 +342,8 @@ FLAGS This configures the sampling rate of requests to the load balancer where 1.0 means all logged requests are reported and 0.0 means no logged requests are reported. This can only be specified if the - protocol is HTTP, HTTPS, HTTP2, TCP, or SSL. The default value is 1.0. + protocol is HTTP, HTTPS, HTTP2, TCP, SSL, UDP, or UNSPECIFIED. The + default value is 0.0. --max-ttl=MAX_TTL Specifies the maximum allowed TTL for cached content served by this diff --git a/gcloud/beta/compute/backend-services/update b/gcloud/beta/compute/backend-services/update index 922984547..e20093c80 100644 --- a/gcloud/beta/compute/backend-services/update +++ b/gcloud/beta/compute/backend-services/update @@ -178,8 +178,8 @@ FLAGS The logging options for the load balancer traffic served by this backend service. If logging is enabled, logs will be exported to Cloud Logging. This can only be specified if the protocol is HTTP, HTTPS, - HTTP2, TCP, or SSL. Disabled by default. Use --enable-logging to enable - and --no-enable-logging to disable. + HTTP2, TCP, SSL, UDP, or UNSPECIFIED. Disabled by default. Use + --enable-logging to enable and --no-enable-logging to disable. --[no-]enable-strong-affinity Enable or disable strong session affinity. This is only available for @@ -249,7 +249,8 @@ FLAGS This configures the sampling rate of requests to the load balancer where 1.0 means all logged requests are reported and 0.0 means no logged requests are reported. This can only be specified if the - protocol is HTTP, HTTPS, HTTP2, TCP, or SSL. The default value is 1.0. + protocol is HTTP, HTTPS, HTTP2, TCP, SSL, UDP, or UNSPECIFIED. The + default value is 0.0. --port-name=PORT_NAME Backend services for external HTTP(S) load balancing, internal HTTP(S) diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index 9bbbff33d..2a16b8da3 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -411,7 +411,7 @@ FLAGS --maintenance-policy=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/beta/compute/instance-templates/create-with-container b/gcloud/beta/compute/instance-templates/create-with-container index 38a77a9a3..7f7b63d9c 100644 --- a/gcloud/beta/compute/instance-templates/create-with-container +++ b/gcloud/beta/compute/instance-templates/create-with-container @@ -411,7 +411,7 @@ FLAGS --maintenance-policy=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index cc82c351b..945b9837f 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -794,7 +794,7 @@ OPTIONAL FLAGS (DEPRECATED) Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. The --maintenance-policy flag is now deprecated. Please use --on-host-maintenance instead. MAINTENANCE_POLICY must be one of: @@ -809,7 +809,7 @@ OPTIONAL FLAGS --on-host-maintenance=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index ea861a2e8..0a2191563 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -477,7 +477,7 @@ FLAGS --maintenance-policy=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index b627f4b27..9a46b4d15 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -445,7 +445,7 @@ FLAGS --maintenance-policy=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/beta/compute/instances/set-scheduling b/gcloud/beta/compute/instances/set-scheduling index ce090c05e..30a1bcffd 100644 --- a/gcloud/beta/compute/instances/set-scheduling +++ b/gcloud/beta/compute/instances/set-scheduling @@ -46,7 +46,7 @@ FLAGS --maintenance-policy=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/beta/compute/networks/create b/gcloud/beta/compute/networks/create index 8274f3197..b2cfb8162 100644 --- a/gcloud/beta/compute/networks/create +++ b/gcloud/beta/compute/networks/create @@ -68,9 +68,9 @@ FLAGS --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet - that can be transmitted on this network. Default value is 1460 bytes, - and the maximum is 1500 bytes. The MTU advertised via DHCP to all - instances attached to this network. + that can be transmitted on this network. Default value is 1460 bytes. + The minimum value is 1300 bytes and the maximum value is 8896 bytes. + The MTU advertised via DHCP to all instances attached to this network. --network-firewall-policy-enforcement-order=NETWORK_FIREWALL_POLICY_ENFORCEMENT_ORDER The Network Firewall Policy enforcement order of this network. If not diff --git a/gcloud/beta/compute/networks/update b/gcloud/beta/compute/networks/update index 81fc7bb56..f65d3d479 100644 --- a/gcloud/beta/compute/networks/update +++ b/gcloud/beta/compute/networks/update @@ -51,9 +51,9 @@ FLAGS --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet - that can be transmitted on this network. Default value is 1460 bytes, - and the maximum is 1500 bytes. The MTU advertised via DHCP to all - instances attached to this network. + that can be transmitted on this network. Default value is 1460 bytes. + The minimum value is 1300 bytes and the maximum value is 8896 bytes. + The MTU advertised via DHCP to all instances attached to this network. --network-firewall-policy-enforcement-order=NETWORK_FIREWALL_POLICY_ENFORCEMENT_ORDER The Network Firewall Policy enforcement order of this network. If not diff --git a/gcloud/beta/compute/target-https-proxies/create b/gcloud/beta/compute/target-https-proxies/create index 1169ba5da..5e109709b 100644 --- a/gcloud/beta/compute/target-https-proxies/create +++ b/gcloud/beta/compute/target-https-proxies/create @@ -31,12 +31,12 @@ EXAMPLES pointing to this map by running: $ gcloud beta compute target-https-proxies create PROXY_NAME \ - --url-map=URL_MAP --ssl-certificates=SSL_CERTIFIFCATE + --url-map=URL_MAP --ssl-certificates=SSL_CERTIFICATE Create a regional target HTTPS proxy by running: $ gcloud beta compute target-https-proxies create PROXY_NAME \ - --url-map=URL_MAP --ssl-certificates=SSL_CERTIFIFCATE \ + --url-map=URL_MAP --ssl-certificates=SSL_CERTIFICATE \ --region=REGION_NAME POSITIONAL ARGUMENTS diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index 2fb99745c..37d2797dc 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -447,7 +447,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -487,39 +487,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 482a0de27..c5505d068 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -479,7 +479,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -519,39 +519,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 38fc4f3b1..854c83d84 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -481,7 +481,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -521,39 +521,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index f3a8bcd34..a658d1524 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -49,7 +49,7 @@ EXAMPLES $ gcloud beta config set proxy/port 8080 For a full list of accepted values, see the Google Cloud CLI properties - page: https://cloud.google.com/sdk/docs/properties + page: https://cloud.google.com/sdk/docs/properties. POSITIONAL ARGUMENTS SECTION/PROPERTY @@ -494,7 +494,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -534,39 +534,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 413f378ce..50c2c7dad 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -455,7 +455,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -495,39 +495,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 3798a6f7e..230b79688 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -309,8 +309,9 @@ FLAGS Size for node VM boot disks in GB. Defaults to 100GB. --disk-type=DISK_TYPE - Type of the node VM boot disk. Defaults to pd-standard. DISK_TYPE must - be one of: pd-standard, pd-ssd, pd-balanced. + Type of the node VM boot disk. For version 1.24.0+, defaults to + pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE + must be one of: pd-standard, pd-ssd, pd-balanced. --enable-autorepair Enable node autorepair feature for a cluster's default node pool(s). diff --git a/gcloud/beta/container/fleet/config-management/apply b/gcloud/beta/container/fleet/config-management/apply index 3804a95fe..be61ab6b3 100644 --- a/gcloud/beta/container/fleet/config-management/apply +++ b/gcloud/beta/container/fleet/config-management/apply @@ -18,7 +18,7 @@ EXAMPLES then run: $ gcloud beta container fleet config-management apply \ - --membership=CLUSTER_NAME --config=APPLY-SPEC.YAML \ + --membership=MEMBERSHIP_NAME --config=APPLY-SPEC.YAML \ --version=VERSION REQUIRED FLAGS diff --git a/gcloud/beta/container/fleet/config-management/unmanage b/gcloud/beta/container/fleet/config-management/unmanage index 07e394a7f..6e6b24ca4 100644 --- a/gcloud/beta/container/fleet/config-management/unmanage +++ b/gcloud/beta/container/fleet/config-management/unmanage @@ -12,10 +12,10 @@ DESCRIPTION unmanaged. EXAMPLES - To remove the Config Management Feature spec for a Membership, run: + To remove the Config Management Feature spec for a membership, run: $ gcloud beta container fleet config-management unmanage \ - --membership=CLUSTER_NAME + --membership=MEMBERSHIP_NAME FLAGS --membership=MEMBERSHIP diff --git a/gcloud/beta/container/fleet/config-management/upgrade b/gcloud/beta/container/fleet/config-management/upgrade index 432498cac..5870cdab3 100644 --- a/gcloud/beta/container/fleet/config-management/upgrade +++ b/gcloud/beta/container/fleet/config-management/upgrade @@ -11,10 +11,10 @@ DESCRIPTION Config Management Feature. EXAMPLES - To upgrade a membership named CLUSTER_NAME, run: + To upgrade a membership named MEMBERSHIP_NAME, run: $ gcloud beta container fleet config-management upgrade \ - --membership=CLUSTER_NAME --version=VERSION + --membership=MEMBERSHIP_NAME --version=VERSION REQUIRED FLAGS --version=VERSION diff --git a/gcloud/beta/container/fleet/help b/gcloud/beta/container/fleet/help index ba0b9c258..a9ae6b1f1 100644 --- a/gcloud/beta/container/fleet/help +++ b/gcloud/beta/container/fleet/help @@ -62,7 +62,7 @@ GROUPS memberships (BETA) Manage memberships of all your GKE and other Kubernetes cluster - with Fleet. + with fleets. mesh (BETA) Manage Service Mesh Feature. diff --git a/gcloud/beta/container/fleet/identity-service/apply b/gcloud/beta/container/fleet/identity-service/apply index bab2d1f75..4dadd8ce0 100644 --- a/gcloud/beta/container/fleet/identity-service/apply +++ b/gcloud/beta/container/fleet/identity-service/apply @@ -18,7 +18,7 @@ EXAMPLES To apply an Identity Service configuration for a membership, run: $ gcloud beta container fleet identity-service apply \ - --membership=CLUSTER_NAME \ + --membership=MEMBERSHIP_NAME \ --config=/path/to/identity-service.yaml REQUIRED FLAGS diff --git a/gcloud/beta/container/fleet/identity-service/delete b/gcloud/beta/container/fleet/identity-service/delete index ccc18cfcd..303b62a62 100644 --- a/gcloud/beta/container/fleet/identity-service/delete +++ b/gcloud/beta/container/fleet/identity-service/delete @@ -13,7 +13,7 @@ EXAMPLES To delete an Identity Service configuration for a membership, run: $ gcloud beta container fleet identity-service delete \ - --membership=CLUSTER_NAME + --membership=MEMBERSHIP_NAME FLAGS --membership=MEMBERSHIP diff --git a/gcloud/beta/container/fleet/memberships/delete b/gcloud/beta/container/fleet/memberships/delete index 292f85b7f..3333000e1 100644 --- a/gcloud/beta/container/fleet/memberships/delete +++ b/gcloud/beta/container/fleet/memberships/delete @@ -6,7 +6,7 @@ SYNOPSIS (MEMBERSHIP : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command deletes the Fleet membership resource corresponding to + (BETA) This command deletes the Fleet Membership resource corresponding to the cluster. This command is intended to delete stale Fleet Membership resources as @@ -22,7 +22,7 @@ EXAMPLES $ gcloud beta container fleet memberships list - Delete a membership from Fleet: + Delete a membership from the active project's fleet: $ gcloud beta container fleet memberships delete MEMBERSHIP_NAME diff --git a/gcloud/beta/container/fleet/memberships/get-credentials b/gcloud/beta/container/fleet/memberships/get-credentials index 8c9d9f531..77cfb9da5 100644 --- a/gcloud/beta/container/fleet/memberships/get-credentials +++ b/gcloud/beta/container/fleet/memberships/get-credentials @@ -1,6 +1,6 @@ NAME gcloud beta container fleet memberships get-credentials - fetch credentials - for a Fleet-registered cluster to be used in Connect Gateway + for a fleet-registered cluster to be used in Connect Gateway SYNOPSIS gcloud beta container fleet memberships get-credentials MEMBERSHIP @@ -9,7 +9,7 @@ SYNOPSIS DESCRIPTION (BETA) gcloud beta container fleet memberships get-credentials updates the kubeconfig file with the appropriate credentials and endpoint information - to send kubectl commands to a Fleet-registered and connected cluster + to send kubectl commands to a fleet-registered and connected cluster through Connect Gateway Service. It takes a project, passed through by set defaults or flags. By default, diff --git a/gcloud/beta/container/fleet/memberships/help b/gcloud/beta/container/fleet/memberships/help index eb72a1b1f..ccd168953 100644 --- a/gcloud/beta/container/fleet/memberships/help +++ b/gcloud/beta/container/fleet/memberships/help @@ -1,13 +1,13 @@ NAME gcloud beta container fleet memberships - manage memberships of all your - GKE and other Kubernetes cluster with Fleet + GKE and other Kubernetes cluster with fleets SYNOPSIS gcloud beta container fleet memberships COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Manage memberships of all your GKE and other Kubernetes cluster with - Fleet. + fleets. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -27,14 +27,14 @@ COMMANDS (BETA) Generate RBAC policy files for connected clusters by the user. get-credentials - (BETA) Fetch credentials for a Fleet-registered cluster to be used in + (BETA) Fetch credentials for a fleet-registered cluster to be used in Connect Gateway. list (BETA) List memberships. register - (BETA) Register a cluster with Fleet. + (BETA) Register a cluster with a fleet. unregister (BETA) Unregister a cluster from Fleet. diff --git a/gcloud/beta/container/fleet/memberships/list b/gcloud/beta/container/fleet/memberships/list index 03137fedc..e6e6c5479 100644 --- a/gcloud/beta/container/fleet/memberships/list +++ b/gcloud/beta/container/fleet/memberships/list @@ -7,10 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List memberships in Fleet. + (BETA) List memberships in a fleet. EXAMPLES - List memberships in Fleet: + List memberships in the active project's fleet: $ gcloud beta container fleet memberships list diff --git a/gcloud/beta/container/fleet/memberships/register b/gcloud/beta/container/fleet/memberships/register index 6f2ae7f3b..ed47d425c 100644 --- a/gcloud/beta/container/fleet/memberships/register +++ b/gcloud/beta/container/fleet/memberships/register @@ -1,9 +1,9 @@ NAME gcloud beta container fleet memberships register - register a cluster with - Fleet + a fleet SYNOPSIS - gcloud beta container fleet memberships register CLUSTER_NAME + gcloud beta container fleet memberships register MEMBERSHIP_NAME (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) (--service-account-key-file=SERVICE_ACCOUNT_KEY_FILE @@ -13,15 +13,15 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command registers a cluster with the Fleet by: + (BETA) This command registers a cluster with the fleet by: 1. Creating a Fleet Membership resource corresponding to the cluster. 2. Adding in-cluster Kubernetes Resources that make the cluster exclusive - to one Fleet. + to one fleet. 3. Installing the Connect Agent into this cluster. A successful registration implies that the cluster is now exclusive to a - single Fleet. + single fleet. For more information about Connect Agent, go to: https://cloud.google.com/anthos/multicluster-management/connect/overview/ @@ -40,9 +40,9 @@ DESCRIPTION If the cluster is already registered to another Fleet, the registration is not successful. - Rerunning this command against the same cluster with the same CLUSTER_NAME - and target GKEFleet is successful and upgrades the Connect Agent if a new - agent is available. + Rerunning this command against the same cluster with the same + MEMBERSHIP_NAME and target GKEFleet is successful and upgrades the Connect + Agent if a new agent is available. EXAMPLES Register a non-GKE or GKE On-Prem cluster referenced from a specific @@ -117,9 +117,9 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json POSITIONAL ARGUMENTS - CLUSTER_NAME + MEMBERSHIP_NAME The membership name that you choose to uniquely represents the cluster - being registered on the Fleet. + being registered on the fleet. REQUIRED FLAGS Cluster identifier. @@ -171,7 +171,7 @@ REQUIRED FLAGS Workload Identity --enable-workload-identity - Enable Workload Identity when registering the cluster with Fleet. + Enable Workload Identity when registering the cluster with a fleet. Ensure that GKE Workload Identity is enabled on your GKE cluster, it is a requirement for using Workload Identity with memberships. Refer to the Registering a cluster using Workload Identity section diff --git a/gcloud/beta/container/fleet/memberships/unregister b/gcloud/beta/container/fleet/memberships/unregister index 17fa4a42c..50d966394 100644 --- a/gcloud/beta/container/fleet/memberships/unregister +++ b/gcloud/beta/container/fleet/memberships/unregister @@ -3,18 +3,18 @@ NAME from Fleet SYNOPSIS - gcloud beta container fleet memberships unregister CLUSTER_NAME + gcloud beta container fleet memberships unregister MEMBERSHIP_NAME (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command unregisters a cluster with the Fleet by: + (BETA) This command unregisters a cluster with the fleet by: 1. Deleting the Fleet Membership resource for this cluster (a.k.a `gcloud beta container fleet memberships delete`). 2. Removing the corresponding in-cluster Kubernetes Resources that make the - cluster exclusive to one Fleet (a.k.a `kubectl delete memberships + cluster exclusive to one fleet (a.k.a `kubectl delete memberships membership`). 3. Uninstalling the Connect Agent from this cluster (a.k.a `kubectl delete on the gke-connect namespace`). @@ -58,7 +58,7 @@ EXAMPLES --gke-cluster=my-cluster-region-or-zone/my-cluster POSITIONAL ARGUMENTS - CLUSTER_NAME + MEMBERSHIP_NAME The membership name that corresponds to the cluster being unregistered. To get list of all the memberships on the Fleet, consider using the command: gcloud beta container fleet memberships list. diff --git a/gcloud/beta/container/hub/config-management/apply b/gcloud/beta/container/hub/config-management/apply index 98ef6f505..1fbecd058 100644 --- a/gcloud/beta/container/hub/config-management/apply +++ b/gcloud/beta/container/hub/config-management/apply @@ -18,7 +18,7 @@ EXAMPLES then run: $ gcloud beta container hub config-management apply \ - --membership=CLUSTER_NAME --config=APPLY-SPEC.YAML \ + --membership=MEMBERSHIP_NAME --config=APPLY-SPEC.YAML \ --version=VERSION REQUIRED FLAGS diff --git a/gcloud/beta/container/hub/config-management/unmanage b/gcloud/beta/container/hub/config-management/unmanage index 9f0d3a652..d4be893ec 100644 --- a/gcloud/beta/container/hub/config-management/unmanage +++ b/gcloud/beta/container/hub/config-management/unmanage @@ -12,10 +12,10 @@ DESCRIPTION unmanaged. EXAMPLES - To remove the Config Management Feature spec for a Membership, run: + To remove the Config Management Feature spec for a membership, run: $ gcloud beta container hub config-management unmanage \ - --membership=CLUSTER_NAME + --membership=MEMBERSHIP_NAME FLAGS --membership=MEMBERSHIP diff --git a/gcloud/beta/container/hub/config-management/upgrade b/gcloud/beta/container/hub/config-management/upgrade index aaa8f65b9..e39caa8b3 100644 --- a/gcloud/beta/container/hub/config-management/upgrade +++ b/gcloud/beta/container/hub/config-management/upgrade @@ -11,10 +11,10 @@ DESCRIPTION Config Management Feature. EXAMPLES - To upgrade a membership named CLUSTER_NAME, run: + To upgrade a membership named MEMBERSHIP_NAME, run: $ gcloud beta container hub config-management upgrade \ - --membership=CLUSTER_NAME --version=VERSION + --membership=MEMBERSHIP_NAME --version=VERSION REQUIRED FLAGS --version=VERSION diff --git a/gcloud/beta/container/hub/help b/gcloud/beta/container/hub/help index 577d63fbd..adf616318 100644 --- a/gcloud/beta/container/hub/help +++ b/gcloud/beta/container/hub/help @@ -62,7 +62,7 @@ GROUPS memberships (BETA) Manage memberships of all your GKE and other Kubernetes cluster - with Fleet. + with fleets. mesh (BETA) Manage Service Mesh Feature. diff --git a/gcloud/beta/container/hub/identity-service/apply b/gcloud/beta/container/hub/identity-service/apply index 1f64cfcd4..55d40c40b 100644 --- a/gcloud/beta/container/hub/identity-service/apply +++ b/gcloud/beta/container/hub/identity-service/apply @@ -18,7 +18,7 @@ EXAMPLES To apply an Identity Service configuration for a membership, run: $ gcloud beta container hub identity-service apply \ - --membership=CLUSTER_NAME \ + --membership=MEMBERSHIP_NAME \ --config=/path/to/identity-service.yaml REQUIRED FLAGS diff --git a/gcloud/beta/container/hub/identity-service/delete b/gcloud/beta/container/hub/identity-service/delete index a3eb03bf9..94c14ce19 100644 --- a/gcloud/beta/container/hub/identity-service/delete +++ b/gcloud/beta/container/hub/identity-service/delete @@ -13,7 +13,7 @@ EXAMPLES To delete an Identity Service configuration for a membership, run: $ gcloud beta container hub identity-service delete \ - --membership=CLUSTER_NAME + --membership=MEMBERSHIP_NAME FLAGS --membership=MEMBERSHIP diff --git a/gcloud/beta/container/hub/memberships/delete b/gcloud/beta/container/hub/memberships/delete index 2156488bb..0736a046d 100644 --- a/gcloud/beta/container/hub/memberships/delete +++ b/gcloud/beta/container/hub/memberships/delete @@ -6,7 +6,7 @@ SYNOPSIS (MEMBERSHIP : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command deletes the Fleet membership resource corresponding to + (BETA) This command deletes the Fleet Membership resource corresponding to the cluster. This command is intended to delete stale Fleet Membership resources as @@ -22,7 +22,7 @@ EXAMPLES $ gcloud beta container hub memberships list - Delete a membership from Fleet: + Delete a membership from the active project's fleet: $ gcloud beta container hub memberships delete MEMBERSHIP_NAME diff --git a/gcloud/beta/container/hub/memberships/get-credentials b/gcloud/beta/container/hub/memberships/get-credentials index 0673758cb..ef200a329 100644 --- a/gcloud/beta/container/hub/memberships/get-credentials +++ b/gcloud/beta/container/hub/memberships/get-credentials @@ -1,6 +1,6 @@ NAME gcloud beta container hub memberships get-credentials - fetch credentials - for a Fleet-registered cluster to be used in Connect Gateway + for a fleet-registered cluster to be used in Connect Gateway SYNOPSIS gcloud beta container hub memberships get-credentials MEMBERSHIP @@ -9,7 +9,7 @@ SYNOPSIS DESCRIPTION (BETA) gcloud beta container hub memberships get-credentials updates the kubeconfig file with the appropriate credentials and endpoint information - to send kubectl commands to a Fleet-registered and connected cluster + to send kubectl commands to a fleet-registered and connected cluster through Connect Gateway Service. It takes a project, passed through by set defaults or flags. By default, diff --git a/gcloud/beta/container/hub/memberships/help b/gcloud/beta/container/hub/memberships/help index 0b5d0ae3e..eeac9b543 100644 --- a/gcloud/beta/container/hub/memberships/help +++ b/gcloud/beta/container/hub/memberships/help @@ -1,13 +1,13 @@ NAME gcloud beta container hub memberships - manage memberships of all your GKE - and other Kubernetes cluster with Fleet + and other Kubernetes cluster with fleets SYNOPSIS gcloud beta container hub memberships COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Manage memberships of all your GKE and other Kubernetes cluster with - Fleet. + fleets. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -27,14 +27,14 @@ COMMANDS (BETA) Generate RBAC policy files for connected clusters by the user. get-credentials - (BETA) Fetch credentials for a Fleet-registered cluster to be used in + (BETA) Fetch credentials for a fleet-registered cluster to be used in Connect Gateway. list (BETA) List memberships. register - (BETA) Register a cluster with Fleet. + (BETA) Register a cluster with a fleet. unregister (BETA) Unregister a cluster from Fleet. diff --git a/gcloud/beta/container/hub/memberships/list b/gcloud/beta/container/hub/memberships/list index 6e037e90c..dee87f6d9 100644 --- a/gcloud/beta/container/hub/memberships/list +++ b/gcloud/beta/container/hub/memberships/list @@ -7,10 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List memberships in Fleet. + (BETA) List memberships in a fleet. EXAMPLES - List memberships in Fleet: + List memberships in the active project's fleet: $ gcloud beta container hub memberships list diff --git a/gcloud/beta/container/hub/memberships/register b/gcloud/beta/container/hub/memberships/register index 2d8c4d7f8..8d1aab8c4 100644 --- a/gcloud/beta/container/hub/memberships/register +++ b/gcloud/beta/container/hub/memberships/register @@ -1,9 +1,9 @@ NAME - gcloud beta container hub memberships register - register a cluster with - Fleet + gcloud beta container hub memberships register - register a cluster with a + fleet SYNOPSIS - gcloud beta container hub memberships register CLUSTER_NAME + gcloud beta container hub memberships register MEMBERSHIP_NAME (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) (--service-account-key-file=SERVICE_ACCOUNT_KEY_FILE @@ -13,15 +13,15 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command registers a cluster with the Fleet by: + (BETA) This command registers a cluster with the fleet by: 1. Creating a Fleet Membership resource corresponding to the cluster. 2. Adding in-cluster Kubernetes Resources that make the cluster exclusive - to one Fleet. + to one fleet. 3. Installing the Connect Agent into this cluster. A successful registration implies that the cluster is now exclusive to a - single Fleet. + single fleet. For more information about Connect Agent, go to: https://cloud.google.com/anthos/multicluster-management/connect/overview/ @@ -40,9 +40,9 @@ DESCRIPTION If the cluster is already registered to another Fleet, the registration is not successful. - Rerunning this command against the same cluster with the same CLUSTER_NAME - and target GKEFleet is successful and upgrades the Connect Agent if a new - agent is available. + Rerunning this command against the same cluster with the same + MEMBERSHIP_NAME and target GKEFleet is successful and upgrades the Connect + Agent if a new agent is available. EXAMPLES Register a non-GKE or GKE On-Prem cluster referenced from a specific @@ -117,9 +117,9 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json POSITIONAL ARGUMENTS - CLUSTER_NAME + MEMBERSHIP_NAME The membership name that you choose to uniquely represents the cluster - being registered on the Fleet. + being registered on the fleet. REQUIRED FLAGS Cluster identifier. @@ -171,7 +171,7 @@ REQUIRED FLAGS Workload Identity --enable-workload-identity - Enable Workload Identity when registering the cluster with Fleet. + Enable Workload Identity when registering the cluster with a fleet. Ensure that GKE Workload Identity is enabled on your GKE cluster, it is a requirement for using Workload Identity with memberships. Refer to the Registering a cluster using Workload Identity section diff --git a/gcloud/beta/container/hub/memberships/unregister b/gcloud/beta/container/hub/memberships/unregister index 0df984bae..77a2aa7c8 100644 --- a/gcloud/beta/container/hub/memberships/unregister +++ b/gcloud/beta/container/hub/memberships/unregister @@ -3,18 +3,18 @@ NAME from Fleet SYNOPSIS - gcloud beta container hub memberships unregister CLUSTER_NAME + gcloud beta container hub memberships unregister MEMBERSHIP_NAME (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command unregisters a cluster with the Fleet by: + (BETA) This command unregisters a cluster with the fleet by: 1. Deleting the Fleet Membership resource for this cluster (a.k.a `gcloud beta container hub memberships delete`). 2. Removing the corresponding in-cluster Kubernetes Resources that make the - cluster exclusive to one Fleet (a.k.a `kubectl delete memberships + cluster exclusive to one fleet (a.k.a `kubectl delete memberships membership`). 3. Uninstalling the Connect Agent from this cluster (a.k.a `kubectl delete on the gke-connect namespace`). @@ -58,7 +58,7 @@ EXAMPLES --gke-cluster=my-cluster-region-or-zone/my-cluster POSITIONAL ARGUMENTS - CLUSTER_NAME + MEMBERSHIP_NAME The membership name that corresponds to the cluster being unregistered. To get list of all the memberships on the Fleet, consider using the command: gcloud beta container hub memberships list. diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index d7f433473..d21980923 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -96,8 +96,9 @@ FLAGS Size for node VM boot disks in GB. Defaults to 100GB. --disk-type=DISK_TYPE - Type of the node VM boot disk. Defaults to pd-standard. DISK_TYPE must - be one of: pd-standard, pd-ssd, pd-balanced. + Type of the node VM boot disk. For version 1.24.0+, defaults to + pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE + must be one of: pd-standard, pd-ssd, pd-balanced. --enable-autoprovisioning Enables Cluster Autoscaler to treat the node pool as if it was diff --git a/gcloud/beta/dataproc/batches/submit/help b/gcloud/beta/dataproc/batches/submit/help index 81a357449..eaf7d3597 100644 --- a/gcloud/beta/dataproc/batches/submit/help +++ b/gcloud/beta/dataproc/batches/submit/help @@ -78,10 +78,9 @@ FLAGS "projects/{project-id}/locations/{region}/services/{service-name}". --properties=[PROPERTY=VALUE,...] - Specifies configuration properties for the batch job. Properties are - mapped to configuration files for the batch job. See [Dataproc - Serverless for Spark job capabilities] - (https://cloud.google.com/dataproc-serverless/docs/overview#for_spark_job_capabilities) + Specifies configuration properties for the workload. See Dataproc + Serverless for Spark documentation + (https://cloud.google.com/dataproc-serverless/docs/concepts/properties) for the list of supported properties. Region resource - Dataproc region to use. Each Dataproc region constitutes diff --git a/gcloud/beta/dataproc/batches/submit/pyspark b/gcloud/beta/dataproc/batches/submit/pyspark index 1d9276f0c..fb4a0c28c 100644 --- a/gcloud/beta/dataproc/batches/submit/pyspark +++ b/gcloud/beta/dataproc/batches/submit/pyspark @@ -90,10 +90,9 @@ FLAGS "projects/{project-id}/locations/{region}/services/{service-name}". --properties=[PROPERTY=VALUE,...] - Specifies configuration properties for the batch job. Properties are - mapped to configuration files for the batch job. See [Dataproc - Serverless for Spark job capabilities] - (https://cloud.google.com/dataproc-serverless/docs/overview#for_spark_job_capabilities) + Specifies configuration properties for the workload. See Dataproc + Serverless for Spark documentation + (https://cloud.google.com/dataproc-serverless/docs/concepts/properties) for the list of supported properties. --py-files=[PY,...] diff --git a/gcloud/beta/dataproc/batches/submit/spark b/gcloud/beta/dataproc/batches/submit/spark index d792c4841..23d33ce52 100644 --- a/gcloud/beta/dataproc/batches/submit/spark +++ b/gcloud/beta/dataproc/batches/submit/spark @@ -109,10 +109,9 @@ OPTIONAL FLAGS "projects/{project-id}/locations/{region}/services/{service-name}". --properties=[PROPERTY=VALUE,...] - Specifies configuration properties for the batch job. Properties are - mapped to configuration files for the batch job. See [Dataproc - Serverless for Spark job capabilities] - (https://cloud.google.com/dataproc-serverless/docs/overview#for_spark_job_capabilities) + Specifies configuration properties for the workload. See Dataproc + Serverless for Spark documentation + (https://cloud.google.com/dataproc-serverless/docs/concepts/properties) for the list of supported properties. Region resource - Dataproc region to use. Each Dataproc region constitutes diff --git a/gcloud/beta/dataproc/batches/submit/spark-r b/gcloud/beta/dataproc/batches/submit/spark-r index a836c3342..143c12f3d 100644 --- a/gcloud/beta/dataproc/batches/submit/spark-r +++ b/gcloud/beta/dataproc/batches/submit/spark-r @@ -86,10 +86,9 @@ FLAGS "projects/{project-id}/locations/{region}/services/{service-name}". --properties=[PROPERTY=VALUE,...] - Specifies configuration properties for the batch job. Properties are - mapped to configuration files for the batch job. See [Dataproc - Serverless for Spark job capabilities] - (https://cloud.google.com/dataproc-serverless/docs/overview#for_spark_job_capabilities) + Specifies configuration properties for the workload. See Dataproc + Serverless for Spark documentation + (https://cloud.google.com/dataproc-serverless/docs/concepts/properties) for the list of supported properties. Region resource - Dataproc region to use. Each Dataproc region constitutes diff --git a/gcloud/beta/dataproc/batches/submit/spark-sql b/gcloud/beta/dataproc/batches/submit/spark-sql index 5f2296c3c..bfe77ff2b 100644 --- a/gcloud/beta/dataproc/batches/submit/spark-sql +++ b/gcloud/beta/dataproc/batches/submit/spark-sql @@ -76,10 +76,9 @@ FLAGS "projects/{project-id}/locations/{region}/services/{service-name}". --properties=[PROPERTY=VALUE,...] - Specifies configuration properties for the batch job. Properties are - mapped to configuration files for the batch job. See [Dataproc - Serverless for Spark job capabilities] - (https://cloud.google.com/dataproc-serverless/docs/overview#for_spark_job_capabilities) + Specifies configuration properties for the workload. See Dataproc + Serverless for Spark documentation + (https://cloud.google.com/dataproc-serverless/docs/concepts/properties) for the list of supported properties. Region resource - Dataproc region to use. Each Dataproc region constitutes diff --git a/gcloud/beta/dns/managed-zones/get-iam-policy b/gcloud/beta/dns/managed-zones/get-iam-policy new file mode 100644 index 000000000..369004a7a --- /dev/null +++ b/gcloud/beta/dns/managed-zones/get-iam-policy @@ -0,0 +1,46 @@ +NAME + gcloud beta dns managed-zones get-iam-policy - get the IAM policy for a + Cloud DNS managed-zone + +SYNOPSIS + gcloud beta dns managed-zones get-iam-policy ZONE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command displays the IAM policy of the specified managed-zone. + +EXAMPLES + To view the details of your managed-zone IAM policy , run: + + $ gcloud beta dns managed-zones get-iam-policy my-zone + +POSITIONAL ARGUMENTS + Zone resource - The name of the managed-zone to get the IAM policy for. + 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 zone 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. + + ZONE + ID of the zone or fully qualified identifier for the zone. To set the + zone attribute: + ▸ provide the argument zone on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha dns managed-zones get-iam-policy + diff --git a/gcloud/beta/dns/managed-zones/help b/gcloud/beta/dns/managed-zones/help index a30d14313..3cd3f26eb 100644 --- a/gcloud/beta/dns/managed-zones/help +++ b/gcloud/beta/dns/managed-zones/help @@ -43,9 +43,15 @@ COMMANDS describe (BETA) View the details of a Cloud DNS managed-zone. + get-iam-policy + (BETA) Get the IAM policy for a Cloud DNS managed-zone. + list (BETA) View the list of all your managed-zones. + set-iam-policy + (BETA) Set the IAM policy for a Cloud DNS managed-zone. + update (BETA) Update an existing Cloud DNS managed-zone. diff --git a/gcloud/beta/dns/managed-zones/set-iam-policy b/gcloud/beta/dns/managed-zones/set-iam-policy new file mode 100644 index 000000000..a33bd73dd --- /dev/null +++ b/gcloud/beta/dns/managed-zones/set-iam-policy @@ -0,0 +1,52 @@ +NAME + gcloud beta dns managed-zones set-iam-policy - set the IAM policy for a + Cloud DNS managed-zone + +SYNOPSIS + gcloud beta dns managed-zones set-iam-policy ZONE --policy-file=POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command sets the IAM policy of the specified managed-zone. + +EXAMPLES + To set the IAM policy of your managed-zone , run: + + $ gcloud beta dns managed-zones set-iam-policy my-zone \ + --policy-file=policy.json + +POSITIONAL ARGUMENTS + Zone resource - The name of the managed-zone to set the IAM policy for. + 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 zone 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. + + ZONE + ID of the zone or fully qualified identifier for the zone. To set the + zone attribute: + ▸ provide the argument zone on the command line. + +REQUIRED FLAGS + --policy-file=POLICY_FILE + JSON or YAML file with the IAM policy + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha dns managed-zones set-iam-policy + diff --git a/gcloud/beta/iap/help b/gcloud/beta/iap/help index ce9251c4d..d5a93b716 100644 --- a/gcloud/beta/iap/help +++ b/gcloud/beta/iap/help @@ -31,6 +31,9 @@ GROUPS settings (BETA) Manage IAP settings. + tcp + (BETA) Manage IAP TCP resources. + web (BETA) Manage IAP web policies. diff --git a/gcloud/beta/iap/tcp/dest-groups/add-iam-policy-binding b/gcloud/beta/iap/tcp/dest-groups/add-iam-policy-binding new file mode 100644 index 000000000..dd72b37b9 --- /dev/null +++ b/gcloud/beta/iap/tcp/dest-groups/add-iam-policy-binding @@ -0,0 +1,128 @@ +NAME + gcloud beta iap tcp dest-groups add-iam-policy-binding - add IAM policy + binding to an IAP TCP Tunnel Destination Group resource + +SYNOPSIS + gcloud beta iap tcp dest-groups add-iam-policy-binding + --group-name=GROUP_NAME --member=PRINCIPAL --region=REGION --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Adds a policy binding to the IAM policy of an IAP TCP Tunnel + Destination Group resource. One binding consists of a member, a role, and + an optional condition. + +EXAMPLES + To add an IAM policy binding for the role of + 'roles/iap.tunnelResourceAccessor' for the user 'test-user@gmail.com' in + the group 'my-group' located in the region 'us-west1', run: + + $ gcloud beta iap tcp dest-groups add-iam-policy-binding \ + --member='user:test-user@gmail.com' \ + --role='roles/iap.tunnelResourceAccessor' \ + --group-name='my-group' --region='us-west1' + + To add an IAM policy binding for the role of + 'roles/iap.tunnelResourceAccessor' for all authenticated users in the group + 'my-group' located in the region 'us-west1', run: + + $ gcloud beta iap tcp dest-groups add-iam-policy-binding \ + --member='allAuthenticatedUsers' \ + --role='roles/iap.tunnelResourceAccessor' \ + --group-name='my-group' --region='us-west1' + + To add an IAM policy binding which expires at the end of the year 2018 for + the role of 'roles/iap.tunnelResourceAccessor' and the user + 'test-user@gmail.com' in the group 'my-group' located in the region + 'us-west1', run: + + $ gcloud beta iap tcp dest-groups add-iam-policy-binding \ + --member='user:test-user@gmail.com' \ + --role='roles/iap.tunnelResourceAccessor' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018, + description=Expires at midnight on 2018-12-31' --group-name='my-group' --region='us-west1' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +REQUIRED FLAGS + --group-name=GROUP_NAME + Name of the Destination Group. + + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --region=REGION + Region of the Destination Group. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iap tcp dest-groups add-iam-policy-binding + diff --git a/gcloud/beta/iap/tcp/dest-groups/create b/gcloud/beta/iap/tcp/dest-groups/create new file mode 100644 index 000000000..e926502b5 --- /dev/null +++ b/gcloud/beta/iap/tcp/dest-groups/create @@ -0,0 +1,68 @@ +NAME + gcloud beta iap tcp dest-groups create - create the IAP TCP Destination + Group resource + +SYNOPSIS + gcloud beta iap tcp dest-groups create GROUP_NAME --region=REGION + [--fqdn-list=FQDN_LIST] [--ip-range-list=IP_RANGE_LIST] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create the IAP TCP Destination Group resource. + +EXAMPLES + To create a DestGroup with name GROUP_NAME, in region REGION in the current + project run: + + $ gcloud beta iap tcp dest-groups create GROUP_NAME --region=REGION + + To create a DestGroup with name GROUP_NAME, in region REGION with ip ranges + CIDR1, CIDR2 in the current project run: + + $ gcloud beta iap tcp dest-groups create GROUP_NAME \ + --region=REGION --ip-range-list=CIDR1,CIDR2 + + To create a DestGroup with name GROUP_NAME, in region REGION with fqdns + FQDN1, FQDN2 in the current project run: + + $ gcloud beta iap tcp dest-groups create GROUP_NAME \ + --region=REGION --fqdn-list=FQDN1,FQDN2 + + To create a DestGroup with name GROUP_NAME, in region REGION with fqdns + FQDN1, FQDN2 and ip ranges CIDR1,CIDR2 in the project PROJECT_ID run: + + $ gcloud beta iap tcp dest-groups create GROUP_NAME \ + --region=REGION --fqdn-list=FQDN1,FQDN2 \ + --ip-range-list=CIDR1,CIDR2 --project=PROJECT_ID + + GROUP_NAME can only contain lower-case letters (a-z) and dashes (-). + +POSITIONAL ARGUMENTS + GROUP_NAME + Name of the Destination Group. + +REQUIRED FLAGS + --region=REGION + Region of the Destination Group. + +OPTIONAL FLAGS + --fqdn-list=FQDN_LIST + List of FQDNs in the Destination Group. + + --ip-range-list=IP_RANGE_LIST + List of ip-ranges in the Destination Group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iap tcp dest-groups create + diff --git a/gcloud/beta/iap/tcp/dest-groups/delete b/gcloud/beta/iap/tcp/dest-groups/delete new file mode 100644 index 000000000..85d36ece3 --- /dev/null +++ b/gcloud/beta/iap/tcp/dest-groups/delete @@ -0,0 +1,46 @@ +NAME + gcloud beta iap tcp dest-groups delete - delete the IAP TCP Destination + Group resource + +SYNOPSIS + gcloud beta iap tcp dest-groups delete GROUP_NAME --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete the IAP TCP Destination Group resource. + +EXAMPLES + To delete a DestGroup with name GROUP_NAME, in region REGION in the current + project run: + + $ gcloud beta iap tcp dest-groups delete DEST_GROUP_NAME \ + --region=REGION + + To delete a DestGroup with name GROUP_NAME, in region REGION in the project + PROJECT_ID run: + + $ gcloud beta iap tcp dest-groups delete DEST_GROUP_NAME \ + --region=REGION --project=PROJECT_ID + +POSITIONAL ARGUMENTS + GROUP_NAME + Name of the Destination Group. + +REQUIRED FLAGS + --region=REGION + Region of the Destination Group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iap tcp dest-groups delete + diff --git a/gcloud/beta/iap/tcp/dest-groups/describe b/gcloud/beta/iap/tcp/dest-groups/describe new file mode 100644 index 000000000..9a214970f --- /dev/null +++ b/gcloud/beta/iap/tcp/dest-groups/describe @@ -0,0 +1,46 @@ +NAME + gcloud beta iap tcp dest-groups describe - describe the IAP TCP Destination + Group resource + +SYNOPSIS + gcloud beta iap tcp dest-groups describe GROUP_NAME --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe the IAP TCP Destination Group resource. + +EXAMPLES + To get a DestGroup with name GROUP_NAME, in region REGION in the current + project run: + + $ gcloud beta iap tcp dest-groups describe DEST_GROUP_NAME \ + --region=REGION + + To get a DestGroup with name GROUP_NAME, in region REGION in the project + PROJECT run: + + $ gcloud beta iap tcp dest-groups describe DEST_GROUP_NAME \ + --region=REGION --project=PROJECT + +POSITIONAL ARGUMENTS + GROUP_NAME + Name of the Destination Group. + +REQUIRED FLAGS + --region=REGION + Region of the Destination Group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iap tcp dest-groups describe + diff --git a/gcloud/beta/iap/tcp/dest-groups/get-iam-policy b/gcloud/beta/iap/tcp/dest-groups/get-iam-policy new file mode 100644 index 000000000..bb11ee0d6 --- /dev/null +++ b/gcloud/beta/iap/tcp/dest-groups/get-iam-policy @@ -0,0 +1,79 @@ +NAME + gcloud beta iap tcp dest-groups get-iam-policy - get IAM policy for an IAP + TCP Destination Group resource + +SYNOPSIS + gcloud beta iap tcp dest-groups get-iam-policy --group-name=GROUP_NAME + --region=REGION [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta iap tcp dest-groups get-iam-policy displays the IAM + policy associated with an IAP TCP Destination Group resource. If formatted + as JSON, the output can be edited and used as a policy file for + set-iam-policy. The output includes an "etag" field identifying the version + emitted and allowing detection of concurrent policy updates; see $ gcloud + beta iap tcp dest-groups set-iam-policy for additional \ details. + +EXAMPLES + To get the IAM policy for the TCP Destination Group resource with name + 'my-group' and located in the region 'us-west1' within the active project, + run: + + $ gcloud beta iap tcp dest-groups get-iam-policy \ + --group-name='my-group' --region='us-west1' + + To get the IAM policy for the TCP Destination Group resource with name + 'my-group' and located in the region 'us-west1' within project 'project', + run: + + $ gcloud beta iap tcp dest-groups get-iam-policy \ + --group-name='my-group' --region='us-west1' --project='project' + +REQUIRED FLAGS + --group-name=GROUP_NAME + Name of the Destination Group. + + --region=REGION + Region of the Destination Group. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iap tcp dest-groups get-iam-policy + diff --git a/gcloud/beta/iap/tcp/dest-groups/help b/gcloud/beta/iap/tcp/dest-groups/help new file mode 100644 index 000000000..0323df97e --- /dev/null +++ b/gcloud/beta/iap/tcp/dest-groups/help @@ -0,0 +1,53 @@ +NAME + gcloud beta iap tcp dest-groups - manage IAP TCP Destination Group + resources + +SYNOPSIS + gcloud beta iap tcp dest-groups COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage IAP TCP Destination Group resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + (BETA) Add IAM policy binding to an IAP TCP Tunnel Destination Group + resource. + + create + (BETA) Create the IAP TCP Destination Group resource. + + delete + (BETA) Delete the IAP TCP Destination Group resource. + + describe + (BETA) Describe the IAP TCP Destination Group resource. + + get-iam-policy + (BETA) Get IAM policy for an IAP TCP Destination Group resource. + + list + (BETA) Lists the IAP TCP Destination Group resource. + + remove-iam-policy-binding + (BETA) Remove IAM policy binding from an IAP TCP Destination Group + resource. + + set-iam-policy + (BETA) Set the IAM policy for an IAP TCP Destination Group resource. + + update + (BETA) Update the IAP TCP Destination Group resource. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iap tcp dest-groups + diff --git a/gcloud/beta/iap/tcp/dest-groups/list b/gcloud/beta/iap/tcp/dest-groups/list new file mode 100644 index 000000000..78d8a9a66 --- /dev/null +++ b/gcloud/beta/iap/tcp/dest-groups/list @@ -0,0 +1,90 @@ +NAME + gcloud beta iap tcp dest-groups list - lists the IAP TCP Destination Group + resource + +SYNOPSIS + gcloud beta iap tcp dest-groups list [--region=REGION; default="-"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Lists the IAP TCP Destination Group resource. + +EXAMPLES + To list all Destination Groups in the current project run: + + $ gcloud beta iap tcp dest-groups list + + To list all Destination Groups in region REGION in the current project run: + + $ gcloud beta iap tcp dest-groups list --region=REGION + + To limit the results returned by the server to be at most PAGE_SIZE, run: + + $ gcloud beta iap tcp dest-groups list --page-size=PAGE_SIZE + + To list at most 5 Destination Groups sorted alphabetically by project ID, + run: + + $ gcloud beta iap tcp dest-groups list --sort-by=projectId --limit=5 + + To list all Destination Groups in the project PROJECT run: + + $ gcloud beta iap tcp dest-groups list --project=PROJECT + + To list all Destination Groups that have cidr CIDR run: + + $ gcloud beta iap tcp dest-groups list --filter="cidrs=CIDR" + + To list all Destination Groups that have FQDN FQDN run: + + $ gcloud beta iap tcp dest-groups list --filter="fqdns=FQDN" + + To list all Destination Groups that have name NAME run: + + $ gcloud beta iap tcp dest-groups list --filter="name=NAME" + +FLAGS + --region=REGION; default="-" + Region of the Destination Group, will list all regions by default + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iap tcp dest-groups list + diff --git a/gcloud/beta/iap/tcp/dest-groups/remove-iam-policy-binding b/gcloud/beta/iap/tcp/dest-groups/remove-iam-policy-binding new file mode 100644 index 000000000..ad9ffe455 --- /dev/null +++ b/gcloud/beta/iap/tcp/dest-groups/remove-iam-policy-binding @@ -0,0 +1,144 @@ +NAME + gcloud beta iap tcp dest-groups remove-iam-policy-binding - remove IAM + policy binding from an IAP TCP Destination Group resource + +SYNOPSIS + gcloud beta iap tcp dest-groups remove-iam-policy-binding + --group-name=GROUP_NAME --member=PRINCIPAL --region=REGION --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Removes a policy binding from the IAM policy of an IAP TCP + Destination Group resource. One binding consists of a member, a role and an + optional condition. + +EXAMPLES + To remove an IAM policy binding for the role of + 'roles/iap.tunnelResourceAccessor' for the user 'test-user@gmail.com' in + the group 'my-group' located in the region 'us-west1', run: + + $ gcloud beta iap tcp dest-groups remove-iam-policy-binding \ + --member='user:test-user@gmail.com' \ + --role='roles/iap.tunnelResourceAccessor' \ + --group-name='my-group' --region='us-west1' + + To remove an IAM policy binding for the role of + 'roles/iap.tunnelResourceAccessor' from all authenticated users in the + group 'my-group' located in the region 'us-west1', run: + + $ gcloud beta iap tcp dest-groups remove-iam-policy-binding \ + --member='allAuthenticatedUsers' \ + --role='roles/iap.tunnelResourceAccessor' \ + --group-name='my-group' --region='us-west1' + + To remove an IAM policy binding which expires at the end of the year 2018 + for the role of 'roles/iap.tunnelResourceAccessor' for the user + 'test-user@gmail.com' in the group 'my-group' located in the region + 'us-west1', run: + + $ gcloud beta iap tcp dest-groups remove-iam-policy-binding \ + --member='user:test-user@gmail.com' \ + --role='roles/iap.tunnelResourceAccessor' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018, + description=Expires at midnight on 2018-12-31' \ + --group-name='my-group' --region='us-west1' + + To remove all IAM policy bindings regardless of the condition for the role + of 'roles/iap.tunnelResourceAccessor' and for the user + 'test-user@gmail.com' in the group 'my-group' located in the region + 'us-west1', run: + + $ gcloud beta iap tcp dest-groups remove-iam-policy-binding \ + --member='user:test-user@gmail.com' \ + --role='roles/iap.tunnelResourceAccessor' \ + --group-name='my-group' --region='us-west1' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +REQUIRED FLAGS + --group-name=GROUP_NAME + Name of the Destination Group. + + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --region=REGION + Region of the Destination Group. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iap tcp dest-groups remove-iam-policy-binding + diff --git a/gcloud/beta/iap/tcp/dest-groups/set-iam-policy b/gcloud/beta/iap/tcp/dest-groups/set-iam-policy new file mode 100644 index 000000000..1363339f4 --- /dev/null +++ b/gcloud/beta/iap/tcp/dest-groups/set-iam-policy @@ -0,0 +1,57 @@ +NAME + gcloud beta iap tcp dest-groups set-iam-policy - set the IAM policy for an + IAP TCP Destination Group resource + +SYNOPSIS + gcloud beta iap tcp dest-groups set-iam-policy POLICY_FILE + --group-name=GROUP_NAME --region=REGION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command replaces the existing IAM policy for an IAP TCP + Destination Group resource, given a file encoded in JSON or YAML that + contains the IAM policy. If the given policy file specifies an "etag" + value, then the replacement will succeed only if the policy already in + place matches that etag. (An etag obtained via $ gcloud beta iap tcp + dest-groups get-iam-policy will prevent the replacement if the policy for + the resource has been subsequently updated.) A policy file that does not + contain an etag value will replace any existing policy for the resource. + +EXAMPLES + To set the IAM policy for the TCP Destination Group resource within the + active project in the group 'my-group' located in the region 'us-west1', + run: + + $ gcloud beta iap tcp dest-groups set-iam-policy POLICY_FILE \ + --group-name='my-group' --region='us-west1' + + To set the IAM policy for the TCP Destination Group resource within project + PROJECT_ID in the group 'my-group' located in the region 'us-west1', run: + + $ gcloud beta iap tcp dest-groups set-iam-policy POLICY_FILE \ + --project=PROJECT_ID --group-name='my-group' --region='us-west1' + +POSITIONAL ARGUMENTS + POLICY_FILE + JSON or YAML file containing the IAM policy. + +REQUIRED FLAGS + --group-name=GROUP_NAME + Name of the Destination Group. + + --region=REGION + Region of the Destination Group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iap tcp dest-groups set-iam-policy + diff --git a/gcloud/beta/iap/tcp/dest-groups/update b/gcloud/beta/iap/tcp/dest-groups/update new file mode 100644 index 000000000..1ec9610db --- /dev/null +++ b/gcloud/beta/iap/tcp/dest-groups/update @@ -0,0 +1,74 @@ +NAME + gcloud beta iap tcp dest-groups update - update the IAP TCP Destination + Group resource + +SYNOPSIS + gcloud beta iap tcp dest-groups update GROUP_NAME --region=REGION + (--fqdn-list=FQDN_LIST --ip-range-list=IP_RANGE_LIST) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the IAP TCP Destination Group resource. + +EXAMPLES + To update a DestGroup with name GROUP_NAME, in region REGION with ip ranges + CIDR1, CIDR2 in the current project run: + + $ gcloud beta iap tcp dest-groups update DEST_GROUP_NAME \ + --region=REGION --ip-range-list=CIDR1,CIDR2 + + To update a DestGroup with name GROUP_NAME, in region REGION with fqdns + FQDN1, FQDN2 in the current project run: + + $ gcloud beta iap tcp dest-groups update DEST_GROUP_NAME \ + --region=REGION --fqdn-list=FQDN1,FQDN2 + + To update a DestGroup with name GROUP_NAME, in region REGION with fqdns + FQDN1, FQDN2 and ip ranges CIDR1, CIDR2 in the project PROJECT_ID run: + + $ gcloud beta iap tcp dest-groups update DEST_GROUP_NAME \ + --region=REGION --fqdn-list=FQDN1,FQDN2 \ + --ip-range-list=CIDR1,CIDR2 --project=PROJECT_ID + + To clear the fqdn list in a DestGroup with name GROUP_NAME, in region + REGION in the current project run: + + $ gcloud beta iap tcp dest-groups update DEST_GROUP_NAME \ + --region=REGION --fqdn-list="" + + To clear the ip range list in a DestGroup with name GROUP_NAME, in region + REGION in the current project run: + + $ gcloud beta iap tcp dest-groups update DEST_GROUP_NAME \ + --region=REGION --ip-range-list="" + +POSITIONAL ARGUMENTS + GROUP_NAME + Name of the Destination Group. + +REQUIRED FLAGS + --region=REGION + Region of the Destination Group. + + At least one of these must be specified: + + --fqdn-list=FQDN_LIST + List of FQDNs in the Destination Group. + + --ip-range-list=IP_RANGE_LIST + List of ip-ranges in the Destination Group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iap tcp dest-groups update + diff --git a/gcloud/beta/iap/tcp/help b/gcloud/beta/iap/tcp/help new file mode 100644 index 000000000..4c0e2cfe9 --- /dev/null +++ b/gcloud/beta/iap/tcp/help @@ -0,0 +1,26 @@ +NAME + gcloud beta iap tcp - manage IAP TCP resources + +SYNOPSIS + gcloud beta iap tcp GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage IAP TCP resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + dest-groups + (BETA) Manage IAP TCP Destination Group resources. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iap tcp + diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 217753186..17eed14aa 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -24,8 +24,8 @@ SYNOPSIS [--[no-]allow-unauthenticated --breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-throttling --execution-environment=EXECUTION_ENVIRONMENT - --revision-suffix=REVISION_SUFFIX --vpc-connector=VPC_CONNECTOR - --vpc-egress=VPC_EGRESS + --revision-suffix=REVISION_SUFFIX --[no-]session-affinity + --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -393,6 +393,11 @@ FLAGS [--revision-suffix=v1] for a service named 'helloworld', would lead to a revision named 'helloworld-v1'. + --[no-]session-affinity + Whether to enable session affinity for connections to the service. + Use --session-affinity to enable and --no-session-affinity to + disable. + --vpc-connector=VPC_CONNECTOR Set a VPC connector for this resource. diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index ccae6be16..a609f98e2 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -13,8 +13,8 @@ SYNOPSIS [--no-traffic] [--[no-]use-http2] [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-throttling --execution-environment=EXECUTION_ENVIRONMENT - --revision-suffix=REVISION_SUFFIX --vpc-connector=VPC_CONNECTOR - --vpc-egress=VPC_EGRESS + --revision-suffix=REVISION_SUFFIX --[no-]session-affinity + --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -229,6 +229,11 @@ FLAGS [--revision-suffix=v1] for a service named 'helloworld', would lead to a revision named 'helloworld-v1'. + --[no-]session-affinity + Whether to enable session affinity for connections to the service. + Use --session-affinity to enable and --no-session-affinity to + disable. + --vpc-connector=VPC_CONNECTOR Set a VPC connector for this resource. diff --git a/gcloud/beta/sql/generate-login-token b/gcloud/beta/sql/generate-login-token new file mode 100644 index 000000000..9cf8ff13c --- /dev/null +++ b/gcloud/beta/sql/generate-login-token @@ -0,0 +1,56 @@ +NAME + gcloud beta sql generate-login-token - generate an IAM login token for + Cloud SQL + +SYNOPSIS + gcloud beta sql generate-login-token [--application-default-credential] + [--instance=INSTANCE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta sql generate-login-token generates an IAM token to use + for logging in to Cloud SQL instances. + +EXAMPLES + To generate an IAM login token using gcloud credentials, run: + + $ gcloud beta sql generate-login-token + + To generate an IAM login token using application default credentials, run: + + $ gcloud beta sql generate-login-token \ + --application-default-credential + + To generate an IAM login token using gcloud credentials for instance + my-instance, run: + + $ gcloud beta sql generate-login-token --instance=my-instance + + To generate an IAM login token using application default credentials for + instance my-instance, run: + + $ gcloud beta sql generate-login-token --instance=my-instance \ + --application-default-credential + +FLAGS + --application-default-credential + Use application default credentials to generate the login token. + + --instance=INSTANCE + Cloud SQL instance ID. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud sql generate-login-token + + $ gcloud alpha sql generate-login-token + diff --git a/gcloud/beta/sql/help b/gcloud/beta/sql/help index f987d381c..3c9ec4b07 100644 --- a/gcloud/beta/sql/help +++ b/gcloud/beta/sql/help @@ -65,6 +65,9 @@ COMMANDS connect (BETA) Connects to a Cloud SQL instance. + generate-login-token + (BETA) Generate an IAM login token for Cloud SQL. + reschedule-maintenance (BETA) Reschedule a Cloud SQL instance's maintenance. diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index 7f68ded63..663e81e56 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -183,7 +183,8 @@ FLAGS --enable-password-policy Enable the password policy, which enforces user password management - with the policies configured for the instance. + with the policies configured for the instance. This flag is only + available for Postgres. --enable-point-in-time-recovery Allows for data recovery from a specific point in time, down to a @@ -271,8 +272,8 @@ FLAGS --network=projects/testproject/global/networks/testsharednetwork --password-policy-complexity=PASSWORD_POLICY_COMPLEXITY - The complexity of the password. PASSWORD_POLICY_COMPLEXITY must be one - of: + The complexity of the password. This flag is available only for + PostgreSQL. PASSWORD_POLICY_COMPLEXITY must be one of: COMPLEXITY_DEFAULT A combination of lowercase, uppercase, numeric, and @@ -282,21 +283,24 @@ FLAGS implies that complexity check is not enabled. --[no-]password-policy-disallow-username-substring - Disallow username as a part of the password. Use - --password-policy-disallow-username-substring to enable and - --no-password-policy-disallow-username-substring to disable. + Disallow username as a part of the password. This flag is available + only for PostgreSQL. Use --password-policy-disallow-username-substring + to enable and --no-password-policy-disallow-username-substring to + disable. --password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH - Minimum number of characters allowed in the password. + Minimum number of characters allowed in the password. This flag is + available only for PostgreSQL. --password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL Minimum interval after which the password can be changed, for example, 2m for 2 minutes. See - $ gcloud topic datetimes for information on duration formats. + $ gcloud topic datetimes for information on duration formats. This + flag is available only for PostgreSQL. --password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL Number of previous passwords that cannot be reused. The valid range is - between 0 and 100. + 0 to 100. This flag is available only for PostgreSQL. --replica-type=REPLICA_TYPE The type of replica to create. REPLICA_TYPE must be one of: READ, diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index 423cbb061..e7d2533d4 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -97,7 +97,8 @@ FLAGS Provides no failover capability. This is the default. --clear-password-policy - Clear the existing password policy. + Clear the existing password policy. This flag is only available for + Postgres. --cpu=CPU Whole number value indicating how many cores are desired in the @@ -135,7 +136,8 @@ FLAGS --enable-password-policy Enable the password policy, which enforces user password management - with the policies configured for the instance. + with the policies configured for the instance. This flag is only + available for Postgres. --enable-point-in-time-recovery Allows for data recovery from a specific point in time, down to a @@ -218,8 +220,8 @@ FLAGS --network=projects/testproject/global/networks/testsharednetwork --password-policy-complexity=PASSWORD_POLICY_COMPLEXITY - The complexity of the password. PASSWORD_POLICY_COMPLEXITY must be one - of: + The complexity of the password. This flag is available only for + PostgreSQL. PASSWORD_POLICY_COMPLEXITY must be one of: COMPLEXITY_DEFAULT A combination of lowercase, uppercase, numeric, and @@ -229,21 +231,24 @@ FLAGS implies that complexity check is not enabled. --[no-]password-policy-disallow-username-substring - Disallow username as a part of the password. Use - --password-policy-disallow-username-substring to enable and - --no-password-policy-disallow-username-substring to disable. + Disallow username as a part of the password. This flag is available + only for PostgreSQL. Use --password-policy-disallow-username-substring + to enable and --no-password-policy-disallow-username-substring to + disable. --password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH - Minimum number of characters allowed in the password. + Minimum number of characters allowed in the password. This flag is + available only for PostgreSQL. --password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL Minimum interval after which the password can be changed, for example, 2m for 2 minutes. See - $ gcloud topic datetimes for information on duration formats. + $ gcloud topic datetimes for information on duration formats. This + flag is available only for PostgreSQL. --password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL Number of previous passwords that cannot be reused. The valid range is - between 0 and 100. + 0 to 100. This flag is available only for PostgreSQL. --pricing-plan=PRICING_PLAN, -p PRICING_PLAN First Generation instances only. The pricing plan for this instance. diff --git a/gcloud/beta/sql/users/create b/gcloud/beta/sql/users/create index 011296520..d0cd72efe 100644 --- a/gcloud/beta/sql/users/create +++ b/gcloud/beta/sql/users/create @@ -40,16 +40,18 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. + This flag is currently not available. --[no-]password-policy-enable-failed-attempts-check - Enables the failed login attempts check if set to true. Use + Enables the failed login attempts check if set to true. This flag is + currently not available. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION Expiration duration after a password is updated, for example, 2m for 2 minutes. See gcloud topic datetimes for information on duration - formats. + formats. This flag is currently not available. --type=TYPE Cloud SQL user's type. It determines the method to authenticate the diff --git a/gcloud/beta/sql/users/set-password-policy b/gcloud/beta/sql/users/set-password-policy index 1203b2715..ff2e438f9 100644 --- a/gcloud/beta/sql/users/set-password-policy +++ b/gcloud/beta/sql/users/set-password-policy @@ -42,7 +42,8 @@ OPTIONAL FLAGS complete. --clear-password-policy - Clear the existing password policy. + Clear the existing password policy. This flag is only available for + Postgres. --host=HOST Cloud SQL user's host name expressed as a specific IP address or @@ -55,16 +56,18 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. + This flag is currently not available. --[no-]password-policy-enable-failed-attempts-check - Enables the failed login attempts check if set to true. Use + Enables the failed login attempts check if set to true. This flag is + currently not available. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION Expiration duration after a password is updated, for example, 2m for 2 minutes. See gcloud topic datetimes for information on duration - formats. + formats. This flag is currently not available. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/composer/environments/create b/gcloud/composer/environments/create index 150cc5441..712267f6c 100644 --- a/gcloud/composer/environments/create +++ b/gcloud/composer/environments/create @@ -22,8 +22,11 @@ SYNOPSIS --web-server-ipv4-cidr=WEB_SERVER_IPV4_CIDR] [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR --cluster-secondary-range-name=CLUSTER_SECONDARY_RANGE_NAME - --enable-ip-alias --services-ipv4-cidr=SERVICES_IPV4_CIDR + --enable-ip-alias --enable-ip-masq-agent + --services-ipv4-cidr=SERVICES_IPV4_CIDR --services-secondary-range-name=SERVICES_SECONDARY_RANGE_NAME] + [--enable-master-authorized-networks + --master-authorized-networks=[NETWORK,...]] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [--maintenance-window-end=MAINTENANCE_WINDOW_END @@ -286,6 +289,16 @@ FLAGS will require at least two secondary ranges in the subnetwork, one for the pod IPs and another to reserve space for the services range. + --enable-ip-masq-agent + When enabled, the IP Masquarade Agent + (https://cloud.google.com/composer/docs/enable-ip-masquerade-agent) + is deployed to your environment's cluster. It performs many-to-one IP + address translations to hide a pod's IP address behind the cluster + node's IP address. This is done when sending traffic to destinations + outside the cluster's pod CIDR range. + + Cannot be specified unless --enable-ip-alias is also specified. + --services-ipv4-cidr=SERVICES_IPV4_CIDR IP range for the services IPs. @@ -304,6 +317,20 @@ FLAGS Cannot be specified unless --enable-ip-alias is also specified. + Master Authorized Networks configuration + + --enable-master-authorized-networks + Enable Master Authorized Networks feature + (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks/) + in the Composer Environment's GKE cluster. + + --master-authorized-networks=[NETWORK,...] + Comma separated Master Authorized Networks specified in CIDR + notation. + + Cannot be specified unless --enable-master-authorized-networks is + also specified. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the environment. The 'Cloud Composer Service Agent' service account must hold permission 'Cloud KMS CryptoKey diff --git a/gcloud/composer/environments/update b/gcloud/composer/environments/update index 698427f75..c3fc3ed38 100644 --- a/gcloud/composer/environments/update +++ b/gcloud/composer/environments/update @@ -7,6 +7,9 @@ SYNOPSIS (--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE | --environment-size=ENVIRONMENT_SIZE | --node-count=NODE_COUNT | --web-server-machine-type=WEB_SERVER_MACHINE_TYPE + | --disable-master-authorized-networks + --enable-master-authorized-networks + --master-authorized-networks=[NETWORK,...] | --max-workers=MAX_WORKERS --min-workers=MIN_WORKERS --scheduler-count=SCHEDULER_COUNT --scheduler-cpu=SCHEDULER_CPU --scheduler-memory=SCHEDULER_MEMORY @@ -86,6 +89,25 @@ REQUIRED FLAGS machine types is available here: https://cloud.google.com/composer/pricing. + Group of arguments for setting master authorized networks configuration. + + --disable-master-authorized-networks + Disable Master Authorized Networks feature + (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks/) + in the Composer Environment's GKE cluster. + + --enable-master-authorized-networks + Enable Master Authorized Networks feature + (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks/) + in the Composer Environment's GKE cluster. + + --master-authorized-networks=[NETWORK,...] + Comma separated Master Authorized Networks specified in CIDR + notation. + + Cannot be specified unless --enable-master-authorized-networks is + also specified. + Group of arguments for setting workloads configuration in Composer 2.X or greater (--scheduler-count flag is available for Composer 1.X as well). diff --git a/gcloud/compute/backend-services/create b/gcloud/compute/backend-services/create index 5ce46d620..c462d2dff 100644 --- a/gcloud/compute/backend-services/create +++ b/gcloud/compute/backend-services/create @@ -314,7 +314,7 @@ FLAGS service. The value of the field must be a float in the range [0, 1]. This configures the sampling rate of requests to the load balancer where 1.0 means all logged requests are reported and 0.0 means no - logged requests are reported. The default value is 1.0. + logged requests are reported. The default value is 0.0. --max-ttl=MAX_TTL Specifies the maximum allowed TTL for cached content served by this diff --git a/gcloud/compute/backend-services/update b/gcloud/compute/backend-services/update index d0bf51911..68fb86dca 100644 --- a/gcloud/compute/backend-services/update +++ b/gcloud/compute/backend-services/update @@ -222,7 +222,7 @@ FLAGS service. The value of the field must be a float in the range [0, 1]. This configures the sampling rate of requests to the load balancer where 1.0 means all logged requests are reported and 0.0 means no - logged requests are reported. The default value is 1.0. + logged requests are reported. The default value is 0.0. --port-name=PORT_NAME Backend services for external HTTP(S) load balancing, internal HTTP(S) diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index 95aff9c1e..aa5d81f1f 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -380,7 +380,7 @@ FLAGS --maintenance-policy=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/compute/instance-templates/create-with-container b/gcloud/compute/instance-templates/create-with-container index f388541b7..72c34246e 100644 --- a/gcloud/compute/instance-templates/create-with-container +++ b/gcloud/compute/instance-templates/create-with-container @@ -375,7 +375,7 @@ FLAGS --maintenance-policy=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index 7908e6b5b..7cd11748c 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -764,7 +764,7 @@ OPTIONAL FLAGS (DEPRECATED) Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. The --maintenance-policy flag is now deprecated. Please use --on-host-maintenance instead. MAINTENANCE_POLICY must be one of: @@ -779,7 +779,7 @@ OPTIONAL FLAGS --on-host-maintenance=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index dd097dcea..4e51102f3 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -445,7 +445,7 @@ FLAGS --maintenance-policy=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index 9c4c19bc4..326f7d265 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -417,7 +417,7 @@ FLAGS --maintenance-policy=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/compute/instances/set-scheduling b/gcloud/compute/instances/set-scheduling index e867b1c05..5aca468f8 100644 --- a/gcloud/compute/instances/set-scheduling +++ b/gcloud/compute/instances/set-scheduling @@ -40,7 +40,7 @@ FLAGS --maintenance-policy=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see - https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options. + https://cloud.google.com/compute/docs/instances/host-maintenance-options. MAINTENANCE_POLICY must be one of: MIGRATE diff --git a/gcloud/compute/networks/create b/gcloud/compute/networks/create index 2a798b322..442251db0 100644 --- a/gcloud/compute/networks/create +++ b/gcloud/compute/networks/create @@ -68,9 +68,9 @@ FLAGS --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet - that can be transmitted on this network. Default value is 1460 bytes, - and the maximum is 1500 bytes. The MTU advertised via DHCP to all - instances attached to this network. + that can be transmitted on this network. Default value is 1460 bytes. + The minimum value is 1300 bytes and the maximum value is 8896 bytes. + The MTU advertised via DHCP to all instances attached to this network. --network-firewall-policy-enforcement-order=NETWORK_FIREWALL_POLICY_ENFORCEMENT_ORDER The Network Firewall Policy enforcement order of this network. If not diff --git a/gcloud/compute/networks/update b/gcloud/compute/networks/update index 1d556e702..b0fcb4c83 100644 --- a/gcloud/compute/networks/update +++ b/gcloud/compute/networks/update @@ -50,9 +50,9 @@ FLAGS --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet - that can be transmitted on this network. Default value is 1460 bytes, - and the maximum is 1500 bytes. The MTU advertised via DHCP to all - instances attached to this network. + that can be transmitted on this network. Default value is 1460 bytes. + The minimum value is 1300 bytes and the maximum value is 8896 bytes. + The MTU advertised via DHCP to all instances attached to this network. --network-firewall-policy-enforcement-order=NETWORK_FIREWALL_POLICY_ENFORCEMENT_ORDER The Network Firewall Policy enforcement order of this network. If not diff --git a/gcloud/compute/target-https-proxies/create b/gcloud/compute/target-https-proxies/create index 9a3343cc9..efea6991e 100644 --- a/gcloud/compute/target-https-proxies/create +++ b/gcloud/compute/target-https-proxies/create @@ -2,11 +2,11 @@ NAME gcloud compute target-https-proxies create - create a target HTTPS proxy SYNOPSIS - gcloud compute target-https-proxies create NAME - --ssl-certificates=SSL_CERTIFICATE,[...] --url-map=URL_MAP + gcloud compute target-https-proxies create NAME --url-map=URL_MAP [--description=DESCRIPTION] [--quic-override=QUIC_OVERRIDE; default="NONE"] - [--ssl-policy=SSL_POLICY] [--global | --region=REGION] + [--ssl-certificates=SSL_CERTIFICATE,[...]] [--ssl-policy=SSL_POLICY] + [--global | --region=REGION] [--global-ssl-certificates | --ssl-certificates-region=SSL_CERTIFICATES_REGION] [--global-url-map | --url-map-region=URL_MAP_REGION] @@ -28,12 +28,12 @@ EXAMPLES pointing to this map by running: $ gcloud compute target-https-proxies create PROXY_NAME \ - --url-map=URL_MAP --ssl-certificates=SSL_CERTIFIFCATE + --url-map=URL_MAP --ssl-certificates=SSL_CERTIFICATE Create a regional target HTTPS proxy by running: $ gcloud compute target-https-proxies create PROXY_NAME \ - --url-map=URL_MAP --ssl-certificates=SSL_CERTIFIFCATE \ + --url-map=URL_MAP --ssl-certificates=SSL_CERTIFICATE \ --region=REGION_NAME POSITIONAL ARGUMENTS @@ -41,13 +41,6 @@ POSITIONAL ARGUMENTS Name of the target HTTPS proxy to create. REQUIRED FLAGS - --ssl-certificates=SSL_CERTIFICATE,[...] - References to at most 15 SSL certificate resources that are used for - server-side authentication. The first SSL certificate in this list is - considered the primary SSL certificate associated with the load - balancer. The SSL certificates must exist and cannot be deleted while - referenced by a target HTTPS proxy. - --url-map=URL_MAP A reference to a URL map resource. A URL map defines the mapping of URLs to backend services. Before you can refer to a URL map, you must @@ -71,6 +64,13 @@ OPTIONAL FLAGS NONE Allows Google to control when QUIC is rolled out. + --ssl-certificates=SSL_CERTIFICATE,[...] + References to at most 15 SSL certificate resources that are used for + server-side authentication. The first SSL certificate in this list is + considered the primary SSL certificate associated with the load + balancer. The SSL certificates must exist and cannot be deleted while + referenced by a target HTTPS proxy. + --ssl-policy=SSL_POLICY A reference to an SSL policy resource that defines the server-side support for SSL features and affects the connections between clients diff --git a/gcloud/config/get b/gcloud/config/get index 792b31db6..c354b1ad9 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -447,7 +447,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -487,39 +487,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/config/help b/gcloud/config/help index ea3ee89d9..90bf15b66 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -479,7 +479,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -519,39 +519,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/config/list b/gcloud/config/list index 8a8fbb17b..24924a755 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -481,7 +481,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -521,39 +521,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/config/set b/gcloud/config/set index 6db98f838..1e3288561 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -49,7 +49,7 @@ EXAMPLES $ gcloud config set proxy/port 8080 For a full list of accepted values, see the Google Cloud CLI properties - page: https://cloud.google.com/sdk/docs/properties + page: https://cloud.google.com/sdk/docs/properties. POSITIONAL ARGUMENTS SECTION/PROPERTY @@ -494,7 +494,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -534,39 +534,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/config/unset b/gcloud/config/unset index 3c793e3ae..bbae70a10 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -455,7 +455,7 @@ AVAILABLE PROPERTIES promote_by_default If True, when deploying a new version of a service, that version will be promoted to receive all traffic for the service. This - property can be overridden via the --promote-by-default or + property can be overridden with the --promote-by-default or --no-promote-by-default flags. stop_previous_version @@ -495,39 +495,35 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - While set, all API requests will be - made as the given service account or target service account in an - impersonation delegation chain instead of the currently selected - account. You can specify either a single service account as the - impersonator, or a comma-separated list of service accounts to - create an impersonation delegation chain. This is done without - needing to create, download, and activate a key for the service - account or accounts. + While set, all API requests will be made as the given service + account or target service account in an impersonation delegation + chain instead of the currently selected account. You can specify + either a single service account as the impersonator, or a + comma-separated list of service accounts to create an impersonation + delegation chain. This is done without needing to create, download, + or activate a key for the service account or accounts. - In order to make API requests as a service account, your - currently selected account must have an IAM role that includes - the `iam.serviceAccounts.getAccessToken` permission for the - service account or accounts. + In order to make API requests as a service account, your currently + selected account must have an IAM role that includes the + iam.serviceAccounts.getAccessToken permission for the service + account or accounts. - The `roles/iam.serviceAccountTokenCreator` role has - the `iam.serviceAccounts.getAccessToken permission`. You can - also create a custom role. + The roles/iam.serviceAccountTokenCreator role has the + iam.serviceAccounts.getAccessToken permission. You can also create + a custom role. - You can specify a list of service accounts, separated with - commas. This creates an impersonation delegation chain in which - each service account delegates its permissions to the next - service account in the chain. Each service account in the list - must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when the property is set - via `gcloud config set auth/impersonate-service-account=` - `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, - the active account must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_1_`, which must have the - `roles/iam.serviceAccountTokenCreator` role on - `_SERVICE_ACCOUNT_2_`. - `_SERVICE_ACCOUNT_1_` is the impersonated service - account and `_SERVICE_ACCOUNT_2_` is the delegate. + You can specify a list of service accounts, separated with commas. + This creates an impersonation delegation chain in which each + service account delegates its permissions to the next service + account in the chain. Each service account in the list must have + the roles/iam.serviceAccountTokenCreator role on the next service + account in the list. For example, when the property is set through + gcloud config set auth/impersonate_service_account= + SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have + the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1, + which must have the roles/iam.serviceAccountTokenCreator role on + SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service + account and SERVICE_ACCOUNT_2 is the delegate. token_host Overrides the token endpoint to provision access tokens. It can be diff --git a/gcloud/container/aws/node-pools/update b/gcloud/container/aws/node-pools/update index 2e49f9c13..1dc2c9cde 100644 --- a/gcloud/container/aws/node-pools/update +++ b/gcloud/container/aws/node-pools/update @@ -6,7 +6,8 @@ SYNOPSIS gcloud container aws node-pools update (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] [--config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN] - [--node-version=NODE_VERSION] [--root-volume-iops=ROOT_VOLUME_IOPS] + [--instance-type=INSTANCE_TYPE] [--node-version=NODE_VERSION] + [--root-volume-iops=ROOT_VOLUME_IOPS] [--root-volume-kms-key-arn=ROOT_VOLUME_KMS_KEY_ARN] [--root-volume-size=ROOT_VOLUME_SIZE] [--root-volume-type=ROOT_VOLUME_TYPE] [--validate-only] @@ -71,6 +72,9 @@ FLAGS --config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN Amazon Resource Name (ARN) of the AWS KMS key to encrypt the user data. + --instance-type=INSTANCE_TYPE + AWS EC2 instance type for the node pool's nodes. + --node-version=NODE_VERSION Kubernetes version to use for the node pool. diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 023e57378..c594d5a34 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -303,8 +303,9 @@ FLAGS Size for node VM boot disks in GB. Defaults to 100GB. --disk-type=DISK_TYPE - Type of the node VM boot disk. Defaults to pd-standard. DISK_TYPE must - be one of: pd-standard, pd-ssd, pd-balanced. + Type of the node VM boot disk. For version 1.24.0+, defaults to + pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE + must be one of: pd-standard, pd-ssd, pd-balanced. --enable-autorepair Enable node autorepair feature for a cluster's default node pool(s). diff --git a/gcloud/container/fleet/help b/gcloud/container/fleet/help index eea397ff2..5b6cb7c32 100644 --- a/gcloud/container/fleet/help +++ b/gcloud/container/fleet/help @@ -59,7 +59,7 @@ GROUPS memberships Manage memberships of all your GKE and other Kubernetes cluster with - Fleet. + fleets. mesh Manage Service Mesh Feature. diff --git a/gcloud/container/fleet/identity-service/apply b/gcloud/container/fleet/identity-service/apply index f25f60cdd..22ce18bdf 100644 --- a/gcloud/container/fleet/identity-service/apply +++ b/gcloud/container/fleet/identity-service/apply @@ -18,7 +18,7 @@ EXAMPLES To apply an Identity Service configuration for a membership, run: $ gcloud container fleet identity-service apply \ - --membership=CLUSTER_NAME \ + --membership=MEMBERSHIP_NAME \ --config=/path/to/identity-service.yaml REQUIRED FLAGS diff --git a/gcloud/container/fleet/identity-service/delete b/gcloud/container/fleet/identity-service/delete index f0e1b45b8..3ad481fbe 100644 --- a/gcloud/container/fleet/identity-service/delete +++ b/gcloud/container/fleet/identity-service/delete @@ -13,7 +13,7 @@ EXAMPLES To delete an Identity Service configuration for a membership, run: $ gcloud container fleet identity-service delete \ - --membership=CLUSTER_NAME + --membership=MEMBERSHIP_NAME FLAGS --membership=MEMBERSHIP diff --git a/gcloud/container/fleet/memberships/delete b/gcloud/container/fleet/memberships/delete index 55be6ed26..4362abe89 100644 --- a/gcloud/container/fleet/memberships/delete +++ b/gcloud/container/fleet/memberships/delete @@ -6,7 +6,7 @@ SYNOPSIS (MEMBERSHIP : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command deletes the Fleet membership resource corresponding to the + This command deletes the Fleet Membership resource corresponding to the cluster. This command is intended to delete stale Fleet Membership resources as @@ -22,7 +22,7 @@ EXAMPLES $ gcloud container fleet memberships list - Delete a membership from Fleet: + Delete a membership from the active project's fleet: $ gcloud container fleet memberships delete MEMBERSHIP_NAME diff --git a/gcloud/container/fleet/memberships/get-credentials b/gcloud/container/fleet/memberships/get-credentials index e307fd508..5b65d8530 100644 --- a/gcloud/container/fleet/memberships/get-credentials +++ b/gcloud/container/fleet/memberships/get-credentials @@ -1,6 +1,6 @@ NAME gcloud container fleet memberships get-credentials - fetch credentials for - a Fleet-registered cluster to be used in Connect Gateway + a fleet-registered cluster to be used in Connect Gateway SYNOPSIS gcloud container fleet memberships get-credentials MEMBERSHIP @@ -9,7 +9,7 @@ SYNOPSIS DESCRIPTION gcloud container fleet memberships get-credentials updates the kubeconfig file with the appropriate credentials and endpoint information to send - kubectl commands to a Fleet-registered and connected cluster through + kubectl commands to a fleet-registered and connected cluster through Connect Gateway Service. It takes a project, passed through by set defaults or flags. By default, diff --git a/gcloud/container/fleet/memberships/help b/gcloud/container/fleet/memberships/help index d02d61d47..267f04d1f 100644 --- a/gcloud/container/fleet/memberships/help +++ b/gcloud/container/fleet/memberships/help @@ -1,12 +1,13 @@ NAME gcloud container fleet memberships - manage memberships of all your GKE and - other Kubernetes cluster with Fleet + other Kubernetes cluster with fleets SYNOPSIS gcloud container fleet memberships COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Manage memberships of all your GKE and other Kubernetes cluster with Fleet. + Manage memberships of all your GKE and other Kubernetes cluster with + fleets. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -23,14 +24,14 @@ COMMANDS Describe a membership. get-credentials - Fetch credentials for a Fleet-registered cluster to be used in Connect + Fetch credentials for a fleet-registered cluster to be used in Connect Gateway. list List memberships. register - Register a cluster with Fleet. + Register a cluster with a fleet. unregister Unregister a cluster from Fleet. diff --git a/gcloud/container/fleet/memberships/list b/gcloud/container/fleet/memberships/list index af0adb5f3..d7d4e819a 100644 --- a/gcloud/container/fleet/memberships/list +++ b/gcloud/container/fleet/memberships/list @@ -7,10 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - List memberships in Fleet. + List memberships in a fleet. EXAMPLES - List memberships in Fleet: + List memberships in the active project's fleet: $ gcloud container fleet memberships list diff --git a/gcloud/container/fleet/memberships/register b/gcloud/container/fleet/memberships/register index 2fe319f77..e333b5750 100644 --- a/gcloud/container/fleet/memberships/register +++ b/gcloud/container/fleet/memberships/register @@ -1,8 +1,9 @@ NAME - gcloud container fleet memberships register - register a cluster with Fleet + gcloud container fleet memberships register - register a cluster with a + fleet SYNOPSIS - gcloud container fleet memberships register CLUSTER_NAME + gcloud container fleet memberships register MEMBERSHIP_NAME (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) (--service-account-key-file=SERVICE_ACCOUNT_KEY_FILE @@ -12,15 +13,15 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command registers a cluster with the Fleet by: + This command registers a cluster with the fleet by: 1. Creating a Fleet Membership resource corresponding to the cluster. 2. Adding in-cluster Kubernetes Resources that make the cluster exclusive - to one Fleet. + to one fleet. 3. Installing the Connect Agent into this cluster. A successful registration implies that the cluster is now exclusive to a - single Fleet. + single fleet. For more information about Connect Agent, go to: https://cloud.google.com/anthos/multicluster-management/connect/overview/ @@ -39,9 +40,9 @@ DESCRIPTION If the cluster is already registered to another Fleet, the registration is not successful. - Rerunning this command against the same cluster with the same CLUSTER_NAME - and target GKEFleet is successful and upgrades the Connect Agent if a new - agent is available. + Rerunning this command against the same cluster with the same + MEMBERSHIP_NAME and target GKEFleet is successful and upgrades the Connect + Agent if a new agent is available. EXAMPLES Register a non-GKE or GKE On-Prem cluster referenced from a specific @@ -116,9 +117,9 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json POSITIONAL ARGUMENTS - CLUSTER_NAME + MEMBERSHIP_NAME The membership name that you choose to uniquely represents the cluster - being registered on the Fleet. + being registered on the fleet. REQUIRED FLAGS Cluster identifier. @@ -170,7 +171,7 @@ REQUIRED FLAGS Workload Identity --enable-workload-identity - Enable Workload Identity when registering the cluster with Fleet. + Enable Workload Identity when registering the cluster with a fleet. Ensure that GKE Workload Identity is enabled on your GKE cluster, it is a requirement for using Workload Identity with memberships. Refer to the Registering a cluster using Workload Identity section diff --git a/gcloud/container/fleet/memberships/unregister b/gcloud/container/fleet/memberships/unregister index 056667294..82e08a852 100644 --- a/gcloud/container/fleet/memberships/unregister +++ b/gcloud/container/fleet/memberships/unregister @@ -3,18 +3,18 @@ NAME Fleet SYNOPSIS - gcloud container fleet memberships unregister CLUSTER_NAME + gcloud container fleet memberships unregister MEMBERSHIP_NAME (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command unregisters a cluster with the Fleet by: + This command unregisters a cluster with the fleet by: 1. Deleting the Fleet Membership resource for this cluster (a.k.a `gcloud container fleet memberships delete`). 2. Removing the corresponding in-cluster Kubernetes Resources that make the - cluster exclusive to one Fleet (a.k.a `kubectl delete memberships + cluster exclusive to one fleet (a.k.a `kubectl delete memberships membership`). 3. Uninstalling the Connect Agent from this cluster (a.k.a `kubectl delete on the gke-connect namespace`). @@ -58,7 +58,7 @@ EXAMPLES --gke-cluster=my-cluster-region-or-zone/my-cluster POSITIONAL ARGUMENTS - CLUSTER_NAME + MEMBERSHIP_NAME The membership name that corresponds to the cluster being unregistered. To get list of all the memberships on the Fleet, consider using the command: gcloud container fleet memberships list. diff --git a/gcloud/container/hub/help b/gcloud/container/hub/help index e0ed94ce1..78743ea04 100644 --- a/gcloud/container/hub/help +++ b/gcloud/container/hub/help @@ -59,7 +59,7 @@ GROUPS memberships Manage memberships of all your GKE and other Kubernetes cluster with - Fleet. + fleets. mesh Manage Service Mesh Feature. diff --git a/gcloud/container/hub/identity-service/apply b/gcloud/container/hub/identity-service/apply index 7ebaf3c24..6237195dd 100644 --- a/gcloud/container/hub/identity-service/apply +++ b/gcloud/container/hub/identity-service/apply @@ -18,7 +18,7 @@ EXAMPLES To apply an Identity Service configuration for a membership, run: $ gcloud container hub identity-service apply \ - --membership=CLUSTER_NAME \ + --membership=MEMBERSHIP_NAME \ --config=/path/to/identity-service.yaml REQUIRED FLAGS diff --git a/gcloud/container/hub/identity-service/delete b/gcloud/container/hub/identity-service/delete index a1b09d50c..874d5af55 100644 --- a/gcloud/container/hub/identity-service/delete +++ b/gcloud/container/hub/identity-service/delete @@ -13,7 +13,7 @@ EXAMPLES To delete an Identity Service configuration for a membership, run: $ gcloud container hub identity-service delete \ - --membership=CLUSTER_NAME + --membership=MEMBERSHIP_NAME FLAGS --membership=MEMBERSHIP diff --git a/gcloud/container/hub/memberships/delete b/gcloud/container/hub/memberships/delete index 0977f19a0..1237ee54c 100644 --- a/gcloud/container/hub/memberships/delete +++ b/gcloud/container/hub/memberships/delete @@ -6,7 +6,7 @@ SYNOPSIS [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command deletes the Fleet membership resource corresponding to the + This command deletes the Fleet Membership resource corresponding to the cluster. This command is intended to delete stale Fleet Membership resources as @@ -22,7 +22,7 @@ EXAMPLES $ gcloud container hub memberships list - Delete a membership from Fleet: + Delete a membership from the active project's fleet: $ gcloud container hub memberships delete MEMBERSHIP_NAME diff --git a/gcloud/container/hub/memberships/get-credentials b/gcloud/container/hub/memberships/get-credentials index 524e3cb12..d4b512a77 100644 --- a/gcloud/container/hub/memberships/get-credentials +++ b/gcloud/container/hub/memberships/get-credentials @@ -1,6 +1,6 @@ NAME gcloud container hub memberships get-credentials - fetch credentials for a - Fleet-registered cluster to be used in Connect Gateway + fleet-registered cluster to be used in Connect Gateway SYNOPSIS gcloud container hub memberships get-credentials MEMBERSHIP @@ -9,7 +9,7 @@ SYNOPSIS DESCRIPTION gcloud container hub memberships get-credentials updates the kubeconfig file with the appropriate credentials and endpoint information to send - kubectl commands to a Fleet-registered and connected cluster through + kubectl commands to a fleet-registered and connected cluster through Connect Gateway Service. It takes a project, passed through by set defaults or flags. By default, diff --git a/gcloud/container/hub/memberships/help b/gcloud/container/hub/memberships/help index 7abf87425..9b4624e9c 100644 --- a/gcloud/container/hub/memberships/help +++ b/gcloud/container/hub/memberships/help @@ -1,12 +1,13 @@ NAME gcloud container hub memberships - manage memberships of all your GKE and - other Kubernetes cluster with Fleet + other Kubernetes cluster with fleets SYNOPSIS gcloud container hub memberships COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Manage memberships of all your GKE and other Kubernetes cluster with Fleet. + Manage memberships of all your GKE and other Kubernetes cluster with + fleets. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -23,14 +24,14 @@ COMMANDS Describe a membership. get-credentials - Fetch credentials for a Fleet-registered cluster to be used in Connect + Fetch credentials for a fleet-registered cluster to be used in Connect Gateway. list List memberships. register - Register a cluster with Fleet. + Register a cluster with a fleet. unregister Unregister a cluster from Fleet. diff --git a/gcloud/container/hub/memberships/list b/gcloud/container/hub/memberships/list index 2189a1214..edbdaadb5 100644 --- a/gcloud/container/hub/memberships/list +++ b/gcloud/container/hub/memberships/list @@ -7,10 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - List memberships in Fleet. + List memberships in a fleet. EXAMPLES - List memberships in Fleet: + List memberships in the active project's fleet: $ gcloud container hub memberships list diff --git a/gcloud/container/hub/memberships/register b/gcloud/container/hub/memberships/register index 4647e0dc9..b36a4e5db 100644 --- a/gcloud/container/hub/memberships/register +++ b/gcloud/container/hub/memberships/register @@ -1,8 +1,8 @@ NAME - gcloud container hub memberships register - register a cluster with Fleet + gcloud container hub memberships register - register a cluster with a fleet SYNOPSIS - gcloud container hub memberships register CLUSTER_NAME + gcloud container hub memberships register MEMBERSHIP_NAME (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) (--service-account-key-file=SERVICE_ACCOUNT_KEY_FILE @@ -12,15 +12,15 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command registers a cluster with the Fleet by: + This command registers a cluster with the fleet by: 1. Creating a Fleet Membership resource corresponding to the cluster. 2. Adding in-cluster Kubernetes Resources that make the cluster exclusive - to one Fleet. + to one fleet. 3. Installing the Connect Agent into this cluster. A successful registration implies that the cluster is now exclusive to a - single Fleet. + single fleet. For more information about Connect Agent, go to: https://cloud.google.com/anthos/multicluster-management/connect/overview/ @@ -39,9 +39,9 @@ DESCRIPTION If the cluster is already registered to another Fleet, the registration is not successful. - Rerunning this command against the same cluster with the same CLUSTER_NAME - and target GKEFleet is successful and upgrades the Connect Agent if a new - agent is available. + Rerunning this command against the same cluster with the same + MEMBERSHIP_NAME and target GKEFleet is successful and upgrades the Connect + Agent if a new agent is available. EXAMPLES Register a non-GKE or GKE On-Prem cluster referenced from a specific @@ -116,9 +116,9 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json POSITIONAL ARGUMENTS - CLUSTER_NAME + MEMBERSHIP_NAME The membership name that you choose to uniquely represents the cluster - being registered on the Fleet. + being registered on the fleet. REQUIRED FLAGS Cluster identifier. @@ -170,7 +170,7 @@ REQUIRED FLAGS Workload Identity --enable-workload-identity - Enable Workload Identity when registering the cluster with Fleet. + Enable Workload Identity when registering the cluster with a fleet. Ensure that GKE Workload Identity is enabled on your GKE cluster, it is a requirement for using Workload Identity with memberships. Refer to the Registering a cluster using Workload Identity section diff --git a/gcloud/container/hub/memberships/unregister b/gcloud/container/hub/memberships/unregister index 09ba9e168..681e1167b 100644 --- a/gcloud/container/hub/memberships/unregister +++ b/gcloud/container/hub/memberships/unregister @@ -3,18 +3,18 @@ NAME Fleet SYNOPSIS - gcloud container hub memberships unregister CLUSTER_NAME + gcloud container hub memberships unregister MEMBERSHIP_NAME (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command unregisters a cluster with the Fleet by: + This command unregisters a cluster with the fleet by: 1. Deleting the Fleet Membership resource for this cluster (a.k.a `gcloud container hub memberships delete`). 2. Removing the corresponding in-cluster Kubernetes Resources that make the - cluster exclusive to one Fleet (a.k.a `kubectl delete memberships + cluster exclusive to one fleet (a.k.a `kubectl delete memberships membership`). 3. Uninstalling the Connect Agent from this cluster (a.k.a `kubectl delete on the gke-connect namespace`). @@ -58,7 +58,7 @@ EXAMPLES --gke-cluster=my-cluster-region-or-zone/my-cluster POSITIONAL ARGUMENTS - CLUSTER_NAME + MEMBERSHIP_NAME The membership name that corresponds to the cluster being unregistered. To get list of all the memberships on the Fleet, consider using the command: gcloud container hub memberships list. diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index a98bdc0c6..66ee96ffb 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -88,8 +88,9 @@ FLAGS Size for node VM boot disks in GB. Defaults to 100GB. --disk-type=DISK_TYPE - Type of the node VM boot disk. Defaults to pd-standard. DISK_TYPE must - be one of: pd-standard, pd-ssd, pd-balanced. + Type of the node VM boot disk. For version 1.24.0+, defaults to + pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE + must be one of: pd-standard, pd-ssd, pd-balanced. --enable-autoprovisioning Enables Cluster Autoscaler to treat the node pool as if it was diff --git a/gcloud/database-migration/connection-profiles/create/cloudsql b/gcloud/database-migration/connection-profiles/create/cloudsql index 51e8c91eb..a173cf5a7 100644 --- a/gcloud/database-migration/connection-profiles/create/cloudsql +++ b/gcloud/database-migration/connection-profiles/create/cloudsql @@ -6,26 +6,34 @@ SYNOPSIS gcloud database-migration connection-profiles create cloudsql (CONNECTION_PROFILE : --region=REGION) --database-version=DATABASE_VERSION --source-id=SOURCE_ID --tier=TIER - [--activation-policy=ACTIVATION_POLICY] + [--activation-policy=ACTIVATION_POLICY] [--no-async] [--authorized-networks=NETWORK,[NETWORK,...]] [--no-auto-storage-increase] [--data-disk-size=DATA_DISK_SIZE] - [--data-disk-type=DATA_DISK_TYPE] [--database-flags=[KEY=VALUE,...]] + [--data-disk-type=DATA_DISK_TYPE] [--database-flags=[FLAG=VALUE,...]] [--display-name=DISPLAY_NAME] [--no-enable-ip-v4] [--labels=[KEY=VALUE,...]] [--private-network=PRIVATE_NETWORK] - [--provider=PROVIDER] [--require-ssl] + [--provider=PROVIDER] [--require-ssl] [--root-password=ROOT_PASSWORD] [--storage-auto-resize-limit=STORAGE_AUTO_RESIZE_LIMIT] [--user-labels=[KEY=VALUE,...]] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Create a Database Migration Service connection profile for Cloud SQL. + Create a Database Migration Service destination connection profile for + Cloud SQL. This will create a Cloud SQL replica. EXAMPLES To create a connection profile for Cloud SQL with database version MySQL 5.6: $ gcloud database-migration connection-profiles create cloudsql \ - CONNECTION_PROFILE --region=us-central1 \ - --display-name=my-profile --database-version=MYSQL_5_6 + my-profile --region=us-central1 --database-version=MYSQL_5_6 \ + --source-id=cp1 --tier=db-n1-standard-1 + + To create a connection profile for Cloud SQL and a Cloud SQL replica with + database version PostgreSQL 10: + + $ gcloud database-migration connection-profiles create cloudsql \ + my-profile --region=us-central1 --database-version=POSTGRES_10 \ + --source-id=cp1 --tier=db-custom-1-3840 --zone=us-central1-a POSITIONAL ARGUMENTS Connection profile resource - The connection profile to create. The @@ -56,10 +64,9 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --database-version=DATABASE_VERSION - Database engine type and version (MYSQL_5_7, MYSQL_5_6, MYSQL_8_0, - POSTGRES_9_6, POSTGRES_10, POSTGRES_11, POSTGRES_12, POSTGRES_13). - DATABASE_VERSION must be one of: MYSQL_5_7, MYSQL_5_6, MYSQL_8_0, - POSTGRES_9_6, POSTGRES_10, POSTGRES_11, POSTGRES_12, POSTGRES_13. + Database engine type and version. DATABASE_VERSION must be one of: + MYSQL_5_7, MYSQL_5_6, MYSQL_8_0, POSTGRES_9_6, POSTGRES_10, + POSTGRES_11, POSTGRES_12, POSTGRES_13, POSTGRES_14. Connection profile resource - Database Migration Service source connection profile ID. This represents a Cloud resource. (NOTE) Some attributes are @@ -82,7 +89,7 @@ REQUIRED FLAGS --tier=TIER Tier (or machine type) for this instance, for example: db-n1-standard-1 - (MySQL instances) of db-custom-1-3840 (PostgreSQL instances). For more + (MySQL instances) or db-custom-1-3840 (PostgreSQL instances). For more information, see Cloud SQL Instance Settings (https://cloud.google.com/sql/docs/mysql/instance-settings). @@ -99,18 +106,20 @@ OPTIONAL FLAGS ACTIVATION_POLICY must be one of: ALWAYS, NEVER. + --no-async + Waits for the operation in progress to complete before returning. + --authorized-networks=NETWORK,[NETWORK,...] - List of external networks that are allowed to connect to the instance - using the IP. See - https://en.wikipedia.org/wiki/CIDR_notation#CIDR_notation, also known - as 'slash' notation (e.g.192.168.100.0/24). + List of external networks that are allowed to connect to the instance. + Specify values in CIDR notation, also known as 'slash' notation + (e.g.192.168.100.0/24). --auto-storage-increase If you enable this setting, Cloud SQL checks your available storage every 30 seconds. If the available storage falls below a threshold size, Cloud SQL automatically adds additional storage capacity. If the available storage repeatedly falls below the threshold size, Cloud SQL - continues to add storage until it reaches the maximum of 30 TB. + continues to add storage until it reaches the maximum of 64 TB. Default: ON. Enabled by default, use --no-auto-storage-increase to disable. @@ -119,16 +128,20 @@ OPTIONAL FLAGS default) size is 10GB. --data-disk-type=DATA_DISK_TYPE - Type of storage: PD_SSD (default) or PD_HDD. DATA_DISK_TYPE must be one - of: PD_SSD, PD_HDD. + Type of storage. DATA_DISK_TYPE must be one of: PD_SSD, PD_HDD. - --database-flags=[KEY=VALUE,...] - Database flags passed to the Cloud SQL instance at startup. An object - containing a list of "key": value pairs. Example: { "name": "wrench", - "mass": "1.3kg", "count": "3" }. + --database-flags=[FLAG=VALUE,...] + Comma-separated list of database flags to set on the instance. Use an + equals sign to separate the flag name and value. Flags without values, + like skip_grant_tables, can be written out without a value, e.g., + skip_grant_tables=. Use on/off values for booleans. View the Instance + Resource API for allowed flags. (e.g., --database-flags + max_allowed_packet=55555 skip_grant_tables=,log_output=1). --display-name=DISPLAY_NAME - Friendly name for the connection profile. + A user-friendly name for the connection profile. The display name can + include letters, numbers, spaces, and hyphens, and must start with a + letter. --enable-ip-v4 Whether the instance should be assigned an IPv4 address or not. Enabled @@ -149,12 +162,15 @@ OPTIONAL FLAGS updated, but it cannot be removed after it is set. --provider=PROVIDER - Database provider (CLOUDSQL or RDS). PROVIDER must be one of: RDS, + Database provider, for managed databases. PROVIDER must be one of: RDS, CLOUDSQL. --require-ssl Whether SSL connections over IP should be enforced or not. + --root-password=ROOT_PASSWORD + Root Cloud SQL user's password. + --storage-auto-resize-limit=STORAGE_AUTO_RESIZE_LIMIT Maximum size to which storage capacity can be automatically increased. The default value is 0, which specifies that there is no limit. diff --git a/gcloud/database-migration/connection-profiles/create/help b/gcloud/database-migration/connection-profiles/create/help index bd3025863..6a0b8a6a7 100644 --- a/gcloud/database-migration/connection-profiles/create/help +++ b/gcloud/database-migration/connection-profiles/create/help @@ -8,6 +8,11 @@ SYNOPSIS DESCRIPTION Commands for creating Database Migration Service connection profiles. + ▪ Create a source connection profile with the mysql or postgresql + commands. + ▪ Create a destination connection profile for a Cloud SQL instance with + the cloudsql command. For Cloud SQL instance as a source, use the + create command for the relevant engine type (e.g. mysql). GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/database-migration/connection-profiles/create/mysql b/gcloud/database-migration/connection-profiles/create/mysql index 2f51a1a8b..392559657 100644 --- a/gcloud/database-migration/connection-profiles/create/mysql +++ b/gcloud/database-migration/connection-profiles/create/mysql @@ -6,8 +6,9 @@ SYNOPSIS gcloud database-migration connection-profiles create mysql (CONNECTION_PROFILE : --region=REGION) --host=HOST --port=PORT --username=USERNAME (--password=PASSWORD | --prompt-for-password) - [--cloudsql-instance=CLOUDSQL_INSTANCE] [--display-name=DISPLAY_NAME] - [--labels=[KEY=VALUE,...]] [--provider=PROVIDER] + [--no-async] [--cloudsql-instance=CLOUDSQL_INSTANCE] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [--provider=PROVIDER] [--ca-certificate=CA_CERTIFICATE : --client-certificate=CLIENT_CERTIFICATE --private-key=PRIVATE_KEY] [GCLOUD_WIDE_FLAG ...] @@ -19,16 +20,15 @@ EXAMPLES To create a connection profile for MySQL: $ gcloud database-migration connection-profiles create mysql \ - CONNECTION_PROFILE --region=us-central1 --password=123456 \ - --username=fakeuser --display-name=my-profile --host=1.2.3.4 \ - --port=1111 + my-profile --region=us-central1 --password=123456 \ + --username=my-user --host=1.2.3.4 --port=3306 If the source is a Cloud SQL database, run: $ gcloud database-migration connection-profiles create mysql \ - CONNECTION_PROFILE --region=us-central1 --password=123456 \ - --username=fakeuser --display-name=my-profile --host=1.2.3.4 \ - --port=1111 --cloudsql-instance=my-instance + my-profile --region=us-central1 --password=123456 \ + --username=my-user --host=1.2.3.4 --port=3306 \ + --cloudsql-instance=my-instance --provider=CLOUDSQL POSITIONAL ARGUMENTS Connection profile resource - The connection profile to create. The @@ -65,27 +65,32 @@ REQUIRED FLAGS Network port of the source database. --username=USERNAME - Username that Database Migration Service will use to connect to the - database. The value is encrypted when stored in Database Migration - Service. + Username that Database Migration Service uses to connect to the + database. Database Migration Service encrypts the value when storing + it. Exactly one of these must be specified: --password=PASSWORD - Password for the user that Database Migration Service will be using - to connect to the database. This field is not returned on request, - and the value is encrypted when stored in Database Migration Service. + Password for the user that Database Migration Service uses to connect + to the source database. Database Migration Service encrypts the value + when storing it, and the field is not returned on request. --prompt-for-password Prompt for the password used to connect to the database. OPTIONAL FLAGS + --no-async + Waits for the operation in progress to complete before returning. + --cloudsql-instance=CLOUDSQL_INSTANCE If the source is a Cloud SQL database, use this field to provide the Cloud SQL instance ID of the source. --display-name=DISPLAY_NAME - Friendly name for the connection profile. + A user-friendly name for the connection profile. The display name can + include letters, numbers, spaces, and hyphens, and must start with a + letter. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. @@ -96,21 +101,24 @@ OPTIONAL FLAGS numbers. --provider=PROVIDER - Database provider (CLOUDSQL or RDS). PROVIDER must be one of: RDS, + Database provider, for managed databases. PROVIDER must be one of: RDS, CLOUDSQL. --ca-certificate=CA_CERTIFICATE x509 PEM-encoded certificate of the CA that signed the source database server's certificate. The replica will use this certificate to verify - it's connecting to the right host. + it's connecting to the correct host. Database Migration Service + encrypts the value when storing it. --client-certificate=CLIENT_CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to - authenticate against the source database server. + authenticate against the source database server. Database Migration + Service encrypts the value when storing it. --private-key=PRIVATE_KEY Unencrypted PKCS#1 or PKCS#8 PEM-encoded private key associated with - the Client Certificate. + the Client Certificate. Database Migration Service encrypts the value + when storing it. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/database-migration/connection-profiles/create/postgresql b/gcloud/database-migration/connection-profiles/create/postgresql index d43df7dc8..aaac09180 100644 --- a/gcloud/database-migration/connection-profiles/create/postgresql +++ b/gcloud/database-migration/connection-profiles/create/postgresql @@ -6,8 +6,8 @@ SYNOPSIS gcloud database-migration connection-profiles create postgresql (CONNECTION_PROFILE : --region=REGION) --host=HOST --port=PORT --username=USERNAME (--password=PASSWORD | --prompt-for-password) - [--cloudsql-instance=CLOUDSQL_INSTANCE] [--display-name=DISPLAY_NAME] - [--labels=[KEY=VALUE,...]] + [--no-async] [--cloudsql-instance=CLOUDSQL_INSTANCE] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--ca-certificate=CA_CERTIFICATE : --client-certificate=CLIENT_CERTIFICATE --private-key=PRIVATE_KEY] [GCLOUD_WIDE_FLAG ...] @@ -19,16 +19,15 @@ EXAMPLES To create a connection profile for PostgreSQL: $ gcloud database-migration connection-profiles create postgresql \ - CONNECTION_PROFILE --region=us-central1 --password=123456 \ - --username=fakeuser --display-name=my-profile --host=1.2.3.4 \ - --port=1111 + my-profile --region=us-central1 --password=123456 \ + --username=my-user --host=1.2.3.4 --port=5432 If the source is a Cloud SQL database, run: $ gcloud database-migration connection-profiles create postgresql \ - CONNECTION_PROFILE --region=us-central1 --password=123456 \ - --username=fakeuser --display-name=my-profile --host=1.2.3.4 \ - --port=1111 --cloudsql-instance=my-instance + my-profile --region=us-central1 --password=123456 \ + --username=my-user --host=1.2.3.4 --port=5432 \ + --cloudsql-instance=my-instance POSITIONAL ARGUMENTS Connection profile resource - The connection profile to create. The @@ -65,27 +64,32 @@ REQUIRED FLAGS Network port of the source database. --username=USERNAME - Username that Database Migration Service will use to connect to the - database. The value is encrypted when stored in Database Migration - Service. + Username that Database Migration Service uses to connect to the + database. Database Migration Service encrypts the value when storing + it. Exactly one of these must be specified: --password=PASSWORD - Password for the user that Database Migration Service will be using - to connect to the database. This field is not returned on request, - and the value is encrypted when stored in Database Migration Service. + Password for the user that Database Migration Service uses to connect + to the source database. Database Migration Service encrypts the value + when storing it, and the field is not returned on request. --prompt-for-password Prompt for the password used to connect to the database. OPTIONAL FLAGS + --no-async + Waits for the operation in progress to complete before returning. + --cloudsql-instance=CLOUDSQL_INSTANCE If the source is a Cloud SQL database, use this field to provide the Cloud SQL instance ID of the source. --display-name=DISPLAY_NAME - Friendly name for the connection profile. + A user-friendly name for the connection profile. The display name can + include letters, numbers, spaces, and hyphens, and must start with a + letter. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. @@ -98,15 +102,18 @@ OPTIONAL FLAGS --ca-certificate=CA_CERTIFICATE x509 PEM-encoded certificate of the CA that signed the source database server's certificate. The replica will use this certificate to verify - it's connecting to the right host. + it's connecting to the correct host. Database Migration Service + encrypts the value when storing it. --client-certificate=CLIENT_CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to - authenticate against the source database server. + authenticate against the source database server. Database Migration + Service encrypts the value when storing it. --private-key=PRIVATE_KEY Unencrypted PKCS#1 or PKCS#8 PEM-encoded private key associated with - the Client Certificate. + the Client Certificate. Database Migration Service encrypts the value + when storing it. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/database-migration/connection-profiles/update b/gcloud/database-migration/connection-profiles/update index a3a7a9af7..131ca5a4d 100644 --- a/gcloud/database-migration/connection-profiles/update +++ b/gcloud/database-migration/connection-profiles/update @@ -15,12 +15,19 @@ SYNOPSIS DESCRIPTION Update a Database Migration Service connection profile. + ▪ Draft connection profile: the user can update all flags available in + connection-profiles create command. + ▪ Existing connection profile: the user can update a limited list of + flags, see connection-profiles update Synopsis. + ▪ If a migration job is using the connection profile, then updates to + fields host, port, username, and password will propagate to the + destination instance. EXAMPLES - To update the display name of a connection profile: + To update the username of a connection profile: - $ gcloud database-migration connection-profiles update \ - CONNECTION_PROFILE --region=us-central1 --display-name=new-name + $ gcloud database-migration connection-profiles update my-profile \ + --region=us-central1 --username=new-user POSITIONAL ARGUMENTS Connection profile resource - The connection profile to update. The @@ -53,18 +60,22 @@ FLAGS --ca-certificate=CA_CERTIFICATE x509 PEM-encoded certificate of the CA that signed the source database server's certificate. The replica will use this certificate to verify - it's connecting to the right host. + it's connecting to the correct host. Database Migration Service + encrypts the value when storing it. --client-certificate=CLIENT_CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to - authenticate against the source database server. + authenticate against the source database server. Database Migration + Service encrypts the value when storing it. --cloudsql-instance=CLOUDSQL_INSTANCE If the source is a Cloud SQL database, use this field to provide the Cloud SQL instance ID of the source. --display-name=DISPLAY_NAME - Friendly name for the connection profile. + A user-friendly name for the connection profile. The display name can + include letters, numbers, spaces, and hyphens, and must start with a + letter. --host=HOST IP or hostname of the source database. @@ -74,7 +85,8 @@ FLAGS --private-key=PRIVATE_KEY Unencrypted PKCS#1 or PKCS#8 PEM-encoded private key associated with - the Client Certificate. + the Client Certificate. Database Migration Service encrypts the value + when storing it. --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value @@ -86,9 +98,9 @@ FLAGS numbers. --username=USERNAME - Username that Database Migration Service will use to connect to the - database. The value is encrypted when stored in Database Migration - Service. + Username that Database Migration Service uses to connect to the + database. Database Migration Service encrypts the value when storing + it. At most one of these can be specified: @@ -113,9 +125,9 @@ FLAGS At most one of these can be specified: --password=PASSWORD - Password for the user that Database Migration Service will be using - to connect to the database. This field is not returned on request, - and the value is encrypted when stored in Database Migration Service. + Password for the user that Database Migration Service uses to connect + to the source database. Database Migration Service encrypts the value + when storing it, and the field is not returned on request. --prompt-for-password Prompt for the password used to connect to the database. diff --git a/gcloud/database-migration/migration-jobs/create b/gcloud/database-migration/migration-jobs/create index 34110db56..6d4fa3282 100644 --- a/gcloud/database-migration/migration-jobs/create +++ b/gcloud/database-migration/migration-jobs/create @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud database-migration migration-jobs create (MIGRATION_JOB : --region=REGION) --destination=DESTINATION - --source=SOURCE --type=TYPE [--display-name=DISPLAY_NAME] - [--dump-path=DUMP_PATH] [--labels=[KEY=VALUE,...]] [--sync] + --source=SOURCE --type=TYPE [--no-async] [--display-name=DISPLAY_NAME] + [--dump-path=DUMP_PATH] [--labels=[KEY=VALUE,...]] [--peer-vpc=PEER_VPC | --static-ip | [--vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC : --vm=VM]] [GCLOUD_WIDE_FLAG ...] @@ -91,6 +91,9 @@ REQUIRED FLAGS of: ONE_TIME, CONTINUOUS. OPTIONAL FLAGS + --no-async + Waits for the operation in progress to complete before returning. + --display-name=DISPLAY_NAME Friendly name for the migration job. @@ -106,9 +109,6 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - --sync - Waits for the operation in progress to complete before returning. - The connectivity method used by the migration job. If a connectivity method isn't specified, then it isn't added to the migration job. diff --git a/gcloud/database-migration/migration-jobs/update b/gcloud/database-migration/migration-jobs/update index 8d661b8af..88c90b06d 100644 --- a/gcloud/database-migration/migration-jobs/update +++ b/gcloud/database-migration/migration-jobs/update @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud database-migration migration-jobs update (MIGRATION_JOB : --region=REGION) --destination=DESTINATION - --source=SOURCE [--display-name=DISPLAY_NAME] [--dump-path=DUMP_PATH] - [--type=TYPE] [--update-labels=[KEY=VALUE,...]] + --source=SOURCE [--no-async] [--display-name=DISPLAY_NAME] + [--dump-path=DUMP_PATH] [--type=TYPE] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [--peer-vpc=PEER_VPC | --static-ip | --vm=VM --vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC] @@ -84,6 +84,9 @@ FLAGS connection_profile. To set the connection_profile attribute: ▸ provide the argument --source on the command line. + --no-async + Waits for the operation in progress to complete before returning. + --display-name=DISPLAY_NAME Friendly name for the migration job. diff --git a/gcloud/dataproc/batches/submit/help b/gcloud/dataproc/batches/submit/help index 3e25c325c..499ed9446 100644 --- a/gcloud/dataproc/batches/submit/help +++ b/gcloud/dataproc/batches/submit/help @@ -78,10 +78,9 @@ FLAGS "projects/{project-id}/locations/{region}/services/{service-name}". --properties=[PROPERTY=VALUE,...] - Specifies configuration properties for the batch job. Properties are - mapped to configuration files for the batch job. See [Dataproc - Serverless for Spark job capabilities] - (https://cloud.google.com/dataproc-serverless/docs/overview#for_spark_job_capabilities) + Specifies configuration properties for the workload. See Dataproc + Serverless for Spark documentation + (https://cloud.google.com/dataproc-serverless/docs/concepts/properties) for the list of supported properties. Region resource - Dataproc region to use. Each Dataproc region constitutes diff --git a/gcloud/dataproc/batches/submit/pyspark b/gcloud/dataproc/batches/submit/pyspark index 5817bbede..4e1ccc228 100644 --- a/gcloud/dataproc/batches/submit/pyspark +++ b/gcloud/dataproc/batches/submit/pyspark @@ -90,10 +90,9 @@ FLAGS "projects/{project-id}/locations/{region}/services/{service-name}". --properties=[PROPERTY=VALUE,...] - Specifies configuration properties for the batch job. Properties are - mapped to configuration files for the batch job. See [Dataproc - Serverless for Spark job capabilities] - (https://cloud.google.com/dataproc-serverless/docs/overview#for_spark_job_capabilities) + Specifies configuration properties for the workload. See Dataproc + Serverless for Spark documentation + (https://cloud.google.com/dataproc-serverless/docs/concepts/properties) for the list of supported properties. --py-files=[PY,...] diff --git a/gcloud/dataproc/batches/submit/spark b/gcloud/dataproc/batches/submit/spark index e6b22a5b6..6bf9a5da1 100644 --- a/gcloud/dataproc/batches/submit/spark +++ b/gcloud/dataproc/batches/submit/spark @@ -108,10 +108,9 @@ OPTIONAL FLAGS "projects/{project-id}/locations/{region}/services/{service-name}". --properties=[PROPERTY=VALUE,...] - Specifies configuration properties for the batch job. Properties are - mapped to configuration files for the batch job. See [Dataproc - Serverless for Spark job capabilities] - (https://cloud.google.com/dataproc-serverless/docs/overview#for_spark_job_capabilities) + Specifies configuration properties for the workload. See Dataproc + Serverless for Spark documentation + (https://cloud.google.com/dataproc-serverless/docs/concepts/properties) for the list of supported properties. Region resource - Dataproc region to use. Each Dataproc region constitutes diff --git a/gcloud/dataproc/batches/submit/spark-r b/gcloud/dataproc/batches/submit/spark-r index cb269d706..7aeb98bd5 100644 --- a/gcloud/dataproc/batches/submit/spark-r +++ b/gcloud/dataproc/batches/submit/spark-r @@ -86,10 +86,9 @@ FLAGS "projects/{project-id}/locations/{region}/services/{service-name}". --properties=[PROPERTY=VALUE,...] - Specifies configuration properties for the batch job. Properties are - mapped to configuration files for the batch job. See [Dataproc - Serverless for Spark job capabilities] - (https://cloud.google.com/dataproc-serverless/docs/overview#for_spark_job_capabilities) + Specifies configuration properties for the workload. See Dataproc + Serverless for Spark documentation + (https://cloud.google.com/dataproc-serverless/docs/concepts/properties) for the list of supported properties. Region resource - Dataproc region to use. Each Dataproc region constitutes diff --git a/gcloud/dataproc/batches/submit/spark-sql b/gcloud/dataproc/batches/submit/spark-sql index 433cd8014..8257aa95d 100644 --- a/gcloud/dataproc/batches/submit/spark-sql +++ b/gcloud/dataproc/batches/submit/spark-sql @@ -75,10 +75,9 @@ FLAGS "projects/{project-id}/locations/{region}/services/{service-name}". --properties=[PROPERTY=VALUE,...] - Specifies configuration properties for the batch job. Properties are - mapped to configuration files for the batch job. See [Dataproc - Serverless for Spark job capabilities] - (https://cloud.google.com/dataproc-serverless/docs/overview#for_spark_job_capabilities) + Specifies configuration properties for the workload. See Dataproc + Serverless for Spark documentation + (https://cloud.google.com/dataproc-serverless/docs/concepts/properties) for the list of supported properties. Region resource - Dataproc region to use. Each Dataproc region constitutes diff --git a/gcloud/network-connectivity/spokes/linked-interconnect-attachments/create b/gcloud/network-connectivity/spokes/linked-interconnect-attachments/create index 26823f359..42b11d1e8 100644 --- a/gcloud/network-connectivity/spokes/linked-interconnect-attachments/create +++ b/gcloud/network-connectivity/spokes/linked-interconnect-attachments/create @@ -11,8 +11,7 @@ SYNOPSIS DESCRIPTION Create a new VLAN attachment spoke - (https://cloud.google.com/network-connectivity/docs/network-connectivity-center/how-to/working-with-hubs-spokes#create-vlan-spoke) - with the specified properties. + (https://cloud.google.com/network-connectivity/docs/network-connectivity-center/how-to/working-with-hubs-spokes#create-vlan-spoke). EXAMPLES To create a spoke in region us-central1 that uses data transfer and has two @@ -61,8 +60,8 @@ REQUIRED FLAGS Hub that the spoke will attach to. The hub must already exist. --interconnect-attachments=[INTERCONNECT_ATTACHMENTS,...] - VLAN attachments that this spoke links to. The resources must already - exist. + VLAN attachments that the spoke provides connectivity to. The resources + must already exist. OPTIONAL FLAGS --async @@ -70,7 +69,7 @@ OPTIONAL FLAGS complete. --description=DESCRIPTION - Description of the spoke to be created. + Description of the spoke to create. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/network-connectivity/spokes/linked-interconnect-attachments/update b/gcloud/network-connectivity/spokes/linked-interconnect-attachments/update index 209e10a0c..c2e7ead7e 100644 --- a/gcloud/network-connectivity/spokes/linked-interconnect-attachments/update +++ b/gcloud/network-connectivity/spokes/linked-interconnect-attachments/update @@ -19,8 +19,8 @@ EXAMPLES --region=us-central1 --description="new spoke description" POSITIONAL ARGUMENTS - Spoke resource - Name of the spoke to be updated. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some + Spoke resource - Name of the spoke to update. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument spoke on the command line with a fully specified diff --git a/gcloud/network-connectivity/spokes/linked-router-appliances/create b/gcloud/network-connectivity/spokes/linked-router-appliances/create index a05153a85..bb5d6ed44 100644 --- a/gcloud/network-connectivity/spokes/linked-router-appliances/create +++ b/gcloud/network-connectivity/spokes/linked-router-appliances/create @@ -10,8 +10,7 @@ SYNOPSIS DESCRIPTION Create a new Router appliance spoke - (https://cloud.google.com/network-connectivity/docs/network-connectivity-center/how-to/working-with-hubs-spokes#create-ra-spoke) - with the specified properties. + (https://cloud.google.com/network-connectivity/docs/network-connectivity-center/how-to/working-with-hubs-spokes#create-ra-spoke). EXAMPLES To create a spoke in region us-central1 that uses data transfer and has two @@ -61,7 +60,8 @@ REQUIRED FLAGS Hub that the spoke will attach to. The hub must already exist. --router-appliance=ROUTER_APPLIANCE - Router appliance instance(s) to which this spoke links. + Router appliance instance(s) that the spoke provides connectivity to. + The resources must already exist. For example, use --router-appliance=instance=ins_uri_1,ip=10.10.0.1 to add a single router appliance instance, or @@ -75,7 +75,7 @@ OPTIONAL FLAGS complete. --description=DESCRIPTION - Description of the spoke to be created. + Description of the spoke to create. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/network-connectivity/spokes/linked-router-appliances/update b/gcloud/network-connectivity/spokes/linked-router-appliances/update index 92d34af55..f3c6f654e 100644 --- a/gcloud/network-connectivity/spokes/linked-router-appliances/update +++ b/gcloud/network-connectivity/spokes/linked-router-appliances/update @@ -31,8 +31,8 @@ EXAMPLES ip=10.10.0.2 POSITIONAL ARGUMENTS - Spoke resource - Name of the spoke to be updated. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some + Spoke resource - Name of the spoke to update. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument spoke on the command line with a fully specified diff --git a/gcloud/network-connectivity/spokes/linked-vpn-tunnels/create b/gcloud/network-connectivity/spokes/linked-vpn-tunnels/create index 8e985440e..b9fbb0a44 100644 --- a/gcloud/network-connectivity/spokes/linked-vpn-tunnels/create +++ b/gcloud/network-connectivity/spokes/linked-vpn-tunnels/create @@ -10,8 +10,7 @@ SYNOPSIS DESCRIPTION Create a new VPN spoke - (https://cloud.google.com/network-connectivity/docs/network-connectivity-center/how-to/working-with-hubs-spokes#create-vpn-spoke) - with the specified properties. + (https://cloud.google.com/network-connectivity/docs/network-connectivity-center/how-to/working-with-hubs-spokes#create-vpn-spoke). EXAMPLES To create a VPN spoke in region us-central1 that uses data transfer and has @@ -59,8 +58,8 @@ REQUIRED FLAGS Hub that the spoke will attach to. The hub must already exist. --vpn-tunnels=[VPN_TUNNELS,...] - HA VPN tunnels that this spoke links to. The resources must already - exist. + HA VPN tunnels that the spoke provides connectivity to. The resources + must already exist. OPTIONAL FLAGS --async @@ -68,7 +67,7 @@ OPTIONAL FLAGS complete. --description=DESCRIPTION - Description of the spoke to be created. + Description of the spoke to create. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/network-connectivity/spokes/linked-vpn-tunnels/update b/gcloud/network-connectivity/spokes/linked-vpn-tunnels/update index f14a822aa..f0bb8b43f 100644 --- a/gcloud/network-connectivity/spokes/linked-vpn-tunnels/update +++ b/gcloud/network-connectivity/spokes/linked-vpn-tunnels/update @@ -19,8 +19,8 @@ EXAMPLES --description="new spoke description" POSITIONAL ARGUMENTS - Spoke resource - Name of the spoke to be updated. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some + Spoke resource - Name of the spoke to update. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument spoke on the command line with a fully specified diff --git a/gcloud/sql/generate-login-token b/gcloud/sql/generate-login-token new file mode 100644 index 000000000..68b775743 --- /dev/null +++ b/gcloud/sql/generate-login-token @@ -0,0 +1,53 @@ +NAME + gcloud sql generate-login-token - generate an IAM login token for Cloud SQL + +SYNOPSIS + gcloud sql generate-login-token [--application-default-credential] + [--instance=INSTANCE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud sql generate-login-token generates an IAM token to use for logging + in to Cloud SQL instances. + +EXAMPLES + To generate an IAM login token using gcloud credentials, run: + + $ gcloud sql generate-login-token + + To generate an IAM login token using application default credentials, run: + + $ gcloud sql generate-login-token --application-default-credential + + To generate an IAM login token using gcloud credentials for instance + my-instance, run: + + $ gcloud sql generate-login-token --instance=my-instance + + To generate an IAM login token using application default credentials for + instance my-instance, run: + + $ gcloud sql generate-login-token --instance=my-instance \ + --application-default-credential + +FLAGS + --application-default-credential + Use application default credentials to generate the login token. + + --instance=INSTANCE + Cloud SQL instance ID. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha sql generate-login-token + + $ gcloud beta sql generate-login-token + diff --git a/gcloud/sql/help b/gcloud/sql/help index 99bb1f5b6..1fb60f223 100644 --- a/gcloud/sql/help +++ b/gcloud/sql/help @@ -63,6 +63,9 @@ COMMANDS connect Connects to a Cloud SQL instance. + generate-login-token + Generate an IAM login token for Cloud SQL. + reschedule-maintenance Reschedule a Cloud SQL instance's maintenance. diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index 1bd48f2e7..8cf1f90ef 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -173,7 +173,8 @@ FLAGS --enable-password-policy Enable the password policy, which enforces user password management - with the policies configured for the instance. + with the policies configured for the instance. This flag is only + available for Postgres. --enable-point-in-time-recovery Allows for data recovery from a specific point in time, down to a @@ -253,8 +254,8 @@ FLAGS --network=projects/testproject/global/networks/testsharednetwork --password-policy-complexity=PASSWORD_POLICY_COMPLEXITY - The complexity of the password. PASSWORD_POLICY_COMPLEXITY must be one - of: + The complexity of the password. This flag is available only for + PostgreSQL. PASSWORD_POLICY_COMPLEXITY must be one of: COMPLEXITY_DEFAULT A combination of lowercase, uppercase, numeric, and @@ -264,21 +265,24 @@ FLAGS implies that complexity check is not enabled. --[no-]password-policy-disallow-username-substring - Disallow username as a part of the password. Use - --password-policy-disallow-username-substring to enable and - --no-password-policy-disallow-username-substring to disable. + Disallow username as a part of the password. This flag is available + only for PostgreSQL. Use --password-policy-disallow-username-substring + to enable and --no-password-policy-disallow-username-substring to + disable. --password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH - Minimum number of characters allowed in the password. + Minimum number of characters allowed in the password. This flag is + available only for PostgreSQL. --password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL Minimum interval after which the password can be changed, for example, 2m for 2 minutes. See - $ gcloud topic datetimes for information on duration formats. + $ gcloud topic datetimes for information on duration formats. This + flag is available only for PostgreSQL. --password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL Number of previous passwords that cannot be reused. The valid range is - between 0 and 100. + 0 to 100. This flag is available only for PostgreSQL. --replica-type=REPLICA_TYPE The type of replica to create. REPLICA_TYPE must be one of: READ, diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index 1948c0052..0fb58a0cb 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -85,7 +85,8 @@ FLAGS Provides no failover capability. This is the default. --clear-password-policy - Clear the existing password policy. + Clear the existing password policy. This flag is only available for + Postgres. --cpu=CPU Whole number value indicating how many cores are desired in the @@ -130,7 +131,8 @@ FLAGS --enable-password-policy Enable the password policy, which enforces user password management - with the policies configured for the instance. + with the policies configured for the instance. This flag is only + available for Postgres. --enable-point-in-time-recovery Allows for data recovery from a specific point in time, down to a @@ -213,8 +215,8 @@ FLAGS --network=projects/testproject/global/networks/testsharednetwork --password-policy-complexity=PASSWORD_POLICY_COMPLEXITY - The complexity of the password. PASSWORD_POLICY_COMPLEXITY must be one - of: + The complexity of the password. This flag is available only for + PostgreSQL. PASSWORD_POLICY_COMPLEXITY must be one of: COMPLEXITY_DEFAULT A combination of lowercase, uppercase, numeric, and @@ -224,21 +226,24 @@ FLAGS implies that complexity check is not enabled. --[no-]password-policy-disallow-username-substring - Disallow username as a part of the password. Use - --password-policy-disallow-username-substring to enable and - --no-password-policy-disallow-username-substring to disable. + Disallow username as a part of the password. This flag is available + only for PostgreSQL. Use --password-policy-disallow-username-substring + to enable and --no-password-policy-disallow-username-substring to + disable. --password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH - Minimum number of characters allowed in the password. + Minimum number of characters allowed in the password. This flag is + available only for PostgreSQL. --password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL Minimum interval after which the password can be changed, for example, 2m for 2 minutes. See - $ gcloud topic datetimes for information on duration formats. + $ gcloud topic datetimes for information on duration formats. This + flag is available only for PostgreSQL. --password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL Number of previous passwords that cannot be reused. The valid range is - between 0 and 100. + 0 to 100. This flag is available only for PostgreSQL. --pricing-plan=PRICING_PLAN, -p PRICING_PLAN First Generation instances only. The pricing plan for this instance. diff --git a/gcloud/sql/users/create b/gcloud/sql/users/create index dbe40e34b..f9e2cdd82 100644 --- a/gcloud/sql/users/create +++ b/gcloud/sql/users/create @@ -40,16 +40,18 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. + This flag is currently not available. --[no-]password-policy-enable-failed-attempts-check - Enables the failed login attempts check if set to true. Use + Enables the failed login attempts check if set to true. This flag is + currently not available. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION Expiration duration after a password is updated, for example, 2m for 2 minutes. See gcloud topic datetimes for information on duration - formats. + formats. This flag is currently not available. --type=TYPE Cloud SQL user's type. It determines the method to authenticate the diff --git a/gcloud/sql/users/set-password-policy b/gcloud/sql/users/set-password-policy index baee6eb29..c95a9efbb 100644 --- a/gcloud/sql/users/set-password-policy +++ b/gcloud/sql/users/set-password-policy @@ -42,7 +42,8 @@ OPTIONAL FLAGS complete. --clear-password-policy - Clear the existing password policy. + Clear the existing password policy. This flag is only available for + Postgres. --host=HOST Cloud SQL user's host name expressed as a specific IP address or @@ -55,16 +56,18 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. + This flag is currently not available. --[no-]password-policy-enable-failed-attempts-check - Enables the failed login attempts check if set to true. Use + Enables the failed login attempts check if set to true. This flag is + currently not available. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION Expiration duration after a password is updated, for example, 2m for 2 minutes. See gcloud topic datetimes for information on duration - formats. + formats. This flag is currently not available. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account,