From 5b5ff68a0db6ca3874d0f8202d7ca59bc7dc08a2 Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 25 May 2022 08:41:12 +0000 Subject: [PATCH] gcloud: Wed May 25 08:41:12 UTC 2022 --- gcloud/_version | 8 +- gcloud/alpha/builds/cancel | 2 +- gcloud/alpha/builds/describe | 2 +- gcloud/alpha/builds/list | 2 +- gcloud/alpha/builds/log | 2 +- gcloud/alpha/builds/submit | 2 +- .../builds/triggers/create/gitlab-enterprise | 2 +- gcloud/alpha/builds/triggers/import | 2 +- gcloud/alpha/builds/triggers/list | 2 +- gcloud/alpha/composer/environments/create | 32 ++-- gcloud/alpha/composer/environments/update | 2 +- gcloud/alpha/compute/firewall-rules/migrate | 7 +- gcloud/alpha/compute/forwarding-rules/create | 31 +++- .../alpha/compute/forwarding-rules/set-target | 31 +++- .../managed/all-instances-config/delete | 39 +++-- .../managed/all-instances-config/help | 9 +- .../managed/all-instances-config/update | 36 +++-- gcloud/alpha/compute/instances/bulk/create | 20 +++ .../instances/ops-agents/policies/create | 1 + .../instances/ops-agents/policies/update | 1 + gcloud/alpha/compute/security-policies/create | 2 +- .../alpha/compute/target-tcp-proxies/create | 37 +++++ .../alpha/compute/target-tcp-proxies/delete | 28 +++- .../alpha/compute/target-tcp-proxies/describe | 28 +++- gcloud/alpha/compute/target-tcp-proxies/list | 46 +++++- gcloud/alpha/compute/tpus/tpu-vm/create | 8 +- gcloud/alpha/dataproc/jobs/submit/hadoop | 21 ++- gcloud/alpha/dataproc/jobs/submit/hive | 21 ++- gcloud/alpha/dataproc/jobs/submit/pig | 21 ++- gcloud/alpha/dataproc/jobs/submit/presto | 19 ++- gcloud/alpha/dataproc/jobs/submit/pyspark | 22 ++- gcloud/alpha/dataproc/jobs/submit/spark | 21 ++- gcloud/alpha/dataproc/jobs/submit/spark-r | 21 ++- gcloud/alpha/dataproc/jobs/submit/spark-sql | 21 ++- .../workflow-templates/add-job/hadoop | 19 ++- .../dataproc/workflow-templates/add-job/hive | 18 +++ .../dataproc/workflow-templates/add-job/pig | 18 +++ .../workflow-templates/add-job/presto | 19 ++- .../workflow-templates/add-job/pyspark | 23 ++- .../dataproc/workflow-templates/add-job/spark | 19 ++- .../workflow-templates/add-job/spark-r | 19 ++- .../workflow-templates/add-job/spark-sql | 19 ++- gcloud/alpha/functions/deploy | 23 ++- gcloud/alpha/logging/metrics/create | 7 +- gcloud/alpha/logging/metrics/update | 7 +- gcloud/alpha/monitoring/metrics-scopes/create | 4 +- gcloud/alpha/monitoring/metrics-scopes/delete | 4 +- .../alpha/monitoring/metrics-scopes/describe | 4 +- gcloud/alpha/monitoring/metrics-scopes/help | 4 +- gcloud/alpha/monitoring/metrics-scopes/list | 4 +- gcloud/alpha/pubsub/subscriptions/create | 28 ++++ gcloud/alpha/pubsub/subscriptions/update | 33 +++++ gcloud/alpha/run/services/logs/help | 3 + gcloud/alpha/run/services/logs/tail | 114 +++++++++++++++ gcloud/alpha/storage/cp | 63 ++++++-- gcloud/alpha/vmware/help | 4 + gcloud/alpha/vmware/network-peerings/create | 9 +- gcloud/alpha/vmware/network-policies/create | 138 ++++++++++++++++++ gcloud/alpha/vmware/network-policies/delete | 73 +++++++++ gcloud/alpha/vmware/network-policies/describe | 67 +++++++++ gcloud/alpha/vmware/network-policies/help | 40 +++++ gcloud/alpha/vmware/network-policies/list | 100 +++++++++++++ gcloud/alpha/vmware/network-policies/update | 93 ++++++++++++ gcloud/beta/builds/cancel | 2 +- gcloud/beta/builds/describe | 2 +- gcloud/beta/builds/list | 2 +- gcloud/beta/builds/log | 2 +- gcloud/beta/builds/submit | 2 +- gcloud/beta/builds/triggers/import | 2 +- gcloud/beta/builds/triggers/list | 2 +- gcloud/beta/composer/environments/create | 32 ++-- gcloud/beta/composer/environments/update | 2 +- gcloud/beta/compute/commitments/create | 2 +- gcloud/beta/compute/forwarding-rules/create | 31 +++- .../beta/compute/forwarding-rules/set-target | 31 +++- .../managed/all-instances-config/delete | 84 +++++++++++ .../managed/all-instances-config/help | 35 +++++ .../managed/all-instances-config/update | 86 +++++++++++ .../beta/compute/instance-groups/managed/help | 4 + gcloud/beta/compute/instances/bulk/create | 20 +++ .../instances/ops-agents/policies/create | 1 + .../instances/ops-agents/policies/update | 1 + gcloud/beta/compute/ssl-policies/create | 12 +- gcloud/beta/compute/ssl-policies/delete | 12 +- gcloud/beta/compute/ssl-policies/describe | 13 +- gcloud/beta/compute/ssl-policies/list | 46 +++++- .../ssl-policies/list-available-features | 6 +- gcloud/beta/compute/ssl-policies/update | 11 +- .../beta/compute/target-https-proxies/create | 10 ++ .../beta/compute/target-https-proxies/update | 13 +- gcloud/beta/compute/target-ssl-proxies/create | 10 ++ gcloud/beta/compute/target-ssl-proxies/update | 12 +- gcloud/beta/compute/target-tcp-proxies/create | 37 +++++ gcloud/beta/compute/target-tcp-proxies/delete | 28 +++- .../beta/compute/target-tcp-proxies/describe | 29 +++- gcloud/beta/compute/target-tcp-proxies/list | 46 +++++- gcloud/beta/dataproc/jobs/submit/hadoop | 21 ++- gcloud/beta/dataproc/jobs/submit/hive | 21 ++- gcloud/beta/dataproc/jobs/submit/pig | 21 ++- gcloud/beta/dataproc/jobs/submit/presto | 19 ++- gcloud/beta/dataproc/jobs/submit/pyspark | 22 ++- gcloud/beta/dataproc/jobs/submit/spark | 21 ++- gcloud/beta/dataproc/jobs/submit/spark-r | 21 ++- gcloud/beta/dataproc/jobs/submit/spark-sql | 21 ++- .../workflow-templates/add-job/hadoop | 19 ++- .../dataproc/workflow-templates/add-job/hive | 18 +++ .../dataproc/workflow-templates/add-job/pig | 18 +++ .../workflow-templates/add-job/presto | 19 ++- .../workflow-templates/add-job/pyspark | 23 ++- .../dataproc/workflow-templates/add-job/spark | 19 ++- .../workflow-templates/add-job/spark-r | 19 ++- .../workflow-templates/add-job/spark-sql | 19 ++- gcloud/beta/functions/deploy | 23 ++- gcloud/beta/monitoring/help | 3 + gcloud/beta/monitoring/metrics-scopes/create | 52 +++++++ gcloud/beta/monitoring/metrics-scopes/delete | 51 +++++++ .../beta/monitoring/metrics-scopes/describe | 60 ++++++++ gcloud/beta/monitoring/metrics-scopes/help | 40 +++++ gcloud/beta/monitoring/metrics-scopes/list | 73 +++++++++ gcloud/beta/pubsub/subscriptions/create | 28 ++++ gcloud/beta/pubsub/subscriptions/update | 33 +++++ gcloud/builds/cancel | 2 +- gcloud/builds/describe | 2 +- gcloud/builds/list | 2 +- gcloud/builds/log | 2 +- gcloud/builds/submit | 2 +- gcloud/composer/environments/create | 31 ++-- gcloud/compute/commitments/create | 2 +- gcloud/dataproc/jobs/submit/hadoop | 21 ++- gcloud/dataproc/jobs/submit/hive | 21 ++- gcloud/dataproc/jobs/submit/pig | 21 ++- gcloud/dataproc/jobs/submit/presto | 19 ++- gcloud/dataproc/jobs/submit/pyspark | 22 ++- gcloud/dataproc/jobs/submit/spark | 21 ++- gcloud/dataproc/jobs/submit/spark-r | 21 ++- gcloud/dataproc/jobs/submit/spark-sql | 21 ++- .../workflow-templates/add-job/hadoop | 19 ++- .../dataproc/workflow-templates/add-job/hive | 18 +++ .../dataproc/workflow-templates/add-job/pig | 18 +++ .../workflow-templates/add-job/presto | 19 ++- .../workflow-templates/add-job/pyspark | 23 ++- .../dataproc/workflow-templates/add-job/spark | 19 ++- .../workflow-templates/add-job/spark-r | 19 ++- .../workflow-templates/add-job/spark-sql | 19 ++- gcloud/eventarc/audit-logs-provider/help | 27 ++++ .../audit-logs-provider/method-names/help | 23 +++ .../audit-logs-provider/method-names/list | 63 ++++++++ .../audit-logs-provider/service-names/help | 23 +++ .../audit-logs-provider/service-names/list | 59 ++++++++ gcloud/eventarc/help | 4 + gcloud/network-connectivity/spokes/delete | 38 +++-- gcloud/network-connectivity/spokes/describe | 37 +++-- gcloud/pubsub/subscriptions/create | 28 ++++ gcloud/pubsub/subscriptions/update | 33 +++++ 154 files changed, 3252 insertions(+), 284 deletions(-) create mode 100644 gcloud/alpha/run/services/logs/tail create mode 100644 gcloud/alpha/vmware/network-policies/create create mode 100644 gcloud/alpha/vmware/network-policies/delete create mode 100644 gcloud/alpha/vmware/network-policies/describe create mode 100644 gcloud/alpha/vmware/network-policies/help create mode 100644 gcloud/alpha/vmware/network-policies/list create mode 100644 gcloud/alpha/vmware/network-policies/update create mode 100644 gcloud/beta/compute/instance-groups/managed/all-instances-config/delete create mode 100644 gcloud/beta/compute/instance-groups/managed/all-instances-config/help create mode 100644 gcloud/beta/compute/instance-groups/managed/all-instances-config/update create mode 100644 gcloud/beta/monitoring/metrics-scopes/create create mode 100644 gcloud/beta/monitoring/metrics-scopes/delete create mode 100644 gcloud/beta/monitoring/metrics-scopes/describe create mode 100644 gcloud/beta/monitoring/metrics-scopes/help create mode 100644 gcloud/beta/monitoring/metrics-scopes/list create mode 100644 gcloud/eventarc/audit-logs-provider/help create mode 100644 gcloud/eventarc/audit-logs-provider/method-names/help create mode 100644 gcloud/eventarc/audit-logs-provider/method-names/list create mode 100644 gcloud/eventarc/audit-logs-provider/service-names/help create mode 100644 gcloud/eventarc/audit-logs-provider/service-names/list diff --git a/gcloud/_version b/gcloud/_version index da3f0b613..de4405754 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,6 +1,6 @@ -Google Cloud SDK 386.0.0 -alpha 2022.05.13 -beta 2022.05.13 +Google Cloud SDK 387.0.0 +alpha 2022.05.20 +beta 2022.05.20 bq 2.0.74 -core 2022.05.13 +core 2022.05.20 gsutil 5.10 diff --git a/gcloud/alpha/builds/cancel b/gcloud/alpha/builds/cancel index 107cfbc12..6dfe80f41 100644 --- a/gcloud/alpha/builds/cancel +++ b/gcloud/alpha/builds/cancel @@ -25,7 +25,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/builds/describe b/gcloud/alpha/builds/describe index 29ec6842b..0f2c35399 100644 --- a/gcloud/alpha/builds/describe +++ b/gcloud/alpha/builds/describe @@ -21,7 +21,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/builds/list b/gcloud/alpha/builds/list index 6ac7b0bba..422266a7e 100644 --- a/gcloud/alpha/builds/list +++ b/gcloud/alpha/builds/list @@ -26,7 +26,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/builds/log b/gcloud/alpha/builds/log index b0e9f0747..dc693fd3e 100644 --- a/gcloud/alpha/builds/log +++ b/gcloud/alpha/builds/log @@ -27,7 +27,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. --stream If a build is ongoing, stream the logs to stdout until the build diff --git a/gcloud/alpha/builds/submit b/gcloud/alpha/builds/submit index 8ea9446f2..7abe99b20 100644 --- a/gcloud/alpha/builds/submit +++ b/gcloud/alpha/builds/submit @@ -95,7 +95,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. --substitutions=[KEY=VALUE,...] Parameters to be substituted in the build specification. diff --git a/gcloud/alpha/builds/triggers/create/gitlab-enterprise b/gcloud/alpha/builds/triggers/create/gitlab-enterprise index 91bedf000..7ecdf984f 100644 --- a/gcloud/alpha/builds/triggers/create/gitlab-enterprise +++ b/gcloud/alpha/builds/triggers/create/gitlab-enterprise @@ -68,7 +68,7 @@ REQUIRED FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global - service region is used. This field is restricted. + service region is used. This flag must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/alpha/builds/triggers/import b/gcloud/alpha/builds/triggers/import index 1029f48a5..176e60245 100644 --- a/gcloud/alpha/builds/triggers/import +++ b/gcloud/alpha/builds/triggers/import @@ -23,7 +23,7 @@ OPTIONAL FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/builds/triggers/list b/gcloud/alpha/builds/triggers/list index feff9ae07..55b92c8c6 100644 --- a/gcloud/alpha/builds/triggers/list +++ b/gcloud/alpha/builds/triggers/list @@ -19,7 +19,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/composer/environments/create b/gcloud/alpha/composer/environments/create index d3126cb24..102289d18 100644 --- a/gcloud/alpha/composer/environments/create +++ b/gcloud/alpha/composer/environments/create @@ -115,7 +115,7 @@ FLAGS When enabled the IP Masq Agent is deployed to the cluster with configuration to masquarade all traffic except between pods. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --env-variables=[NAME=VALUE,...] A comma-delimited list of environment variable NAME=VALUE pairs to @@ -216,7 +216,7 @@ FLAGS IPv4 CIDR range to use for the Cloud SQL network. This should have a size of the netmask not greater than 24. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. --composer-network-ipv4-cidr=COMPOSER_NETWORK_IPV4_CIDR @@ -224,7 +224,7 @@ FLAGS size of the netmask between 24 and 29. Can be specified for Composer 2.X or greater. Cannot be specified - unless '--enable-private-environment' is also specified. + unless --enable-private-environment is also specified. --connection-subnetwork=CONNECTION_SUBNETWORK Subnetwork from which an IP address for internal communications will @@ -233,7 +233,7 @@ FLAGS which the environment is connected. Can be specified for Composer 2.X or greater. Cannot be specified - unless '--enable-private-environment' is also specified. + unless --enable-private-environment is also specified. --enable-private-endpoint Environment cluster is managed using the private IP address of the @@ -243,7 +243,7 @@ FLAGS If not specified, the master API endpoint will be accessible by its public IP address. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. --enable-private-environment @@ -252,28 +252,28 @@ FLAGS If not specified, cluster nodes will be assigned public IP addresses. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --enable-privately-used-public-ips When enabled GKE pods and services may use public(non-RFC1918) IP ranges privately. The ranges are specified by '--cluster-ipv4-cidr' - and ' --services-ipv4-cidr' flags. + and --services-ipv4-cidr flags. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. --master-ipv4-cidr=MASTER_IPV4_CIDR IPv4 CIDR range to use for the cluster master network. This should have a size of the netmask between 23 and 28. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. --web-server-ipv4-cidr=WEB_SERVER_IPV4_CIDR IPv4 CIDR range to use for the Airflow web server network. This should have a size of the netmask between 24 and 29. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. IP Alias (VPC-native) @@ -282,14 +282,14 @@ FLAGS IP address range for the pods in this cluster in CIDR notation (e.g. 10.0.0.0/14). - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --cluster-secondary-range-name=CLUSTER_SECONDARY_RANGE_NAME Secondary range to be used as the source for pod IPs. Alias ranges will be allocated from this secondary range. NAME must be the name of an existing secondary range in the cluster subnetwork. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --enable-ip-alias Enable use of alias IPs @@ -302,7 +302,7 @@ FLAGS used to limit the size of IP range assigned to the node in VPC native cluster setup. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --services-ipv4-cidr=SERVICES_IPV4_CIDR IP range for the services IPs. @@ -314,13 +314,13 @@ FLAGS If unspecified, the services CIDR range will be chosen with a default mask size. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --services-secondary-range-name=SERVICES_SECONDARY_RANGE_NAME Secondary range to be used for services (e.g. ClusterIPs). NAME must be the name of an existing secondary range in the cluster subnetwork. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. Master Authorized Networks configuration @@ -333,7 +333,7 @@ FLAGS Comma separated Master Authorized Networks specified in CIDR notation. - Cannot be specified unless '--enable-master-authorized-networks' is + Cannot be specified unless --enable-master-authorized-networks is also specified. Key resource - The Cloud KMS (Key Management Service) cryptokey that will diff --git a/gcloud/alpha/composer/environments/update b/gcloud/alpha/composer/environments/update index bbeecdfda..552299aef 100644 --- a/gcloud/alpha/composer/environments/update +++ b/gcloud/alpha/composer/environments/update @@ -142,7 +142,7 @@ REQUIRED FLAGS Comma separated Master Authorized Networks specified in CIDR notation. - Cannot be specified unless '--enable-master-authorized-networks' is + Cannot be specified unless --enable-master-authorized-networks is also specified. Group of arguments for setting the maintenance window value. diff --git a/gcloud/alpha/compute/firewall-rules/migrate b/gcloud/alpha/compute/firewall-rules/migrate index 27c9acf64..23d2e9cf0 100644 --- a/gcloud/alpha/compute/firewall-rules/migrate +++ b/gcloud/alpha/compute/firewall-rules/migrate @@ -6,7 +6,8 @@ SYNOPSIS gcloud alpha compute firewall-rules migrate --source-network=SOURCE_NETWORK (--export-tag-mapping | --target-firewall-policy=TARGET_FIREWALL_POLICY) - [--tag-mapping-file=TAG_MAPPING_FILE] [GCLOUD_WIDE_FLAG ...] + [--disable-logging] [--tag-mapping-file=TAG_MAPPING_FILE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute firewall-rules migrate is used to create a new @@ -37,6 +38,10 @@ REQUIRED FLAGS result. OPTIONAL FLAGS + --disable-logging + If set, migration tool will not migrate logging config. This is a + workaround to use before Network Firewall Policies support logging. + --tag-mapping-file=TAG_MAPPING_FILE Path to a JSON file with legacy to secure tag mapping. diff --git a/gcloud/alpha/compute/forwarding-rules/create b/gcloud/alpha/compute/forwarding-rules/create index a3d26038a..7eb564b8c 100644 --- a/gcloud/alpha/compute/forwarding-rules/create +++ b/gcloud/alpha/compute/forwarding-rules/create @@ -35,6 +35,8 @@ SYNOPSIS | --target-http-proxy-region=TARGET_HTTP_PROXY_REGION] [--global-target-https-proxy | --target-https-proxy-region=TARGET_HTTPS_PROXY_REGION] + [--global-target-tcp-proxy + | --target-tcp-proxy-region=TARGET_TCP_PROXY_REGION] [--port-range=[PORT | START_PORT-END_PORT] | --ports=ALL | [PORT | START_PORT-END_PORT],[...]] [GCLOUD_WIDE_FLAG ...] @@ -221,8 +223,8 @@ OPTIONAL FLAGS INTERNAL Internal load balancing or forwarding, used with --backend-service. INTERNAL_MANAGED - Internal HTTP(S) Load Balancing, used with --target-http-proxy, - --target-https-proxy. + Internal load balancing, used with --target-tcp-proxy, + --target-http-proxy, --target-https-proxy. INTERNAL_SELF_MANAGED Traffic Director load balancing or forwarding, used with --target-http-proxy, --target-https-proxy, --target-grpc-proxy, @@ -448,6 +450,31 @@ OPTIONAL FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + At most one of these can be specified: + + --global-target-tcp-proxy + If set, the tcp proxy is global. + + --target-tcp-proxy-region=TARGET_TCP_PROXY_REGION + Region of the tcp proxy to operate on. If not specified, you might be + prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + At most one of these can be specified: --port-range=[PORT | START_PORT-END_PORT] diff --git a/gcloud/alpha/compute/forwarding-rules/set-target b/gcloud/alpha/compute/forwarding-rules/set-target index 66bf19456..0c5c4cf24 100644 --- a/gcloud/alpha/compute/forwarding-rules/set-target +++ b/gcloud/alpha/compute/forwarding-rules/set-target @@ -23,6 +23,8 @@ SYNOPSIS | --target-http-proxy-region=TARGET_HTTP_PROXY_REGION] [--global-target-https-proxy | --target-https-proxy-region=TARGET_HTTPS_PROXY_REGION] + [--global-target-tcp-proxy + | --target-tcp-proxy-region=TARGET_TCP_PROXY_REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -142,8 +144,8 @@ OPTIONAL FLAGS INTERNAL Internal load balancing or forwarding, used with --backend-service. INTERNAL_MANAGED - Internal HTTP(S) Load Balancing, used with --target-http-proxy, - --target-https-proxy. + Internal load balancing, used with --target-tcp-proxy, + --target-http-proxy, --target-https-proxy. INTERNAL_SELF_MANAGED Traffic Director load balancing or forwarding, used with --target-http-proxy, --target-https-proxy, --target-grpc-proxy, @@ -268,6 +270,31 @@ OPTIONAL FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + At most one of these can be specified: + + --global-target-tcp-proxy + If set, the tcp proxy is global. + + --target-tcp-proxy-region=TARGET_TCP_PROXY_REGION + Region of the tcp proxy to operate on. If not specified, you might be + prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/instance-groups/managed/all-instances-config/delete b/gcloud/alpha/compute/instance-groups/managed/all-instances-config/delete index 4b54265e6..5c6041424 100644 --- a/gcloud/alpha/compute/instance-groups/managed/all-instances-config/delete +++ b/gcloud/alpha/compute/instance-groups/managed/all-instances-config/delete @@ -1,6 +1,6 @@ NAME gcloud alpha compute instance-groups managed all-instances-config delete - - delete values defined in all-instances configuration of a managed + delete values defined in the all-instances configuration of a managed instance group SYNOPSIS @@ -10,8 +10,8 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha compute instance-groups managed all-instances-config - delete deletes one or more values defined in all-instances configuration of - a managed instance group. + delete deletes one or more values defined in the all-instances + configuration of a managed instance group. To apply a revised all-instances configuration to existing instances in the group, use one of the following methods: @@ -21,23 +21,33 @@ DESCRIPTION ▪ Use the rolling-action start-update command. ▪ Use the API to set the group's updatePolicy.type to PROACTIVE. +EXAMPLES + To delete the group's all-instances configuration in order to stop + overriding the group's instance template for a label with the key label-key + and metadata with the key metadata-key in group my-group, run: + + $ gcloud alpha compute instance-groups managed \ + all-instances-config delete my-group --metadata=metadata-key \ + --labels=label-key + POSITIONAL ARGUMENTS NAME - Name of the managed instance group to delete all-instances' config for. + Name of the managed instance group to delete the all instances + configuration for. FLAGS --labels=KEY,[KEY,...] - Remove labels keys from all-instances' config configuration. + Remove labels keys from the group's all instances configuration. --metadata=KEY,[KEY,...] - Remove metadata keys from all-instances' config configuration. + Remove metadata keys from the group's all instances configuration. At most one of these can be specified: --region=REGION - Region of the managed instance group to delete all-instances' config - for. If not specified, you might be prompted to select a region - (interactive mode only). + Region of the managed instance group to delete the all instances + configuration for. If not specified, you might be prompted to select + a region (interactive mode only). A list of regions can be fetched by running: @@ -47,9 +57,9 @@ FLAGS invocation. --zone=ZONE - Zone of the managed instance group to delete all-instances' config - for. If not specified, you might be prompted to select a zone - (interactive mode only). + Zone of the managed instance group to delete the all instances + configuration for. If not specified, you might be prompted to select + a zone (interactive mode only). A list of zones can be fetched by running: @@ -70,5 +80,8 @@ 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 compute instance-groups managed all-instances-config \ + delete diff --git a/gcloud/alpha/compute/instance-groups/managed/all-instances-config/help b/gcloud/alpha/compute/instance-groups/managed/all-instances-config/help index 70a56a1bb..361918e68 100644 --- a/gcloud/alpha/compute/instance-groups/managed/all-instances-config/help +++ b/gcloud/alpha/compute/instance-groups/managed/all-instances-config/help @@ -20,15 +20,18 @@ COMMANDS COMMAND is one of the following: delete - (ALPHA) Delete values defined in all-instances configuration of a + (ALPHA) Delete values defined in the all-instances configuration of a managed instance group. update - (ALPHA) Update all-instances configuration of a managed instance group. + (ALPHA) Update the all-instances configuration of a managed instance + group. NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute instance-groups managed all-instances-config diff --git a/gcloud/alpha/compute/instance-groups/managed/all-instances-config/update b/gcloud/alpha/compute/instance-groups/managed/all-instances-config/update index 54c90fb05..b522caf9c 100644 --- a/gcloud/alpha/compute/instance-groups/managed/all-instances-config/update +++ b/gcloud/alpha/compute/instance-groups/managed/all-instances-config/update @@ -1,6 +1,6 @@ NAME gcloud alpha compute instance-groups managed all-instances-config update - - update all-instances configuration of a managed instance group + update the all-instances configuration of a managed instance group SYNOPSIS gcloud alpha compute instance-groups managed all-instances-config update @@ -21,23 +21,34 @@ DESCRIPTION ▪ Use the rolling-action start-update command. ▪ Use the API to set the group's updatePolicy.type to PROACTIVE. +EXAMPLES + To update an all-instances configuration in order to override the group's + instance template for a label with the key label-key and metadata with the + key metadata-key in group my-group, run: + + $ gcloud alpha compute instance-groups managed \ + all-instances-config update my-group \ + --metadata=metadata-key=metadata-override-value \ + --labels=qlabel-key=label-override-value + POSITIONAL ARGUMENTS NAME - Name of the managed instance group to update all-instances' config for. + Name of the managed instance group to update the all instances + configuration for. FLAGS --labels=KEY=VALUE,[KEY=VALUE,...] - Add labels to all-instances' config configuration. + Add labels to the group's all instances configuration. --metadata=KEY=VALUE,[KEY=VALUE,...] - Add metadata to all-instances' config configuration. + Add metadata to the group's all instances configuration. At most one of these can be specified: --region=REGION - Region of the managed instance group to update all-instances' config - for. If not specified, you might be prompted to select a region - (interactive mode only). + Region of the managed instance group to update the all instances + configuration for. If not specified, you might be prompted to select + a region (interactive mode only). A list of regions can be fetched by running: @@ -47,9 +58,9 @@ FLAGS invocation. --zone=ZONE - Zone of the managed instance group to update all-instances' config - for. If not specified, you might be prompted to select a zone - (interactive mode only). + Zone of the managed instance group to update the all instances + configuration for. If not specified, you might be prompted to select + a zone (interactive mode only). A list of zones can be fetched by running: @@ -70,5 +81,8 @@ 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 compute instance-groups managed all-instances-config \ + update diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index 925c1af31..df3f3815f 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -39,6 +39,7 @@ SYNOPSIS [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--source-instance-template=SOURCE_INSTANCE_TEMPLATE] [--subnet=SUBNET] [--tags=TAG,[TAG,...]] + [--target-distribution-shape=SHAPE] [--termination-time=TERMINATION_TIME] [--threads-per-core=THREADS_PER_CORE] [--visible-core-count=VISIBLE_CORE_COUNT] @@ -690,6 +691,25 @@ OPTIONAL FLAGS $ gcloud compute instances list --filter='tags:tag1' + --target-distribution-shape=SHAPE + Specifies whether and how to distribute VMs across multiple zones in a + region or to enforce placement of VMs in a single zone. The default + shape is ANY_SINGLE_ZONE. SHAPE must be one of: + + ANY + Allows creating VMs in multiple zones if one zone cannot + accommodate all the requested VMs. The resulting distribution + shapes can vary. + ANY_SINGLE_ZONE + Enforces VM placement in one allowed zone. Use this to avoid + cross-zone network egress or to reduce network latency. This is the + default value. + BALANCED + Allows distribution of VMs in zones where resources are available + while distributing VMs as evenly as possible across selected zones + to minimize the impact of zonal failures. Recommended for highly + available serving or batch workloads. + --termination-time=TERMINATION_TIME Limits how long this VM instance can run, specified as a time. Format the time, TERMINATION_TIME, as a RFC 3339 timestamp. Alternatively, to diff --git a/gcloud/alpha/compute/instances/ops-agents/policies/create b/gcloud/alpha/compute/instances/ops-agents/policies/create index 5bec2531a..a46e4482c 100644 --- a/gcloud/alpha/compute/instances/ops-agents/policies/create +++ b/gcloud/alpha/compute/instances/ops-agents/policies/create @@ -242,6 +242,7 @@ REQUIRED FLAGS ubuntu 20.04 ubuntu 21.04 ubuntu 21.10 + ubuntu 22.04 windows 10.* windows 6.* diff --git a/gcloud/alpha/compute/instances/ops-agents/policies/update b/gcloud/alpha/compute/instances/ops-agents/policies/update index 5b19b16c5..ffab886ff 100644 --- a/gcloud/alpha/compute/instances/ops-agents/policies/update +++ b/gcloud/alpha/compute/instances/ops-agents/policies/update @@ -279,6 +279,7 @@ FLAGS ubuntu 20.04 ubuntu 21.04 ubuntu 21.10 + ubuntu 22.04 windows 10.* windows 6.* diff --git a/gcloud/alpha/compute/security-policies/create b/gcloud/alpha/compute/security-policies/create index 1d6230c0e..06172e3d2 100644 --- a/gcloud/alpha/compute/security-policies/create +++ b/gcloud/alpha/compute/security-policies/create @@ -38,7 +38,7 @@ FLAGS --type=SECURITY_POLICY_TYPE The type indicates the intended use of the security policy. SECURITY_POLICY_TYPE must be one of: CLOUD_ARMOR, CLOUD_ARMOR_EDGE, - CLOUD_ARMOR_NETWORK. + CLOUD_ARMOR_NETWORK, CLOUD_ARMOR_INTERNAL_SERVICE. At most one of these can be specified: diff --git a/gcloud/alpha/compute/target-tcp-proxies/create b/gcloud/alpha/compute/target-tcp-proxies/create index f26e04839..8c021541d 100644 --- a/gcloud/alpha/compute/target-tcp-proxies/create +++ b/gcloud/alpha/compute/target-tcp-proxies/create @@ -5,6 +5,8 @@ SYNOPSIS gcloud alpha compute target-tcp-proxies create NAME --backend-service=BACKEND_SERVICE [--description=DESCRIPTION] [--[no-]proxy-bind] [--proxy-header=PROXY_HEADER; default="NONE"] + [--backend-service-region=BACKEND_SERVICE_REGION + | --global-backend-service] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -51,6 +53,41 @@ OPTIONAL FLAGS Enables PROXY protocol (version 1) for passing client connection information. + At most one of these can be specified: + + --backend-service-region=BACKEND_SERVICE_REGION + Region of the backend service to operate on. If not specified it will + be set to the region of the TCP Proxy. Overrides the default + compute/region property value for this command invocation. + + --global-backend-service + If set, the backend service is global. + + At most one of these can be specified: + + --global + If set, the target TCP proxy is global. + + --region=REGION + Region of the target TCP proxy to create. If not specified, you might + be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/target-tcp-proxies/delete b/gcloud/alpha/compute/target-tcp-proxies/delete index 829c1d3cf..9505402b5 100644 --- a/gcloud/alpha/compute/target-tcp-proxies/delete +++ b/gcloud/alpha/compute/target-tcp-proxies/delete @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud alpha compute target-tcp-proxies delete NAME [NAME ...] - [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute target-tcp-proxies delete deletes one or more @@ -13,6 +13,32 @@ POSITIONAL ARGUMENTS NAME [NAME ...] Names of the target TCP proxies to delete. +FLAGS + At most one of these can be specified: + + --global + If set, the target TCP proxies are global. + + --region=REGION + Region of the target TCP proxies to delete. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/target-tcp-proxies/describe b/gcloud/alpha/compute/target-tcp-proxies/describe index 02178c4dd..51005393f 100644 --- a/gcloud/alpha/compute/target-tcp-proxies/describe +++ b/gcloud/alpha/compute/target-tcp-proxies/describe @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha compute target-tcp-proxies describe NAME - [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute target-tcp-proxies describe displays all data @@ -14,6 +14,32 @@ POSITIONAL ARGUMENTS NAME Name of the target TCP proxy to describe. +FLAGS + At most one of these can be specified: + + --global + If set, the target TCP proxy is global. + + --region=REGION + Region of the target TCP proxy to describe. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/target-tcp-proxies/list b/gcloud/alpha/compute/target-tcp-proxies/list index 2ba382452..70e590e55 100644 --- a/gcloud/alpha/compute/target-tcp-proxies/list +++ b/gcloud/alpha/compute/target-tcp-proxies/list @@ -3,14 +3,19 @@ NAME target TCP proxies SYNOPSIS - gcloud alpha compute target-tcp-proxies list [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha compute target-tcp-proxies list [NAME ...] + [--regexp=REGEXP, -r REGEXP] [--global | --regions=[REGION,...]] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute target-tcp-proxies list displays all Google Compute Engine target TCP proxies in a project. + By default, global target TCP proxies and target TCP proxies from all + regions are listed. The results can be narrowed down by providing the + --global or --regions flag. + EXAMPLES To list all target TCP proxies in a project in table form, run: @@ -20,6 +25,41 @@ EXAMPLES $ gcloud alpha compute target-tcp-proxies list --uri + To list all global target TCP proxies in a project, run: + + $ gcloud alpha compute target-tcp-proxies list --global + + To list all target TCP proxies in the us-central1 and europe-west1 regions, + given they are regional resources, run: + + $ gcloud alpha compute target-tcp-proxies list \ + --filter="region:( europe-west1 us-central1 )" + +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. + + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. + +FLAGS + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. + + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + + At most one of these can be specified: + + --global + If provided, only global resources are shown. + + --regions=[REGION,...] + If provided, only regional resources are shown. If arguments are + provided, only resources from the given regions are shown. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/compute/tpus/tpu-vm/create b/gcloud/alpha/compute/tpus/tpu-vm/create index d94154867..4fb6c564f 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/create +++ b/gcloud/alpha/compute/tpus/tpu-vm/create @@ -9,8 +9,8 @@ SYNOPSIS [--metadata-from-file=[METADATA_FROM_FILE,...]] [--network=NETWORK; default="default"] [--preemptible] [--range=RANGE] [--reserved] [--scopes=[SCOPES,...]] - [--service-account=SERVICE_ACCOUNT] [--subnetwork=SUBNETWORK] - [--tags=[TAGS,...]] [GCLOUD_WIDE_FLAG ...] + [--service-account=SERVICE_ACCOUNT] [--shielded-secure-boot] + [--subnetwork=SUBNETWORK] [--tags=[TAGS,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a new Cloud TPU VM node. @@ -163,6 +163,10 @@ OPTIONAL FLAGS Email address of the service account. If empty, default Google Compute Engine service account will be used. + --shielded-secure-boot + Specifies that the TPU instances are created with secure boot enabled. + This implicitly makes them Shielded VM instances. + --subnetwork=SUBNETWORK Subnetwork that this TPU will be a part of. diff --git a/gcloud/alpha/dataproc/jobs/submit/hadoop b/gcloud/alpha/dataproc/jobs/submit/hadoop index 80cb48b76..cd2949012 100644 --- a/gcloud/alpha/dataproc/jobs/submit/hadoop +++ b/gcloud/alpha/dataproc/jobs/submit/hadoop @@ -10,8 +10,8 @@ SYNOPSIS [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] DESCRIPTION (ALPHA) Submit a Hadoop job to a cluster. @@ -111,6 +111,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hadoop. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/alpha/dataproc/jobs/submit/hive b/gcloud/alpha/dataproc/jobs/submit/hive index 0e3367321..316258be9 100644 --- a/gcloud/alpha/dataproc/jobs/submit/hive +++ b/gcloud/alpha/dataproc/jobs/submit/hive @@ -9,8 +9,8 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] [--params=[PARAM=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Submit a Hive job to a cluster. @@ -89,6 +89,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hive. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/alpha/dataproc/jobs/submit/pig b/gcloud/alpha/dataproc/jobs/submit/pig index 8194edaa9..e373d6d36 100644 --- a/gcloud/alpha/dataproc/jobs/submit/pig +++ b/gcloud/alpha/dataproc/jobs/submit/pig @@ -10,8 +10,8 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] [--params=[PARAM=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Submit a Pig job to a cluster. @@ -97,6 +97,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Pig. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/alpha/dataproc/jobs/submit/presto b/gcloud/alpha/dataproc/jobs/submit/presto index fba634d87..52e07746f 100644 --- a/gcloud/alpha/dataproc/jobs/submit/presto +++ b/gcloud/alpha/dataproc/jobs/submit/presto @@ -10,7 +10,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PARAM=VALUE,...]] + [--properties=[PARAM=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--query-output-format=QUERY_OUTPUT_FORMAT] [--region=REGION] [GCLOUD_WIDE_FLAG ...] @@ -90,6 +90,23 @@ OPTIONAL FLAGS --properties=[PARAM=VALUE,...] A list of key value pairs to set Presto session properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --query-output-format=QUERY_OUTPUT_FORMAT The query output display format. See the Presto documentation for supported output formats. diff --git a/gcloud/alpha/dataproc/jobs/submit/pyspark b/gcloud/alpha/dataproc/jobs/submit/pyspark index 7197c7148..6a87747e6 100644 --- a/gcloud/alpha/dataproc/jobs/submit/pyspark +++ b/gcloud/alpha/dataproc/jobs/submit/pyspark @@ -10,8 +10,9 @@ SYNOPSIS [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PROPERTY=VALUE,...]] [--py-files=[PY_FILE,...]] - [--region=REGION] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--py-files=[PY_FILE,...]] [--region=REGION] [GCLOUD_WIDE_FLAG ...] + [-- JOB_ARGS ...] DESCRIPTION (ALPHA) Submit a PySpark job to a cluster. @@ -102,6 +103,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --py-files=[PY_FILE,...] Comma separated list of Python files to be provided to the job. Must be one of the following file formats ".py, .zip, or .egg". diff --git a/gcloud/alpha/dataproc/jobs/submit/spark b/gcloud/alpha/dataproc/jobs/submit/spark index be322af9a..ae3d18940 100644 --- a/gcloud/alpha/dataproc/jobs/submit/spark +++ b/gcloud/alpha/dataproc/jobs/submit/spark @@ -10,8 +10,8 @@ SYNOPSIS [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] DESCRIPTION (ALPHA) Submit a Spark job to a cluster. @@ -114,6 +114,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/alpha/dataproc/jobs/submit/spark-r b/gcloud/alpha/dataproc/jobs/submit/spark-r index ac3e41972..3bc18e39b 100644 --- a/gcloud/alpha/dataproc/jobs/submit/spark-r +++ b/gcloud/alpha/dataproc/jobs/submit/spark-r @@ -10,8 +10,8 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] DESCRIPTION (ALPHA) Submit a SparkR job to a cluster. @@ -97,6 +97,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/alpha/dataproc/jobs/submit/spark-sql b/gcloud/alpha/dataproc/jobs/submit/spark-sql index b0d20b5c4..a4122636c 100644 --- a/gcloud/alpha/dataproc/jobs/submit/spark-sql +++ b/gcloud/alpha/dataproc/jobs/submit/spark-sql @@ -10,8 +10,8 @@ SYNOPSIS [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] [--params=[PARAM=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Submit a Spark SQL job to a cluster. @@ -91,6 +91,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hive. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/alpha/dataproc/workflow-templates/add-job/hadoop b/gcloud/alpha/dataproc/workflow-templates/add-job/hadoop index b198d5575..a4d1fb1c7 100644 --- a/gcloud/alpha/dataproc/workflow-templates/add-job/hadoop +++ b/gcloud/alpha/dataproc/workflow-templates/add-job/hadoop @@ -8,7 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] @@ -104,6 +104,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hadoop. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/alpha/dataproc/workflow-templates/add-job/hive b/gcloud/alpha/dataproc/workflow-templates/add-job/hive index a1f8326d5..ca65f7f6e 100644 --- a/gcloud/alpha/dataproc/workflow-templates/add-job/hive +++ b/gcloud/alpha/dataproc/workflow-templates/add-job/hive @@ -8,6 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--continue-on-failure] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--params=[PARAM=VALUE,...]] [--properties=[PROPERTY=VALUE,...]] + [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -86,6 +87,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hive. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/alpha/dataproc/workflow-templates/add-job/pig b/gcloud/alpha/dataproc/workflow-templates/add-job/pig index 4c7ededd1..55a4435cb 100644 --- a/gcloud/alpha/dataproc/workflow-templates/add-job/pig +++ b/gcloud/alpha/dataproc/workflow-templates/add-job/pig @@ -9,6 +9,7 @@ SYNOPSIS [--continue-on-failure] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--params=[PARAM=VALUE,...]] [--properties=[PROPERTY=VALUE,...]] + [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -91,6 +92,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Pig. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/alpha/dataproc/workflow-templates/add-job/presto b/gcloud/alpha/dataproc/workflow-templates/add-job/presto index e009fcea5..5cd079c73 100644 --- a/gcloud/alpha/dataproc/workflow-templates/add-job/presto +++ b/gcloud/alpha/dataproc/workflow-templates/add-job/presto @@ -8,7 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--client-tags=[CLIENT_TAG,...]] [--continue-on-failure] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PARAM=VALUE,...]] + [--properties=[PARAM=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--query-output-format=QUERY_OUTPUT_FORMAT] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] @@ -89,6 +89,23 @@ OPTIONAL FLAGS --properties=[PARAM=VALUE,...] A list of key value pairs to set Presto session properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --query-output-format=QUERY_OUTPUT_FORMAT The query output display format. See the Presto documentation for supported output formats. diff --git a/gcloud/alpha/dataproc/workflow-templates/add-job/pyspark b/gcloud/alpha/dataproc/workflow-templates/add-job/pyspark index 13dae2de1..3445e4e35 100644 --- a/gcloud/alpha/dataproc/workflow-templates/add-job/pyspark +++ b/gcloud/alpha/dataproc/workflow-templates/add-job/pyspark @@ -8,9 +8,9 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] [--py-files=[PY_FILE,...]] - [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] - [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--py-files=[PY_FILE,...]] [--start-after=STEP_ID,[STEP_ID,...]] + [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] DESCRIPTION (ALPHA) Add a PySpark job to the workflow template. @@ -100,6 +100,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --py-files=[PY_FILE,...] Comma separated list of Python files to be provided to the job. Must be one of the following file formats ".py, .zip, or .egg". diff --git a/gcloud/alpha/dataproc/workflow-templates/add-job/spark b/gcloud/alpha/dataproc/workflow-templates/add-job/spark index 499f977ec..4d2002c0c 100644 --- a/gcloud/alpha/dataproc/workflow-templates/add-job/spark +++ b/gcloud/alpha/dataproc/workflow-templates/add-job/spark @@ -7,7 +7,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [--class=MAIN_CLASS --jar=MAIN_JAR] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] @@ -96,6 +96,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/alpha/dataproc/workflow-templates/add-job/spark-r b/gcloud/alpha/dataproc/workflow-templates/add-job/spark-r index 876b19dc7..d80d175ef 100644 --- a/gcloud/alpha/dataproc/workflow-templates/add-job/spark-r +++ b/gcloud/alpha/dataproc/workflow-templates/add-job/spark-r @@ -8,7 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] @@ -96,6 +96,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/alpha/dataproc/workflow-templates/add-job/spark-sql b/gcloud/alpha/dataproc/workflow-templates/add-job/spark-sql index eef32c6a9..b314df142 100644 --- a/gcloud/alpha/dataproc/workflow-templates/add-job/spark-sql +++ b/gcloud/alpha/dataproc/workflow-templates/add-job/spark-sql @@ -8,7 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--driver-log-levels=[PACKAGE=LEVEL,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--params=[PARAM=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -88,6 +88,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hive. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/alpha/functions/deploy b/gcloud/alpha/functions/deploy index e5d061c6b..3399451e6 100644 --- a/gcloud/alpha/functions/deploy +++ b/gcloud/alpha/functions/deploy @@ -38,10 +38,11 @@ SYNOPSIS /secret_path=SECRET_VALUE_REF, /mount_path:/secret_file_path=SECRET_VALUE_REF,...]] [--clear-vpc-connector | --vpc-connector=VPC_CONNECTOR] - [--trigger-bucket=TRIGGER_BUCKET - | --trigger-event-filters=[ATTRIBUTE=VALUE,...] | --trigger-http + [--trigger-bucket=TRIGGER_BUCKET | --trigger-http | --trigger-topic=TRIGGER_TOPIC - | --trigger-event=EVENT_TYPE --trigger-resource=RESOURCE] + | --trigger-event=EVENT_TYPE --trigger-resource=RESOURCE + | --trigger-event-filters=[ATTRIBUTE=VALUE,...] + --trigger-event-filters-path-pattern=[ATTRIBUTE=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -559,11 +560,6 @@ FLAGS Google Cloud Storage bucket name. Every change in files in this bucket will trigger function execution. - --trigger-event-filters=[ATTRIBUTE=VALUE,...] - The Eventarc matching criteria for the trigger. The criteria can be - specified either as a single comma-separated argument or as multiple - arguments. This is only relevant when --gen2 is provided. - --trigger-http Function will be assigned an endpoint, which you can view by using the describe command. Any HTTP request (of a supported type) to the @@ -589,6 +585,17 @@ FLAGS must be a bucket name. For a list of expected resources, call gcloud functions event-types list. + --trigger-event-filters=[ATTRIBUTE=VALUE,...] + The Eventarc matching criteria for the trigger. The criteria can be + specified either as a single comma-separated argument or as multiple + arguments. This is only relevant when --gen2 is provided. + + --trigger-event-filters-path-pattern=[ATTRIBUTE=VALUE,...] + The Eventarc matching criteria for the trigger in path pattern + format. The criteria can be specified as a single comma-separated + argument or as multiple arguments. This is only relevant when --gen2 + is provided. + 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/logging/metrics/create b/gcloud/alpha/logging/metrics/create index 05fcc12ee..5069f9f55 100644 --- a/gcloud/alpha/logging/metrics/create +++ b/gcloud/alpha/logging/metrics/create @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha logging metrics create METRIC_NAME (--config-from-file=CONFIG_FROM_FILE - | --description=DESCRIPTION --log-filter=LOG_FILTER) - [GCLOUD_WIDE_FLAG ...] + | [--description=DESCRIPTION --log-filter=LOG_FILTER + : --bucket-name=BUCKET_NAME]) [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates a logs-based metric to count the number of log entries that @@ -60,6 +60,9 @@ REQUIRED FLAGS This flag must be specified if any of the other arguments in this group are specified. + --bucket-name=BUCKET_NAME + The Log Bucket name which owns the log-based metric. + 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/logging/metrics/update b/gcloud/alpha/logging/metrics/update index d309b3beb..d8d45f5e9 100644 --- a/gcloud/alpha/logging/metrics/update +++ b/gcloud/alpha/logging/metrics/update @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha logging metrics update METRIC_NAME - (--config-from-file=CONFIG_FROM_FILE - | --description=DESCRIPTION --log-filter=LOG_FILTER) + (--config-from-file=CONFIG_FROM_FILE | --bucket-name=BUCKET_NAME + --description=DESCRIPTION --log-filter=LOG_FILTER) [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -54,6 +54,9 @@ REQUIRED FLAGS Arguments to specify information about simple counter logs-based metrics. + --bucket-name=BUCKET_NAME + The Log Bucket name which owns the log-based metric. + --description=DESCRIPTION A new description for the metric. If omitted, the description is not changed. diff --git a/gcloud/alpha/monitoring/metrics-scopes/create b/gcloud/alpha/monitoring/metrics-scopes/create index 279b54b07..ec706045f 100644 --- a/gcloud/alpha/monitoring/metrics-scopes/create +++ b/gcloud/alpha/monitoring/metrics-scopes/create @@ -48,5 +48,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta monitoring metrics-scopes create diff --git a/gcloud/alpha/monitoring/metrics-scopes/delete b/gcloud/alpha/monitoring/metrics-scopes/delete index 674be8ed4..29fb3df9d 100644 --- a/gcloud/alpha/monitoring/metrics-scopes/delete +++ b/gcloud/alpha/monitoring/metrics-scopes/delete @@ -47,5 +47,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 monitoring metrics-scopes delete diff --git a/gcloud/alpha/monitoring/metrics-scopes/describe b/gcloud/alpha/monitoring/metrics-scopes/describe index 9bd749431..ae33f1d53 100644 --- a/gcloud/alpha/monitoring/metrics-scopes/describe +++ b/gcloud/alpha/monitoring/metrics-scopes/describe @@ -56,5 +56,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 monitoring metrics-scopes describe diff --git a/gcloud/alpha/monitoring/metrics-scopes/help b/gcloud/alpha/monitoring/metrics-scopes/help index 4e003c8c3..96187ee34 100644 --- a/gcloud/alpha/monitoring/metrics-scopes/help +++ b/gcloud/alpha/monitoring/metrics-scopes/help @@ -36,5 +36,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 monitoring metrics-scopes diff --git a/gcloud/alpha/monitoring/metrics-scopes/list b/gcloud/alpha/monitoring/metrics-scopes/list index a0c32f819..f511bb772 100644 --- a/gcloud/alpha/monitoring/metrics-scopes/list +++ b/gcloud/alpha/monitoring/metrics-scopes/list @@ -69,5 +69,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 monitoring metrics-scopes list diff --git a/gcloud/alpha/pubsub/subscriptions/create b/gcloud/alpha/pubsub/subscriptions/create index 64623b964..f49855c5b 100644 --- a/gcloud/alpha/pubsub/subscriptions/create +++ b/gcloud/alpha/pubsub/subscriptions/create @@ -12,6 +12,8 @@ SYNOPSIS [--push-auth-service-account=SERVICE_ACCOUNT_EMAIL] [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] [--push-endpoint=PUSH_ENDPOINT] [--retain-acked-messages] + [--bigquery-table=BIGQUERY_TABLE + : --drop-unknown-fields --use-topic-schema --write-metadata] [--max-delivery-attempts=MAX_DELIVERY_ATTEMPTS [--dead-letter-topic=DEAD_LETTER_TOPIC : --dead-letter-topic-project=DEAD_LETTER_TOPIC_PROJECT]] @@ -133,6 +135,32 @@ OPTIONAL FLAGS --message-retention-duration window. Acknowledged messages are not retained by default. + BigQuery Config Options. The Cloud Pub/Sub service account associated with + the enclosing subscription's parent project (i.e., + service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have + permission to write to this BigQuery table. + + --bigquery-table=BIGQUERY_TABLE + A BigQuery table of the form {project}:{dataset_name}.{table_name} to + which to write messages for this subscription. + + This flag must be specified if any of the other arguments in this + group are specified. + + --drop-unknown-fields + When --use-topic-schema is set, whether or not to ignore fields in + the topic schema that do not appear in the BigQuery schema. If false, + then the BigQuery schema must contain all fields that are also + present in the topic schema. + + --use-topic-schema + Whether or not to use the schema for the subscription's topic (if it + exists) when writing messages to BigQuery. + + --write-metadata + Whether or not to write message metadata including message ID, + publish timestamp, ordering key, and attributes to BigQuery. + Dead Letter Queue Options. The Cloud Pub/Sub service account associated with the enclosing subscription's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have diff --git a/gcloud/alpha/pubsub/subscriptions/update b/gcloud/alpha/pubsub/subscriptions/update index 4a89cae09..3bff4ae98 100644 --- a/gcloud/alpha/pubsub/subscriptions/update +++ b/gcloud/alpha/pubsub/subscriptions/update @@ -11,6 +11,8 @@ SYNOPSIS [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] [--push-endpoint=PUSH_ENDPOINT] [--retain-acked-messages] [--update-labels=[KEY=VALUE,...]] + [--clear-bigquery-config | [--bigquery-table=BIGQUERY_TABLE + : --drop-unknown-fields --use-topic-schema --write-metadata]] [--clear-dead-letter-policy | --max-delivery-attempts=MAX_DELIVERY_ATTEMPTS [--dead-letter-topic=DEAD_LETTER_TOPIC @@ -97,6 +99,37 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + At most one of these can be specified: + + --clear-bigquery-config + If set, clear the BigQuery config from the subscription. + + BigQuery Config Options. The Cloud Pub/Sub service account associated + with the enclosing subscription's parent project (i.e., + service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must + have permission to write to this BigQuery table. + + --bigquery-table=BIGQUERY_TABLE + A BigQuery table of the form {project}:{dataset_name}.{table_name} + to which to write messages for this subscription. + + This flag must be specified if any of the other arguments in this + group are specified. + + --drop-unknown-fields + When --use-topic-schema is set, whether or not to ignore fields in + the topic schema that do not appear in the BigQuery schema. If + false, then the BigQuery schema must contain all fields that are + also present in the topic schema. + + --use-topic-schema + Whether or not to use the schema for the subscription's topic (if + it exists) when writing messages to BigQuery. + + --write-metadata + Whether or not to write message metadata including message ID, + publish timestamp, ordering key, and attributes to BigQuery. + At most one of these can be specified: --clear-dead-letter-policy diff --git a/gcloud/alpha/run/services/logs/help b/gcloud/alpha/run/services/logs/help index 338a1e490..710b9feea 100644 --- a/gcloud/alpha/run/services/logs/help +++ b/gcloud/alpha/run/services/logs/help @@ -99,6 +99,9 @@ COMMANDS read (ALPHA) Read logs for a service. + tail + (ALPHA) Tail logs for a service. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/run/services/logs/tail b/gcloud/alpha/run/services/logs/tail new file mode 100644 index 000000000..af58a1219 --- /dev/null +++ b/gcloud/alpha/run/services/logs/tail @@ -0,0 +1,114 @@ +NAME + gcloud alpha run services logs tail - tail logs for a service + +SYNOPSIS + gcloud alpha run services logs tail SERVICE [--log-filter=LOG_FILTER] + [--platform=PLATFORM; default="managed"] + [--region=REGION + | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION + | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha run services logs tail tails log-entries for a + particular Cloud Run service in real time. The log entries are formatted + for consumption in a terminal. + +POSITIONAL ARGUMENTS + SERVICE + Name for a Cloud Run service. + +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 + + --platform=PLATFORM; default="managed" + Target platform for running commands. Alternatively, set the property + [run/platform]. PLATFORM must be one of: + + managed + Fully managed version of Cloud Run. Use with the --region flag or + set the [run/region] property to specify a Cloud Run region. + gke + Cloud Run for Anthos on Google Cloud. Use with the --cluster and + --cluster-location flags or set the [run/cluster] and + [run/cluster_location] properties to specify a cluster in a given + zone. + kubernetes + Use a Knative-compatible kubernetes cluster. Use with the + --kubeconfig and --context flags to specify a kubeconfig file and + the context for connecting. + + Arguments to locate resources, depending on the platform used. + + At most one of these can be specified: + + Only applicable if connecting to Cloud Run (fully managed). Specify + --platform=managed to use: + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Only applicable if connecting to Cloud Run for Anthos deployed on Google + Cloud. Specify --platform=gke to use: + + Cluster resource - Kubernetes Engine cluster to connect to. 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 run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --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; + ◇ set the property run/cluster; + ◇ specify the cluster from a list of available clusters. + + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. To set the location attribute: + ◇ provide the argument --cluster on the command line with a + fully specified name; + ◇ set the property run/cluster with a fully specified name; + ◇ specify the cluster from a list of available clusters with a + fully specified name; + ◇ provide the argument --cluster-location on the command line; + ◇ set the property run/cluster_location; + ◇ specify the cluster location from a list of available zones. + + Only applicable if connecting to Cloud Run for Anthos deployed on + VMware. Specify --platform=kubernetes to use: + + --context=CONTEXT + The name of the context in your kubectl config file to use for + connecting. + + --kubeconfig=KUBECONFIG + The absolute path to your kubectl config file. If not specified, + the colon- or semicolon-delimited list of paths specified by + $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to + ~/.kube/config. + +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/storage/cp b/gcloud/alpha/storage/cp index b45cdb8b6..5a99378de 100644 --- a/gcloud/alpha/storage/cp +++ b/gcloud/alpha/storage/cp @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud alpha storage cp SOURCE [SOURCE ...] DESTINATION - [--all-versions, -A] [--cache-control=CACHE_CONTROL] [--no-clobber, -n] - [--content-disposition=CONTENT_DISPOSITION] + [--all-versions, -A] [--cache-control=CACHE_CONTROL] + [--canned-acl=CANNED_ACL, --predefined-acl=CANNED_ACL, -a CANNED_ACL] + [--no-clobber, -n] [--content-disposition=CONTENT_DISPOSITION] [--content-encoding=CONTENT_ENCODING] [--content-language=CONTENT_LANGUAGE] [--content-md5=MD5_DIGEST] [--content-type=CONTENT_TYPE] [--continue-on-error, -c] @@ -15,9 +16,10 @@ SYNOPSIS [--preserve-posix, -P] [--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,...], - -j [FILE_EXTENSIONS,...]] [GCLOUD_WIDE_FLAG ...] + [--gzip-in-flight=[FILE_EXTENSIONS,...], -j [FILE_EXTENSIONS,...] + | --gzip-in-flight-all, -J + | --gzip-local=[FILE_EXTENSIONS,...], -z [FILE_EXTENSIONS,...] + | --gzip-local-all, -Z] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Copy data between your local file system and the cloud, within the @@ -64,6 +66,11 @@ FLAGS --cache-control=CACHE_CONTROL How caches should handle requests and responses. + --canned-acl=CANNED_ACL, --predefined-acl=CANNED_ACL, -a CANNED_ACL + Applies predefined, or "canned," ACLs to a copied object. See docs for + a list of predefined ACL constants: + https://cloud.google.com/storage/docs/access-control/lists#predefined-acl + --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 @@ -168,15 +175,7 @@ FLAGS At most one of these can be specified: - --gzip-in-flight-all, -J - Applies gzip transport encoding to file uploads. This option works - like the --gzip-transfer option described above, but it applies to - all uploaded files, regardless of extension. - - CAUTION: If some of the source files don't compress well, such as - binary data, using this option may result in longer uploads. - - --gzip-in-flight-extensions=[FILE_EXTENSIONS,...], -j [FILE_EXTENSIONS,...] + --gzip-in-flight=[FILE_EXTENSIONS,...], -j [FILE_EXTENSIONS,...] Applies gzip transport encoding to any file upload whose extension matches the input extension list. This is useful when uploading files with compressible content such as .js, .css, or .html files. This @@ -188,6 +187,42 @@ FLAGS and Cloud Storage objects remain uncompressed. The uploaded objects retain the Content-Type and name of the original files. + --gzip-in-flight-all, -J + Applies gzip transport encoding to file uploads. This option works + like the --gzip-in-flight option described above, but it applies to + all uploaded files, regardless of extension. + + CAUTION: If some of the source files don't compress well, such as + binary data, using this option may result in longer uploads. + + --gzip-local=[FILE_EXTENSIONS,...], -z [FILE_EXTENSIONS,...] + Applies gzip content encoding to any file upload whose extension + matches the input extension list. This is useful when uploading files + with compressible content such as .js, .css, or .html files. This + saves network bandwidth and space in Cloud Storage. + + When you specify the --gzip-local option, the data from files is + compressed before it is uploaded, but the original files are left + uncompressed on the local disk. The uploaded objects retain the + Content-Type and name of the original files. However, the + Content-Encoding metadata is set to gzip and the Cache-Control + metadata set to no-transform. The data remains compressed on Cloud + Storage servers and will not be decompressed on download by gcloud + stroage because of the no-transform field. + + Since the local gzip option compresses data prior to upload, it is + not subject to the same compression buffer bottleneck of the + in-flight gzip option. + + --gzip-local-all, -Z + Applies gzip content encoding to file uploads. This option works like + the --gzip-local option described above, but it applies to all + uploaded files, regardless of extension. + + CAUTION: If some of the source files don't compress well, such as + binary data, using this option may result in files taking up more + space in the cloud than they would if left uncompressed. + 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/vmware/help b/gcloud/alpha/vmware/help index b5b9f49f7..a683c01f7 100644 --- a/gcloud/alpha/vmware/help +++ b/gcloud/alpha/vmware/help @@ -28,6 +28,10 @@ GROUPS (ALPHA) Manage VMware Engine VPC peering using Google Cloud VMware Engine. + network-policies + (ALPHA) Manage VMware Engine network policies in Google Cloud VMware + Engine. + node-types (ALPHA) Show node types in Google Cloud VMware Engine. diff --git a/gcloud/alpha/vmware/network-peerings/create b/gcloud/alpha/vmware/network-peerings/create index 371153915..cc7ae8dd9 100644 --- a/gcloud/alpha/vmware/network-peerings/create +++ b/gcloud/alpha/vmware/network-peerings/create @@ -5,8 +5,9 @@ NAME SYNOPSIS gcloud alpha vmware network-peerings create NETWORK_PEERING --peer-network=PEER_NETWORK --peer-network-type=PEER_NETWORK_TYPE - (--vmware-engine-network=VMWARE_ENGINE_NETWORK : --location=LOCATION) - [--async] [--description=DESCRIPTION] [--no-exchange-subnet-routes] + (--vmware-engine-network=VMWARE_ENGINE_NETWORK + : --network-location=NETWORK_LOCATION) [--async] + [--description=DESCRIPTION] [--no-exchange-subnet-routes] [--no-export-custom-routes] [--no-export-custom-routes-with-public-ip] [--no-import-custom-routes] [--no-import-custom-routes-with-public-ip] [--peer-mtu=PEER_MTU] [GCLOUD_WIDE_FLAG ...] @@ -103,11 +104,11 @@ REQUIRED FLAGS This flag must be specified if any of the other arguments in this group are specified. - --location=LOCATION + --network-location=NETWORK_LOCATION The resource name of the location. To set the location attribute: ▸ provide the argument --vmware-engine-network on the command line with a fully specified name; - ▸ provide the argument --location on the command line; + ▸ provide the argument --network-location on the command line; ▸ set location as 'global' (default) or a region. OPTIONAL FLAGS diff --git a/gcloud/alpha/vmware/network-policies/create b/gcloud/alpha/vmware/network-policies/create new file mode 100644 index 000000000..e6e598fbb --- /dev/null +++ b/gcloud/alpha/vmware/network-policies/create @@ -0,0 +1,138 @@ +NAME + gcloud alpha vmware network-policies create - create a VMware Engine + network policy + +SYNOPSIS + gcloud alpha vmware network-policies create + (NETWORK_POLICY : --location=LOCATION) + --edge-services-cidr=EDGE_SERVICES_CIDR + (--vmware-engine-network=VMWARE_ENGINE_NETWORK + : --network-location=NETWORK_LOCATION) [--async] + [--description=DESCRIPTION] [--external-ip-access] [--internet-access] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a VMware Engine network policy. Only one network policy + applies to a VMware Engine network per region. Check the progress of a + network policy creation using gcloud alpha vmware network-policies list. + +EXAMPLES + To create a network policy called my-network-policy which connects to the + VMware Engine network + projects/my-project/locations/global/vmwareEngineNetworks/my-vmware-engine-network + using the edge services address range 192.168.0.0/26 with the internet + access service enabled and the external IP access service disabled, run: + + $ gcloud alpha vmware network-policies create my-network-policy \ + --location=us-west2 --project=my-project \ + --vmware-engine-network=projects/my-project/locations/global/\ + vmwareEngineNetworks/my-vmware-engine-network \ + --edge-services-cidr=192.168.0.0/26 --internet-access \ + --no-external-ip-access + + Or: + + $ gcloud alpha vmware network-policies create my-network-policy \ + --vmware-engine-network=projects/my-project/locations/global/\ + vmwareEngineNetworks/my-vmware-engine-network \ + --edge-services-cidr=192.168.0.0/26 --internet-access + + In the second example, the project and the location are taken from gcloud + properties core/project and compute/region respectively. If the + --external-ip-access flag is not specified, it is taken as False. + +POSITIONAL ARGUMENTS + VMware Engine Network Policy resource - network_policy. 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 network_policy 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. + + NETWORK_POLICY + ID of the VMware Engine Network Policy or fully qualified identifier + for the VMware Engine Network Policy. To set the network-policy + attribute: + ▸ provide the argument network_policy on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The resource name of the location. To set the location attribute: + ▸ provide the argument network_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + --edge-services-cidr=EDGE_SERVICES_CIDR + IP address range to use for internet access and external IP access + gateways, in CIDR notation. An RFC 1918 CIDR block with a "/26" prefix + is required. + + VMware Engine network resource - vmware_engine_network. 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 --vmware-engine-network 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. + + --vmware-engine-network=VMWARE_ENGINE_NETWORK + ID of the VMware Engine network or fully qualified identifier for the + VMware Engine network. To set the vmware-engine-network attribute: + ▸ provide the argument --vmware-engine-network on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --network-location=NETWORK_LOCATION + The resource name of the location. To set the location attribute: + ▸ provide the argument --vmware-engine-network on the command line + with a fully specified name; + ▸ provide the argument --network-location on the command line; + ▸ set location as 'global' (default) or a region. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + User-provided description of the network policy. + + --external-ip-access + Enable or disable network service that allows external IP addresses to + be assigned to VMware workloads. To enable this service, + internet-access must also be enabled. Use --no-external-ip-access to + disable. If the flag is not provided, access to VMware workloads + through external IP addresses is disabled. + + --internet-access + Enable or disable network service that allows VMware workloads to + access the internet. Use --no-internet-access to disable. If the flag + is not provided, internet access is disabled. + +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/vmware/network-policies/delete b/gcloud/alpha/vmware/network-policies/delete new file mode 100644 index 000000000..feaadb2d7 --- /dev/null +++ b/gcloud/alpha/vmware/network-policies/delete @@ -0,0 +1,73 @@ +NAME + gcloud alpha vmware network-policies delete - delete a VMware Engine + network policy + +SYNOPSIS + gcloud alpha vmware network-policies delete + (NETWORK_POLICY : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a VMware Engine network policy. + +EXAMPLES + To delete a network policy called my-network-policy in project my-project + and region us-west2, run: + + $ gcloud alpha vmware network-policies delete my-network-policy \ + --location=us-west2 --project=my-project + + Or: + + $ gcloud alpha vmware network-policies delete my-network-policy + + In the second example, the project and the location are taken from gcloud + properties core/project and compute/region respectively. + +POSITIONAL ARGUMENTS + VMware Engine Network Policy resource - network_policy. 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 network_policy 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. + + NETWORK_POLICY + ID of the VMware Engine Network Policy or fully qualified identifier + for the VMware Engine Network Policy. To set the network-policy + attribute: + ▸ provide the argument network_policy on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The resource name of the location. To set the location attribute: + ▸ provide the argument network_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +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/vmware/network-policies/describe b/gcloud/alpha/vmware/network-policies/describe new file mode 100644 index 000000000..d62dff28f --- /dev/null +++ b/gcloud/alpha/vmware/network-policies/describe @@ -0,0 +1,67 @@ +NAME + gcloud alpha vmware network-policies describe - describe a VMware Engine + network policy + +SYNOPSIS + gcloud alpha vmware network-policies describe + (NETWORK_POLICY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a VMware Engine network policy. + +EXAMPLES + To get a description of a network policy called my-network-policy in + project my-project and region us-west2, run: + + $ gcloud alpha vmware network-policies describe my-network-policy \ + --location=us-west2 --project=my-project + + Or: + + $ gcloud alpha vmware network-policies describe my-network-policy + + In the second example, the project and the location are taken from gcloud + properties core/project and compute/region respectively. + +POSITIONAL ARGUMENTS + VMware Engine Network Policy resource - network_policy. 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 network_policy 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. + + NETWORK_POLICY + ID of the VMware Engine Network Policy or fully qualified identifier + for the VMware Engine Network Policy. To set the network-policy + attribute: + ▸ provide the argument network_policy on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The resource name of the location. To set the location attribute: + ▸ provide the argument network_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/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/vmware/network-policies/help b/gcloud/alpha/vmware/network-policies/help new file mode 100644 index 000000000..dde45f993 --- /dev/null +++ b/gcloud/alpha/vmware/network-policies/help @@ -0,0 +1,40 @@ +NAME + gcloud alpha vmware network-policies - manage VMware Engine network + policies in Google Cloud VMware Engine + +SYNOPSIS + gcloud alpha vmware network-policies COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage VMware Engine network policies in Google Cloud VMware + Engine. + +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 VMware Engine network policy. + + delete + (ALPHA) Delete a VMware Engine network policy. + + describe + (ALPHA) Describe a VMware Engine network policy. + + list + (ALPHA) List VMware Engine network policies. + + update + (ALPHA) Update a VMware Engine network policy. + +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/vmware/network-policies/list b/gcloud/alpha/vmware/network-policies/list new file mode 100644 index 000000000..3ee4a5705 --- /dev/null +++ b/gcloud/alpha/vmware/network-policies/list @@ -0,0 +1,100 @@ +NAME + gcloud alpha vmware network-policies list - list VMware Engine network + policies + +SYNOPSIS + gcloud alpha vmware network-policies list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List VMware Engine network policies. + +EXAMPLES + To list network policies in your project in the region us-west2 sorted from + oldest to newest, run: + + $ gcloud alpha vmware network-policies list --location=us-west2 \ + --project=my-project --sort-by=~create_time + + Or: + + $ gcloud alpha vmware network-policies list --sort-by=~create_time + + In the second example, the project and the location are taken from gcloud + properties core/project and compute/region respectively. + + To list network policies in your project from all regions, run: + + $ gcloud alpha vmware network-policies list --location=- \ + --project=my-project + + Or: + + $ gcloud alpha vmware network-policies list --location=- + + In the last example, the project is taken from gcloud properties + core/project. + +FLAGS + Location resource - location. 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 compute/region 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 compute/region. + +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/vmware/network-policies/update b/gcloud/alpha/vmware/network-policies/update new file mode 100644 index 000000000..6bac74abc --- /dev/null +++ b/gcloud/alpha/vmware/network-policies/update @@ -0,0 +1,93 @@ +NAME + gcloud alpha vmware network-policies update - update a VMware Engine + network policy + +SYNOPSIS + gcloud alpha vmware network-policies update + (NETWORK_POLICY : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--edge-services-cidr=EDGE_SERVICES_CIDR] + [--external-ip-access] [--internet-access] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a VMware Engine network policy. + +EXAMPLES + To update a network policy named my-network-policy so that it disables the + external IP access service, run: + + $ gcloud alpha vmware network-policies update my-network-policy \ + --location=us-west2 --project=my-project --no-external-ip-access + + Or: + + $ gcloud alpha vmware network-policies update my-network-policy \ + --no-external-ip-access + + In the second example, the project and the location are taken from gcloud + properties core/project and compute/regions respectively. + +POSITIONAL ARGUMENTS + VMware Engine Network Policy resource - network_policy. 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 network_policy 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. + + NETWORK_POLICY + ID of the VMware Engine Network Policy or fully qualified identifier + for the VMware Engine Network Policy. To set the network-policy + attribute: + ▸ provide the argument network_policy on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The resource name of the location. To set the location attribute: + ▸ provide the argument network_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + Updated description for the network policy. + + --edge-services-cidr=EDGE_SERVICES_CIDR + Updated IP address range to use for internet access and external IP + access gateways, in CIDR notation. + + --external-ip-access + Enable or disable network service that allows external IP addresses to + be assigned to VMware workloads. To enable this service, + internet-access must also be enabled. Use --no-external-ip-access to + disable. + + --internet-access + Enable or disable network service that allows VMware workloads to + access the internet. Use --no-internet-access to disable. + +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/beta/builds/cancel b/gcloud/beta/builds/cancel index 1619e7140..42c3d0603 100644 --- a/gcloud/beta/builds/cancel +++ b/gcloud/beta/builds/cancel @@ -25,7 +25,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/builds/describe b/gcloud/beta/builds/describe index 8583a9784..1b240c0c2 100644 --- a/gcloud/beta/builds/describe +++ b/gcloud/beta/builds/describe @@ -21,7 +21,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/builds/list b/gcloud/beta/builds/list index 3ac487d6c..a135ea3c6 100644 --- a/gcloud/beta/builds/list +++ b/gcloud/beta/builds/list @@ -25,7 +25,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/builds/log b/gcloud/beta/builds/log index 84195c24d..5ce61a851 100644 --- a/gcloud/beta/builds/log +++ b/gcloud/beta/builds/log @@ -27,7 +27,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. --stream If a build is ongoing, stream the logs to stdout until the build diff --git a/gcloud/beta/builds/submit b/gcloud/beta/builds/submit index 32a249f39..898f478f8 100644 --- a/gcloud/beta/builds/submit +++ b/gcloud/beta/builds/submit @@ -95,7 +95,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. --substitutions=[KEY=VALUE,...] Parameters to be substituted in the build specification. diff --git a/gcloud/beta/builds/triggers/import b/gcloud/beta/builds/triggers/import index 565f7cc49..76ba44ef3 100644 --- a/gcloud/beta/builds/triggers/import +++ b/gcloud/beta/builds/triggers/import @@ -23,7 +23,7 @@ OPTIONAL FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/builds/triggers/list b/gcloud/beta/builds/triggers/list index 8579d340f..ddf5a40b6 100644 --- a/gcloud/beta/builds/triggers/list +++ b/gcloud/beta/builds/triggers/list @@ -19,7 +19,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/composer/environments/create b/gcloud/beta/composer/environments/create index 230d51f16..ea9b23cc5 100644 --- a/gcloud/beta/composer/environments/create +++ b/gcloud/beta/composer/environments/create @@ -115,7 +115,7 @@ FLAGS When enabled the IP Masq Agent is deployed to the cluster with configuration to masquarade all traffic except between pods. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --env-variables=[NAME=VALUE,...] A comma-delimited list of environment variable NAME=VALUE pairs to @@ -216,7 +216,7 @@ FLAGS IPv4 CIDR range to use for the Cloud SQL network. This should have a size of the netmask not greater than 24. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. --composer-network-ipv4-cidr=COMPOSER_NETWORK_IPV4_CIDR @@ -224,7 +224,7 @@ FLAGS size of the netmask between 24 and 29. Can be specified for Composer 2.X or greater. Cannot be specified - unless '--enable-private-environment' is also specified. + unless --enable-private-environment is also specified. --connection-subnetwork=CONNECTION_SUBNETWORK Subnetwork from which an IP address for internal communications will @@ -233,7 +233,7 @@ FLAGS which the environment is connected. Can be specified for Composer 2.X or greater. Cannot be specified - unless '--enable-private-environment' is also specified. + unless --enable-private-environment is also specified. --enable-private-endpoint Environment cluster is managed using the private IP address of the @@ -243,7 +243,7 @@ FLAGS If not specified, the master API endpoint will be accessible by its public IP address. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. --enable-private-environment @@ -252,28 +252,28 @@ FLAGS If not specified, cluster nodes will be assigned public IP addresses. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --enable-privately-used-public-ips When enabled GKE pods and services may use public(non-RFC1918) IP ranges privately. The ranges are specified by '--cluster-ipv4-cidr' - and ' --services-ipv4-cidr' flags. + and --services-ipv4-cidr flags. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. --master-ipv4-cidr=MASTER_IPV4_CIDR IPv4 CIDR range to use for the cluster master network. This should have a size of the netmask between 23 and 28. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. --web-server-ipv4-cidr=WEB_SERVER_IPV4_CIDR IPv4 CIDR range to use for the Airflow web server network. This should have a size of the netmask between 24 and 29. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. IP Alias (VPC-native) @@ -282,14 +282,14 @@ FLAGS IP address range for the pods in this cluster in CIDR notation (e.g. 10.0.0.0/14). - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --cluster-secondary-range-name=CLUSTER_SECONDARY_RANGE_NAME Secondary range to be used as the source for pod IPs. Alias ranges will be allocated from this secondary range. NAME must be the name of an existing secondary range in the cluster subnetwork. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --enable-ip-alias Enable use of alias IPs @@ -302,7 +302,7 @@ FLAGS used to limit the size of IP range assigned to the node in VPC native cluster setup. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --services-ipv4-cidr=SERVICES_IPV4_CIDR IP range for the services IPs. @@ -314,13 +314,13 @@ FLAGS If unspecified, the services CIDR range will be chosen with a default mask size. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --services-secondary-range-name=SERVICES_SECONDARY_RANGE_NAME Secondary range to be used for services (e.g. ClusterIPs). NAME must be the name of an existing secondary range in the cluster subnetwork. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. Master Authorized Networks configuration @@ -333,7 +333,7 @@ FLAGS Comma separated Master Authorized Networks specified in CIDR notation. - Cannot be specified unless '--enable-master-authorized-networks' is + Cannot be specified unless --enable-master-authorized-networks is also specified. Key resource - The Cloud KMS (Key Management Service) cryptokey that will diff --git a/gcloud/beta/composer/environments/update b/gcloud/beta/composer/environments/update index ea11a9598..2583321d2 100644 --- a/gcloud/beta/composer/environments/update +++ b/gcloud/beta/composer/environments/update @@ -142,7 +142,7 @@ REQUIRED FLAGS Comma separated Master Authorized Networks specified in CIDR notation. - Cannot be specified unless '--enable-master-authorized-networks' is + Cannot be specified unless --enable-master-authorized-networks is also specified. Group of arguments for setting the maintenance window value. diff --git a/gcloud/beta/compute/commitments/create b/gcloud/beta/compute/commitments/create index 86c98ae2f..6bc5a9655 100644 --- a/gcloud/beta/compute/commitments/create +++ b/gcloud/beta/compute/commitments/create @@ -89,7 +89,7 @@ OPTIONAL FLAGS for memory-optimized VMs. TYPE must be one of: accelerator-optimized, compute-optimized, compute-optimized-c2d, general-purpose, general-purpose-e2, general-purpose-n2, general-purpose-n2d, - general-purpose-t2d, memory-optimized. + general-purpose-t2d, memory-optimized, memory-optimized-m3. Manage the reservations to be created with the commitment. diff --git a/gcloud/beta/compute/forwarding-rules/create b/gcloud/beta/compute/forwarding-rules/create index 1be8d276a..7e649fdd9 100644 --- a/gcloud/beta/compute/forwarding-rules/create +++ b/gcloud/beta/compute/forwarding-rules/create @@ -34,6 +34,8 @@ SYNOPSIS | --target-http-proxy-region=TARGET_HTTP_PROXY_REGION] [--global-target-https-proxy | --target-https-proxy-region=TARGET_HTTPS_PROXY_REGION] + [--global-target-tcp-proxy + | --target-tcp-proxy-region=TARGET_TCP_PROXY_REGION] [--port-range=[PORT | START_PORT-END_PORT] | --ports=ALL | [PORT | START_PORT-END_PORT],[...]] [GCLOUD_WIDE_FLAG ...] @@ -213,8 +215,8 @@ OPTIONAL FLAGS INTERNAL Internal load balancing or forwarding, used with --backend-service. INTERNAL_MANAGED - Internal HTTP(S) Load Balancing, used with --target-http-proxy, - --target-https-proxy. + Internal load balancing, used with --target-tcp-proxy, + --target-http-proxy, --target-https-proxy. INTERNAL_SELF_MANAGED Traffic Director load balancing or forwarding, used with --target-http-proxy, --target-https-proxy, --target-grpc-proxy, @@ -440,6 +442,31 @@ OPTIONAL FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + At most one of these can be specified: + + --global-target-tcp-proxy + If set, the tcp proxy is global. + + --target-tcp-proxy-region=TARGET_TCP_PROXY_REGION + Region of the tcp proxy to operate on. If not specified, you might be + prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + At most one of these can be specified: --port-range=[PORT | START_PORT-END_PORT] diff --git a/gcloud/beta/compute/forwarding-rules/set-target b/gcloud/beta/compute/forwarding-rules/set-target index d5f6e2f7e..b2274068e 100644 --- a/gcloud/beta/compute/forwarding-rules/set-target +++ b/gcloud/beta/compute/forwarding-rules/set-target @@ -23,6 +23,8 @@ SYNOPSIS | --target-http-proxy-region=TARGET_HTTP_PROXY_REGION] [--global-target-https-proxy | --target-https-proxy-region=TARGET_HTTPS_PROXY_REGION] + [--global-target-tcp-proxy + | --target-tcp-proxy-region=TARGET_TCP_PROXY_REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -142,8 +144,8 @@ OPTIONAL FLAGS INTERNAL Internal load balancing or forwarding, used with --backend-service. INTERNAL_MANAGED - Internal HTTP(S) Load Balancing, used with --target-http-proxy, - --target-https-proxy. + Internal load balancing, used with --target-tcp-proxy, + --target-http-proxy, --target-https-proxy. INTERNAL_SELF_MANAGED Traffic Director load balancing or forwarding, used with --target-http-proxy, --target-https-proxy, --target-grpc-proxy, @@ -268,6 +270,31 @@ OPTIONAL FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + At most one of these can be specified: + + --global-target-tcp-proxy + If set, the tcp proxy is global. + + --target-tcp-proxy-region=TARGET_TCP_PROXY_REGION + Region of the tcp proxy to operate on. If not specified, you might be + prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/instance-groups/managed/all-instances-config/delete b/gcloud/beta/compute/instance-groups/managed/all-instances-config/delete new file mode 100644 index 000000000..c33566389 --- /dev/null +++ b/gcloud/beta/compute/instance-groups/managed/all-instances-config/delete @@ -0,0 +1,84 @@ +NAME + gcloud beta compute instance-groups managed all-instances-config delete - + delete values defined in the all-instances configuration of a managed + instance group + +SYNOPSIS + gcloud beta compute instance-groups managed all-instances-config delete + NAME [--labels=KEY,[KEY,...]] [--metadata=KEY,[KEY,...]] + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute instance-groups managed all-instances-config + delete deletes one or more values defined in the all-instances + configuration of a managed instance group. + + To apply a revised all-instances configuration to existing instances in the + group, use one of the following methods: + + ▪ Update instances using the update-instances command. + ▪ Recreate instances using the recreate-instances command. + ▪ Use the rolling-action start-update command. + ▪ Use the API to set the group's updatePolicy.type to PROACTIVE. + +EXAMPLES + To delete the group's all-instances configuration in order to stop + overriding the group's instance template for a label with the key label-key + and metadata with the key metadata-key in group my-group, run: + + $ gcloud beta compute instance-groups managed all-instances-config \ + delete my-group --metadata=metadata-key --labels=label-key + +POSITIONAL ARGUMENTS + NAME + Name of the managed instance group to delete the all instances + configuration for. + +FLAGS + --labels=KEY,[KEY,...] + Remove labels keys from the group's all instances configuration. + + --metadata=KEY,[KEY,...] + Remove metadata keys from the group's all instances configuration. + + At most one of these can be specified: + + --region=REGION + Region of the managed instance group to delete the all instances + configuration for. If not specified, you might be prompted to select + a region (interactive mode only). + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + Overrides the default compute/region property value for this command + invocation. + + --zone=ZONE + Zone of the managed instance group to delete the all instances + configuration for. If not specified, you might be prompted to select + a zone (interactive mode only). + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute instance-groups managed \ + all-instances-config delete + diff --git a/gcloud/beta/compute/instance-groups/managed/all-instances-config/help b/gcloud/beta/compute/instance-groups/managed/all-instances-config/help new file mode 100644 index 000000000..f0273b85c --- /dev/null +++ b/gcloud/beta/compute/instance-groups/managed/all-instances-config/help @@ -0,0 +1,35 @@ +NAME + gcloud beta compute instance-groups managed all-instances-config - override + instance template settings for all instances in a managed instance + group + +SYNOPSIS + gcloud beta compute instance-groups managed all-instances-config COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Override instance template settings for all instances in a managed + instance group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (BETA) Delete values defined in the all-instances configuration of a + managed instance group. + + update + (BETA) Update the all-instances configuration of a managed instance + group. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute instance-groups managed all-instances-config + diff --git a/gcloud/beta/compute/instance-groups/managed/all-instances-config/update b/gcloud/beta/compute/instance-groups/managed/all-instances-config/update new file mode 100644 index 000000000..e56bfeab6 --- /dev/null +++ b/gcloud/beta/compute/instance-groups/managed/all-instances-config/update @@ -0,0 +1,86 @@ +NAME + gcloud beta compute instance-groups managed all-instances-config update - + update the all-instances configuration of a managed instance group + +SYNOPSIS + gcloud beta compute instance-groups managed all-instances-config update + NAME [--labels=KEY=VALUE,[KEY=VALUE,...]] + [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--region=REGION | --zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute instance-groups managed all-instances-config + update updates the group's all-instances configuration and applies it only + to new instances that are added to the group. + + To apply a revised all-instances configuration to existing instances in the + group, use one of the following methods: + + ▪ Update instances using the update-instances command. + ▪ Recreate instances using the recreate-instances command. + ▪ Use the rolling-action start-update command. + ▪ Use the API to set the group's updatePolicy.type to PROACTIVE. + +EXAMPLES + To update an all-instances configuration in order to override the group's + instance template for a label with the key label-key and metadata with the + key metadata-key in group my-group, run: + + $ gcloud beta compute instance-groups managed all-instances-config \ + update my-group \ + --metadata=metadata-key=metadata-override-value \ + --labels=qlabel-key=label-override-value + +POSITIONAL ARGUMENTS + NAME + Name of the managed instance group to update the all instances + configuration for. + +FLAGS + --labels=KEY=VALUE,[KEY=VALUE,...] + Add labels to the group's all instances configuration. + + --metadata=KEY=VALUE,[KEY=VALUE,...] + Add metadata to the group's all instances configuration. + + At most one of these can be specified: + + --region=REGION + Region of the managed instance group to update the all instances + configuration for. If not specified, you might be prompted to select + a region (interactive mode only). + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + Overrides the default compute/region property value for this command + invocation. + + --zone=ZONE + Zone of the managed instance group to update the all instances + configuration for. If not specified, you might be prompted to select + a zone (interactive mode only). + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute instance-groups managed \ + all-instances-config update + diff --git a/gcloud/beta/compute/instance-groups/managed/help b/gcloud/beta/compute/instance-groups/managed/help index 61c8662ed..4928da7a1 100644 --- a/gcloud/beta/compute/instance-groups/managed/help +++ b/gcloud/beta/compute/instance-groups/managed/help @@ -17,6 +17,10 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + all-instances-config + (BETA) Override instance template settings for all instances in a + managed instance group. + instance-configs (BETA) Manage instance-specific settings in a managed instance group. diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index 781a71995..cc82c351b 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -36,6 +36,7 @@ SYNOPSIS [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--source-instance-template=SOURCE_INSTANCE_TEMPLATE] [--subnet=SUBNET] [--tags=TAG,[TAG,...]] + [--target-distribution-shape=SHAPE] [--threads-per-core=THREADS_PER_CORE] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY : --boot-disk-kms-keyring=BOOT_DISK_KMS_KEYRING @@ -649,6 +650,25 @@ OPTIONAL FLAGS $ gcloud compute instances list --filter='tags:tag1' + --target-distribution-shape=SHAPE + Specifies whether and how to distribute VMs across multiple zones in a + region or to enforce placement of VMs in a single zone. The default + shape is ANY_SINGLE_ZONE. SHAPE must be one of: + + ANY + Allows creating VMs in multiple zones if one zone cannot + accommodate all the requested VMs. The resulting distribution + shapes can vary. + ANY_SINGLE_ZONE + Enforces VM placement in one allowed zone. Use this to avoid + cross-zone network egress or to reduce network latency. This is the + default value. + BALANCED + Allows distribution of VMs in zones where resources are available + while distributing VMs as evenly as possible across selected zones + to minimize the impact of zonal failures. Recommended for highly + available serving or batch workloads. + --threads-per-core=THREADS_PER_CORE The number of visible threads per physical core. To disable simultaneous multithreading (SMT) set this to 1. Valid values are: 1 or diff --git a/gcloud/beta/compute/instances/ops-agents/policies/create b/gcloud/beta/compute/instances/ops-agents/policies/create index f2e3cec45..edb44cc3d 100644 --- a/gcloud/beta/compute/instances/ops-agents/policies/create +++ b/gcloud/beta/compute/instances/ops-agents/policies/create @@ -242,6 +242,7 @@ REQUIRED FLAGS ubuntu 20.04 ubuntu 21.04 ubuntu 21.10 + ubuntu 22.04 windows 10.* windows 6.* diff --git a/gcloud/beta/compute/instances/ops-agents/policies/update b/gcloud/beta/compute/instances/ops-agents/policies/update index 2a8217594..480be561c 100644 --- a/gcloud/beta/compute/instances/ops-agents/policies/update +++ b/gcloud/beta/compute/instances/ops-agents/policies/update @@ -279,6 +279,7 @@ FLAGS ubuntu 20.04 ubuntu 21.04 ubuntu 21.10 + ubuntu 22.04 windows 10.* windows 6.* diff --git a/gcloud/beta/compute/ssl-policies/create b/gcloud/beta/compute/ssl-policies/create index 41feb704c..3602a5e38 100644 --- a/gcloud/beta/compute/ssl-policies/create +++ b/gcloud/beta/compute/ssl-policies/create @@ -6,7 +6,8 @@ SYNOPSIS gcloud beta compute ssl-policies create SSL_POLICY [--custom-features=[CUSTOM_FEATURES,...]] [--description=DESCRIPTION] [--min-tls-version=MIN_TLS_VERSION; default="1.0"] - [--profile=PROFILE; default="COMPATIBLE"] [GCLOUD_WIDE_FLAG ...] + [--profile=PROFILE; default="COMPATIBLE"] [--global | --region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute ssl-policies create creates a new SSL policy. @@ -69,6 +70,15 @@ FLAGS Restricted profile. Supports a reduced set of SSL features, intended to meet stricter compliance requirements. + At most one of these can be specified: + + --global + If set, the SSL policy is global. + + --region=REGION + Region of the SSL policy to create. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/ssl-policies/delete b/gcloud/beta/compute/ssl-policies/delete index a20091151..876e48d75 100644 --- a/gcloud/beta/compute/ssl-policies/delete +++ b/gcloud/beta/compute/ssl-policies/delete @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta compute ssl-policies delete SSL_POLICY [SSL_POLICY ...] - [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute ssl-policies delete is used to delete one or @@ -22,6 +22,16 @@ POSITIONAL ARGUMENTS SSL_POLICY [SSL_POLICY ...] Names of the SSL policies to delete. +FLAGS + At most one of these can be specified: + + --global + If set, the SSL policies are global. + + --region=REGION + Region of the SSL policies to delete. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/ssl-policies/describe b/gcloud/beta/compute/ssl-policies/describe index d09af3551..41dfebfdc 100644 --- a/gcloud/beta/compute/ssl-policies/describe +++ b/gcloud/beta/compute/ssl-policies/describe @@ -3,7 +3,8 @@ NAME policy SYNOPSIS - gcloud beta compute ssl-policies describe SSL_POLICY [GCLOUD_WIDE_FLAG ...] + gcloud beta compute ssl-policies describe SSL_POLICY + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute ssl-policies describe is used to display all @@ -19,6 +20,16 @@ POSITIONAL ARGUMENTS SSL_POLICY Name of the SSL policy to describe. +FLAGS + At most one of these can be specified: + + --global + If set, the SSL policy is global. + + --region=REGION + Region of the SSL policy to describe. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/ssl-policies/list b/gcloud/beta/compute/ssl-policies/list index 40575e137..e37dad5d2 100644 --- a/gcloud/beta/compute/ssl-policies/list +++ b/gcloud/beta/compute/ssl-policies/list @@ -3,14 +3,19 @@ NAME policies SYNOPSIS - gcloud beta compute ssl-policies list [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud beta compute ssl-policies list [NAME ...] + [--regexp=REGEXP, -r REGEXP] [--global | --regions=[REGION,...]] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute ssl-policies list displays all Google Compute Engine SSL policies in a project. + By default, global SSL policies and SSL policies from all regions are + listed. The results can be narrowed down by providing the --global or + --regions flag. + EXAMPLES To list all SSL policies in a project in table form, run: @@ -20,6 +25,41 @@ EXAMPLES $ gcloud beta compute ssl-policies list --uri + To list all global SSL policies in a project, run: + + $ gcloud beta compute ssl-policies list --global + + To list all SSL policies in the us-central1 and europe-west1 regions, given + they are regional resources, run: + + $ gcloud beta compute ssl-policies list \ + --filter="region:( europe-west1 us-central1 )" + +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. + + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. + +FLAGS + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. + + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + + At most one of these can be specified: + + --global + If provided, only global resources are shown. + + --regions=[REGION,...] + If provided, only regional resources are shown. If arguments are + provided, only resources from the given regions are shown. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/compute/ssl-policies/list-available-features b/gcloud/beta/compute/ssl-policies/list-available-features index 921ad6018..f37dbcd19 100644 --- a/gcloud/beta/compute/ssl-policies/list-available-features +++ b/gcloud/beta/compute/ssl-policies/list-available-features @@ -3,7 +3,7 @@ NAME features that can be specified in an SSL policy SYNOPSIS - gcloud beta compute ssl-policies list-available-features + gcloud beta compute ssl-policies list-available-features [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -18,6 +18,10 @@ DESCRIPTION balancer. SSL policies do not affect the connection between the load balancers and the backends. +FLAGS + --region=REGION + If provided, only features for the given region are shown. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/compute/ssl-policies/update b/gcloud/beta/compute/ssl-policies/update index 8138e8bd5..c3004529c 100644 --- a/gcloud/beta/compute/ssl-policies/update +++ b/gcloud/beta/compute/ssl-policies/update @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta compute ssl-policies update SSL_POLICY [--custom-features=[CUSTOM_FEATURES,...]] [--min-tls-version=MIN_TLS_VERSION] [--profile=PROFILE] - [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute ssl-policies update is used to update SSL @@ -67,6 +67,15 @@ FLAGS Restricted profile. Supports a reduced set of SSL features, intended to meet stricter compliance requirements. + At most one of these can be specified: + + --global + If set, the SSL policy is global. + + --region=REGION + Region of the SSL policy to patch. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/target-https-proxies/create b/gcloud/beta/compute/target-https-proxies/create index b35bc84e6..1169ba5da 100644 --- a/gcloud/beta/compute/target-https-proxies/create +++ b/gcloud/beta/compute/target-https-proxies/create @@ -10,6 +10,7 @@ SYNOPSIS [--global | --region=REGION] [--global-ssl-certificates | --ssl-certificates-region=SSL_CERTIFICATES_REGION] + [--global-ssl-policy | --ssl-policy-region=SSL_POLICY_REGION] [--global-url-map | --url-map-region=URL_MAP_REGION] [GCLOUD_WIDE_FLAG ...] @@ -145,6 +146,15 @@ OPTIONAL FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + At most one of these can be specified: + + --global-ssl-policy + If set, the SSL policy is global. + + --ssl-policy-region=SSL_POLICY_REGION + Region of the SSL policy to operate on. Overrides the default + compute/region property value for this command invocation. + At most one of these can be specified: --global-url-map diff --git a/gcloud/beta/compute/target-https-proxies/update b/gcloud/beta/compute/target-https-proxies/update index b3b4e39f7..f5fef2175 100644 --- a/gcloud/beta/compute/target-https-proxies/update +++ b/gcloud/beta/compute/target-https-proxies/update @@ -8,8 +8,8 @@ SYNOPSIS [[--certificate-map=CERTIFICATE_MAP : --clear-certificate-map] | --ssl-certificates=SSL_CERTIFICATE,[...] --global-ssl-certificates | --ssl-certificates-region=SSL_CERTIFICATES_REGION] - [--clear-ssl-policy | --ssl-policy=SSL_POLICY] - [--global | --region=REGION] + [--clear-ssl-policy | --ssl-policy=SSL_POLICY --global-ssl-policy + | --ssl-policy-region=SSL_POLICY_REGION] [--global | --region=REGION] [--global-url-map | --url-map-region=URL_MAP_REGION] [GCLOUD_WIDE_FLAG ...] @@ -136,6 +136,15 @@ FLAGS and the HTTPS proxy load balancer. The SSL policy must exist and cannot be deleted while referenced by a target HTTPS proxy. + At most one of these can be specified: + + --global-ssl-policy + If set, the SSL policy is global. + + --ssl-policy-region=SSL_POLICY_REGION + Region of the SSL policy to operate on. Overrides the default + compute/region property value for this command invocation. + At most one of these can be specified: --global diff --git a/gcloud/beta/compute/target-ssl-proxies/create b/gcloud/beta/compute/target-ssl-proxies/create index a0089ab90..15cccd4d3 100644 --- a/gcloud/beta/compute/target-ssl-proxies/create +++ b/gcloud/beta/compute/target-ssl-proxies/create @@ -8,6 +8,7 @@ SYNOPSIS : --ssl-certificates=SSL_CERTIFICATE,[...]) [--description=DESCRIPTION] [--proxy-header=PROXY_HEADER; default="NONE"] [--ssl-policy=SSL_POLICY] + [--global-ssl-policy | --ssl-policy-region=SSL_POLICY_REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -74,6 +75,15 @@ OPTIONAL FLAGS and the SSL proxy load balancer. The SSL policy must exist and cannot be deleted while referenced by a target SSL proxy. + At most one of these can be specified: + + --global-ssl-policy + If set, the SSL policy is global. + + --ssl-policy-region=SSL_POLICY_REGION + Region of the SSL policy to operate on. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/target-ssl-proxies/update b/gcloud/beta/compute/target-ssl-proxies/update index 85c82cc25..ac07055b1 100644 --- a/gcloud/beta/compute/target-ssl-proxies/update +++ b/gcloud/beta/compute/target-ssl-proxies/update @@ -7,7 +7,8 @@ SYNOPSIS [--certificate-map=CERTIFICATE_MAP : --ssl-certificates=SSL_CERTIFICATE,[...] | --clear-ssl-certificates | --clear-certificate-map] - [--clear-ssl-policy | --ssl-policy=SSL_POLICY] [GCLOUD_WIDE_FLAG ...] + [--clear-ssl-policy | --ssl-policy=SSL_POLICY --global-ssl-policy + | --ssl-policy-region=SSL_POLICY_REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute target-ssl-proxies update is used to replace the @@ -81,6 +82,15 @@ FLAGS and the SSL proxy load balancer. The SSL policy must exist and cannot be deleted while referenced by a target SSL proxy. + At most one of these can be specified: + + --global-ssl-policy + If set, the SSL policy is global. + + --ssl-policy-region=SSL_POLICY_REGION + Region of the SSL policy to operate on. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/target-tcp-proxies/create b/gcloud/beta/compute/target-tcp-proxies/create index 711f86c52..6d3865bef 100644 --- a/gcloud/beta/compute/target-tcp-proxies/create +++ b/gcloud/beta/compute/target-tcp-proxies/create @@ -5,6 +5,8 @@ SYNOPSIS gcloud beta compute target-tcp-proxies create NAME --backend-service=BACKEND_SERVICE [--description=DESCRIPTION] [--[no-]proxy-bind] [--proxy-header=PROXY_HEADER; default="NONE"] + [--backend-service-region=BACKEND_SERVICE_REGION + | --global-backend-service] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -51,6 +53,41 @@ OPTIONAL FLAGS Enables PROXY protocol (version 1) for passing client connection information. + At most one of these can be specified: + + --backend-service-region=BACKEND_SERVICE_REGION + Region of the backend service to operate on. If not specified it will + be set to the region of the TCP Proxy. Overrides the default + compute/region property value for this command invocation. + + --global-backend-service + If set, the backend service is global. + + At most one of these can be specified: + + --global + If set, the target TCP proxy is global. + + --region=REGION + Region of the target TCP proxy to create. If not specified, you might + be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/target-tcp-proxies/delete b/gcloud/beta/compute/target-tcp-proxies/delete index a3c880f49..b9e14651d 100644 --- a/gcloud/beta/compute/target-tcp-proxies/delete +++ b/gcloud/beta/compute/target-tcp-proxies/delete @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud beta compute target-tcp-proxies delete NAME [NAME ...] - [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute target-tcp-proxies delete deletes one or more @@ -13,6 +13,32 @@ POSITIONAL ARGUMENTS NAME [NAME ...] Names of the target TCP proxies to delete. +FLAGS + At most one of these can be specified: + + --global + If set, the target TCP proxies are global. + + --region=REGION + Region of the target TCP proxies to delete. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/target-tcp-proxies/describe b/gcloud/beta/compute/target-tcp-proxies/describe index 76458a2f5..932aca7b7 100644 --- a/gcloud/beta/compute/target-tcp-proxies/describe +++ b/gcloud/beta/compute/target-tcp-proxies/describe @@ -3,7 +3,8 @@ NAME information about a target TCP proxy SYNOPSIS - gcloud beta compute target-tcp-proxies describe NAME [GCLOUD_WIDE_FLAG ...] + gcloud beta compute target-tcp-proxies describe NAME + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute target-tcp-proxies describe displays all data @@ -13,6 +14,32 @@ POSITIONAL ARGUMENTS NAME Name of the target TCP proxy to describe. +FLAGS + At most one of these can be specified: + + --global + If set, the target TCP proxy is global. + + --region=REGION + Region of the target TCP proxy to describe. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/target-tcp-proxies/list b/gcloud/beta/compute/target-tcp-proxies/list index 19ead23ce..b588979b8 100644 --- a/gcloud/beta/compute/target-tcp-proxies/list +++ b/gcloud/beta/compute/target-tcp-proxies/list @@ -3,14 +3,19 @@ NAME target TCP proxies SYNOPSIS - gcloud beta compute target-tcp-proxies list [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud beta compute target-tcp-proxies list [NAME ...] + [--regexp=REGEXP, -r REGEXP] [--global | --regions=[REGION,...]] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute target-tcp-proxies list displays all Google Compute Engine target TCP proxies in a project. + By default, global target TCP proxies and target TCP proxies from all + regions are listed. The results can be narrowed down by providing the + --global or --regions flag. + EXAMPLES To list all target TCP proxies in a project in table form, run: @@ -20,6 +25,41 @@ EXAMPLES $ gcloud beta compute target-tcp-proxies list --uri + To list all global target TCP proxies in a project, run: + + $ gcloud beta compute target-tcp-proxies list --global + + To list all target TCP proxies in the us-central1 and europe-west1 regions, + given they are regional resources, run: + + $ gcloud beta compute target-tcp-proxies list \ + --filter="region:( europe-west1 us-central1 )" + +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. + + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. + +FLAGS + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. + + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + + At most one of these can be specified: + + --global + If provided, only global resources are shown. + + --regions=[REGION,...] + If provided, only regional resources are shown. If arguments are + provided, only resources from the given regions are shown. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/dataproc/jobs/submit/hadoop b/gcloud/beta/dataproc/jobs/submit/hadoop index 974eb7bfe..a47b0353a 100644 --- a/gcloud/beta/dataproc/jobs/submit/hadoop +++ b/gcloud/beta/dataproc/jobs/submit/hadoop @@ -10,8 +10,8 @@ SYNOPSIS [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] DESCRIPTION (BETA) Submit a Hadoop job to a cluster. @@ -111,6 +111,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hadoop. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/beta/dataproc/jobs/submit/hive b/gcloud/beta/dataproc/jobs/submit/hive index 2ab5a099c..8ddda3129 100644 --- a/gcloud/beta/dataproc/jobs/submit/hive +++ b/gcloud/beta/dataproc/jobs/submit/hive @@ -9,8 +9,8 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] [--params=[PARAM=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Submit a Hive job to a cluster. @@ -89,6 +89,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hive. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/beta/dataproc/jobs/submit/pig b/gcloud/beta/dataproc/jobs/submit/pig index 54cf8eeab..46b21cd4f 100644 --- a/gcloud/beta/dataproc/jobs/submit/pig +++ b/gcloud/beta/dataproc/jobs/submit/pig @@ -10,8 +10,8 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] [--params=[PARAM=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Submit a Pig job to a cluster. @@ -97,6 +97,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Pig. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/beta/dataproc/jobs/submit/presto b/gcloud/beta/dataproc/jobs/submit/presto index c69f450d4..eeda57806 100644 --- a/gcloud/beta/dataproc/jobs/submit/presto +++ b/gcloud/beta/dataproc/jobs/submit/presto @@ -10,7 +10,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PARAM=VALUE,...]] + [--properties=[PARAM=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--query-output-format=QUERY_OUTPUT_FORMAT] [--region=REGION] [GCLOUD_WIDE_FLAG ...] @@ -90,6 +90,23 @@ OPTIONAL FLAGS --properties=[PARAM=VALUE,...] A list of key value pairs to set Presto session properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --query-output-format=QUERY_OUTPUT_FORMAT The query output display format. See the Presto documentation for supported output formats. diff --git a/gcloud/beta/dataproc/jobs/submit/pyspark b/gcloud/beta/dataproc/jobs/submit/pyspark index fd1ce3331..85d067362 100644 --- a/gcloud/beta/dataproc/jobs/submit/pyspark +++ b/gcloud/beta/dataproc/jobs/submit/pyspark @@ -10,8 +10,9 @@ SYNOPSIS [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PROPERTY=VALUE,...]] [--py-files=[PY_FILE,...]] - [--region=REGION] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--py-files=[PY_FILE,...]] [--region=REGION] [GCLOUD_WIDE_FLAG ...] + [-- JOB_ARGS ...] DESCRIPTION (BETA) Submit a PySpark job to a cluster. @@ -102,6 +103,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --py-files=[PY_FILE,...] Comma separated list of Python files to be provided to the job. Must be one of the following file formats ".py, .zip, or .egg". diff --git a/gcloud/beta/dataproc/jobs/submit/spark b/gcloud/beta/dataproc/jobs/submit/spark index dfd6e77cf..3196a42ee 100644 --- a/gcloud/beta/dataproc/jobs/submit/spark +++ b/gcloud/beta/dataproc/jobs/submit/spark @@ -10,8 +10,8 @@ SYNOPSIS [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] DESCRIPTION (BETA) Submit a Spark job to a cluster. @@ -114,6 +114,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/beta/dataproc/jobs/submit/spark-r b/gcloud/beta/dataproc/jobs/submit/spark-r index f65150640..3ebc898dd 100644 --- a/gcloud/beta/dataproc/jobs/submit/spark-r +++ b/gcloud/beta/dataproc/jobs/submit/spark-r @@ -9,8 +9,8 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] DESCRIPTION (BETA) Submit a SparkR job to a cluster. @@ -96,6 +96,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/beta/dataproc/jobs/submit/spark-sql b/gcloud/beta/dataproc/jobs/submit/spark-sql index f804c73c6..da430f95c 100644 --- a/gcloud/beta/dataproc/jobs/submit/spark-sql +++ b/gcloud/beta/dataproc/jobs/submit/spark-sql @@ -10,8 +10,8 @@ SYNOPSIS [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] [--params=[PARAM=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Submit a Spark SQL job to a cluster. @@ -91,6 +91,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hive. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/beta/dataproc/workflow-templates/add-job/hadoop b/gcloud/beta/dataproc/workflow-templates/add-job/hadoop index dc62d3802..0f0ceb67e 100644 --- a/gcloud/beta/dataproc/workflow-templates/add-job/hadoop +++ b/gcloud/beta/dataproc/workflow-templates/add-job/hadoop @@ -8,7 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] @@ -104,6 +104,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hadoop. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/beta/dataproc/workflow-templates/add-job/hive b/gcloud/beta/dataproc/workflow-templates/add-job/hive index 3fea3c150..6182514e7 100644 --- a/gcloud/beta/dataproc/workflow-templates/add-job/hive +++ b/gcloud/beta/dataproc/workflow-templates/add-job/hive @@ -8,6 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--continue-on-failure] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--params=[PARAM=VALUE,...]] [--properties=[PROPERTY=VALUE,...]] + [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -86,6 +87,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hive. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/beta/dataproc/workflow-templates/add-job/pig b/gcloud/beta/dataproc/workflow-templates/add-job/pig index 05ee0c240..2c029c513 100644 --- a/gcloud/beta/dataproc/workflow-templates/add-job/pig +++ b/gcloud/beta/dataproc/workflow-templates/add-job/pig @@ -9,6 +9,7 @@ SYNOPSIS [--continue-on-failure] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--params=[PARAM=VALUE,...]] [--properties=[PROPERTY=VALUE,...]] + [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -91,6 +92,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Pig. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/beta/dataproc/workflow-templates/add-job/presto b/gcloud/beta/dataproc/workflow-templates/add-job/presto index 09092e6e0..82dcb502b 100644 --- a/gcloud/beta/dataproc/workflow-templates/add-job/presto +++ b/gcloud/beta/dataproc/workflow-templates/add-job/presto @@ -8,7 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--client-tags=[CLIENT_TAG,...]] [--continue-on-failure] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PARAM=VALUE,...]] + [--properties=[PARAM=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--query-output-format=QUERY_OUTPUT_FORMAT] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] @@ -89,6 +89,23 @@ OPTIONAL FLAGS --properties=[PARAM=VALUE,...] A list of key value pairs to set Presto session properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --query-output-format=QUERY_OUTPUT_FORMAT The query output display format. See the Presto documentation for supported output formats. diff --git a/gcloud/beta/dataproc/workflow-templates/add-job/pyspark b/gcloud/beta/dataproc/workflow-templates/add-job/pyspark index 421eeb6b4..8cdb70894 100644 --- a/gcloud/beta/dataproc/workflow-templates/add-job/pyspark +++ b/gcloud/beta/dataproc/workflow-templates/add-job/pyspark @@ -8,9 +8,9 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] [--py-files=[PY_FILE,...]] - [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] - [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--py-files=[PY_FILE,...]] [--start-after=STEP_ID,[STEP_ID,...]] + [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] DESCRIPTION (BETA) Add a PySpark job to the workflow template. @@ -100,6 +100,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --py-files=[PY_FILE,...] Comma separated list of Python files to be provided to the job. Must be one of the following file formats ".py, .zip, or .egg". diff --git a/gcloud/beta/dataproc/workflow-templates/add-job/spark b/gcloud/beta/dataproc/workflow-templates/add-job/spark index 56a80c794..55b6c17c6 100644 --- a/gcloud/beta/dataproc/workflow-templates/add-job/spark +++ b/gcloud/beta/dataproc/workflow-templates/add-job/spark @@ -7,7 +7,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [--class=MAIN_CLASS --jar=MAIN_JAR] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] @@ -96,6 +96,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/beta/dataproc/workflow-templates/add-job/spark-r b/gcloud/beta/dataproc/workflow-templates/add-job/spark-r index 7be84c547..57eedafba 100644 --- a/gcloud/beta/dataproc/workflow-templates/add-job/spark-r +++ b/gcloud/beta/dataproc/workflow-templates/add-job/spark-r @@ -8,7 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] @@ -96,6 +96,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/beta/dataproc/workflow-templates/add-job/spark-sql b/gcloud/beta/dataproc/workflow-templates/add-job/spark-sql index 289dd09a1..b0651186a 100644 --- a/gcloud/beta/dataproc/workflow-templates/add-job/spark-sql +++ b/gcloud/beta/dataproc/workflow-templates/add-job/spark-sql @@ -8,7 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--driver-log-levels=[PACKAGE=LEVEL,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--params=[PARAM=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -88,6 +88,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hive. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/beta/functions/deploy b/gcloud/beta/functions/deploy index 442d241ba..727f02b55 100644 --- a/gcloud/beta/functions/deploy +++ b/gcloud/beta/functions/deploy @@ -38,10 +38,11 @@ SYNOPSIS /secret_path=SECRET_VALUE_REF, /mount_path:/secret_file_path=SECRET_VALUE_REF,...]] [--clear-vpc-connector | --vpc-connector=VPC_CONNECTOR] - [--trigger-bucket=TRIGGER_BUCKET - | --trigger-event-filters=[ATTRIBUTE=VALUE,...] | --trigger-http + [--trigger-bucket=TRIGGER_BUCKET | --trigger-http | --trigger-topic=TRIGGER_TOPIC - | --trigger-event=EVENT_TYPE --trigger-resource=RESOURCE] + | --trigger-event=EVENT_TYPE --trigger-resource=RESOURCE + | --trigger-event-filters=[ATTRIBUTE=VALUE,...] + --trigger-event-filters-path-pattern=[ATTRIBUTE=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -548,11 +549,6 @@ FLAGS Google Cloud Storage bucket name. Every change in files in this bucket will trigger function execution. - --trigger-event-filters=[ATTRIBUTE=VALUE,...] - The Eventarc matching criteria for the trigger. The criteria can be - specified either as a single comma-separated argument or as multiple - arguments. This is only relevant when --gen2 is provided. - --trigger-http Function will be assigned an endpoint, which you can view by using the describe command. Any HTTP request (of a supported type) to the @@ -578,6 +574,17 @@ FLAGS must be a bucket name. For a list of expected resources, call gcloud functions event-types list. + --trigger-event-filters=[ATTRIBUTE=VALUE,...] + The Eventarc matching criteria for the trigger. The criteria can be + specified either as a single comma-separated argument or as multiple + arguments. This is only relevant when --gen2 is provided. + + --trigger-event-filters-path-pattern=[ATTRIBUTE=VALUE,...] + The Eventarc matching criteria for the trigger in path pattern + format. The criteria can be specified as a single comma-separated + argument or as multiple arguments. This is only relevant when --gen2 + is provided. + 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/monitoring/help b/gcloud/beta/monitoring/help index 1cdc8fdf2..0d2cff25e 100644 --- a/gcloud/beta/monitoring/help +++ b/gcloud/beta/monitoring/help @@ -30,6 +30,9 @@ GROUPS dashboards (BETA) Manage Cloud Monitoring dashboards. + metrics-scopes + (BETA) Manage Cloud Monitoring Metrics Scopes. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/monitoring/metrics-scopes/create b/gcloud/beta/monitoring/metrics-scopes/create new file mode 100644 index 000000000..4bec834b8 --- /dev/null +++ b/gcloud/beta/monitoring/metrics-scopes/create @@ -0,0 +1,52 @@ +NAME + gcloud beta monitoring metrics-scopes create - create a monitored project + in a metrics scope + +SYNOPSIS + gcloud beta monitoring metrics-scopes create MONITORED_PROJECT_ID_OR_NUMBER + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The projects specified do not exist. + ▪ The active account does not have permission to access one of the + given project. + ▪ The monitored project already exists in the metrics scope. + + More details can be found at + https://cloud.google.com/monitoring/api/ref_v3/rest/v1/locations.global.metricsScopes.projects/create + +EXAMPLES + The following command adds a monitored project with the ID + monitored-project-1 to a metrics scope with project id metrics-scope-1 + assuming the metrics-scope-1 is the default project: + + $ gcloud beta monitoring metrics-scopes create monitored-project-1 + + The following command adds a monitored project with the ID + monitored-project-1 to a metrics scope with project id metrics-scope-1: + + $ gcloud beta monitoring metrics-scopes create monitored-project-1 \ + --project=metrics-scope-1 + $ gcloud beta monitoring metrics-scopes create \ + locations/global/metricsScopes/metrics-scope-1/projects/\ + monitored-project-1 + +POSITIONAL ARGUMENTS + MONITORED_PROJECT_ID_OR_NUMBER + Monitored project ID or number for the project you want to create. + +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 monitoring metrics-scopes create + diff --git a/gcloud/beta/monitoring/metrics-scopes/delete b/gcloud/beta/monitoring/metrics-scopes/delete new file mode 100644 index 000000000..22badb43c --- /dev/null +++ b/gcloud/beta/monitoring/metrics-scopes/delete @@ -0,0 +1,51 @@ +NAME + gcloud beta monitoring metrics-scopes delete - delete a monitored project + in a metrics scope + +SYNOPSIS + gcloud beta monitoring metrics-scopes delete MONITORED_PROJECT_ID_OR_NUMBER + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The projects specified do not exist. + ▪ The active account does not have permission to access one of the + given project. + + More details can be found at + https://cloud.google.com/monitoring/api/ref_v3/rest/v1/locations.global.metricsScopes.projects/delete + +EXAMPLES + The following command adds a monitored project with the ID + monitored-project-1 to a metrics scope with project id metrics-scope-1 + assuming the metrics-scope-1 is the default project: + + $ gcloud beta monitoring metrics-scopes delete monitored-project-1 + + The following command adds a monitored project with the ID + monitored-project-1 to a metrics scope with project id metrics-scope-1: + + $ gcloud beta monitoring metrics-scopes delete monitored-project-1 \ + --project=metrics-scope-1 + $ gcloud beta monitoring metrics-scopes delete \ + locations/global/metricsScopes/metrics-scope-1/projects/\ + monitored-project-1 + +POSITIONAL ARGUMENTS + MONITORED_PROJECT_ID_OR_NUMBER + Monitored project ID or number for the project you want to delete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha monitoring metrics-scopes delete + diff --git a/gcloud/beta/monitoring/metrics-scopes/describe b/gcloud/beta/monitoring/metrics-scopes/describe new file mode 100644 index 000000000..3822c1de8 --- /dev/null +++ b/gcloud/beta/monitoring/metrics-scopes/describe @@ -0,0 +1,60 @@ +NAME + gcloud beta monitoring metrics-scopes describe - describe a Cloud + Monitoring metrics scope + +SYNOPSIS + gcloud beta monitoring metrics-scopes describe METRICS_SCOPE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Cloud Monitoring metrics scope along with the list of + projects it is monitoring. + + More details can be found at + https://cloud.google.com/monitoring/api/ref_v3/rest/v1/locations.global.metricsScopes/get + +EXAMPLES + To describe a metrics scope contained within a specific project, run: + + $ gcloud beta monitoring metrics-scopes describe \ + MY-METRICS-SCOPE-PROJECT-ID + + To describe a metrics scope in JSON, run: + + $ gcloud beta monitoring metrics-scopes describe \ + MY-METRICS-SCOPE-PROJECT-ID --format=json + + To describe a metrics scope with a fully qualified metrics scope ID, run: + + $ gcloud beta monitoring metrics-scopes describe \ + locations/global/metricsScopes/MY-METRICS-SCOPE-PROJECT-ID + +POSITIONAL ARGUMENTS + Metrics scope resource - The metrics scope to describe. This represents a + Cloud resource. + + This must be specified. + + METRICS_SCOPE + ID of the metrics_scope or fully qualified identifier for the + metrics_scope. To set the metrics_scope attribute: + ▸ provide the argument metrics_scope 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 monitoring/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha monitoring metrics-scopes describe + diff --git a/gcloud/beta/monitoring/metrics-scopes/help b/gcloud/beta/monitoring/metrics-scopes/help new file mode 100644 index 000000000..9e174c2cd --- /dev/null +++ b/gcloud/beta/monitoring/metrics-scopes/help @@ -0,0 +1,40 @@ +NAME + gcloud beta monitoring metrics-scopes - manage Cloud Monitoring Metrics + Scopes + +SYNOPSIS + gcloud beta monitoring metrics-scopes COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The gcloud beta monitoring metrics-scopes group lets you manage + Monitoring metrics scopes. + + More information on managing metrics scopes can be found here: + https://cloud.google.com/monitoring/settings/manage-api + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a monitored project in a metrics scope. + + delete + (BETA) Delete a monitored project in a metrics scope. + + describe + (BETA) Describe a Cloud Monitoring metrics scope. + + list + (BETA) List the metrics scopes monitoring the specified project. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha monitoring metrics-scopes + diff --git a/gcloud/beta/monitoring/metrics-scopes/list b/gcloud/beta/monitoring/metrics-scopes/list new file mode 100644 index 000000000..d4f459098 --- /dev/null +++ b/gcloud/beta/monitoring/metrics-scopes/list @@ -0,0 +1,73 @@ +NAME + gcloud beta monitoring metrics-scopes list - list the metrics scopes + monitoring the specified project + +SYNOPSIS + gcloud beta monitoring metrics-scopes list PROJECT_ID_OR_NUMBER + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The projects specified do not exist. + ▪ The active account does not have permission to access one of the + given project. + + More details can be found at + https://cloud.google.com/monitoring/api/ref_v3/rest/v1/locations.global.metricsScopes/listMetricsScopesByMonitoredProject + +EXAMPLES + To list the metrics scopes monitoring MY-PROJECT-ID + + $ gcloud beta monitoring metrics-scopes list MY-PROJECT-ID + +POSITIONAL ARGUMENTS + PROJECT_ID_OR_NUMBER + ID or number for the project you want to 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. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha monitoring metrics-scopes list + diff --git a/gcloud/beta/pubsub/subscriptions/create b/gcloud/beta/pubsub/subscriptions/create index c00b7df1b..077c3612e 100644 --- a/gcloud/beta/pubsub/subscriptions/create +++ b/gcloud/beta/pubsub/subscriptions/create @@ -12,6 +12,8 @@ SYNOPSIS [--push-auth-service-account=SERVICE_ACCOUNT_EMAIL] [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] [--push-endpoint=PUSH_ENDPOINT] [--retain-acked-messages] + [--bigquery-table=BIGQUERY_TABLE + : --drop-unknown-fields --use-topic-schema --write-metadata] [--max-delivery-attempts=MAX_DELIVERY_ATTEMPTS [--dead-letter-topic=DEAD_LETTER_TOPIC : --dead-letter-topic-project=DEAD_LETTER_TOPIC_PROJECT]] @@ -133,6 +135,32 @@ OPTIONAL FLAGS --message-retention-duration window. Acknowledged messages are not retained by default. + BigQuery Config Options. The Cloud Pub/Sub service account associated with + the enclosing subscription's parent project (i.e., + service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have + permission to write to this BigQuery table. + + --bigquery-table=BIGQUERY_TABLE + A BigQuery table of the form {project}:{dataset_name}.{table_name} to + which to write messages for this subscription. + + This flag must be specified if any of the other arguments in this + group are specified. + + --drop-unknown-fields + When --use-topic-schema is set, whether or not to ignore fields in + the topic schema that do not appear in the BigQuery schema. If false, + then the BigQuery schema must contain all fields that are also + present in the topic schema. + + --use-topic-schema + Whether or not to use the schema for the subscription's topic (if it + exists) when writing messages to BigQuery. + + --write-metadata + Whether or not to write message metadata including message ID, + publish timestamp, ordering key, and attributes to BigQuery. + Dead Letter Queue Options. The Cloud Pub/Sub service account associated with the enclosing subscription's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have diff --git a/gcloud/beta/pubsub/subscriptions/update b/gcloud/beta/pubsub/subscriptions/update index 35f7c35b1..dcdbfec57 100644 --- a/gcloud/beta/pubsub/subscriptions/update +++ b/gcloud/beta/pubsub/subscriptions/update @@ -11,6 +11,8 @@ SYNOPSIS [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] [--push-endpoint=PUSH_ENDPOINT] [--retain-acked-messages] [--update-labels=[KEY=VALUE,...]] + [--clear-bigquery-config | [--bigquery-table=BIGQUERY_TABLE + : --drop-unknown-fields --use-topic-schema --write-metadata]] [--clear-dead-letter-policy | --max-delivery-attempts=MAX_DELIVERY_ATTEMPTS [--dead-letter-topic=DEAD_LETTER_TOPIC @@ -97,6 +99,37 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + At most one of these can be specified: + + --clear-bigquery-config + If set, clear the BigQuery config from the subscription. + + BigQuery Config Options. The Cloud Pub/Sub service account associated + with the enclosing subscription's parent project (i.e., + service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must + have permission to write to this BigQuery table. + + --bigquery-table=BIGQUERY_TABLE + A BigQuery table of the form {project}:{dataset_name}.{table_name} + to which to write messages for this subscription. + + This flag must be specified if any of the other arguments in this + group are specified. + + --drop-unknown-fields + When --use-topic-schema is set, whether or not to ignore fields in + the topic schema that do not appear in the BigQuery schema. If + false, then the BigQuery schema must contain all fields that are + also present in the topic schema. + + --use-topic-schema + Whether or not to use the schema for the subscription's topic (if + it exists) when writing messages to BigQuery. + + --write-metadata + Whether or not to write message metadata including message ID, + publish timestamp, ordering key, and attributes to BigQuery. + At most one of these can be specified: --clear-dead-letter-policy diff --git a/gcloud/builds/cancel b/gcloud/builds/cancel index f2c2dde39..c4c655cdb 100644 --- a/gcloud/builds/cancel +++ b/gcloud/builds/cancel @@ -25,7 +25,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/builds/describe b/gcloud/builds/describe index a0c562be4..5b2c3ffd2 100644 --- a/gcloud/builds/describe +++ b/gcloud/builds/describe @@ -21,7 +21,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/builds/list b/gcloud/builds/list index 87a912a72..d93f8e28f 100644 --- a/gcloud/builds/list +++ b/gcloud/builds/list @@ -25,7 +25,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/builds/log b/gcloud/builds/log index 1803cd6ee..15befd524 100644 --- a/gcloud/builds/log +++ b/gcloud/builds/log @@ -26,7 +26,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. --stream If a build is ongoing, stream the logs to stdout until the build diff --git a/gcloud/builds/submit b/gcloud/builds/submit index 936abf7a2..e95f2c37c 100644 --- a/gcloud/builds/submit +++ b/gcloud/builds/submit @@ -95,7 +95,7 @@ FLAGS --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, the global service - region is used. This field is restricted. + region is used. --substitutions=[KEY=VALUE,...] Parameters to be substituted in the build specification. diff --git a/gcloud/composer/environments/create b/gcloud/composer/environments/create index 15eb35dbf..150cc5441 100644 --- a/gcloud/composer/environments/create +++ b/gcloud/composer/environments/create @@ -17,6 +17,7 @@ SYNOPSIS --composer-network-ipv4-cidr=COMPOSER_NETWORK_IPV4_CIDR --connection-subnetwork=CONNECTION_SUBNETWORK --enable-private-endpoint --enable-private-environment + --enable-privately-used-public-ips --master-ipv4-cidr=MASTER_IPV4_CIDR --web-server-ipv4-cidr=WEB_SERVER_IPV4_CIDR] [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR @@ -204,7 +205,7 @@ FLAGS IPv4 CIDR range to use for the Cloud SQL network. This should have a size of the netmask not greater than 24. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. --composer-network-ipv4-cidr=COMPOSER_NETWORK_IPV4_CIDR @@ -212,7 +213,7 @@ FLAGS size of the netmask between 24 and 29. Can be specified for Composer 2.X or greater. Cannot be specified - unless '--enable-private-environment' is also specified. + unless --enable-private-environment is also specified. --connection-subnetwork=CONNECTION_SUBNETWORK Subnetwork from which an IP address for internal communications will @@ -221,7 +222,7 @@ FLAGS which the environment is connected. Can be specified for Composer 2.X or greater. Cannot be specified - unless '--enable-private-environment' is also specified. + unless --enable-private-environment is also specified. --enable-private-endpoint Environment cluster is managed using the private IP address of the @@ -231,7 +232,7 @@ FLAGS If not specified, the master API endpoint will be accessible by its public IP address. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. --enable-private-environment @@ -240,20 +241,28 @@ FLAGS If not specified, cluster nodes will be assigned public IP addresses. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. + + --enable-privately-used-public-ips + When enabled GKE pods and services may use public(non-RFC1918) IP + ranges privately. The ranges are specified by '--cluster-ipv4-cidr' + and --services-ipv4-cidr flags. + + Cannot be specified unless --enable-private-environment is also + specified. --master-ipv4-cidr=MASTER_IPV4_CIDR IPv4 CIDR range to use for the cluster master network. This should have a size of the netmask between 23 and 28. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. --web-server-ipv4-cidr=WEB_SERVER_IPV4_CIDR IPv4 CIDR range to use for the Airflow web server network. This should have a size of the netmask between 24 and 29. - Cannot be specified unless '--enable-private-environment' is also + Cannot be specified unless --enable-private-environment is also specified. IP Alias (VPC-native) @@ -262,14 +271,14 @@ FLAGS IP address range for the pods in this cluster in CIDR notation (e.g. 10.0.0.0/14). - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --cluster-secondary-range-name=CLUSTER_SECONDARY_RANGE_NAME Secondary range to be used as the source for pod IPs. Alias ranges will be allocated from this secondary range. NAME must be the name of an existing secondary range in the cluster subnetwork. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --enable-ip-alias Enable use of alias IPs @@ -287,13 +296,13 @@ FLAGS If unspecified, the services CIDR range will be chosen with a default mask size. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. --services-secondary-range-name=SERVICES_SECONDARY_RANGE_NAME Secondary range to be used for services (e.g. ClusterIPs). NAME must be the name of an existing secondary range in the cluster subnetwork. - Cannot be specified unless '--enable-ip-alias' is also specified. + Cannot be specified unless --enable-ip-alias is also specified. Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the environment. The 'Cloud Composer Service Agent' diff --git a/gcloud/compute/commitments/create b/gcloud/compute/commitments/create index 96446f5d7..d036f2303 100644 --- a/gcloud/compute/commitments/create +++ b/gcloud/compute/commitments/create @@ -88,7 +88,7 @@ OPTIONAL FLAGS for memory-optimized VMs. TYPE must be one of: accelerator-optimized, compute-optimized, compute-optimized-c2d, general-purpose, general-purpose-e2, general-purpose-n2, general-purpose-n2d, - general-purpose-t2d, memory-optimized. + general-purpose-t2d, memory-optimized, memory-optimized-m3. Manage the reservations to be created with the commitment. diff --git a/gcloud/dataproc/jobs/submit/hadoop b/gcloud/dataproc/jobs/submit/hadoop index d70227c1a..63fc9b99c 100644 --- a/gcloud/dataproc/jobs/submit/hadoop +++ b/gcloud/dataproc/jobs/submit/hadoop @@ -9,8 +9,8 @@ SYNOPSIS [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] DESCRIPTION Submit a Hadoop job to a cluster. @@ -110,6 +110,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hadoop. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/dataproc/jobs/submit/hive b/gcloud/dataproc/jobs/submit/hive index 707317244..52a31a85f 100644 --- a/gcloud/dataproc/jobs/submit/hive +++ b/gcloud/dataproc/jobs/submit/hive @@ -9,8 +9,8 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] [--params=[PARAM=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Submit a Hive job to a cluster. @@ -89,6 +89,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hive. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/dataproc/jobs/submit/pig b/gcloud/dataproc/jobs/submit/pig index 517cdbbe2..134f21977 100644 --- a/gcloud/dataproc/jobs/submit/pig +++ b/gcloud/dataproc/jobs/submit/pig @@ -10,8 +10,8 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] [--params=[PARAM=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Submit a Pig job to a cluster. @@ -97,6 +97,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Pig. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/dataproc/jobs/submit/presto b/gcloud/dataproc/jobs/submit/presto index 67e8b545d..d59e342c5 100644 --- a/gcloud/dataproc/jobs/submit/presto +++ b/gcloud/dataproc/jobs/submit/presto @@ -10,7 +10,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PARAM=VALUE,...]] + [--properties=[PARAM=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--query-output-format=QUERY_OUTPUT_FORMAT] [--region=REGION] [GCLOUD_WIDE_FLAG ...] @@ -90,6 +90,23 @@ OPTIONAL FLAGS --properties=[PARAM=VALUE,...] A list of key value pairs to set Presto session properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --query-output-format=QUERY_OUTPUT_FORMAT The query output display format. See the Presto documentation for supported output formats. diff --git a/gcloud/dataproc/jobs/submit/pyspark b/gcloud/dataproc/jobs/submit/pyspark index 17528ddfa..4ff56bed9 100644 --- a/gcloud/dataproc/jobs/submit/pyspark +++ b/gcloud/dataproc/jobs/submit/pyspark @@ -9,8 +9,9 @@ SYNOPSIS [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PROPERTY=VALUE,...]] [--py-files=[PY_FILE,...]] - [--region=REGION] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--py-files=[PY_FILE,...]] [--region=REGION] [GCLOUD_WIDE_FLAG ...] + [-- JOB_ARGS ...] DESCRIPTION Submit a PySpark job to a cluster. @@ -101,6 +102,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --py-files=[PY_FILE,...] Comma separated list of Python files to be provided to the job. Must be one of the following file formats ".py, .zip, or .egg". diff --git a/gcloud/dataproc/jobs/submit/spark b/gcloud/dataproc/jobs/submit/spark index 285db1ea5..23d1760ee 100644 --- a/gcloud/dataproc/jobs/submit/spark +++ b/gcloud/dataproc/jobs/submit/spark @@ -9,8 +9,8 @@ SYNOPSIS [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] DESCRIPTION Submit a Spark job to a cluster. @@ -113,6 +113,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/dataproc/jobs/submit/spark-r b/gcloud/dataproc/jobs/submit/spark-r index 523a210e3..f07b9aa3d 100644 --- a/gcloud/dataproc/jobs/submit/spark-r +++ b/gcloud/dataproc/jobs/submit/spark-r @@ -9,8 +9,8 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] DESCRIPTION Submit a SparkR job to a cluster. @@ -96,6 +96,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/dataproc/jobs/submit/spark-sql b/gcloud/dataproc/jobs/submit/spark-sql index 2ccc9f875..2c4f2da5f 100644 --- a/gcloud/dataproc/jobs/submit/spark-sql +++ b/gcloud/dataproc/jobs/submit/spark-sql @@ -9,8 +9,8 @@ SYNOPSIS [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--max-failures-total=MAX_FAILURES_TOTAL] [--params=[PARAM=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Submit a Spark SQL job to a cluster. @@ -90,6 +90,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hive. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --region=REGION Dataproc region to use. Each Dataproc region constitutes an independent resource namespace constrained to deploying instances into Compute diff --git a/gcloud/dataproc/workflow-templates/add-job/hadoop b/gcloud/dataproc/workflow-templates/add-job/hadoop index e8252d9f5..51e22724b 100644 --- a/gcloud/dataproc/workflow-templates/add-job/hadoop +++ b/gcloud/dataproc/workflow-templates/add-job/hadoop @@ -8,7 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] @@ -104,6 +104,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hadoop. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/dataproc/workflow-templates/add-job/hive b/gcloud/dataproc/workflow-templates/add-job/hive index a4b1744eb..b57d38a4f 100644 --- a/gcloud/dataproc/workflow-templates/add-job/hive +++ b/gcloud/dataproc/workflow-templates/add-job/hive @@ -8,6 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--continue-on-failure] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--params=[PARAM=VALUE,...]] [--properties=[PROPERTY=VALUE,...]] + [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -86,6 +87,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hive. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/dataproc/workflow-templates/add-job/pig b/gcloud/dataproc/workflow-templates/add-job/pig index 764a6a983..001252f50 100644 --- a/gcloud/dataproc/workflow-templates/add-job/pig +++ b/gcloud/dataproc/workflow-templates/add-job/pig @@ -9,6 +9,7 @@ SYNOPSIS [--continue-on-failure] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--params=[PARAM=VALUE,...]] [--properties=[PROPERTY=VALUE,...]] + [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -91,6 +92,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Pig. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/dataproc/workflow-templates/add-job/presto b/gcloud/dataproc/workflow-templates/add-job/presto index 4acf95d6a..663d99a6a 100644 --- a/gcloud/dataproc/workflow-templates/add-job/presto +++ b/gcloud/dataproc/workflow-templates/add-job/presto @@ -8,7 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--client-tags=[CLIENT_TAG,...]] [--continue-on-failure] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PARAM=VALUE,...]] + [--properties=[PARAM=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--query-output-format=QUERY_OUTPUT_FORMAT] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] @@ -89,6 +89,23 @@ OPTIONAL FLAGS --properties=[PARAM=VALUE,...] A list of key value pairs to set Presto session properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --query-output-format=QUERY_OUTPUT_FORMAT The query output display format. See the Presto documentation for supported output formats. diff --git a/gcloud/dataproc/workflow-templates/add-job/pyspark b/gcloud/dataproc/workflow-templates/add-job/pyspark index dc31daa90..58ee0f9dd 100644 --- a/gcloud/dataproc/workflow-templates/add-job/pyspark +++ b/gcloud/dataproc/workflow-templates/add-job/pyspark @@ -8,9 +8,9 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] [--py-files=[PY_FILE,...]] - [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] - [-- JOB_ARGS ...] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] + [--py-files=[PY_FILE,...]] [--start-after=STEP_ID,[STEP_ID,...]] + [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] DESCRIPTION Add a PySpark job to the workflow template. @@ -100,6 +100,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --py-files=[PY_FILE,...] Comma separated list of Python files to be provided to the job. Must be one of the following file formats ".py, .zip, or .egg". diff --git a/gcloud/dataproc/workflow-templates/add-job/spark b/gcloud/dataproc/workflow-templates/add-job/spark index 5f45d0214..1c902d986 100644 --- a/gcloud/dataproc/workflow-templates/add-job/spark +++ b/gcloud/dataproc/workflow-templates/add-job/spark @@ -7,7 +7,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [--class=MAIN_CLASS --jar=MAIN_JAR] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] @@ -96,6 +96,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/dataproc/workflow-templates/add-job/spark-r b/gcloud/dataproc/workflow-templates/add-job/spark-r index 2c986afa3..265f7c290 100644 --- a/gcloud/dataproc/workflow-templates/add-job/spark-r +++ b/gcloud/dataproc/workflow-templates/add-job/spark-r @@ -7,7 +7,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--archives=[ARCHIVE,...]] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--labels=[KEY=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...] @@ -95,6 +95,23 @@ OPTIONAL FLAGS properties, see: https://spark.apache.org/docs/latest/configuration.html#available-properties. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/dataproc/workflow-templates/add-job/spark-sql b/gcloud/dataproc/workflow-templates/add-job/spark-sql index d18444c64..47df08e5c 100644 --- a/gcloud/dataproc/workflow-templates/add-job/spark-sql +++ b/gcloud/dataproc/workflow-templates/add-job/spark-sql @@ -8,7 +8,7 @@ SYNOPSIS (--workflow-template=WORKFLOW_TEMPLATE : --region=REGION) [--driver-log-levels=[PACKAGE=LEVEL,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--params=[PARAM=VALUE,...]] - [--properties=[PROPERTY=VALUE,...]] + [--properties=[PROPERTY=VALUE,...]] [--properties-file=PROPERTIES_FILE] [--start-after=STEP_ID,[STEP_ID,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -88,6 +88,23 @@ OPTIONAL FLAGS --properties=[PROPERTY=VALUE,...] A list of key value pairs to configure Hive. + --properties-file=PROPERTIES_FILE + Path to a local file or a file in a Cloud Storage bucket containing + configuration properties for the job. The client machine running this + command must have read permission to the file. + + Specify properties in the form of property=value in the text file. For + example: + + # Properties to set for the job: + key1=value1 + key2=value2 + # Comment out properties not used. + # key3=value3 + + If a property is set in both --properties and --properties-file, the + value defined in --properties takes precedence. + --start-after=STEP_ID,[STEP_ID,...] (Optional) List of step IDs to start this job after. diff --git a/gcloud/eventarc/audit-logs-provider/help b/gcloud/eventarc/audit-logs-provider/help new file mode 100644 index 000000000..b6508bbcf --- /dev/null +++ b/gcloud/eventarc/audit-logs-provider/help @@ -0,0 +1,27 @@ +NAME + gcloud eventarc audit-logs-provider - explore provider serviceNames and + methodNames for event type google.cloud.audit.log.v1.written in + Eventarc + +SYNOPSIS + gcloud eventarc audit-logs-provider GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Explore provider serviceNames and methodNames for event type + google.cloud.audit.log.v1.written in Eventarc. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + method-names + Explore values for the methodName attribute for event type + google.cloud.audit.log.v1.written. + + service-names + Explore values for the serviceName attribute for event type + google.cloud.audit.log.v1.written. diff --git a/gcloud/eventarc/audit-logs-provider/method-names/help b/gcloud/eventarc/audit-logs-provider/method-names/help new file mode 100644 index 000000000..cd394456d --- /dev/null +++ b/gcloud/eventarc/audit-logs-provider/method-names/help @@ -0,0 +1,23 @@ +NAME + gcloud eventarc audit-logs-provider method-names - explore values for the + methodName attribute for event type google.cloud.audit.log.v1.written + +SYNOPSIS + gcloud eventarc audit-logs-provider method-names COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Explore values for the methodName attribute for event type + google.cloud.audit.log.v1.written. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + List values for the methodName attribute for event type + google.cloud.audit.log.v1.written. diff --git a/gcloud/eventarc/audit-logs-provider/method-names/list b/gcloud/eventarc/audit-logs-provider/method-names/list new file mode 100644 index 000000000..e6753b92d --- /dev/null +++ b/gcloud/eventarc/audit-logs-provider/method-names/list @@ -0,0 +1,63 @@ +NAME + gcloud eventarc audit-logs-provider method-names list - list values for the + methodName attribute for event type google.cloud.audit.log.v1.written + +SYNOPSIS + gcloud eventarc audit-logs-provider method-names list + --service-name=SERVICE_NAME [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List values for the methodName attribute for event type + google.cloud.audit.log.v1.written. + +EXAMPLES + To list methodName values for serviceName storage.googleapis.com, run: + + $ gcloud eventarc audit-logs-provider method-names list \ + --service-name=storage.googleapis.com + +REQUIRED FLAGS + --service-name=SERVICE_NAME + The value of the serviceName CloudEvents attribute. + +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. diff --git a/gcloud/eventarc/audit-logs-provider/service-names/help b/gcloud/eventarc/audit-logs-provider/service-names/help new file mode 100644 index 000000000..b39d5d1b8 --- /dev/null +++ b/gcloud/eventarc/audit-logs-provider/service-names/help @@ -0,0 +1,23 @@ +NAME + gcloud eventarc audit-logs-provider service-names - explore values for the + serviceName attribute for event type google.cloud.audit.log.v1.written + +SYNOPSIS + gcloud eventarc audit-logs-provider service-names COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Explore values for the serviceName attribute for event type + google.cloud.audit.log.v1.written. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + List values for the serviceName attribute for event type + google.cloud.audit.log.v1.written. diff --git a/gcloud/eventarc/audit-logs-provider/service-names/list b/gcloud/eventarc/audit-logs-provider/service-names/list new file mode 100644 index 000000000..304c1d77d --- /dev/null +++ b/gcloud/eventarc/audit-logs-provider/service-names/list @@ -0,0 +1,59 @@ +NAME + gcloud eventarc audit-logs-provider service-names list - list values for + the serviceName attribute for event type + google.cloud.audit.log.v1.written + +SYNOPSIS + gcloud eventarc audit-logs-provider service-names list + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List values for the serviceName attribute for event type + google.cloud.audit.log.v1.written. + +EXAMPLES + To list serviceName values for event type + google.cloud.audit.log.v1.written, run: + + $ gcloud eventarc audit-logs-provider service-names 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. diff --git a/gcloud/eventarc/help b/gcloud/eventarc/help index 3511c7d18..1ef561c93 100644 --- a/gcloud/eventarc/help +++ b/gcloud/eventarc/help @@ -15,6 +15,10 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + audit-logs-provider + Explore provider serviceNames and methodNames for event type + google.cloud.audit.log.v1.written in Eventarc. + channel-connections Manage Eventarc channel connections. diff --git a/gcloud/network-connectivity/spokes/delete b/gcloud/network-connectivity/spokes/delete index 0e774d60b..2d232c531 100644 --- a/gcloud/network-connectivity/spokes/delete +++ b/gcloud/network-connectivity/spokes/delete @@ -2,27 +2,29 @@ NAME gcloud network-connectivity spokes delete - delete a spoke SYNOPSIS - gcloud network-connectivity spokes delete (SPOKE : --region=REGION) - [--async] [GCLOUD_WIDE_FLAG ...] + gcloud network-connectivity spokes delete SPOKE [--async] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Delete the specified spoke. EXAMPLES - To delete a spoke with name myspoke in region us-central1, run: + To delete a spoke named myspoke in the us-central1 region, run: $ gcloud network-connectivity spokes delete myspoke \ - --region=us-central1 + --region=us-central1 POSITIONAL ARGUMENTS - Spoke resource - Name of the spoke to be deleted. 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: + Spoke resource - Name of the spoke to delete. 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 spoke on the command line with a fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. + ◆ provide the argument --project on the command line; + ◆ set the property core/project. To set the location attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --region on the command line. This must be specified. @@ -31,22 +33,16 @@ POSITIONAL ARGUMENTS the spoke attribute: ▸ provide the argument spoke on the command line. - This positional must be specified if any of the other arguments in - this group are specified. - - --region=REGION - The location Id. - - To set the region attribute: - ▸ provide the argument spoke on the command line with a fully - specified name; - ▸ provide the argument --region on the command line. - FLAGS --async Return immediately, without waiting for the operation in progress to complete. + --region=REGION + A Google Cloud region. To see the names of regions, see Viewing a list + of available regions + (https://cloud.google.com/compute/docs/regions-zones/viewing-regions-zones#viewing_a_list_of_available_regions). + 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/network-connectivity/spokes/describe b/gcloud/network-connectivity/spokes/describe index a1ee94c45..b6576a20c 100644 --- a/gcloud/network-connectivity/spokes/describe +++ b/gcloud/network-connectivity/spokes/describe @@ -2,28 +2,30 @@ NAME gcloud network-connectivity spokes describe - describe a spoke SYNOPSIS - gcloud network-connectivity spokes describe (SPOKE : --region=REGION) + gcloud network-connectivity spokes describe SPOKE [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Retrieve and display details about a spoke. EXAMPLES - To display details about the spoke named spoke-1 in region us-central1, + To display details about a spoke named myspoke in the us-central1 region, run: - $ gcloud network-connectivity spokes describe spoke-1 \ - --region=us-central1 + $ gcloud network-connectivity spokes describe myspoke \ + --region=us-central1 POSITIONAL ARGUMENTS - Spoke resource - Name of the spoke 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: + Spoke resource - Name of the spoke 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 spoke on the command line with a fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. + ◆ provide the argument --project on the command line; + ◆ set the property core/project. To set the location attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --region on the command line. This must be specified. @@ -32,16 +34,11 @@ POSITIONAL ARGUMENTS the spoke attribute: ▸ provide the argument spoke on the command line. - This positional must be specified if any of the other arguments in - this group are specified. - - --region=REGION - The location Id. - - To set the region attribute: - ▸ provide the argument spoke on the command line with a fully - specified name; - ▸ provide the argument --region on the command line. +FLAGS + --region=REGION + A Google Cloud region. To see the names of regions, see Viewing a list + of available regions + (https://cloud.google.com/compute/docs/regions-zones/viewing-regions-zones#viewing_a_list_of_available_regions). GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/pubsub/subscriptions/create b/gcloud/pubsub/subscriptions/create index 2f7fe00be..a24bb9e71 100644 --- a/gcloud/pubsub/subscriptions/create +++ b/gcloud/pubsub/subscriptions/create @@ -12,6 +12,8 @@ SYNOPSIS [--push-auth-service-account=SERVICE_ACCOUNT_EMAIL] [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] [--push-endpoint=PUSH_ENDPOINT] [--retain-acked-messages] + [--bigquery-table=BIGQUERY_TABLE + : --drop-unknown-fields --use-topic-schema --write-metadata] [--max-delivery-attempts=MAX_DELIVERY_ATTEMPTS [--dead-letter-topic=DEAD_LETTER_TOPIC : --dead-letter-topic-project=DEAD_LETTER_TOPIC_PROJECT]] @@ -125,6 +127,32 @@ OPTIONAL FLAGS --message-retention-duration window. Acknowledged messages are not retained by default. + BigQuery Config Options. The Cloud Pub/Sub service account associated with + the enclosing subscription's parent project (i.e., + service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have + permission to write to this BigQuery table. + + --bigquery-table=BIGQUERY_TABLE + A BigQuery table of the form {project}:{dataset_name}.{table_name} to + which to write messages for this subscription. + + This flag must be specified if any of the other arguments in this + group are specified. + + --drop-unknown-fields + When --use-topic-schema is set, whether or not to ignore fields in + the topic schema that do not appear in the BigQuery schema. If false, + then the BigQuery schema must contain all fields that are also + present in the topic schema. + + --use-topic-schema + Whether or not to use the schema for the subscription's topic (if it + exists) when writing messages to BigQuery. + + --write-metadata + Whether or not to write message metadata including message ID, + publish timestamp, ordering key, and attributes to BigQuery. + Dead Letter Queue Options. The Cloud Pub/Sub service account associated with the enclosing subscription's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have diff --git a/gcloud/pubsub/subscriptions/update b/gcloud/pubsub/subscriptions/update index 927659ced..9b24b2e74 100644 --- a/gcloud/pubsub/subscriptions/update +++ b/gcloud/pubsub/subscriptions/update @@ -10,6 +10,8 @@ SYNOPSIS [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] [--push-endpoint=PUSH_ENDPOINT] [--retain-acked-messages] [--update-labels=[KEY=VALUE,...]] + [--clear-bigquery-config | [--bigquery-table=BIGQUERY_TABLE + : --drop-unknown-fields --use-topic-schema --write-metadata]] [--clear-dead-letter-policy | --max-delivery-attempts=MAX_DELIVERY_ATTEMPTS [--dead-letter-topic=DEAD_LETTER_TOPIC @@ -87,6 +89,37 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + At most one of these can be specified: + + --clear-bigquery-config + If set, clear the BigQuery config from the subscription. + + BigQuery Config Options. The Cloud Pub/Sub service account associated + with the enclosing subscription's parent project (i.e., + service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must + have permission to write to this BigQuery table. + + --bigquery-table=BIGQUERY_TABLE + A BigQuery table of the form {project}:{dataset_name}.{table_name} + to which to write messages for this subscription. + + This flag must be specified if any of the other arguments in this + group are specified. + + --drop-unknown-fields + When --use-topic-schema is set, whether or not to ignore fields in + the topic schema that do not appear in the BigQuery schema. If + false, then the BigQuery schema must contain all fields that are + also present in the topic schema. + + --use-topic-schema + Whether or not to use the schema for the subscription's topic (if + it exists) when writing messages to BigQuery. + + --write-metadata + Whether or not to write message metadata including message ID, + publish timestamp, ordering key, and attributes to BigQuery. + At most one of these can be specified: --clear-dead-letter-policy