diff --git a/gcloud/_version b/gcloud/_version index dd6cc129a..0c0dc1d53 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,6 +1,6 @@ -Google Cloud SDK 382.0.0 -alpha 2022.04.15 -beta 2022.04.15 +Google Cloud SDK 383.0.1 +alpha 2022.04.26 +beta 2022.04.26 bq 2.0.74 -core 2022.04.15 +core 2022.04.26 gsutil 5.9 diff --git a/gcloud/access-approval/help b/gcloud/access-approval/help index 1849daedf..91cfaeb04 100644 --- a/gcloud/access-approval/help +++ b/gcloud/access-approval/help @@ -19,6 +19,9 @@ GROUPS requests Manage Access Approval requests. + service-account + Manage Access Approval service account. + settings Manage Access Approval settings. diff --git a/gcloud/access-approval/service-account/get b/gcloud/access-approval/service-account/get new file mode 100644 index 000000000..126e1050d --- /dev/null +++ b/gcloud/access-approval/service-account/get @@ -0,0 +1,51 @@ +NAME + gcloud access-approval service-account get - get Access Approval service + account + +SYNOPSIS + gcloud access-approval service-account get + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieves the service account that is used by Access Approval to access KMS + keys for signing approved approval requests. + +EXAMPLES + To get the service account for the current project use + + $ gcloud access-approval service-account get + + To get the service account for folder f1 use + + $ gcloud access-approval service-account get --folder=f1 + + To get the service account for organization org1 use + + $ gcloud access-approval service-account get --organization=org1 + +FLAGS + At most one of these can be specified: + + --folder=FOLDER + Folder number. Only one of --project, --folder, or --organization can + be provided. If none are provided then it uses config property + [core/project]. + + --organization=ORGANIZATION + Organization number. Either --project, --folder, or --organization + must be provided. If none are provided then it uses config property + [core/project]. + + --project=PROJECT + Project number or id. Only one of --project, --folder, or + --organization can be provided. If none are provided then it uses + config property [core/project]. + +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/access-approval/service-account/help b/gcloud/access-approval/service-account/help new file mode 100644 index 000000000..df258be2c --- /dev/null +++ b/gcloud/access-approval/service-account/help @@ -0,0 +1,21 @@ +NAME + gcloud access-approval service-account - manage Access Approval service + account + +SYNOPSIS + gcloud access-approval service-account COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Access Approval uses a unique service account when accessing custom keys + for signing approvals for a project, folder, or organization. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + get + Get Access Approval service account. diff --git a/gcloud/alpha/anthos/config/controller/create b/gcloud/alpha/anthos/config/controller/create index eb539b428..f06d150c6 100644 --- a/gcloud/alpha/anthos/config/controller/create +++ b/gcloud/alpha/anthos/config/controller/create @@ -43,7 +43,8 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Config Controller instance location. Currently, only - us-central1 is supported. To set the location attribute: + us-central1, us-east1, northamerica-northeast1, and asia-northeast1 + are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/alpha/anthos/config/controller/delete b/gcloud/alpha/anthos/config/controller/delete index 9c342d37b..08b78521e 100644 --- a/gcloud/alpha/anthos/config/controller/delete +++ b/gcloud/alpha/anthos/config/controller/delete @@ -38,8 +38,8 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. - Currently, only us-central1 is supported. To set the location - attribute: + Currently, only us-central1, us-east1, northamerica-northeast1, and + asia-northeast1 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/alpha/anthos/config/controller/describe b/gcloud/alpha/anthos/config/controller/describe index 7ababea67..0b71ef943 100644 --- a/gcloud/alpha/anthos/config/controller/describe +++ b/gcloud/alpha/anthos/config/controller/describe @@ -39,8 +39,8 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. - Currently, only us-central1 is supported. To set the location - attribute: + Currently, only us-central1, us-east1, northamerica-northeast1, and + asia-northeast1 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/alpha/anthos/config/controller/get-config-connector-identity b/gcloud/alpha/anthos/config/controller/get-config-connector-identity new file mode 100644 index 000000000..74c3d0edb --- /dev/null +++ b/gcloud/alpha/anthos/config/controller/get-config-connector-identity @@ -0,0 +1,44 @@ +NAME + gcloud alpha anthos config controller get-config-connector-identity - fetch + default Config Connector identity + +SYNOPSIS + gcloud alpha anthos config controller get-config-connector-identity NAME + --location=LOCATION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha anthos config controller get-config-connector-identity + prints the default Config Connector Google Service Account in a specific + Anthos Config Controller. + +EXAMPLES + To print the default Config Connector identity used by your Config + Controller 'main' in the location 'us-central1', run: + + $ gcloud alpha anthos config controller \ + get-config-connector-identity main --location=us-central1 + +POSITIONAL ARGUMENTS + NAME + Name of the Anthos Config Controller. + +REQUIRED FLAGS + --location=LOCATION + The location (region) of the Anthos Config Controller. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud anthos config controller get-config-connector-identity + diff --git a/gcloud/alpha/anthos/config/controller/help b/gcloud/alpha/anthos/config/controller/help index 147bdd61f..870d6dba6 100644 --- a/gcloud/alpha/anthos/config/controller/help +++ b/gcloud/alpha/anthos/config/controller/help @@ -25,6 +25,9 @@ COMMANDS describe (ALPHA) Describe Anthos Config Controller instances. + get-config-connector-identity + (ALPHA) Fetch default Config Connector identity. + get-credentials (ALPHA) Fetch credentials for a running Anthos Config Controller. diff --git a/gcloud/alpha/anthos/config/operations/describe b/gcloud/alpha/anthos/config/operations/describe index 8fe2f131d..86b02cf4f 100644 --- a/gcloud/alpha/anthos/config/operations/describe +++ b/gcloud/alpha/anthos/config/operations/describe @@ -39,8 +39,8 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. - Currently, only us-central1 is supported. To set the location - attribute: + Currently, only us-central1, us-east1, northamerica-northeast1, and + asia-northeast1 are supported. To set the location attribute: ▸ provide the argument operation on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/alpha/auth/login b/gcloud/alpha/auth/login index 367d5f4af..921fa85d1 100644 --- a/gcloud/alpha/auth/login +++ b/gcloud/alpha/auth/login @@ -61,9 +61,24 @@ FLAGS Minimal user output. --no-browser - Use this flag to authenticate gcloud CLI on a machine without a web + Use this flag to authenticate the gcloud CLI on a machine without a web browser. + Run gcloud auth login --no-browser and follow these steps: + + 1. Copy the long command that begins with "gcloud auth login + --remote-bootstrap=". + + 2. Paste and run this command on the command line of a different, + trusted machine that has local installations of both a web browser and + the gcloud CLI tool version 372.0 or later. + + 3. Copy the long URL output from the machine with the web browser. + + 4. Paste the long URL back to the first machine under the prompt, + "Enter the output of the above command", and press Enter to complete + the authorization. + --cred-file=CRED_FILE Path to the external account configuration file (workload identity pool, generated by the Cloud Console or gcloud iam @@ -82,8 +97,8 @@ FLAGS it is not possible to launch a browser, prints a URL to standard output to be copied. - The --[no-]launch-browser flags are deprecated and will be removed in - version 383.0.0 (04/26/2022). Use --no-browser to replace + The --[no-]launch-browser flags are deprecated and will be removed on + June 7th 2022 (Release 389.0.0). Use --no-browser to replace --no-launch-browser. Enabled by default, use --no-launch-browser to disable. diff --git a/gcloud/alpha/builds/enterprise-config/gitlab/delete b/gcloud/alpha/builds/enterprise-config/gitlab/delete new file mode 100644 index 000000000..944c85793 --- /dev/null +++ b/gcloud/alpha/builds/enterprise-config/gitlab/delete @@ -0,0 +1,29 @@ +NAME + gcloud alpha builds enterprise-config gitlab delete - delete a GitLab + Enterprise config from Google Cloud Build + +SYNOPSIS + gcloud alpha builds enterprise-config gitlab delete CONFIG + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a GitLab Enterprise config from Google Cloud Build. + +POSITIONAL ARGUMENTS + CONFIG + The id of the GitLab Enterprise 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/builds/enterprise-config/gitlab/help b/gcloud/alpha/builds/enterprise-config/gitlab/help index ee671655f..b42558735 100644 --- a/gcloud/alpha/builds/enterprise-config/gitlab/help +++ b/gcloud/alpha/builds/enterprise-config/gitlab/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + delete + (ALPHA) Delete a GitLab Enterprise config from Google Cloud Build. + describe (ALPHA) Describe a GitLab Enterprise config in a Google Cloud project. diff --git a/gcloud/alpha/compute/backend-services/create b/gcloud/alpha/compute/backend-services/create index c0cde3cde..97a16cbfc 100644 --- a/gcloud/alpha/compute/backend-services/create +++ b/gcloud/alpha/compute/backend-services/create @@ -542,36 +542,39 @@ FLAGS same backend VM while that VM remains healthy. GENERATED_COOKIE (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, - INTERNAL_SELF_MANAGED, or EXTERNAL) If the --load-balancing-scheme - is EXTERNAL or EXTERNAL_MANAGED, routes requests to backend VMs or - endpoints in a NEG, based on the contents of the GCLB cookie set by - the load balancer. Only applicable when --protocol is HTTP, HTTPS, - or HTTP2. If the --load-balancing-scheme is INTERNAL_MANAGED or + INTERNAL_SELF_MANAGED, EXTERNAL_MANAGED, or EXTERNAL) If the + --load-balancing-scheme is EXTERNAL or EXTERNAL_MANAGED, routes + requests to backend VMs or endpoints in a NEG, based on the + contents of the GCLB cookie set by the load balancer. Only + applicable when --protocol is HTTP, HTTPS, or HTTP2. If the + --load-balancing-scheme is INTERNAL_MANAGED or INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints in a NEG, based on the contents of the GCILB cookie set by the proxy. (If no cookie is present, the proxy chooses a backend VM or endpoint and sends a Set-Cookie response for future requests.) If the --load-balancing-scheme is INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints in a NEG, based on the - contents of a cookie set by Traffic Director. + contents of a cookie set by Traffic Director. This session affinity + is only valid if the load balancing locality policy is either + RING_HASH or MAGLEV. HEADER_FIELD - (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or - INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints - in a NEG based on the value of the HTTP header named in the - --custom-request-header flag. This session affinity is only valid - if the load balancing locality policy is either RING_HASH or MAGLEV - and the backend service's consistent hash specifies the name of the - HTTP header. + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, + EXTERNAL_MANAGED, or INTERNAL_SELF_MANAGED) Route requests to + backend VMs or endpoints in a NEG based on the value of the HTTP + header named in the --custom-request-header flag. This session + affinity is only valid if the load balancing locality policy is + either RING_HASH or MAGLEV and the backend service's consistent + hash specifies the name of the HTTP header. HTTP_COOKIE - (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or - INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints - in a NEG, based on an HTTP cookie named in the HTTP_COOKIE flag - (with the optional --affinity-cookie-ttl flag). If the client has - not provided the cookie, the proxy generates the cookie and returns - it to the client in a Set-Cookie header. This session affinity is - only valid if the load balancing locality policy is either - RING_HASH or MAGLEV and the backend service's consistent hash - specifies the HTTP cookie. + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, + EXTERNAL_MANAGED or INTERNAL_SELF_MANAGED) Route requests to + backend VMs or endpoints in a NEG, based on an HTTP cookie named in + the HTTP_COOKIE flag (with the optional --affinity-cookie-ttl + flag). If the client has not provided the cookie, the proxy + generates the cookie and returns it to the client in a Set-Cookie + header. This session affinity is only valid if the load balancing + locality policy is either RING_HASH or MAGLEV and the backend + service's consistent hash specifies the HTTP cookie. NONE Session affinity is disabled. diff --git a/gcloud/alpha/compute/backend-services/update b/gcloud/alpha/compute/backend-services/update index 1fd1cc2cd..515bd90fb 100644 --- a/gcloud/alpha/compute/backend-services/update +++ b/gcloud/alpha/compute/backend-services/update @@ -341,36 +341,39 @@ FLAGS same backend VM while that VM remains healthy. GENERATED_COOKIE (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, - INTERNAL_SELF_MANAGED, or EXTERNAL) If the --load-balancing-scheme - is EXTERNAL or EXTERNAL_MANAGED, routes requests to backend VMs or - endpoints in a NEG, based on the contents of the GCLB cookie set by - the load balancer. Only applicable when --protocol is HTTP, HTTPS, - or HTTP2. If the --load-balancing-scheme is INTERNAL_MANAGED or + INTERNAL_SELF_MANAGED, EXTERNAL_MANAGED, or EXTERNAL) If the + --load-balancing-scheme is EXTERNAL or EXTERNAL_MANAGED, routes + requests to backend VMs or endpoints in a NEG, based on the + contents of the GCLB cookie set by the load balancer. Only + applicable when --protocol is HTTP, HTTPS, or HTTP2. If the + --load-balancing-scheme is INTERNAL_MANAGED or INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints in a NEG, based on the contents of the GCILB cookie set by the proxy. (If no cookie is present, the proxy chooses a backend VM or endpoint and sends a Set-Cookie response for future requests.) If the --load-balancing-scheme is INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints in a NEG, based on the - contents of a cookie set by Traffic Director. + contents of a cookie set by Traffic Director. This session affinity + is only valid if the load balancing locality policy is either + RING_HASH or MAGLEV. HEADER_FIELD - (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or - INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints - in a NEG based on the value of the HTTP header named in the - --custom-request-header flag. This session affinity is only valid - if the load balancing locality policy is either RING_HASH or MAGLEV - and the backend service's consistent hash specifies the name of the - HTTP header. + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, + EXTERNAL_MANAGED, or INTERNAL_SELF_MANAGED) Route requests to + backend VMs or endpoints in a NEG based on the value of the HTTP + header named in the --custom-request-header flag. This session + affinity is only valid if the load balancing locality policy is + either RING_HASH or MAGLEV and the backend service's consistent + hash specifies the name of the HTTP header. HTTP_COOKIE - (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or - INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints - in a NEG, based on an HTTP cookie named in the HTTP_COOKIE flag - (with the optional --affinity-cookie-ttl flag). If the client has - not provided the cookie, the proxy generates the cookie and returns - it to the client in a Set-Cookie header. This session affinity is - only valid if the load balancing locality policy is either - RING_HASH or MAGLEV and the backend service's consistent hash - specifies the HTTP cookie. + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, + EXTERNAL_MANAGED or INTERNAL_SELF_MANAGED) Route requests to + backend VMs or endpoints in a NEG, based on an HTTP cookie named in + the HTTP_COOKIE flag (with the optional --affinity-cookie-ttl + flag). If the client has not provided the cookie, the proxy + generates the cookie and returns it to the client in a Set-Cookie + header. This session affinity is only valid if the load balancing + locality policy is either RING_HASH or MAGLEV and the backend + service's consistent hash specifies the HTTP cookie. NONE Session affinity is disabled. diff --git a/gcloud/alpha/compute/forwarding-rules/create b/gcloud/alpha/compute/forwarding-rules/create index 9c963e7c7..a3d26038a 100644 --- a/gcloud/alpha/compute/forwarding-rules/create +++ b/gcloud/alpha/compute/forwarding-rules/create @@ -15,7 +15,8 @@ SYNOPSIS | --target-tcp-proxy=TARGET_TCP_PROXY | --target-vpn-gateway=TARGET_VPN_GATEWAY) [--allow-global-access] [--allow-psc-global-access] [--description=DESCRIPTION] - [--ip-protocol=IP_PROTOCOL] [--is-mirroring-collector] + [--disable-automate-dns-zone] [--ip-protocol=IP_PROTOCOL] + [--is-mirroring-collector] [--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--network=NETWORK] [--network-tier=NETWORK_TIER] [--service-directory-registration=SERVICE_DIRECTORY_REGISTRATION] @@ -180,6 +181,13 @@ OPTIONAL FLAGS --description=DESCRIPTION Optional textual description for the forwarding rule. + --disable-automate-dns-zone + If specified, then a DNS zone will not be auto-generated for this + Private Service Connect forwarding rule. This can only be specified if + the forwarding rule's target is a service attachment + (--target-service-attachment=SERVICE_ATTACHMENT) or Google APIs bundle + (--target-google-apis-bundle=API_BUNDLE) + --ip-protocol=IP_PROTOCOL IP protocol that the rule will serve. The default is TCP. diff --git a/gcloud/alpha/compute/forwarding-rules/update b/gcloud/alpha/compute/forwarding-rules/update index ddb9c1260..08a296db8 100644 --- a/gcloud/alpha/compute/forwarding-rules/update +++ b/gcloud/alpha/compute/forwarding-rules/update @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha compute forwarding-rules update NAME [--allow-global-access] - [--network-tier=NETWORK_TIER] + [--allow-psc-global-access] [--network-tier=NETWORK_TIER] [--source-ip-ranges=SOURCE_IP_RANGE,[...]] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] @@ -47,6 +47,12 @@ FLAGS the LOAD_BALANCING_SCHEME set to INTERNAL and the target must be either a backend service or a target instance. + --allow-psc-global-access + If specified, then clients from all regions can access this Private + Service Connect forwarding rule. This can only be specified if the + forwarding rule's target is a service attachment + (--target-service-attachment). + --network-tier=NETWORK_TIER Update the network tier of a forwarding rule. It does not allow to change from PREMIUM to STANDARD and visa versa. diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index ffd0dcc04..f293dab5d 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -413,7 +413,8 @@ FLAGS --local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE],[size=SIZE] Attaches a local SSD to the instances. - This flag is currently in BETA and might change without notice. + This flag is currently in alpha and beta versions only and might change + without notice. device-name Optional. A name that indicates the disk name the guest operating @@ -427,11 +428,10 @@ FLAGS higher performance. size - Optional. Size of the SSD disk. The value must be a whole number - followed by a size unit of KB for kilobyte, MB for megabyte, GB for - gigabyte, or TB for terabyte. For example, 750GB will produce a 750 - gigabyte disk. The size must be a multiple of 375 GB and the - default is 375 GB. For Alpha API only. + Optional. The only valid value is 375GB. Specify the --local-ssd + flag multiple times if you need multiple 375GB local SSD + partitions. You can specify a maximum of 24 local SSDs for a + maximum of 9TB attached to an instance. --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of @@ -908,7 +908,7 @@ FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. Maintenance Behavior. diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index 1f6c4bd50..4ffa7aac6 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -415,7 +415,8 @@ FLAGS --local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE],[size=SIZE] Attaches a local SSD to the instances. - This flag is currently in BETA and might change without notice. + This flag is currently in alpha and beta versions only and might change + without notice. device-name Optional. A name that indicates the disk name the guest operating @@ -429,11 +430,10 @@ FLAGS higher performance. size - Optional. Size of the SSD disk. The value must be a whole number - followed by a size unit of KB for kilobyte, MB for megabyte, GB for - gigabyte, or TB for terabyte. For example, 750GB will produce a 750 - gigabyte disk. The size must be a multiple of 375 GB and the - default is 375 GB. For Alpha API only. + Optional. The only valid value is 375GB. Specify the --local-ssd + flag multiple times if you need multiple 375GB local SSD + partitions. You can specify a maximum of 24 local SSDs for a + maximum of 9TB attached to an instance. --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of @@ -740,7 +740,7 @@ FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. Maintenance Behavior. diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index 4cac7d6d1..d4d35941b 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -421,7 +421,8 @@ OPTIONAL FLAGS --local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE],[size=SIZE] Attaches a local SSD to the instances. - This flag is currently in BETA and might change without notice. + This flag is currently in alpha and beta versions only and might change + without notice. device-name Optional. A name that indicates the disk name the guest operating @@ -435,11 +436,10 @@ OPTIONAL FLAGS higher performance. size - Optional. Size of the SSD disk. The value must be a whole number - followed by a size unit of KB for kilobyte, MB for megabyte, GB for - gigabyte, or TB for terabyte. For example, 750GB will produce a 750 - gigabyte disk. The size must be a multiple of 375 GB and the - default is 375 GB. For Alpha API only. + Optional. The only valid value is 375GB. Specify the --local-ssd + flag multiple times if you need multiple 375GB local SSD + partitions. You can specify a maximum of 24 local SSDs for a + maximum of 9TB attached to an instance. --location-policy=[ZONE=POLICY,...] Policy for which zones to include or exclude during bulk instance @@ -802,7 +802,7 @@ OPTIONAL FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. --source-snapshot=SOURCE_SNAPSHOT The name of the source disk snapshot that the instance boot disk will diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 3d610f28c..5684e354d 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -536,7 +536,8 @@ FLAGS --local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE],[size=SIZE] Attaches a local SSD to the instances. - This flag is currently in BETA and might change without notice. + This flag is currently in alpha and beta versions only and might change + without notice. device-name Optional. A name that indicates the disk name the guest operating @@ -550,11 +551,10 @@ FLAGS higher performance. size - Optional. Size of the SSD disk. The value must be a whole number - followed by a size unit of KB for kilobyte, MB for megabyte, GB for - gigabyte, or TB for terabyte. For example, 750GB will produce a 750 - gigabyte disk. The size must be a multiple of 375 GB and the - default is 375 GB. For Alpha API only. + Optional. The only valid value is 375GB. Specify the --local-ssd + flag multiple times if you need multiple 375GB local SSD + partitions. You can specify a maximum of 24 local SSDs for a + maximum of 9TB attached to an instance. --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of @@ -990,7 +990,7 @@ FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. --source-snapshot=SOURCE_SNAPSHOT The name of the source disk snapshot that the instance boot disk will diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index 173447557..129cf5f4c 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -461,7 +461,8 @@ FLAGS --local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE],[size=SIZE] Attaches a local SSD to the instances. - This flag is currently in BETA and might change without notice. + This flag is currently in alpha and beta versions only and might change + without notice. device-name Optional. A name that indicates the disk name the guest operating @@ -475,11 +476,10 @@ FLAGS higher performance. size - Optional. Size of the SSD disk. The value must be a whole number - followed by a size unit of KB for kilobyte, MB for megabyte, GB for - gigabyte, or TB for terabyte. For example, 750GB will produce a 750 - gigabyte disk. The size must be a multiple of 375 GB and the - default is 375 GB. For Alpha API only. + Optional. The only valid value is 375GB. Specify the --local-ssd + flag multiple times if you need multiple 375GB local SSD + partitions. You can specify a maximum of 24 local SSDs for a + maximum of 9TB attached to an instance. --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of @@ -846,7 +846,7 @@ FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. Maintenance Behavior. diff --git a/gcloud/alpha/compute/network-endpoint-groups/create b/gcloud/alpha/compute/network-endpoint-groups/create index dd883400a..db410ea4f 100644 --- a/gcloud/alpha/compute/network-endpoint-groups/create +++ b/gcloud/alpha/compute/network-endpoint-groups/create @@ -59,6 +59,11 @@ FLAGS non-gcp-private-ip-port, gce-vm-primary-ip, gce-vm-ip, or private-service-connect. + For Private Service Connect NEGs, you can optionally specify --network + and --subnet if --psc-target-service points to a published service. If + --psc-target-service points to the regional service endpoint of a + Google API, do not specify --network or --subnet. + --network-endpoint-type=NETWORK_ENDPOINT_TYPE; default="gce-vm-ip-port" Determines the spec of endpoints attached to this group. @@ -126,7 +131,11 @@ FLAGS region where the network endpoint group is created. This is only supported for NEGs with endpoint type gce-vm-ip-port, - gce-vm-primary-ip, or gce-vm-ip. + gce-vm-primary-ip, gce-vm-ip, or private-service-connect. For Private + Service Connect NEGs, you can optionally specify --network and --subnet + if --psc-target-service points to a published service. If + --psc-target-service points to the regional service endpoint of a + Google API, do not specify --network or --subnet. The serverless routing configurations are only valid when endpoint type of the network endpoint group is serverless. diff --git a/gcloud/alpha/compute/public-advertised-prefixes/create b/gcloud/alpha/compute/public-advertised-prefixes/create index 8bccd06cb..695a10994 100644 --- a/gcloud/alpha/compute/public-advertised-prefixes/create +++ b/gcloud/alpha/compute/public-advertised-prefixes/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha compute public-advertised-prefixes create NAME --dns-verification-ip=DNS_VERIFICATION_IP --range=RANGE - [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--pdp-scope=PDP_SCOPE] + [GCLOUD_WIDE_FLAG ...] EXAMPLES To create a public advertised prefix: @@ -14,6 +15,12 @@ EXAMPLES my-public-advertised-prefix --range=120.120.10.0/24 \ --dns-verification-ip=120.120.10.15 + To create a v2 public advertised prefix: + + $ gcloud alpha compute public-advertised-prefixes create \ + my-v2-public-advertised-prefix --range=120.120.10.0/24 \ + --dns-verification-ip=120.120.10.15 --pdp-scope=REGIONAL + POSITIONAL ARGUMENTS NAME Name of the public advertised prefix to operate on. @@ -30,6 +37,10 @@ OPTIONAL FLAGS --description=DESCRIPTION Description of this public advertised prefix. + --pdp-scope=PDP_SCOPE + Specifies how child public delegated prefix will be scoped. PDP_SCOPE + must be one of: GLOBAL, REGIONAL. + 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/config/help b/gcloud/alpha/config/help index d70540022..cae85c85f 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -965,9 +965,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index ae7c8d2b4..6542dd85a 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -970,9 +970,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 9603316f2..0d0d7939b 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -31,11 +31,11 @@ DESCRIPTION EXAMPLES To set the project property in the core section, run: - $ gcloud alpha config set project myProject + $ gcloud alpha config set project PROJECT_ID To set the zone property in the compute section, run: - $ gcloud alpha config set compute/zone asia-east1-b + $ gcloud alpha config set compute/zone ZONE_NAME To disable prompting for scripting, run: @@ -983,9 +983,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 3b7a0ea2c..5effff6ed 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -944,9 +944,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/alpha/container/aws/clusters/create b/gcloud/alpha/container/aws/clusters/create index 9bd62bc3b..b1b8800e3 100644 --- a/gcloud/alpha/container/aws/clusters/create +++ b/gcloud/alpha/container/aws/clusters/create @@ -97,7 +97,7 @@ REQUIRED FLAGS --pod-address-cidr-blocks=POD_ADDRESS_CIDR_BLOCKS IP address range for the pods in this cluster in CIDR notation (e.g. - 10.0.0.0/8). Can be any RFC 1918 IP range. + 10.0.0.0/8). --role-arn=ROLE_ARN Amazon Resource Name (ARN) of the IAM role to assume when managing AWS @@ -105,7 +105,7 @@ REQUIRED FLAGS --service-address-cidr-blocks=SERVICE_ADDRESS_CIDR_BLOCKS IP address range for the services IPs in CIDR notation (e.g. - 10.0.0.0/8). Can be any RFC 1918 IP range. + 10.0.0.0/8). --subnet-ids=[SUBNET_ID,...] Subnet ID of an existing VNET to use for the cluster control plane. diff --git a/gcloud/alpha/container/azure/clusters/create b/gcloud/alpha/container/azure/clusters/create index 419fa9a7a..240c6e01b 100644 --- a/gcloud/alpha/container/azure/clusters/create +++ b/gcloud/alpha/container/azure/clusters/create @@ -102,14 +102,14 @@ REQUIRED FLAGS --pod-address-cidr-blocks=POD_ADDRESS_CIDR_BLOCKS IP address range for the pods in this cluster in CIDR notation (e.g. - 10.0.0.0/8). Can be any RFC 1918 IP range. + 10.0.0.0/8). --resource-group-id=RESOURCE_GROUP_ID ID of the Azure Resource Group to associate the cluster with. --service-address-cidr-blocks=SERVICE_ADDRESS_CIDR_BLOCKS IP address range for the services IPs in CIDR notation (e.g. - 10.0.0.0/8). Can be any RFC 1918 IP range. + 10.0.0.0/8). --ssh-public-key=SSH_PUBLIC_KEY SSH public key to use for authentication. diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index f4c5248ff..e4eb001df 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -1256,7 +1256,7 @@ FLAGS Flags to specify identity for autoprovisioned nodes: --autoprovisioning-scopes=[SCOPE,...] - The scopes be used by node instances in autoprovisioned node + The scopes to be used by node instances in autoprovisioned node pools. Multiple scopes can be specified, separated by commas. For information on defaults, look at: https://cloud.google.com/sdk/gcloud/reference/container/clusters/create#--scopes diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index e1ebb9621..1850e4e38 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -858,9 +858,9 @@ REQUIRED FLAGS Flags to specify identity for autoprovisioned nodes: --autoprovisioning-scopes=[SCOPE,...] - The scopes be used by node instances in autoprovisioned node - pools. Multiple scopes can be specified, separated by commas. - For information on defaults, look at: + The scopes to be used by node instances in autoprovisioned + node pools. Multiple scopes can be specified, separated by + commas. For information on defaults, look at: https://cloud.google.com/sdk/gcloud/reference/container/clusters/create#--scopes --autoprovisioning-service-account=AUTOPROVISIONING_SERVICE_ACCOUNT diff --git a/gcloud/alpha/dns/policies/delete b/gcloud/alpha/dns/policies/delete index e89adc20a..83e95d48e 100644 --- a/gcloud/alpha/dns/policies/delete +++ b/gcloud/alpha/dns/policies/delete @@ -39,7 +39,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dns/v1beta2 API. The full documentation for this API - can be found at: https://developers.google.com/cloud-dns + can be found at: https://cloud.google.com/dns/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dns/policies/describe b/gcloud/alpha/dns/policies/describe index 5d550fd5c..7cc0257c3 100644 --- a/gcloud/alpha/dns/policies/describe +++ b/gcloud/alpha/dns/policies/describe @@ -39,7 +39,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dns/v1 API. The full documentation for this API can - be found at: https://developers.google.com/cloud-dns + be found at: https://cloud.google.com/dns/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dns/policies/list b/gcloud/alpha/dns/policies/list index 412f416f9..e0539e78c 100644 --- a/gcloud/alpha/dns/policies/list +++ b/gcloud/alpha/dns/policies/list @@ -61,7 +61,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dns/v1beta2 API. The full documentation for this API - can be found at: https://developers.google.com/cloud-dns + can be found at: https://cloud.google.com/dns/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/interconnects/attachments/dedicated/create b/gcloud/alpha/edge-cloud/networking/interconnects/attachments/dedicated/create index 6695512e9..02948b2cb 100644 --- a/gcloud/alpha/edge-cloud/networking/interconnects/attachments/dedicated/create +++ b/gcloud/alpha/edge-cloud/networking/interconnects/attachments/dedicated/create @@ -100,7 +100,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/interconnects/attachments/delete b/gcloud/alpha/edge-cloud/networking/interconnects/attachments/delete index 236957f5e..6910a07dd 100644 --- a/gcloud/alpha/edge-cloud/networking/interconnects/attachments/delete +++ b/gcloud/alpha/edge-cloud/networking/interconnects/attachments/delete @@ -68,7 +68,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/interconnects/attachments/describe b/gcloud/alpha/edge-cloud/networking/interconnects/attachments/describe index 6d44da9ec..65b5bd31d 100644 --- a/gcloud/alpha/edge-cloud/networking/interconnects/attachments/describe +++ b/gcloud/alpha/edge-cloud/networking/interconnects/attachments/describe @@ -65,7 +65,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/interconnects/attachments/list b/gcloud/alpha/edge-cloud/networking/interconnects/attachments/list index ec910d9bc..13e0518d4 100644 --- a/gcloud/alpha/edge-cloud/networking/interconnects/attachments/list +++ b/gcloud/alpha/edge-cloud/networking/interconnects/attachments/list @@ -87,7 +87,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/interconnects/describe b/gcloud/alpha/edge-cloud/networking/interconnects/describe index f8ebce334..d75d4377f 100644 --- a/gcloud/alpha/edge-cloud/networking/interconnects/describe +++ b/gcloud/alpha/edge-cloud/networking/interconnects/describe @@ -60,7 +60,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/interconnects/get-diagnostics b/gcloud/alpha/edge-cloud/networking/interconnects/get-diagnostics new file mode 100644 index 000000000..a3a27b9b1 --- /dev/null +++ b/gcloud/alpha/edge-cloud/networking/interconnects/get-diagnostics @@ -0,0 +1,67 @@ +NAME + gcloud alpha edge-cloud networking interconnects get-diagnostics - get the + diagnostics of a specified Distributed Cloud Edge Network interconnect + +SYNOPSIS + gcloud alpha edge-cloud networking interconnects get-diagnostics + (INTERCONNECT : --location=LOCATION --zone=ZONE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get the diagnostics of a specified Distributed Cloud Edge Network + interconnect. + +EXAMPLES + To get the diagnostics of the Distributed Cloud Edge Network interconnect + 'my-interconnect' in edge zone 'us-central1-edge-den1' , run: + + $ gcloud alpha edge-cloud networking interconnects get-diagnostics \ + my-interconnect --location=us-central1 \ + --zone=us-central1-edge-den1 + +POSITIONAL ARGUMENTS + Interconnect resource - The interconnect to get diagnostics. 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 interconnect on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INTERCONNECT + ID of the interconnect or fully qualified identifier for the + interconnect. To set the interconnect attribute: + ▸ provide the argument interconnect on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The Cloud location for the interconnect. To set the location + attribute: + ▸ provide the argument interconnect on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --zone=ZONE + The zone of the interconnect. To set the zone attribute: + ▸ provide the argument interconnect on the command line with a + fully specified name; + ▸ provide the argument --zone on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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/edge-cloud/networking/interconnects/help b/gcloud/alpha/edge-cloud/networking/interconnects/help index 703fd206b..7e1189aa5 100644 --- a/gcloud/alpha/edge-cloud/networking/interconnects/help +++ b/gcloud/alpha/edge-cloud/networking/interconnects/help @@ -27,6 +27,10 @@ COMMANDS (ALPHA) Show details about the Distributed Cloud Edge Network interconnect. + get-diagnostics + (ALPHA) Get the diagnostics of a specified Distributed Cloud Edge + Network interconnect. + list (ALPHA) List Distributed Cloud Edge Network interconnects. diff --git a/gcloud/alpha/edge-cloud/networking/interconnects/list b/gcloud/alpha/edge-cloud/networking/interconnects/list index 068f8abe6..9c3f4c97b 100644 --- a/gcloud/alpha/edge-cloud/networking/interconnects/list +++ b/gcloud/alpha/edge-cloud/networking/interconnects/list @@ -87,7 +87,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/networks/create b/gcloud/alpha/edge-cloud/networking/networks/create index 07b55c485..0e6e8e578 100644 --- a/gcloud/alpha/edge-cloud/networking/networks/create +++ b/gcloud/alpha/edge-cloud/networking/networks/create @@ -1,6 +1,6 @@ NAME - gcloud alpha edge-cloud networking networks create - create a Edge Network - network + gcloud alpha edge-cloud networking networks create - create a Distributed + Cloud Edge Network network SYNOPSIS gcloud alpha edge-cloud networking networks create @@ -9,20 +9,20 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create a new Edge Network network resource. + (ALPHA) Create a new Distributed Cloud Edge Network network resource. EXAMPLES To create a network called 'my-network' with MTU value of 9000 bytes in edge zone 'us-central1-edge-den1', run: $ gcloud alpha edge-cloud networking networks create my-network \ - --location=us-central1 --zone=den1 --mtu=9000 + --location=us-central1 --zone=us-central1-edge-den1 --mtu=9000 POSITIONAL ARGUMENTS - Network resource - Edge Network network to create. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. To set the project attribute: + Network resource - Distributed Cloud Edge Network network to create. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: ◆ provide the argument network on the command line with a fully specified name; ◆ set the property core/project; @@ -82,7 +82,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/networks/delete b/gcloud/alpha/edge-cloud/networking/networks/delete index 921152438..b966537d8 100644 --- a/gcloud/alpha/edge-cloud/networking/networks/delete +++ b/gcloud/alpha/edge-cloud/networking/networks/delete @@ -1,6 +1,6 @@ NAME - gcloud alpha edge-cloud networking networks delete - delete a Edge Network - network + gcloud alpha edge-cloud networking networks delete - delete a Distributed + Cloud Edge Network network SYNOPSIS gcloud alpha edge-cloud networking networks delete @@ -8,20 +8,20 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete a Edge Network network. + (ALPHA) Delete a Distributed Cloud Edge Network network. EXAMPLES - To delete a network called 'my-network' in edge zone - 'us-central1-edge-den1', run: + To delete a Distributed Cloud Edge Network network called 'my-network' in + edge zone 'us-central1-edge-den1', run: $ gcloud alpha edge-cloud networking networks delete my-network \ - --location=us-central1 --zone=den1 + --location=us-central1 --zone=us-central1-edge-den1 POSITIONAL ARGUMENTS - Network resource - Edge Network network to delete. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. To set the project attribute: + Network resource - Distributed Cloud Edge Network network to delete. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: ◆ provide the argument network on the command line with a fully specified name; ◆ set the property core/project; @@ -65,7 +65,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/networks/describe b/gcloud/alpha/edge-cloud/networking/networks/describe index bf448ba0b..1d17502ac 100644 --- a/gcloud/alpha/edge-cloud/networking/networks/describe +++ b/gcloud/alpha/edge-cloud/networking/networks/describe @@ -1,26 +1,27 @@ NAME gcloud alpha edge-cloud networking networks describe - show details about - the Edge Network network + the Distributed Cloud Edge Network network SYNOPSIS gcloud alpha edge-cloud networking networks describe (NETWORK : --location=LOCATION --zone=ZONE) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Show details about the Edge Network network. + (ALPHA) Show details about the Distributed Cloud Edge Network network. EXAMPLES To show details about a network called 'my-network' in edge zone 'us-central1-edge-den1', run: $ gcloud alpha edge-cloud networking networks describe my-network \ - --location=us-central1 --zone=den1 + --location=us-central1 --zone=us-central1-edge-den1 POSITIONAL ARGUMENTS - Network resource - The Edge Network network 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: + Network resource - The Distributed Cloud Edge Network network you want to + describe. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. To set the project + attribute: ◆ provide the argument network on the command line with a fully specified name; ◆ set the property core/project; @@ -59,7 +60,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/networks/get-status b/gcloud/alpha/edge-cloud/networking/networks/get-status new file mode 100644 index 000000000..130aa1e83 --- /dev/null +++ b/gcloud/alpha/edge-cloud/networking/networks/get-status @@ -0,0 +1,65 @@ +NAME + gcloud alpha edge-cloud networking networks get-status - get the status of + a specified Distributed Cloud Edge Network network + +SYNOPSIS + gcloud alpha edge-cloud networking networks get-status + (NETWORK : --location=LOCATION --zone=ZONE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get the status of a specified Distributed Cloud Edge Network + network. + +EXAMPLES + To get the status of the Distributed Cloud Edge Network network + 'my-network' in edge zone 'us-central1-edge-den1' , run: + + $ gcloud alpha edge-cloud networking networks get-status \ + my-network --location=us-central1 --zone=us-central1-edge-den1 + +POSITIONAL ARGUMENTS + Network resource - The network to get status. 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 on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + NETWORK + ID of the network or fully qualified identifier for the network. To + set the network attribute: + ▸ provide the argument network on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The Cloud location for the network. To set the location attribute: + ▸ provide the argument network on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --zone=ZONE + The zone of the network. To set the zone attribute: + ▸ provide the argument network on the command line with a fully + specified name; + ▸ provide the argument --zone on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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/edge-cloud/networking/networks/help b/gcloud/alpha/edge-cloud/networking/networks/help index bdf14f5d7..526222276 100644 --- a/gcloud/alpha/edge-cloud/networking/networks/help +++ b/gcloud/alpha/edge-cloud/networking/networks/help @@ -17,16 +17,20 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create a Edge Network network. + (ALPHA) Create a Distributed Cloud Edge Network network. delete - (ALPHA) Delete a Edge Network network. + (ALPHA) Delete a Distributed Cloud Edge Network network. describe - (ALPHA) Show details about the Edge Network network. + (ALPHA) Show details about the Distributed Cloud Edge Network network. + + get-status + (ALPHA) Get the status of a specified Distributed Cloud Edge Network + network. list - (ALPHA) List Edge Network networks. + (ALPHA) List Distributed Cloud Edge Network networks. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/networks/list b/gcloud/alpha/edge-cloud/networking/networks/list index d7c95edc5..8d982ffc7 100644 --- a/gcloud/alpha/edge-cloud/networking/networks/list +++ b/gcloud/alpha/edge-cloud/networking/networks/list @@ -1,6 +1,6 @@ NAME - gcloud alpha edge-cloud networking networks list - list Edge Network - networks + gcloud alpha edge-cloud networking networks list - list Distributed Cloud + Edge Network networks SYNOPSIS gcloud alpha edge-cloud networking networks list @@ -9,11 +9,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Edge Network networks. + (ALPHA) List Distributed Cloud Edge Network networks. EXAMPLES - To list the Edge Network networks in edge zone 'us-central1-edge-den1', - run: + To list the Distributed Cloud Edge Network networks in edge zone + 'us-central1-edge-den1', run: $ gcloud alpha edge-cloud networking networks list \ --location=us-central1 --zone=us-central1-edge-den1 @@ -87,7 +87,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/operations/describe b/gcloud/alpha/edge-cloud/networking/operations/describe index 946f9be10..c66b28a8a 100644 --- a/gcloud/alpha/edge-cloud/networking/operations/describe +++ b/gcloud/alpha/edge-cloud/networking/operations/describe @@ -53,7 +53,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/operations/wait b/gcloud/alpha/edge-cloud/networking/operations/wait index e66eab8ea..e2808c819 100644 --- a/gcloud/alpha/edge-cloud/networking/operations/wait +++ b/gcloud/alpha/edge-cloud/networking/operations/wait @@ -55,7 +55,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/routers/add-interface b/gcloud/alpha/edge-cloud/networking/routers/add-interface index 524b97c07..8b793fe87 100644 --- a/gcloud/alpha/edge-cloud/networking/routers/add-interface +++ b/gcloud/alpha/edge-cloud/networking/routers/add-interface @@ -71,10 +71,12 @@ REQUIRED FLAGS Exactly one of these must be specified: - --subnetwork=SUBNETWORK - The subnetwork of the interface being added. + The argument group for adding southbound interfaces to edge router. - The argument group for adding northbound interface to edge router + --subnetwork=SUBNETWORK + The subnetwork of the interface being added. + + The argument group for adding northbound interfaces to edge router. --interconnect-attachment=INTERCONNECT_ATTACHMENT The interconnect attachment of the interface being added. diff --git a/gcloud/alpha/edge-cloud/networking/routers/create b/gcloud/alpha/edge-cloud/networking/routers/create index 1de603bac..771115424 100644 --- a/gcloud/alpha/edge-cloud/networking/routers/create +++ b/gcloud/alpha/edge-cloud/networking/routers/create @@ -91,7 +91,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/routers/delete b/gcloud/alpha/edge-cloud/networking/routers/delete index 20362f07a..964794bd3 100644 --- a/gcloud/alpha/edge-cloud/networking/routers/delete +++ b/gcloud/alpha/edge-cloud/networking/routers/delete @@ -65,7 +65,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/routers/describe b/gcloud/alpha/edge-cloud/networking/routers/describe index b188bffe8..b81df6b2f 100644 --- a/gcloud/alpha/edge-cloud/networking/routers/describe +++ b/gcloud/alpha/edge-cloud/networking/routers/describe @@ -59,7 +59,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/routers/get-status b/gcloud/alpha/edge-cloud/networking/routers/get-status new file mode 100644 index 000000000..e98d7b4e3 --- /dev/null +++ b/gcloud/alpha/edge-cloud/networking/routers/get-status @@ -0,0 +1,65 @@ +NAME + gcloud alpha edge-cloud networking routers get-status - get the status of a + specified Distributed Cloud Edge Network router + +SYNOPSIS + gcloud alpha edge-cloud networking routers get-status + (ROUTER : --location=LOCATION --zone=ZONE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get the status of a specified Distributed Cloud Edge Network + router. + +EXAMPLES + To get the status of the Distributed Cloud Edge Network router 'my-router' + in edge zone 'us-central1-edge-den1' , run: + + $ gcloud alpha edge-cloud networking routers get-status my-router \ + --location=us-central1 --zone=us-central1-edge-den1 + +POSITIONAL ARGUMENTS + Router resource - The router to get status. 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 router on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + ROUTER + ID of the router or fully qualified identifier for the router. To set + the router attribute: + ▸ provide the argument router on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The Cloud location for the router. To set the location attribute: + ▸ provide the argument router on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --zone=ZONE + The zone of the router. To set the zone attribute: + ▸ provide the argument router on the command line with a fully + specified name; + ▸ provide the argument --zone on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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/edge-cloud/networking/routers/help b/gcloud/alpha/edge-cloud/networking/routers/help index 7cda5f9c4..89a82b5a7 100644 --- a/gcloud/alpha/edge-cloud/networking/routers/help +++ b/gcloud/alpha/edge-cloud/networking/routers/help @@ -31,6 +31,10 @@ COMMANDS describe (ALPHA) Show details about the Distributed Cloud Edge Network router. + get-status + (ALPHA) Get the status of a specified Distributed Cloud Edge Network + router. + list (ALPHA) List Distributed Cloud Edge Network routers. diff --git a/gcloud/alpha/edge-cloud/networking/routers/list b/gcloud/alpha/edge-cloud/networking/routers/list index f1b6739ec..4064179a8 100644 --- a/gcloud/alpha/edge-cloud/networking/routers/list +++ b/gcloud/alpha/edge-cloud/networking/routers/list @@ -86,7 +86,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/subnets/create b/gcloud/alpha/edge-cloud/networking/subnets/create index f93f2ac6c..4d60cdbc4 100644 --- a/gcloud/alpha/edge-cloud/networking/subnets/create +++ b/gcloud/alpha/edge-cloud/networking/subnets/create @@ -98,7 +98,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/subnets/delete b/gcloud/alpha/edge-cloud/networking/subnets/delete index 0e9c9d010..3c1d4091f 100644 --- a/gcloud/alpha/edge-cloud/networking/subnets/delete +++ b/gcloud/alpha/edge-cloud/networking/subnets/delete @@ -65,7 +65,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/subnets/describe b/gcloud/alpha/edge-cloud/networking/subnets/describe index 3a35495fe..ab6c2ff2a 100644 --- a/gcloud/alpha/edge-cloud/networking/subnets/describe +++ b/gcloud/alpha/edge-cloud/networking/subnets/describe @@ -59,7 +59,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/networking/subnets/list b/gcloud/alpha/edge-cloud/networking/subnets/list index 74c6ddc4b..737b52c99 100644 --- a/gcloud/alpha/edge-cloud/networking/subnets/list +++ b/gcloud/alpha/edge-cloud/networking/subnets/list @@ -86,7 +86,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the edgenetwork/v1alpha1 API. The full documentation for - this API can be found at: go/gmec-nas + this API can be found at: + https://cloud.google.com/distributed-cloud-edge/docs NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/functions/deploy b/gcloud/alpha/functions/deploy index d870e49bc..7e072ab21 100644 --- a/gcloud/alpha/functions/deploy +++ b/gcloud/alpha/functions/deploy @@ -173,9 +173,11 @@ FLAGS ◆ nodejs14: Node.js 14 ◆ nodejs16: Node.js 16 ◆ php74: PHP 7.4 + ◆ php81: PHP 8.1 (preview) ◆ python37: Python 3.7 ◆ python38: Python 3.8 ◆ python39: Python 3.9 + ◆ python310: Python 3.10 (preview) ◆ go111: Go 1.11 ◆ go113: Go 1.13 ◆ go116: Go 1.16 diff --git a/gcloud/alpha/iam/service-accounts/sign-jwt b/gcloud/alpha/iam/service-accounts/sign-jwt index 83b93ca6c..968844b3c 100644 --- a/gcloud/alpha/iam/service-accounts/sign-jwt +++ b/gcloud/alpha/iam/service-accounts/sign-jwt @@ -48,7 +48,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud iam service-accounts sign-jwt $ gcloud beta iam service-accounts sign-jwt diff --git a/gcloud/alpha/iam/workload-identity-pools/create-cred-config b/gcloud/alpha/iam/workload-identity-pools/create-cred-config index a3985043e..b598a89ed 100644 --- a/gcloud/alpha/iam/workload-identity-pools/create-cred-config +++ b/gcloud/alpha/iam/workload-identity-pools/create-cred-config @@ -97,7 +97,7 @@ OPTIONAL FLAGS The format of the credential source (JSON or text). --enable-imdsv2 - Adds the AWS IMDSv2 session token url to the credential source to + Adds the AWS IMDSv2 session token Url to the credential source to enforce the AWS IMDSv2 flow. --service-account=SERVICE_ACCOUNT diff --git a/gcloud/alpha/run/help b/gcloud/alpha/run/help index 75bce08c5..d2a769367 100644 --- a/gcloud/alpha/run/help +++ b/gcloud/alpha/run/help @@ -26,6 +26,9 @@ GROUPS domain-mappings (ALPHA) View and manage your Cloud Run domain mappings. + integrations + (ALPHA) View and manage your Cloud Run (fully managed) integrations. + jobs (ALPHA) View and manage your Cloud Run jobs. diff --git a/gcloud/alpha/run/integrations/create b/gcloud/alpha/run/integrations/create new file mode 100644 index 000000000..e0e7005cf --- /dev/null +++ b/gcloud/alpha/run/integrations/create @@ -0,0 +1,57 @@ +NAME + gcloud alpha run integrations create - create a Cloud Run Integration + +SYNOPSIS + gcloud alpha run integrations create --service=SERVICE --type=TYPE + [--name=NAME] [--parameters=[PARAMETER=VALUE,...]] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Cloud Run Integration. + +EXAMPLES + To create and attach a redis instance to a Cloud Run service + + $ gcloud alpha run integrations create --type=redis \ + --service=myservice + + To attach a custom domain to a Cloud Run service + + $ gcloud alpha run integrations create --type=custom-domain \ + --service=myservice --parameters=domain=mydomain.com + +REQUIRED FLAGS + --service=SERVICE + Name of the Cloud Run service to attach to the integration. + + --type=TYPE + Type of the integration. To see available types and usage, use "gcloud + run integrations types list" command. + +OPTIONAL FLAGS + --name=NAME + Name of the integration. + + --parameters=[PARAMETER=VALUE,...] + Comma-separated list of parameter names and values. Names must be one + of the parameters shown when describing the integration type. Only + simple values can be specified with this flag. + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/run/integrations/delete b/gcloud/alpha/run/integrations/delete new file mode 100644 index 000000000..777949791 --- /dev/null +++ b/gcloud/alpha/run/integrations/delete @@ -0,0 +1,39 @@ +NAME + gcloud alpha run integrations delete - delete a Cloud Run Integration and + its associated resources + +SYNOPSIS + gcloud alpha run integrations delete NAME [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Cloud Run Integration and its associated resources. + +EXAMPLES + To delete a redis integration and the associated resources + + $ gcloud alpha run integrations delete my-redis-integration + +POSITIONAL ARGUMENTS + NAME + Name of the integration. + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --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/run/integrations/describe b/gcloud/alpha/run/integrations/describe new file mode 100644 index 000000000..628d0af0f --- /dev/null +++ b/gcloud/alpha/run/integrations/describe @@ -0,0 +1,38 @@ +NAME + gcloud alpha run integrations describe - describe a Cloud Run Integration + +SYNOPSIS + gcloud alpha run integrations describe NAME [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Cloud Run Integration. + +EXAMPLES + To describe an integration + + $ gcloud alpha run integrations describe my-redis-integration + +POSITIONAL ARGUMENTS + NAME + Name of the integration. + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --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/run/integrations/help b/gcloud/alpha/run/integrations/help new file mode 100644 index 000000000..cf0234dec --- /dev/null +++ b/gcloud/alpha/run/integrations/help @@ -0,0 +1,57 @@ +NAME + gcloud alpha run integrations - view and manage your Cloud Run + (fully managed) integrations + +SYNOPSIS + gcloud alpha run integrations GROUP | COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This set of commands can be used to view and manage your Cloud Run + integrations. + +EXAMPLES + To list your existing integrations, run: + + $ gcloud alpha run integrations list + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + types + (ALPHA) View available Cloud Run (fully managed) integrations types. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a Cloud Run Integration. + + delete + (ALPHA) Delete a Cloud Run Integration and its associated resources. + + describe + (ALPHA) Describe a Cloud Run Integration. + + list + (ALPHA) List Cloud Run Integrations. + + update + (ALPHA) Update a Cloud Run Integration. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/run/integrations/list b/gcloud/alpha/run/integrations/list new file mode 100644 index 000000000..e9065283e --- /dev/null +++ b/gcloud/alpha/run/integrations/list @@ -0,0 +1,82 @@ +NAME + gcloud alpha run integrations list - list Cloud Run Integrations + +SYNOPSIS + gcloud alpha run integrations list [--region=REGION] [--service=SERVICE] + [--type=TYPE] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Cloud Run Integrations. + +EXAMPLES + List all Cloud Run Integrations within the current project + + $ gcloud alpha run integrations list + + List all Cloud Run Integrations of a particular type + + $ gcloud alpha run integrations list --type=redis + + List all Cloud Run Integrations attached to a particular Service + + $ gcloud alpha run integrations list --service=my-service + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + --service=SERVICE + Filter Integrations by Name of Cloud Run service. + + --type=TYPE + Filter Integrations by Type of Integration. + +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/run/integrations/types/describe b/gcloud/alpha/run/integrations/types/describe new file mode 100644 index 000000000..7d6fce443 --- /dev/null +++ b/gcloud/alpha/run/integrations/types/describe @@ -0,0 +1,39 @@ +NAME + gcloud alpha run integrations types describe - describes a Cloud Run + Integration + +SYNOPSIS + gcloud alpha run integrations types describe TYPE [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describes a Cloud Run Integration. + +EXAMPLES + To describe an integration type + + $ gcloud alpha run integrations types describe [TYPE] + +POSITIONAL ARGUMENTS + TYPE + Type of the integration. + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --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/run/integrations/types/help b/gcloud/alpha/run/integrations/types/help new file mode 100644 index 000000000..fbbfea798 --- /dev/null +++ b/gcloud/alpha/run/integrations/types/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha run integrations types - view available Cloud Run + (fully managed) integrations types + +SYNOPSIS + gcloud alpha run integrations types COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This set of commands can be used to view Cloud Run integrations + types. + +EXAMPLES + To list available integrations types, run: + + $ gcloud alpha run integrations types list + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describes a Cloud Run Integration. + + list + (ALPHA) Lists Cloud Run Integration Types. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/run/integrations/types/list b/gcloud/alpha/run/integrations/types/list new file mode 100644 index 000000000..028a6a261 --- /dev/null +++ b/gcloud/alpha/run/integrations/types/list @@ -0,0 +1,68 @@ +NAME + gcloud alpha run integrations types list - lists Cloud Run Integration + Types + +SYNOPSIS + gcloud alpha run integrations types list [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lists Cloud Run Integration Types. + +EXAMPLES + To list all integration types + + $ gcloud alpha run integrations types list + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/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/run/integrations/update b/gcloud/alpha/run/integrations/update new file mode 100644 index 000000000..262d253aa --- /dev/null +++ b/gcloud/alpha/run/integrations/update @@ -0,0 +1,54 @@ +NAME + gcloud alpha run integrations update - update a Cloud Run Integration + +SYNOPSIS + gcloud alpha run integrations update NAME + [--parameters=[PARAMETER=VALUE,...]] [--region=REGION] + [--add-service=ADD_SERVICE | --remove-service=REMOVE_SERVICE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Cloud Run Integration. + +EXAMPLES + To update a redis integration to change the cache size + + $ gcloud alpha run integrations update redis-integration \ + --parameters=memory-size-gb=5 + +POSITIONAL ARGUMENTS + NAME + Name of the integration. + +FLAGS + --parameters=[PARAMETER=VALUE,...] + Comma-separated list of parameter names and values. Names must be one + of the parameters shown when describing the integration type. Only + simple values can be specified with this flag. + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + At most one of these can be specified: + + --add-service=ADD_SERVICE + Name of the Cloud Run service to attach to the integration. + + --remove-service=REMOVE_SERVICE + Name of the Cloud Run service to remove from the integration. + +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/anthos/config/controller/create b/gcloud/anthos/config/controller/create index ebb109a55..147998c41 100644 --- a/gcloud/anthos/config/controller/create +++ b/gcloud/anthos/config/controller/create @@ -43,7 +43,8 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Config Controller instance location. Currently, only - us-central1 is supported. To set the location attribute: + us-central1, us-east1, northamerica-northeast1, and asia-northeast1 + are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/anthos/config/controller/delete b/gcloud/anthos/config/controller/delete index 9e5a50648..21372ebc0 100644 --- a/gcloud/anthos/config/controller/delete +++ b/gcloud/anthos/config/controller/delete @@ -37,8 +37,8 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. - Currently, only us-central1 is supported. To set the location - attribute: + Currently, only us-central1, us-east1, northamerica-northeast1, and + asia-northeast1 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/anthos/config/controller/describe b/gcloud/anthos/config/controller/describe index c5ce1e8ce..d806eb50c 100644 --- a/gcloud/anthos/config/controller/describe +++ b/gcloud/anthos/config/controller/describe @@ -39,8 +39,8 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. - Currently, only us-central1 is supported. To set the location - attribute: + Currently, only us-central1, us-east1, northamerica-northeast1, and + asia-northeast1 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/anthos/config/controller/get-config-connector-identity b/gcloud/anthos/config/controller/get-config-connector-identity new file mode 100644 index 000000000..9dae4f8a8 --- /dev/null +++ b/gcloud/anthos/config/controller/get-config-connector-identity @@ -0,0 +1,41 @@ +NAME + gcloud anthos config controller get-config-connector-identity - fetch + default Config Connector identity + +SYNOPSIS + gcloud anthos config controller get-config-connector-identity NAME + --location=LOCATION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud anthos config controller get-config-connector-identity prints the + default Config Connector Google Service Account in a specific Anthos Config + Controller. + +EXAMPLES + To print the default Config Connector identity used by your Config + Controller 'main' in the location 'us-central1', run: + + $ gcloud anthos config controller get-config-connector-identity \ + main --location=us-central1 + +POSITIONAL ARGUMENTS + NAME + Name of the Anthos Config Controller. + +REQUIRED FLAGS + --location=LOCATION + The location (region) of the Anthos Config Controller. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha anthos config controller get-config-connector-identity + diff --git a/gcloud/anthos/config/controller/help b/gcloud/anthos/config/controller/help index cc7446293..2708ff21a 100644 --- a/gcloud/anthos/config/controller/help +++ b/gcloud/anthos/config/controller/help @@ -24,6 +24,9 @@ COMMANDS describe Describe Anthos Config Controller instances. + get-config-connector-identity + Fetch default Config Connector identity. + get-credentials Fetch credentials for a running Anthos Config Controller. diff --git a/gcloud/anthos/config/operations/describe b/gcloud/anthos/config/operations/describe index 8651ae27b..8fbc91160 100644 --- a/gcloud/anthos/config/operations/describe +++ b/gcloud/anthos/config/operations/describe @@ -39,8 +39,8 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. - Currently, only us-central1 is supported. To set the location - attribute: + Currently, only us-central1, us-east1, northamerica-northeast1, and + asia-northeast1 are supported. To set the location attribute: ▸ provide the argument operation on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/auth/application-default/login b/gcloud/auth/application-default/login index d2be2132d..56a7b021f 100644 --- a/gcloud/auth/application-default/login +++ b/gcloud/auth/application-default/login @@ -45,8 +45,23 @@ EXAMPLES FLAGS --no-browser - Use this flag to authenticate client libraries on a machine without a - web browser. + Use this flag to authenticate the client libraries on a machine without + a web browser. + + Run gcloud auth login --no-browser and follow these steps: + + 1. Copy the long command that begins with "gcloud auth login + --remote-bootstrap=". + + 2. Paste and run this command on the command line of a different, + trusted machine that has local installations of both a web browser and + the gcloud CLI tool version 372.0 or later. + + 3. Copy the long URL output from the machine with the web browser. + + 4. Paste the long URL back to the first machine under the prompt, + "Enter the output of the above command", and press Enter to complete + the authorization. --client-id-file=CLIENT_ID_FILE A file containing your own client id to use to login. If @@ -81,8 +96,8 @@ FLAGS it is not possible to launch a browser, prints a URL to standard output to be copied. - The --[no-]launch-browser flags are deprecated and will be removed in - version 383.0.0 (04/26/2022). Use --no-browser to replace + The --[no-]launch-browser flags are deprecated and will be removed on + June 7th 2022 (Release 389.0.0). Use --no-browser to replace --no-launch-browser. Enabled by default, use --no-launch-browser to disable. diff --git a/gcloud/auth/login b/gcloud/auth/login index c8f653e32..f8bd6ca88 100644 --- a/gcloud/auth/login +++ b/gcloud/auth/login @@ -60,9 +60,24 @@ FLAGS Minimal user output. --no-browser - Use this flag to authenticate gcloud CLI on a machine without a web + Use this flag to authenticate the gcloud CLI on a machine without a web browser. + Run gcloud auth login --no-browser and follow these steps: + + 1. Copy the long command that begins with "gcloud auth login + --remote-bootstrap=". + + 2. Paste and run this command on the command line of a different, + trusted machine that has local installations of both a web browser and + the gcloud CLI tool version 372.0 or later. + + 3. Copy the long URL output from the machine with the web browser. + + 4. Paste the long URL back to the first machine under the prompt, + "Enter the output of the above command", and press Enter to complete + the authorization. + --cred-file=CRED_FILE Path to the external account configuration file (workload identity pool, generated by the Cloud Console or gcloud iam @@ -81,8 +96,8 @@ FLAGS it is not possible to launch a browser, prints a URL to standard output to be copied. - The --[no-]launch-browser flags are deprecated and will be removed in - version 383.0.0 (04/26/2022). Use --no-browser to replace + The --[no-]launch-browser flags are deprecated and will be removed on + June 7th 2022 (Release 389.0.0). Use --no-browser to replace --no-launch-browser. Enabled by default, use --no-launch-browser to disable. diff --git a/gcloud/beta/auth/application-default/login b/gcloud/beta/auth/application-default/login index 1cf859c76..4e4eb89f6 100644 --- a/gcloud/beta/auth/application-default/login +++ b/gcloud/beta/auth/application-default/login @@ -45,8 +45,23 @@ EXAMPLES FLAGS --no-browser - Use this flag to authenticate client libraries on a machine without a - web browser. + Use this flag to authenticate the client libraries on a machine without + a web browser. + + Run gcloud auth login --no-browser and follow these steps: + + 1. Copy the long command that begins with "gcloud auth login + --remote-bootstrap=". + + 2. Paste and run this command on the command line of a different, + trusted machine that has local installations of both a web browser and + the gcloud CLI tool version 372.0 or later. + + 3. Copy the long URL output from the machine with the web browser. + + 4. Paste the long URL back to the first machine under the prompt, + "Enter the output of the above command", and press Enter to complete + the authorization. --client-id-file=CLIENT_ID_FILE A file containing your own client id to use to login. If @@ -81,8 +96,8 @@ FLAGS it is not possible to launch a browser, prints a URL to standard output to be copied. - The --[no-]launch-browser flags are deprecated and will be removed in - version 383.0.0 (04/26/2022). Use --no-browser to replace + The --[no-]launch-browser flags are deprecated and will be removed on + June 7th 2022 (Release 389.0.0). Use --no-browser to replace --no-launch-browser. Enabled by default, use --no-launch-browser to disable. diff --git a/gcloud/beta/auth/login b/gcloud/beta/auth/login index 2ef1a8ad8..ec59030c1 100644 --- a/gcloud/beta/auth/login +++ b/gcloud/beta/auth/login @@ -61,9 +61,24 @@ FLAGS Minimal user output. --no-browser - Use this flag to authenticate gcloud CLI on a machine without a web + Use this flag to authenticate the gcloud CLI on a machine without a web browser. + Run gcloud auth login --no-browser and follow these steps: + + 1. Copy the long command that begins with "gcloud auth login + --remote-bootstrap=". + + 2. Paste and run this command on the command line of a different, + trusted machine that has local installations of both a web browser and + the gcloud CLI tool version 372.0 or later. + + 3. Copy the long URL output from the machine with the web browser. + + 4. Paste the long URL back to the first machine under the prompt, + "Enter the output of the above command", and press Enter to complete + the authorization. + --cred-file=CRED_FILE Path to the external account configuration file (workload identity pool, generated by the Cloud Console or gcloud iam @@ -82,8 +97,8 @@ FLAGS it is not possible to launch a browser, prints a URL to standard output to be copied. - The --[no-]launch-browser flags are deprecated and will be removed in - version 383.0.0 (04/26/2022). Use --no-browser to replace + The --[no-]launch-browser flags are deprecated and will be removed on + June 7th 2022 (Release 389.0.0). Use --no-browser to replace --no-launch-browser. Enabled by default, use --no-launch-browser to disable. diff --git a/gcloud/beta/compute/backend-services/create b/gcloud/beta/compute/backend-services/create index 97167eea6..9beae17b3 100644 --- a/gcloud/beta/compute/backend-services/create +++ b/gcloud/beta/compute/backend-services/create @@ -534,36 +534,39 @@ FLAGS same backend VM while that VM remains healthy. GENERATED_COOKIE (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, - INTERNAL_SELF_MANAGED, or EXTERNAL) If the --load-balancing-scheme - is EXTERNAL or EXTERNAL_MANAGED, routes requests to backend VMs or - endpoints in a NEG, based on the contents of the GCLB cookie set by - the load balancer. Only applicable when --protocol is HTTP, HTTPS, - or HTTP2. If the --load-balancing-scheme is INTERNAL_MANAGED or + INTERNAL_SELF_MANAGED, EXTERNAL_MANAGED, or EXTERNAL) If the + --load-balancing-scheme is EXTERNAL or EXTERNAL_MANAGED, routes + requests to backend VMs or endpoints in a NEG, based on the + contents of the GCLB cookie set by the load balancer. Only + applicable when --protocol is HTTP, HTTPS, or HTTP2. If the + --load-balancing-scheme is INTERNAL_MANAGED or INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints in a NEG, based on the contents of the GCILB cookie set by the proxy. (If no cookie is present, the proxy chooses a backend VM or endpoint and sends a Set-Cookie response for future requests.) If the --load-balancing-scheme is INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints in a NEG, based on the - contents of a cookie set by Traffic Director. + contents of a cookie set by Traffic Director. This session affinity + is only valid if the load balancing locality policy is either + RING_HASH or MAGLEV. HEADER_FIELD - (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or - INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints - in a NEG based on the value of the HTTP header named in the - --custom-request-header flag. This session affinity is only valid - if the load balancing locality policy is either RING_HASH or MAGLEV - and the backend service's consistent hash specifies the name of the - HTTP header. + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, + EXTERNAL_MANAGED, or INTERNAL_SELF_MANAGED) Route requests to + backend VMs or endpoints in a NEG based on the value of the HTTP + header named in the --custom-request-header flag. This session + affinity is only valid if the load balancing locality policy is + either RING_HASH or MAGLEV and the backend service's consistent + hash specifies the name of the HTTP header. HTTP_COOKIE - (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or - INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints - in a NEG, based on an HTTP cookie named in the HTTP_COOKIE flag - (with the optional --affinity-cookie-ttl flag). If the client has - not provided the cookie, the proxy generates the cookie and returns - it to the client in a Set-Cookie header. This session affinity is - only valid if the load balancing locality policy is either - RING_HASH or MAGLEV and the backend service's consistent hash - specifies the HTTP cookie. + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, + EXTERNAL_MANAGED or INTERNAL_SELF_MANAGED) Route requests to + backend VMs or endpoints in a NEG, based on an HTTP cookie named in + the HTTP_COOKIE flag (with the optional --affinity-cookie-ttl + flag). If the client has not provided the cookie, the proxy + generates the cookie and returns it to the client in a Set-Cookie + header. This session affinity is only valid if the load balancing + locality policy is either RING_HASH or MAGLEV and the backend + service's consistent hash specifies the HTTP cookie. NONE Session affinity is disabled. diff --git a/gcloud/beta/compute/backend-services/update b/gcloud/beta/compute/backend-services/update index b6d552232..4874d11a0 100644 --- a/gcloud/beta/compute/backend-services/update +++ b/gcloud/beta/compute/backend-services/update @@ -340,36 +340,39 @@ FLAGS same backend VM while that VM remains healthy. GENERATED_COOKIE (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, - INTERNAL_SELF_MANAGED, or EXTERNAL) If the --load-balancing-scheme - is EXTERNAL or EXTERNAL_MANAGED, routes requests to backend VMs or - endpoints in a NEG, based on the contents of the GCLB cookie set by - the load balancer. Only applicable when --protocol is HTTP, HTTPS, - or HTTP2. If the --load-balancing-scheme is INTERNAL_MANAGED or + INTERNAL_SELF_MANAGED, EXTERNAL_MANAGED, or EXTERNAL) If the + --load-balancing-scheme is EXTERNAL or EXTERNAL_MANAGED, routes + requests to backend VMs or endpoints in a NEG, based on the + contents of the GCLB cookie set by the load balancer. Only + applicable when --protocol is HTTP, HTTPS, or HTTP2. If the + --load-balancing-scheme is INTERNAL_MANAGED or INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints in a NEG, based on the contents of the GCILB cookie set by the proxy. (If no cookie is present, the proxy chooses a backend VM or endpoint and sends a Set-Cookie response for future requests.) If the --load-balancing-scheme is INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints in a NEG, based on the - contents of a cookie set by Traffic Director. + contents of a cookie set by Traffic Director. This session affinity + is only valid if the load balancing locality policy is either + RING_HASH or MAGLEV. HEADER_FIELD - (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or - INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints - in a NEG based on the value of the HTTP header named in the - --custom-request-header flag. This session affinity is only valid - if the load balancing locality policy is either RING_HASH or MAGLEV - and the backend service's consistent hash specifies the name of the - HTTP header. + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, + EXTERNAL_MANAGED, or INTERNAL_SELF_MANAGED) Route requests to + backend VMs or endpoints in a NEG based on the value of the HTTP + header named in the --custom-request-header flag. This session + affinity is only valid if the load balancing locality policy is + either RING_HASH or MAGLEV and the backend service's consistent + hash specifies the name of the HTTP header. HTTP_COOKIE - (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or - INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints - in a NEG, based on an HTTP cookie named in the HTTP_COOKIE flag - (with the optional --affinity-cookie-ttl flag). If the client has - not provided the cookie, the proxy generates the cookie and returns - it to the client in a Set-Cookie header. This session affinity is - only valid if the load balancing locality policy is either - RING_HASH or MAGLEV and the backend service's consistent hash - specifies the HTTP cookie. + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, + EXTERNAL_MANAGED or INTERNAL_SELF_MANAGED) Route requests to + backend VMs or endpoints in a NEG, based on an HTTP cookie named in + the HTTP_COOKIE flag (with the optional --affinity-cookie-ttl + flag). If the client has not provided the cookie, the proxy + generates the cookie and returns it to the client in a Set-Cookie + header. This session affinity is only valid if the load balancing + locality policy is either RING_HASH or MAGLEV and the backend + service's consistent hash specifies the HTTP cookie. NONE Session affinity is disabled. diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index eecc3cfbd..faa6ee7ef 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -841,7 +841,7 @@ FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. Sole Tenancy. diff --git a/gcloud/beta/compute/instance-templates/create-with-container b/gcloud/beta/compute/instance-templates/create-with-container index 33a72aebc..38a77a9a3 100644 --- a/gcloud/beta/compute/instance-templates/create-with-container +++ b/gcloud/beta/compute/instance-templates/create-with-container @@ -26,9 +26,8 @@ SYNOPSIS [--disk=[auto-delete=AUTO-DELETE], [boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]] [--labels=[KEY=VALUE,...]] - [--local-ssd=[device-name=DEVICE-NAME], - [interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE] - [--maintenance-policy=MAINTENANCE_POLICY] + [--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]] + [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] [--min-cpu-platform=PLATFORM] [--network=NETWORK] @@ -390,11 +389,9 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - --local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE],[size=SIZE] + --local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE] Attaches a local SSD to the instances. - This flag is currently in BETA and might change without notice. - device-name Optional. A name that indicates the disk name the guest operating system will see. Can only be specified if interface is SCSI. If @@ -406,13 +403,6 @@ FLAGS supported by more guest operating systems. NVME might provide higher performance. - size - Optional. Size of the SSD disk. The value must be a whole number - followed by a size unit of KB for kilobyte, MB for megabyte, GB for - gigabyte, or TB for terabyte. For example, 750GB will produce a 750 - gigabyte disk. The size must be a multiple of 375 GB and the - default is 375 GB. For Alpha API only. - --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of available machine types, run 'gcloud compute machine-types list'. If @@ -722,7 +712,7 @@ FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. At most one of these can be specified: diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index ef3f425f9..d9622098c 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -743,7 +743,7 @@ OPTIONAL FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. --source-snapshot=SOURCE_SNAPSHOT The name of the source disk snapshot that the instance boot disk will diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index b24a00945..991dd4040 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -924,7 +924,7 @@ FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. --source-snapshot=SOURCE_SNAPSHOT The name of the source disk snapshot that the instance boot disk will diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index ff0501cd0..b627f4b27 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -29,9 +29,8 @@ SYNOPSIS [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--labels=[KEY=VALUE,...]] - [--local-ssd=[device-name=DEVICE-NAME], - [interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE] - [--maintenance-policy=MAINTENANCE_POLICY] + [--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]] + [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] [--min-cpu-platform=PLATFORM] [--network=NETWORK] @@ -424,11 +423,9 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - --local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE],[size=SIZE] + --local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE] Attaches a local SSD to the instances. - This flag is currently in BETA and might change without notice. - device-name Optional. A name that indicates the disk name the guest operating system will see. Can only be specified if interface is SCSI. If @@ -440,13 +437,6 @@ FLAGS supported by more guest operating systems. NVME might provide higher performance. - size - Optional. Size of the SSD disk. The value must be a whole number - followed by a size unit of KB for kilobyte, MB for megabyte, GB for - gigabyte, or TB for terabyte. For example, 750GB will produce a 750 - gigabyte disk. The size must be a multiple of 375 GB and the - default is 375 GB. For Alpha API only. - --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of available machine types, run 'gcloud compute machine-types list'. If @@ -805,7 +795,7 @@ FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. At most one of these can be specified: diff --git a/gcloud/beta/compute/network-endpoint-groups/create b/gcloud/beta/compute/network-endpoint-groups/create index 8c0f62f07..c7c4bbb7d 100644 --- a/gcloud/beta/compute/network-endpoint-groups/create +++ b/gcloud/beta/compute/network-endpoint-groups/create @@ -58,6 +58,11 @@ FLAGS This is only supported for NEGs with endpoint type gce-vm-ip-port, non-gcp-private-ip-port, gce-vm-ip, or private-service-connect. + For Private Service Connect NEGs, you can optionally specify --network + and --subnet if --psc-target-service points to a published service. If + --psc-target-service points to the regional service endpoint of a + Google API, do not specify --network or --subnet. + --network-endpoint-type=NETWORK_ENDPOINT_TYPE; default="gce-vm-ip-port" Determines the spec of endpoints attached to this group. @@ -120,8 +125,12 @@ FLAGS If not specified, network endpoints may belong to any subnetwork in the region where the network endpoint group is created. - This is only supported for NEGs with endpoint type gce-vm-ip-port or - gce-vm-ip. + This is only supported for NEGs with endpoint type gce-vm-ip-port, + gce-vm-ip, or private-service-connect. For Private Service Connect + NEGs, you can optionally specify --network and --subnet if + --psc-target-service points to a published service. If + --psc-target-service points to the regional service endpoint of a + Google API, do not specify --network or --subnet. The serverless routing configurations are only valid when endpoint type of the network endpoint group is serverless. diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index 330442b56..d4852a429 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -936,9 +936,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 04fd3a413..368c0184f 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -968,9 +968,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index ed450c632..2339d15e8 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -970,9 +970,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 273225f46..1288239d9 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -31,11 +31,11 @@ DESCRIPTION EXAMPLES To set the project property in the core section, run: - $ gcloud beta config set project myProject + $ gcloud beta config set project PROJECT_ID To set the zone property in the compute section, run: - $ gcloud beta config set compute/zone asia-east1-b + $ gcloud beta config set compute/zone ZONE_NAME To disable prompting for scripting, run: @@ -983,9 +983,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 51ca4139f..9c3a53723 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -944,9 +944,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index f061c05b6..edb446d98 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -1219,7 +1219,7 @@ FLAGS Flags to specify identity for autoprovisioned nodes: --autoprovisioning-scopes=[SCOPE,...] - The scopes be used by node instances in autoprovisioned node + The scopes to be used by node instances in autoprovisioned node pools. Multiple scopes can be specified, separated by commas. For information on defaults, look at: https://cloud.google.com/sdk/gcloud/reference/container/clusters/create#--scopes diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index b7c166c3a..b06ca86d1 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -835,9 +835,9 @@ REQUIRED FLAGS Flags to specify identity for autoprovisioned nodes: --autoprovisioning-scopes=[SCOPE,...] - The scopes be used by node instances in autoprovisioned node - pools. Multiple scopes can be specified, separated by commas. - For information on defaults, look at: + The scopes to be used by node instances in autoprovisioned + node pools. Multiple scopes can be specified, separated by + commas. For information on defaults, look at: https://cloud.google.com/sdk/gcloud/reference/container/clusters/create#--scopes --autoprovisioning-service-account=AUTOPROVISIONING_SERVICE_ACCOUNT diff --git a/gcloud/beta/dns/policies/delete b/gcloud/beta/dns/policies/delete index 2250fe41e..4169d2cc8 100644 --- a/gcloud/beta/dns/policies/delete +++ b/gcloud/beta/dns/policies/delete @@ -39,7 +39,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dns/v1beta2 API. The full documentation for this API - can be found at: https://developers.google.com/cloud-dns + can be found at: https://cloud.google.com/dns/docs NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/dns/policies/describe b/gcloud/beta/dns/policies/describe index e9f8e86e5..faa6c2b3a 100644 --- a/gcloud/beta/dns/policies/describe +++ b/gcloud/beta/dns/policies/describe @@ -39,7 +39,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dns/v1 API. The full documentation for this API can - be found at: https://developers.google.com/cloud-dns + be found at: https://cloud.google.com/dns/docs NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/dns/policies/list b/gcloud/beta/dns/policies/list index a544d3a66..445263dae 100644 --- a/gcloud/beta/dns/policies/list +++ b/gcloud/beta/dns/policies/list @@ -61,7 +61,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dns/v1beta2 API. The full documentation for this API - can be found at: https://developers.google.com/cloud-dns + can be found at: https://cloud.google.com/dns/docs NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/functions/deploy b/gcloud/beta/functions/deploy index 2f6d2fba2..9d00ecddf 100644 --- a/gcloud/beta/functions/deploy +++ b/gcloud/beta/functions/deploy @@ -166,9 +166,11 @@ FLAGS ◆ nodejs14: Node.js 14 ◆ nodejs16: Node.js 16 ◆ php74: PHP 7.4 + ◆ php81: PHP 8.1 (preview) ◆ python37: Python 3.7 ◆ python38: Python 3.8 ◆ python39: Python 3.9 + ◆ python310: Python 3.10 (preview) ◆ go111: Go 1.11 ◆ go113: Go 1.13 ◆ go116: Go 1.16 diff --git a/gcloud/beta/iam/service-accounts/sign-jwt b/gcloud/beta/iam/service-accounts/sign-jwt index 76eae12a6..dc3bf69af 100644 --- a/gcloud/beta/iam/service-accounts/sign-jwt +++ b/gcloud/beta/iam/service-accounts/sign-jwt @@ -44,8 +44,10 @@ SEE ALSO https://cloud.google.com/appengine/docs/java/appidentity/. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud iam service-accounts sign-jwt $ gcloud alpha iam service-accounts sign-jwt diff --git a/gcloud/beta/iam/workload-identity-pools/create-cred-config b/gcloud/beta/iam/workload-identity-pools/create-cred-config index cd0d5a7cc..f32decef1 100644 --- a/gcloud/beta/iam/workload-identity-pools/create-cred-config +++ b/gcloud/beta/iam/workload-identity-pools/create-cred-config @@ -10,7 +10,7 @@ SYNOPSIS [--app-id-uri=APP_ID_URI] [--credential-source-field-name=CREDENTIAL_SOURCE_FIELD_NAME] [--credential-source-headers=[key=value,...]] - [--credential-source-type=CREDENTIAL_SOURCE_TYPE] + [--credential-source-type=CREDENTIAL_SOURCE_TYPE] [--enable-imdsv2] [--service-account=SERVICE_ACCOUNT] [--subject-token-type=SUBJECT_TOKEN_TYPE] [GCLOUD_WIDE_FLAG ...] @@ -43,7 +43,8 @@ EXAMPLES $ gcloud beta iam workload-identity-pools create-cred-config \ projects/$PROJECT_NUMBER/locations/$REGION/\ workloadIdentityPools/$WORKLOAD_POOL_ID/providers/$PROVIDER_ID \ - --service-account=$EMAIL --aws --output-file=credentials.json + --service-account=$EMAIL --aws --enable-imdsv2 \ + --output-file=credentials.json To create an Azure-based credential configuration for your project, run: @@ -95,6 +96,10 @@ OPTIONAL FLAGS --credential-source-type=CREDENTIAL_SOURCE_TYPE The format of the credential source (JSON or text). + --enable-imdsv2 + Adds the AWS IMDSv2 session token Url to the credential source to + enforce the AWS IMDSv2 flow. + --service-account=SERVICE_ACCOUNT The email of the service account to impersonate. diff --git a/gcloud/compute/backend-services/create b/gcloud/compute/backend-services/create index 29c0bdbc6..d47a77c66 100644 --- a/gcloud/compute/backend-services/create +++ b/gcloud/compute/backend-services/create @@ -500,36 +500,39 @@ FLAGS same backend VM while that VM remains healthy. GENERATED_COOKIE (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, - INTERNAL_SELF_MANAGED, or EXTERNAL) If the --load-balancing-scheme - is EXTERNAL or EXTERNAL_MANAGED, routes requests to backend VMs or - endpoints in a NEG, based on the contents of the GCLB cookie set by - the load balancer. Only applicable when --protocol is HTTP, HTTPS, - or HTTP2. If the --load-balancing-scheme is INTERNAL_MANAGED or + INTERNAL_SELF_MANAGED, EXTERNAL_MANAGED, or EXTERNAL) If the + --load-balancing-scheme is EXTERNAL or EXTERNAL_MANAGED, routes + requests to backend VMs or endpoints in a NEG, based on the + contents of the GCLB cookie set by the load balancer. Only + applicable when --protocol is HTTP, HTTPS, or HTTP2. If the + --load-balancing-scheme is INTERNAL_MANAGED or INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints in a NEG, based on the contents of the GCILB cookie set by the proxy. (If no cookie is present, the proxy chooses a backend VM or endpoint and sends a Set-Cookie response for future requests.) If the --load-balancing-scheme is INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints in a NEG, based on the - contents of a cookie set by Traffic Director. + contents of a cookie set by Traffic Director. This session affinity + is only valid if the load balancing locality policy is either + RING_HASH or MAGLEV. HEADER_FIELD - (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or - INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints - in a NEG based on the value of the HTTP header named in the - --custom-request-header flag. This session affinity is only valid - if the load balancing locality policy is either RING_HASH or MAGLEV - and the backend service's consistent hash specifies the name of the - HTTP header. + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, + EXTERNAL_MANAGED, or INTERNAL_SELF_MANAGED) Route requests to + backend VMs or endpoints in a NEG based on the value of the HTTP + header named in the --custom-request-header flag. This session + affinity is only valid if the load balancing locality policy is + either RING_HASH or MAGLEV and the backend service's consistent + hash specifies the name of the HTTP header. HTTP_COOKIE - (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or - INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints - in a NEG, based on an HTTP cookie named in the HTTP_COOKIE flag - (with the optional --affinity-cookie-ttl flag). If the client has - not provided the cookie, the proxy generates the cookie and returns - it to the client in a Set-Cookie header. This session affinity is - only valid if the load balancing locality policy is either - RING_HASH or MAGLEV and the backend service's consistent hash - specifies the HTTP cookie. + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, + EXTERNAL_MANAGED or INTERNAL_SELF_MANAGED) Route requests to + backend VMs or endpoints in a NEG, based on an HTTP cookie named in + the HTTP_COOKIE flag (with the optional --affinity-cookie-ttl + flag). If the client has not provided the cookie, the proxy + generates the cookie and returns it to the client in a Set-Cookie + header. This session affinity is only valid if the load balancing + locality policy is either RING_HASH or MAGLEV and the backend + service's consistent hash specifies the HTTP cookie. NONE Session affinity is disabled. diff --git a/gcloud/compute/backend-services/update b/gcloud/compute/backend-services/update index 67784bc76..05ac49f5f 100644 --- a/gcloud/compute/backend-services/update +++ b/gcloud/compute/backend-services/update @@ -312,36 +312,39 @@ FLAGS same backend VM while that VM remains healthy. GENERATED_COOKIE (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, - INTERNAL_SELF_MANAGED, or EXTERNAL) If the --load-balancing-scheme - is EXTERNAL or EXTERNAL_MANAGED, routes requests to backend VMs or - endpoints in a NEG, based on the contents of the GCLB cookie set by - the load balancer. Only applicable when --protocol is HTTP, HTTPS, - or HTTP2. If the --load-balancing-scheme is INTERNAL_MANAGED or + INTERNAL_SELF_MANAGED, EXTERNAL_MANAGED, or EXTERNAL) If the + --load-balancing-scheme is EXTERNAL or EXTERNAL_MANAGED, routes + requests to backend VMs or endpoints in a NEG, based on the + contents of the GCLB cookie set by the load balancer. Only + applicable when --protocol is HTTP, HTTPS, or HTTP2. If the + --load-balancing-scheme is INTERNAL_MANAGED or INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints in a NEG, based on the contents of the GCILB cookie set by the proxy. (If no cookie is present, the proxy chooses a backend VM or endpoint and sends a Set-Cookie response for future requests.) If the --load-balancing-scheme is INTERNAL_SELF_MANAGED, routes requests to backend VMs or endpoints in a NEG, based on the - contents of a cookie set by Traffic Director. + contents of a cookie set by Traffic Director. This session affinity + is only valid if the load balancing locality policy is either + RING_HASH or MAGLEV. HEADER_FIELD - (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or - INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints - in a NEG based on the value of the HTTP header named in the - --custom-request-header flag. This session affinity is only valid - if the load balancing locality policy is either RING_HASH or MAGLEV - and the backend service's consistent hash specifies the name of the - HTTP header. + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, + EXTERNAL_MANAGED, or INTERNAL_SELF_MANAGED) Route requests to + backend VMs or endpoints in a NEG based on the value of the HTTP + header named in the --custom-request-header flag. This session + affinity is only valid if the load balancing locality policy is + either RING_HASH or MAGLEV and the backend service's consistent + hash specifies the name of the HTTP header. HTTP_COOKIE - (Applicable if --load-balancing-scheme is INTERNAL_MANAGED or - INTERNAL_SELF_MANAGED) Route requests to backend VMs or endpoints - in a NEG, based on an HTTP cookie named in the HTTP_COOKIE flag - (with the optional --affinity-cookie-ttl flag). If the client has - not provided the cookie, the proxy generates the cookie and returns - it to the client in a Set-Cookie header. This session affinity is - only valid if the load balancing locality policy is either - RING_HASH or MAGLEV and the backend service's consistent hash - specifies the HTTP cookie. + (Applicable if --load-balancing-scheme is INTERNAL_MANAGED, + EXTERNAL_MANAGED or INTERNAL_SELF_MANAGED) Route requests to + backend VMs or endpoints in a NEG, based on an HTTP cookie named in + the HTTP_COOKIE flag (with the optional --affinity-cookie-ttl + flag). If the client has not provided the cookie, the proxy + generates the cookie and returns it to the client in a Set-Cookie + header. This session affinity is only valid if the load balancing + locality policy is either RING_HASH or MAGLEV and the backend + service's consistent hash specifies the HTTP cookie. NONE Session affinity is disabled. diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index 1b8dc08b0..95aff9c1e 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -796,7 +796,7 @@ FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. Sole Tenancy. diff --git a/gcloud/compute/instance-templates/create-with-container b/gcloud/compute/instance-templates/create-with-container index c6aa0a23f..f388541b7 100644 --- a/gcloud/compute/instance-templates/create-with-container +++ b/gcloud/compute/instance-templates/create-with-container @@ -676,7 +676,7 @@ FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. At most one of these can be specified: diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index 96faa8991..0a7a3413b 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -733,7 +733,7 @@ OPTIONAL FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. --source-snapshot=SOURCE_SNAPSHOT The name of the source disk snapshot that the instance boot disk will diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index 57137ebb0..dd097dcea 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -878,7 +878,7 @@ FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. --source-snapshot=SOURCE_SNAPSHOT The name of the source disk snapshot that the instance boot disk will diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index 11c3600bb..9c4c19bc4 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -767,7 +767,7 @@ FLAGS practice to use --image-family when the latest version of an image is needed. - By default, debian-10 is assumed for this flag. + By default, debian-11 is assumed for this flag. At most one of these can be specified: diff --git a/gcloud/compute/network-endpoint-groups/create b/gcloud/compute/network-endpoint-groups/create index 98405e9ea..fe712c5c5 100644 --- a/gcloud/compute/network-endpoint-groups/create +++ b/gcloud/compute/network-endpoint-groups/create @@ -54,6 +54,11 @@ FLAGS This is only supported for NEGs with endpoint type gce-vm-ip-port, non-gcp-private-ip-port, gce-vm-ip, or private-service-connect. + For Private Service Connect NEGs, you can optionally specify --network + and --subnet if --psc-target-service points to a published service. If + --psc-target-service points to the regional service endpoint of a + Google API, do not specify --network or --subnet. + --network-endpoint-type=NETWORK_ENDPOINT_TYPE; default="gce-vm-ip-port" Determines the spec of endpoints attached to this group. @@ -116,8 +121,12 @@ FLAGS If not specified, network endpoints may belong to any subnetwork in the region where the network endpoint group is created. - This is only supported for NEGs with endpoint type gce-vm-ip-port or - gce-vm-ip. + This is only supported for NEGs with endpoint type gce-vm-ip-port, + gce-vm-ip, or private-service-connect. For Private Service Connect + NEGs, you can optionally specify --network and --subnet if + --psc-target-service points to a published service. If + --psc-target-service points to the regional service endpoint of a + Google API, do not specify --network or --subnet. The serverless routing configurations are only valid when endpoint type of the network endpoint group is serverless. diff --git a/gcloud/config/get b/gcloud/config/get index aa59e3620..d533c3c2e 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -936,9 +936,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/config/help b/gcloud/config/help index ff6c0f1f1..3ed59104e 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -968,9 +968,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/config/list b/gcloud/config/list index e18f1ac90..4018ef265 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -970,9 +970,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/config/set b/gcloud/config/set index 97d944535..b74f56cbc 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -31,11 +31,11 @@ DESCRIPTION EXAMPLES To set the project property in the core section, run: - $ gcloud config set project myProject + $ gcloud config set project PROJECT_ID To set the zone property in the compute section, run: - $ gcloud config set compute/zone asia-east1-b + $ gcloud config set compute/zone ZONE_NAME To disable prompting for scripting, run: @@ -983,9 +983,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/config/unset b/gcloud/config/unset index d198f2ea0..ad4047d41 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -944,9 +944,6 @@ AVAILABLE PROPERTIES back to this value, if set. scc - location - Default location gcloud should use for scc slz-overwatch surface. - organization Default organization gcloud should use for scc surface. diff --git a/gcloud/container/aws/clusters/create b/gcloud/container/aws/clusters/create index 6af2d31b0..b2c12571c 100644 --- a/gcloud/container/aws/clusters/create +++ b/gcloud/container/aws/clusters/create @@ -94,7 +94,7 @@ REQUIRED FLAGS --pod-address-cidr-blocks=POD_ADDRESS_CIDR_BLOCKS IP address range for the pods in this cluster in CIDR notation (e.g. - 10.0.0.0/8). Can be any RFC 1918 IP range. + 10.0.0.0/8). --role-arn=ROLE_ARN Amazon Resource Name (ARN) of the IAM role to assume when managing AWS @@ -102,7 +102,7 @@ REQUIRED FLAGS --service-address-cidr-blocks=SERVICE_ADDRESS_CIDR_BLOCKS IP address range for the services IPs in CIDR notation (e.g. - 10.0.0.0/8). Can be any RFC 1918 IP range. + 10.0.0.0/8). --subnet-ids=[SUBNET_ID,...] Subnet ID of an existing VNET to use for the cluster control plane. diff --git a/gcloud/container/azure/clusters/create b/gcloud/container/azure/clusters/create index 86aeaa6d3..e143a5191 100644 --- a/gcloud/container/azure/clusters/create +++ b/gcloud/container/azure/clusters/create @@ -99,14 +99,14 @@ REQUIRED FLAGS --pod-address-cidr-blocks=POD_ADDRESS_CIDR_BLOCKS IP address range for the pods in this cluster in CIDR notation (e.g. - 10.0.0.0/8). Can be any RFC 1918 IP range. + 10.0.0.0/8). --resource-group-id=RESOURCE_GROUP_ID ID of the Azure Resource Group to associate the cluster with. --service-address-cidr-blocks=SERVICE_ADDRESS_CIDR_BLOCKS IP address range for the services IPs in CIDR notation (e.g. - 10.0.0.0/8). Can be any RFC 1918 IP range. + 10.0.0.0/8). --ssh-public-key=SSH_PUBLIC_KEY SSH public key to use for authentication. diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index f26be2a40..afbeaf441 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -1105,7 +1105,7 @@ FLAGS Flags to specify identity for autoprovisioned nodes: --autoprovisioning-scopes=[SCOPE,...] - The scopes be used by node instances in autoprovisioned node + The scopes to be used by node instances in autoprovisioned node pools. Multiple scopes can be specified, separated by commas. For information on defaults, look at: https://cloud.google.com/sdk/gcloud/reference/container/clusters/create#--scopes diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 6eadda3af..94005c475 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -757,9 +757,9 @@ REQUIRED FLAGS Flags to specify identity for autoprovisioned nodes: --autoprovisioning-scopes=[SCOPE,...] - The scopes be used by node instances in autoprovisioned node - pools. Multiple scopes can be specified, separated by commas. - For information on defaults, look at: + The scopes to be used by node instances in autoprovisioned + node pools. Multiple scopes can be specified, separated by + commas. For information on defaults, look at: https://cloud.google.com/sdk/gcloud/reference/container/clusters/create#--scopes --autoprovisioning-service-account=AUTOPROVISIONING_SERVICE_ACCOUNT diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index 648e3729e..22adaabe0 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -6,9 +6,11 @@ SYNOPSIS gcloud container node-pools update NAME (--enable-gvnic | --enable-image-streaming | --network-performance-configs=[PROPERTY=VALUE,...] - | --node-locations=ZONE,[ZONE,...] + | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] + | --node-taints=[NODE_TAINT,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE - | --workload-metadata=WORKLOAD_METADATA | --enable-autoprovisioning + | --tags=[TAG,...] | --workload-metadata=WORKLOAD_METADATA + | --enable-autoprovisioning --enable-autoscaling --max-nodes=MAX_NODES --min-nodes=MIN_NODES | --enable-autorepair --enable-autoupgrade | --max-surge-upgrade=MAX_SURGE_UPGRADE @@ -52,6 +54,26 @@ REQUIRED FLAGS external IP destinations. The following tier values are allowed: [DEFAULT,TIER_1] + --node-labels=[NODE_LABEL,...] + Replaces all the user specified Kubernetes labels on all nodes in an + existing node pool with the given labels. + + Examples: + + $ gcloud container node-pools update node-pool-1 \ + --cluster=example-cluster \ + --node-labels=label1=value1,label2=value2 + + New nodes, including ones created by resize or recreate, will have + these labels on the Kubernetes API node object and can be used in + nodeSelectors. See + http://kubernetes.io/docs/user-guide/node-selection/ for examples. + + Note that Kubernetes labels, intended to associate cluster components + and resources with one another and manage resource lifecycles, are + different from Google Kubernetes Engine labels that are used for the + purpose of tracking billing and usage information. + --node-locations=ZONE,[ZONE,...] Set of zones in which the node pool's nodes should be located. Changing the locations for a node pool will result in nodes being @@ -65,6 +87,20 @@ REQUIRED FLAGS --cluster=sample-cluster \ --node-locations=us-central1-a,us-central1-b + --node-taints=[NODE_TAINT,...] + Replaces all the user specified Kubernetes taints on all nodes in an + existing node pool, which can be used with tolerations for pod + scheduling. + + Examples: + + $ gcloud container node-pools update node-pool-1 \ + --cluster=example-cluster \ + --node-taints=key1=val1:NoSchedule,key2=val2:PreferNoSchedule + + To read more about node-taints, see + https://cloud.google.com/kubernetes-engine/docs/node-taints. + --system-config-from-file=SYSTEM_CONFIG_FROM_FILE Path of the YAML/JSON file that contains the node configuration, including Linux kernel parameters (sysctls) and kubelet configs. @@ -110,6 +146,21 @@ REQUIRED FLAGS requires recreation of the nodes which which might cause a disruption. + --tags=[TAG,...] + Replaces all the user specified Compute Engine tags on all nodes in + an existing node pool with the given tags (comma separated). + + Examples: + + $ gcloud container node-pools update node-pool-1 \ + --cluster=example-cluster --tags=tag1,tag2 + + New nodes, including ones created by resize or recreate, will have + these tags on the Compute Engine API instance object and these tags + can be used in firewall rules. See + https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/create + for examples. + --workload-metadata=WORKLOAD_METADATA Type of metadata server available to pods running in the node pool. WORKLOAD_METADATA must be one of: diff --git a/gcloud/dns/policies/delete b/gcloud/dns/policies/delete index e0d042867..71cd0c1d9 100644 --- a/gcloud/dns/policies/delete +++ b/gcloud/dns/policies/delete @@ -39,7 +39,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dns/v1 API. The full documentation for this API can - be found at: https://developers.google.com/cloud-dns + be found at: https://cloud.google.com/dns/docs NOTES These variants are also available: diff --git a/gcloud/dns/policies/describe b/gcloud/dns/policies/describe index 25c882b6e..64adf7bd0 100644 --- a/gcloud/dns/policies/describe +++ b/gcloud/dns/policies/describe @@ -39,7 +39,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dns/v1 API. The full documentation for this API can - be found at: https://developers.google.com/cloud-dns + be found at: https://cloud.google.com/dns/docs NOTES These variants are also available: diff --git a/gcloud/dns/policies/list b/gcloud/dns/policies/list index 33d22bf86..c5e8f27a6 100644 --- a/gcloud/dns/policies/list +++ b/gcloud/dns/policies/list @@ -60,7 +60,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dns/v1 API. The full documentation for this API can - be found at: https://developers.google.com/cloud-dns + be found at: https://cloud.google.com/dns/docs NOTES These variants are also available: diff --git a/gcloud/functions/deploy b/gcloud/functions/deploy index f92fcf676..8631d63b7 100644 --- a/gcloud/functions/deploy +++ b/gcloud/functions/deploy @@ -133,9 +133,11 @@ FLAGS ◆ nodejs14: Node.js 14 ◆ nodejs16: Node.js 16 ◆ php74: PHP 7.4 + ◆ php81: PHP 8.1 (preview) ◆ python37: Python 3.7 ◆ python38: Python 3.8 ◆ python39: Python 3.9 + ◆ python310: Python 3.10 (preview) ◆ go111: Go 1.11 ◆ go113: Go 1.13 ◆ go116: Go 1.16 diff --git a/gcloud/iam/service-accounts/help b/gcloud/iam/service-accounts/help index 18e74bffa..b14e8a410 100644 --- a/gcloud/iam/service-accounts/help +++ b/gcloud/iam/service-accounts/help @@ -62,6 +62,9 @@ COMMANDS sign-blob Sign a blob with a managed service account key. + sign-jwt + Sign a JWT with a managed service account key. + undelete Undelete a service account for a project. diff --git a/gcloud/iam/service-accounts/sign-jwt b/gcloud/iam/service-accounts/sign-jwt new file mode 100644 index 000000000..e9f52d55e --- /dev/null +++ b/gcloud/iam/service-accounts/sign-jwt @@ -0,0 +1,52 @@ +NAME + gcloud iam service-accounts sign-jwt - sign a JWT with a managed service + account key + +SYNOPSIS + gcloud iam service-accounts sign-jwt INPUT-FILE OUTPUT-FILE + --iam-account=IAM_ACCOUNT [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command signs a JWT using a system-managed service account key. + + If the service account does not exist, this command returns a + PERMISSION_DENIED error. + +EXAMPLES + To create a sign JWT with a system-managed service account key, run: + + $ gcloud iam service-accounts sign-jwt \ + --iam-account=my-iam-account@my-project.iam.gserviceaccount.com \ + input.json output.jwt + +POSITIONAL ARGUMENTS + INPUT-FILE + A path to the file containing the JSON JWT Claim set to be signed. + + OUTPUT-FILE + A path the resulting signed JWT will be written to. + +REQUIRED FLAGS + --iam-account=IAM_ACCOUNT + The service account to sign as. + +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. + +SEE ALSO + For more information on how this command ties into the wider cloud + infrastructure, please see + https://cloud.google.com/appengine/docs/java/appidentity/. + +NOTES + These variants are also available: + + $ gcloud alpha iam service-accounts sign-jwt + + $ gcloud beta iam service-accounts sign-jwt + diff --git a/gcloud/iam/workload-identity-pools/create-cred-config b/gcloud/iam/workload-identity-pools/create-cred-config index 0d47ea09e..a14ccf461 100644 --- a/gcloud/iam/workload-identity-pools/create-cred-config +++ b/gcloud/iam/workload-identity-pools/create-cred-config @@ -10,7 +10,7 @@ SYNOPSIS [--app-id-uri=APP_ID_URI] [--credential-source-field-name=CREDENTIAL_SOURCE_FIELD_NAME] [--credential-source-headers=[key=value,...]] - [--credential-source-type=CREDENTIAL_SOURCE_TYPE] + [--credential-source-type=CREDENTIAL_SOURCE_TYPE] [--enable-imdsv2] [--service-account=SERVICE_ACCOUNT] [--subject-token-type=SUBJECT_TOKEN_TYPE] [GCLOUD_WIDE_FLAG ...] @@ -43,7 +43,8 @@ EXAMPLES $ gcloud iam workload-identity-pools create-cred-config \ projects/$PROJECT_NUMBER/locations/$REGION/\ workloadIdentityPools/$WORKLOAD_POOL_ID/providers/$PROVIDER_ID \ - --service-account=$EMAIL --aws --output-file=credentials.json + --service-account=$EMAIL --aws --enable-imdsv2 \ + --output-file=credentials.json To create an Azure-based credential configuration for your project, run: @@ -95,6 +96,10 @@ OPTIONAL FLAGS --credential-source-type=CREDENTIAL_SOURCE_TYPE The format of the credential source (JSON or text). + --enable-imdsv2 + Adds the AWS IMDSv2 session token Url to the credential source to + enforce the AWS IMDSv2 flow. + --service-account=SERVICE_ACCOUNT The email of the service account to impersonate.