diff --git a/gcloud/_version b/gcloud/_version index c4f773474..96232e0f0 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,6 +1,6 @@ -Google Cloud SDK 379.0.0 -alpha 2022.03.25 -beta 2022.03.25 +Google Cloud SDK 380.0.0 +alpha 2022.04.01 +beta 2022.04.01 bq 2.0.74 -core 2022.03.25 +core 2022.04.01 gsutil 5.8 diff --git a/gcloud/alpha/composer/environments/check-upgrade b/gcloud/alpha/composer/environments/check-upgrade index fc3b84a89..c2c75b40a 100644 --- a/gcloud/alpha/composer/environments/check-upgrade +++ b/gcloud/alpha/composer/environments/check-upgrade @@ -58,27 +58,31 @@ FLAGS At most one of these can be specified: --airflow-version=AIRFLOW_VERSION - Upgrade the environment to a later Airflow version in-place. + Upgrade the environment to a later Apache Airflow version in-place. - Must be of the form X.Y[.Z]. + Must be of the form X[.Y[.Z]], where [] denotes optional fragments. - The Airflow version is a semantic version. The patch version can be - omitted and the current version will be selected. The version numbers - that are used will be stored. + The Apache Airflow version is a semantic version or an alias in the + form of major or major.minor version numbers, resolved to the latest + matching Apache Airflow version supported in the current Cloud + Composer version. The resolved version is stored in the upgraded + environment. --image-version=IMAGE_VERSION Upgrade the environment to a later version in-place. The image version encapsulates the versions of both Cloud Composer and Apache Airflow. Must be of the form - composer-A[.B.C[-D.E]]-airflow-X.Y[.Z]. + composer-A[.B.C[-D.E]]-airflow-X[.Y[.Z]], where [] denotes optional + fragments. - The Cloud Composer and Airflow versions are semantic versions. latest - can be provided instead of an explicit Cloud Composer version number - indicating that the server will replace latest with the current Cloud - Composer version. For the Apache Airflow portion, the patch version - can be omitted and the current version will be selected. The version - numbers that are used will be stored. + The Cloud Composer portion of the image version is a semantic version + or an alias in the form of major version number or latest, resolved + to the current Cloud Composer version. The Apache Airflow portion of + the image version is a semantic version or an alias in the form of + major or major.minor version numbers, resolved to the latest matching + Apache Airflow version supported in the given Cloud Composer version. + The resolved versions are stored in the upgraded environment. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/composer/environments/create b/gcloud/alpha/composer/environments/create index ce56cc36e..1d4399398 100644 --- a/gcloud/alpha/composer/environments/create +++ b/gcloud/alpha/composer/environments/create @@ -183,11 +183,15 @@ FLAGS At most one of these can be specified: --airflow-version=AIRFLOW_VERSION - Version of Airflow to run in the environment. + Version of Apache Airflow to run in the environment. - Must be of the form `X.Y[.Z]`. + Must be of the form `X[.Y[.Z]]`, where `[]` denotes optional fragments. The current Cloud Composer version will be used within the created + environment. The Apache Airflow version is a semantic version or an alias + in the form of major or major.minor version numbers, resolved to the + latest matching Apache Airflow version supported in the current Cloud + Composer version. The resolved version is stored in the created environment. --image-version=IMAGE_VERSION @@ -195,15 +199,16 @@ FLAGS The image version encapsulates the versions of both Cloud Composer and Apache Airflow. Must be of the form - `composer-A[.B.C[-D.E]]-airflow-X.Y[.Z]`. + `composer-A[.B.C[-D.E]]-airflow-X[.Y[.Z]]`, where `[]` denotes optional + fragments. - The Cloud Composer and Airflow versions are semantic versions. - `latest` can be provided instead of an explicit Cloud Composer - version number indicating that the server will replace `latest` - with the current Cloud Composer version. For the Apache Airflow - portion, the patch version can be omitted and the current - version will be selected. The version numbers that are used will - be stored. + The Cloud Composer portion of the image version is a semantic version or + an alias in the form of major version number or `latest`, resolved to the + current Cloud Composer version. The Apache Airflow portion of the image + version is a semantic version or an alias in the form of major or + major.minor version numbers, resolved to the latest matching Apache + Airflow version supported in the given Cloud Composer version. The + resolved versions are stored in the created environment. Private Clusters diff --git a/gcloud/alpha/composer/environments/help b/gcloud/alpha/composer/environments/help index b6d6ea7c5..8b7c9e7d4 100644 --- a/gcloud/alpha/composer/environments/help +++ b/gcloud/alpha/composer/environments/help @@ -21,6 +21,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + snapshots + (ALPHA) Saves and loads snapshots of environment. + storage (ALPHA) Manage Cloud Storage objects stored as part of Cloud Composer environments. diff --git a/gcloud/alpha/composer/environments/snapshots/help b/gcloud/alpha/composer/environments/snapshots/help new file mode 100644 index 000000000..a71e4d03e --- /dev/null +++ b/gcloud/alpha/composer/environments/snapshots/help @@ -0,0 +1,33 @@ +NAME + gcloud alpha composer environments snapshots - saves and loads snapshots of + environment + +SYNOPSIS + gcloud alpha composer environments snapshots COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The gcloud alpha composer environments snapshots command group + saves and loads snapshots of Cloud Composer environments. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + load + (ALPHA) Load a snapshot into the environment. + + save + (ALPHA) Save a snapshot of the environment. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta composer environments snapshots + diff --git a/gcloud/alpha/composer/environments/snapshots/load b/gcloud/alpha/composer/environments/snapshots/load new file mode 100644 index 000000000..a051cf870 --- /dev/null +++ b/gcloud/alpha/composer/environments/snapshots/load @@ -0,0 +1,77 @@ +NAME + gcloud alpha composer environments snapshots load - load a snapshot into + the environment + +SYNOPSIS + gcloud alpha composer environments snapshots load + (ENVIRONMENT : --location=LOCATION) --snapshot-path=SNAPSHOT_PATH + [--async] [--skip-pypi-packages-installation] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Load a snapshot into the environment. + +EXAMPLES + To load a snapshot into the environment named env-1, run: + + $ gcloud alpha composer environments snapshots load env-1 \ + --snapshot-path=gs://my-bucket/path-to-the-specific-snapshot + +POSITIONAL ARGUMENTS + Environment resource - The environment where to load a snapshot. 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 environment 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. + + ENVIRONMENT + ID of the environment or fully qualified identifier for the + environment. To set the environment attribute: + ▸ provide the argument environment on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Compute Engine region in which to create the environment. To set the + location attribute: + ▸ provide the argument environment on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property composer/location. + +REQUIRED FLAGS + --snapshot-path=SNAPSHOT_PATH + The Cloud Storage path to load the snapshot from. It must start with + prefix gs:// and one needs to specify a single snapshot that should be + loaded. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --skip-pypi-packages-installation + When specified, skips the installation of custom PyPI packages from the + snapshot. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta composer environments snapshots load + diff --git a/gcloud/alpha/composer/environments/snapshots/save b/gcloud/alpha/composer/environments/snapshots/save new file mode 100644 index 000000000..15a282b6c --- /dev/null +++ b/gcloud/alpha/composer/environments/snapshots/save @@ -0,0 +1,71 @@ +NAME + gcloud alpha composer environments snapshots save - save a snapshot of the + environment + +SYNOPSIS + gcloud alpha composer environments snapshots save + (ENVIRONMENT : --location=LOCATION) [--async] + [--snapshot-location=SNAPSHOT_LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Save a snapshot of the environment. + +EXAMPLES + To save a snapshot of the environment named env-1, run: + + $ gcloud alpha composer environments snapshots save env-1 + +POSITIONAL ARGUMENTS + Environment resource - The environment where the snapshot must be saved. + 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 environment 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. + + ENVIRONMENT + ID of the environment or fully qualified identifier for the + environment. To set the environment attribute: + ▸ provide the argument environment on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Compute Engine region in which to create the environment. To set the + location attribute: + ▸ provide the argument environment on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property composer/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --snapshot-location=SNAPSHOT_LOCATION + The Cloud Storage location where to save the snapshot. It must start + with the prefix gs://. Default value is /snapshots directory in the + Cloud Storage bucket of the environment. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta composer environments snapshots save + diff --git a/gcloud/alpha/composer/environments/update b/gcloud/alpha/composer/environments/update index b4035758d..84e6dc24d 100644 --- a/gcloud/alpha/composer/environments/update +++ b/gcloud/alpha/composer/environments/update @@ -99,27 +99,32 @@ REQUIRED FLAGS At most one of these can be specified: --airflow-version=AIRFLOW_VERSION - Upgrade the environment to a later Airflow version in-place. + Upgrade the environment to a later Apache Airflow version in-place. - Must be of the form X.Y[.Z]. + Must be of the form X[.Y[.Z]], where [] denotes optional fragments. - The Airflow version is a semantic version. The patch version can be - omitted and the current version will be selected. The version - numbers that are used will be stored. + The Apache Airflow version is a semantic version or an alias in the + form of major or major.minor version numbers, resolved to the + latest matching Apache Airflow version supported in the current + Cloud Composer version. The resolved version is stored in the + upgraded environment. --image-version=IMAGE_VERSION Upgrade the environment to a later version in-place. The image version encapsulates the versions of both Cloud Composer and Apache Airflow. Must be of the form - composer-A[.B.C[-D.E]]-airflow-X.Y[.Z]. + composer-A[.B.C[-D.E]]-airflow-X[.Y[.Z]], where [] denotes optional + fragments. - The Cloud Composer and Airflow versions are semantic versions. - latest can be provided instead of an explicit Cloud Composer - version number indicating that the server will replace latest with - the current Cloud Composer version. For the Apache Airflow portion, - the patch version can be omitted and the current version will be - selected. The version numbers that are used will be stored. + The Cloud Composer portion of the image version is a semantic + version or an alias in the form of major version number or latest, + resolved to the current Cloud Composer version. The Apache Airflow + portion of the image version is a semantic version or an alias in + the form of major or major.minor version numbers, resolved to the + latest matching Apache Airflow version supported in the given Cloud + Composer version. The resolved versions are stored in the upgraded + environment. Group of arguments for setting master authorized networks configuration. diff --git a/gcloud/alpha/compute/addresses/create b/gcloud/alpha/compute/addresses/create index 0bbd3fdf5..04b4f05e1 100644 --- a/gcloud/alpha/compute/addresses/create +++ b/gcloud/alpha/compute/addresses/create @@ -3,9 +3,9 @@ NAME SYNOPSIS gcloud alpha compute addresses create [NAME ...] - [--description=DESCRIPTION] [--network=NETWORK] - [--network-tier=NETWORK_TIER] [--prefix-length=PREFIX_LENGTH] - [--purpose=PURPOSE] [--subnet=SUBNET] + [--description=DESCRIPTION] [--endpoint-type=ENDPOINT_TYPE] + [--network=NETWORK] [--network-tier=NETWORK_TIER] + [--prefix-length=PREFIX_LENGTH] [--purpose=PURPOSE] [--subnet=SUBNET] [--addresses=ADDRESS,[ADDRESS,...] | --ip-version=IP_VERSION] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] @@ -72,6 +72,10 @@ FLAGS --description=DESCRIPTION An optional textual description for the addresses. + --endpoint-type=ENDPOINT_TYPE + The endpoint type of the external IPv6 address to be reserved. + Currently it can only be 'VM'. ENDPOINT_TYPE must be one of: VM, NETLB. + --network=NETWORK If specified, the network resource in which the address(es) should be reserved. diff --git a/gcloud/alpha/compute/backend-services/export b/gcloud/alpha/compute/backend-services/export index 35a681b58..1f3bc26f6 100644 --- a/gcloud/alpha/compute/backend-services/export +++ b/gcloud/alpha/compute/backend-services/export @@ -22,10 +22,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/BackendService.yaml. At most one of these can be specified: diff --git a/gcloud/alpha/compute/backend-services/import b/gcloud/alpha/compute/backend-services/import index 14c3ef977..8507a2e75 100644 --- a/gcloud/alpha/compute/backend-services/import +++ b/gcloud/alpha/compute/backend-services/import @@ -20,10 +20,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/BackendService.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/forwarding-rules/export b/gcloud/alpha/compute/forwarding-rules/export index c185734cf..07c139736 100644 --- a/gcloud/alpha/compute/forwarding-rules/export +++ b/gcloud/alpha/compute/forwarding-rules/export @@ -21,10 +21,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/ForwardingRule.yaml. At most one of these can be specified: diff --git a/gcloud/alpha/compute/forwarding-rules/import b/gcloud/alpha/compute/forwarding-rules/import index 571b4b8d9..841c533af 100644 --- a/gcloud/alpha/compute/forwarding-rules/import +++ b/gcloud/alpha/compute/forwarding-rules/import @@ -20,10 +20,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/ForwardingRule.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index 8bafb2c4d..ffd0dcc04 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -60,7 +60,7 @@ SYNOPSIS [--scopes=[SCOPE,...] | --no-scopes] [--service-account=SERVICE_ACCOUNT | --no-service-account] [--service-proxy=[enabled],[intercept-all-outbound-traffic], - [access-log=ACCESS-LOG], + [intercept-dns],[access-log=ACCESS-LOG], [exclude-outbound-ip-ranges=EXCLUDE-OUTBOUND-IP-RANGES], [exclude-outbound-port-ranges=EXCLUDE-OUTBOUND-PORT-RANGES], [mesh=MESH],[network=NETWORK],[project-number=PROJECT-NUMBER], @@ -1052,7 +1052,7 @@ FLAGS --no-service-account Create instance without service account - --service-proxy=[enabled],[intercept-all-outbound-traffic],[access-log=ACCESS-LOG],[exclude-outbound-ip-ranges=EXCLUDE-OUTBOUND-IP-RANGES],[exclude-outbound-port-ranges=EXCLUDE-OUTBOUND-PORT-RANGES],[mesh=MESH],[network=NETWORK],[project-number=PROJECT-NUMBER],[proxy-port=PROXY-PORT],[scope=SCOPE],[serving-ports=SERVING-PORTS],[tracing=TRACING] + --service-proxy=[enabled],[intercept-all-outbound-traffic],[intercept-dns],[access-log=ACCESS-LOG],[exclude-outbound-ip-ranges=EXCLUDE-OUTBOUND-IP-RANGES],[exclude-outbound-port-ranges=EXCLUDE-OUTBOUND-PORT-RANGES],[mesh=MESH],[network=NETWORK],[project-number=PROJECT-NUMBER],[proxy-port=PROXY-PORT],[scope=SCOPE],[serving-ports=SERVING-PORTS],[tracing=TRACING] Controls whether the Traffic Director service proxy (Envoy) and agent are installed and configured on the VM. "cloud-platform" scope is enabled automatically to allow connections to the Traffic Director API. @@ -1099,6 +1099,9 @@ FLAGS network used by the service proxy's control plane to generate dynamic configuration for the service proxy. + intercept-dns + Enables interception of UDP traffic by the service proxy. + intercept-all-outbound-traffic Enables interception of all outgoing traffic. The traffic is intercepted by the service proxy and then redirected to external diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 5cbf2ac31..3d610f28c 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -19,7 +19,8 @@ SYNOPSIS [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] [--hostname=HOSTNAME] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] - [--ipv6-network-tier=IPV6_NETWORK_TIER] + [--ipv6-address=IPV6_ADDRESS] [--ipv6-network-tier=IPV6_NETWORK_TIER] + [--ipv6-prefix-length=IPV6_PREFIX_LENGTH] [--ipv6-public-ptr-domain=IPV6_PUBLIC_PTR_DOMAIN] [--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]] [--local-nvdimm=[size=SIZE]] @@ -480,6 +481,11 @@ FLAGS Default. Stop the VM without preserving memory. The VM can be restarted later. + --ipv6-address=IPV6_ADDRESS + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP in the range. This option can + only be used when creating a single instance. + --ipv6-network-tier=IPV6_NETWORK_TIER Specifies the IPv6 network tier that will be used to configure the instance network interface IPv6 access config. IPV6_NETWORK_TIER must @@ -488,6 +494,11 @@ FLAGS PREMIUM High quality, Google-grade network tier. + --ipv6-prefix-length=IPV6_PREFIX_LENGTH + Prefix Length of the External IPv6 address range, should be used + together with --ipv6-address. Currently only /96 is supported and the + default value is 96. + --ipv6-public-ptr-domain=IPV6_PUBLIC_PTR_DOMAIN Assigns a custom PTR domain for the external IPv6 in the IPv6 access configuration of instance. If its value is not specified, the default diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index 4be330afb..173447557 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -28,7 +28,8 @@ SYNOPSIS [--[no-]enable-nested-virtualization] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] - [--ipv6-network-tier=IPV6_NETWORK_TIER] [--labels=[KEY=VALUE,...]] + [--ipv6-address=IPV6_ADDRESS] [--ipv6-network-tier=IPV6_NETWORK_TIER] + [--ipv6-prefix-length=IPV6_PREFIX_LENGTH] [--labels=[KEY=VALUE,...]] [--local-nvdimm=[size=SIZE]] [--local-ssd=[device-name=DEVICE-NAME], [interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE] @@ -421,6 +422,11 @@ FLAGS Default. Stop the VM without preserving memory. The VM can be restarted later. + --ipv6-address=IPV6_ADDRESS + Assigns the given external IPv6 address to the instance that is + created. The address must be the first IP in the range. This option can + only be used when creating a single instance. + --ipv6-network-tier=IPV6_NETWORK_TIER Specifies the IPv6 network tier that will be used to configure the instance network interface IPv6 access config. IPV6_NETWORK_TIER must @@ -429,6 +435,11 @@ FLAGS PREMIUM High quality, Google-grade network tier. + --ipv6-prefix-length=IPV6_PREFIX_LENGTH + Prefix Length of the External IPv6 address range, should be used + together with --ipv6-address. Currently only /96 is supported and the + default value is 96. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/alpha/compute/instances/network-interfaces/update b/gcloud/alpha/compute/instances/network-interfaces/update index 54156cf3f..da68c3c99 100644 --- a/gcloud/alpha/compute/instances/network-interfaces/update +++ b/gcloud/alpha/compute/instances/network-interfaces/update @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha compute instances network-interfaces update INSTANCE_NAME - [--aliases=ALIASES] [--ipv6-network-tier=IPV6_NETWORK_TIER] - [--network=NETWORK] + [--aliases=ALIASES] [--ipv6-address=IPV6_ADDRESS] + [--ipv6-network-tier=IPV6_NETWORK_TIER] + [--ipv6-prefix-length=IPV6_PREFIX_LENGTH] [--network=NETWORK] [--network-interface=NETWORK_INTERFACE; default="nic0"] [--private-network-ip=PRIVATE_NETWORK_IP] [--stack-type=STACK_TYPE] [--subnetwork=SUBNETWORK] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] @@ -42,6 +43,11 @@ FLAGS --aliases="10.128.1.0/24;r1:/32" + --ipv6-address=IPV6_ADDRESS + Assigns the given external IPv6 address to an instance. The address + must be the first IP in the range. This option can only be used on a + IPv4 only dual stack instance. + --ipv6-network-tier=IPV6_NETWORK_TIER Specifies the IPv6 network tier that will be used to configure the instance network interface IPv6 access config. IPV6_NETWORK_TIER must @@ -50,6 +56,11 @@ FLAGS PREMIUM High quality, Google-grade network tier. + --ipv6-prefix-length=IPV6_PREFIX_LENGTH + Prefix Length of the External IPv6 address range, should be used + together with --ipv6-address. Currently only /96 is supported and the + default value is 96. + --network=NETWORK Specifies the network this network interface belongs to. diff --git a/gcloud/alpha/compute/instances/update-from-file b/gcloud/alpha/compute/instances/update-from-file index 313d870a6..3dcf623fe 100644 --- a/gcloud/alpha/compute/instances/update-from-file +++ b/gcloud/alpha/compute/instances/update-from-file @@ -41,10 +41,9 @@ FLAGS default will be REFRESH. --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/Instance.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/ssl-policies/export b/gcloud/alpha/compute/ssl-policies/export index 44fa265d0..66dc366a9 100644 --- a/gcloud/alpha/compute/ssl-policies/export +++ b/gcloud/alpha/compute/ssl-policies/export @@ -15,10 +15,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/SslPolicy.yaml. GCLOUD WIDE FLAGS diff --git a/gcloud/alpha/compute/ssl-policies/import b/gcloud/alpha/compute/ssl-policies/import index d9e3a5f00..6bc14b3b9 100644 --- a/gcloud/alpha/compute/ssl-policies/import +++ b/gcloud/alpha/compute/ssl-policies/import @@ -17,10 +17,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/SslPolicy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/target-grpc-proxies/export b/gcloud/alpha/compute/target-grpc-proxies/export index 8f56db1e2..eb3111c12 100644 --- a/gcloud/alpha/compute/target-grpc-proxies/export +++ b/gcloud/alpha/compute/target-grpc-proxies/export @@ -15,10 +15,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/TargetGrpcProxy.yaml. GCLOUD WIDE FLAGS diff --git a/gcloud/alpha/compute/target-grpc-proxies/import b/gcloud/alpha/compute/target-grpc-proxies/import index fd75bd00b..d5c54ba3d 100644 --- a/gcloud/alpha/compute/target-grpc-proxies/import +++ b/gcloud/alpha/compute/target-grpc-proxies/import @@ -15,10 +15,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/TargetGrpcProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/target-http-proxies/export b/gcloud/alpha/compute/target-http-proxies/export index 16a363b75..d182c87fe 100644 --- a/gcloud/alpha/compute/target-http-proxies/export +++ b/gcloud/alpha/compute/target-http-proxies/export @@ -23,10 +23,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/TargetHttpProxy.yaml. At most one of these can be specified: diff --git a/gcloud/alpha/compute/target-http-proxies/import b/gcloud/alpha/compute/target-http-proxies/import index 8af234c5c..82ba955c6 100644 --- a/gcloud/alpha/compute/target-http-proxies/import +++ b/gcloud/alpha/compute/target-http-proxies/import @@ -21,10 +21,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/TargetHttpProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/target-https-proxies/export b/gcloud/alpha/compute/target-https-proxies/export index f16548d49..08019aae6 100644 --- a/gcloud/alpha/compute/target-https-proxies/export +++ b/gcloud/alpha/compute/target-https-proxies/export @@ -23,10 +23,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/TargetHttpsProxy.yaml. At most one of these can be specified: diff --git a/gcloud/alpha/compute/target-https-proxies/import b/gcloud/alpha/compute/target-https-proxies/import index 41d250832..b0c22862d 100644 --- a/gcloud/alpha/compute/target-https-proxies/import +++ b/gcloud/alpha/compute/target-https-proxies/import @@ -21,10 +21,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/TargetHttpsProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/target-ssl-proxies/create b/gcloud/alpha/compute/target-ssl-proxies/create index 19081b946..f9e5c5ec3 100644 --- a/gcloud/alpha/compute/target-ssl-proxies/create +++ b/gcloud/alpha/compute/target-ssl-proxies/create @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud alpha compute target-ssl-proxies create NAME --backend-service=BACKEND_SERVICE - --ssl-certificates=SSL_CERTIFICATE,[...] [--description=DESCRIPTION] + (--certificate-map=CERTIFICATE_MAP + : --ssl-certificates=SSL_CERTIFICATE,[...]) + [--description=DESCRIPTION] [--proxy-header=PROXY_HEADER; default="NONE"] [--ssl-policy=SSL_POLICY] [GCLOUD_WIDE_FLAG ...] @@ -14,8 +16,8 @@ DESCRIPTION forwarding rules which define which packets the proxy is responsible for routing. The target SSL proxy points to a backend service which handle the actual requests. The target SSL proxy also points to at most 15 SSL - certificates used for server-side authentication. The target SSL proxy can - be associated with at most one SSL policy. + certificates used for server-side authentication or one certificate map. + The target SSL proxy can be associated with at most one SSL policy. POSITIONAL ARGUMENTS NAME @@ -26,12 +28,31 @@ REQUIRED FLAGS A backend service that will be used for connections to the target SSL proxy. - --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 SSL proxy. + At least one of these must be specified: + + Certificate map resource - The certificate map to attach. 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 --certificate-map on the command line with a + fully specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. To set the location attribute: + ▸ provide the argument --certificate-map on the command line with a + fully specified name; + ▸ default value of location is [global]. + + --certificate-map=CERTIFICATE_MAP + ID of the certificate map or fully qualified identifier for the + certificate map. To set the map attribute: + ▫ provide the argument --certificate-map on the command line. + + --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 SSL proxy. OPTIONAL FLAGS --description=DESCRIPTION diff --git a/gcloud/alpha/compute/target-ssl-proxies/update b/gcloud/alpha/compute/target-ssl-proxies/update index 51150df82..71aaa3e76 100644 --- a/gcloud/alpha/compute/target-ssl-proxies/update +++ b/gcloud/alpha/compute/target-ssl-proxies/update @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud alpha compute target-ssl-proxies update NAME [--backend-service=BACKEND_SERVICE] [--proxy-header=PROXY_HEADER] - [--ssl-certificates=SSL_CERTIFICATE,[...]] + [--certificate-map=CERTIFICATE_MAP + : --ssl-certificates=SSL_CERTIFICATE,[...] | --clear-ssl-certificates + | --clear-certificate-map] [--clear-ssl-policy | --ssl-policy=SSL_POLICY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -14,8 +16,8 @@ DESCRIPTION more forwarding rules which define which packets the proxy is responsible for routing. The target SSL proxy in turn points to a backend service which will handle the requests. The target SSL proxy also points to at most 15 - SSL certificates used for server-side authentication. The target SSL proxy - can be associated with at most one SSL policy. + SSL certificates used for server-side authentication or one certificate + map. The target SSL proxy can be associated with at most one SSL policy. POSITIONAL ARGUMENTS NAME @@ -36,12 +38,37 @@ FLAGS Enables PROXY protocol (version 1) for passing client connection information. - --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 SSL proxy. + At most one of these can be specified: + + --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 SSL proxy. + + --clear-ssl-certificates + Removes any attached SSL Certificates from the SSL proxy. + + Certificate map resource - The certificate map to attach. 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 --certificate-map on the command line with a + fully specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. To set the location attribute: + ▸ provide the argument --certificate-map on the command line with a + fully specified name; + ▸ default value of location is [global]. + + --certificate-map=CERTIFICATE_MAP + ID of the certificate map or fully qualified identifier for the + certificate map. To set the map attribute: + ▫ provide the argument --certificate-map on the command line. + + --clear-certificate-map + Removes any attached certificate map from the SSL proxy. At most one of these can be specified: diff --git a/gcloud/alpha/compute/tpus/help b/gcloud/alpha/compute/tpus/help index 5684f121c..462eecc81 100644 --- a/gcloud/alpha/compute/tpus/help +++ b/gcloud/alpha/compute/tpus/help @@ -31,6 +31,9 @@ GROUPS locations (ALPHA) List or Describe Available Cloud TPU Locations. + queued-resources + (ALPHA) List, create, delete, and manage Queued Resources. + tpu-vm (ALPHA) List, create, and manage Cloud TPU VM nodes. diff --git a/gcloud/alpha/compute/tpus/queued-resources/create b/gcloud/alpha/compute/tpus/queued-resources/create new file mode 100644 index 000000000..e5a36a54e --- /dev/null +++ b/gcloud/alpha/compute/tpus/queued-resources/create @@ -0,0 +1,86 @@ +NAME + gcloud alpha compute tpus queued-resources create - create a Queued + Resource + +SYNOPSIS + gcloud alpha compute tpus queued-resources create + (QUEUED_RESOURCE : --zone=ZONE) [--accelerator-type=ACCELERATOR_TYPE] + [--async] [--node-id=NODE_ID] [--runtime-version=RUNTIME_VERSION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new Queued Resource with the specified attributes. + +EXAMPLES + To create a Queued Resource with ID my-queued-resource in zone + us-central1-b and project my-project, run: + + $ gcloud alpha compute tpus queued-resources create \ + my-queued-resource --accelerator-type=v2-8 \ + --runtime-version=v2-alpha --node-id=my-node-001 \ + --zone=us-central1-b --project=my-project + +POSITIONAL ARGUMENTS + Queued resource resource - The Queued Resource you want to create. 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 queued_resource 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. + + QUEUED_RESOURCE + ID of the queued_resource or fully qualified identifier for the + queued_resource. To set the queued_resource attribute: + ▸ provide the argument queued_resource on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --zone=ZONE + The compute/zone of the Cloud TPU. + + If not specified, will use default compute/zone. + + To set the zone attribute: + ▸ provide the argument queued_resource on the command line with a + fully specified name; + ▸ provide the argument --zone on the command line; + ▸ set the property compute/zone. + +FLAGS + --accelerator-type=ACCELERATOR_TYPE + Accelerator type for the TPU. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --node-id=NODE_ID + The unqualified Node identifier, used to identify the TPU in the Nodes + collection once provisioned. + + --runtime-version=RUNTIME_VERSION + Runtime version for the TPU, such as 2.3. + +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 tpu/v2alpha1 API. The full documentation for this API + can be found at: https://cloud.google.com/tpu/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/tpus/queued-resources/delete b/gcloud/alpha/compute/tpus/queued-resources/delete new file mode 100644 index 000000000..f1ed24de0 --- /dev/null +++ b/gcloud/alpha/compute/tpus/queued-resources/delete @@ -0,0 +1,76 @@ +NAME + gcloud alpha compute tpus queued-resources delete - delete a Queued + Resource + +SYNOPSIS + gcloud alpha compute tpus queued-resources delete + (QUEUED_RESOURCE : --zone=ZONE) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an existing Queued Resource. + + To get a list of Queued Resources for deletion, run: + + $ gcloud alpha compute tpus queued-resources list + +EXAMPLES + To delete a Queued Resource in zone us-central1-b and project my-project, + run: + + $ gcloud alpha compute tpus queued-resources delete \ + --zone=us-central1-b --project=my-project + +POSITIONAL ARGUMENTS + Queued resource resource - The Queued Resource you want to delete. 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 queued_resource 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. + + QUEUED_RESOURCE + ID of the queued_resource or fully qualified identifier for the + queued_resource. To set the queued_resource attribute: + ▸ provide the argument queued_resource on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --zone=ZONE + The compute/zone of the Cloud TPU. + + If not specified, will use default compute/zone. + + To set the zone attribute: + ▸ provide the argument queued_resource on the command line with a + fully specified name; + ▸ provide the argument --zone on the command line; + ▸ set the property compute/zone. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the tpu/v2alpha1 API. The full documentation for this API + can be found at: https://cloud.google.com/tpu/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/tpus/queued-resources/describe b/gcloud/alpha/compute/tpus/queued-resources/describe new file mode 100644 index 000000000..8652ff930 --- /dev/null +++ b/gcloud/alpha/compute/tpus/queued-resources/describe @@ -0,0 +1,71 @@ +NAME + gcloud alpha compute tpus queued-resources describe - describe a Queued + Resource + +SYNOPSIS + gcloud alpha compute tpus queued-resources describe + (QUEUED_RESOURCE : --zone=ZONE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get details on a Queued Resource. + + To get a list of Queued Resources to describe in more detail, run: + + $ gcloud alpha compute tpus queued-resources list + +EXAMPLES + To describe a Queued Resource with ID my-queued-resource in zone + us-central1-b and project 'my-project', run: + + $ gcloud alpha compute tpus queued-resources describe \ + my-queued-resource --zone=us-central1-b --project=my-project + +POSITIONAL ARGUMENTS + Queued resource resource - The Queued Resource you want to describe. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: + ◆ provide the argument queued_resource 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. + + QUEUED_RESOURCE + ID of the queued_resource or fully qualified identifier for the + queued_resource. To set the queued_resource attribute: + ▸ provide the argument queued_resource on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --zone=ZONE + The compute/zone of the Cloud TPU. + + If not specified, will use default compute/zone. + + To set the zone attribute: + ▸ provide the argument queued_resource on the command line with a + fully specified name; + ▸ provide the argument --zone on the command line; + ▸ set the property compute/zone. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the tpu/v2alpha1 API. The full documentation for this API + can be found at: https://cloud.google.com/tpu/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/tpus/queued-resources/help b/gcloud/alpha/compute/tpus/queued-resources/help new file mode 100644 index 000000000..ea9a7c74e --- /dev/null +++ b/gcloud/alpha/compute/tpus/queued-resources/help @@ -0,0 +1,36 @@ +NAME + gcloud alpha compute tpus queued-resources - list, create, delete, and + manage Queued Resources + +SYNOPSIS + gcloud alpha compute tpus queued-resources COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List, create, delete, and manage Queued Resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a Queued Resource. + + delete + (ALPHA) Delete a Queued Resource. + + describe + (ALPHA) Describe a Queued Resource. + + list + (ALPHA) List Queued Resources. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/tpus/queued-resources/list b/gcloud/alpha/compute/tpus/queued-resources/list new file mode 100644 index 000000000..b14425045 --- /dev/null +++ b/gcloud/alpha/compute/tpus/queued-resources/list @@ -0,0 +1,89 @@ +NAME + gcloud alpha compute tpus queued-resources list - list Queued Resources + +SYNOPSIS + gcloud alpha compute tpus queued-resources list [--zone=ZONE] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all Queued Resources associated with a project and location. + +EXAMPLES + To list all Queued Resources available in zone us-central1-b for project + my-project, run: + + $ gcloud alpha compute tpus queued-resources list \ + --zone=us-central1-b --project=my-project + +FLAGS + Location resource - The compute/zone of the Queued Resource. + + If not specified, will use the value of the [compute/zone] property in the + current gcloud configuration. To find a list of compute zones available + for Cloud TPUs in your project, run gcloud alpha compute tpus + queued-resources locations list. 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; + ◆ set the property compute/zone with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --zone=ZONE + ID of the location or fully qualified identifier for the location. To + set the zone attribute: + ▸ provide the argument --zone on the command line; + ▸ set the property compute/zone. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the tpu/v2alpha1 API. The full documentation for this API + can be found at: https://cloud.google.com/tpu/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/tpus/tpu-vm/scp b/gcloud/alpha/compute/tpus/tpu-vm/scp index 6851ad6a6..e15515bee 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/scp +++ b/gcloud/alpha/compute/tpus/tpu-vm/scp @@ -4,10 +4,11 @@ NAME SYNOPSIS gcloud alpha compute tpus tpu-vm scp [[USER@]INSTANCE:]SRC [[[USER@]INSTANCE:]SRC ...] [[USER@]INSTANCE:]DEST [--compress] - [--dry-run] [--force-key-file-overwrite] [--internal-ip] [--plain] - [--recurse] [--scp-flag=SCP_FLAG] [--ssh-key-file=SSH_KEY_FILE] + [--dry-run] [--force-key-file-overwrite] [--plain] [--recurse] + [--scp-flag=SCP_FLAG] [--ssh-key-file=SSH_KEY_FILE] [--strict-host-key-checking=STRICT_HOST_KEY_CHECKING] [--worker=WORKER; default="0"] [--zone=ZONE] + [--internal-ip | --tunnel-through-iap] [--ssh-key-expiration=SSH_KEY_EXPIRATION | --ssh-key-expire-after=SSH_KEY_EXPIRE_AFTER] [GCLOUD_WIDE_FLAG ...] @@ -38,12 +39,6 @@ FLAGS regenerated and will fail in both interactive and non-interactive environments. - --internal-ip - Connect to TPU VMs using their internal IP addresses rather than their - external IP addresses. Use this to connect from a Google Compute Engine - VM to a TPU VM on the same VPC network, or between two peered VPC - networks. - --plain Suppress the automatic addition of ssh(1)/scp(1) flags. This flag is useful if you want to take care of authentication yourself or use @@ -98,6 +93,32 @@ FLAGS Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE. + At most one of these can be specified: + + --internal-ip + Connect to TPU VMs using their internal IP addresses rather than + their external IP addresses. Use this to connect from a Google + Compute Engine VM to a TPU VM on the same VPC network, or between two + peered VPC networks. + + --tunnel-through-iap + Tunnel the SSH connection through Cloud Identity-Aware Proxy for TCP + forwarding. + + This flag must be specified to attempt to connect via IAP tunneling. + If it is not set, and connection to a Cloud TPU VM without external + IP address is attempted from outside the network, then the command + will fail. + + To use IAP tunneling, there must be firewall access to the SSH port + for the IAP TCP IP address range for the network the TPU is created + in. See the user guide + (https://cloud.google.com/iap/docs/using-tcp-forwarding) for more + details. + + To learn more, see the IAP for TCP forwarding documentation + (https://cloud.google.com/iap/docs/tcp-forwarding-overview). + At most one of these can be specified: --ssh-key-expiration=SSH_KEY_EXPIRATION diff --git a/gcloud/alpha/compute/tpus/tpu-vm/ssh b/gcloud/alpha/compute/tpus/tpu-vm/ssh index 0efdccaaf..f3073d327 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/ssh +++ b/gcloud/alpha/compute/tpus/tpu-vm/ssh @@ -3,11 +3,12 @@ NAME SYNOPSIS gcloud alpha compute tpus tpu-vm ssh [USER@]TPU [--dry-run] - [--force-key-file-overwrite] [--internal-ip] [--plain] - [--ssh-flag=SSH_FLAG] [--ssh-key-file=SSH_KEY_FILE] + [--force-key-file-overwrite] [--plain] [--ssh-flag=SSH_FLAG] + [--ssh-key-file=SSH_KEY_FILE] [--strict-host-key-checking=STRICT_HOST_KEY_CHECKING] [--worker=WORKER; default="0"] [--zone=ZONE] [--command=COMMAND --output-directory=OUTPUT_DIRECTORY] + [--internal-ip | --tunnel-through-iap] [--ssh-key-expiration=SSH_KEY_EXPIRATION | --ssh-key-expire-after=SSH_KEY_EXPIRE_AFTER] [GCLOUD_WIDE_FLAG ...] [-- SSH_ARGS ...] @@ -47,12 +48,6 @@ FLAGS regenerated and will fail in both interactive and non-interactive environments. - --internal-ip - Connect to TPU VMs using their internal IP addresses rather than their - external IP addresses. Use this to connect from a Google Compute Engine - VM to a TPU VM on the same VPC network, or between two peered VPC - networks. - --plain Suppress the automatic addition of ssh(1)/scp(1) flags. This flag is useful if you want to take care of authentication yourself or use @@ -139,6 +134,32 @@ FLAGS The logs will be written in files named {WORKER_ID}.log. For example: "2.log". + At most one of these can be specified: + + --internal-ip + Connect to TPU VMs using their internal IP addresses rather than + their external IP addresses. Use this to connect from a Google + Compute Engine VM to a TPU VM on the same VPC network, or between two + peered VPC networks. + + --tunnel-through-iap + Tunnel the SSH connection through Cloud Identity-Aware Proxy for TCP + forwarding. + + This flag must be specified to attempt to connect via IAP tunneling. + If it is not set, and connection to a Cloud TPU VM without external + IP address is attempted from outside the network, then the command + will fail. + + To use IAP tunneling, there must be firewall access to the SSH port + for the IAP TCP IP address range for the network the TPU is created + in. See the user guide + (https://cloud.google.com/iap/docs/using-tcp-forwarding) for more + details. + + To learn more, see the IAP for TCP forwarding documentation + (https://cloud.google.com/iap/docs/tcp-forwarding-overview). + At most one of these can be specified: --ssh-key-expiration=SSH_KEY_EXPIRATION diff --git a/gcloud/alpha/compute/url-maps/export b/gcloud/alpha/compute/url-maps/export index 3a53d5e63..8d4baf0cf 100644 --- a/gcloud/alpha/compute/url-maps/export +++ b/gcloud/alpha/compute/url-maps/export @@ -21,10 +21,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/UrlMap.yaml. At most one of these can be specified: diff --git a/gcloud/alpha/compute/url-maps/import b/gcloud/alpha/compute/url-maps/import index 7308e0628..8da731c6d 100644 --- a/gcloud/alpha/compute/url-maps/import +++ b/gcloud/alpha/compute/url-maps/import @@ -19,10 +19,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/UrlMap.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index cae85c85f..d70540022 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -965,6 +965,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index 6542dd85a..ae7c8d2b4 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -970,6 +970,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 53ae400e6..9603316f2 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -983,6 +983,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 5effff6ed..3b7a0ea2c 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -944,6 +944,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index 4af1acf75..adab4153b 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -18,12 +18,14 @@ SYNOPSIS [--max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] - [--min-cpu-platform=PLATFORM] [--node-group=NODE_GROUP] - [--node-labels=[NODE_LABEL,...]] [--node-locations=ZONE,[ZONE,...]] - [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] - [--num-nodes=NUM_NODES; default=3] [--placement-type=PLACEMENT_TYPE] - [--preemptible] [--sandbox=[type=TYPE]] - [--shielded-integrity-monitoring] [--shielded-secure-boot] [--spot] + [--min-cpu-platform=PLATFORM] + [--network-performance-configs=[PROPERTY=VALUE,...]] + [--node-group=NODE_GROUP] [--node-labels=[NODE_LABEL,...]] + [--node-locations=ZONE,[ZONE,...]] [--node-taints=[NODE_TAINT,...]] + [--node-version=NODE_VERSION] [--num-nodes=NUM_NODES; default=3] + [--placement-type=PLACEMENT_TYPE] [--preemptible] + [--sandbox=[type=TYPE]] [--shielded-integrity-monitoring] + [--shielded-secure-boot] [--spot] [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--workload-metadata=WORKLOAD_METADATA] @@ -277,6 +279,17 @@ FLAGS CPU platform selection is available only in selected zones. + --network-performance-configs=[PROPERTY=VALUE,...] + Configures network performance settings for the node pool. If this flag + is not specified, the pool will be created with its default network + performance configuration. + + total-egress-bandwidth-tier + Total egress bandwidth is the available outbound bandwidth from a + VM, regardless of whether the traffic is going to internal IP or + external IP destinations. The following tier values are allowed: + [DEFAULT,TIER_1] + --node-group=NODE_GROUP Assign instances of this pool to run on the specified Google Compute Engine node group. This is useful for running workloads on sole tenant diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index 0bb8b6a30..1d050f0c3 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -5,8 +5,10 @@ NAME SYNOPSIS gcloud alpha container node-pools update NAME (--enable-confidential-nodes | --enable-gvnic - | --enable-image-streaming | --node-labels=[NODE_LABEL,...] - | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] + | --enable-image-streaming + | --network-performance-configs=[PROPERTY=VALUE,...] + | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] + | --node-taints=[NODE_TAINT,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE | --tags=[TAG,...] | --workload-metadata=WORKLOAD_METADATA | --enable-autoprovisioning @@ -46,6 +48,17 @@ REQUIRED FLAGS --enable-image-streaming Specifies whether to enable image streaming on node pool. + --network-performance-configs=[PROPERTY=VALUE,...] + Configures network performance settings for the node pool. If this + flag is not specified, the pool will be created with its default + network performance configuration. + + total-egress-bandwidth-tier + Total egress bandwidth is the available outbound bandwidth from a + VM, regardless of whether the traffic is going to internal IP or + external IP destinations. The following tier values are allowed: + [DEFAULT,TIER_1] + --node-labels=[NODE_LABEL,...] Replaces all the user specified Kubernetes labels on all nodes in an existing node pool with the given labels. diff --git a/gcloud/alpha/dataproc/autoscaling-policies/export b/gcloud/alpha/dataproc/autoscaling-policies/export index f24209e6b..e7526c17c 100644 --- a/gcloud/alpha/dataproc/autoscaling-policies/export +++ b/gcloud/alpha/dataproc/autoscaling-policies/export @@ -53,9 +53,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dataproc/autoscaling-policies/import b/gcloud/alpha/dataproc/autoscaling-policies/import index 887236037..27d84641b 100644 --- a/gcloud/alpha/dataproc/autoscaling-policies/import +++ b/gcloud/alpha/dataproc/autoscaling-policies/import @@ -57,9 +57,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input. + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dataproc/clusters/export b/gcloud/alpha/dataproc/clusters/export index 2c6c81a03..1561bf98d 100644 --- a/gcloud/alpha/dataproc/clusters/export +++ b/gcloud/alpha/dataproc/clusters/export @@ -54,9 +54,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dataproc/clusters/import b/gcloud/alpha/dataproc/clusters/import index 7fa219b55..a9a7b8cd1 100644 --- a/gcloud/alpha/dataproc/clusters/import +++ b/gcloud/alpha/dataproc/clusters/import @@ -57,9 +57,8 @@ FLAGS complete. --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input. + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dataproc/workflow-templates/export b/gcloud/alpha/dataproc/workflow-templates/export index 9d2c0cc3d..872bd1c43 100644 --- a/gcloud/alpha/dataproc/workflow-templates/export +++ b/gcloud/alpha/dataproc/workflow-templates/export @@ -52,9 +52,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. --version=VERSION The version of the workflow template. diff --git a/gcloud/alpha/dataproc/workflow-templates/import b/gcloud/alpha/dataproc/workflow-templates/import index 94d49d2ca..652907d99 100644 --- a/gcloud/alpha/dataproc/workflow-templates/import +++ b/gcloud/alpha/dataproc/workflow-templates/import @@ -45,9 +45,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input. + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/deploy/delivery-pipelines/export b/gcloud/alpha/deploy/delivery-pipelines/export index 2d6a69fec..a6dc1cf65 100644 --- a/gcloud/alpha/deploy/delivery-pipelines/export +++ b/gcloud/alpha/deploy/delivery-pipelines/export @@ -48,9 +48,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/deploy/targets/export b/gcloud/alpha/deploy/targets/export index 123d8fe0b..1a372db19 100644 --- a/gcloud/alpha/deploy/targets/export +++ b/gcloud/alpha/deploy/targets/export @@ -46,9 +46,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/edge-cloud/container/clusters/create b/gcloud/alpha/edge-cloud/container/clusters/create new file mode 100644 index 000000000..cd74f2ba2 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/create @@ -0,0 +1,136 @@ +NAME + gcloud alpha edge-cloud container clusters create - create an Edge + Container cluster + +SYNOPSIS + gcloud alpha edge-cloud container clusters create + (CLUSTER : --location=LOCATION) [--admin-users=ADMIN_USERS] [--async] + [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR; default="10.0.0.0/17"] + [--cluster-ipv6-cidr=CLUSTER_IPV6_CIDR] + [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] + [--fleet-project=FLEET_PROJECT] [--hub-membership=HUB_MEMBERSHIP] + [--labels=[KEY=VALUE,...]] + [--maintenance-window-end=MAINTENANCE_WINDOW_END] + [--maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE] + [--maintenance-window-start=MAINTENANCE_WINDOW_START] + [--services-ipv4-cidr=SERVICES_IPV4_CIDR; default="10.96.0.0/12"] + [--services-ipv6-cidr=SERVICES_IPV6_CIDR] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create an Edge Container cluster. + +EXAMPLES + To create a cluster called 'my-cluster' in region us-central1, run: + + $ gcloud alpha edge-cloud container clusters create my-cluster \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Cluster resource - Edge Container cluster to create. 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 cluster on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. To + set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +FLAGS + --admin-users=ADMIN_USERS + Username (Google email address) of the user who should be granted + cluster-admin initially. This currently supports exactly one admin. If + not set, the account issuing the creation request will be used by + default. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --cluster-ipv4-cidr=CLUSTER_IPV4_CIDR; default="10.0.0.0/17" + All pods in the cluster are assigned an RFC1918 IPv4 address from this + block. This field cannot be changed after creation. + + --cluster-ipv6-cidr=CLUSTER_IPV6_CIDR + If specified, all pods in the cluster are assigned an RFC4193 IPv6 + address from this block. This field cannot be changed after creation. + + --default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE + The default maximum number of pods per node. + + --fleet-project=FLEET_PROJECT + Name of the Fleet host project where the cluster is registered. + + --hub-membership=HUB_MEMBERSHIP + DEPRECATED - use --fleet-project instead. + + Name of the membership resource to use when registering this cluster + with GKE Hub. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + --maintenance-window-end=MAINTENANCE_WINDOW_END + End time of the recurring cluster maintenance window in the RFC 3339 + (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + + --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE + An RFC 5545 (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) + recurrence rule for how the cluster maintenance window recurs. They go + on for the span of time between the start and the end time. + + --maintenance-window-start=MAINTENANCE_WINDOW_START + Start time of the recurring cluster maintenance window in the RFC 3339 + (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + + --services-ipv4-cidr=SERVICES_IPV4_CIDR; default="10.96.0.0/12" + All services in the cluster are assigned an RFC1918 IPv4 address from + this block. This field cannot be changed after creation. + + --services-ipv6-cidr=SERVICES_IPV6_CIDR + If specified, all services in the cluster are assigned an RFC4193 IPv6 + address from this block. This field cannot be changed after creation. + +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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters create + diff --git a/gcloud/alpha/edge-cloud/container/clusters/delete b/gcloud/alpha/edge-cloud/container/clusters/delete new file mode 100644 index 000000000..150060753 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/delete @@ -0,0 +1,69 @@ +NAME + gcloud alpha edge-cloud container clusters delete - delete an Edge + Container cluster + +SYNOPSIS + gcloud alpha edge-cloud container clusters delete + (CLUSTER : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an Edge Container cluster. + +EXAMPLES + To delete a cluster called 'my-cluster' in region us-central1, run: + + $ gcloud alpha edge-cloud container clusters delete my-cluster \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Cluster resource - Edge Container cluster to delete. 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 cluster on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. To + set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters delete + diff --git a/gcloud/alpha/edge-cloud/container/clusters/describe b/gcloud/alpha/edge-cloud/container/clusters/describe new file mode 100644 index 000000000..fe53ad408 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/describe @@ -0,0 +1,65 @@ +NAME + gcloud alpha edge-cloud container clusters describe - show details about + the cluster + +SYNOPSIS + gcloud alpha edge-cloud container clusters describe + (CLUSTER : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show details about the cluster. + +EXAMPLES + To show details about a cluster called 'my-cluster' in region us-central1, + run: + + $ gcloud alpha edge-cloud container clusters describe my-cluster \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Cluster resource - The cluster you want to describe. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. To + set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters describe + diff --git a/gcloud/alpha/edge-cloud/container/clusters/get-credentials b/gcloud/alpha/edge-cloud/container/clusters/get-credentials new file mode 100644 index 000000000..1009193d8 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/get-credentials @@ -0,0 +1,76 @@ +NAME + gcloud alpha edge-cloud container clusters get-credentials - get + credentials of an edge-container cluster + +SYNOPSIS + gcloud alpha edge-cloud container clusters get-credentials + (CLUSTER : --location=LOCATION) + [--auth-provider-cmd-path=AUTH_PROVIDER_CMD_PATH] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Fetch credentials for a running Edge Container cluster. This + command updates a kubeconfig file with appropriate credentials and endpoint + information to point kubectl at a specific Edge Container cluster. By + default, credentials are written to HOME/.kube/config. You can provide an + alternate path by setting the KUBECONFIG environment variable. If + KUBECONFIG contains multiple paths, the first one is used. This command + enables switching to a specific cluster, when working with multiple + clusters. It can also be used to access a previously created cluster from a + new workstation. The command will configure kubectl to automatically + refresh its credentials using the same identity as the gcloud command-line + tool. See https://cloud.google.com/kubernetes-engine/docs/kubectl for + kubectl documentation. + +EXAMPLES + To get credentials of a cluster named my-cluster managed in location + us-west1, run: $ gcloud alpha edge-cloud container clusters get-credentials \ + my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Cluster resource - edge-cloud container cluster to get credentials. 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 cluster 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. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. To + set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --auth-provider-cmd-path=AUTH_PROVIDER_CMD_PATH + Path to the gcloud executable for the auth provider field in + kubeconfig. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters get-credentials + diff --git a/gcloud/alpha/edge-cloud/container/clusters/help b/gcloud/alpha/edge-cloud/container/clusters/help new file mode 100644 index 000000000..1831ed48f --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/help @@ -0,0 +1,51 @@ +NAME + gcloud alpha edge-cloud container clusters - manage Kubernetes Edge + clusters + +SYNOPSIS + gcloud alpha edge-cloud container clusters GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Kubernetes Edge clusters. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + node-pools + (ALPHA) Manage Kubernetes Edge node pools. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create an Edge Container cluster. + + delete + (ALPHA) Delete an Edge Container cluster. + + describe + (ALPHA) Show details about the cluster. + + get-credentials + (ALPHA) Get credentials of an edge-container cluster. + + list + (ALPHA) List Edge Container clusters. + + update + (ALPHA) Update an Edge Container cluster. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters + diff --git a/gcloud/alpha/edge-cloud/container/clusters/list b/gcloud/alpha/edge-cloud/container/clusters/list new file mode 100644 index 000000000..7e1a2ebaf --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/list @@ -0,0 +1,87 @@ +NAME + gcloud alpha edge-cloud container clusters list - list Edge Container + clusters + +SYNOPSIS + gcloud alpha edge-cloud container clusters list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Edge Container clusters. + +EXAMPLES + To list the clusters in region us-central1, run: + + $ gcloud alpha edge-cloud container clusters list \ + --location=us-central1 + +FLAGS + Location resource - Parent Edge Container location to list all contained + Edge Container clusters. 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; + ◆ set the property edge_container/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; + ▸ set the property edge_container/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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters list + diff --git a/gcloud/alpha/edge-cloud/container/clusters/node-pools/create b/gcloud/alpha/edge-cloud/container/clusters/node-pools/create new file mode 100644 index 000000000..cffcbec07 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/node-pools/create @@ -0,0 +1,123 @@ +NAME + gcloud alpha edge-cloud container clusters node-pools create - create an + Edge Container node pool + +SYNOPSIS + gcloud alpha edge-cloud container clusters node-pools create + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) + --node-count=NODE_COUNT --node-location=NODE_LOCATION [--async] + [--labels=[KEY=VALUE,...]] [--local-disk-kms-key=LOCAL_DISK_KMS_KEY] + [--machine-filter=MACHINE_FILTER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new Edge Container nodePool. + +EXAMPLES + To create a node pool called 'my-nodePool', containing 3 nodes in region + us-central1, run: + + $ gcloud alpha edge-cloud container clusters node-pools create \ + my-nodePool --cluster= --location=us-central1 \ + --node-location= --node-count=3 + + To create a node pool called 'my-nodePool', containing 3 nodes in region + us-central1, using only machine names matching a specific pattern, run: + + $ gcloud alpha edge-cloud container clusters node-pools create \ + my-nodePool --cluster= --location=us-central1 \ + --node-location= --node-count=3 \ + --machine-filter="name:" + + To create a node pool called 'my-nodePool', containing 3 nodes in region + us-central1, using only machine names NOT matching a specific pattern, run: + + $ gcloud alpha edge-cloud container clusters node-pools create \ + my-nodePool --cluster= --location=us-central1 \ + --node-location= --node-count=3 \ + --machine-filter="NOT name:" + +POSITIONAL ARGUMENTS + Node pool resource - Edge Container node pool to create. 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 node_pool on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NODE_POOL + ID of the node pool or fully qualified identifier for the node pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --cluster=CLUSTER + Kubernetes cluster. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +REQUIRED FLAGS + --node-count=NODE_COUNT + Default nodeCount used by this node pool. + + --node-location=NODE_LOCATION + Google Edge Cloud zone where nodes in this node pool will be created. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + --local-disk-kms-key=LOCAL_DISK_KMS_KEY + Google Cloud KMS key that will be used to secure local disks on nodes + in this node pool. The Edge Container service account for this project + must have roles/cloudkms.cryptoKeyEncrypterDecrypter on the key. + + If not provided, a Google-managed key will be used instead. + + --machine-filter=MACHINE_FILTER + Only machines matching this filter will be allowed to join the node + pool. The filtering language accepts strings like "name=", and is + documented in more detail at https://google.aip.dev/160. + +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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters node-pools create + diff --git a/gcloud/alpha/edge-cloud/container/clusters/node-pools/delete b/gcloud/alpha/edge-cloud/container/clusters/node-pools/delete new file mode 100644 index 000000000..111f8aaf4 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/node-pools/delete @@ -0,0 +1,76 @@ +NAME + gcloud alpha edge-cloud container clusters node-pools delete - delete an + Edge Container nodePool + +SYNOPSIS + gcloud alpha edge-cloud container clusters node-pools delete + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an Edge Container nodePool. + +EXAMPLES + To delete a nodePool called 'my-nodePool' in region us-central1, run: + + $ gcloud alpha edge-cloud container clusters node-pools delete \ + my-nodePool --cluster= --location=us-central1 + +POSITIONAL ARGUMENTS + Node pool resource - Edge Container nodePool to delete. 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 node_pool on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NODE_POOL + ID of the node pool or fully qualified identifier for the node pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --cluster=CLUSTER + Kubernetes cluster. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters node-pools delete + diff --git a/gcloud/alpha/edge-cloud/container/clusters/node-pools/describe b/gcloud/alpha/edge-cloud/container/clusters/node-pools/describe new file mode 100644 index 000000000..196231312 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/node-pools/describe @@ -0,0 +1,72 @@ +NAME + gcloud alpha edge-cloud container clusters node-pools describe - show + details about the nodePool + +SYNOPSIS + gcloud alpha edge-cloud container clusters node-pools describe + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show details about the nodePool. + +EXAMPLES + To show details about a node pool called 'my-nodePool' in region + us-central1, run: + + $ gcloud alpha edge-cloud container clusters node-pools describe \ + my-nodePool --location=us-central1 --cluster= + +POSITIONAL ARGUMENTS + Node pool resource - The nodePool you want to describe. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. To set the project attribute: + ◆ provide the argument node_pool on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NODE_POOL + ID of the node pool or fully qualified identifier for the node pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --cluster=CLUSTER + Kubernetes cluster. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters node-pools describe + diff --git a/gcloud/alpha/edge-cloud/container/clusters/node-pools/help b/gcloud/alpha/edge-cloud/container/clusters/node-pools/help new file mode 100644 index 000000000..0e2704955 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/node-pools/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha edge-cloud container clusters node-pools - manage Kubernetes + Edge node pools + +SYNOPSIS + gcloud alpha edge-cloud container clusters node-pools COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Kubernetes Edge node pools. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create an Edge Container node pool. + + delete + (ALPHA) Delete an Edge Container nodePool. + + describe + (ALPHA) Show details about the nodePool. + + list + (ALPHA) List Edge Container nodePools. + + update + (ALPHA) Updates an Edge Container node pool. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters node-pools + diff --git a/gcloud/alpha/edge-cloud/container/clusters/node-pools/list b/gcloud/alpha/edge-cloud/container/clusters/node-pools/list new file mode 100644 index 000000000..6a11773fc --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/node-pools/list @@ -0,0 +1,99 @@ +NAME + gcloud alpha edge-cloud container clusters node-pools list - list Edge + Container nodePools + +SYNOPSIS + gcloud alpha edge-cloud container clusters node-pools list + (--cluster=CLUSTER : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Edge Container nodePools. + +EXAMPLES + To list the nodePools in region us-central1, run: + + $ gcloud alpha edge-cloud container clusters node-pools list \ + --location=us-central1 --cluster= + +REQUIRED FLAGS + Cluster resource - Parent Edge Container location to list all contained + Edge Container nodePools. 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 --cluster on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. To + set the cluster attribute: + ▸ provide the argument --cluster on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument --cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters node-pools list + diff --git a/gcloud/alpha/edge-cloud/container/clusters/node-pools/update b/gcloud/alpha/edge-cloud/container/clusters/node-pools/update new file mode 100644 index 000000000..1152f0f73 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/node-pools/update @@ -0,0 +1,118 @@ +NAME + gcloud alpha edge-cloud container clusters node-pools update - updates an + Edge Container node pool + +SYNOPSIS + gcloud alpha edge-cloud container clusters node-pools update + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] + [--machine-filter=MACHINE_FILTER] [--node-count=NODE_COUNT] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates an Edge Container node pool. + +EXAMPLES + To update the number of nodes in a node pool called 'my-node-pool' in + region us-central1, run: + + $ gcloud alpha edge-cloud container clusters node-pools update \ + my-node-pool --location=us-central1 --cluster= \ + --node-count= + +POSITIONAL ARGUMENTS + Node pool resource - Edge Container node pool 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 node_pool on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NODE_POOL + ID of the node pool or fully qualified identifier for the node pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --cluster=CLUSTER + Kubernetes cluster. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --machine-filter=MACHINE_FILTER + Only machines matching this filter will be allowed to join the node + pool. The filtering language accepts strings like "name=", and is + documented in more detail at https://google.aip.dev/160. + + --node-count=NODE_COUNT + Default nodeCount used by this node pool. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha edge-cloud container clusters node-pools update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha edge-cloud container clusters node-pools update \ + --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters node-pools update + diff --git a/gcloud/alpha/edge-cloud/container/clusters/update b/gcloud/alpha/edge-cloud/container/clusters/update new file mode 100644 index 000000000..c8855fa6e --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/update @@ -0,0 +1,90 @@ +NAME + gcloud alpha edge-cloud container clusters update - update an Edge + Container cluster + +SYNOPSIS + gcloud alpha edge-cloud container clusters update + (CLUSTER : --location=LOCATION) [--async] + [--maintenance-window-end=MAINTENANCE_WINDOW_END] + [--maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE] + [--maintenance-window-start=MAINTENANCE_WINDOW_START] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an Edge Container cluster. + +EXAMPLES + To update the maintenance window recurrence rule of a cluster called + 'my-cluster' in region us-central1, run: + + $ gcloud alpha edge-cloud container clusters update my-cluster \ + --location=us-central1 \ + --maintenance-window-recurrence="FREQ=WEEKLY" + +POSITIONAL ARGUMENTS + Cluster resource - Edge Container cluster 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 cluster on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. To + set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --maintenance-window-end=MAINTENANCE_WINDOW_END + End time of the recurring cluster maintenance window in the RFC 3339 + (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + + --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE + An RFC 5545 (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) + recurrence rule for how the cluster maintenance window recurs. They go + on for the span of time between the start and the end time. + + --maintenance-window-start=MAINTENANCE_WINDOW_START + Start time of the recurring cluster maintenance window in the RFC 3339 + (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + +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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters update + diff --git a/gcloud/alpha/edge-cloud/container/help b/gcloud/alpha/edge-cloud/container/help new file mode 100644 index 000000000..416ef92b1 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/help @@ -0,0 +1,44 @@ +NAME + gcloud alpha edge-cloud container - manage Edge Container resources + +SYNOPSIS + gcloud alpha edge-cloud container GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Edge Container resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + clusters + (ALPHA) Manage Kubernetes Edge clusters. + + machines + (ALPHA) Manage Kubernetes Edge machines. + + operations + (ALPHA) Command group for working with Kubernetes Edge operations. + + regions + (ALPHA) Manages Edge Container regions. + + vpn-connections + (ALPHA) Manage Edge VPN connections between an Edge Container cluster + and a VPC network. + + zones + (ALPHA) Inspect Edge Container zones. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container + diff --git a/gcloud/alpha/edge-cloud/container/machines/describe b/gcloud/alpha/edge-cloud/container/machines/describe new file mode 100644 index 000000000..5de213868 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/machines/describe @@ -0,0 +1,65 @@ +NAME + gcloud alpha edge-cloud container machines describe - show details about + the machine + +SYNOPSIS + gcloud alpha edge-cloud container machines describe + (MACHINE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show details about the machine. + +EXAMPLES + To show details about a machine called 'my-machine' in region us-central1, + run: + + $ gcloud alpha edge-cloud container machines describe my-machine \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Machine resource - The machine you want to describe. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. To set the project attribute: + ◆ provide the argument machine on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + MACHINE + ID of the machine or fully qualified identifier for the machine. To + set the machine attribute: + ▸ provide the argument machine on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument machine on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container machines describe + diff --git a/gcloud/alpha/edge-cloud/container/machines/help b/gcloud/alpha/edge-cloud/container/machines/help new file mode 100644 index 000000000..de0052974 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/machines/help @@ -0,0 +1,32 @@ +NAME + gcloud alpha edge-cloud container machines - manage Kubernetes Edge + machines + +SYNOPSIS + gcloud alpha edge-cloud container machines COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Kubernetes Edge machines. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Show details about the machine. + + list + (ALPHA) List Edge Container machines. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container machines + diff --git a/gcloud/alpha/edge-cloud/container/machines/list b/gcloud/alpha/edge-cloud/container/machines/list new file mode 100644 index 000000000..fd66a354e --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/machines/list @@ -0,0 +1,87 @@ +NAME + gcloud alpha edge-cloud container machines list - list Edge Container + machines + +SYNOPSIS + gcloud alpha edge-cloud container machines list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Edge Container machines. + +EXAMPLES + To list the machines in region us-central1, run: + + $ gcloud alpha edge-cloud container machines list \ + --location=us-central1 + +FLAGS + Location resource - Parent Edge Container location to list all contained + Edge Container machines. 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; + ◆ set the property edge_container/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; + ▸ set the property edge_container/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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container machines list + diff --git a/gcloud/alpha/edge-cloud/container/operations/describe b/gcloud/alpha/edge-cloud/container/operations/describe new file mode 100644 index 000000000..10587dda6 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/operations/describe @@ -0,0 +1,66 @@ +NAME + gcloud alpha edge-cloud container operations describe - get description of + a long-running edge container operation + +SYNOPSIS + gcloud alpha edge-cloud container operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get information about a long-running edge container operation. + +EXAMPLES + To get information about a long-running operation with name + 'projects/my-project/locations/us-east1/operations/123', run the following + command: + + $ gcloud alpha edge-cloud container operations describe \ + projects/my-project/locations/us-east1/operations/123 + +POSITIONAL ARGUMENTS + Operation resource - The ID of the operation to describe. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. To set the project attribute: + ◆ provide the argument operation on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. 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; + ▸ set the property edge_container/location. + +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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container operations describe + diff --git a/gcloud/alpha/edge-cloud/container/operations/help b/gcloud/alpha/edge-cloud/container/operations/help new file mode 100644 index 000000000..9a5a5119a --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/operations/help @@ -0,0 +1,32 @@ +NAME + gcloud alpha edge-cloud container operations - command group for working + with Kubernetes Edge operations + +SYNOPSIS + gcloud alpha edge-cloud container operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Command group for working with Kubernetes Edge operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Get description of a long-running edge container operation. + + wait + (ALPHA) Poll long-running edge container operation until it completes. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container operations + diff --git a/gcloud/alpha/edge-cloud/container/operations/wait b/gcloud/alpha/edge-cloud/container/operations/wait new file mode 100644 index 000000000..f21c52be3 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/operations/wait @@ -0,0 +1,68 @@ +NAME + gcloud alpha edge-cloud container operations wait - poll long-running edge + container operation until it completes + +SYNOPSIS + gcloud alpha edge-cloud container operations wait + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Poll a long-running edge container operation until it completes. + When the operation is complete, this command will display the results of + the analysis. + +EXAMPLES + To poll a long-running edge container operation named + 'projects/my-project/locations/us-east1/operations/123' until it completes, + run the following: + + $ gcloud alpha edge-cloud container operations wait \ + projects/my-project/locations/us-east1/operations/123 + +POSITIONAL ARGUMENTS + Operation resource - ID for the operation to poll until complete. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: + ◆ provide the argument operation on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. 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; + ▸ set the property edge_container/location. + +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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container operations wait + diff --git a/gcloud/alpha/edge-cloud/container/regions/describe b/gcloud/alpha/edge-cloud/container/regions/describe new file mode 100644 index 000000000..e92adbd4f --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/regions/describe @@ -0,0 +1,52 @@ +NAME + gcloud alpha edge-cloud container regions describe - describe an Edge + Container region (location) + +SYNOPSIS + gcloud alpha edge-cloud container regions describe [LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe an Edge Container region (location). + +EXAMPLES + To display the metadata for the region us-central1, run: + + $ gcloud alpha edge-cloud container regions describe us-central1 + +POSITIONAL ARGUMENTS + Location resource - The region to describe. 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; + ◆ set the property edge_container/location with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + [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; + ▸ set the property edge_container/location. + +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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container regions describe + diff --git a/gcloud/alpha/edge-cloud/container/regions/help b/gcloud/alpha/edge-cloud/container/regions/help new file mode 100644 index 000000000..086bb7f53 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/regions/help @@ -0,0 +1,31 @@ +NAME + gcloud alpha edge-cloud container regions - manages Edge Container regions + +SYNOPSIS + gcloud alpha edge-cloud container regions COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manages Edge Container regions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe an Edge Container region (location). + + list + (ALPHA) List Edge Container regions. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container regions + diff --git a/gcloud/alpha/edge-cloud/container/regions/list b/gcloud/alpha/edge-cloud/container/regions/list new file mode 100644 index 000000000..5ceae2790 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/regions/list @@ -0,0 +1,71 @@ +NAME + gcloud alpha edge-cloud container regions list - list Edge Container + regions + +SYNOPSIS + gcloud alpha edge-cloud container regions list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all regions (locations) where Edge Container clusters can be + created. + +EXAMPLES + To list all the regions (locations) where Edge Container clusters can be + created, run: + + $ gcloud alpha edge-cloud container regions list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container regions list + diff --git a/gcloud/alpha/edge-cloud/container/vpn-connections/create b/gcloud/alpha/edge-cloud/container/vpn-connections/create new file mode 100644 index 000000000..ccbbdf835 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/vpn-connections/create @@ -0,0 +1,101 @@ +NAME + gcloud alpha edge-cloud container vpn-connections create - create a VPN + connection between an Edge Container cluster and a VPC network + +SYNOPSIS + gcloud alpha edge-cloud container vpn-connections create + (VPN_CONNECTION : --location=LOCATION) --cluster=CLUSTER + --vpc-network=VPC_NETWORK [--async] [--high-availability] + [--labels=[KEY=VALUE,...]] [--nat-gateway-ip=NAT_GATEWAY_IP] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Creates a new VPN connection. + +EXAMPLES + To create a connection called 'my-vpn-connection' between the VPC network + 'my-vpc' and the Edge Container cluster 'my-cluster' which is at region + us-central1, run: + + $ gcloud alpha edge-cloud container vpn-connections create \ + my-vpn-connection --location=us-central1 \ + --vpc-network='my-vpc' --cluster='my-cluster' + + Here VPC network and cluster should be under the same project. + +POSITIONAL ARGUMENTS + Vpn connection resource - VPN connection to create. 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 vpn_connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + VPN_CONNECTION + ID of the vpn connection or fully qualified identifier for the vpn + connection. To set the vpn_connection attribute: + ▸ provide the argument vpn_connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument vpn_connection on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +REQUIRED FLAGS + --cluster=CLUSTER + The name of the cluster to be connected under current project. + + --vpc-network=VPC_NETWORK + The name of the {vpc_name_short} to be connected under current project. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --high-availability + Enables high availability on cluster side. This creates an additional + VPN endpoint in cluster. Multiple Nodes/NodePools are required to + enable this feature. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + --nat-gateway-ip=NAT_GATEWAY_IP + The NAT gateway IP for the gateway floating IPs. Do not specify this if + no NAT is used. + +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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container vpn-connections create + diff --git a/gcloud/alpha/edge-cloud/container/vpn-connections/delete b/gcloud/alpha/edge-cloud/container/vpn-connections/delete new file mode 100644 index 000000000..ef7b7c626 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/vpn-connections/delete @@ -0,0 +1,70 @@ +NAME + gcloud alpha edge-cloud container vpn-connections delete - delete a VPN + connection between an Edge Container cluster and a VPC network + +SYNOPSIS + gcloud alpha edge-cloud container vpn-connections delete + (VPN_CONNECTION : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a VPN connection. + +EXAMPLES + To delete a VPN connection called 'test-vpn-connection' at region + 'us-central1', run: + + $ gcloud alpha edge-cloud container vpn-connections delete \ + test-vpn-connection --location=us-central1 + +POSITIONAL ARGUMENTS + Vpn connection resource - VPN connection to delete. 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 vpn_connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + VPN_CONNECTION + ID of the vpn connection or fully qualified identifier for the vpn + connection. To set the vpn_connection attribute: + ▸ provide the argument vpn_connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument vpn_connection on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container vpn-connections delete + diff --git a/gcloud/alpha/edge-cloud/container/vpn-connections/describe b/gcloud/alpha/edge-cloud/container/vpn-connections/describe new file mode 100644 index 000000000..3d5d22f48 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/vpn-connections/describe @@ -0,0 +1,65 @@ +NAME + gcloud alpha edge-cloud container vpn-connections describe - show details + about a VPN connection + +SYNOPSIS + gcloud alpha edge-cloud container vpn-connections describe + (VPN_CONNECTION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show details about a VPN connection. + +EXAMPLES + To show details about the VPN connection 'test-vpn-connection' at region + us-central1, run: + + $ gcloud alpha edge-cloud container vpn-connections describe \ + test-vpn-connection --location=us-central1 + +POSITIONAL ARGUMENTS + Vpn connection resource - VPN connection you want to describe. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: + ◆ provide the argument vpn_connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + VPN_CONNECTION + ID of the vpn connection or fully qualified identifier for the vpn + connection. To set the vpn_connection attribute: + ▸ provide the argument vpn_connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument vpn_connection on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container vpn-connections describe + diff --git a/gcloud/alpha/edge-cloud/container/vpn-connections/help b/gcloud/alpha/edge-cloud/container/vpn-connections/help new file mode 100644 index 000000000..4439a47bb --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/vpn-connections/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha edge-cloud container vpn-connections - manage Edge VPN + connections between an Edge Container cluster and a VPC network + +SYNOPSIS + gcloud alpha edge-cloud container vpn-connections COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Edge VPN connections between an Edge Container cluster and a + VPC network. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a VPN connection between an Edge Container cluster and a + VPC network. + + delete + (ALPHA) Delete a VPN connection between an Edge Container cluster and a + VPC network. + + describe + (ALPHA) Show details about a VPN connection. + + list + (ALPHA) List VPN connections. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container vpn-connections + diff --git a/gcloud/alpha/edge-cloud/container/vpn-connections/list b/gcloud/alpha/edge-cloud/container/vpn-connections/list new file mode 100644 index 000000000..f40a39a7c --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/vpn-connections/list @@ -0,0 +1,88 @@ +NAME + gcloud alpha edge-cloud container vpn-connections list - list VPN + connections + +SYNOPSIS + gcloud alpha edge-cloud container vpn-connections list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List VPN connections. + +EXAMPLES + To list the VPN connections at region us-central1, run: + + $ gcloud alpha edge-cloud container vpn-connections list \ + --location=us-central + +FLAGS + Location resource - Parent location to list all contained VPN connections. + 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; + ◆ set the property edge_container/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; + ▸ set the property edge_container/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 edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container vpn-connections list + diff --git a/gcloud/alpha/edge-cloud/container/zones/describe b/gcloud/alpha/edge-cloud/container/zones/describe new file mode 100644 index 000000000..4054c2763 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/zones/describe @@ -0,0 +1,53 @@ +NAME + gcloud alpha edge-cloud container zones describe - describe an Edge + Container zone + +SYNOPSIS + gcloud alpha edge-cloud container zones describe ZONE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe an Edge Container zone. + +EXAMPLES + To display the metadata for the zone us-central1-edge-operator-a, run: + + $ gcloud alpha edge-cloud container zones describe \ + us-central1-edge-operator-a + +POSITIONAL ARGUMENTS + Zone resource - The zone name. 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; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + 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. + +API REFERENCE + This command uses the edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container zones describe + diff --git a/gcloud/alpha/edge-cloud/container/zones/help b/gcloud/alpha/edge-cloud/container/zones/help new file mode 100644 index 000000000..01bc3840f --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/zones/help @@ -0,0 +1,31 @@ +NAME + gcloud alpha edge-cloud container zones - inspect Edge Container zones + +SYNOPSIS + gcloud alpha edge-cloud container zones COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Inspect Edge Container zones. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe an Edge Container zone. + + list + (ALPHA) List Edge Container zones. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container zones + diff --git a/gcloud/alpha/edge-cloud/container/zones/list b/gcloud/alpha/edge-cloud/container/zones/list new file mode 100644 index 000000000..d4cdf284e --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/zones/list @@ -0,0 +1,62 @@ +NAME + gcloud alpha edge-cloud container zones list - list Edge Container zones + +SYNOPSIS + gcloud alpha edge-cloud container zones list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all zones where Edge Container node pools can be created. + +EXAMPLES + To list all the zones where Edge Container node pools can be created, run: + + $ gcloud alpha edge-cloud container zones list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container zones list + diff --git a/gcloud/alpha/edge-cloud/help b/gcloud/alpha/edge-cloud/help new file mode 100644 index 000000000..9aa000a98 --- /dev/null +++ b/gcloud/alpha/edge-cloud/help @@ -0,0 +1,28 @@ +NAME + gcloud alpha edge-cloud - manage edge-cloud resources + +SYNOPSIS + gcloud alpha edge-cloud GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage edge-cloud resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + container + (ALPHA) Manage Edge Container resources. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud + diff --git a/gcloud/alpha/resource-manager/tags/help b/gcloud/alpha/resource-manager/tags/help index 8d74e0b0d..acd834872 100644 --- a/gcloud/alpha/resource-manager/tags/help +++ b/gcloud/alpha/resource-manager/tags/help @@ -22,6 +22,9 @@ GROUPS bindings (ALPHA) Create and manipulate TagBindings. + holds + (ALPHA) Create and manipulate TagHolds. + keys (ALPHA) Create and manipulate TagKeys. diff --git a/gcloud/alpha/resource-manager/tags/holds/create b/gcloud/alpha/resource-manager/tags/holds/create new file mode 100644 index 000000000..e9e3f9ceb --- /dev/null +++ b/gcloud/alpha/resource-manager/tags/holds/create @@ -0,0 +1,65 @@ +NAME + gcloud alpha resource-manager tags holds create - create a TagHold resource + +SYNOPSIS + gcloud alpha resource-manager tags holds create PARENT --holder=HOLDER + [--help-link=HELP_LINK] [--location=LOCATION] [--origin=ORIGIN] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a TagHold under a TagValue, indicating that the TagValue is + being used by a holder (cloud resource) from an (optional) origin. The + TagValue can be represented with its numeric id or its namespaced name of + {org_id}/{tag_key_short_name}/{tag_value_short_name}. + +EXAMPLES + To create a TagHold on tagValues/123, with holder cloud-resource-holder, + origin creator-origin, in region us-central1-a, with help link + www.example.help.link.com, run: + + $ gcloud alpha resource-manager tags holds create tagValues/123 \ + --holder=cloud-resource-holder --origin=creator-origin \ + --help-link=www.example.help.link.com --location=us-central1-a + + To create a TagHold under TagValue test under TagKey env in organization id + 789, with holder cloud-resource-holder, run: + + $ gcloud alpha resource-manager tags holds create 789/env/test \ + --holder=cloud-resource-holder + +POSITIONAL ARGUMENTS + PARENT + Tag value name or namespaced name. + +REQUIRED FLAGS + --holder=HOLDER + The name of the resource where the TagValue is being used. Must be less + than 200 characters. + +OPTIONAL FLAGS + --help-link=HELP_LINK + A URL where an end user can learn more about removing this hold. + + --location=LOCATION + Region or zone where the TagHold will be stored. If not provided, the + TagHold will be stored in a "global" region. + + --origin=ORIGIN + An optional string representing the origin of this request. This field + should include human-understandable information to distinguish origins + from each other. Must be less than 200 characters. + +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/resource-manager/tags/holds/delete b/gcloud/alpha/resource-manager/tags/holds/delete new file mode 100644 index 000000000..54744873f --- /dev/null +++ b/gcloud/alpha/resource-manager/tags/holds/delete @@ -0,0 +1,43 @@ +NAME + gcloud alpha resource-manager tags holds delete - delete a TagHold + +SYNOPSIS + gcloud alpha resource-manager tags holds delete TAG_HOLD_NAME + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a TagHold given its full name, specified as + tagValues/{tag_value_id}/tagHolds/{tag_hold_id}. + +EXAMPLES + To delete a TagHold under tagValue/111 with id abc-123-def in region + us-central1-a, run: + + $ gcloud alpha resource-manager tags holds delete \ + tagValue/111/tagHolds/abc-123-def --location=us-central1-a + +POSITIONAL ARGUMENTS + TAG_HOLD_NAME + TagHold given its full name, specified as + tagValues/{tag_value_id}/tagHolds/{tag_hold_id} + +FLAGS + --location=LOCATION + Region where the TagHold is stored. If not provided, the API will + attempt to find and delete the specified TagHold from the "global" + 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/resource-manager/tags/holds/help b/gcloud/alpha/resource-manager/tags/holds/help new file mode 100644 index 000000000..11fc38a2d --- /dev/null +++ b/gcloud/alpha/resource-manager/tags/holds/help @@ -0,0 +1,35 @@ +NAME + gcloud alpha resource-manager tags holds - create and manipulate TagHolds + +SYNOPSIS + gcloud alpha resource-manager tags holds COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The Resource Manager Service gives you centralized and programmatic + control over your organization's Tags. As the tag administrator, you will + be able to create and configure restrictions across the tags in the org, + and you will be able to indicate the use of a TagValue as a TagHold. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a TagHold resource. + + delete + (ALPHA) Delete a TagHold. + + list + (ALPHA) List TagHolds under the specified TagValue. + +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/resource-manager/tags/holds/list b/gcloud/alpha/resource-manager/tags/holds/list new file mode 100644 index 000000000..5d9811c22 --- /dev/null +++ b/gcloud/alpha/resource-manager/tags/holds/list @@ -0,0 +1,96 @@ +NAME + gcloud alpha resource-manager tags holds list - list TagHolds under the + specified TagValue + +SYNOPSIS + gcloud alpha resource-manager tags holds list PARENT [--holder=HOLDER] + [--location=LOCATION] [--origin=ORIGIN] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List TagHolds under a TagValue. The TagValue can be represented + with its numeric id or its namespaced name of + {org_id}/{tag_key_short_name}/{tag_value_short_name}. Limited to TagHolds + stored in a single --location: if none is provided, the API will assume the + "global" location. Optional filters are --holder and --origin: if provided, + returned TagHolds' holder and origin fields must match the exact flag + value. + +EXAMPLES + To list TagHolds for tagValues/456 in us-central1-a, run: + + $ gcloud alpha resource-manager tags holds list tagValues/456 \ + --location=us-central1-a + + To list TagHolds for tagValues/456, with holder cloud-holder-resource and + origin creator-origin, run: + + $ gcloud alpha resource-manager tags holds list tagValues/456 \ + --holder=cloud-holder-resource --origin=creator-origin + +POSITIONAL ARGUMENTS + PARENT + TagValue resource name or namespaced name to list TagHolds for. This + field should be in the form tagValues/ or + //. + +FLAGS + --holder=HOLDER + The holder field of the TagHold to match exactly. If not provided, the + API will return all matching TagHolds disregarding the holder field. + + --location=LOCATION + Region where the matching TagHolds are stored. If not provided, the API + will attempt to retrieve matching TagHolds from the "global" region. + + --origin=ORIGIN + The origin field of the TagHold to match exactly. If not provided, the + API will return all matching TagHolds disregarding the origin field. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/spanner/backups/add-iam-policy-binding b/gcloud/alpha/spanner/backups/add-iam-policy-binding index f47c4f589..5922e5638 100644 --- a/gcloud/alpha/spanner/backups/add-iam-policy-binding +++ b/gcloud/alpha/spanner/backups/add-iam-policy-binding @@ -9,9 +9,8 @@ SYNOPSIS | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Add an IAM policy binding to the IAM policy of Cloud Spanner - backup. One binding consists of a member, a role, and an optional - condition. + (ALPHA) Add an IAM policy binding to a Cloud Spanner backup. One binding + consists of a member, a role, and an optional condition. EXAMPLES To add an IAM policy binding for the role of 'roles/spanner.backupAdmin' diff --git a/gcloud/alpha/spanner/backups/copy b/gcloud/alpha/spanner/backups/copy new file mode 100644 index 000000000..14b52ea67 --- /dev/null +++ b/gcloud/alpha/spanner/backups/copy @@ -0,0 +1,173 @@ +NAME + gcloud alpha spanner backups copy - copies a backup of a Cloud Spanner + database + +SYNOPSIS + gcloud alpha spanner backups copy + (--destination-backup=DESTINATION_BACKUP + : --destination-instance=DESTINATION_INSTANCE) + (--expiration-date=EXPIRATION_DATE + | --retention-period=RETENTION_PERIOD) + (--source-backup=SOURCE_BACKUP : --source-instance=SOURCE_INSTANCE) + [--async] + [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY + : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Copies a backup of a Cloud Spanner database. + +EXAMPLES + To copy a backup within the same project, run: + + $ gcloud alpha spanner backups copy \ + --source-instance=SOURCE_INSTANCE_ID \ + --source-backup=SOURCE_BACKUP_ID \ + --destination-instance=DESTINATION_INSTANCE_ID \ + --destination-backup=DESTINATION_BACKUP_ID \ + --expiration-date=2020-03-29T10:49:41Z + + To copy a backup to a different project, run: + + $ gcloud alpha spanner backups copy \ + --source-backup=projects/SOURCE_PROJECT_ID/instances/\ + SOURCE_INSTANCE_ID/backups/SOURCE_BACKUP_ID \ + --destination-backup=projects/DESTINATION_PROJECT_ID/instances/\ + DESTINATION_INSTANCE_ID/backups/DESTINATION_BACKUP_ID \ + --expiration-date=2020-03-29T10:49:41Z + +REQUIRED FLAGS + Backup resource - TEXT 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 --destination-backup 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. + + --destination-backup=DESTINATION_BACKUP + ID of the backup or fully qualified identifier for the backup. To set + the backup attribute: + ▸ provide the argument --destination-backup on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --destination-instance=DESTINATION_INSTANCE + The Cloud Spanner instance for the backup. To set the instance + attribute: + ▸ provide the argument --destination-backup on the command line + with a fully specified name; + ▸ provide the argument --destination-instance on the command line; + ▸ set the property spanner/instance. + + Exactly one of these must be specified: + + --expiration-date=EXPIRATION_DATE + Expiration time of the backup, must be at least 6 hours and at most + 366 days from the time when the source backup is created. See $ + gcloud topic datetimes for information on date/time formats. + + --retention-period=RETENTION_PERIOD + Retention period of the backup relative from now, must be at least 6 + hours and at most 366 days from the time when the source backup is + created. See $ gcloud topic datetimes for information on duration + formats. + + Backup resource - TEXT 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 --source-backup 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. + + --source-backup=SOURCE_BACKUP + ID of the backup or fully qualified identifier for the backup. To set + the backup attribute: + ▸ provide the argument --source-backup on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --source-instance=SOURCE_INSTANCE + The Cloud Spanner instance for the backup. To set the instance + attribute: + ▸ provide the argument --source-backup on the command line with a + fully specified name; + ▸ provide the argument --source-instance on the command line; + ▸ set the property spanner/instance. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --encryption-type=ENCRYPTION_TYPE + The encryption type of the copied backup. ENCRYPTION_TYPE must be one + of: + + customer-managed-encryption + Use the provided Cloud KMS key for encryption. If this option is + selected, kms-key must be set. + google-default-encryption + Use Google default encryption. + use-config-default-or-backup-encryption + Use the default encryption configuration if one exists. otherwise + use the same encryption configuration as the source backup. + + Key resource - Cloud KMS key to be used to copy the Cloud Spanner backup. + The arguments in this group can be used to specify the attributes of this + resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. To set the + kms-key attribute: + ▸ provide the argument --kms-key on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. To set the kms-keyring attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-keyring on the command line. + + --kms-location=KMS_LOCATION + Cloud location for the key. To set the kms-location attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. To set the kms-project attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-project 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. These variants are also available: + + $ gcloud spanner backups copy + + $ gcloud beta spanner backups copy + diff --git a/gcloud/alpha/spanner/backups/help b/gcloud/alpha/spanner/backups/help index b4b36cb64..e0748ac6c 100644 --- a/gcloud/alpha/spanner/backups/help +++ b/gcloud/alpha/spanner/backups/help @@ -18,6 +18,9 @@ COMMANDS add-iam-policy-binding (ALPHA) Add IAM policy binding to a Cloud Spanner backup. + copy + (ALPHA) Copies a backup of a Cloud Spanner database. + create (ALPHA) Creates a backup of a Cloud Spanner database. diff --git a/gcloud/alpha/spanner/backups/remove-iam-policy-binding b/gcloud/alpha/spanner/backups/remove-iam-policy-binding index b33960055..e3db6b914 100644 --- a/gcloud/alpha/spanner/backups/remove-iam-policy-binding +++ b/gcloud/alpha/spanner/backups/remove-iam-policy-binding @@ -9,9 +9,8 @@ SYNOPSIS | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Remove an IAM policy binding from the IAM policy of a Cloud Spanner - backup. One binding consists of a member, a role, and an optional - condition. + (ALPHA) Remove an IAM policy binding of a Cloud Spanner backup. One binding + consists of a member, a role, and an optional condition. EXAMPLES To remove an IAM policy binding for the role of 'roles/spanner.backupAdmin' @@ -23,9 +22,10 @@ EXAMPLES --member='user:test-user@gmail.com' \ --role='roles/spanner.backupAdmin' - To add an IAM policy binding which expires at the end of the year 2018 for - the role of 'roles/spanner.backupAdmin' and the user 'test-user@gmail.com' - with backup 'example-backup' and instance 'example-instance', run: + To remove an IAM policy binding which expires at the end of the year 2018 + for the role of 'roles/spanner.backupAdmin' and the user + 'test-user@gmail.com' with backup 'example-backup' and instance + 'example-instance', run: $ gcloud alpha spanner backups remove-iam-policy-binding \ example-backup --instance='example-instance' \ diff --git a/gcloud/alpha/spanner/databases/add-iam-policy-binding b/gcloud/alpha/spanner/databases/add-iam-policy-binding index af68f0ede..73c686f62 100644 --- a/gcloud/alpha/spanner/databases/add-iam-policy-binding +++ b/gcloud/alpha/spanner/databases/add-iam-policy-binding @@ -9,9 +9,8 @@ SYNOPSIS | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Add an IAM policy binding to the IAM policy of Cloud Spanner - database. One binding consists of a member, a role, and an optional - condition. + (ALPHA) Add an IAM policy binding to a Cloud Spanner database. One binding + consists of a member, a role, and an optional condition. EXAMPLES To add an IAM policy binding for the role of 'roles/editor' for the user diff --git a/gcloud/alpha/spanner/databases/remove-iam-policy-binding b/gcloud/alpha/spanner/databases/remove-iam-policy-binding index 187229566..46c2df103 100644 --- a/gcloud/alpha/spanner/databases/remove-iam-policy-binding +++ b/gcloud/alpha/spanner/databases/remove-iam-policy-binding @@ -9,9 +9,7 @@ SYNOPSIS | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Remove an IAM policy binding from the IAM policy of a Cloud Spanner - database. One binding consists of a member, a role, and an optional - condition. + (ALPHA) Remove an IAM policy binding of a Cloud Spanner database. EXAMPLES To remove an IAM policy binding for the role of 'roles/editor' for the user diff --git a/gcloud/alpha/spanner/instances/add-iam-policy-binding b/gcloud/alpha/spanner/instances/add-iam-policy-binding index 9789a4033..8aa9f7719 100644 --- a/gcloud/alpha/spanner/instances/add-iam-policy-binding +++ b/gcloud/alpha/spanner/instances/add-iam-policy-binding @@ -9,9 +9,8 @@ SYNOPSIS | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Add an IAM policy binding to the IAM policy of Cloud Spanner - instance. One binding consists of a member, a role, and an optional - condition. + (ALPHA) Add an IAM policy binding to a Cloud Spanner instance. One binding + consists of a member, a role, and an optional condition. EXAMPLES To add an IAM policy binding for the role of 'roles/editor' for the user diff --git a/gcloud/alpha/spanner/instances/remove-iam-policy-binding b/gcloud/alpha/spanner/instances/remove-iam-policy-binding index 02b3c45b1..0614a6d9b 100644 --- a/gcloud/alpha/spanner/instances/remove-iam-policy-binding +++ b/gcloud/alpha/spanner/instances/remove-iam-policy-binding @@ -9,9 +9,8 @@ SYNOPSIS | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Remove an IAM policy binding from the IAM policy of a Cloud Spanner - instance. One binding consists of a member, a role, and an optional - condition. + (ALPHA) Remove an IAM policy binding of a Cloud Spanner instance. One + binding consists of a member, a role, and an optional condition. EXAMPLES To remove an IAM policy binding for the role of 'roles/editor' for the user diff --git a/gcloud/alpha/sql/connect b/gcloud/alpha/sql/connect index 52b28dbb1..b69d00580 100644 --- a/gcloud/alpha/sql/connect +++ b/gcloud/alpha/sql/connect @@ -7,8 +7,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Connects to Cloud SQL V2 instances through the Cloud SQL Proxy. - Connects to Cloud SQL V1 instances directly. + (ALPHA) Connects to a Cloud SQL instance. EXAMPLES To connect to a Cloud SQL instance, run: diff --git a/gcloud/alpha/sql/export/sql b/gcloud/alpha/sql/export/sql index ab3c742b0..cea73dc84 100644 --- a/gcloud/alpha/sql/export/sql +++ b/gcloud/alpha/sql/export/sql @@ -12,6 +12,11 @@ DESCRIPTION (ALPHA) Exports data from a Cloud SQL instance to a Google Cloud Storage bucket as a SQL dump file. + NOTE: Certain roles and permissions are required to export data to Google + Cloud Storage. For more information on exporting data from Google Cloud SQL + see Export from Cloud SQL to a SQL dump file + (https://cloud.google.com/sql/docs/mysql/import-export/import-export-sql#gcloud). + POSITIONAL ARGUMENTS INSTANCE Cloud SQL instance ID. diff --git a/gcloud/alpha/sql/import/sql b/gcloud/alpha/sql/import/sql index 90e56e42f..04743088e 100644 --- a/gcloud/alpha/sql/import/sql +++ b/gcloud/alpha/sql/import/sql @@ -10,6 +10,11 @@ DESCRIPTION (ALPHA) gcloud alpha sql import sql imports data into a Cloud SQL instance from a SQL dump file in Google Cloud Storage. + NOTE: Certain roles and permissions are required to import data into Google + Cloud SQL. For more information on importing data into Google Cloud SQL see + Import a SQL dump file + (https://cloud.google.com/sql/docs/mysql/import-export/import-export-sql#gcloud_1). + For detailed help on importing data into Cloud SQL, refer to this guide: https://cloud.google.com/sql/docs/mysql/import-export/importing diff --git a/gcloud/alpha/storage/cp b/gcloud/alpha/storage/cp index 9b2f43441..32a35962d 100644 --- a/gcloud/alpha/storage/cp +++ b/gcloud/alpha/storage/cp @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud alpha storage cp SOURCE [SOURCE ...] DESTINATION - [--all-versions, -A] [--cache-control=CACHE_CONTROL] + [--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] @@ -11,7 +11,8 @@ SYNOPSIS [--custom-metadata=[CUSTOM_METADATA,...]] [--custom-time=CUSTOM_TIME] [--do-not-decompress] [--if-generation-match=GENERATION] [--if-metageneration-match=METAGENERATION] [--ignore-symlinks] - [--recursive, -R, -r] [--skip-unsupported, -U] + [--print-created-message, -v] [--recursive, -R, -r] + [--skip-unsupported, -U] [--storage-class=STORAGE_CLASS, -s STORAGE_CLASS] [--gzip-in-flight-all, -J | --gzip-in-flight-extensions=[FILE_EXTENSIONS,...], @@ -62,6 +63,11 @@ FLAGS --cache-control=CACHE_CONTROL How caches should handle requests and responses. + --no-clobber, -n + Do not overwrite existing files or objects at the destination. Skipped + items will be printed. This option performs an additional GET request + for cloud objects before attempting an upload. + --content-disposition=CONTENT_DISPOSITION How content should be displayed. @@ -106,6 +112,9 @@ FLAGS Ignore file symlinks instead of copying what they point to. Symlinks pointing to directories will always be ignored. + --print-created-message, -v + Prints the version-specific URL for each copied object. + --recursive, -R, -r Recursively copy the contents of any directories that match the source path expression. @@ -116,9 +125,9 @@ FLAGS class. --storage-class=STORAGE_CLASS, -s STORAGE_CLASS - Specifies the storage class of the destination object. If not - specified, the default storage class of the destination bucket is used. - This option is not valid for copying to non-cloud destinations. + Specify the storage class of the destination object. If not specified, + the default storage class of the destination bucket is used. This + option is not valid for copying to non-cloud destinations. At most one of these can be specified: diff --git a/gcloud/alpha/terraform/help b/gcloud/alpha/terraform/help new file mode 100644 index 000000000..d95860d71 --- /dev/null +++ b/gcloud/alpha/terraform/help @@ -0,0 +1,30 @@ +NAME + gcloud alpha terraform - commands related to Terraform management of Google + Cloud Platform resources + +SYNOPSIS + gcloud alpha terraform COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Commands related to Terraform management of Google Cloud Platform + resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + vet + (ALPHA) Validate that a terraform plan complies with policies. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta terraform + diff --git a/gcloud/alpha/terraform/vet b/gcloud/alpha/terraform/vet new file mode 100644 index 000000000..d99d9bc48 --- /dev/null +++ b/gcloud/alpha/terraform/vet @@ -0,0 +1,43 @@ +NAME + gcloud alpha terraform vet - validate that a terraform plan complies with + policies + +SYNOPSIS + gcloud alpha terraform vet TERRAFORM_PLAN_JSON + --policy-library=POLICY_LIBRARY [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Validate that a terraform plan complies with policies. + +EXAMPLES + To validate that a terraform plan complies with a policy library at + /my/policy/library: + + $ gcloud alpha terraform vet tfplan.json \ + --policy-library=/my/policy/library + +POSITIONAL ARGUMENTS + TERRAFORM_PLAN_JSON + File which contains a JSON export of a terraform plan. This file will + be validated against the given policy library. + +REQUIRED FLAGS + --policy-library=POLICY_LIBRARY + Directory which contains a policy library + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta terraform vet + diff --git a/gcloud/beta/composer/environments/check-upgrade b/gcloud/beta/composer/environments/check-upgrade index 8ac290951..8ce714f17 100644 --- a/gcloud/beta/composer/environments/check-upgrade +++ b/gcloud/beta/composer/environments/check-upgrade @@ -58,27 +58,31 @@ FLAGS At most one of these can be specified: --airflow-version=AIRFLOW_VERSION - Upgrade the environment to a later Airflow version in-place. + Upgrade the environment to a later Apache Airflow version in-place. - Must be of the form X.Y[.Z]. + Must be of the form X[.Y[.Z]], where [] denotes optional fragments. - The Airflow version is a semantic version. The patch version can be - omitted and the current version will be selected. The version numbers - that are used will be stored. + The Apache Airflow version is a semantic version or an alias in the + form of major or major.minor version numbers, resolved to the latest + matching Apache Airflow version supported in the current Cloud + Composer version. The resolved version is stored in the upgraded + environment. --image-version=IMAGE_VERSION Upgrade the environment to a later version in-place. The image version encapsulates the versions of both Cloud Composer and Apache Airflow. Must be of the form - composer-A[.B.C[-D.E]]-airflow-X.Y[.Z]. + composer-A[.B.C[-D.E]]-airflow-X[.Y[.Z]], where [] denotes optional + fragments. - The Cloud Composer and Airflow versions are semantic versions. latest - can be provided instead of an explicit Cloud Composer version number - indicating that the server will replace latest with the current Cloud - Composer version. For the Apache Airflow portion, the patch version - can be omitted and the current version will be selected. The version - numbers that are used will be stored. + The Cloud Composer portion of the image version is a semantic version + or an alias in the form of major version number or latest, resolved + to the current Cloud Composer version. The Apache Airflow portion of + the image version is a semantic version or an alias in the form of + major or major.minor version numbers, resolved to the latest matching + Apache Airflow version supported in the given Cloud Composer version. + The resolved versions are stored in the upgraded environment. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/composer/environments/create b/gcloud/beta/composer/environments/create index acbb593a2..dd2259fe0 100644 --- a/gcloud/beta/composer/environments/create +++ b/gcloud/beta/composer/environments/create @@ -183,11 +183,15 @@ FLAGS At most one of these can be specified: --airflow-version=AIRFLOW_VERSION - Version of Airflow to run in the environment. + Version of Apache Airflow to run in the environment. - Must be of the form `X.Y[.Z]`. + Must be of the form `X[.Y[.Z]]`, where `[]` denotes optional fragments. The current Cloud Composer version will be used within the created + environment. The Apache Airflow version is a semantic version or an alias + in the form of major or major.minor version numbers, resolved to the + latest matching Apache Airflow version supported in the current Cloud + Composer version. The resolved version is stored in the created environment. --image-version=IMAGE_VERSION @@ -195,15 +199,16 @@ FLAGS The image version encapsulates the versions of both Cloud Composer and Apache Airflow. Must be of the form - `composer-A[.B.C[-D.E]]-airflow-X.Y[.Z]`. + `composer-A[.B.C[-D.E]]-airflow-X[.Y[.Z]]`, where `[]` denotes optional + fragments. - The Cloud Composer and Airflow versions are semantic versions. - `latest` can be provided instead of an explicit Cloud Composer - version number indicating that the server will replace `latest` - with the current Cloud Composer version. For the Apache Airflow - portion, the patch version can be omitted and the current - version will be selected. The version numbers that are used will - be stored. + The Cloud Composer portion of the image version is a semantic version or + an alias in the form of major version number or `latest`, resolved to the + current Cloud Composer version. The Apache Airflow portion of the image + version is a semantic version or an alias in the form of major or + major.minor version numbers, resolved to the latest matching Apache + Airflow version supported in the given Cloud Composer version. The + resolved versions are stored in the created environment. Private Clusters diff --git a/gcloud/beta/composer/environments/help b/gcloud/beta/composer/environments/help index 96baceaad..6e207a233 100644 --- a/gcloud/beta/composer/environments/help +++ b/gcloud/beta/composer/environments/help @@ -21,6 +21,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + snapshots + (BETA) Saves and loads snapshots of environment. + storage (BETA) Manage Cloud Storage objects stored as part of Cloud Composer environments. diff --git a/gcloud/beta/composer/environments/snapshots/help b/gcloud/beta/composer/environments/snapshots/help new file mode 100644 index 000000000..5f066e34b --- /dev/null +++ b/gcloud/beta/composer/environments/snapshots/help @@ -0,0 +1,31 @@ +NAME + gcloud beta composer environments snapshots - saves and loads snapshots of + environment + +SYNOPSIS + gcloud beta composer environments snapshots COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The gcloud beta composer environments snapshots command group saves + and loads snapshots of Cloud Composer environments. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + load + (BETA) Load a snapshot into the environment. + + save + (BETA) Save a snapshot of the environment. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha composer environments snapshots + diff --git a/gcloud/beta/composer/environments/snapshots/load b/gcloud/beta/composer/environments/snapshots/load new file mode 100644 index 000000000..eef586474 --- /dev/null +++ b/gcloud/beta/composer/environments/snapshots/load @@ -0,0 +1,75 @@ +NAME + gcloud beta composer environments snapshots load - load a snapshot into the + environment + +SYNOPSIS + gcloud beta composer environments snapshots load + (ENVIRONMENT : --location=LOCATION) --snapshot-path=SNAPSHOT_PATH + [--async] [--skip-pypi-packages-installation] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Load a snapshot into the environment. + +EXAMPLES + To load a snapshot into the environment named env-1, run: + + $ gcloud beta composer environments snapshots load env-1 \ + --snapshot-path=gs://my-bucket/path-to-the-specific-snapshot + +POSITIONAL ARGUMENTS + Environment resource - The environment where to load a snapshot. 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 environment 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. + + ENVIRONMENT + ID of the environment or fully qualified identifier for the + environment. To set the environment attribute: + ▸ provide the argument environment on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Compute Engine region in which to create the environment. To set the + location attribute: + ▸ provide the argument environment on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property composer/location. + +REQUIRED FLAGS + --snapshot-path=SNAPSHOT_PATH + The Cloud Storage path to load the snapshot from. It must start with + prefix gs:// and one needs to specify a single snapshot that should be + loaded. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --skip-pypi-packages-installation + When specified, skips the installation of custom PyPI packages from the + snapshot. + +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 composer environments snapshots load + diff --git a/gcloud/beta/composer/environments/snapshots/save b/gcloud/beta/composer/environments/snapshots/save new file mode 100644 index 000000000..195107b20 --- /dev/null +++ b/gcloud/beta/composer/environments/snapshots/save @@ -0,0 +1,69 @@ +NAME + gcloud beta composer environments snapshots save - save a snapshot of the + environment + +SYNOPSIS + gcloud beta composer environments snapshots save + (ENVIRONMENT : --location=LOCATION) [--async] + [--snapshot-location=SNAPSHOT_LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Save a snapshot of the environment. + +EXAMPLES + To save a snapshot of the environment named env-1, run: + + $ gcloud beta composer environments snapshots save env-1 + +POSITIONAL ARGUMENTS + Environment resource - The environment where the snapshot must be saved. + 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 environment 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. + + ENVIRONMENT + ID of the environment or fully qualified identifier for the + environment. To set the environment attribute: + ▸ provide the argument environment on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Compute Engine region in which to create the environment. To set the + location attribute: + ▸ provide the argument environment on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property composer/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --snapshot-location=SNAPSHOT_LOCATION + The Cloud Storage location where to save the snapshot. It must start + with the prefix gs://. Default value is /snapshots directory in the + Cloud Storage bucket of the environment. + +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 composer environments snapshots save + diff --git a/gcloud/beta/composer/environments/update b/gcloud/beta/composer/environments/update index e66c68d1f..a7eadd8f7 100644 --- a/gcloud/beta/composer/environments/update +++ b/gcloud/beta/composer/environments/update @@ -99,27 +99,32 @@ REQUIRED FLAGS At most one of these can be specified: --airflow-version=AIRFLOW_VERSION - Upgrade the environment to a later Airflow version in-place. + Upgrade the environment to a later Apache Airflow version in-place. - Must be of the form X.Y[.Z]. + Must be of the form X[.Y[.Z]], where [] denotes optional fragments. - The Airflow version is a semantic version. The patch version can be - omitted and the current version will be selected. The version - numbers that are used will be stored. + The Apache Airflow version is a semantic version or an alias in the + form of major or major.minor version numbers, resolved to the + latest matching Apache Airflow version supported in the current + Cloud Composer version. The resolved version is stored in the + upgraded environment. --image-version=IMAGE_VERSION Upgrade the environment to a later version in-place. The image version encapsulates the versions of both Cloud Composer and Apache Airflow. Must be of the form - composer-A[.B.C[-D.E]]-airflow-X.Y[.Z]. + composer-A[.B.C[-D.E]]-airflow-X[.Y[.Z]], where [] denotes optional + fragments. - The Cloud Composer and Airflow versions are semantic versions. - latest can be provided instead of an explicit Cloud Composer - version number indicating that the server will replace latest with - the current Cloud Composer version. For the Apache Airflow portion, - the patch version can be omitted and the current version will be - selected. The version numbers that are used will be stored. + The Cloud Composer portion of the image version is a semantic + version or an alias in the form of major version number or latest, + resolved to the current Cloud Composer version. The Apache Airflow + portion of the image version is a semantic version or an alias in + the form of major or major.minor version numbers, resolved to the + latest matching Apache Airflow version supported in the given Cloud + Composer version. The resolved versions are stored in the upgraded + environment. Group of arguments for setting master authorized networks configuration. diff --git a/gcloud/beta/compute/backend-services/export b/gcloud/beta/compute/backend-services/export index 0ec917a41..0d6e45573 100644 --- a/gcloud/beta/compute/backend-services/export +++ b/gcloud/beta/compute/backend-services/export @@ -22,10 +22,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/BackendService.yaml. At most one of these can be specified: diff --git a/gcloud/beta/compute/backend-services/import b/gcloud/beta/compute/backend-services/import index ed33824ba..2e1abefc8 100644 --- a/gcloud/beta/compute/backend-services/import +++ b/gcloud/beta/compute/backend-services/import @@ -20,10 +20,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/BackendService.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/compute/forwarding-rules/export b/gcloud/beta/compute/forwarding-rules/export index a83af5e2b..f4417a76d 100644 --- a/gcloud/beta/compute/forwarding-rules/export +++ b/gcloud/beta/compute/forwarding-rules/export @@ -21,10 +21,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/ForwardingRule.yaml. At most one of these can be specified: diff --git a/gcloud/beta/compute/forwarding-rules/import b/gcloud/beta/compute/forwarding-rules/import index 2a615635e..151ae5304 100644 --- a/gcloud/beta/compute/forwarding-rules/import +++ b/gcloud/beta/compute/forwarding-rules/import @@ -20,10 +20,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/ForwardingRule.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/compute/instances/update-from-file b/gcloud/beta/compute/instances/update-from-file index 1827d182f..65b4e1102 100644 --- a/gcloud/beta/compute/instances/update-from-file +++ b/gcloud/beta/compute/instances/update-from-file @@ -38,10 +38,9 @@ FLAGS default will be REFRESH. --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/Instance.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/compute/target-http-proxies/export b/gcloud/beta/compute/target-http-proxies/export index 3b5970d55..df2d5010e 100644 --- a/gcloud/beta/compute/target-http-proxies/export +++ b/gcloud/beta/compute/target-http-proxies/export @@ -22,10 +22,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/TargetHttpProxy.yaml. At most one of these can be specified: diff --git a/gcloud/beta/compute/target-http-proxies/import b/gcloud/beta/compute/target-http-proxies/import index f96c0e356..25db59e2d 100644 --- a/gcloud/beta/compute/target-http-proxies/import +++ b/gcloud/beta/compute/target-http-proxies/import @@ -20,10 +20,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/TargetHttpProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/compute/target-https-proxies/export b/gcloud/beta/compute/target-https-proxies/export index d3b7177e3..b4cff795f 100644 --- a/gcloud/beta/compute/target-https-proxies/export +++ b/gcloud/beta/compute/target-https-proxies/export @@ -23,10 +23,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/TargetHttpsProxy.yaml. At most one of these can be specified: diff --git a/gcloud/beta/compute/target-https-proxies/import b/gcloud/beta/compute/target-https-proxies/import index 43c74c103..62866b2ab 100644 --- a/gcloud/beta/compute/target-https-proxies/import +++ b/gcloud/beta/compute/target-https-proxies/import @@ -21,10 +21,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/TargetHttpsProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/compute/target-ssl-proxies/create b/gcloud/beta/compute/target-ssl-proxies/create index 223ec7c28..a0089ab90 100644 --- a/gcloud/beta/compute/target-ssl-proxies/create +++ b/gcloud/beta/compute/target-ssl-proxies/create @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud beta compute target-ssl-proxies create NAME --backend-service=BACKEND_SERVICE - --ssl-certificates=SSL_CERTIFICATE,[...] [--description=DESCRIPTION] + (--certificate-map=CERTIFICATE_MAP + : --ssl-certificates=SSL_CERTIFICATE,[...]) + [--description=DESCRIPTION] [--proxy-header=PROXY_HEADER; default="NONE"] [--ssl-policy=SSL_POLICY] [GCLOUD_WIDE_FLAG ...] @@ -14,8 +16,8 @@ DESCRIPTION forwarding rules which define which packets the proxy is responsible for routing. The target SSL proxy points to a backend service which handle the actual requests. The target SSL proxy also points to at most 15 SSL - certificates used for server-side authentication. The target SSL proxy can - be associated with at most one SSL policy. + certificates used for server-side authentication or one certificate map. + The target SSL proxy can be associated with at most one SSL policy. POSITIONAL ARGUMENTS NAME @@ -26,12 +28,31 @@ REQUIRED FLAGS A backend service that will be used for connections to the target SSL proxy. - --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 SSL proxy. + At least one of these must be specified: + + Certificate map resource - The certificate map to attach. 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 --certificate-map on the command line with a + fully specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. To set the location attribute: + ▸ provide the argument --certificate-map on the command line with a + fully specified name; + ▸ default value of location is [global]. + + --certificate-map=CERTIFICATE_MAP + ID of the certificate map or fully qualified identifier for the + certificate map. To set the map attribute: + ▫ provide the argument --certificate-map on the command line. + + --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 SSL proxy. OPTIONAL FLAGS --description=DESCRIPTION diff --git a/gcloud/beta/compute/target-ssl-proxies/update b/gcloud/beta/compute/target-ssl-proxies/update index 11e9d8859..85c82cc25 100644 --- a/gcloud/beta/compute/target-ssl-proxies/update +++ b/gcloud/beta/compute/target-ssl-proxies/update @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud beta compute target-ssl-proxies update NAME [--backend-service=BACKEND_SERVICE] [--proxy-header=PROXY_HEADER] - [--ssl-certificates=SSL_CERTIFICATE,[...]] + [--certificate-map=CERTIFICATE_MAP + : --ssl-certificates=SSL_CERTIFICATE,[...] | --clear-ssl-certificates + | --clear-certificate-map] [--clear-ssl-policy | --ssl-policy=SSL_POLICY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -14,8 +16,8 @@ DESCRIPTION forwarding rules which define which packets the proxy is responsible for routing. The target SSL proxy in turn points to a backend service which will handle the requests. The target SSL proxy also points to at most 15 - SSL certificates used for server-side authentication. The target SSL proxy - can be associated with at most one SSL policy. + SSL certificates used for server-side authentication or one certificate + map. The target SSL proxy can be associated with at most one SSL policy. POSITIONAL ARGUMENTS NAME @@ -36,12 +38,37 @@ FLAGS Enables PROXY protocol (version 1) for passing client connection information. - --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 SSL proxy. + At most one of these can be specified: + + --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 SSL proxy. + + --clear-ssl-certificates + Removes any attached SSL Certificates from the SSL proxy. + + Certificate map resource - The certificate map to attach. 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 --certificate-map on the command line with a + fully specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. To set the location attribute: + ▸ provide the argument --certificate-map on the command line with a + fully specified name; + ▸ default value of location is [global]. + + --certificate-map=CERTIFICATE_MAP + ID of the certificate map or fully qualified identifier for the + certificate map. To set the map attribute: + ▫ provide the argument --certificate-map on the command line. + + --clear-certificate-map + Removes any attached certificate map from the SSL proxy. At most one of these can be specified: diff --git a/gcloud/beta/compute/url-maps/export b/gcloud/beta/compute/url-maps/export index 9a1963347..2f370e973 100644 --- a/gcloud/beta/compute/url-maps/export +++ b/gcloud/beta/compute/url-maps/export @@ -21,10 +21,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/UrlMap.yaml. At most one of these can be specified: diff --git a/gcloud/beta/compute/url-maps/import b/gcloud/beta/compute/url-maps/import index 0ee29c842..ccbbee7d1 100644 --- a/gcloud/beta/compute/url-maps/import +++ b/gcloud/beta/compute/url-maps/import @@ -19,10 +19,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/UrlMap.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index d4852a429..330442b56 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -936,6 +936,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 368c0184f..04fd3a413 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -968,6 +968,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 2339d15e8..ed450c632 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -970,6 +970,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index a964e5d34..273225f46 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -983,6 +983,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 9c3a53723..51ca4139f 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -944,6 +944,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 7172cfc15..dfb4508a7 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -17,12 +17,14 @@ SYNOPSIS [--max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] - [--min-cpu-platform=PLATFORM] [--node-group=NODE_GROUP] - [--node-labels=[NODE_LABEL,...]] [--node-locations=ZONE,[ZONE,...]] - [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] - [--num-nodes=NUM_NODES; default=3] [--placement-type=PLACEMENT_TYPE] - [--preemptible] [--sandbox=[type=TYPE]] - [--shielded-integrity-monitoring] [--shielded-secure-boot] [--spot] + [--min-cpu-platform=PLATFORM] + [--network-performance-configs=[PROPERTY=VALUE,...]] + [--node-group=NODE_GROUP] [--node-labels=[NODE_LABEL,...]] + [--node-locations=ZONE,[ZONE,...]] [--node-taints=[NODE_TAINT,...]] + [--node-version=NODE_VERSION] [--num-nodes=NUM_NODES; default=3] + [--placement-type=PLACEMENT_TYPE] [--preemptible] + [--sandbox=[type=TYPE]] [--shielded-integrity-monitoring] + [--shielded-secure-boot] [--spot] [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--workload-metadata=WORKLOAD_METADATA] @@ -264,6 +266,17 @@ FLAGS CPU platform selection is available only in selected zones. + --network-performance-configs=[PROPERTY=VALUE,...] + Configures network performance settings for the node pool. If this flag + is not specified, the pool will be created with its default network + performance configuration. + + total-egress-bandwidth-tier + Total egress bandwidth is the available outbound bandwidth from a + VM, regardless of whether the traffic is going to internal IP or + external IP destinations. The following tier values are allowed: + [DEFAULT,TIER_1] + --node-group=NODE_GROUP Assign instances of this pool to run on the specified Google Compute Engine node group. This is useful for running workloads on sole tenant diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index a7dcc2dc6..c6bb0d15f 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -5,8 +5,10 @@ NAME SYNOPSIS gcloud beta container node-pools update NAME (--enable-confidential-nodes | --enable-gvnic - | --enable-image-streaming | --node-labels=[NODE_LABEL,...] - | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] + | --enable-image-streaming + | --network-performance-configs=[PROPERTY=VALUE,...] + | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] + | --node-taints=[NODE_TAINT,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE | --tags=[TAG,...] | --workload-metadata=WORKLOAD_METADATA | --enable-autoprovisioning @@ -46,6 +48,17 @@ REQUIRED FLAGS --enable-image-streaming Specifies whether to enable image streaming on node pool. + --network-performance-configs=[PROPERTY=VALUE,...] + Configures network performance settings for the node pool. If this + flag is not specified, the pool will be created with its default + network performance configuration. + + total-egress-bandwidth-tier + Total egress bandwidth is the available outbound bandwidth from a + VM, regardless of whether the traffic is going to internal IP or + external IP destinations. The following tier values are allowed: + [DEFAULT,TIER_1] + --node-labels=[NODE_LABEL,...] Replaces all the user specified Kubernetes labels on all nodes in an existing node pool with the given labels. diff --git a/gcloud/beta/dataproc/autoscaling-policies/export b/gcloud/beta/dataproc/autoscaling-policies/export index a2baa88ab..00284ec81 100644 --- a/gcloud/beta/dataproc/autoscaling-policies/export +++ b/gcloud/beta/dataproc/autoscaling-policies/export @@ -53,9 +53,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dataproc/autoscaling-policies/import b/gcloud/beta/dataproc/autoscaling-policies/import index e70492eeb..8c47fbb4e 100644 --- a/gcloud/beta/dataproc/autoscaling-policies/import +++ b/gcloud/beta/dataproc/autoscaling-policies/import @@ -57,9 +57,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input. + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dataproc/clusters/export b/gcloud/beta/dataproc/clusters/export index 7034162b9..55b0aedb1 100644 --- a/gcloud/beta/dataproc/clusters/export +++ b/gcloud/beta/dataproc/clusters/export @@ -54,9 +54,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dataproc/clusters/import b/gcloud/beta/dataproc/clusters/import index c6f56e58d..783f144ed 100644 --- a/gcloud/beta/dataproc/clusters/import +++ b/gcloud/beta/dataproc/clusters/import @@ -57,9 +57,8 @@ FLAGS complete. --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input. + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dataproc/workflow-templates/export b/gcloud/beta/dataproc/workflow-templates/export index d5e54d8d1..a09674323 100644 --- a/gcloud/beta/dataproc/workflow-templates/export +++ b/gcloud/beta/dataproc/workflow-templates/export @@ -50,9 +50,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. --version=VERSION The version of the workflow template. diff --git a/gcloud/beta/dataproc/workflow-templates/import b/gcloud/beta/dataproc/workflow-templates/import index d91914633..03f7e1df1 100644 --- a/gcloud/beta/dataproc/workflow-templates/import +++ b/gcloud/beta/dataproc/workflow-templates/import @@ -44,9 +44,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input. + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/deploy/delivery-pipelines/export b/gcloud/beta/deploy/delivery-pipelines/export index 2c3f9c256..b26156c02 100644 --- a/gcloud/beta/deploy/delivery-pipelines/export +++ b/gcloud/beta/deploy/delivery-pipelines/export @@ -48,9 +48,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/deploy/targets/export b/gcloud/beta/deploy/targets/export index a1565f0b4..e1803ed3f 100644 --- a/gcloud/beta/deploy/targets/export +++ b/gcloud/beta/deploy/targets/export @@ -46,9 +46,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/spanner/backups/add-iam-policy-binding b/gcloud/beta/spanner/backups/add-iam-policy-binding index 13dbec078..6e45cde5f 100644 --- a/gcloud/beta/spanner/backups/add-iam-policy-binding +++ b/gcloud/beta/spanner/backups/add-iam-policy-binding @@ -9,8 +9,8 @@ SYNOPSIS | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Add an IAM policy binding to the IAM policy of Cloud Spanner backup. - One binding consists of a member, a role, and an optional condition. + (BETA) Add an IAM policy binding to a Cloud Spanner backup. One binding + consists of a member, a role, and an optional condition. EXAMPLES To add an IAM policy binding for the role of 'roles/spanner.backupAdmin' diff --git a/gcloud/beta/spanner/backups/copy b/gcloud/beta/spanner/backups/copy new file mode 100644 index 000000000..01c3d0e26 --- /dev/null +++ b/gcloud/beta/spanner/backups/copy @@ -0,0 +1,171 @@ +NAME + gcloud beta spanner backups copy - copies a backup of a Cloud Spanner + database + +SYNOPSIS + gcloud beta spanner backups copy + (--destination-backup=DESTINATION_BACKUP + : --destination-instance=DESTINATION_INSTANCE) + (--expiration-date=EXPIRATION_DATE + | --retention-period=RETENTION_PERIOD) + (--source-backup=SOURCE_BACKUP : --source-instance=SOURCE_INSTANCE) + [--async] + [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY + : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Copies a backup of a Cloud Spanner database. + +EXAMPLES + To copy a backup within the same project, run: + + $ gcloud beta spanner backups copy \ + --source-instance=SOURCE_INSTANCE_ID \ + --source-backup=SOURCE_BACKUP_ID \ + --destination-instance=DESTINATION_INSTANCE_ID \ + --destination-backup=DESTINATION_BACKUP_ID \ + --expiration-date=2020-03-29T10:49:41Z + + To copy a backup to a different project, run: + + $ gcloud beta spanner backups copy \ + --source-backup=projects/SOURCE_PROJECT_ID/instances/\ + SOURCE_INSTANCE_ID/backups/SOURCE_BACKUP_ID \ + --destination-backup=projects/DESTINATION_PROJECT_ID/instances/\ + DESTINATION_INSTANCE_ID/backups/DESTINATION_BACKUP_ID \ + --expiration-date=2020-03-29T10:49:41Z + +REQUIRED FLAGS + Backup resource - TEXT 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 --destination-backup 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. + + --destination-backup=DESTINATION_BACKUP + ID of the backup or fully qualified identifier for the backup. To set + the backup attribute: + ▸ provide the argument --destination-backup on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --destination-instance=DESTINATION_INSTANCE + The Cloud Spanner instance for the backup. To set the instance + attribute: + ▸ provide the argument --destination-backup on the command line + with a fully specified name; + ▸ provide the argument --destination-instance on the command line; + ▸ set the property spanner/instance. + + Exactly one of these must be specified: + + --expiration-date=EXPIRATION_DATE + Expiration time of the backup, must be at least 6 hours and at most + 366 days from the time when the source backup is created. See $ + gcloud topic datetimes for information on date/time formats. + + --retention-period=RETENTION_PERIOD + Retention period of the backup relative from now, must be at least 6 + hours and at most 366 days from the time when the source backup is + created. See $ gcloud topic datetimes for information on duration + formats. + + Backup resource - TEXT 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 --source-backup 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. + + --source-backup=SOURCE_BACKUP + ID of the backup or fully qualified identifier for the backup. To set + the backup attribute: + ▸ provide the argument --source-backup on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --source-instance=SOURCE_INSTANCE + The Cloud Spanner instance for the backup. To set the instance + attribute: + ▸ provide the argument --source-backup on the command line with a + fully specified name; + ▸ provide the argument --source-instance on the command line; + ▸ set the property spanner/instance. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --encryption-type=ENCRYPTION_TYPE + The encryption type of the copied backup. ENCRYPTION_TYPE must be one + of: + + customer-managed-encryption + Use the provided Cloud KMS key for encryption. If this option is + selected, kms-key must be set. + google-default-encryption + Use Google default encryption. + use-config-default-or-backup-encryption + Use the default encryption configuration if one exists. otherwise + use the same encryption configuration as the source backup. + + Key resource - Cloud KMS key to be used to copy the Cloud Spanner backup. + The arguments in this group can be used to specify the attributes of this + resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. To set the + kms-key attribute: + ▸ provide the argument --kms-key on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. To set the kms-keyring attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-keyring on the command line. + + --kms-location=KMS_LOCATION + Cloud location for the key. To set the kms-location attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. To set the kms-project attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-project on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud spanner backups copy + + $ gcloud alpha spanner backups copy + diff --git a/gcloud/beta/spanner/backups/help b/gcloud/beta/spanner/backups/help index b2b96ea16..40c79eaf5 100644 --- a/gcloud/beta/spanner/backups/help +++ b/gcloud/beta/spanner/backups/help @@ -18,6 +18,9 @@ COMMANDS add-iam-policy-binding (BETA) Add IAM policy binding to a Cloud Spanner backup. + copy + (BETA) Copies a backup of a Cloud Spanner database. + create (BETA) Creates a backup of a Cloud Spanner database. diff --git a/gcloud/beta/spanner/backups/remove-iam-policy-binding b/gcloud/beta/spanner/backups/remove-iam-policy-binding index 5f7118502..073aff56b 100644 --- a/gcloud/beta/spanner/backups/remove-iam-policy-binding +++ b/gcloud/beta/spanner/backups/remove-iam-policy-binding @@ -9,9 +9,8 @@ SYNOPSIS | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Remove an IAM policy binding from the IAM policy of a Cloud Spanner - backup. One binding consists of a member, a role, and an optional - condition. + (BETA) Remove an IAM policy binding of a Cloud Spanner backup. One binding + consists of a member, a role, and an optional condition. EXAMPLES To remove an IAM policy binding for the role of 'roles/spanner.backupAdmin' @@ -23,9 +22,10 @@ EXAMPLES --member='user:test-user@gmail.com' \ --role='roles/spanner.backupAdmin' - To add an IAM policy binding which expires at the end of the year 2018 for - the role of 'roles/spanner.backupAdmin' and the user 'test-user@gmail.com' - with backup 'example-backup' and instance 'example-instance', run: + To remove an IAM policy binding which expires at the end of the year 2018 + for the role of 'roles/spanner.backupAdmin' and the user + 'test-user@gmail.com' with backup 'example-backup' and instance + 'example-instance', run: $ gcloud beta spanner backups remove-iam-policy-binding \ example-backup --instance='example-instance' \ diff --git a/gcloud/beta/spanner/databases/add-iam-policy-binding b/gcloud/beta/spanner/databases/add-iam-policy-binding index 970892486..a1758cdc5 100644 --- a/gcloud/beta/spanner/databases/add-iam-policy-binding +++ b/gcloud/beta/spanner/databases/add-iam-policy-binding @@ -5,10 +5,12 @@ NAME SYNOPSIS gcloud beta spanner databases add-iam-policy-binding (DATABASE : --instance=INSTANCE) --member=PRINCIPAL --role=ROLE - [GCLOUD_WIDE_FLAG ...] + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Add an IAM policy binding to a Cloud Spanner database. + (BETA) Add an IAM policy binding to a Cloud Spanner database. One binding + consists of a member, a role, and an optional condition. EXAMPLES To add an IAM policy binding for the role of 'roles/editor' for the user @@ -19,6 +21,18 @@ EXAMPLES --instance='my-instance' --member='user:test-user@gmail.com' \ --role='roles/editor' + To add an IAM policy binding which expires at the end of the year 2018 for + the role of 'roles/spanner.databaseAdmin' and the user + 'test-user@gmail.com' with database 'my-database' and instance + 'my-instance', run: + + $ gcloud beta spanner databases add-iam-policy-binding my-database \ + --instance='my-instance' --member='user:test-user@gmail.com' \ + --role='roles/spanner.databaseAdmin' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' + See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. @@ -73,6 +87,44 @@ REQUIRED FLAGS for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer. +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/spanner/databases/remove-iam-policy-binding b/gcloud/beta/spanner/databases/remove-iam-policy-binding index 0035483b7..25bcb8998 100644 --- a/gcloud/beta/spanner/databases/remove-iam-policy-binding +++ b/gcloud/beta/spanner/databases/remove-iam-policy-binding @@ -5,13 +5,14 @@ NAME SYNOPSIS gcloud beta spanner databases remove-iam-policy-binding (DATABASE : --instance=INSTANCE) --member=PRINCIPAL --role=ROLE - [GCLOUD_WIDE_FLAG ...] + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Remove an IAM policy binding of a Cloud Spanner database. EXAMPLES - To Remove an IAM policy binding for the role of 'roles/editor' for the user + To remove an IAM policy binding for the role of 'roles/editor' for the user 'test-user@gmail.com' with database 'my-database' and instance 'my-instance', run: @@ -19,6 +20,19 @@ EXAMPLES my-database --instance='my-instance' \ --member='user:test-user@gmail.com' --role='roles/editor' + To remove an IAM policy binding which expires at the end of the year 2018 + for the role of 'roles/spanner.databaseAdmin' and the user + 'test-user@gmail.com' with database 'my-database' and instance + 'my-instance', run: + + $ gcloud beta spanner databases remove-iam-policy-binding \ + my-database --instance='my-instance' \ + --member='user:test-user@gmail.com' \ + --role='roles/spanner.databaseAdmin' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' + See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. @@ -74,6 +88,48 @@ REQUIRED FLAGS --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, diff --git a/gcloud/beta/spanner/instances/add-iam-policy-binding b/gcloud/beta/spanner/instances/add-iam-policy-binding index 55d22a5b1..946839d2f 100644 --- a/gcloud/beta/spanner/instances/add-iam-policy-binding +++ b/gcloud/beta/spanner/instances/add-iam-policy-binding @@ -4,10 +4,13 @@ NAME SYNOPSIS gcloud beta spanner instances add-iam-policy-binding [INSTANCE] - --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Add an IAM policy binding to a Cloud Spanner instance. + (BETA) Add an IAM policy binding to a Cloud Spanner instance. One binding + consists of a member, a role, and an optional condition. EXAMPLES To add an IAM policy binding for the role of 'roles/editor' for the user @@ -16,6 +19,17 @@ EXAMPLES $ gcloud beta spanner instances add-iam-policy-binding my-instance \ --member='user:test-user@gmail.com' --role='roles/editor' + To add an IAM policy binding which expires at the end of the year 2018 for + the role of 'roles/spanner.admin' and the user 'test-user@gmail.com' with + instance 'my-instance', run: + + $ gcloud beta spanner instances add-iam-policy-binding my-instance \ + --member='user:test-user@gmail.com' \ + --role='roles/spanner.admin' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' + See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. @@ -57,6 +71,44 @@ REQUIRED FLAGS for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer. +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/spanner/instances/remove-iam-policy-binding b/gcloud/beta/spanner/instances/remove-iam-policy-binding index 080bea109..f97b9c2b9 100644 --- a/gcloud/beta/spanner/instances/remove-iam-policy-binding +++ b/gcloud/beta/spanner/instances/remove-iam-policy-binding @@ -4,19 +4,33 @@ NAME SYNOPSIS gcloud beta spanner instances remove-iam-policy-binding [INSTANCE] - --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Remove an IAM policy binding of a Cloud Spanner instance. + (BETA) Remove an IAM policy binding of a Cloud Spanner instance. One + binding consists of a member, a role, and an optional condition. EXAMPLES - To Remove an IAM policy binding for the role of 'roles/editor' for the user + To remove an IAM policy binding for the role of 'roles/editor' for the user 'test-user@gmail.com' with instance 'my-instance', run: $ gcloud beta spanner instances remove-iam-policy-binding \ my-instance --member='user:test-user@gmail.com' \ --role='roles/editor' + To remove an IAM policy binding which expires at the end of the year 2018 + for the role of 'roles/spanner.admin' and the user 'test-user@gmail.com' + with instance 'my-instance', run: + + $ gcloud beta spanner instances remove-iam-policy-binding \ + my-instance --member='user:test-user@gmail.com' \ + --role='roles/spanner.admin' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' + See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. @@ -59,6 +73,48 @@ REQUIRED FLAGS --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, diff --git a/gcloud/beta/sql/connect b/gcloud/beta/sql/connect index a6f6fc2fd..445ef047e 100644 --- a/gcloud/beta/sql/connect +++ b/gcloud/beta/sql/connect @@ -7,8 +7,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Connects to Cloud SQL V2 instances through the Cloud SQL Proxy. - Connects to Cloud SQL V1 instances directly. + (BETA) Connects to a Cloud SQL instance. EXAMPLES To connect to a Cloud SQL instance, run: diff --git a/gcloud/beta/sql/export/sql b/gcloud/beta/sql/export/sql index 17a1c11a9..73ef69f9b 100644 --- a/gcloud/beta/sql/export/sql +++ b/gcloud/beta/sql/export/sql @@ -12,6 +12,11 @@ DESCRIPTION (BETA) Exports data from a Cloud SQL instance to a Google Cloud Storage bucket as a SQL dump file. + NOTE: Certain roles and permissions are required to export data to Google + Cloud Storage. For more information on exporting data from Google Cloud SQL + see Export from Cloud SQL to a SQL dump file + (https://cloud.google.com/sql/docs/mysql/import-export/import-export-sql#gcloud). + POSITIONAL ARGUMENTS INSTANCE Cloud SQL instance ID. diff --git a/gcloud/beta/sql/import/sql b/gcloud/beta/sql/import/sql index da85c012f..f2ac482e5 100644 --- a/gcloud/beta/sql/import/sql +++ b/gcloud/beta/sql/import/sql @@ -10,6 +10,11 @@ DESCRIPTION (BETA) gcloud beta sql import sql imports data into a Cloud SQL instance from a SQL dump file in Google Cloud Storage. + NOTE: Certain roles and permissions are required to import data into Google + Cloud SQL. For more information on importing data into Google Cloud SQL see + Import a SQL dump file + (https://cloud.google.com/sql/docs/mysql/import-export/import-export-sql#gcloud_1). + For detailed help on importing data into Cloud SQL, refer to this guide: https://cloud.google.com/sql/docs/mysql/import-export/importing diff --git a/gcloud/beta/terraform/help b/gcloud/beta/terraform/help new file mode 100644 index 000000000..046052a61 --- /dev/null +++ b/gcloud/beta/terraform/help @@ -0,0 +1,28 @@ +NAME + gcloud beta terraform - commands related to Terraform management of Google + Cloud Platform resources + +SYNOPSIS + gcloud beta terraform COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Commands related to Terraform management of Google Cloud Platform + resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + vet + (BETA) Validate that a terraform plan complies with policies. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha terraform + diff --git a/gcloud/beta/terraform/vet b/gcloud/beta/terraform/vet new file mode 100644 index 000000000..474c3c39a --- /dev/null +++ b/gcloud/beta/terraform/vet @@ -0,0 +1,41 @@ +NAME + gcloud beta terraform vet - validate that a terraform plan complies with + policies + +SYNOPSIS + gcloud beta terraform vet TERRAFORM_PLAN_JSON + --policy-library=POLICY_LIBRARY [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Validate that a terraform plan complies with policies. + +EXAMPLES + To validate that a terraform plan complies with a policy library at + /my/policy/library: + + $ gcloud beta terraform vet tfplan.json \ + --policy-library=/my/policy/library + +POSITIONAL ARGUMENTS + TERRAFORM_PLAN_JSON + File which contains a JSON export of a terraform plan. This file will + be validated against the given policy library. + +REQUIRED FLAGS + --policy-library=POLICY_LIBRARY + Directory which contains a policy library + +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 terraform vet + diff --git a/gcloud/composer/environments/create b/gcloud/composer/environments/create index 1fd58e81b..864ec6963 100644 --- a/gcloud/composer/environments/create +++ b/gcloud/composer/environments/create @@ -171,11 +171,15 @@ FLAGS At most one of these can be specified: --airflow-version=AIRFLOW_VERSION - Version of Airflow to run in the environment. + Version of Apache Airflow to run in the environment. - Must be of the form `X.Y[.Z]`. + Must be of the form `X[.Y[.Z]]`, where `[]` denotes optional fragments. The current Cloud Composer version will be used within the created + environment. The Apache Airflow version is a semantic version or an alias + in the form of major or major.minor version numbers, resolved to the + latest matching Apache Airflow version supported in the current Cloud + Composer version. The resolved version is stored in the created environment. --image-version=IMAGE_VERSION @@ -183,15 +187,16 @@ FLAGS The image version encapsulates the versions of both Cloud Composer and Apache Airflow. Must be of the form - `composer-A[.B.C[-D.E]]-airflow-X.Y[.Z]`. + `composer-A[.B.C[-D.E]]-airflow-X[.Y[.Z]]`, where `[]` denotes optional + fragments. - The Cloud Composer and Airflow versions are semantic versions. - `latest` can be provided instead of an explicit Cloud Composer - version number indicating that the server will replace `latest` - with the current Cloud Composer version. For the Apache Airflow - portion, the patch version can be omitted and the current - version will be selected. The version numbers that are used will - be stored. + The Cloud Composer portion of the image version is a semantic version or + an alias in the form of major version number or `latest`, resolved to the + current Cloud Composer version. The Apache Airflow portion of the image + version is a semantic version or an alias in the form of major or + major.minor version numbers, resolved to the latest matching Apache + Airflow version supported in the given Cloud Composer version. The + resolved versions are stored in the created environment. Private Clusters diff --git a/gcloud/compute/backend-services/export b/gcloud/compute/backend-services/export index 7bc690d71..db4d20612 100644 --- a/gcloud/compute/backend-services/export +++ b/gcloud/compute/backend-services/export @@ -22,10 +22,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/BackendService.yaml. At most one of these can be specified: diff --git a/gcloud/compute/backend-services/import b/gcloud/compute/backend-services/import index c620f7d28..3683edf89 100644 --- a/gcloud/compute/backend-services/import +++ b/gcloud/compute/backend-services/import @@ -20,10 +20,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/BackendService.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/compute/forwarding-rules/export b/gcloud/compute/forwarding-rules/export index ad3d3f8df..9bc505788 100644 --- a/gcloud/compute/forwarding-rules/export +++ b/gcloud/compute/forwarding-rules/export @@ -20,10 +20,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/ForwardingRule.yaml. At most one of these can be specified: diff --git a/gcloud/compute/forwarding-rules/import b/gcloud/compute/forwarding-rules/import index 7b0366681..218af1285 100644 --- a/gcloud/compute/forwarding-rules/import +++ b/gcloud/compute/forwarding-rules/import @@ -19,10 +19,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/ForwardingRule.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/compute/instances/update-from-file b/gcloud/compute/instances/update-from-file index 5c5bbe57f..b9dee7654 100644 --- a/gcloud/compute/instances/update-from-file +++ b/gcloud/compute/instances/update-from-file @@ -38,10 +38,9 @@ FLAGS default will be REFRESH. --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/Instance.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/compute/target-http-proxies/export b/gcloud/compute/target-http-proxies/export index 28e41d567..25c3cfbc8 100644 --- a/gcloud/compute/target-http-proxies/export +++ b/gcloud/compute/target-http-proxies/export @@ -21,10 +21,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/TargetHttpProxy.yaml. At most one of these can be specified: diff --git a/gcloud/compute/target-http-proxies/import b/gcloud/compute/target-http-proxies/import index 4d193a2f5..342c2ee9b 100644 --- a/gcloud/compute/target-http-proxies/import +++ b/gcloud/compute/target-http-proxies/import @@ -20,10 +20,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/TargetHttpProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/compute/target-https-proxies/export b/gcloud/compute/target-https-proxies/export index e704d8551..013da500c 100644 --- a/gcloud/compute/target-https-proxies/export +++ b/gcloud/compute/target-https-proxies/export @@ -21,10 +21,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/TargetHttpsProxy.yaml. At most one of these can be specified: diff --git a/gcloud/compute/target-https-proxies/import b/gcloud/compute/target-https-proxies/import index 1142a67a1..f0a3f740c 100644 --- a/gcloud/compute/target-https-proxies/import +++ b/gcloud/compute/target-https-proxies/import @@ -20,10 +20,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/TargetHttpsProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/compute/url-maps/export b/gcloud/compute/url-maps/export index bf3b54c0d..48f232ffa 100644 --- a/gcloud/compute/url-maps/export +++ b/gcloud/compute/url-maps/export @@ -20,10 +20,9 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. For a schema - describing the export/import format, see: + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/UrlMap.yaml. At most one of these can be specified: diff --git a/gcloud/compute/url-maps/import b/gcloud/compute/url-maps/import index 8040f606a..d805cc47e 100644 --- a/gcloud/compute/url-maps/import +++ b/gcloud/compute/url-maps/import @@ -19,10 +19,9 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input.For a schema describing the - export/import format, see: + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/UrlMap.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/config/get b/gcloud/config/get index d533c3c2e..aa59e3620 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -936,6 +936,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/config/help b/gcloud/config/help index 3ed59104e..ff6c0f1f1 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -968,6 +968,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/config/list b/gcloud/config/list index 4018ef265..e18f1ac90 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -970,6 +970,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/config/set b/gcloud/config/set index c76d8ede6..97d944535 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -983,6 +983,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/config/unset b/gcloud/config/unset index ad4047d41..d198f2ea0 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -944,6 +944,9 @@ AVAILABLE PROPERTIES back to this value, if set. scc + location + Default location gcloud should use for scc slz-overwatch surface. + organization Default organization gcloud should use for scc surface. diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index e5dae3824..4cb72ba0e 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -32,7 +32,7 @@ SYNOPSIS [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] [--max-nodes-per-pool=MAX_NODES_PER_POOL] [--max-pods-per-node=MAX_PODS_PER_NODE] - [--max-surge-upgrade=MAX_SURGE_UPGRADE] + [--max-surge-upgrade=MAX_SURGE_UPGRADE; default=1] [--max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] @@ -541,7 +541,7 @@ FLAGS Must be used in conjunction with '--enable-ip-alias'. - --max-surge-upgrade=MAX_SURGE_UPGRADE + --max-surge-upgrade=MAX_SURGE_UPGRADE; default=1 Number of extra (surge) nodes to be created on each upgrade of a node pool. diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index d194327a8..fad3c5346 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -12,16 +12,17 @@ SYNOPSIS [--image-type=IMAGE_TYPE] [--local-ssd-count=LOCAL_SSD_COUNT] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] [--max-pods-per-node=MAX_PODS_PER_NODE] - [--max-surge-upgrade=MAX_SURGE_UPGRADE] + [--max-surge-upgrade=MAX_SURGE_UPGRADE; default=1] [--max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] - [--min-cpu-platform=PLATFORM] [--node-group=NODE_GROUP] - [--node-labels=[NODE_LABEL,...]] [--node-locations=ZONE,[ZONE,...]] - [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] - [--num-nodes=NUM_NODES; default=3] [--preemptible] - [--sandbox=[type=TYPE]] [--shielded-integrity-monitoring] - [--shielded-secure-boot] [--spot] + [--min-cpu-platform=PLATFORM] + [--network-performance-configs=[PROPERTY=VALUE,...]] + [--node-group=NODE_GROUP] [--node-labels=[NODE_LABEL,...]] + [--node-locations=ZONE,[ZONE,...]] [--node-taints=[NODE_TAINT,...]] + [--node-version=NODE_VERSION] [--num-nodes=NUM_NODES; default=3] + [--preemptible] [--sandbox=[type=TYPE]] + [--shielded-integrity-monitoring] [--shielded-secure-boot] [--spot] [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--workload-metadata=WORKLOAD_METADATA] @@ -177,7 +178,7 @@ FLAGS Must be used in conjunction with '--enable-ip-alias'. - --max-surge-upgrade=MAX_SURGE_UPGRADE + --max-surge-upgrade=MAX_SURGE_UPGRADE; default=1 Number of extra (surge) nodes to be created on each upgrade of the node pool. @@ -262,6 +263,17 @@ FLAGS CPU platform selection is available only in selected zones. + --network-performance-configs=[PROPERTY=VALUE,...] + Configures network performance settings for the node pool. If this flag + is not specified, the pool will be created with its default network + performance configuration. + + total-egress-bandwidth-tier + Total egress bandwidth is the available outbound bandwidth from a + VM, regardless of whether the traffic is going to internal IP or + external IP destinations. The following tier values are allowed: + [DEFAULT,TIER_1] + --node-group=NODE_GROUP Assign instances of this pool to run on the specified Google Compute Engine node group. This is useful for running workloads on sole tenant diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index 984752756..648e3729e 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud container node-pools update NAME (--enable-gvnic | --enable-image-streaming + | --network-performance-configs=[PROPERTY=VALUE,...] | --node-locations=ZONE,[ZONE,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE | --workload-metadata=WORKLOAD_METADATA | --enable-autoprovisioning @@ -40,6 +41,17 @@ REQUIRED FLAGS --enable-image-streaming Specifies whether to enable image streaming on node pool. + --network-performance-configs=[PROPERTY=VALUE,...] + Configures network performance settings for the node pool. If this + flag is not specified, the pool will be created with its default + network performance configuration. + + total-egress-bandwidth-tier + Total egress bandwidth is the available outbound bandwidth from a + VM, regardless of whether the traffic is going to internal IP or + external IP destinations. The following tier values are allowed: + [DEFAULT,TIER_1] + --node-locations=ZONE,[ZONE,...] Set of zones in which the node pool's nodes should be located. Changing the locations for a node pool will result in nodes being diff --git a/gcloud/dataproc/autoscaling-policies/export b/gcloud/dataproc/autoscaling-policies/export index 965a6bb9b..74b69e468 100644 --- a/gcloud/dataproc/autoscaling-policies/export +++ b/gcloud/dataproc/autoscaling-policies/export @@ -52,9 +52,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/dataproc/autoscaling-policies/import b/gcloud/dataproc/autoscaling-policies/import index 83dd8d804..992498c53 100644 --- a/gcloud/dataproc/autoscaling-policies/import +++ b/gcloud/dataproc/autoscaling-policies/import @@ -56,9 +56,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input. + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/dataproc/clusters/export b/gcloud/dataproc/clusters/export index e481b1c56..9bbf50896 100644 --- a/gcloud/dataproc/clusters/export +++ b/gcloud/dataproc/clusters/export @@ -52,9 +52,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/dataproc/clusters/import b/gcloud/dataproc/clusters/import index 094ee7fdb..801365fca 100644 --- a/gcloud/dataproc/clusters/import +++ b/gcloud/dataproc/clusters/import @@ -56,9 +56,8 @@ FLAGS complete. --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input. + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/dataproc/workflow-templates/export b/gcloud/dataproc/workflow-templates/export index 82e515f0f..c62220433 100644 --- a/gcloud/dataproc/workflow-templates/export +++ b/gcloud/dataproc/workflow-templates/export @@ -50,9 +50,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. --version=VERSION The version of the workflow template. diff --git a/gcloud/dataproc/workflow-templates/import b/gcloud/dataproc/workflow-templates/import index 93681507c..03496a1b5 100644 --- a/gcloud/dataproc/workflow-templates/import +++ b/gcloud/dataproc/workflow-templates/import @@ -44,9 +44,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE - Path to a YAML file containing configuration export data. The YAML file - must not contain any output-only fields. Alternatively, you may omit - this flag to read from standard input. + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/deploy/delivery-pipelines/export b/gcloud/deploy/delivery-pipelines/export index a63ac5ee3..5b7c65ff6 100644 --- a/gcloud/deploy/delivery-pipelines/export +++ b/gcloud/deploy/delivery-pipelines/export @@ -47,9 +47,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/deploy/targets/export b/gcloud/deploy/targets/export index 3b33e90f7..cb83324b1 100644 --- a/gcloud/deploy/targets/export +++ b/gcloud/deploy/targets/export @@ -45,9 +45,8 @@ POSITIONAL ARGUMENTS FLAGS --destination=DESTINATION - Path to a YAML file where the configuration will be exported. The - exported data will not contain any output-only fields. Alternatively, - you may omit this flag to write to standard output. + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/edge-cloud/container/clusters/create b/gcloud/edge-cloud/container/clusters/create new file mode 100644 index 000000000..a6ef0964c --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/create @@ -0,0 +1,117 @@ +NAME + gcloud edge-cloud container clusters create - create an Edge Container + cluster + +SYNOPSIS + gcloud edge-cloud container clusters create (CLUSTER : --location=LOCATION) + [--admin-users=ADMIN_USERS] [--async] + [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR; default="10.0.0.0/17"] + [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] + [--fleet-project=FLEET_PROJECT] [--labels=[KEY=VALUE,...]] + [--maintenance-window-end=MAINTENANCE_WINDOW_END] + [--maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE] + [--maintenance-window-start=MAINTENANCE_WINDOW_START] + [--services-ipv4-cidr=SERVICES_IPV4_CIDR; default="10.96.0.0/12"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create an Edge Container cluster. + +EXAMPLES + To create a cluster called 'my-cluster' in region us-central1, run: + + $ gcloud edge-cloud container clusters create my-cluster \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Cluster resource - Edge Container cluster to create. 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 cluster on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. To + set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +FLAGS + --admin-users=ADMIN_USERS + Username (Google email address) of the user who should be granted + cluster-admin initially. This currently supports exactly one admin. If + not set, the account issuing the creation request will be used by + default. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --cluster-ipv4-cidr=CLUSTER_IPV4_CIDR; default="10.0.0.0/17" + All pods in the cluster are assigned an RFC1918 IPv4 address from this + block. This field cannot be changed after creation. + + --default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE + The default maximum number of pods per node. + + --fleet-project=FLEET_PROJECT + Name of the Fleet host project where the cluster is registered. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + --maintenance-window-end=MAINTENANCE_WINDOW_END + End time of the recurring cluster maintenance window in the RFC 3339 + (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + + --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE + An RFC 5545 (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) + recurrence rule for how the cluster maintenance window recurs. They go + on for the span of time between the start and the end time. + + --maintenance-window-start=MAINTENANCE_WINDOW_START + Start time of the recurring cluster maintenance window in the RFC 3339 + (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + + --services-ipv4-cidr=SERVICES_IPV4_CIDR; default="10.96.0.0/12" + All services in the cluster are assigned an RFC1918 IPv4 address from + this block. This field cannot be changed after creation. + +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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters create + diff --git a/gcloud/edge-cloud/container/clusters/delete b/gcloud/edge-cloud/container/clusters/delete new file mode 100644 index 000000000..42329d186 --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/delete @@ -0,0 +1,66 @@ +NAME + gcloud edge-cloud container clusters delete - delete an Edge Container + cluster + +SYNOPSIS + gcloud edge-cloud container clusters delete (CLUSTER : --location=LOCATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an Edge Container cluster. + +EXAMPLES + To delete a cluster called 'my-cluster' in region us-central1, run: + + $ gcloud edge-cloud container clusters delete my-cluster \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Cluster resource - Edge Container cluster to delete. 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 cluster on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. To + set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters delete + diff --git a/gcloud/edge-cloud/container/clusters/describe b/gcloud/edge-cloud/container/clusters/describe new file mode 100644 index 000000000..698846d97 --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/describe @@ -0,0 +1,62 @@ +NAME + gcloud edge-cloud container clusters describe - show details about the + cluster + +SYNOPSIS + gcloud edge-cloud container clusters describe + (CLUSTER : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details about the cluster. + +EXAMPLES + To show details about a cluster called 'my-cluster' in region us-central1, + run: + + $ gcloud edge-cloud container clusters describe my-cluster \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Cluster resource - The cluster you want to describe. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. To + set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters describe + diff --git a/gcloud/edge-cloud/container/clusters/get-credentials b/gcloud/edge-cloud/container/clusters/get-credentials new file mode 100644 index 000000000..af86ba5fb --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/get-credentials @@ -0,0 +1,73 @@ +NAME + gcloud edge-cloud container clusters get-credentials - get credentials of + an edge-container cluster + +SYNOPSIS + gcloud edge-cloud container clusters get-credentials + (CLUSTER : --location=LOCATION) + [--auth-provider-cmd-path=AUTH_PROVIDER_CMD_PATH] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Fetch credentials for a running Edge Container cluster. This command + updates a kubeconfig file with appropriate credentials and endpoint + information to point kubectl at a specific Edge Container cluster. By + default, credentials are written to HOME/.kube/config. You can provide an + alternate path by setting the KUBECONFIG environment variable. If + KUBECONFIG contains multiple paths, the first one is used. This command + enables switching to a specific cluster, when working with multiple + clusters. It can also be used to access a previously created cluster from a + new workstation. The command will configure kubectl to automatically + refresh its credentials using the same identity as the gcloud command-line + tool. See https://cloud.google.com/kubernetes-engine/docs/kubectl for + kubectl documentation. + +EXAMPLES + To get credentials of a cluster named my-cluster managed in location + us-west1, run: $ gcloud edge-cloud container clusters get-credentials my-cluster \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Cluster resource - edge-cloud container cluster to get credentials. 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 cluster 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. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. To + set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --auth-provider-cmd-path=AUTH_PROVIDER_CMD_PATH + Path to the gcloud executable for the auth provider field in + kubeconfig. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters get-credentials + diff --git a/gcloud/edge-cloud/container/clusters/help b/gcloud/edge-cloud/container/clusters/help new file mode 100644 index 000000000..ce3c725a4 --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/help @@ -0,0 +1,46 @@ +NAME + gcloud edge-cloud container clusters - manage Kubernetes Edge clusters + +SYNOPSIS + gcloud edge-cloud container clusters GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Kubernetes Edge clusters. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + node-pools + Manage Kubernetes Edge node pools. + +COMMANDS + COMMAND is one of the following: + + create + Create an Edge Container cluster. + + delete + Delete an Edge Container cluster. + + describe + Show details about the cluster. + + get-credentials + Get credentials of an edge-container cluster. + + list + List Edge Container clusters. + + update + Update an Edge Container cluster. + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters + diff --git a/gcloud/edge-cloud/container/clusters/list b/gcloud/edge-cloud/container/clusters/list new file mode 100644 index 000000000..52c5ea006 --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/list @@ -0,0 +1,82 @@ +NAME + gcloud edge-cloud container clusters list - list Edge Container clusters + +SYNOPSIS + gcloud edge-cloud container clusters list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Edge Container clusters. + +EXAMPLES + To list the clusters in region us-central1, run: + + $ gcloud edge-cloud container clusters list --location=us-central1 + +FLAGS + Location resource - Parent Edge Container location to list all contained + Edge Container clusters. 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; + ◆ set the property edge_container/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; + ▸ set the property edge_container/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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters list + diff --git a/gcloud/edge-cloud/container/clusters/node-pools/create b/gcloud/edge-cloud/container/clusters/node-pools/create new file mode 100644 index 000000000..f49ff68aa --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/node-pools/create @@ -0,0 +1,120 @@ +NAME + gcloud edge-cloud container clusters node-pools create - create an Edge + Container node pool + +SYNOPSIS + gcloud edge-cloud container clusters node-pools create + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) + --node-count=NODE_COUNT --node-location=NODE_LOCATION [--async] + [--labels=[KEY=VALUE,...]] [--local-disk-kms-key=LOCAL_DISK_KMS_KEY] + [--machine-filter=MACHINE_FILTER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new Edge Container nodePool. + +EXAMPLES + To create a node pool called 'my-nodePool', containing 3 nodes in region + us-central1, run: + + $ gcloud edge-cloud container clusters node-pools create \ + my-nodePool --cluster= --location=us-central1 \ + --node-location= --node-count=3 + + To create a node pool called 'my-nodePool', containing 3 nodes in region + us-central1, using only machine names matching a specific pattern, run: + + $ gcloud edge-cloud container clusters node-pools create \ + my-nodePool --cluster= --location=us-central1 \ + --node-location= --node-count=3 \ + --machine-filter="name:" + + To create a node pool called 'my-nodePool', containing 3 nodes in region + us-central1, using only machine names NOT matching a specific pattern, run: + + $ gcloud edge-cloud container clusters node-pools create \ + my-nodePool --cluster= --location=us-central1 \ + --node-location= --node-count=3 \ + --machine-filter="NOT name:" + +POSITIONAL ARGUMENTS + Node pool resource - Edge Container node pool to create. 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 node_pool on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NODE_POOL + ID of the node pool or fully qualified identifier for the node pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --cluster=CLUSTER + Kubernetes cluster. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +REQUIRED FLAGS + --node-count=NODE_COUNT + Default nodeCount used by this node pool. + + --node-location=NODE_LOCATION + Google Edge Cloud zone where nodes in this node pool will be created. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + --local-disk-kms-key=LOCAL_DISK_KMS_KEY + Google Cloud KMS key that will be used to secure local disks on nodes + in this node pool. The Edge Container service account for this project + must have roles/cloudkms.cryptoKeyEncrypterDecrypter on the key. + + If not provided, a Google-managed key will be used instead. + + --machine-filter=MACHINE_FILTER + Only machines matching this filter will be allowed to join the node + pool. The filtering language accepts strings like "name=", and is + documented in more detail at https://google.aip.dev/160. + +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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters node-pools create + diff --git a/gcloud/edge-cloud/container/clusters/node-pools/delete b/gcloud/edge-cloud/container/clusters/node-pools/delete new file mode 100644 index 000000000..3976ec88c --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/node-pools/delete @@ -0,0 +1,73 @@ +NAME + gcloud edge-cloud container clusters node-pools delete - delete an Edge + Container nodePool + +SYNOPSIS + gcloud edge-cloud container clusters node-pools delete + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an Edge Container nodePool. + +EXAMPLES + To delete a nodePool called 'my-nodePool' in region us-central1, run: + + $ gcloud edge-cloud container clusters node-pools delete \ + my-nodePool --cluster= --location=us-central1 + +POSITIONAL ARGUMENTS + Node pool resource - Edge Container nodePool to delete. 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 node_pool on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NODE_POOL + ID of the node pool or fully qualified identifier for the node pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --cluster=CLUSTER + Kubernetes cluster. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters node-pools delete + diff --git a/gcloud/edge-cloud/container/clusters/node-pools/describe b/gcloud/edge-cloud/container/clusters/node-pools/describe new file mode 100644 index 000000000..7d64f5d9b --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/node-pools/describe @@ -0,0 +1,69 @@ +NAME + gcloud edge-cloud container clusters node-pools describe - show details + about the nodePool + +SYNOPSIS + gcloud edge-cloud container clusters node-pools describe + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details about the nodePool. + +EXAMPLES + To show details about a node pool called 'my-nodePool' in region + us-central1, run: + + $ gcloud edge-cloud container clusters node-pools describe \ + my-nodePool --location=us-central1 --cluster= + +POSITIONAL ARGUMENTS + Node pool resource - The nodePool you want to describe. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. To set the project attribute: + ◆ provide the argument node_pool on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NODE_POOL + ID of the node pool or fully qualified identifier for the node pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --cluster=CLUSTER + Kubernetes cluster. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters node-pools describe + diff --git a/gcloud/edge-cloud/container/clusters/node-pools/help b/gcloud/edge-cloud/container/clusters/node-pools/help new file mode 100644 index 000000000..ecc89179f --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/node-pools/help @@ -0,0 +1,39 @@ +NAME + gcloud edge-cloud container clusters node-pools - manage Kubernetes Edge + node pools + +SYNOPSIS + gcloud edge-cloud container clusters node-pools COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Kubernetes Edge node pools. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create an Edge Container node pool. + + delete + Delete an Edge Container nodePool. + + describe + Show details about the nodePool. + + list + List Edge Container nodePools. + + update + Updates an Edge Container node pool. + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters node-pools + diff --git a/gcloud/edge-cloud/container/clusters/node-pools/list b/gcloud/edge-cloud/container/clusters/node-pools/list new file mode 100644 index 000000000..6e1c50af6 --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/node-pools/list @@ -0,0 +1,96 @@ +NAME + gcloud edge-cloud container clusters node-pools list - list Edge Container + nodePools + +SYNOPSIS + gcloud edge-cloud container clusters node-pools list + (--cluster=CLUSTER : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Edge Container nodePools. + +EXAMPLES + To list the nodePools in region us-central1, run: + + $ gcloud edge-cloud container clusters node-pools list \ + --location=us-central1 --cluster= + +REQUIRED FLAGS + Cluster resource - Parent Edge Container location to list all contained + Edge Container nodePools. 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 --cluster on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. To + set the cluster attribute: + ▸ provide the argument --cluster on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument --cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters node-pools list + diff --git a/gcloud/edge-cloud/container/clusters/node-pools/update b/gcloud/edge-cloud/container/clusters/node-pools/update new file mode 100644 index 000000000..66dd767e8 --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/node-pools/update @@ -0,0 +1,115 @@ +NAME + gcloud edge-cloud container clusters node-pools update - updates an Edge + Container node pool + +SYNOPSIS + gcloud edge-cloud container clusters node-pools update + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] + [--machine-filter=MACHINE_FILTER] [--node-count=NODE_COUNT] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates an Edge Container node pool. + +EXAMPLES + To update the number of nodes in a node pool called 'my-node-pool' in + region us-central1, run: + + $ gcloud edge-cloud container clusters node-pools update \ + my-node-pool --location=us-central1 --cluster= \ + --node-count= + +POSITIONAL ARGUMENTS + Node pool resource - Edge Container node pool 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 node_pool on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NODE_POOL + ID of the node pool or fully qualified identifier for the node pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --cluster=CLUSTER + Kubernetes cluster. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --machine-filter=MACHINE_FILTER + Only machines matching this filter will be allowed to join the node + pool. The filtering language accepts strings like "name=", and is + documented in more detail at https://google.aip.dev/160. + + --node-count=NODE_COUNT + Default nodeCount used by this node pool. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud edge-cloud container clusters node-pools update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud edge-cloud container clusters node-pools update \ + --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters node-pools update + diff --git a/gcloud/edge-cloud/container/clusters/update b/gcloud/edge-cloud/container/clusters/update new file mode 100644 index 000000000..398d38ec6 --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/update @@ -0,0 +1,86 @@ +NAME + gcloud edge-cloud container clusters update - update an Edge Container + cluster + +SYNOPSIS + gcloud edge-cloud container clusters update (CLUSTER : --location=LOCATION) + [--async] [--maintenance-window-end=MAINTENANCE_WINDOW_END] + [--maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE] + [--maintenance-window-start=MAINTENANCE_WINDOW_START] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an Edge Container cluster. + +EXAMPLES + To update the maintenance window recurrence rule of a cluster called + 'my-cluster' in region us-central1, run: + + $ gcloud edge-cloud container clusters update my-cluster \ + --location=us-central1 \ + --maintenance-window-recurrence="FREQ=WEEKLY" + +POSITIONAL ARGUMENTS + Cluster resource - Edge Container cluster 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 cluster on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. To + set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --maintenance-window-end=MAINTENANCE_WINDOW_END + End time of the recurring cluster maintenance window in the RFC 3339 + (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + + --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE + An RFC 5545 (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) + recurrence rule for how the cluster maintenance window recurs. They go + on for the span of time between the start and the end time. + + --maintenance-window-start=MAINTENANCE_WINDOW_START + Start time of the recurring cluster maintenance window in the RFC 3339 + (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + +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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters update + diff --git a/gcloud/edge-cloud/container/help b/gcloud/edge-cloud/container/help new file mode 100644 index 000000000..ab90f6af4 --- /dev/null +++ b/gcloud/edge-cloud/container/help @@ -0,0 +1,41 @@ +NAME + gcloud edge-cloud container - manage Edge Container resources + +SYNOPSIS + gcloud edge-cloud container GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Edge Container resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + clusters + Manage Kubernetes Edge clusters. + + machines + Manage Kubernetes Edge machines. + + operations + Command group for working with Kubernetes Edge operations. + + regions + Manages Edge Container regions. + + vpn-connections + Manage Edge VPN connections between an Edge Container cluster and a VPC + network. + + zones + Inspect Edge Container zones. + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container + diff --git a/gcloud/edge-cloud/container/machines/describe b/gcloud/edge-cloud/container/machines/describe new file mode 100644 index 000000000..42b048515 --- /dev/null +++ b/gcloud/edge-cloud/container/machines/describe @@ -0,0 +1,62 @@ +NAME + gcloud edge-cloud container machines describe - show details about the + machine + +SYNOPSIS + gcloud edge-cloud container machines describe + (MACHINE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details about the machine. + +EXAMPLES + To show details about a machine called 'my-machine' in region us-central1, + run: + + $ gcloud edge-cloud container machines describe my-machine \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Machine resource - The machine you want to describe. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. To set the project attribute: + ◆ provide the argument machine on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + MACHINE + ID of the machine or fully qualified identifier for the machine. To + set the machine attribute: + ▸ provide the argument machine on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument machine on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container machines describe + diff --git a/gcloud/edge-cloud/container/machines/help b/gcloud/edge-cloud/container/machines/help new file mode 100644 index 000000000..b945aa2f7 --- /dev/null +++ b/gcloud/edge-cloud/container/machines/help @@ -0,0 +1,28 @@ +NAME + gcloud edge-cloud container machines - manage Kubernetes Edge machines + +SYNOPSIS + gcloud edge-cloud container machines COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Kubernetes Edge machines. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Show details about the machine. + + list + List Edge Container machines. + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container machines + diff --git a/gcloud/edge-cloud/container/machines/list b/gcloud/edge-cloud/container/machines/list new file mode 100644 index 000000000..53b031488 --- /dev/null +++ b/gcloud/edge-cloud/container/machines/list @@ -0,0 +1,82 @@ +NAME + gcloud edge-cloud container machines list - list Edge Container machines + +SYNOPSIS + gcloud edge-cloud container machines list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Edge Container machines. + +EXAMPLES + To list the machines in region us-central1, run: + + $ gcloud edge-cloud container machines list --location=us-central1 + +FLAGS + Location resource - Parent Edge Container location to list all contained + Edge Container machines. 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; + ◆ set the property edge_container/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; + ▸ set the property edge_container/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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container machines list + diff --git a/gcloud/edge-cloud/container/operations/describe b/gcloud/edge-cloud/container/operations/describe new file mode 100644 index 000000000..46096f62a --- /dev/null +++ b/gcloud/edge-cloud/container/operations/describe @@ -0,0 +1,63 @@ +NAME + gcloud edge-cloud container operations describe - get description of a + long-running edge container operation + +SYNOPSIS + gcloud edge-cloud container operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get information about a long-running edge container operation. + +EXAMPLES + To get information about a long-running operation with name + 'projects/my-project/locations/us-east1/operations/123', run the following + command: + + $ gcloud edge-cloud container operations describe \ + projects/my-project/locations/us-east1/operations/123 + +POSITIONAL ARGUMENTS + Operation resource - The ID of the operation to describe. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. To set the project attribute: + ◆ provide the argument operation on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. 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; + ▸ set the property edge_container/location. + +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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container operations describe + diff --git a/gcloud/edge-cloud/container/operations/help b/gcloud/edge-cloud/container/operations/help new file mode 100644 index 000000000..182a123bc --- /dev/null +++ b/gcloud/edge-cloud/container/operations/help @@ -0,0 +1,29 @@ +NAME + gcloud edge-cloud container operations - command group for working with + Kubernetes Edge operations + +SYNOPSIS + gcloud edge-cloud container operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Command group for working with Kubernetes Edge operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Get description of a long-running edge container operation. + + wait + Poll long-running edge container operation until it completes. + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container operations + diff --git a/gcloud/edge-cloud/container/operations/wait b/gcloud/edge-cloud/container/operations/wait new file mode 100644 index 000000000..c445ce083 --- /dev/null +++ b/gcloud/edge-cloud/container/operations/wait @@ -0,0 +1,65 @@ +NAME + gcloud edge-cloud container operations wait - poll long-running edge + container operation until it completes + +SYNOPSIS + gcloud edge-cloud container operations wait + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Poll a long-running edge container operation until it completes. When the + operation is complete, this command will display the results of the + analysis. + +EXAMPLES + To poll a long-running edge container operation named + 'projects/my-project/locations/us-east1/operations/123' until it completes, + run the following: + + $ gcloud edge-cloud container operations wait \ + projects/my-project/locations/us-east1/operations/123 + +POSITIONAL ARGUMENTS + Operation resource - ID for the operation to poll until complete. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: + ◆ provide the argument operation on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. 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; + ▸ set the property edge_container/location. + +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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container operations wait + diff --git a/gcloud/edge-cloud/container/regions/describe b/gcloud/edge-cloud/container/regions/describe new file mode 100644 index 000000000..4c6b0affb --- /dev/null +++ b/gcloud/edge-cloud/container/regions/describe @@ -0,0 +1,49 @@ +NAME + gcloud edge-cloud container regions describe - describe an Edge Container + region (location) + +SYNOPSIS + gcloud edge-cloud container regions describe [LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an Edge Container region (location). + +EXAMPLES + To display the metadata for the region us-central1, run: + + $ gcloud edge-cloud container regions describe us-central1 + +POSITIONAL ARGUMENTS + Location resource - The region to describe. 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; + ◆ set the property edge_container/location with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + [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; + ▸ set the property edge_container/location. + +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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container regions describe + diff --git a/gcloud/edge-cloud/container/regions/help b/gcloud/edge-cloud/container/regions/help new file mode 100644 index 000000000..c7a53b7fe --- /dev/null +++ b/gcloud/edge-cloud/container/regions/help @@ -0,0 +1,28 @@ +NAME + gcloud edge-cloud container regions - manages Edge Container regions + +SYNOPSIS + gcloud edge-cloud container regions COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manages Edge Container regions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe an Edge Container region (location). + + list + List Edge Container regions. + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container regions + diff --git a/gcloud/edge-cloud/container/regions/list b/gcloud/edge-cloud/container/regions/list new file mode 100644 index 000000000..322dff1b0 --- /dev/null +++ b/gcloud/edge-cloud/container/regions/list @@ -0,0 +1,66 @@ +NAME + gcloud edge-cloud container regions list - list Edge Container regions + +SYNOPSIS + gcloud edge-cloud container regions list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all regions (locations) where Edge Container clusters can be created. + +EXAMPLES + To list all the regions (locations) where Edge Container clusters can be + created, run: + + $ gcloud edge-cloud container regions list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container regions list + diff --git a/gcloud/edge-cloud/container/vpn-connections/create b/gcloud/edge-cloud/container/vpn-connections/create new file mode 100644 index 000000000..55257696c --- /dev/null +++ b/gcloud/edge-cloud/container/vpn-connections/create @@ -0,0 +1,98 @@ +NAME + gcloud edge-cloud container vpn-connections create - create a VPN + connection between an Edge Container cluster and a VPC network + +SYNOPSIS + gcloud edge-cloud container vpn-connections create + (VPN_CONNECTION : --location=LOCATION) --cluster=CLUSTER + --vpc-network=VPC_NETWORK [--async] [--high-availability] + [--labels=[KEY=VALUE,...]] [--nat-gateway-ip=NAT_GATEWAY_IP] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Creates a new VPN connection. + +EXAMPLES + To create a connection called 'my-vpn-connection' between the VPC network + 'my-vpc' and the Edge Container cluster 'my-cluster' which is at region + us-central1, run: + + $ gcloud edge-cloud container vpn-connections create \ + my-vpn-connection --location=us-central1 \ + --vpc-network='my-vpc' --cluster='my-cluster' + + Here VPC network and cluster should be under the same project. + +POSITIONAL ARGUMENTS + Vpn connection resource - VPN connection to create. 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 vpn_connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + VPN_CONNECTION + ID of the vpn connection or fully qualified identifier for the vpn + connection. To set the vpn_connection attribute: + ▸ provide the argument vpn_connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument vpn_connection on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +REQUIRED FLAGS + --cluster=CLUSTER + The name of the cluster to be connected under current project. + + --vpc-network=VPC_NETWORK + The name of the {vpc_name_short} to be connected under current project. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --high-availability + Enables high availability on cluster side. This creates an additional + VPN endpoint in cluster. Multiple Nodes/NodePools are required to + enable this feature. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + --nat-gateway-ip=NAT_GATEWAY_IP + The NAT gateway IP for the gateway floating IPs. Do not specify this if + no NAT is used. + +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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container vpn-connections create + diff --git a/gcloud/edge-cloud/container/vpn-connections/delete b/gcloud/edge-cloud/container/vpn-connections/delete new file mode 100644 index 000000000..52ff6845d --- /dev/null +++ b/gcloud/edge-cloud/container/vpn-connections/delete @@ -0,0 +1,67 @@ +NAME + gcloud edge-cloud container vpn-connections delete - delete a VPN + connection between an Edge Container cluster and a VPC network + +SYNOPSIS + gcloud edge-cloud container vpn-connections delete + (VPN_CONNECTION : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a VPN connection. + +EXAMPLES + To delete a VPN connection called 'test-vpn-connection' at region + 'us-central1', run: + + $ gcloud edge-cloud container vpn-connections delete \ + test-vpn-connection --location=us-central1 + +POSITIONAL ARGUMENTS + Vpn connection resource - VPN connection to delete. 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 vpn_connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + VPN_CONNECTION + ID of the vpn connection or fully qualified identifier for the vpn + connection. To set the vpn_connection attribute: + ▸ provide the argument vpn_connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument vpn_connection on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container vpn-connections delete + diff --git a/gcloud/edge-cloud/container/vpn-connections/describe b/gcloud/edge-cloud/container/vpn-connections/describe new file mode 100644 index 000000000..bbc8e8b0f --- /dev/null +++ b/gcloud/edge-cloud/container/vpn-connections/describe @@ -0,0 +1,62 @@ +NAME + gcloud edge-cloud container vpn-connections describe - show details about a + VPN connection + +SYNOPSIS + gcloud edge-cloud container vpn-connections describe + (VPN_CONNECTION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details about a VPN connection. + +EXAMPLES + To show details about the VPN connection 'test-vpn-connection' at region + us-central1, run: + + $ gcloud edge-cloud container vpn-connections describe \ + test-vpn-connection --location=us-central1 + +POSITIONAL ARGUMENTS + Vpn connection resource - VPN connection you want to describe. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: + ◆ provide the argument vpn_connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + VPN_CONNECTION + ID of the vpn connection or fully qualified identifier for the vpn + connection. To set the vpn_connection attribute: + ▸ provide the argument vpn_connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The global location name. To set the location attribute: + ▸ provide the argument vpn_connection on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/location. + +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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container vpn-connections describe + diff --git a/gcloud/edge-cloud/container/vpn-connections/help b/gcloud/edge-cloud/container/vpn-connections/help new file mode 100644 index 000000000..8384b5eeb --- /dev/null +++ b/gcloud/edge-cloud/container/vpn-connections/help @@ -0,0 +1,38 @@ +NAME + gcloud edge-cloud container vpn-connections - manage Edge VPN connections + between an Edge Container cluster and a VPC network + +SYNOPSIS + gcloud edge-cloud container vpn-connections COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Edge VPN connections between an Edge Container cluster and a VPC + network. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a VPN connection between an Edge Container cluster and a VPC + network. + + delete + Delete a VPN connection between an Edge Container cluster and a VPC + network. + + describe + Show details about a VPN connection. + + list + List VPN connections. + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container vpn-connections + diff --git a/gcloud/edge-cloud/container/vpn-connections/list b/gcloud/edge-cloud/container/vpn-connections/list new file mode 100644 index 000000000..83a9b03de --- /dev/null +++ b/gcloud/edge-cloud/container/vpn-connections/list @@ -0,0 +1,83 @@ +NAME + gcloud edge-cloud container vpn-connections list - list VPN connections + +SYNOPSIS + gcloud edge-cloud container vpn-connections list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List VPN connections. + +EXAMPLES + To list the VPN connections at region us-central1, run: + + $ gcloud edge-cloud container vpn-connections list \ + --location=us-central + +FLAGS + Location resource - Parent location to list all contained VPN connections. + 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; + ◆ set the property edge_container/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; + ▸ set the property edge_container/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 edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container vpn-connections list + diff --git a/gcloud/edge-cloud/container/zones/describe b/gcloud/edge-cloud/container/zones/describe new file mode 100644 index 000000000..d80c33029 --- /dev/null +++ b/gcloud/edge-cloud/container/zones/describe @@ -0,0 +1,49 @@ +NAME + gcloud edge-cloud container zones describe - describe an Edge Container + zone + +SYNOPSIS + gcloud edge-cloud container zones describe ZONE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an Edge Container zone. + +EXAMPLES + To display the metadata for the zone us-central1-edge-operator-a, run: + + $ gcloud edge-cloud container zones describe \ + us-central1-edge-operator-a + +POSITIONAL ARGUMENTS + Zone resource - The zone name. 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; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + 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. + +API REFERENCE + This command uses the edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container zones describe + diff --git a/gcloud/edge-cloud/container/zones/help b/gcloud/edge-cloud/container/zones/help new file mode 100644 index 000000000..3c873cc49 --- /dev/null +++ b/gcloud/edge-cloud/container/zones/help @@ -0,0 +1,28 @@ +NAME + gcloud edge-cloud container zones - inspect Edge Container zones + +SYNOPSIS + gcloud edge-cloud container zones COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Inspect Edge Container zones. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe an Edge Container zone. + + list + List Edge Container zones. + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container zones + diff --git a/gcloud/edge-cloud/container/zones/list b/gcloud/edge-cloud/container/zones/list new file mode 100644 index 000000000..c89e94d11 --- /dev/null +++ b/gcloud/edge-cloud/container/zones/list @@ -0,0 +1,59 @@ +NAME + gcloud edge-cloud container zones list - list Edge Container zones + +SYNOPSIS + gcloud edge-cloud container zones list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all zones where Edge Container node pools can be created. + +EXAMPLES + To list all the zones where Edge Container node pools can be created, run: + + $ gcloud edge-cloud container zones list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container zones list + diff --git a/gcloud/edge-cloud/help b/gcloud/edge-cloud/help new file mode 100644 index 000000000..faf00b78c --- /dev/null +++ b/gcloud/edge-cloud/help @@ -0,0 +1,25 @@ +NAME + gcloud edge-cloud - manage edge-cloud resources + +SYNOPSIS + gcloud edge-cloud GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage edge-cloud resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + container + Manage Edge Container resources. + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud + diff --git a/gcloud/spanner/backups/add-iam-policy-binding b/gcloud/spanner/backups/add-iam-policy-binding index 516683a8b..d81d6c2b3 100644 --- a/gcloud/spanner/backups/add-iam-policy-binding +++ b/gcloud/spanner/backups/add-iam-policy-binding @@ -5,10 +5,12 @@ NAME SYNOPSIS gcloud spanner backups add-iam-policy-binding (BACKUP : --instance=INSTANCE) --member=PRINCIPAL --role=ROLE - [GCLOUD_WIDE_FLAG ...] + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Add an IAM policy binding to a Cloud Spanner backup. + Add an IAM policy binding to a Cloud Spanner backup. One binding consists + of a member, a role, and an optional condition. EXAMPLES To add an IAM policy binding for the role of 'roles/spanner.backupAdmin' @@ -20,6 +22,18 @@ EXAMPLES --member='user:test-user@gmail.com' \ --role='roles/spanner.backupAdmin' + To add an IAM policy binding which expires at the end of the year 2018 for + the role of 'roles/spanner.backupAdmin' and the user 'test-user@gmail.com' + with backup 'example-backup' and instance 'example-instance', run: + + $ gcloud spanner backups add-iam-policy-binding example-backup \ + --instance='example-instance' \ + --member='user:test-user@gmail.com' \ + --role='roles/spanner.backupAdmin' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' + See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. @@ -73,6 +87,44 @@ REQUIRED FLAGS for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer. +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/spanner/backups/copy b/gcloud/spanner/backups/copy new file mode 100644 index 000000000..e4a36dc02 --- /dev/null +++ b/gcloud/spanner/backups/copy @@ -0,0 +1,168 @@ +NAME + gcloud spanner backups copy - copies a backup of a Cloud Spanner database + +SYNOPSIS + gcloud spanner backups copy + (--destination-backup=DESTINATION_BACKUP + : --destination-instance=DESTINATION_INSTANCE) + (--expiration-date=EXPIRATION_DATE + | --retention-period=RETENTION_PERIOD) + (--source-backup=SOURCE_BACKUP : --source-instance=SOURCE_INSTANCE) + [--async] + [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY + : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Copies a backup of a Cloud Spanner database. + +EXAMPLES + To copy a backup within the same project, run: + + $ gcloud spanner backups copy --source-instance=SOURCE_INSTANCE_ID \ + --source-backup=SOURCE_BACKUP_ID \ + --destination-instance=DESTINATION_INSTANCE_ID \ + --destination-backup=DESTINATION_BACKUP_ID \ + --expiration-date=2020-03-29T10:49:41Z + + To copy a backup to a different project, run: + + $ gcloud spanner backups copy \ + --source-backup=projects/SOURCE_PROJECT_ID/instances/\ + SOURCE_INSTANCE_ID/backups/SOURCE_BACKUP_ID \ + --destination-backup=projects/DESTINATION_PROJECT_ID/instances/\ + DESTINATION_INSTANCE_ID/backups/DESTINATION_BACKUP_ID \ + --expiration-date=2020-03-29T10:49:41Z + +REQUIRED FLAGS + Backup resource - TEXT 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 --destination-backup 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. + + --destination-backup=DESTINATION_BACKUP + ID of the backup or fully qualified identifier for the backup. To set + the backup attribute: + ▸ provide the argument --destination-backup on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --destination-instance=DESTINATION_INSTANCE + The Cloud Spanner instance for the backup. To set the instance + attribute: + ▸ provide the argument --destination-backup on the command line + with a fully specified name; + ▸ provide the argument --destination-instance on the command line; + ▸ set the property spanner/instance. + + Exactly one of these must be specified: + + --expiration-date=EXPIRATION_DATE + Expiration time of the backup, must be at least 6 hours and at most + 366 days from the time when the source backup is created. See $ + gcloud topic datetimes for information on date/time formats. + + --retention-period=RETENTION_PERIOD + Retention period of the backup relative from now, must be at least 6 + hours and at most 366 days from the time when the source backup is + created. See $ gcloud topic datetimes for information on duration + formats. + + Backup resource - TEXT 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 --source-backup 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. + + --source-backup=SOURCE_BACKUP + ID of the backup or fully qualified identifier for the backup. To set + the backup attribute: + ▸ provide the argument --source-backup on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --source-instance=SOURCE_INSTANCE + The Cloud Spanner instance for the backup. To set the instance + attribute: + ▸ provide the argument --source-backup on the command line with a + fully specified name; + ▸ provide the argument --source-instance on the command line; + ▸ set the property spanner/instance. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --encryption-type=ENCRYPTION_TYPE + The encryption type of the copied backup. ENCRYPTION_TYPE must be one + of: + + customer-managed-encryption + Use the provided Cloud KMS key for encryption. If this option is + selected, kms-key must be set. + google-default-encryption + Use Google default encryption. + use-config-default-or-backup-encryption + Use the default encryption configuration if one exists. otherwise + use the same encryption configuration as the source backup. + + Key resource - Cloud KMS key to be used to copy the Cloud Spanner backup. + The arguments in this group can be used to specify the attributes of this + resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. To set the + kms-key attribute: + ▸ provide the argument --kms-key on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. To set the kms-keyring attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-keyring on the command line. + + --kms-location=KMS_LOCATION + Cloud location for the key. To set the kms-location attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. To set the kms-project attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-project on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha spanner backups copy + + $ gcloud beta spanner backups copy + diff --git a/gcloud/spanner/backups/help b/gcloud/spanner/backups/help index 7b29a7dfd..8f852bae8 100644 --- a/gcloud/spanner/backups/help +++ b/gcloud/spanner/backups/help @@ -18,6 +18,9 @@ COMMANDS add-iam-policy-binding Add IAM policy binding to a Cloud Spanner backup. + copy + Copies a backup of a Cloud Spanner database. + create Creates a backup of a Cloud Spanner database. diff --git a/gcloud/spanner/backups/remove-iam-policy-binding b/gcloud/spanner/backups/remove-iam-policy-binding index 4bf2f1764..85cfe46f5 100644 --- a/gcloud/spanner/backups/remove-iam-policy-binding +++ b/gcloud/spanner/backups/remove-iam-policy-binding @@ -5,10 +5,12 @@ NAME SYNOPSIS gcloud spanner backups remove-iam-policy-binding (BACKUP : --instance=INSTANCE) --member=PRINCIPAL --role=ROLE - [GCLOUD_WIDE_FLAG ...] + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Remove an IAM policy binding of a Cloud Spanner backup. + Remove an IAM policy binding of a Cloud Spanner backup. One binding + consists of a member, a role, and an optional condition. EXAMPLES To remove an IAM policy binding for the role of 'roles/spanner.backupAdmin' @@ -20,6 +22,19 @@ EXAMPLES --member='user:test-user@gmail.com' \ --role='roles/spanner.backupAdmin' + To remove an IAM policy binding which expires at the end of the year 2018 + for the role of 'roles/spanner.backupAdmin' and the user + 'test-user@gmail.com' with backup 'example-backup' and instance + 'example-instance', run: + + $ gcloud spanner backups remove-iam-policy-binding example-backup \ + --instance='example-instance' \ + --member='user:test-user@gmail.com' \ + --role='roles/spanner.backupAdmin' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' + See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. @@ -75,6 +90,48 @@ REQUIRED FLAGS --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, diff --git a/gcloud/spanner/databases/add-iam-policy-binding b/gcloud/spanner/databases/add-iam-policy-binding index cf04eb281..45957ac08 100644 --- a/gcloud/spanner/databases/add-iam-policy-binding +++ b/gcloud/spanner/databases/add-iam-policy-binding @@ -5,10 +5,12 @@ NAME SYNOPSIS gcloud spanner databases add-iam-policy-binding (DATABASE : --instance=INSTANCE) --member=PRINCIPAL --role=ROLE - [GCLOUD_WIDE_FLAG ...] + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Add an IAM policy binding to a Cloud Spanner database. + Add an IAM policy binding to a Cloud Spanner database. One binding consists + of a member, a role, and an optional condition. EXAMPLES To add an IAM policy binding for the role of 'roles/editor' for the user @@ -19,6 +21,18 @@ EXAMPLES --instance='my-instance' --member='user:test-user@gmail.com' \ --role='roles/editor' + To add an IAM policy binding which expires at the end of the year 2018 for + the role of 'roles/spanner.databaseAdmin' and the user + 'test-user@gmail.com' with database 'my-database' and instance + 'my-instance', run: + + $ gcloud spanner databases add-iam-policy-binding my-database \ + --instance='my-instance' --member='user:test-user@gmail.com' \ + --role='roles/spanner.databaseAdmin' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' + See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. @@ -73,6 +87,44 @@ REQUIRED FLAGS for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer. +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/spanner/databases/remove-iam-policy-binding b/gcloud/spanner/databases/remove-iam-policy-binding index e5d830eea..bb0a938de 100644 --- a/gcloud/spanner/databases/remove-iam-policy-binding +++ b/gcloud/spanner/databases/remove-iam-policy-binding @@ -5,13 +5,14 @@ NAME SYNOPSIS gcloud spanner databases remove-iam-policy-binding (DATABASE : --instance=INSTANCE) --member=PRINCIPAL --role=ROLE - [GCLOUD_WIDE_FLAG ...] + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Remove an IAM policy binding of a Cloud Spanner database. EXAMPLES - To Remove an IAM policy binding for the role of 'roles/editor' for the user + To remove an IAM policy binding for the role of 'roles/editor' for the user 'test-user@gmail.com' with database 'my-database' and instance 'my-instance', run: @@ -19,6 +20,18 @@ EXAMPLES --instance='my-instance' --member='user:test-user@gmail.com' \ --role='roles/editor' + To remove an IAM policy binding which expires at the end of the year 2018 + for the role of 'roles/spanner.databaseAdmin' and the user + 'test-user@gmail.com' with database 'my-database' and instance + 'my-instance', run: + + $ gcloud spanner databases remove-iam-policy-binding my-database \ + --instance='my-instance' --member='user:test-user@gmail.com' \ + --role='roles/spanner.databaseAdmin' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' + See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. @@ -74,6 +87,48 @@ REQUIRED FLAGS --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, diff --git a/gcloud/spanner/instances/add-iam-policy-binding b/gcloud/spanner/instances/add-iam-policy-binding index 8b3a116c6..47c534a41 100644 --- a/gcloud/spanner/instances/add-iam-policy-binding +++ b/gcloud/spanner/instances/add-iam-policy-binding @@ -4,10 +4,13 @@ NAME SYNOPSIS gcloud spanner instances add-iam-policy-binding [INSTANCE] - --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Add an IAM policy binding to a Cloud Spanner instance. + Add an IAM policy binding to a Cloud Spanner instance. One binding consists + of a member, a role, and an optional condition. EXAMPLES To add an IAM policy binding for the role of 'roles/editor' for the user @@ -16,6 +19,17 @@ EXAMPLES $ gcloud spanner instances add-iam-policy-binding my-instance \ --member='user:test-user@gmail.com' --role='roles/editor' + To add an IAM policy binding which expires at the end of the year 2018 for + the role of 'roles/spanner.admin' and the user 'test-user@gmail.com' with + instance 'my-instance', run: + + $ gcloud spanner instances add-iam-policy-binding my-instance \ + --member='user:test-user@gmail.com' \ + --role='roles/spanner.admin' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' + See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. @@ -57,6 +71,44 @@ REQUIRED FLAGS for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer. +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/spanner/instances/remove-iam-policy-binding b/gcloud/spanner/instances/remove-iam-policy-binding index fd40f7557..b00d0a759 100644 --- a/gcloud/spanner/instances/remove-iam-policy-binding +++ b/gcloud/spanner/instances/remove-iam-policy-binding @@ -4,18 +4,32 @@ NAME SYNOPSIS gcloud spanner instances remove-iam-policy-binding [INSTANCE] - --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Remove an IAM policy binding of a Cloud Spanner instance. + Remove an IAM policy binding of a Cloud Spanner instance. One binding + consists of a member, a role, and an optional condition. EXAMPLES - To Remove an IAM policy binding for the role of 'roles/editor' for the user + To remove an IAM policy binding for the role of 'roles/editor' for the user 'test-user@gmail.com' with instance 'my-instance', run: $ gcloud spanner instances remove-iam-policy-binding my-instance \ --member='user:test-user@gmail.com' --role='roles/editor' + To remove an IAM policy binding which expires at the end of the year 2018 + for the role of 'roles/spanner.admin' and the user 'test-user@gmail.com' + with instance 'my-instance', run: + + $ gcloud spanner instances remove-iam-policy-binding my-instance \ + --member='user:test-user@gmail.com' \ + --role='roles/spanner.admin' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' + See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. @@ -58,6 +72,48 @@ REQUIRED FLAGS --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, diff --git a/gcloud/sql/export/sql b/gcloud/sql/export/sql index d30e477f2..3755768d1 100644 --- a/gcloud/sql/export/sql +++ b/gcloud/sql/export/sql @@ -12,6 +12,11 @@ DESCRIPTION Exports data from a Cloud SQL instance to a Google Cloud Storage bucket as a SQL dump file. + NOTE: Certain roles and permissions are required to export data to Google + Cloud Storage. For more information on exporting data from Google Cloud SQL + see Export from Cloud SQL to a SQL dump file + (https://cloud.google.com/sql/docs/mysql/import-export/import-export-sql#gcloud). + POSITIONAL ARGUMENTS INSTANCE Cloud SQL instance ID. diff --git a/gcloud/sql/import/sql b/gcloud/sql/import/sql index 76b31a130..e4823c3f2 100644 --- a/gcloud/sql/import/sql +++ b/gcloud/sql/import/sql @@ -10,6 +10,11 @@ DESCRIPTION gcloud sql import sql imports data into a Cloud SQL instance from a SQL dump file in Google Cloud Storage. + NOTE: Certain roles and permissions are required to import data into Google + Cloud SQL. For more information on importing data into Google Cloud SQL see + Import a SQL dump file + (https://cloud.google.com/sql/docs/mysql/import-export/import-export-sql#gcloud_1). + For detailed help on importing data into Cloud SQL, refer to this guide: https://cloud.google.com/sql/docs/mysql/import-export/importing