diff --git a/gcloud/_version b/gcloud/_version index 3899073a9..ea03190b5 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 418.0.0 -alpha 2023.02.13 -beta 2023.02.13 +Google Cloud SDK 419.0.0 +alpha 2023.02.17 +beta 2023.02.17 bq 2.0.85 bundled-python3-unix 3.9.16 -core 2023.02.13 +core 2023.02.17 gcloud-crc32c 1.0.0 gsutil 5.20 diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index fe479ab31..1a36816a0 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -40,7 +40,7 @@ SYNOPSIS [--secure-tags=SECURE_TAG,[SECURE_TAG,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--source-instance-template=SOURCE_INSTANCE_TEMPLATE] - [--subnet=SUBNET] [--tags=TAG,[TAG,...]] + [--stack-type=STACK_TYPE] [--subnet=SUBNET] [--tags=TAG,[TAG,...]] [--target-distribution-shape=SHAPE] [--termination-time=TERMINATION_TIME] [--threads-per-core=THREADS_PER_CORE] @@ -717,6 +717,15 @@ OPTIONAL FLAGS The name of the instance template that the instance will be created from. Users can override fields by specifying other flags. + --stack-type=STACK_TYPE + Specifies whether IPv6 is enabled on the default network interface. If + not specified, IPV4_ONLY will be used. STACK_TYPE must be one of: + + IPV4_IPV6 + The network interface can have both IPv4 and IPv6 addresses + IPV4_ONLY + The network interface will be assigned IPv4 addresses + --subnet=SUBNET Specifies the subnet that the VM instances are a part of. If --network is also specified, subnet must be a subnetwork of the network specified diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index 32e387e0c..1fed003c1 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -40,7 +40,7 @@ SYNOPSIS [--secure-tags=SECURE_TAG,[SECURE_TAG,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--source-instance-template=SOURCE_INSTANCE_TEMPLATE] - [--subnet=SUBNET] [--tags=TAG,[TAG,...]] + [--stack-type=STACK_TYPE] [--subnet=SUBNET] [--tags=TAG,[TAG,...]] [--target-distribution-shape=SHAPE] [--termination-time=TERMINATION_TIME] [--threads-per-core=THREADS_PER_CORE] @@ -690,6 +690,15 @@ OPTIONAL FLAGS The name of the instance template that the instance will be created from. Users can override fields by specifying other flags. + --stack-type=STACK_TYPE + Specifies whether IPv6 is enabled on the default network interface. If + not specified, IPV4_ONLY will be used. STACK_TYPE must be one of: + + IPV4_IPV6 + The network interface can have both IPv4 and IPv6 addresses + IPV4_ONLY + The network interface will be assigned IPv4 addresses + --subnet=SUBNET Specifies the subnet that the VM instances are a part of. If --network is also specified, subnet must be a subnetwork of the network specified diff --git a/gcloud/alpha/container/bare-metal/clusters/create b/gcloud/alpha/container/bare-metal/clusters/create index 0fd4aaf75..32650c6d7 100644 --- a/gcloud/alpha/container/bare-metal/clusters/create +++ b/gcloud/alpha/container/bare-metal/clusters/create @@ -10,7 +10,10 @@ SYNOPSIS (--control-plane-load-balancer-port=CONTROL_PLANE_LOAD_BALANCER_PORT (--control-plane-vip=CONTROL_PLANE_VIP --ingress-vip=INGRESS_VIP) (--enable-manual-lb - | [--metal-lb-address-pools-from-file=METAL_LB_ADDRESS_POOLS_FROM_FILE : --metal-lb-load-balancer-node-configs=[labels=LABELS], + | [--metal-lb-address-pools=[addresses=ADDRESSES], + [avoid-buggy-ips=AVOID-BUGGY-IPS], + [manual-assign=MANUAL-ASSIGN],[pool=POOL] + : --metal-lb-load-balancer-node-configs=[labels=LABELS], [node-ip=NODE-IP] --metal-lb-load-balancer-node-labels=[KEY=VALUE,...] --metal-lb-load-balancer-node-taints=[KEY=VALUE:EFFECT,...]])) @@ -142,37 +145,12 @@ REQUIRED FLAGS MetalLB Configuration - --metal-lb-address-pools-from-file=METAL_LB_ADDRESS_POOLS_FROM_FILE - Path of the YAML/JSON file that contains the MetalLB address - pools. + MetalLB address pools configuration. - Examples: + Exactly one of these must be specified: - addressPools: - - pool: pool-1 - addresses: - - 10.200.0.14/32 - - 10.200.0.15/32 - avoidBuggyIPs: True - manualAssign: True - - pool: pool-2 - addresses: - - 10.200.0.16/32 - avoidBuggyIPs: False - manualAssign: False - - List of supported fields in addressPools - - KEY VALUE NOTE - pool string required, mutable - addresses one or more IP ranges required, mutable - avoidBuggyIPs bool optional, mutable, - defaults to False - manualAssign bool optional, mutable, - defaults to False - - This flag argument must be specified if any of the other - arguments in this group are specified. + --metal-lb-address-pools=[addresses=ADDRESSES],[avoid-buggy-ips=AVOID-BUGGY-IPS],[manual-assign=MANUAL-ASSIGN],[pool=POOL] + MetalLB address pools configuration. Anthos on bare metal node pool configuration for MetalLB load balancer nodes. diff --git a/gcloud/alpha/container/bare-metal/clusters/update b/gcloud/alpha/container/bare-metal/clusters/update index 4ee6ed442..2da1a701e 100644 --- a/gcloud/alpha/container/bare-metal/clusters/update +++ b/gcloud/alpha/container/bare-metal/clusters/update @@ -13,7 +13,9 @@ SYNOPSIS --control-plane-node-configs=[labels=LABELS],[node-ip=NODE-IP] --control-plane-node-labels=[KEY=VALUE,...] --control-plane-node-taints=[KEY=VALUE:EFFECT,...]] - [--metal-lb-address-pools-from-file=METAL_LB_ADDRESS_POOLS_FROM_FILE + [--metal-lb-address-pools=[addresses=ADDRESSES], + [avoid-buggy-ips=AVOID-BUGGY-IPS], + [manual-assign=MANUAL-ASSIGN],[pool=POOL] --metal-lb-load-balancer-node-configs=[labels=LABELS], [node-ip=NODE-IP] --metal-lb-load-balancer-node-labels=[KEY=VALUE,...] @@ -131,34 +133,12 @@ FLAGS MetalLB Configuration - --metal-lb-address-pools-from-file=METAL_LB_ADDRESS_POOLS_FROM_FILE - Path of the YAML/JSON file that contains the MetalLB address - pools. + MetalLB address pools configuration. - Examples: + At most one of these can be specified: - addressPools: - - pool: pool-1 - addresses: - - 10.200.0.14/32 - - 10.200.0.15/32 - avoidBuggyIPs: True - manualAssign: True - - pool: pool-2 - addresses: - - 10.200.0.16/32 - avoidBuggyIPs: False - manualAssign: False - - List of supported fields in addressPools - - KEY VALUE NOTE - pool string required, mutable - addresses one or more IP ranges required, mutable - avoidBuggyIPs bool optional, mutable, - defaults to False - manualAssign bool optional, mutable, - defaults to False + --metal-lb-address-pools=[addresses=ADDRESSES],[avoid-buggy-ips=AVOID-BUGGY-IPS],[manual-assign=MANUAL-ASSIGN],[pool=POOL] + MetalLB address pools configuration. Anthos on bare metal node pool configuration for MetalLB load balancer nodes. diff --git a/gcloud/alpha/container/bare-metal/node-pools/create b/gcloud/alpha/container/bare-metal/node-pools/create index d44f6532d..6054b8398 100644 --- a/gcloud/alpha/container/bare-metal/node-pools/create +++ b/gcloud/alpha/container/bare-metal/node-pools/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha container bare-metal node-pools create (NODE_POOL : --cluster=CLUSTER --location=LOCATION) - (--node-configs-from-file=NODE_CONFIGS_FROM_FILE + (--node-configs=[labels=LABELS],[node-ip=NODE-IP] : --node-labels=[KEY=VALUE,...] --node-taints=[KEY=VALUE:EFFECT,...]) [--annotations=[KEY=VALUE,...]] [--async] [--display-name=DISPLAY_NAME] [--validate-only] [GCLOUD_WIDE_FLAG ...] @@ -59,29 +59,12 @@ REQUIRED FLAGS This must be specified. - --node-configs-from-file=NODE_CONFIGS_FROM_FILE - Path of the YAML/JSON file that contains the node configs. + Populate Bare Metal Node Pool node config. - Examples: + Exactly one of these must be specified: - nodeConfigs: - - nodeIP: 10.200.0.10 - labels: - node1: label1 - node2: label2 - - nodeIP: 10.200.0.11 - labels: - node3: label3 - node4: label4 - - List of supported fields in nodeConfigs - - KEY VALUE NOTE - nodeIP string required, mutable - labels one or more key-val pairs optional, mutable - - This flag argument must be specified if any of the other arguments in - this group are specified. + --node-configs=[labels=LABELS],[node-ip=NODE-IP] + Bare Metal Node Pool node configuration. --node-labels=[KEY=VALUE,...] Labels assigned to nodes of a node pool. diff --git a/gcloud/alpha/container/bare-metal/node-pools/update b/gcloud/alpha/container/bare-metal/node-pools/update index 4aff51de7..df3f1cafc 100644 --- a/gcloud/alpha/container/bare-metal/node-pools/update +++ b/gcloud/alpha/container/bare-metal/node-pools/update @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha container bare-metal node-pools update (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--allow-missing] [--async] [--display-name=DISPLAY_NAME] [--validate-only] - [--node-configs-from-file=NODE_CONFIGS_FROM_FILE + [--node-configs=[labels=LABELS],[node-ip=NODE-IP] --node-labels=[KEY=VALUE,...] --node-taints=[KEY=VALUE:EFFECT,...]] [GCLOUD_WIDE_FLAG ...] @@ -73,26 +73,12 @@ FLAGS Anthos on bare metal node pool configuration. - --node-configs-from-file=NODE_CONFIGS_FROM_FILE - Path of the YAML/JSON file that contains the node configs. + Populate Bare Metal Node Pool node config. - Examples: + At most one of these can be specified: - nodeConfigs: - - nodeIP: 10.200.0.10 - labels: - node1: label1 - node2: label2 - - nodeIP: 10.200.0.11 - labels: - node3: label3 - node4: label4 - - List of supported fields in nodeConfigs - - KEY VALUE NOTE - nodeIP string required, mutable - labels one or more key-val pairs optional, mutable + --node-configs=[labels=LABELS],[node-ip=NODE-IP] + Bare Metal Node Pool node configuration. --node-labels=[KEY=VALUE,...] Labels assigned to nodes of a node pool. diff --git a/gcloud/alpha/container/vmware/clusters/update b/gcloud/alpha/container/vmware/clusters/update index 5e64512e3..cf2199a99 100644 --- a/gcloud/alpha/container/vmware/clusters/update +++ b/gcloud/alpha/container/vmware/clusters/update @@ -11,6 +11,8 @@ SYNOPSIS [manual-assign=MANUAL-ASSIGN],[pool=POOL]] [--static-ip-config-ip-blocks=[gateway=GATEWAY], [ips=IPS],[netmask=NETMASK]] [--version=VERSION] + [--add-annotations=[KEY1=VALUE1,KEY2=VALUE2,...] + | --remove-annotations=[KEY1,KEY2,...]] [--cpus=CPUS --memory=MEMORY --disable-auto-resize | --enable-auto-resize] [--disable-aag-config | --enable-aag-config] [--disable-auto-repair | --enable-auto-repair] @@ -115,6 +117,15 @@ FLAGS --version=VERSION Anthos Cluster on VMware version for the user cluster resource + At most one of these can be specified: + + --add-annotations=[KEY1=VALUE1,KEY2=VALUE2,...] + Add the given key-value pairs to the current annotations, or update + its value if the key already exists. + + --remove-annotations=[KEY1,KEY2,...] + Remove annotations of the given keys. + Control plane node configurations --cpus=CPUS diff --git a/gcloud/alpha/firebase/test/android/help b/gcloud/alpha/firebase/test/android/help index 755b570aa..293a4bbd9 100644 --- a/gcloud/alpha/firebase/test/android/help +++ b/gcloud/alpha/firebase/test/android/help @@ -64,6 +64,9 @@ GROUPS COMMANDS COMMAND is one of the following: + list-device-capacities + (ALPHA) List capacity information for Android models & versions. + run (ALPHA) Invoke a test in Firebase Test Lab for Android and view test results. diff --git a/gcloud/alpha/firebase/test/android/list-device-capacities b/gcloud/alpha/firebase/test/android/list-device-capacities new file mode 100644 index 000000000..1554dfe59 --- /dev/null +++ b/gcloud/alpha/firebase/test/android/list-device-capacities @@ -0,0 +1,79 @@ +NAME + gcloud alpha firebase test android list-device-capacities - list capacity + information for Android models & versions + +SYNOPSIS + gcloud alpha firebase test android list-device-capacities + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List device capacity information (high/medium/low/none) for all + Android models & versions which are available for testing and have capacity + information published. + + Device capacity is the number of online devices in Firebase Test Lab. For + physical devices, the number is the average of online devices in the last + 30 days. It's important to note that device capacity does not directly + reflect any real-time data, like the length of the test queue, or the + available/busy state of the devices based on current test traffic. + +EXAMPLES + To list all published capacity information for Android devices, run: + + $ gcloud alpha firebase test android list-device-capacities + + To list capacity only for the model named 'redfin', run: + + $ gcloud alpha firebase test android list-device-capacities \ + --filter=redfin + + To list capacities only for models that support API version 30, run: + + $ gcloud alpha firebase test android list-device-capacities \ + --filter=30 + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud firebase test android list-device-capacities + + $ gcloud beta firebase test android list-device-capacities + diff --git a/gcloud/alpha/firebase/test/android/run b/gcloud/alpha/firebase/test/android/run index 8a6587eac..d0ef92383 100644 --- a/gcloud/alpha/firebase/test/android/run +++ b/gcloud/alpha/firebase/test/android/run @@ -244,6 +244,13 @@ FLAGS --client-details=buildNumber=1234,pullRequest=https://example.com/link/to/pull-request + To help you identify and locate your test matrix in the Firebase + console, use the matrixLabel key. + + Example: + + --client-details=matrixLabel="Example matrix label" + --directories-to-pull=[DIR_TO_PULL,...] A list of paths that will be copied from the device's storage to the designated results bucket after the test is complete. These must be diff --git a/gcloud/alpha/firebase/test/ios/help b/gcloud/alpha/firebase/test/ios/help index 44f3ad475..5f1375d8b 100644 --- a/gcloud/alpha/firebase/test/ios/help +++ b/gcloud/alpha/firebase/test/ios/help @@ -51,6 +51,9 @@ GROUPS COMMANDS COMMAND is one of the following: + list-device-capacities + (ALPHA) List capacity information for iOS models & versions. + run (ALPHA) Invoke a test in Firebase Test Lab for iOS and view test results. diff --git a/gcloud/alpha/firebase/test/ios/list-device-capacities b/gcloud/alpha/firebase/test/ios/list-device-capacities new file mode 100644 index 000000000..19fcb2717 --- /dev/null +++ b/gcloud/alpha/firebase/test/ios/list-device-capacities @@ -0,0 +1,77 @@ +NAME + gcloud alpha firebase test ios list-device-capacities - list capacity + information for iOS models & versions + +SYNOPSIS + gcloud alpha firebase test ios list-device-capacities [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List device capacity information (high/medium/low/none) for all iOS + models & versions which are available for testing and have capacity + information published. + + Device capacity is the number of online devices in Firebase Test Lab. For + physical devices, the number is the average of online devices in the last + 30 days. It's important to note that device capacity does not directly + reflect any real-time data, like the length of the test queue, or the + available/busy state of the devices based on current test traffic. + +EXAMPLES + To list all published capacity information for iOS devices, run: + + $ gcloud alpha firebase test ios list-device-capacities + + To list capacities for only iPad devices, run: + + $ gcloud alpha firebase test ios list-device-capacities --filter=ipad + + To list capacities for only iOS version 14.2 devices, run: + + $ gcloud alpha firebase test ios list-device-capacities --filter=14.2 + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud firebase test ios list-device-capacities + + $ gcloud beta firebase test ios list-device-capacities + diff --git a/gcloud/alpha/firebase/test/ios/run b/gcloud/alpha/firebase/test/ios/run index be1d865ec..d873fe39e 100644 --- a/gcloud/alpha/firebase/test/ios/run +++ b/gcloud/alpha/firebase/test/ios/run @@ -41,6 +41,12 @@ DESCRIPTION arg-files for more information about argument files. EXAMPLES + To help you identify and locate your test matrix in the Firebase console, + run: + + $ gcloud alpha firebase test ios run --test=XCTEST_ZIP \ + --client-details=matrixLabel="Example matrix label" + To invoke an XCTest lasting up to five minutes against the default device environment, run: @@ -183,6 +189,13 @@ FLAGS --client-details=buildNumber=1234,pullRequest=https://example.com/link/to/pull-request + To help you identify and locate your test matrix in the Firebase + console, use the matrixLabel key. + + Example: + + --client-details=matrixLabel="Example matrix label" + --directories-to-pull=[DIR_TO_PULL,...] A list of paths that will be copied from the device's storage to the designated results bucket after the test is complete. These must be diff --git a/gcloud/alpha/functions/deploy b/gcloud/alpha/functions/deploy index 57e8f90f3..1903b59d2 100644 --- a/gcloud/alpha/functions/deploy +++ b/gcloud/alpha/functions/deploy @@ -342,8 +342,11 @@ FLAGS DOCKER_REPOSITORY must be an Artifact Registry Docker repository present in the same project and location as the Cloud Function. - The repository name should match the pattern - projects/${PROJECT}/locations/${LOCATION}/repositories/${REPOSITORY} + The repository name should match one of these patterns: + + ▸ projects/${PROJECT}/locations/${LOCATION}/repositories/${REPOSITORY}, + ▸ {LOCATION}-docker.pkg.dev/{PROJECT}/{REPOSITORY}. + where ${PROJECT} is the project, ${LOCATION} is the location of the repository and ${REPOSITORY} is a valid repository ID. diff --git a/gcloud/alpha/netapp/volumes/revert b/gcloud/alpha/netapp/volumes/revert index ccdfcfce6..2d3420503 100644 --- a/gcloud/alpha/netapp/volumes/revert +++ b/gcloud/alpha/netapp/volumes/revert @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha netapp volumes revert (VOLUME : --location=LOCATION) - --snapshot=SNAPSHOT [GCLOUD_WIDE_FLAG ...] + --snapshot=SNAPSHOT [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Revert a Cloud NetApp Volume back to a specified Snapshot. @@ -60,6 +60,11 @@ REQUIRED FLAGS set the snapshot attribute: ▸ provide the argument --snapshot on the command line. +OPTIONAL 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, diff --git a/gcloud/alpha/recaptcha/keys/create b/gcloud/alpha/recaptcha/keys/create index 8991a5e1e..a5cbd3d90 100644 --- a/gcloud/alpha/recaptcha/keys/create +++ b/gcloud/alpha/recaptcha/keys/create @@ -164,12 +164,14 @@ OPTIONAL FLAGS this group are specified. --waf-service=WAF_SERVICE - The WAF service provider to use. WAF_SERVICE must be (currently only - one value is supported): + The WAF service provider to use. WAF_SERVICE must be one of: ca Cloud Armor + fastly + Fastly + This flag argument must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/alpha/run/jobs/executions/logs/help b/gcloud/alpha/run/jobs/executions/logs/help index a5fa3a36e..39cbd880a 100644 --- a/gcloud/alpha/run/jobs/executions/logs/help +++ b/gcloud/alpha/run/jobs/executions/logs/help @@ -41,5 +41,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run jobs executions logs diff --git a/gcloud/alpha/run/jobs/executions/logs/read b/gcloud/alpha/run/jobs/executions/logs/read index c4d341a3a..312764804 100644 --- a/gcloud/alpha/run/jobs/executions/logs/read +++ b/gcloud/alpha/run/jobs/executions/logs/read @@ -80,5 +80,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run jobs executions logs read diff --git a/gcloud/alpha/run/jobs/executions/logs/tail b/gcloud/alpha/run/jobs/executions/logs/tail index fd99cad59..51d877ff2 100644 --- a/gcloud/alpha/run/jobs/executions/logs/tail +++ b/gcloud/alpha/run/jobs/executions/logs/tail @@ -50,5 +50,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run jobs executions logs tail diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index c8684b91e..4f8ced191 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -12,7 +12,8 @@ SYNOPSIS [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--[no-]use-http2] [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost - --[no-]cpu-throttling --execution-environment=EXECUTION_ENVIRONMENT + --[no-]cpu-throttling --description=DESCRIPTION + --execution-environment=EXECUTION_ENVIRONMENT --revision-suffix=REVISION_SUFFIX --[no-]session-affinity --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -225,6 +226,9 @@ FLAGS serving requests. Use --cpu-throttling to enable and --no-cpu-throttling to disable. + --description=DESCRIPTION + Provides an optional, human-readable description of the service. + --execution-environment=EXECUTION_ENVIRONMENT Selects the execution environment where the application will run. EXECUTION_ENVIRONMENT must be one of: diff --git a/gcloud/alpha/storage/hash b/gcloud/alpha/storage/hash new file mode 100644 index 000000000..812fdbb4d --- /dev/null +++ b/gcloud/alpha/storage/hash @@ -0,0 +1,78 @@ +NAME + gcloud alpha storage hash - calculates hashes on local or cloud files + +SYNOPSIS + gcloud alpha storage hash URLS [URLS ...] + [--additional-headers=HEADER=VALUE] [--hex] + [--skip-crc32c | --skip-md5] [--decryption-keys=[DECRYPTION_KEY,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Calculates hashes on local or cloud files that can be used to + compare with "gcloud storage ls -L" output. If a specific hash option is + not provided, this command calculates all gcloud storage-supported hashes + for the file. + + Note that gcloud storage automatically performs hash validation when + uploading or downloading files, so this command is only needed if you want + to write a script that separately checks the hash for some reason. + + If you calculate a CRC32C hash for the file without a precompiled + google-crc32c installation, hashing will be very slow. + +EXAMPLES + To get the MD5 and CRC32C hash digest of a cloud object in Base64 format: + + $ gcloud alpha storage hash gs://bucket/object + + To get just the MD5 hash digest of a local object in hex format: + + $ gcloud alpha storage hash /dir/object.txt --skip-md5 --hex + +POSITIONAL ARGUMENTS + URLS [URLS ...] + Local or cloud URLs of objects to hash. + +FLAGS + --additional-headers=HEADER=VALUE + Includes arbitrary headers in storage API calls. Accepts a comma + separated list of key=value pairs, e.g. header1=value1,header2=value2. + Overrides the default storage/additional_headers property value for + this command invocation. + + --hex + Output hash digests in hex format. By default, digests are displayed in + base64. + + At most one of these can be specified: + + --skip-crc32c + Skip CRC32C hash calculation. Useful if command is running slow. + + --skip-md5 + Skip MD5 hash calculation. Useful if command is running slow. + +ENCRYPTION FLAGS + --decryption-keys=[DECRYPTION_KEY,...] + A comma-separated list of customer-supplied encryption keys (RFC 4648 + section 4 base64-encoded AES256 strings) that will be used to decrypt + Google Cloud Storage objects. Data encrypted with a customer-managed + encryption key (CMEK) is decrypted automatically, so CMEKs do not need + to be listed here. + +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 storage hash + diff --git a/gcloud/alpha/storage/help b/gcloud/alpha/storage/help index b68af75f2..0501fe8e3 100644 --- a/gcloud/alpha/storage/help +++ b/gcloud/alpha/storage/help @@ -35,6 +35,9 @@ COMMANDS cp (ALPHA) Upload, download, and copy Cloud Storage objects. + hash + (ALPHA) Calculates hashes on local or cloud files. + ls (ALPHA) List Cloud Storage buckets and objects. diff --git a/gcloud/beta/datastream/connection-profiles/discover b/gcloud/beta/datastream/connection-profiles/discover index 0d8a9f537..99c88e2af 100644 --- a/gcloud/beta/datastream/connection-profiles/discover +++ b/gcloud/beta/datastream/connection-profiles/discover @@ -6,6 +6,7 @@ SYNOPSIS gcloud beta datastream connection-profiles discover --location=LOCATION (--connection-profile-name=CONNECTION_PROFILE_NAME | --connection-profile-object-file=CONNECTION_PROFILE_OBJECT_FILE) + [--full-hierarchy | --hierarchy-depth=HIERARCHY_DEPTH] [--mysql-rdbms-file=MYSQL_RDBMS_FILE | --oracle-rdbms-file=ORACLE_RDBMS_FILE | --postgresql-rdbms-file=POSTGRESQL_RDBMS_FILE] @@ -23,7 +24,7 @@ EXAMPLES $ gcloud beta datastream connection-profiles discover \ CONNECTION_PROFILE --location=us-central1 \ - --connection-profile-name=some-cp --recursive + --connection-profile-name=some-cp --recursive=true To discover a non-existing connection profile: @@ -74,6 +75,16 @@ REQUIRED FLAGS file content will be read from stdin. OPTIONAL FLAGS + At most one of these can be specified: + + --full-hierarchy + Whether to retrieve the full hierarchy of data objects (TRUE) or only + the current level (FALSE). + + --hierarchy-depth=HIERARCHY_DEPTH + The number of hierarchy levels below the current level to be + retrieved. + At most one of these can be specified: --mysql-rdbms-file=MYSQL_RDBMS_FILE @@ -94,12 +105,17 @@ OPTIONAL FLAGS At most one of these can be specified: --recursive - Whether to retrieve the full hierarchy of data objects (TRUE) or only - the current level (FALSE). + (DEPRECATED) Whether to retrieve the full hierarchy of data objects + (TRUE) or only the current level (FALSE). + + The --recursive option is deprecated; use --full-hierarchy instead. --recursive-depth=RECURSIVE_DEPTH - The number of hierarchy levels below the current level to be - retrieved. + (DEPRECATED) The number of hierarchy levels below the current level + to be retrieved. + + The --recursive-depth option is deprecated; use --hierarchy-depth + instead. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/firebase/test/android/help b/gcloud/beta/firebase/test/android/help index 9a513c049..e8fcbfd2b 100644 --- a/gcloud/beta/firebase/test/android/help +++ b/gcloud/beta/firebase/test/android/help @@ -64,6 +64,9 @@ GROUPS COMMANDS COMMAND is one of the following: + list-device-capacities + (BETA) List capacity information for Android models & versions. + run (BETA) Invoke a test in Firebase Test Lab for Android and view test results. diff --git a/gcloud/beta/firebase/test/android/list-device-capacities b/gcloud/beta/firebase/test/android/list-device-capacities new file mode 100644 index 000000000..4fca87ff6 --- /dev/null +++ b/gcloud/beta/firebase/test/android/list-device-capacities @@ -0,0 +1,77 @@ +NAME + gcloud beta firebase test android list-device-capacities - list capacity + information for Android models & versions + +SYNOPSIS + gcloud beta firebase test android list-device-capacities + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List device capacity information (high/medium/low/none) for all + Android models & versions which are available for testing and have capacity + information published. + + Device capacity is the number of online devices in Firebase Test Lab. For + physical devices, the number is the average of online devices in the last + 30 days. It's important to note that device capacity does not directly + reflect any real-time data, like the length of the test queue, or the + available/busy state of the devices based on current test traffic. + +EXAMPLES + To list all published capacity information for Android devices, run: + + $ gcloud beta firebase test android list-device-capacities + + To list capacity only for the model named 'redfin', run: + + $ gcloud beta firebase test android list-device-capacities \ + --filter=redfin + + To list capacities only for models that support API version 30, run: + + $ gcloud beta firebase test android list-device-capacities \ + --filter=30 + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud firebase test android list-device-capacities + + $ gcloud alpha firebase test android list-device-capacities + diff --git a/gcloud/beta/firebase/test/android/run b/gcloud/beta/firebase/test/android/run index 6627c4b11..56086fdb8 100644 --- a/gcloud/beta/firebase/test/android/run +++ b/gcloud/beta/firebase/test/android/run @@ -244,6 +244,13 @@ FLAGS --client-details=buildNumber=1234,pullRequest=https://example.com/link/to/pull-request + To help you identify and locate your test matrix in the Firebase + console, use the matrixLabel key. + + Example: + + --client-details=matrixLabel="Example matrix label" + --directories-to-pull=[DIR_TO_PULL,...] A list of paths that will be copied from the device's storage to the designated results bucket after the test is complete. These must be diff --git a/gcloud/beta/firebase/test/ios/help b/gcloud/beta/firebase/test/ios/help index 59d28296a..53531f7cf 100644 --- a/gcloud/beta/firebase/test/ios/help +++ b/gcloud/beta/firebase/test/ios/help @@ -50,6 +50,9 @@ GROUPS COMMANDS COMMAND is one of the following: + list-device-capacities + (BETA) List capacity information for iOS models & versions. + run (BETA) Invoke a test in Firebase Test Lab for iOS and view test results. diff --git a/gcloud/beta/firebase/test/ios/list-device-capacities b/gcloud/beta/firebase/test/ios/list-device-capacities new file mode 100644 index 000000000..fd0ded682 --- /dev/null +++ b/gcloud/beta/firebase/test/ios/list-device-capacities @@ -0,0 +1,75 @@ +NAME + gcloud beta firebase test ios list-device-capacities - list capacity + information for iOS models & versions + +SYNOPSIS + gcloud beta firebase test ios list-device-capacities [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List device capacity information (high/medium/low/none) for all iOS + models & versions which are available for testing and have capacity + information published. + + Device capacity is the number of online devices in Firebase Test Lab. For + physical devices, the number is the average of online devices in the last + 30 days. It's important to note that device capacity does not directly + reflect any real-time data, like the length of the test queue, or the + available/busy state of the devices based on current test traffic. + +EXAMPLES + To list all published capacity information for iOS devices, run: + + $ gcloud beta firebase test ios list-device-capacities + + To list capacities for only iPad devices, run: + + $ gcloud beta firebase test ios list-device-capacities --filter=ipad + + To list capacities for only iOS version 14.2 devices, run: + + $ gcloud beta firebase test ios list-device-capacities --filter=14.2 + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud firebase test ios list-device-capacities + + $ gcloud alpha firebase test ios list-device-capacities + diff --git a/gcloud/beta/firebase/test/ios/run b/gcloud/beta/firebase/test/ios/run index e2a1ba35d..5cc26a5f9 100644 --- a/gcloud/beta/firebase/test/ios/run +++ b/gcloud/beta/firebase/test/ios/run @@ -41,6 +41,12 @@ DESCRIPTION for more information about argument files. EXAMPLES + To help you identify and locate your test matrix in the Firebase console, + run: + + $ gcloud beta firebase test ios run --test=XCTEST_ZIP \ + --client-details=matrixLabel="Example matrix label" + To invoke an XCTest lasting up to five minutes against the default device environment, run: @@ -183,6 +189,13 @@ FLAGS --client-details=buildNumber=1234,pullRequest=https://example.com/link/to/pull-request + To help you identify and locate your test matrix in the Firebase + console, use the matrixLabel key. + + Example: + + --client-details=matrixLabel="Example matrix label" + --directories-to-pull=[DIR_TO_PULL,...] A list of paths that will be copied from the device's storage to the designated results bucket after the test is complete. These must be diff --git a/gcloud/beta/functions/deploy b/gcloud/beta/functions/deploy index 9f749a4dc..93609c6a5 100644 --- a/gcloud/beta/functions/deploy +++ b/gcloud/beta/functions/deploy @@ -338,8 +338,11 @@ FLAGS DOCKER_REPOSITORY must be an Artifact Registry Docker repository present in the same project and location as the Cloud Function. - The repository name should match the pattern - projects/${PROJECT}/locations/${LOCATION}/repositories/${REPOSITORY} + The repository name should match one of these patterns: + + ▸ projects/${PROJECT}/locations/${LOCATION}/repositories/${REPOSITORY}, + ▸ {LOCATION}-docker.pkg.dev/{PROJECT}/{REPOSITORY}. + where ${PROJECT} is the project, ${LOCATION} is the location of the repository and ${REPOSITORY} is a valid repository ID. diff --git a/gcloud/beta/run/jobs/executions/help b/gcloud/beta/run/jobs/executions/help index 924dbbc8e..88497648c 100644 --- a/gcloud/beta/run/jobs/executions/help +++ b/gcloud/beta/run/jobs/executions/help @@ -28,6 +28,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + logs + (BETA) Read logs for Cloud Run jobs executions. + tasks (BETA) View and manage your Cloud Run jobs tasks. diff --git a/gcloud/beta/run/jobs/executions/logs/help b/gcloud/beta/run/jobs/executions/logs/help new file mode 100644 index 000000000..293f829c4 --- /dev/null +++ b/gcloud/beta/run/jobs/executions/logs/help @@ -0,0 +1,45 @@ +NAME + gcloud beta run jobs executions logs - read logs for Cloud Run jobs + executions + +SYNOPSIS + gcloud beta run jobs executions logs COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Read logs for Cloud Run jobs executions. + +EXAMPLES + To tail logs for a job execution, run: + + $ gcloud beta run jobs executions logs tail my-job-execution + + To read logs for a job execution, run: + + $ gcloud beta run jobs executions logs read my-job-execution + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + read + (BETA) Read logs for Cloud Run job executions. + + tail + (BETA) Tail logs for Cloud Run job executions. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run jobs executions logs + diff --git a/gcloud/beta/run/jobs/executions/logs/read b/gcloud/beta/run/jobs/executions/logs/read new file mode 100644 index 000000000..eea6d0a18 --- /dev/null +++ b/gcloud/beta/run/jobs/executions/logs/read @@ -0,0 +1,84 @@ +NAME + gcloud beta run jobs executions logs read - read logs for Cloud Run job + executions + +SYNOPSIS + gcloud beta run jobs executions logs read EXECUTION + [--freshness=FRESHNESS; default="1d"] [--log-filter=LOG_FILTER] + [--order=ORDER; default="desc"] [--region=REGION] [--limit=LIMIT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta run jobs executions logs read reads log entries. Log + entries matching --log-filter are returned according to the specified + --order. If the log entries come from multiple logs, then entries from + different logs might be intermingled in the results. + +EXAMPLES + To read log entries from for a Cloud Run job execution, run: + + $ gcloud beta run jobs executions logs read my-job-execution + + To read log entries with severity ERROR or higher, run: + + $ gcloud beta run jobs executions logs read my-job-execution \ + --log-filter="severity>=ERROR" + + To read log entries written in a specific time window, run: + + $ gcloud beta run jobs executions logs read my-job-execution \ + --log-filter='timestamp<="2015-05-31T23:59:59Z" AND + timestamp>="2015-05-31T00:00:00Z"' + + To read up to 10 log entries in your job payloads that include the word + SearchText and format the output in JSON format, run: + + $ gcloud beta run jobs executions logs read my-job-execution \ + --log-filter="textPayload:SearchText" --limit=10 --format=json + + Detailed information about filters can be found at: + https://cloud.google.com/logging/docs/view/advanced_filters + +POSITIONAL ARGUMENTS + EXECUTION + Name for a Cloud Run job execution. + +FLAGS + --freshness=FRESHNESS; default="1d" + Return entries that are not older than this value. Works only with DESC + ordering and filters without a timestamp. See $ gcloud topic datetimes + for information on duration formats. + + --log-filter=LOG_FILTER + Filter expression that specifies the log entries to return. Detailed + information about filters can be found at: + https://cloud.google.com/logging/docs/view/logging-query-language + + --order=ORDER; default="desc" + Ordering of returned log entries based on timestamp field. ORDER must + be one of: desc, asc. + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +LIST COMMAND FLAGS + --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. + +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 run jobs executions logs read + diff --git a/gcloud/beta/run/jobs/executions/logs/tail b/gcloud/beta/run/jobs/executions/logs/tail new file mode 100644 index 000000000..7735dbdd9 --- /dev/null +++ b/gcloud/beta/run/jobs/executions/logs/tail @@ -0,0 +1,54 @@ +NAME + gcloud beta run jobs executions logs tail - tail logs for Cloud Run job + executions + +SYNOPSIS + gcloud beta run jobs executions logs tail EXECUTION + [--log-filter=LOG_FILTER] [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta run jobs executions logs tail tails log-entries for a + particular Cloud Run job exeuction in real time. The log entries are + formatted for consumption in a terminal. + +EXAMPLES + To tail log entries for a Cloud Run job exeuction, run: + + $ gcloud beta run jobs executions logs tail my-job-execution + + To tail log entries with severity ERROR or higher, run: + + $ gcloud beta run jobs executions logs tail my-job-execution \ + --log-filter="severity>=ERROR" + + Detailed information about filters can be found at: + https://cloud.google.com/logging/docs/view/advanced_filters + +POSITIONAL ARGUMENTS + EXECUTION + Name for a Cloud Run job. + +FLAGS + --log-filter=LOG_FILTER + Filter expression that specifies the log entries to return. Detailed + information about filters can be found at: + https://cloud.google.com/logging/docs/view/logging-query-language + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run jobs executions logs tail + diff --git a/gcloud/compute/backend-services/create b/gcloud/compute/backend-services/create index 647844953..6d2f58068 100644 --- a/gcloud/compute/backend-services/create +++ b/gcloud/compute/backend-services/create @@ -25,6 +25,8 @@ SYNOPSIS oauth2-client-secret=OAUTH2-CLIENT-SECRET]] [--idle-timeout-sec=IDLE_TIMEOUT_SEC] [--load-balancing-scheme=LOAD_BALANCING_SCHEME; default="EXTERNAL"] + [--logging-optional=LOGGING_OPTIONAL] + [--logging-optional-fields=[LOGGING_OPTIONAL_FIELDS,...]] [--logging-sample-rate=LOGGING_SAMPLE_RATE] [--max-ttl=MAX_TTL] [--[no-]negative-caching] [--negative-caching-policy=[[CODE=TTL],...]] [--network=NETWORK] [--port-name=PORT_NAME] [--protocol=PROTOCOL] @@ -325,6 +327,22 @@ FLAGS LOAD_BALANCING_SCHEME must be one of: INTERNAL, EXTERNAL, INTERNAL_SELF_MANAGED, EXTERNAL_MANAGED, INTERNAL_MANAGED. + --logging-optional=LOGGING_OPTIONAL + This field can only be specified if logging is enabled for the backend + service. Configures whether all, none, or a subset of optional fields + should be added to the reported logs. Default is EXCLUDE_ALL_OPTIONAL. + This field can only be specified for Internal TCP/UDP Load Balancing + and External Network Load Balancing. LOGGING_OPTIONAL must be one of: + EXCLUDE_ALL_OPTIONAL, INCLUDE_ALL_OPTIONAL, CUSTOM. + + --logging-optional-fields=[LOGGING_OPTIONAL_FIELDS,...] + This field can only be specified if logging is enabled for the backend + service and "--logging-optional" was set to CUSTOM. Contains a + comma-separated list of optional fields you want to include in the + logs. For example: serverInstance, serverGkeDetails.cluster, + serverGkeDetails.pod.podNamespace. This can only be specified for + Internal TCP/UDP Load Balancing and External Network Load Balancing. + --logging-sample-rate=LOGGING_SAMPLE_RATE This field can only be specified if logging is enabled for the backend service. The value of the field must be a float in the range [0, 1]. diff --git a/gcloud/compute/backend-services/update b/gcloud/compute/backend-services/update index d6724617d..348cdbcce 100644 --- a/gcloud/compute/backend-services/update +++ b/gcloud/compute/backend-services/update @@ -20,6 +20,8 @@ SYNOPSIS [--iap=disabled|enabled,[oauth2-client-id=OAUTH2-CLIENT-ID, oauth2-client-secret=OAUTH2-CLIENT-SECRET]] [--idle-timeout-sec=IDLE_TIMEOUT_SEC] + [--logging-optional=LOGGING_OPTIONAL] + [--logging-optional-fields=[LOGGING_OPTIONAL_FIELDS,...]] [--logging-sample-rate=LOGGING_SAMPLE_RATE] [--port-name=PORT_NAME] [--protocol=PROTOCOL] [--[no-]request-coalescing] [--security-policy=SECURITY_POLICY] @@ -235,6 +237,22 @@ FLAGS service-based network load balancers and internal TCP/UDP load balancers as part of a connection tracking policy. + --logging-optional=LOGGING_OPTIONAL + This field can only be specified if logging is enabled for the backend + service. Configures whether all, none, or a subset of optional fields + should be added to the reported logs. Default is EXCLUDE_ALL_OPTIONAL. + This field can only be specified for Internal TCP/UDP Load Balancing + and External Network Load Balancing. LOGGING_OPTIONAL must be one of: + EXCLUDE_ALL_OPTIONAL, INCLUDE_ALL_OPTIONAL, CUSTOM. + + --logging-optional-fields=[LOGGING_OPTIONAL_FIELDS,...] + This field can only be specified if logging is enabled for the backend + service and "--logging-optional" was set to CUSTOM. Contains a + comma-separated list of optional fields you want to include in the + logs. For example: serverInstance, serverGkeDetails.cluster, + serverGkeDetails.pod.podNamespace. This can only be specified for + Internal TCP/UDP Load Balancing and External Network Load Balancing. + --logging-sample-rate=LOGGING_SAMPLE_RATE This field can only be specified if logging is enabled for the backend service. The value of the field must be a float in the range [0, 1]. diff --git a/gcloud/datastream/connection-profiles/discover b/gcloud/datastream/connection-profiles/discover index 53d1e109d..0f28abfcf 100644 --- a/gcloud/datastream/connection-profiles/discover +++ b/gcloud/datastream/connection-profiles/discover @@ -6,6 +6,7 @@ SYNOPSIS gcloud datastream connection-profiles discover --location=LOCATION (--connection-profile-name=CONNECTION_PROFILE_NAME | --connection-profile-object-file=CONNECTION_PROFILE_OBJECT_FILE) + [--full-hierarchy | --hierarchy-depth=HIERARCHY_DEPTH] [--mysql-rdbms-file=MYSQL_RDBMS_FILE | --oracle-rdbms-file=ORACLE_RDBMS_FILE | --postgresql-rdbms-file=POSTGRESQL_RDBMS_FILE] @@ -20,7 +21,7 @@ EXAMPLES $ gcloud datastream connection-profiles discover \ CONNECTION_PROFILE --location=us-central1 \ - --connection-profile-name=some-cp --recursive + --connection-profile-name=some-cp --recursive=true To discover a non-existing connection profile: @@ -71,6 +72,16 @@ REQUIRED FLAGS file content will be read from stdin. OPTIONAL FLAGS + At most one of these can be specified: + + --full-hierarchy + Whether to retrieve the full hierarchy of data objects (TRUE) or only + the current level (FALSE). + + --hierarchy-depth=HIERARCHY_DEPTH + The number of hierarchy levels below the current level to be + retrieved. + At most one of these can be specified: --mysql-rdbms-file=MYSQL_RDBMS_FILE @@ -91,12 +102,17 @@ OPTIONAL FLAGS At most one of these can be specified: --recursive - Whether to retrieve the full hierarchy of data objects (TRUE) or only - the current level (FALSE). + (DEPRECATED) Whether to retrieve the full hierarchy of data objects + (TRUE) or only the current level (FALSE). + + The --recursive option is deprecated; use --full-hierarchy instead. --recursive-depth=RECURSIVE_DEPTH - The number of hierarchy levels below the current level to be - retrieved. + (DEPRECATED) The number of hierarchy levels below the current level + to be retrieved. + + The --recursive-depth option is deprecated; use --hierarchy-depth + instead. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/firebase/test/android/list-device-capacities b/gcloud/firebase/test/android/list-device-capacities index 7d706d226..f73b74aeb 100644 --- a/gcloud/firebase/test/android/list-device-capacities +++ b/gcloud/firebase/test/android/list-device-capacities @@ -64,3 +64,11 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha firebase test android list-device-capacities + + $ gcloud beta firebase test android list-device-capacities + diff --git a/gcloud/firebase/test/android/run b/gcloud/firebase/test/android/run index 1c9636ed0..103f642fb 100644 --- a/gcloud/firebase/test/android/run +++ b/gcloud/firebase/test/android/run @@ -7,6 +7,7 @@ SYNOPSIS [--device=DIMENSION=VALUE,[...]] [--test=TEST] [--timeout=TIMEOUT] [--type=TYPE] [--additional-apks=APK,[APK,...]] [--app-package=APP_PACKAGE] [--async] [--auto-google-login] + [--client-details=[KEY=VALUE,...]] [--directories-to-pull=[DIR_TO_PULL,...]] [--environment-variables=[KEY=VALUE,...]] [--network-profile=PROFILE_ID] [--num-flaky-test-attempts=int] @@ -227,6 +228,25 @@ FLAGS account before beginning the test. Enabled by default, use --no-auto-google-login to disable. + --client-details=[KEY=VALUE,...] + Comma-separated, KEY=VALUE map of additional details to attach to the + test matrix. Arbitrary KEY=VALUE pairs may be attached to a test matrix + to provide additional context about the tests being run. When consuming + the test results, such as in Cloud Functions or a CI system, these + details can add additional context such as a link to the corresponding + pull request. + + Example: + + --client-details=buildNumber=1234,pullRequest=https://example.com/link/to/pull-request + + To help you identify and locate your test matrix in the Firebase + console, use the matrixLabel key. + + Example: + + --client-details=matrixLabel="Example matrix label" + --directories-to-pull=[DIR_TO_PULL,...] A list of paths that will be copied from the device's storage to the designated results bucket after the test is complete. These must be diff --git a/gcloud/firebase/test/ios/list-device-capacities b/gcloud/firebase/test/ios/list-device-capacities index c8df580fa..dc3a58545 100644 --- a/gcloud/firebase/test/ios/list-device-capacities +++ b/gcloud/firebase/test/ios/list-device-capacities @@ -64,3 +64,11 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha firebase test ios list-device-capacities + + $ gcloud beta firebase test ios list-device-capacities + diff --git a/gcloud/firebase/test/ios/run b/gcloud/firebase/test/ios/run index 5aac8778e..85415e796 100644 --- a/gcloud/firebase/test/ios/run +++ b/gcloud/firebase/test/ios/run @@ -6,7 +6,8 @@ SYNOPSIS gcloud firebase test ios run [ARGSPEC] [--device=DIMENSION=VALUE,[...]] [--test=XCTEST_ZIP] [--timeout=TIMEOUT] [--type=TYPE] [--xcode-version=XCODE_VERSION] [--xctestrun-file=XCTESTRUN_FILE] - [--app=APP] [--async] [--num-flaky-test-attempts=int] [--record-video] + [--app=APP] [--async] [--client-details=[KEY=VALUE,...]] + [--num-flaky-test-attempts=int] [--record-video] [--results-bucket=RESULTS_BUCKET] [--results-dir=RESULTS_DIR] [--results-history-name=RESULTS_HISTORY_NAME] [--test-special-entitlements] [--filter=EXPRESSION] [--limit=LIMIT] @@ -30,6 +31,12 @@ DESCRIPTION for more information about argument files. EXAMPLES + To help you identify and locate your test matrix in the Firebase console, + run: + + $ gcloud firebase test ios run --test=XCTEST_ZIP \ + --client-details=matrixLabel="Example matrix label" + To invoke an XCTest lasting up to five minutes against the default device environment, run: @@ -136,6 +143,25 @@ FLAGS --async Invoke a test asynchronously without waiting for test results. + --client-details=[KEY=VALUE,...] + Comma-separated, KEY=VALUE map of additional details to attach to the + test matrix. Arbitrary KEY=VALUE pairs may be attached to a test matrix + to provide additional context about the tests being run. When consuming + the test results, such as in Cloud Functions or a CI system, these + details can add additional context such as a link to the corresponding + pull request. + + Example: + + --client-details=buildNumber=1234,pullRequest=https://example.com/link/to/pull-request + + To help you identify and locate your test matrix in the Firebase + console, use the matrixLabel key. + + Example: + + --client-details=matrixLabel="Example matrix label" + --num-flaky-test-attempts=int Specifies the number of times a test execution should be reattempted if one or more of its test cases fail for any reason. An execution that diff --git a/gcloud/functions/deploy b/gcloud/functions/deploy index 836e70170..c7b9d8dfa 100644 --- a/gcloud/functions/deploy +++ b/gcloud/functions/deploy @@ -347,8 +347,11 @@ FLAGS DOCKER_REPOSITORY must be an Artifact Registry Docker repository present in the same project and location as the Cloud Function. - The repository name should match the pattern - projects/${PROJECT}/locations/${LOCATION}/repositories/${REPOSITORY} + The repository name should match one of these patterns: + + ▸ projects/${PROJECT}/locations/${LOCATION}/repositories/${REPOSITORY}, + ▸ {LOCATION}-docker.pkg.dev/{PROJECT}/{REPOSITORY}. + where ${PROJECT} is the project, ${LOCATION} is the location of the repository and ${REPOSITORY} is a valid repository ID. diff --git a/gcloud/recaptcha/keys/create b/gcloud/recaptcha/keys/create index 8107e9af8..63b7eb68e 100644 --- a/gcloud/recaptcha/keys/create +++ b/gcloud/recaptcha/keys/create @@ -164,12 +164,14 @@ OPTIONAL FLAGS this group are specified. --waf-service=WAF_SERVICE - The WAF service provider to use. WAF_SERVICE must be (currently only - one value is supported): + The WAF service provider to use. WAF_SERVICE must be one of: ca Cloud Armor + fastly + Fastly + This flag argument must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/storage/hash b/gcloud/storage/hash new file mode 100644 index 000000000..5368d2a2a --- /dev/null +++ b/gcloud/storage/hash @@ -0,0 +1,73 @@ +NAME + gcloud storage hash - calculates hashes on local or cloud files + +SYNOPSIS + gcloud storage hash URLS [URLS ...] [--additional-headers=HEADER=VALUE] + [--hex] [--skip-crc32c | --skip-md5] + [--decryption-keys=[DECRYPTION_KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Calculates hashes on local or cloud files that can be used to compare with + "gcloud storage ls -L" output. If a specific hash option is not provided, + this command calculates all gcloud storage-supported hashes for the file. + + Note that gcloud storage automatically performs hash validation when + uploading or downloading files, so this command is only needed if you want + to write a script that separately checks the hash for some reason. + + If you calculate a CRC32C hash for the file without a precompiled + google-crc32c installation, hashing will be very slow. + +EXAMPLES + To get the MD5 and CRC32C hash digest of a cloud object in Base64 format: + + $ gcloud storage hash gs://bucket/object + + To get just the MD5 hash digest of a local object in hex format: + + $ gcloud storage hash /dir/object.txt --skip-md5 --hex + +POSITIONAL ARGUMENTS + URLS [URLS ...] + Local or cloud URLs of objects to hash. + +FLAGS + --additional-headers=HEADER=VALUE + Includes arbitrary headers in storage API calls. Accepts a comma + separated list of key=value pairs, e.g. header1=value1,header2=value2. + Overrides the default storage/additional_headers property value for + this command invocation. + + --hex + Output hash digests in hex format. By default, digests are displayed in + base64. + + At most one of these can be specified: + + --skip-crc32c + Skip CRC32C hash calculation. Useful if command is running slow. + + --skip-md5 + Skip MD5 hash calculation. Useful if command is running slow. + +ENCRYPTION FLAGS + --decryption-keys=[DECRYPTION_KEY,...] + A comma-separated list of customer-supplied encryption keys (RFC 4648 + section 4 base64-encoded AES256 strings) that will be used to decrypt + Google Cloud Storage objects. Data encrypted with a customer-managed + encryption key (CMEK) is decrypted automatically, so CMEKs do not need + to be listed here. + +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 storage hash + diff --git a/gcloud/storage/help b/gcloud/storage/help index 79568cced..8e311207d 100644 --- a/gcloud/storage/help +++ b/gcloud/storage/help @@ -35,6 +35,9 @@ COMMANDS cp Upload, download, and copy Cloud Storage objects. + hash + Calculates hashes on local or cloud files. + ls List Cloud Storage buckets and objects.