From d7d92f80009d276881832032141f6a83ca27da21 Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 30 Oct 2024 10:13:17 +0000 Subject: [PATCH] gcloud: Wed Oct 30 10:13:17 UTC 2024 --- gcloud/_version | 8 +- gcloud/access-approval/settings/update | 48 ++ gcloud/alloydb/backups/create | 8 +- gcloud/alpha/access-approval/settings/update | 48 ++ gcloud/alpha/alloydb/backups/create | 8 +- gcloud/alpha/alloydb/instances/create | 7 + gcloud/alpha/alloydb/instances/update | 14 +- gcloud/alpha/audit-manager/enrollments/add | 6 +- gcloud/alpha/backup-dr/backup-vaults/create | 3 +- gcloud/alpha/backup-dr/backup-vaults/delete | 24 +- gcloud/alpha/backup-dr/backup-vaults/update | 3 +- .../alpha/backup-dr/backups/restore/compute | 5 +- gcloud/alpha/compute/disks/update | 41 ++ .../compute/firewall-policies/export-rules | 48 ++ gcloud/alpha/compute/firewall-policies/help | 6 + .../compute/firewall-policies/import-rules | 49 ++ .../alpha/compute/future-reservations/create | 10 +- .../alpha/compute/future-reservations/update | 6 - .../instance-templates/create-with-container | 4 + .../compute/instances/create-with-container | 4 + .../compute/interconnects/groups/add-members | 44 ++ .../alpha/compute/interconnects/groups/create | 21 +- .../alpha/compute/interconnects/groups/delete | 32 + .../compute/interconnects/groups/describe | 30 + .../alpha/compute/interconnects/groups/help | 17 + .../alpha/compute/interconnects/groups/list | 68 ++ .../interconnects/groups/remove-members | 44 ++ .../alpha/compute/interconnects/groups/update | 15 +- .../compute/network-endpoint-groups/update | 26 +- .../network-firewall-policies/export-rules | 52 ++ .../compute/network-firewall-policies/help | 6 + .../network-firewall-policies/import-rules | 53 ++ .../compute/tpus/queued-resources/create | 7 +- .../alpha/compute/tpus/queued-resources/help | 3 + .../tpus/queued-resources/perform-maintenance | 82 +++ gcloud/alpha/compute/tpus/tpu-vm/help | 3 + .../compute/tpus/tpu-vm/perform-maintenance | 75 +++ .../compute/url-maps/invalidate-cdn-cache | 31 +- .../url-maps/list-cdn-cache-invalidations | 30 +- gcloud/alpha/container/clusters/create | 15 +- gcloud/alpha/container/clusters/create-auto | 7 + gcloud/alpha/container/clusters/update | 9 +- .../container/fleet/memberships/register | 3 +- .../alpha/container/hub/memberships/register | 3 +- gcloud/alpha/container/node-pools/create | 5 + gcloud/alpha/container/node-pools/update | 5 + gcloud/alpha/dataproc/clusters/create | 36 ++ .../workflow-templates/set-managed-cluster | 36 ++ gcloud/alpha/memorystore/instances/create | 21 +- .../internal-ranges/create | 6 +- .../multicast-group-definitions/create | 5 + gcloud/alpha/recaptcha/keys/add-ip-override | 62 ++ gcloud/alpha/recaptcha/keys/help | 6 + .../alpha/recaptcha/keys/remove-ip-override | 64 ++ .../redis/clusters/add-cluster-endpoints | 133 ++++ gcloud/alpha/redis/clusters/help | 6 + .../redis/clusters/remove-cluster-endpoints | 115 ++++ gcloud/alpha/redis/instances/create | 2 +- gcloud/alpha/source/repos/update | 5 +- gcloud/alpha/workstations/configs/create | 6 + gcloud/alpha/workstations/configs/update | 6 + gcloud/artifacts/docker/upgrade/migrate | 12 +- gcloud/beta/access-approval/settings/update | 48 ++ gcloud/beta/alloydb/backups/create | 8 +- gcloud/beta/colab-enterprise/runtimes/assign | 12 +- gcloud/beta/colab-enterprise/runtimes/create | 110 ++++ gcloud/beta/colab-enterprise/runtimes/delete | 2 +- .../beta/colab-enterprise/runtimes/describe | 2 +- gcloud/beta/colab-enterprise/runtimes/help | 5 +- gcloud/beta/colab-enterprise/runtimes/start | 2 +- gcloud/beta/colab-enterprise/runtimes/upgrade | 2 +- gcloud/beta/colab/runtimes/assign | 12 +- gcloud/beta/colab/runtimes/create | 109 ++++ gcloud/beta/colab/runtimes/delete | 2 +- gcloud/beta/colab/runtimes/describe | 2 +- gcloud/beta/colab/runtimes/help | 5 +- gcloud/beta/colab/runtimes/start | 2 +- gcloud/beta/colab/runtimes/upgrade | 2 +- .../beta/compute/backend-services/add-backend | 76 +++ gcloud/beta/compute/backend-services/create | 68 ++ gcloud/beta/compute/backend-services/update | 71 ++ .../compute/backend-services/update-backend | 79 +++ gcloud/beta/compute/instance-templates/create | 4 + .../instance-templates/create-with-container | 4 + gcloud/beta/compute/instances/create | 4 + .../compute/instances/create-with-container | 4 + .../compute/network-endpoint-groups/update | 15 +- .../compute/url-maps/invalidate-cdn-cache | 31 +- .../url-maps/list-cdn-cache-invalidations | 30 +- gcloud/beta/container/clusters/create | 14 +- gcloud/beta/container/clusters/create-auto | 7 + gcloud/beta/container/clusters/update | 9 +- .../beta/container/fleet/memberships/register | 3 +- .../beta/container/hub/memberships/register | 3 +- gcloud/beta/container/node-pools/create | 5 + gcloud/beta/container/node-pools/update | 5 + gcloud/beta/dataproc/clusters/create | 36 ++ .../workflow-templates/set-managed-cluster | 36 ++ gcloud/beta/eventarc/enrollments/create | 119 ++++ gcloud/beta/eventarc/enrollments/delete | 67 ++ gcloud/beta/eventarc/enrollments/describe | 62 ++ gcloud/beta/eventarc/enrollments/help | 35 + gcloud/beta/eventarc/enrollments/list | 90 +++ gcloud/beta/eventarc/enrollments/update | 80 +++ .../beta/eventarc/google-api-sources/create | 120 ++++ .../beta/eventarc/google-api-sources/delete | 70 ++ .../beta/eventarc/google-api-sources/describe | 64 ++ gcloud/beta/eventarc/google-api-sources/help | 36 ++ gcloud/beta/eventarc/google-api-sources/list | 91 +++ .../beta/eventarc/google-api-sources/update | 139 ++++ gcloud/beta/eventarc/help | 15 + gcloud/beta/eventarc/message-buses/create | 77 +++ gcloud/beta/eventarc/message-buses/delete | 67 ++ gcloud/beta/eventarc/message-buses/describe | 63 ++ gcloud/beta/eventarc/message-buses/help | 41 ++ gcloud/beta/eventarc/message-buses/list | 90 +++ .../eventarc/message-buses/list-enrollments | 97 +++ gcloud/beta/eventarc/message-buses/publish | 121 ++++ gcloud/beta/eventarc/message-buses/update | 92 +++ gcloud/beta/eventarc/pipelines/create | 608 ++++++++++++++++++ gcloud/beta/eventarc/pipelines/delete | 65 ++ gcloud/beta/eventarc/pipelines/describe | 60 ++ gcloud/beta/eventarc/pipelines/help | 35 + gcloud/beta/eventarc/pipelines/list | 90 +++ gcloud/beta/eventarc/pipelines/update | 439 +++++++++++++ gcloud/beta/memorystore/instances/create | 21 +- gcloud/beta/network-connectivity/hubs/create | 4 +- gcloud/beta/network-connectivity/spokes/help | 3 + .../spokes/linked-producer-vpc-network/create | 109 ++++ .../spokes/linked-producer-vpc-network/help | 31 + .../spokes/linked-producer-vpc-network/update | 106 +++ .../beta/redis/clusters/add-cluster-endpoints | 131 ++++ gcloud/beta/redis/clusters/help | 6 + .../redis/clusters/remove-cluster-endpoints | 113 ++++ gcloud/beta/redis/instances/create | 2 +- gcloud/beta/source/repos/update | 2 +- gcloud/beta/workstations/configs/create | 6 + gcloud/beta/workstations/configs/update | 6 + gcloud/compute/instance-templates/create | 4 + .../instance-templates/create-with-container | 4 + gcloud/compute/instances/create | 4 + .../compute/instances/create-with-container | 4 + gcloud/compute/network-endpoint-groups/update | 16 +- gcloud/compute/url-maps/invalidate-cdn-cache | 30 +- .../url-maps/list-cdn-cache-invalidations | 32 +- gcloud/container/clusters/create | 7 +- gcloud/container/fleet/memberships/register | 3 +- gcloud/container/hub/memberships/register | 3 +- gcloud/container/node-pools/create | 5 + gcloud/container/node-pools/update | 5 + gcloud/dataproc/clusters/create | 36 ++ .../workflow-templates/set-managed-cluster | 36 ++ .../service-connection-policies/create | 37 +- .../spokes/linked-producer-vpc-network/create | 14 +- .../spokes/linked-producer-vpc-network/help | 6 + .../spokes/linked-producer-vpc-network/update | 7 + gcloud/recaptcha/keys/add-ip-override | 59 ++ gcloud/recaptcha/keys/help | 6 + gcloud/recaptcha/keys/remove-ip-override | 60 ++ gcloud/redis/clusters/add-cluster-endpoints | 128 ++++ gcloud/redis/clusters/help | 6 + .../redis/clusters/remove-cluster-endpoints | 110 ++++ gcloud/redis/instances/create | 2 +- gcloud/source/repos/update | 2 +- gcloud/workstations/configs/create | 6 + gcloud/workstations/configs/update | 6 + 166 files changed, 6197 insertions(+), 300 deletions(-) create mode 100644 gcloud/alpha/compute/firewall-policies/export-rules create mode 100644 gcloud/alpha/compute/firewall-policies/import-rules create mode 100644 gcloud/alpha/compute/interconnects/groups/add-members create mode 100644 gcloud/alpha/compute/interconnects/groups/delete create mode 100644 gcloud/alpha/compute/interconnects/groups/describe create mode 100644 gcloud/alpha/compute/interconnects/groups/list create mode 100644 gcloud/alpha/compute/interconnects/groups/remove-members create mode 100644 gcloud/alpha/compute/network-firewall-policies/export-rules create mode 100644 gcloud/alpha/compute/network-firewall-policies/import-rules create mode 100644 gcloud/alpha/compute/tpus/queued-resources/perform-maintenance create mode 100644 gcloud/alpha/compute/tpus/tpu-vm/perform-maintenance create mode 100644 gcloud/alpha/recaptcha/keys/add-ip-override create mode 100644 gcloud/alpha/recaptcha/keys/remove-ip-override create mode 100644 gcloud/alpha/redis/clusters/add-cluster-endpoints create mode 100644 gcloud/alpha/redis/clusters/remove-cluster-endpoints create mode 100644 gcloud/beta/colab-enterprise/runtimes/create create mode 100644 gcloud/beta/colab/runtimes/create create mode 100644 gcloud/beta/eventarc/enrollments/create create mode 100644 gcloud/beta/eventarc/enrollments/delete create mode 100644 gcloud/beta/eventarc/enrollments/describe create mode 100644 gcloud/beta/eventarc/enrollments/help create mode 100644 gcloud/beta/eventarc/enrollments/list create mode 100644 gcloud/beta/eventarc/enrollments/update create mode 100644 gcloud/beta/eventarc/google-api-sources/create create mode 100644 gcloud/beta/eventarc/google-api-sources/delete create mode 100644 gcloud/beta/eventarc/google-api-sources/describe create mode 100644 gcloud/beta/eventarc/google-api-sources/help create mode 100644 gcloud/beta/eventarc/google-api-sources/list create mode 100644 gcloud/beta/eventarc/google-api-sources/update create mode 100644 gcloud/beta/eventarc/message-buses/create create mode 100644 gcloud/beta/eventarc/message-buses/delete create mode 100644 gcloud/beta/eventarc/message-buses/describe create mode 100644 gcloud/beta/eventarc/message-buses/help create mode 100644 gcloud/beta/eventarc/message-buses/list create mode 100644 gcloud/beta/eventarc/message-buses/list-enrollments create mode 100644 gcloud/beta/eventarc/message-buses/publish create mode 100644 gcloud/beta/eventarc/message-buses/update create mode 100644 gcloud/beta/eventarc/pipelines/create create mode 100644 gcloud/beta/eventarc/pipelines/delete create mode 100644 gcloud/beta/eventarc/pipelines/describe create mode 100644 gcloud/beta/eventarc/pipelines/help create mode 100644 gcloud/beta/eventarc/pipelines/list create mode 100644 gcloud/beta/eventarc/pipelines/update create mode 100644 gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/create create mode 100644 gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/help create mode 100644 gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/update create mode 100644 gcloud/beta/redis/clusters/add-cluster-endpoints create mode 100644 gcloud/beta/redis/clusters/remove-cluster-endpoints create mode 100644 gcloud/recaptcha/keys/add-ip-override create mode 100644 gcloud/recaptcha/keys/remove-ip-override create mode 100644 gcloud/redis/clusters/add-cluster-endpoints create mode 100644 gcloud/redis/clusters/remove-cluster-endpoints diff --git a/gcloud/_version b/gcloud/_version index 46c979b39..a42491c0b 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 498.0.0 -alpha 2024.10.18 -beta 2024.10.18 +Google Cloud SDK 499.0.0 +alpha 2024.10.25 +beta 2024.10.25 bq 2.1.9 bundled-python3-unix 3.11.9 -core 2024.10.18 +core 2024.10.25 gcloud-crc32c 1.0.0 gsutil 5.31 diff --git a/gcloud/access-approval/settings/update b/gcloud/access-approval/settings/update index 4e9d88d05..567edff60 100644 --- a/gcloud/access-approval/settings/update +++ b/gcloud/access-approval/settings/update @@ -6,6 +6,11 @@ SYNOPSIS [--active_key_version=ACTIVE_KEY_VERSION] [--enrolled_services=ENROLLED_SERVICES] [--notification_emails=NOTIFICATION_EMAILS] + [--notification_pubsub_topic=NOTIFICATION_PUBSUB_TOPIC] + [--prefer_no_broad_approval_requests=PREFER_NO_BROAD_APPROVAL_REQUESTS] + [--preferred_request_expiration_days=PREFERRED_REQUEST_EXPIRATION_DAYS] + [--request_scope_max_width_preference=REQUEST_SCOPE_MAX_WIDTH_PREFERENCE] + [--require_customer_visible_justification=REQUIRE_CUSTOMER_VISIBLE_JUSTIFICATION] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -39,6 +44,26 @@ EXAMPLES --active_key_version='projects/p1/locations/global/keyRings/sign\ ing-keys/cryptoKeys/signing-key/cryptoKeyVersions/1' + Update preferred request expiration days for project p1: + + $ gcloud access-approval settings update --project=p1 \ + --preferred_request_expiration_days=5 + + Enable prefer no broad approval requests for project p1: + + $ gcloud access-approval settings update --project=p1 \ + --prefer_no_broad_approval_requests=true + + Update notification pubsub topic for project p1: + + $ gcloud access-approval settings update --project=p1 \ + --notification_pubsub_topic='exampleTopic' + + Update request scope max width preference for project p1: + + $ gcloud access-approval settings update --project=p1 \ + --request_scope_max_width_preference=PROJECT + FLAGS --active_key_version=ACTIVE_KEY_VERSION The asymmetric crypto key version to use for signing approval requests. @@ -54,6 +79,29 @@ FLAGS to approval requests should be sent or '' to clear all saved notification emails. + --notification_pubsub_topic=NOTIFICATION_PUBSUB_TOPIC + The pubsub topic to publish notifications to when approval requests are + made. + + --prefer_no_broad_approval_requests=PREFER_NO_BROAD_APPROVAL_REQUESTS + If set to true it will communicate the preference to Google personnel + to request access with as targeted a resource scope as possible. + + --preferred_request_expiration_days=PREFERRED_REQUEST_EXPIRATION_DAYS + The default expiration time for approval requests. This value must be + between 1 and 30. Note that this can be overridden at time of Approval + Request creation and modified by the customer at approval time. + + --request_scope_max_width_preference=REQUEST_SCOPE_MAX_WIDTH_PREFERENCE + The preference for the broadest scope of access for access requests + without a specific method. REQUEST_SCOPE_MAX_WIDTH_PREFERENCE must be + one of: ORGANIZATION, FOLDER, PROJECT. + + --require_customer_visible_justification=REQUIRE_CUSTOMER_VISIBLE_JUSTIFICATION + The preference to configure if a customer visible justification (i.e. + Vector Case) is required for a Googler to create an Access Ticket to + send to the customer when attempting to access customer resources. + At most one of these can be specified: --folder=FOLDER diff --git a/gcloud/alloydb/backups/create b/gcloud/alloydb/backups/create index a258f046b..04cb0a064 100644 --- a/gcloud/alloydb/backups/create +++ b/gcloud/alloydb/backups/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alloydb backups create BACKUP --cluster=CLUSTER --region=REGION - [--async] + [--async] [--tags=[KEY=VALUE,...]] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -45,6 +45,12 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. + + Example: 123/environment=production,123/costCenter=marketing + Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the backup. The 'AlloyDB Service Agent' service account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. The diff --git a/gcloud/alpha/access-approval/settings/update b/gcloud/alpha/access-approval/settings/update index 4d930864b..3e0c0e673 100644 --- a/gcloud/alpha/access-approval/settings/update +++ b/gcloud/alpha/access-approval/settings/update @@ -7,6 +7,11 @@ SYNOPSIS [--active_key_version=ACTIVE_KEY_VERSION] [--enrolled_services=ENROLLED_SERVICES] [--notification_emails=NOTIFICATION_EMAILS] + [--notification_pubsub_topic=NOTIFICATION_PUBSUB_TOPIC] + [--prefer_no_broad_approval_requests=PREFER_NO_BROAD_APPROVAL_REQUESTS] + [--preferred_request_expiration_days=PREFERRED_REQUEST_EXPIRATION_DAYS] + [--request_scope_max_width_preference=REQUEST_SCOPE_MAX_WIDTH_PREFERENCE] + [--require_customer_visible_justification=REQUIRE_CUSTOMER_VISIBLE_JUSTIFICATION] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -41,6 +46,26 @@ EXAMPLES --active_key_version='projects/p1/locations/global/keyRings/sign\ ing-keys/cryptoKeys/signing-key/cryptoKeyVersions/1' + Update preferred request expiration days for project p1: + + $ gcloud alpha access-approval settings update --project=p1 \ + --preferred_request_expiration_days=5 + + Enable prefer no broad approval requests for project p1: + + $ gcloud alpha access-approval settings update --project=p1 \ + --prefer_no_broad_approval_requests=true + + Update notification pubsub topic for project p1: + + $ gcloud alpha access-approval settings update --project=p1 \ + --notification_pubsub_topic='exampleTopic' + + Update request scope max width preference for project p1: + + $ gcloud alpha access-approval settings update --project=p1 \ + --request_scope_max_width_preference=PROJECT + FLAGS --active_key_version=ACTIVE_KEY_VERSION The asymmetric crypto key version to use for signing approval requests. @@ -56,6 +81,29 @@ FLAGS to approval requests should be sent or '' to clear all saved notification emails. + --notification_pubsub_topic=NOTIFICATION_PUBSUB_TOPIC + The pubsub topic to publish notifications to when approval requests are + made. + + --prefer_no_broad_approval_requests=PREFER_NO_BROAD_APPROVAL_REQUESTS + If set to true it will communicate the preference to Google personnel + to request access with as targeted a resource scope as possible. + + --preferred_request_expiration_days=PREFERRED_REQUEST_EXPIRATION_DAYS + The default expiration time for approval requests. This value must be + between 1 and 30. Note that this can be overridden at time of Approval + Request creation and modified by the customer at approval time. + + --request_scope_max_width_preference=REQUEST_SCOPE_MAX_WIDTH_PREFERENCE + The preference for the broadest scope of access for access requests + without a specific method. REQUEST_SCOPE_MAX_WIDTH_PREFERENCE must be + one of: ORGANIZATION, FOLDER, PROJECT. + + --require_customer_visible_justification=REQUIRE_CUSTOMER_VISIBLE_JUSTIFICATION + The preference to configure if a customer visible justification (i.e. + Vector Case) is required for a Googler to create an Access Ticket to + send to the customer when attempting to access customer resources. + At most one of these can be specified: --folder=FOLDER diff --git a/gcloud/alpha/alloydb/backups/create b/gcloud/alpha/alloydb/backups/create index 2ffba44c5..9b36e4218 100644 --- a/gcloud/alpha/alloydb/backups/create +++ b/gcloud/alpha/alloydb/backups/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha alloydb backups create BACKUP --cluster=CLUSTER - --region=REGION [--async] + --region=REGION [--async] [--tags=[KEY=VALUE,...]] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -45,6 +45,12 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. + + Example: 123/environment=production,123/costCenter=marketing + Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the backup. The 'AlloyDB Service Agent' service account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. The diff --git a/gcloud/alpha/alloydb/instances/create b/gcloud/alpha/alloydb/instances/create index 0559982df..d9a15bd1a 100644 --- a/gcloud/alpha/alloydb/instances/create +++ b/gcloud/alpha/alloydb/instances/create @@ -21,6 +21,7 @@ SYNOPSIS [--[no-]observability-config-record-application-tags] [--[no-]observability-config-track-active-queries] [--observability-config-track-wait-events] [--[no-]outbound-public-ip] + [--psc-network-attachment-url=PSC_NETWORK_ATTACHMENT_URL] [--read-pool-node-count=READ_POOL_NODE_COUNT] [--[no-]require-connectors] [--ssl-mode=SSL_MODE; default="ENCRYPTED_ONLY"] [GCLOUD_WIDE_FLAG ...] @@ -178,6 +179,12 @@ OPTIONAL FLAGS Add outbound Public IP connectivity to an AlloyDB instance. Use --outbound-public-ip to enable and --no-outbound-public-ip to disable. + --psc-network-attachment-url=PSC_NETWORK_ATTACHMENT_URL + Full URL of the network attachment that is configured to support + outbound connectivity from an AlloyDB instance which uses Private + Service Connect (PSC). For example, this would be of the + form:psc-network-attachment-url=projects/test-project/regions/us-central1/networkAttachments/my-na + --read-pool-node-count=READ_POOL_NODE_COUNT Read capacity, i.e. number of nodes in a read pool instance. diff --git a/gcloud/alpha/alloydb/instances/update b/gcloud/alpha/alloydb/instances/update index 35bb32f1f..6b5649a41 100644 --- a/gcloud/alpha/alloydb/instances/update +++ b/gcloud/alpha/alloydb/instances/update @@ -7,7 +7,8 @@ SYNOPSIS --region=REGION [--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]] [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async] [--authorized-external-networks=[AUTHORIZED_NETWORK,...]] - [--availability-type=AVAILABILITY_TYPE] [--cpu-count=CPU_COUNT] + [--availability-type=AVAILABILITY_TYPE] + [--clear-psc-network-attachment-url] [--cpu-count=CPU_COUNT] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] @@ -20,6 +21,7 @@ SYNOPSIS [--[no-]observability-config-record-application-tags] [--[no-]observability-config-track-active-queries] [--observability-config-track-wait-events] [--[no-]outbound-public-ip] + [--psc-network-attachment-url=PSC_NETWORK_ATTACHMENT_URL] [--read-pool-node-count=READ_POOL_NODE_COUNT] [--[no-]require-connectors] [--ssl-mode=SSL_MODE] [--update-mode=UPDATE_MODE] [GCLOUD_WIDE_FLAG ...] @@ -86,6 +88,10 @@ OPTIONAL FLAGS production instances; instance does not automatically fail over to another zone. + --clear-psc-network-attachment-url + Disable outbound connectivity from an AlloyDB instance which uses + Private Service Connect (PSC). + --cpu-count=CPU_COUNT Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: @@ -160,6 +166,12 @@ OPTIONAL FLAGS Add outbound Public IP connectivity to an AlloyDB instance. Use --outbound-public-ip to enable and --no-outbound-public-ip to disable. + --psc-network-attachment-url=PSC_NETWORK_ATTACHMENT_URL + Full URL of the network attachment that is configured to support + outbound connectivity from an AlloyDB instance which uses Private + Service Connect (PSC). For example, this would be of the + form:psc-network-attachment-url=projects/test-project/regions/us-central1/networkAttachments/my-na + --read-pool-node-count=READ_POOL_NODE_COUNT Read capacity, i.e. number of nodes in a read pool instance. diff --git a/gcloud/alpha/audit-manager/enrollments/add b/gcloud/alpha/audit-manager/enrollments/add index 99aa81bbc..843da1cc2 100644 --- a/gcloud/alpha/audit-manager/enrollments/add +++ b/gcloud/alpha/audit-manager/enrollments/add @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud alpha audit-manager enrollments add --eligible-gcs-buckets=BUCKET - URI,[BUCKET URI,...] (--folder=FOLDER | --project=PROJECT) + URI,[BUCKET URI,...] + (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -26,6 +27,9 @@ REQUIRED FLAGS --folder=FOLDER Folder Id to enroll + --organization=ORGANIZATION + Organization Id to enroll + --project=PROJECT Project Id to enroll diff --git a/gcloud/alpha/backup-dr/backup-vaults/create b/gcloud/alpha/backup-dr/backup-vaults/create index b99269aca..5ac31be08 100644 --- a/gcloud/alpha/backup-dr/backup-vaults/create +++ b/gcloud/alpha/backup-dr/backup-vaults/create @@ -82,7 +82,8 @@ REQUIRED FLAGS --backup-min-enforced-retention=BACKUP_MIN_ENFORCED_RETENTION Backups will be kept for this minimum period before they can be deleted. Once the effective time is reached, the enforced retention - period cannot be decreased or removed. + period cannot be decreased or removed. The value must be specified in + relative time format (e.g. p1d, p1m, p1m1d). OPTIONAL FLAGS --no-async diff --git a/gcloud/alpha/backup-dr/backup-vaults/delete b/gcloud/alpha/backup-dr/backup-vaults/delete index 6d1324c3c..d42cbcfc8 100644 --- a/gcloud/alpha/backup-dr/backup-vaults/delete +++ b/gcloud/alpha/backup-dr/backup-vaults/delete @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha backup-dr backup-vaults delete (BACKUP_VAULT : --location=LOCATION) [--allow-missing] [--no-async] - [--force-delete] [GCLOUD_WIDE_FLAG ...] + [--ignore-backup-plan-references] [--ignore-inactive-datasources] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Delete the specified Backup Vault. @@ -17,10 +18,17 @@ EXAMPLES --location=MY_LOCATION To override restrictions against the deletion of a backup vault - BACKUP_VAULT in location MY_LOCATION, run: + BACKUP_VAULT containing inactive datasources in location MY_LOCATION, run: $ gcloud alpha backup-dr backup-vaults delete BACKUP_VAULT \ - --location=MY_LOCATION --force-delete + --location=MY_LOCATION --ignore-inactive-datasources + + To override restrictions against the deletion of a backup vault + BACKUP_VAULT containing backup plan references in location MY_LOCATION, + run: + + $ gcloud alpha backup-dr backup-vaults delete BACKUP_VAULT \ + --location=MY_LOCATION --ignore-backup-plan-references POSITIONAL ARGUMENTS Backup Vault resource - Name of the backup vault to delete. Before you @@ -64,11 +72,15 @@ FLAGS --no-async Wait for the operation in progress to complete. - --force-delete + --ignore-backup-plan-references + If set, the following restrictions against deletion of the backup vault + instance can be overridden: * deletion of a backup vault instance being + actively referenced by a backup plan. + + --ignore-inactive-datasources If set, the following restrictions against deletion of the backup vault instance can be overridden: * deletion of a backup vault instance - containing no backups,but still contains empty datasources. * deletion - of a backup vault instance being actively referenced by a backup plan. + containing no backups,but still contains empty datasources. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/backup-dr/backup-vaults/update b/gcloud/alpha/backup-dr/backup-vaults/update index 0d5e4de9e..a529565d8 100644 --- a/gcloud/alpha/backup-dr/backup-vaults/update +++ b/gcloud/alpha/backup-dr/backup-vaults/update @@ -67,7 +67,8 @@ FLAGS --backup-min-enforced-retention=BACKUP_MIN_ENFORCED_RETENTION Backups will be kept for this minimum period before they can be deleted. Once the effective time is reached, the enforced retention - period cannot be decreased or removed. + period cannot be decreased or removed. The value must be specified in + relative time format (e.g. p1d, p1m, p1m1d). --description=DESCRIPTION Optional description for the backup vault (2048 characters or less). diff --git a/gcloud/alpha/backup-dr/backups/restore/compute b/gcloud/alpha/backup-dr/backups/restore/compute index fe5951f4b..ac938c1c0 100644 --- a/gcloud/alpha/backup-dr/backups/restore/compute +++ b/gcloud/alpha/backup-dr/backups/restore/compute @@ -289,9 +289,8 @@ OPTIONAL FLAGS specify multiple network interfaces. The following keys are allowed: network, subnet, private-network-ip, internal-ipv6-address, internal-ipv6-prefix-length, address, external-ipv6-address, - external-ipv6-prefix-length, public-ptr-domain, ipv6-public-ptr-domain, - network-tier, aliases, stack-type, queue-count, nic-type, - network-attachment + external-ipv6-prefix-length, network-tier, aliases, stack-type, + queue-count, nic-type, network-attachment --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the restored instance. If diff --git a/gcloud/alpha/compute/disks/update b/gcloud/alpha/compute/disks/update index 8a3313403..7ab045c14 100644 --- a/gcloud/alpha/compute/disks/update +++ b/gcloud/alpha/compute/disks/update @@ -6,6 +6,9 @@ SYNOPSIS [--provisioned-iops=PROVISIONED_IOPS] [--provisioned-throughput=PROVISIONED_THROUGHPUT] [--size=SIZE] [--update-labels=[KEY=VALUE,...]] + [--append-licenses=[LICENSE,LICENSE...,...] + --remove-licenses=[LICENSE,LICENSE...,...] + --replace-license=OLD_LICENSE,NEW_LICENSE,...,[...]] [--clear-architecture | --update-architecture=UPDATE_ARCHITECTURE] [--clear-labels | --remove-labels=[KEY,...]] [--clear-user-licenses | --update-user-licenses=[LICENSE,...]] @@ -35,6 +38,27 @@ EXAMPLES $ gcloud alpha compute disks describe example-disk \ --format="default(labels)" + To append licenses to the disk, run: + + $ gcloud alpha compute disks update example-disk \ + --zone=us-central1-a \ + --append-licenses=projects/license-project/global/licenses/\ + license-1,projects/license-project/global/licenses/license-2 + + To remove licenses from the disk, run: + + $ gcloud alpha compute disks update example-disk \ + --zone=us-central1-a \ + --replace-licenses=projects/license-project/global/licenses/\ + license-1,projects/license-project/global/licenses/license-2 + + To replace a license on the disk, run: + + $ gcloud alpha compute disks update example-disk \ + --zone=us-central1-a \ + --replace-license=projects/license-project/global/licenses/\ + old-license,projects/license-project/global/licenses/new-license + POSITIONAL ARGUMENTS DISK_NAME Name of the disk to update. @@ -71,6 +95,23 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --append-licenses=[LICENSE,LICENSE...,...] + "A list of license URIs or license codes. These licenses will be + appended to the existing licenses on the disk. Provided licenses can be + either license URIs or license codes but not a mix of both. + + --remove-licenses=[LICENSE,LICENSE...,...] + A list of license URIs or license codes. If present in the set of + existing licenses, these licenses will be removed. If not present, this + is a no-op. Provided licenses can be either license URIs or license + codes but not a mix of both. + + --replace-license=OLD_LICENSE,NEW_LICENSE,...,[...] + A list of license URIs or license codes. The first license is the + license to be replaced and the second license is the replacement + license. Provided licenses can be either license URIs or license codes + but not a mix of both. + At most one of these can be specified: --clear-architecture diff --git a/gcloud/alpha/compute/firewall-policies/export-rules b/gcloud/alpha/compute/firewall-policies/export-rules new file mode 100644 index 000000000..1fbfbeb40 --- /dev/null +++ b/gcloud/alpha/compute/firewall-policies/export-rules @@ -0,0 +1,48 @@ +NAME + gcloud alpha compute firewall-policies export-rules - export Compute Engine + organization firewall policy rules + +SYNOPSIS + gcloud alpha compute firewall-policies export-rules FIREWALL_POLICY + [--destination=DESTINATION] [--organization=ORGANIZATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Exports Firewall Policy rules configuration to a file. + +EXAMPLES + Firewall Policy rules can be exported by running: + + $ gcloud alpha compute firewall-policies export-rules \ + FIREWALL_POLICY --destination= \ + --organization= + +POSITIONAL ARGUMENTS + FIREWALL_POLICY + Short name or ID of the firewall policy to export rules from. + +FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: + $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/FirewallPolicy.yaml. + + --organization=ORGANIZATION + Organization in which the organization firewall policy rules export + from. Must be set if FIREWALL_POLICY is short name. + +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/compute/firewall-policies/help b/gcloud/alpha/compute/firewall-policies/help index 9a3028fcb..8704f5747 100644 --- a/gcloud/alpha/compute/firewall-policies/help +++ b/gcloud/alpha/compute/firewall-policies/help @@ -46,6 +46,12 @@ COMMANDS describe (ALPHA) Describe a Compute Engine organization firewall policy. + export-rules + (ALPHA) Export Compute Engine organization firewall policy rules. + + import-rules + (ALPHA) Import Compute Engine organization firewall policy rules. + list (ALPHA) List Compute Engine organization firewall policies. diff --git a/gcloud/alpha/compute/firewall-policies/import-rules b/gcloud/alpha/compute/firewall-policies/import-rules new file mode 100644 index 000000000..e4c2f8b6e --- /dev/null +++ b/gcloud/alpha/compute/firewall-policies/import-rules @@ -0,0 +1,49 @@ +NAME + gcloud alpha compute firewall-policies import-rules - import Compute Engine + organization firewall policy rules + +SYNOPSIS + gcloud alpha compute firewall-policies import-rules FIREWALL_POLICY + [--organization=ORGANIZATION] [--source=SOURCE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Imports Firewall Policy rules configuration from a file. + +EXAMPLES + Firewall Policy rules can be imported by running: + + $ gcloud alpha compute firewall-policies import-rules \ + FIREWALL_POLICY --source= \ + --organization= + +POSITIONAL ARGUMENTS + FIREWALL_POLICY + Short name or ID of the firewall policy to imports rules to. + +FLAGS + --organization=ORGANIZATION + Organization in which the organization firewall policy rules import to. + Must be set if FIREWALL_POLICY is short name. + + --source=SOURCE + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: + $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/FirewallPolicy.yaml. + + Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. + +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/compute/future-reservations/create b/gcloud/alpha/compute/future-reservations/create index 9793bb3e1..4180e740f 100644 --- a/gcloud/alpha/compute/future-reservations/create +++ b/gcloud/alpha/compute/future-reservations/create @@ -14,9 +14,8 @@ SYNOPSIS --min-cpu-platform=MIN_CPU_PLATFORM]) (--start-time=START_TIME (--duration=DURATION | --end-time=END_TIME)) [--deployment-type=DEPLOYMENT_TYPE] [--description=DESCRIPTION] - [--[no-]enable-opportunistic-maintenance] - [--instance-termination-action=INSTANCE_TERMINATION_ACTION] - [--name-prefix=NAME_PREFIX] [--planning-status=PLANNING_STATUS] + [--[no-]enable-opportunistic-maintenance] [--name-prefix=NAME_PREFIX] + [--planning-status=PLANNING_STATUS] [--[no-]require-specific-reservation] [--reservation-name=RESERVATION_NAME] [--scheduling-type=SCHEDULING_TYPE] [--zone=ZONE] @@ -187,11 +186,6 @@ OPTIONAL FLAGS --enable-opportunistic-maintenance to enable and --no-enable-opportunistic-maintenance to disable. - --instance-termination-action=INSTANCE_TERMINATION_ACTION - Specific termination action for running instances at the end of - reservation duration, it can be DELETE or STOP. - INSTANCE_TERMINATION_ACTION must be one of: DELETE, STOP. - --name-prefix=NAME_PREFIX A name prefix for the auto-created reservations when capacity is delivered at the start time. Each auto-created reservation name starts diff --git a/gcloud/alpha/compute/future-reservations/update b/gcloud/alpha/compute/future-reservations/update index eeaf766b0..7ce68f659 100644 --- a/gcloud/alpha/compute/future-reservations/update +++ b/gcloud/alpha/compute/future-reservations/update @@ -7,7 +7,6 @@ SYNOPSIS [--[no-]auto-delete-auto-created-reservations] [--deployment-type=DEPLOYMENT_TYPE] [--description=DESCRIPTION] [--[no-]enable-opportunistic-maintenance] - [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--planning-status=PLANNING_STATUS] [--[no-]require-specific-reservation] [--reservation-name=RESERVATION_NAME] @@ -69,11 +68,6 @@ FLAGS --enable-opportunistic-maintenance to enable and --no-enable-opportunistic-maintenance to disable. - --instance-termination-action=INSTANCE_TERMINATION_ACTION - Specific termination action for running instances at the end of - reservation duration, it can be DELETE or STOP. - INSTANCE_TERMINATION_ACTION must be one of: DELETE, STOP. - --planning-status=PLANNING_STATUS The planning status of the future reservation. The default value is DRAFT. While in DRAFT, any changes to the future reservation's diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index 17dc93b4a..220c8d163 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -681,6 +681,10 @@ FLAGS available range with the specified netmask and allocate it to this network interface. + network-attachment + Specifies the network attachment that this interface should connect + to. Mutually exclusive with --network and --subnet flags. + --network-tier=NETWORK_TIER Specifies the network tier that will be used to configure the instance. NETWORK_TIER must be one of: PREMIUM, STANDARD. The default value is diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index cf046983d..ee6fc236c 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -772,6 +772,10 @@ FLAGS available range with the specified netmask and allocate it to this network interface. + network-attachment + Specifies the network attachment that this interface should connect + to. Mutually exclusive with --network and --subnet flags. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/alpha/compute/interconnects/groups/add-members b/gcloud/alpha/compute/interconnects/groups/add-members new file mode 100644 index 000000000..3e20b710d --- /dev/null +++ b/gcloud/alpha/compute/interconnects/groups/add-members @@ -0,0 +1,44 @@ +NAME + gcloud alpha compute interconnects groups add-members - add member + interconnects to a Compute Engine interconnect group + +SYNOPSIS + gcloud alpha compute interconnects groups add-members NAME + --interconnects=[INTERCONNECT,...] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects groups add-members is used to + add member interconnects to an interconnect group. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To add interconnects interconnect1 and interconnect2 to interconnect group + example-interconnect-group, run: + + $ gcloud alpha compute interconnects groups add-members \ + example-interconnect-group \ + --interconnects=interconnect1,interconnect2 + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect group to update. + +REQUIRED FLAGS + --interconnects=[INTERCONNECT,...] + Member interconnects to add to or remove from the interconnect group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/groups/create b/gcloud/alpha/compute/interconnects/groups/create index 237b5a838..7af588c7e 100644 --- a/gcloud/alpha/compute/interconnects/groups/create +++ b/gcloud/alpha/compute/interconnects/groups/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha compute interconnects groups create NAME --intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY - [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--interconnects=[INTERCONNECT,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute interconnects groups create is used to create @@ -15,12 +16,23 @@ DESCRIPTION For an example, refer to the EXAMPLES section below. EXAMPLES - To create an interconnect group capable of PRODUCTION_NON_CRITICAL, run: + To create an interconnect group capable of PRODUCTION_CRITICAL, run: + + $ gcloud alpha compute interconnects groups create \ + example-interconnect-group \ + --intended-topology-capability=PRODUCTION_CRITICAL \ + --description="Example interconnect group" + + It is easy to add members to an existing interconnect group after creation + using the add-members command. + + To create an interconnect group capable of PRODUCTION_NON_CRITICAL, with + two members at creation time, run: $ gcloud alpha compute interconnects groups create \ example-interconnect-group \ --intended-topology-capability=PRODUCTION_NON_CRITICAL \ - --description="Example interconnect group" + --interconnects=interconnect-1,interconnect-2 POSITIONAL ARGUMENTS NAME @@ -35,6 +47,9 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional, textual description for the interconnect group. + --interconnects=[INTERCONNECT,...] + Member interconnects to add to the interconnect group initially. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/interconnects/groups/delete b/gcloud/alpha/compute/interconnects/groups/delete new file mode 100644 index 000000000..15deac382 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/groups/delete @@ -0,0 +1,32 @@ +NAME + gcloud alpha compute interconnects groups delete - delete Compute Engine + interconnect groups + +SYNOPSIS + gcloud alpha compute interconnects groups delete NAME [NAME ...] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects groups delete deletes Compute + Engine interconnect groups. Interconnect groups can be deleted even if they + are referenced by interconnects. Each interconnect in the group will be + updated to remove its reference to this group. + +POSITIONAL ARGUMENTS + NAME [NAME ...] + Names of the interconnect groups to delete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/groups/describe b/gcloud/alpha/compute/interconnects/groups/describe new file mode 100644 index 000000000..f8699f379 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/groups/describe @@ -0,0 +1,30 @@ +NAME + gcloud alpha compute interconnects groups describe - describe a Compute + Engine interconnect group + +SYNOPSIS + gcloud alpha compute interconnects groups describe NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects groups describe displays all + data associated with Compute Engine interconnect group in a project. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect group to describe. + +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/compute/interconnects/groups/help b/gcloud/alpha/compute/interconnects/groups/help index c6d54315e..1a638d1f3 100644 --- a/gcloud/alpha/compute/interconnects/groups/help +++ b/gcloud/alpha/compute/interconnects/groups/help @@ -16,9 +16,26 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add-members + (ALPHA) Add member interconnects to a Compute Engine interconnect + group. + create (ALPHA) Create a Compute Engine interconnect group. + delete + (ALPHA) Delete Compute Engine interconnect groups. + + describe + (ALPHA) Describe a Compute Engine interconnect group. + + list + (ALPHA) List Google Compute Engine interconnect groups. + + remove-members + (ALPHA) Remove member interconnects from a Compute Engine interconnect + group. + update (ALPHA) Update a Compute Engine interconnect group. diff --git a/gcloud/alpha/compute/interconnects/groups/list b/gcloud/alpha/compute/interconnects/groups/list new file mode 100644 index 000000000..df17918a2 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/groups/list @@ -0,0 +1,68 @@ +NAME + gcloud alpha compute interconnects groups list - list Google Compute Engine + interconnect groups + +SYNOPSIS + gcloud alpha compute interconnects groups list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects groups list displays all Google + Compute Engine interconnect groups in a project. + +EXAMPLES + To list all interconnect groups in a project in table form, run: + + $ gcloud alpha compute interconnects groups list + + To list the URIs of all interconnect groups in a project, run: + + $ gcloud alpha compute interconnects groups list --uri + +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/compute/interconnects/groups/remove-members b/gcloud/alpha/compute/interconnects/groups/remove-members new file mode 100644 index 000000000..3f79f565f --- /dev/null +++ b/gcloud/alpha/compute/interconnects/groups/remove-members @@ -0,0 +1,44 @@ +NAME + gcloud alpha compute interconnects groups remove-members - remove member + interconnects from a Compute Engine interconnect group + +SYNOPSIS + gcloud alpha compute interconnects groups remove-members NAME + --interconnects=[INTERCONNECT,...] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects groups remove-members is used to + remove member interconnects from an interconnect group. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To remove interconnects interconnect1 and interconnect2 from interconnect + group example-interconnect-group, run: + + $ gcloud alpha compute interconnects groups remove-members \ + example-interconnect-group \ + --interconnects=interconnect1,interconnect2 + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect group to update. + +REQUIRED FLAGS + --interconnects=[INTERCONNECT,...] + Member interconnects to add to or remove from the interconnect group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/groups/update b/gcloud/alpha/compute/interconnects/groups/update index 4768da50b..10e27f35e 100644 --- a/gcloud/alpha/compute/interconnects/groups/update +++ b/gcloud/alpha/compute/interconnects/groups/update @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha compute interconnects groups update NAME - --intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY - [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] + [--intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY] + [--interconnects=[INTERCONNECT,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute interconnects groups update is used to update @@ -16,14 +17,16 @@ POSITIONAL ARGUMENTS NAME Name of the interconnect group to update. -REQUIRED FLAGS +FLAGS + --description=DESCRIPTION + An optional, textual description for the interconnect group. + --intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY The reliability the user intends this group to be capable of, in terms of the Interconnect product SLAs. -OPTIONAL FLAGS - --description=DESCRIPTION - An optional, textual description for the interconnect group. + --interconnects=[INTERCONNECT,...] + Member interconnects to set the interconnect group to contain. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/network-endpoint-groups/update b/gcloud/alpha/compute/network-endpoint-groups/update index 15c41e622..4ca0d65b8 100644 --- a/gcloud/alpha/compute/network-endpoint-groups/update +++ b/gcloud/alpha/compute/network-endpoint-groups/update @@ -63,8 +63,6 @@ REQUIRED FLAGS address must belong to a VM in compute engine (either the internal or external IPv6 address). - At least one of the ip and ipv6 must be specified. - *port* - Required endpoint port unless NEG default port is set. *client-destination-port* - Required endpoint client destination port only for the port @@ -72,14 +70,9 @@ REQUIRED FLAGS internet-ip-port - *ip* - Optional IPv4 address of the endpoint to attach. Must be + *ip* - Required IPv4 address of the endpoint to attach. Must be publicly routable. - *ipv6* - Optional IPv6 address of the endpoint to attach. Must be - publicly routable. - - At least one of the ip and ipv6 must be specified. - *port* - Optional port of the endpoint to attach. If unspecified, the NEG default port is set. If no default port is set, the well-known port for the backend protocol is used instead @@ -100,18 +93,11 @@ REQUIRED FLAGS non-gcp-private-ip-port - *ip* - Optional IPv4 address of the network endpoint to attach. + *ip* - Required IPv4 address of the network endpoint to attach. The IP address must belong to a VM not in Compute Engine and must be routable using a Cloud Router over VPN or an Interconnect connection. - *ipv6* - Optional IPv6 address of the network endpoint to attach. - The IP address must belong to a VM not in Compute Engine and must - be routable using a Cloud Router over VPN or an Interconnect - connection. - - At least one of the ip and ipv6 must be specified. - *port* - Required port of the network endpoint to attach unless the NEG default port is set. @@ -153,10 +139,6 @@ REQUIRED FLAGS *ip* - Required IPv4 address of the network endpoint to detach. - *ipv6* - Required IPv6 address of the network endpoint to detach. - - At least one of the ip and ipv6 must be specified. - *port* - Optional port of the network endpoint to detach if the endpoint has a port specified. @@ -172,10 +154,6 @@ REQUIRED FLAGS *ip* - Required IPv4 address of the network endpoint to detach. - *ipv6* - Required IPv6 address of the network endpoint to detach. - - At least one of the ip and ipv6 must be specified. - *port* - Required port of the network endpoint to detach unless NEG default port is set. diff --git a/gcloud/alpha/compute/network-firewall-policies/export-rules b/gcloud/alpha/compute/network-firewall-policies/export-rules new file mode 100644 index 000000000..a36557f32 --- /dev/null +++ b/gcloud/alpha/compute/network-firewall-policies/export-rules @@ -0,0 +1,52 @@ +NAME + gcloud alpha compute network-firewall-policies export-rules - export + Compute Engine network firewall policy rules + +SYNOPSIS + gcloud alpha compute network-firewall-policies export-rules FIREWALL_POLICY + [--destination=DESTINATION] [--global | --region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Exports Firewall Policy rules configuration to a file. + +EXAMPLES + Firewall Policy rules can be exported by running: + + $ gcloud alpha compute network-firewall-policies export-rules \ + FIREWALL_POLICY --destination= --global + +POSITIONAL ARGUMENTS + FIREWALL_POLICY + name of the network firewall policy to export rules from. + +FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. For + a schema describing the export/import format, see: + $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/FirewallPolicy.yaml. + + At most one of these can be specified: + + --global + If set, the firewall policy is global. + + --region=REGION + Region of the firewall policy to export-rules. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --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/compute/network-firewall-policies/help b/gcloud/alpha/compute/network-firewall-policies/help index ecfe2fddd..db107b1b8 100644 --- a/gcloud/alpha/compute/network-firewall-policies/help +++ b/gcloud/alpha/compute/network-firewall-policies/help @@ -46,9 +46,15 @@ COMMANDS describe (ALPHA) Describe a Compute Engine network firewall policy. + export-rules + (ALPHA) Export Compute Engine network firewall policy rules. + get-effective-firewalls (ALPHA) Get the effective firewalls for a network. + import-rules + (ALPHA) Import a Compute Engine network firewall policy rules. + list (ALPHA) List Compute Engine network firewall policies. diff --git a/gcloud/alpha/compute/network-firewall-policies/import-rules b/gcloud/alpha/compute/network-firewall-policies/import-rules new file mode 100644 index 000000000..4c4161c10 --- /dev/null +++ b/gcloud/alpha/compute/network-firewall-policies/import-rules @@ -0,0 +1,53 @@ +NAME + gcloud alpha compute network-firewall-policies import-rules - import a + Compute Engine network firewall policy rules + +SYNOPSIS + gcloud alpha compute network-firewall-policies import-rules FIREWALL_POLICY + [--source=SOURCE] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Imports Firewall Policy rules configuration from a file. + +EXAMPLES + Firewall Policy rules can be imported by running: + + $ gcloud alpha compute network-firewall-policies import-rules \ + FIREWALL_POLICY --source= --global + +POSITIONAL ARGUMENTS + FIREWALL_POLICY + name of the network firewall policy to import rules to. + +FLAGS + --source=SOURCE + Path to a YAML file containing configuration export data. + Alternatively, you may omit this flag to read from standard input.For a + schema describing the export/import format, see: + $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/FirewallPolicy.yaml. + + Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. + + At most one of these can be specified: + + --global + If set, the firewall policy is global. + + --region=REGION + Region of the firewall policy to import-rules. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --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/compute/tpus/queued-resources/create b/gcloud/alpha/compute/tpus/queued-resources/create index 22200880c..4a13d8e4d 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/create +++ b/gcloud/alpha/compute/tpus/queued-resources/create @@ -6,8 +6,8 @@ SYNOPSIS gcloud alpha compute tpus queued-resources create (QUEUED_RESOURCE : --zone=ZONE) --runtime-version=RUNTIME_VERSION (--accelerator-type=ACCELERATOR_TYPE | --topology=TOPOLOGY --type=TYPE) - (--node-id=NODE_ID - | [--node-count=NODE_COUNT : --node-prefix=NODE_PREFIX]) [--async] + (--node-id=NODE_ID | [--node-count=NODE_COUNT + : --node-prefix=NODE_PREFIX --workload-type=WORKLOAD_TYPE]) [--async] [--autocheckpoint-enabled] [--best-effort] [--boot-disk=[KEY=VALUE,...]] [--data-disk=[mode=MODE],[source=SOURCE]] [--description=DESCRIPTION] [--guaranteed] [--labels=[KEY=VALUE,...]] @@ -140,6 +140,9 @@ REQUIRED FLAGS Must also specify --node-count. + --workload-type=WORKLOAD_TYPE + Specifies the workload type for the multi-node TPUs. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alpha/compute/tpus/queued-resources/help b/gcloud/alpha/compute/tpus/queued-resources/help index 9938912c4..879e58cd8 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/help +++ b/gcloud/alpha/compute/tpus/queued-resources/help @@ -28,6 +28,9 @@ COMMANDS list (ALPHA) List Queued Resources. + perform-maintenance + (ALPHA) Performs maintenance on a Cloud TPU Queued Resource. + reset (ALPHA) Reset a Queued Resource. diff --git a/gcloud/alpha/compute/tpus/queued-resources/perform-maintenance b/gcloud/alpha/compute/tpus/queued-resources/perform-maintenance new file mode 100644 index 000000000..13449e62a --- /dev/null +++ b/gcloud/alpha/compute/tpus/queued-resources/perform-maintenance @@ -0,0 +1,82 @@ +NAME + gcloud alpha compute tpus queued-resources perform-maintenance - performs + maintenance on a Cloud TPU Queued Resource + +SYNOPSIS + gcloud alpha compute tpus queued-resources perform-maintenance + (QUEUED_RESOURCE : --zone=ZONE) [--async] + [--node-names=[NODE_NAMES,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Performs maintenance on the list of nodes provided within the Cloud + TPU Queued Resource.. + +EXAMPLES + The following example command performs maintenance on a Cloud TPU Cloud TPU + Queued Resource "my-resource" in zone "us-central1-b" of the default + project, targeting nodes "node-a" and "node-b". + + $ gcloud alpha compute tpus queued-resources perform-maintenance \ + my-resource --zone=us-central1-b --nodeames=node-a,node-b + +POSITIONAL ARGUMENTS + Queued resource resource - The Queued Resource you want to perform + maintenance on. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument queued_resource on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + QUEUED_RESOURCE + ID of the queued_resource or fully qualified identifier for the + queued_resource. + + To set the queued_resource attribute: + ▸ provide the argument queued_resource on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --zone=ZONE + The compute/zone of the Cloud TPU. + + If not specified, will use default compute/zone. + + To set the zone attribute: + ▸ provide the argument queued_resource on the command line with a + fully specified name; + ▸ provide the argument --zone on the command line; + ▸ set the property compute/zone. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --node-names=[NODE_NAMES,...] + The nodes you want to perform maintenance on. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the tpu/v2alpha1 API. The full documentation for this API + can be found at: https://cloud.google.com/tpu/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/tpus/tpu-vm/help b/gcloud/alpha/compute/tpus/tpu-vm/help index d47bb0cb6..64e2f9815 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/help +++ b/gcloud/alpha/compute/tpus/tpu-vm/help @@ -49,6 +49,9 @@ COMMANDS list (ALPHA) List Cloud TPU VM nodes. + perform-maintenance + (ALPHA) perform maintenance on a Cloud TPU VM. + scp (ALPHA) Copy files to and from a Cloud TPU VM via SCP. diff --git a/gcloud/alpha/compute/tpus/tpu-vm/perform-maintenance b/gcloud/alpha/compute/tpus/tpu-vm/perform-maintenance new file mode 100644 index 000000000..306b7c1df --- /dev/null +++ b/gcloud/alpha/compute/tpus/tpu-vm/perform-maintenance @@ -0,0 +1,75 @@ +NAME + gcloud alpha compute tpus tpu-vm perform-maintenance - perform maintenance + on a Cloud TPU VM + +SYNOPSIS + gcloud alpha compute tpus tpu-vm perform-maintenance (TPU : --zone=ZONE) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) perform maintenance on a Cloud TPU VM. + +EXAMPLES + The following example command performs maintenance on a Cloud TPU named + "my-tpu" in the zone "us-central1-b" of the default project. + + $ gcloud alpha compute tpus tpu-vm perform-maintenance my-tpu \ + --zone=us-central1-b + +POSITIONAL ARGUMENTS + Tpu resource - The Cloud TPU on which to perform maintenance. 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 tpu 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. + + TPU + ID of the tpu or fully qualified identifier for the tpu. + + To set the tpu attribute: + ▸ provide the argument tpu on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --zone=ZONE + The compute/zone of the Cloud TPU. + + If not specified, will use default compute/zone. + + To set the zone attribute: + ▸ provide the argument tpu on the command line with a fully + specified name; + ▸ provide the argument --zone on the command line; + ▸ set the property compute/zone. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the tpu/v2alpha1 API. The full documentation for this API + can be found at: https://cloud.google.com/tpu/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/url-maps/invalidate-cdn-cache b/gcloud/alpha/compute/url-maps/invalidate-cdn-cache index 86f419f54..64744decd 100644 --- a/gcloud/alpha/compute/url-maps/invalidate-cdn-cache +++ b/gcloud/alpha/compute/url-maps/invalidate-cdn-cache @@ -4,8 +4,7 @@ NAME SYNOPSIS gcloud alpha compute url-maps invalidate-cdn-cache URLMAP --path=PATH - [--async] [--host=HOST] [--global | --region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--async] [--global] [--host=HOST] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute url-maps invalidate-cdn-cache requests that @@ -45,35 +44,13 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --global + (Default) The URL map is global. Regional URL maps are not supported. + --host=HOST If set, this invalidation will apply only to requests to the specified host. - At most one of these can be specified: - - --global - If set, the URL map is global. - - --region=REGION - Region of the URL map to operate on. If not specified, you might be - prompted to select a region (interactive mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/region property: - - $ gcloud config set compute/region REGION - - A list of regions can be fetched by running: - - $ gcloud compute regions list - - To unset the property, run: - - $ gcloud config unset compute/region - - Alternatively, the region can be stored in the environment variable - CLOUDSDK_COMPUTE_REGION. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/url-maps/list-cdn-cache-invalidations b/gcloud/alpha/compute/url-maps/list-cdn-cache-invalidations index c9ee1f3ba..c9573b6d2 100644 --- a/gcloud/alpha/compute/url-maps/list-cdn-cache-invalidations +++ b/gcloud/alpha/compute/url-maps/list-cdn-cache-invalidations @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha compute url-maps list-cdn-cache-invalidations URL_MAP - [--limit=LIMIT] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] + [--global] [--limit=LIMIT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) List Cloud CDN cache invalidations for a URL map. A cache @@ -16,34 +16,12 @@ POSITIONAL ARGUMENTS Name of the URL map to describe. FLAGS + --global + (Default) The URL map is global. Regional URL maps are not supported. + --limit=LIMIT The maximum number of invalidations to list. - At most one of these can be specified: - - --global - If set, the URL map is global. - - --region=REGION - Region of the URL map to describe. If not specified, you might be - prompted to select a region (interactive mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/region property: - - $ gcloud config set compute/region REGION - - A list of regions can be fetched by running: - - $ gcloud compute regions list - - To unset the property, run: - - $ gcloud config unset compute/region - - Alternatively, the region can be stored in the environment variable - CLOUDSDK_COMPUTE_REGION. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index df1acb9e0..23154fd73 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -10,6 +10,7 @@ SYNOPSIS gpu-sharing-strategy=GPU_SHARING_STRATEGY, max-shared-clients-per-gpu=MAX_SHARED_CLIENTS_PER_GPU],...]] [--addons=[ADDON,...]] [--allow-route-overlap] [--async] + [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] [--autoprovisioning-enable-insecure-kubelet-readonly-port] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] @@ -210,7 +211,8 @@ FLAGS ADDON must be one of: HttpLoadBalancing, HorizontalPodAutoscaling, KubernetesDashboard, NetworkPolicy, NodeLocalDNS, ConfigConnector, GcePersistentDiskCsiDriver, GcpFilestoreCsiDriver, BackupRestore, - GcsFuseCsiDriver, RayOperator, Istio, CloudBuild, CloudRun. + GcsFuseCsiDriver, ParallelstoreCsiDriver, RayOperator, Istio, + CloudBuild, CloudRun. --allow-route-overlap Allows the provided cluster CIDRs to overlap with existing routes that @@ -228,6 +230,12 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --auto-monitoring-scope=AUTO_MONITORING_SCOPE + Enables Auto-Monitoring for a specific scope within the cluster. ALL: + Enables Auto-Monitoring for all supported workloads within the cluster. + NONE: Disables Auto-Monitoring. AUTO_MONITORING_SCOPE must be one of: + ALL, NONE. + --autoprovisioning-enable-insecure-kubelet-readonly-port Enables the Kubelet's insecure read only port for Autoprovisioned Node Pools. @@ -1328,6 +1336,11 @@ FLAGS net.ipv4.tcp_rmem Any positive integer tuple net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + kernel.shmmni Must be [4096, 32768] + kernel.shmmax Must be [0, + 18446744073692774399] + kernel.shmall Must be [0, + 18446744073692774399] List of supported hugepage size in 'hugepageConfig'. diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index 2f6ff26a3..8e03eac56 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud alpha container clusters create-auto NAME [--async] + [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] [--autoprovisioning-enable-insecure-kubelet-readonly-port] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] @@ -69,6 +70,12 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --auto-monitoring-scope=AUTO_MONITORING_SCOPE + Enables Auto-Monitoring for a specific scope within the cluster. ALL: + Enables Auto-Monitoring for all supported workloads within the cluster. + NONE: Disables Auto-Monitoring. AUTO_MONITORING_SCOPE must be one of: + ALL, NONE. + --autoprovisioning-enable-insecure-kubelet-readonly-port Enables the Kubelet's insecure read only port for Autoprovisioned Node Pools. diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 0211d4326..fce1aa289 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -49,7 +49,8 @@ SYNOPSIS | --additional-pod-ipv4-ranges=NAME,[NAME,...] --remove-additional-pod-ipv4-ranges=NAME,[NAME,...] | --additional-zones=[ZONE,...] | --node-locations=ZONE,[ZONE,...] - | --logging=[COMPONENT,...] + | --auto-monitoring-scope=AUTO_MONITORING_SCOPE + --logging=[COMPONENT,...] --monitoring=[COMPONENT,...] --disable-managed-prometheus | --enable-managed-prometheus | --binauthz-policy-bindings=[name=BINAUTHZ_POLICY, @@ -843,6 +844,12 @@ REQUIRED FLAGS --location us-central1-a \ --node-locations us-central1-a,us-central1-b + --auto-monitoring-scope=AUTO_MONITORING_SCOPE + Enables Auto-Monitoring for a specific scope within the cluster. ALL: + Enables Auto-Monitoring for all supported workloads within the + cluster. NONE: Disables Auto-Monitoring. AUTO_MONITORING_SCOPE must + be one of: ALL, NONE. + --logging=[COMPONENT,...] Set the components that have logging enabled. Valid component values are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, diff --git a/gcloud/alpha/container/fleet/memberships/register b/gcloud/alpha/container/fleet/memberships/register index c6cac2330..153b00cc3 100644 --- a/gcloud/alpha/container/fleet/memberships/register +++ b/gcloud/alpha/container/fleet/memberships/register @@ -52,7 +52,8 @@ DESCRIPTION Rerunning this command against the same cluster with the same MEMBERSHIP_NAME and target fleet is successful, and will upgrade the Connect agent if it is supposed to be installed and a newer version is - avaible. + available. Rerunning with --enable-workload-identity ensures that Workload + Identity is enabled on the cluster. EXAMPLES Register a non-GKE cluster referenced from a specific kubeconfig file, and diff --git a/gcloud/alpha/container/hub/memberships/register b/gcloud/alpha/container/hub/memberships/register index a76c1603f..0f5294f64 100644 --- a/gcloud/alpha/container/hub/memberships/register +++ b/gcloud/alpha/container/hub/memberships/register @@ -52,7 +52,8 @@ DESCRIPTION Rerunning this command against the same cluster with the same MEMBERSHIP_NAME and target fleet is successful, and will upgrade the Connect agent if it is supposed to be installed and a newer version is - avaible. + available. Rerunning with --enable-workload-identity ensures that Workload + Identity is enabled on the cluster. EXAMPLES Register a non-GKE cluster referenced from a specific kubeconfig file, and diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index a852cf6de..acca5257e 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -726,6 +726,11 @@ FLAGS net.ipv4.tcp_rmem Any positive integer tuple net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + kernel.shmmni Must be [4096, 32768] + kernel.shmmax Must be [0, + 18446744073692774399] + kernel.shmall Must be [0, + 18446744073692774399] List of supported hugepage size in 'hugepageConfig'. diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index 67c89e181..de8b7e94f 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -306,6 +306,11 @@ REQUIRED FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + kernel.shmmni Must be [4096, 32768] + kernel.shmmax Must be [0, + 18446744073692774399] + kernel.shmall Must be [0, + 18446744073692774399] List of supported hugepage size in 'hugepageConfig'. diff --git a/gcloud/alpha/dataproc/clusters/create b/gcloud/alpha/dataproc/clusters/create index 0bbce2dff..e57701a61 100644 --- a/gcloud/alpha/dataproc/clusters/create +++ b/gcloud/alpha/dataproc/clusters/create @@ -17,6 +17,8 @@ SYNOPSIS [--initialization-actions=CLOUD_STORAGE_URI,[...]] [--labels=[KEY=VALUE,...]] [--master-accelerator=[type=TYPE,[count=COUNT],...]] + [--master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS] + [--master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--master-boot-disk-size=MASTER_BOOT_DISK_SIZE] [--master-boot-disk-type=MASTER_BOOT_DISK_TYPE] [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] @@ -43,6 +45,8 @@ SYNOPSIS [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] + [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] [--worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE] @@ -218,6 +222,22 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the disk. This sets the limit for disk I/O operations per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + + --master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) to + provision for the disk. This sets the limit for throughput in MiB per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + --master-boot-disk-size=MASTER_BOOT_DISK_SIZE The size of the boot 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 @@ -414,6 +434,22 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the disk. This sets the limit for disk I/O operations per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + + --worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) to + provision for the disk. This sets the limit for throughput in MiB per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + --worker-boot-disk-size=WORKER_BOOT_DISK_SIZE The size of the boot 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 diff --git a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster index d474d1404..ef1e1b1f2 100644 --- a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster @@ -11,6 +11,8 @@ SYNOPSIS [--initialization-actions=CLOUD_STORAGE_URI,[...]] [--labels=[KEY=VALUE,...]] [--master-accelerator=[type=TYPE,[count=COUNT],...]] + [--master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS] + [--master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--master-boot-disk-size=MASTER_BOOT_DISK_SIZE] [--master-boot-disk-type=MASTER_BOOT_DISK_TYPE] [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] @@ -36,6 +38,8 @@ SYNOPSIS [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] + [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] [--worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE] @@ -158,6 +162,22 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the disk. This sets the limit for disk I/O operations per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + + --master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) to + provision for the disk. This sets the limit for throughput in MiB per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + --master-boot-disk-size=MASTER_BOOT_DISK_SIZE The size of the boot 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 @@ -346,6 +366,22 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the disk. This sets the limit for disk I/O operations per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + + --worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) to + provision for the disk. This sets the limit for throughput in MiB per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + --worker-boot-disk-size=WORKER_BOOT_DISK_SIZE The size of the boot 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 diff --git a/gcloud/alpha/memorystore/instances/create b/gcloud/alpha/memorystore/instances/create index 32a473d9b..c0c3a17bd 100644 --- a/gcloud/alpha/memorystore/instances/create +++ b/gcloud/alpha/memorystore/instances/create @@ -4,12 +4,11 @@ NAME SYNOPSIS gcloud alpha memorystore instances create (INSTANCE : --location=LOCATION) --psc-auto-connections=[network=NETWORK],[projectId=PROJECTID] - --shard-count=SHARD_COUNT [--async] - [--authorization-mode=AUTHORIZATION_MODE] + [--async] [--authorization-mode=AUTHORIZATION_MODE] [--deletion-protection-enabled] [--engine-configs=[ENGINE_CONFIGS,...]] - [--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]] + [--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]] [--mode=MODE] [--node-type=NODE_TYPE] [--replica-count=REPLICA_COUNT] - [--request-id=REQUEST_ID] + [--request-id=REQUEST_ID] [--shard-count=SHARD_COUNT] [--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE] [--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC --persistence-config-mode=PERSISTENCE_CONFIG_MODE @@ -101,9 +100,6 @@ REQUIRED FLAGS --psc-auto-connections=path_to_file.(yaml|json) - --shard-count=SHARD_COUNT - Number of shards for the instance. - OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to @@ -169,6 +165,14 @@ OPTIONAL FLAGS --labels=path_to_file.(yaml|json) + --mode=MODE + The mode config for the instance. MODE must be one of: + + cluster + Instance is in cluster mode. + standalone + Instance is in standalone mode. + --node-type=NODE_TYPE Machine type for individual nodes of the instance. NODE_TYPE must be one of: @@ -203,6 +207,9 @@ OPTIONAL FLAGS The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). + --shard-count=SHARD_COUNT + Number of shards for the instance. + --transit-encryption-mode=TRANSIT_ENCRYPTION_MODE In-transit encryption mode of the instance. TRANSIT_ENCRYPTION_MODE must be one of: diff --git a/gcloud/alpha/network-connectivity/internal-ranges/create b/gcloud/alpha/network-connectivity/internal-ranges/create index 0df95310b..5ffdbc7e7 100644 --- a/gcloud/alpha/network-connectivity/internal-ranges/create +++ b/gcloud/alpha/network-connectivity/internal-ranges/create @@ -7,7 +7,7 @@ SYNOPSIS (INTERNAL_RANGE : --region=REGION) --network=NETWORK (--ip-cidr-range=IP_CIDR_RANGE | [--prefix-length=PREFIX_LENGTH : --target-cidr-range=[TARGET_CIDR_RANGE,...]]) [--async] - [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--description=DESCRIPTION] [--immutable] [--labels=[KEY=VALUE,...]] [--overlaps=[OVERLAPS,...]] [--peering=PEERING; default="for-self"] [--usage=USAGE; default="for-vpc"] [--migration-source=MIGRATION_SOURCE @@ -104,6 +104,10 @@ OPTIONAL FLAGS --description=DESCRIPTION Description of the internal range to be created. + --immutable + Mark the internal range as immutable. Then only non-semantic fields + like description and labels could be modified after creation. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/alpha/network-services/multicast-group-definitions/create b/gcloud/alpha/network-services/multicast-group-definitions/create index 27a445e3e..d922d6409 100644 --- a/gcloud/alpha/network-services/multicast-group-definitions/create +++ b/gcloud/alpha/network-services/multicast-group-definitions/create @@ -7,6 +7,7 @@ SYNOPSIS (MULTICAST_GROUP_DEFINITION : --location=LOCATION) --multicast-domain=MULTICAST_DOMAIN --reserved-internal-range=RESERVED_INTERNAL_RANGE [--async] + [--consumer-accept-list=[CONSUMER_ACCEPT_LIST,...]] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] @@ -69,6 +70,10 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --consumer-accept-list=[CONSUMER_ACCEPT_LIST,...] + An optional list of consumer projects that can use this multicast group + definition. + --description=DESCRIPTION The description for the multicast group definition. diff --git a/gcloud/alpha/recaptcha/keys/add-ip-override b/gcloud/alpha/recaptcha/keys/add-ip-override new file mode 100644 index 000000000..314a848b9 --- /dev/null +++ b/gcloud/alpha/recaptcha/keys/add-ip-override @@ -0,0 +1,62 @@ +NAME + gcloud alpha recaptcha keys add-ip-override - add an IP override to a key + +SYNOPSIS + gcloud alpha recaptcha keys add-ip-override KEY --ip=IP --override=OVERRIDE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Add an IP override to a key. + +EXAMPLES + $ gcloud alpha recaptcha keys add-ip-override test-key \ + --ip=1.2.3.4 --override=allow + +POSITIONAL ARGUMENTS + Key resource - The reCAPTCHA key to add the IP override to. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument key 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. + + KEY + ID of the key or fully qualified identifier for the key. + + To set the key attribute: + ▸ provide the argument key on the command line. + +REQUIRED FLAGS + --ip=IP + IP address to override for the key. + + --override=OVERRIDE + If set to allow, the IP address/CIDR range will be allowlisted for the + key. OVERRIDE must be one of: allow, override-type-unspecified. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the recaptchaenterprise/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/recaptcha-enterprise/ + +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 recaptcha keys add-ip-override + diff --git a/gcloud/alpha/recaptcha/keys/help b/gcloud/alpha/recaptcha/keys/help index cc1a7a0bf..8de57abe3 100644 --- a/gcloud/alpha/recaptcha/keys/help +++ b/gcloud/alpha/recaptcha/keys/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add-ip-override + (ALPHA) Add an IP override to a key. + create (ALPHA) Create a Key. @@ -30,6 +33,9 @@ COMMANDS migrate (ALPHA) Migrate a key to reCAPTCHA Enterprise. + remove-ip-override + (ALPHA) Remove an IP override from a key. + update (ALPHA) Update a Key. diff --git a/gcloud/alpha/recaptcha/keys/remove-ip-override b/gcloud/alpha/recaptcha/keys/remove-ip-override new file mode 100644 index 000000000..649950a6f --- /dev/null +++ b/gcloud/alpha/recaptcha/keys/remove-ip-override @@ -0,0 +1,64 @@ +NAME + gcloud alpha recaptcha keys remove-ip-override - remove an IP override from + a key + +SYNOPSIS + gcloud alpha recaptcha keys remove-ip-override KEY --ip=IP + --override=OVERRIDE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Remove an IP override from a key. + +EXAMPLES + $ gcloud alpha recaptcha keys remove-ip-override test-key \ + --ip=1.2.3.4 --override=allow + +POSITIONAL ARGUMENTS + Key resource - The reCAPTCHA key from which to remove the IP override. + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument key 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. + + KEY + ID of the key or fully qualified identifier for the key. + + To set the key attribute: + ▸ provide the argument key on the command line. + +REQUIRED FLAGS + --ip=IP + IP address to override for the key. + + --override=OVERRIDE + If set to allow, the IP address/CIDR range will be removed from the + allowlisted IPs. OVERRIDE must be one of: allow, + override-type-unspecified. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the recaptchaenterprise/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/recaptcha-enterprise/ + +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 recaptcha keys remove-ip-override + diff --git a/gcloud/alpha/redis/clusters/add-cluster-endpoints b/gcloud/alpha/redis/clusters/add-cluster-endpoints new file mode 100644 index 000000000..6eb728b1c --- /dev/null +++ b/gcloud/alpha/redis/clusters/add-cluster-endpoints @@ -0,0 +1,133 @@ +NAME + gcloud alpha redis clusters add-cluster-endpoints - add more cluster + endpoints + +SYNOPSIS + gcloud alpha redis clusters add-cluster-endpoints + (CLUSTER : --region=REGION) + --cluster-endpoint=[psc-connection=PSC-CONNECTION] [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This is required to enable multi-vpc for Redis cluster. + + To add one cluster endpoint to an existing Redis cluster, two PSC + connections MUST be added as a pair: one for the Redis cluster's discovery + service attachment and the other for the additional service attachment. + + Multiple cluster endpoints COULD be added simultaneously. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The number of connections provided to a cluster endpoint are not in + pairs. + ▪ One of the connections is not found. + +EXAMPLES + To connect redis cluster to one additional VPC, run: + + $ gcloud alpha redis clusters add-cluster-endpoints \ + my-redis-cluster add-cluster-endpoints \ + --cluster-endpoint='["psc-connection":[{"psc-connection-id":"$ID\ + ","address":"$IP","network":"projects/$PROJECT/global/networks/$NETW\ + ORK","forwarding-rule":"projects/$PROJECT/regions/us-east1/forwardin\ + gRules/$FR_NAME","service-attachment":"projects/$PROJECT/regions/$RE\ + GION/serviceAttachments/$SA_NAME"},{$ADDITIONAL_PSC_CONNECTION}]]' \ + --cluster_endpoint=$ADDITIONAL_CLUSTER_ENDPOINT \ + $PSCConnectionID SHOULD be extracted from forwarding rules. \ + E.g. 75311697652483351 + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Memorystore Redis + cluster you want to update. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +REQUIRED FLAGS + --cluster-endpoint=[psc-connection=PSC-CONNECTION] + Required, Resource details of a redis cluster endpoint. + + psc-connection + Sets psc-connection value. + + address + Sets address value. + + forwarding-rule + Sets forwarding-rule value. + + network + Sets network value. + + psc-connection-id + Sets psc-connection-id value. + + service-attachment + Sets service-attachment value. + + Shorthand Example: + + --cluster-endpoint='psc-connection=[{"address": "string", "forwarding-rule": "string", "network": "string", "psc-connection-id": "string", "service-attachment": "string"}]' --cluster-endpoint='psc-connection=[{"address": "string", "forwarding-rule": "string", "network": "string", "psc-connection-id": "string", "service-attachment": "string"}]' + + JSON Example: + + --cluster-endpoint='[{"psc-connection": [{"address": "string", "forwarding-rule": "string", "network": "string", "psc-connection-id": "string", "service-attachment": "string"}]}]' + + File Example: + + --cluster-endpoint=path_to_file.(yaml|json) + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud redis clusters add-cluster-endpoints + + $ gcloud beta redis clusters add-cluster-endpoints + diff --git a/gcloud/alpha/redis/clusters/help b/gcloud/alpha/redis/clusters/help index c3ef33d7b..2dd167e00 100644 --- a/gcloud/alpha/redis/clusters/help +++ b/gcloud/alpha/redis/clusters/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add-cluster-endpoints + (ALPHA) Add more cluster endpoints. + create (ALPHA) Create a new Memorystore for Redis Cluster instance. @@ -38,6 +41,9 @@ COMMANDS list (ALPHA) List Memorystore for Redis Cluster instances. + remove-cluster-endpoints + (ALPHA) Remove existing Memorystore cluster endpoints. + reschedule-maintenance (ALPHA) Reschedule maintenance window for a Memorystore for Redis Cluster instance. diff --git a/gcloud/alpha/redis/clusters/remove-cluster-endpoints b/gcloud/alpha/redis/clusters/remove-cluster-endpoints new file mode 100644 index 000000000..fb8b346bf --- /dev/null +++ b/gcloud/alpha/redis/clusters/remove-cluster-endpoints @@ -0,0 +1,115 @@ +NAME + gcloud alpha redis clusters remove-cluster-endpoints - remove existing + Memorystore cluster endpoints + +SYNOPSIS + gcloud alpha redis clusters remove-cluster-endpoints + (CLUSTER : --region=REGION) + --cluster-endpoint=[psc-connection=PSC-CONNECTION] [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) To remove one cluster endpoint from an existing Redis cluster, two + PSC connections MUST be removed as a pair: one to the Redis cluster's + discovery service attachment and the other to its additional service + attachment. + + Multiple cluster endpoints COULD be removed simultaneously. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ Some connections in the to be removed list do not exist. + +EXAMPLES + To remove an endpoint from redis cluster, run: + + $ gcloud alpha redis clusters remove-cluster-endpoints \ + my-redis-cluster remove-cluster-endpoints \ + --cluster-endpoint='["psc-connection":[{"psc-connection-id":"$PS\ + C_CONNECTION_ID"},{$ADDITIONAL_PSC_CONNECTION}]]' \ + --cluster_endpoint=$ADDITIONAL_CLUSTER_ENDPOINT \ + $PSCConnectionID SHOULD be extracted from forwarding rules. \ + E.g. 75311697652483351 + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Memorystore Redis + cluster you want to update. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +REQUIRED FLAGS + --cluster-endpoint=[psc-connection=PSC-CONNECTION] + Required, Resource details of a redis cluster endpoint. + + psc-connection + Sets psc-connection value. + + psc-connection-id + Sets psc-connection-id value. + + Shorthand Example: + + --cluster-endpoint='psc-connection=[{"psc-connection-id": "string"}]' --cluster-endpoint='psc-connection=[{"psc-connection-id": "string"}]' + + JSON Example: + + --cluster-endpoint='[{"psc-connection": [{"psc-connection-id": "string"}]}]' + + File Example: + + --cluster-endpoint=path_to_file.(yaml|json) + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud redis clusters remove-cluster-endpoints + + $ gcloud beta redis clusters remove-cluster-endpoints + diff --git a/gcloud/alpha/redis/instances/create b/gcloud/alpha/redis/instances/create index 8e736c725..66e070f13 100644 --- a/gcloud/alpha/redis/instances/create +++ b/gcloud/alpha/redis/instances/create @@ -163,7 +163,7 @@ FLAGS parameters are: Redis version 3.2 and newer: maxmemory-policy, notify-keyspace-events, - timeout. + timeout, databases. Redis version 4.0 and newer: activedefrag, lfu-decay-time, lfu-log-factor, maxmemory-gb. diff --git a/gcloud/alpha/source/repos/update b/gcloud/alpha/source/repos/update index 6c22efa8e..0ebc585c9 100644 --- a/gcloud/alpha/source/repos/update +++ b/gcloud/alpha/source/repos/update @@ -13,8 +13,9 @@ EXAMPLES To associate a Cloud Pub/Sub topic to receive repository update notifications, run: - $ gcloud alpha source repos update --add-topic=TOPIC_NAME \ - --service-account=SERVICE_ACCOUNT_EMAIL --message-format=json + $ gcloud alpha source repos update REPO_NAME \ + --add-topic=TOPIC_NAME --service-account=SERVICE_ACCOUNT_EMAIL \ + --message-format=json POSITIONAL ARGUMENTS Repo resource - Name of the Cloud Source repository to update. This diff --git a/gcloud/alpha/workstations/configs/create b/gcloud/alpha/workstations/configs/create index 9e0371980..a208459ab 100644 --- a/gcloud/alpha/workstations/configs/create +++ b/gcloud/alpha/workstations/configs/create @@ -18,6 +18,7 @@ SYNOPSIS [--disable-tcp-connections] [--enable-audit-agent] [--enable-confidential-compute] [--enable-nested-virtualization] [--enable-ssh-to-vm] [--ephemeral-directory=[PROPERTY=VALUE,...]] + [--grant-workstation-admin-role-on-create] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] @@ -265,6 +266,11 @@ FLAGS --ephemeral-directory=[PROPERTY=VALUE,...] Ephemeral directory which won't persist across workstation sessions. + --grant-workstation-admin-role-on-create + Default value is false. If set, creator of a workstation will get + roles/workstations.policyAdmin role along with roles/workstations.user + role on the workstation created by them. + --idle-timeout=IDLE_TIMEOUT; default=7200 How long (in seconds) to wait before automatically stopping an instance that hasn't received any user traffic. A value of 0 indicates that this diff --git a/gcloud/alpha/workstations/configs/update b/gcloud/alpha/workstations/configs/update index 74175ae3c..6eeab0abe 100644 --- a/gcloud/alpha/workstations/configs/update +++ b/gcloud/alpha/workstations/configs/update @@ -14,6 +14,7 @@ SYNOPSIS [--container-working-dir=CONTAINER_WORKING_DIR] [--disable-public-ip-addresses] [--enable-audit-agent] [--enable-confidential-compute] [--enable-nested-virtualization] + [--grant-workstation-admin-role-on-create] [--idle-timeout=IDLE_TIMEOUT] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE] [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] @@ -226,6 +227,11 @@ FLAGS Default value is false. If set, instances will have nested virtualization enabled. + --grant-workstation-admin-role-on-create + Default value is false. If set, creator of a workstation will get + roles/workstations.policyAdmin role along with roles/workstations.user + role on the workstation created by them. + --idle-timeout=IDLE_TIMEOUT How long (in seconds) to wait before automatically stopping an instance that hasn't received any user traffic. A value of 0 indicates that this diff --git a/gcloud/artifacts/docker/upgrade/migrate b/gcloud/artifacts/docker/upgrade/migrate index 59885b150..ee489d1ce 100644 --- a/gcloud/artifacts/docker/upgrade/migrate +++ b/gcloud/artifacts/docker/upgrade/migrate @@ -3,10 +3,10 @@ NAME Registry to Artifact Registry SYNOPSIS - gcloud artifacts docker upgrade migrate [--copy-only] - [--from-gcr=GCR_HOST/PROJECT_ID] [--last-uploaded-versions=N] - [--max-threads=MAX_THREADS; default=8] [--projects=PROJECTS] - [--recent-images=NUM_DAYS] [--skip-iam-update] + gcloud artifacts docker upgrade migrate [--canary-reads=PERCENT] + [--copy-only] [--from-gcr=GCR_HOST/PROJECT_ID] + [--last-uploaded-versions=N] [--max-threads=MAX_THREADS; default=8] + [--projects=PROJECTS] [--recent-images=NUM_DAYS] [--skip-iam-update] [--to-pkg-dev=PROJECT_ID/REPOSITORY_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -28,6 +28,10 @@ EXAMPLES --from-gcr=gcr.io/project1 --to-pkg-dev=project2/repo_name FLAGS + --canary-reads=PERCENT + Send only a percent of reads to Artifact Registry. The rest of reads + and all writes are sent to Container Registry. + --copy-only Only perform image copying diff --git a/gcloud/beta/access-approval/settings/update b/gcloud/beta/access-approval/settings/update index e1beb3512..5f4c44c7b 100644 --- a/gcloud/beta/access-approval/settings/update +++ b/gcloud/beta/access-approval/settings/update @@ -7,6 +7,11 @@ SYNOPSIS [--active_key_version=ACTIVE_KEY_VERSION] [--enrolled_services=ENROLLED_SERVICES] [--notification_emails=NOTIFICATION_EMAILS] + [--notification_pubsub_topic=NOTIFICATION_PUBSUB_TOPIC] + [--prefer_no_broad_approval_requests=PREFER_NO_BROAD_APPROVAL_REQUESTS] + [--preferred_request_expiration_days=PREFERRED_REQUEST_EXPIRATION_DAYS] + [--request_scope_max_width_preference=REQUEST_SCOPE_MAX_WIDTH_PREFERENCE] + [--require_customer_visible_justification=REQUIRE_CUSTOMER_VISIBLE_JUSTIFICATION] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -41,6 +46,26 @@ EXAMPLES --active_key_version='projects/p1/locations/global/keyRings/sign\ ing-keys/cryptoKeys/signing-key/cryptoKeyVersions/1' + Update preferred request expiration days for project p1: + + $ gcloud beta access-approval settings update --project=p1 \ + --preferred_request_expiration_days=5 + + Enable prefer no broad approval requests for project p1: + + $ gcloud beta access-approval settings update --project=p1 \ + --prefer_no_broad_approval_requests=true + + Update notification pubsub topic for project p1: + + $ gcloud beta access-approval settings update --project=p1 \ + --notification_pubsub_topic='exampleTopic' + + Update request scope max width preference for project p1: + + $ gcloud beta access-approval settings update --project=p1 \ + --request_scope_max_width_preference=PROJECT + FLAGS --active_key_version=ACTIVE_KEY_VERSION The asymmetric crypto key version to use for signing approval requests. @@ -56,6 +81,29 @@ FLAGS to approval requests should be sent or '' to clear all saved notification emails. + --notification_pubsub_topic=NOTIFICATION_PUBSUB_TOPIC + The pubsub topic to publish notifications to when approval requests are + made. + + --prefer_no_broad_approval_requests=PREFER_NO_BROAD_APPROVAL_REQUESTS + If set to true it will communicate the preference to Google personnel + to request access with as targeted a resource scope as possible. + + --preferred_request_expiration_days=PREFERRED_REQUEST_EXPIRATION_DAYS + The default expiration time for approval requests. This value must be + between 1 and 30. Note that this can be overridden at time of Approval + Request creation and modified by the customer at approval time. + + --request_scope_max_width_preference=REQUEST_SCOPE_MAX_WIDTH_PREFERENCE + The preference for the broadest scope of access for access requests + without a specific method. REQUEST_SCOPE_MAX_WIDTH_PREFERENCE must be + one of: ORGANIZATION, FOLDER, PROJECT. + + --require_customer_visible_justification=REQUIRE_CUSTOMER_VISIBLE_JUSTIFICATION + The preference to configure if a customer visible justification (i.e. + Vector Case) is required for a Googler to create an Access Ticket to + send to the customer when attempting to access customer resources. + At most one of these can be specified: --folder=FOLDER diff --git a/gcloud/beta/alloydb/backups/create b/gcloud/beta/alloydb/backups/create index 2efaba54c..090e5038c 100644 --- a/gcloud/beta/alloydb/backups/create +++ b/gcloud/beta/alloydb/backups/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta alloydb backups create BACKUP --cluster=CLUSTER --region=REGION - [--async] + [--async] [--tags=[KEY=VALUE,...]] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -45,6 +45,12 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. + + Example: 123/environment=production,123/costCenter=marketing + Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the backup. The 'AlloyDB Service Agent' service account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. The diff --git a/gcloud/beta/colab-enterprise/runtimes/assign b/gcloud/beta/colab-enterprise/runtimes/assign index b35c89557..eefcbdb2d 100644 --- a/gcloud/beta/colab-enterprise/runtimes/assign +++ b/gcloud/beta/colab-enterprise/runtimes/assign @@ -9,8 +9,10 @@ SYNOPSIS [--runtime-user=RUNTIME_USER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Assign a notebook runtime to run code from your notebook (IPYNB - file). + (BETA) (DEPRECATED) This command is deprecated. Please use gcloud beta + colab runtimes create instead. + + Assign a notebook runtime to run code from your notebook (IPYNB file). EXAMPLES To create a runtime in region 'us-central1' with the display name @@ -28,7 +30,7 @@ EXAMPLES REQUIRED FLAGS --display-name=DISPLAY_NAME - The display name of the runtime to assign. + The display name of the runtime to create. Runtime template resource - Unique name of the runtime template to configure the runtime with. This was optionally provided by setting @@ -69,7 +71,7 @@ OPTIONAL FLAGS --labels=[KEY=VALUE,...] Add labels to identify and group the runtime template. - Region resource - Cloud region to assign runtime. Please see + Region resource - Cloud region to create runtime. Please see https://cloud.google.com/colab/docs/locations for a list of supported regions. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -89,7 +91,7 @@ OPTIONAL FLAGS ▸ set the property colab/region. --runtime-id=RUNTIME_ID - The id of the runtime to assign. If not specified, a random id will be + The id of the runtime to create. If not specified, a random id will be generated. --runtime-user=RUNTIME_USER diff --git a/gcloud/beta/colab-enterprise/runtimes/create b/gcloud/beta/colab-enterprise/runtimes/create new file mode 100644 index 000000000..bd7e0c2ae --- /dev/null +++ b/gcloud/beta/colab-enterprise/runtimes/create @@ -0,0 +1,110 @@ +NAME + gcloud beta colab-enterprise runtimes create - create a notebook runtime + +SYNOPSIS + gcloud beta colab-enterprise runtimes create --display-name=DISPLAY_NAME + --runtime-template=RUNTIME_TEMPLATE [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--region=REGION] [--runtime-id=RUNTIME_ID] + [--runtime-user=RUNTIME_USER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a notebook runtime that can be used to run code from your + notebook (IPYNB file). + +EXAMPLES + To create a runtime in region 'us-central1' with the display name + 'my-runtime' and template with id 'my-template', run: + + $ gcloud beta colab-enterprise runtimes create \ + --region=us-central1 --display-name=my-runtime \ + --runtime-template=my-template + + To create a runtime for user 'USER@DOMAIN.COM', run: + + $ gcloud beta colab-enterprise runtimes create \ + --runtime-user=USER@DOMAIN.COM --region=us-central1 \ + --display-name=my-runtime --runtime-template=my-template + +REQUIRED FLAGS + --display-name=DISPLAY_NAME + The display name of the runtime to create. + + Runtime template resource - Unique name of the runtime template to + configure the runtime with. This was optionally provided by setting + --runtime-template-id in the create runtime-template command, or was + system-generated if unspecified. This represents a Cloud resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument --runtime-template on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the region attribute: + ◆ provide the argument --runtime-template on the command line with a + fully specified name; + ◆ provide the argument --region on the command line; + ◆ set the property colab/region. + + This must be specified. + + --runtime-template=RUNTIME_TEMPLATE + ID of the runtime template or fully qualified identifier for the + runtime template. + + To set the name attribute: + ▸ provide the argument --runtime-template on the command line. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description + + --labels=[KEY=VALUE,...] + Add labels to identify and group the runtime template. + + Region resource - Cloud region to create runtime. Please see + https://cloud.google.com/colab/docs/locations for a list of supported + regions. This represents a Cloud resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --region on the command line with a fully + specified name; + ◆ set the property colab/region with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. + + --runtime-id=RUNTIME_ID + The id of the runtime to create. If not specified, a random id will be + generated. + + --runtime-user=RUNTIME_USER + User email for the runtime owner. Runtimes can only be used by the + owner. If a user is not provided, the gcloud user will be assumed to be + the owner. The user cannot be a service account. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/colab-enterprise/runtimes/delete b/gcloud/beta/colab-enterprise/runtimes/delete index 20a56a781..13703dd13 100644 --- a/gcloud/beta/colab-enterprise/runtimes/delete +++ b/gcloud/beta/colab-enterprise/runtimes/delete @@ -16,7 +16,7 @@ EXAMPLES POSITIONAL ARGUMENTS Runtime resource - Unique name of the runtime to delete. This was - optionally provided by setting --runtime-id in the assign runtime command, + optionally provided by setting --runtime-id in the create runtime command, or was system-generated if unspecified. 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. diff --git a/gcloud/beta/colab-enterprise/runtimes/describe b/gcloud/beta/colab-enterprise/runtimes/describe index 6fc552d9c..c082cbcb8 100644 --- a/gcloud/beta/colab-enterprise/runtimes/describe +++ b/gcloud/beta/colab-enterprise/runtimes/describe @@ -16,7 +16,7 @@ EXAMPLES POSITIONAL ARGUMENTS Runtime resource - Unique name of the runtime to describe. This was - optionally provided by setting --runtime-id in the assign runtime command, + optionally provided by setting --runtime-id in the create runtime command, or was system-generated if unspecified. 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. diff --git a/gcloud/beta/colab-enterprise/runtimes/help b/gcloud/beta/colab-enterprise/runtimes/help index 5c5c6b9ce..89700a13f 100644 --- a/gcloud/beta/colab-enterprise/runtimes/help +++ b/gcloud/beta/colab-enterprise/runtimes/help @@ -17,7 +17,10 @@ COMMANDS COMMAND is one of the following: assign - (BETA) Assign a notebook runtime. + (BETA) (DEPRECATED) Assign a notebook runtime. + + create + (BETA) Create a notebook runtime. delete (BETA) Delete a runtime. diff --git a/gcloud/beta/colab-enterprise/runtimes/start b/gcloud/beta/colab-enterprise/runtimes/start index 013024a28..ec14fe3f8 100644 --- a/gcloud/beta/colab-enterprise/runtimes/start +++ b/gcloud/beta/colab-enterprise/runtimes/start @@ -16,7 +16,7 @@ EXAMPLES POSITIONAL ARGUMENTS Runtime resource - Unique name of the runtime to start. This was - optionally provided by setting --runtime-id in the assign runtime command, + optionally provided by setting --runtime-id in the create runtime command, or was system-generated if unspecified. 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. diff --git a/gcloud/beta/colab-enterprise/runtimes/upgrade b/gcloud/beta/colab-enterprise/runtimes/upgrade index 4aed69754..3e8e23634 100644 --- a/gcloud/beta/colab-enterprise/runtimes/upgrade +++ b/gcloud/beta/colab-enterprise/runtimes/upgrade @@ -16,7 +16,7 @@ EXAMPLES POSITIONAL ARGUMENTS Runtime resource - Unique name of the runtime to upgrade. This was - optionally provided by setting --runtime-id in the assign runtime command, + optionally provided by setting --runtime-id in the create runtime command, or was system-generated if unspecified. 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. diff --git a/gcloud/beta/colab/runtimes/assign b/gcloud/beta/colab/runtimes/assign index a2e001a15..f562dcc54 100644 --- a/gcloud/beta/colab/runtimes/assign +++ b/gcloud/beta/colab/runtimes/assign @@ -9,8 +9,10 @@ SYNOPSIS [--runtime-user=RUNTIME_USER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Assign a notebook runtime to run code from your notebook (IPYNB - file). + (BETA) (DEPRECATED) This command is deprecated. Please use gcloud beta + colab runtimes create instead. + + Assign a notebook runtime to run code from your notebook (IPYNB file). EXAMPLES To create a runtime in region 'us-central1' with the display name @@ -27,7 +29,7 @@ EXAMPLES REQUIRED FLAGS --display-name=DISPLAY_NAME - The display name of the runtime to assign. + The display name of the runtime to create. Runtime template resource - Unique name of the runtime template to configure the runtime with. This was optionally provided by setting @@ -68,7 +70,7 @@ OPTIONAL FLAGS --labels=[KEY=VALUE,...] Add labels to identify and group the runtime template. - Region resource - Cloud region to assign runtime. Please see + Region resource - Cloud region to create runtime. Please see https://cloud.google.com/colab/docs/locations for a list of supported regions. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -88,7 +90,7 @@ OPTIONAL FLAGS ▸ set the property colab/region. --runtime-id=RUNTIME_ID - The id of the runtime to assign. If not specified, a random id will be + The id of the runtime to create. If not specified, a random id will be generated. --runtime-user=RUNTIME_USER diff --git a/gcloud/beta/colab/runtimes/create b/gcloud/beta/colab/runtimes/create new file mode 100644 index 000000000..6856d24a9 --- /dev/null +++ b/gcloud/beta/colab/runtimes/create @@ -0,0 +1,109 @@ +NAME + gcloud beta colab runtimes create - create a notebook runtime + +SYNOPSIS + gcloud beta colab runtimes create --display-name=DISPLAY_NAME + --runtime-template=RUNTIME_TEMPLATE [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--region=REGION] [--runtime-id=RUNTIME_ID] + [--runtime-user=RUNTIME_USER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a notebook runtime that can be used to run code from your + notebook (IPYNB file). + +EXAMPLES + To create a runtime in region 'us-central1' with the display name + 'my-runtime' and template with id 'my-template', run: + + $ gcloud beta colab runtimes create --region=us-central1 \ + --display-name=my-runtime --runtime-template=my-template + + To create a runtime for user 'USER@DOMAIN.COM', run: + + $ gcloud beta colab runtimes create --runtime-user=USER@DOMAIN.COM \ + --region=us-central1 --display-name=my-runtime \ + --runtime-template=my-template + +REQUIRED FLAGS + --display-name=DISPLAY_NAME + The display name of the runtime to create. + + Runtime template resource - Unique name of the runtime template to + configure the runtime with. This was optionally provided by setting + --runtime-template-id in the create runtime-template command, or was + system-generated if unspecified. This represents a Cloud resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument --runtime-template on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the region attribute: + ◆ provide the argument --runtime-template on the command line with a + fully specified name; + ◆ provide the argument --region on the command line; + ◆ set the property colab/region. + + This must be specified. + + --runtime-template=RUNTIME_TEMPLATE + ID of the runtime template or fully qualified identifier for the + runtime template. + + To set the name attribute: + ▸ provide the argument --runtime-template on the command line. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description + + --labels=[KEY=VALUE,...] + Add labels to identify and group the runtime template. + + Region resource - Cloud region to create runtime. Please see + https://cloud.google.com/colab/docs/locations for a list of supported + regions. This represents a Cloud resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --region on the command line with a fully + specified name; + ◆ set the property colab/region with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. + + --runtime-id=RUNTIME_ID + The id of the runtime to create. If not specified, a random id will be + generated. + + --runtime-user=RUNTIME_USER + User email for the runtime owner. Runtimes can only be used by the + owner. If a user is not provided, the gcloud user will be assumed to be + the owner. The user cannot be a service account. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/colab/runtimes/delete b/gcloud/beta/colab/runtimes/delete index de7cee976..0e348a27e 100644 --- a/gcloud/beta/colab/runtimes/delete +++ b/gcloud/beta/colab/runtimes/delete @@ -15,7 +15,7 @@ EXAMPLES POSITIONAL ARGUMENTS Runtime resource - Unique name of the runtime to delete. This was - optionally provided by setting --runtime-id in the assign runtime command, + optionally provided by setting --runtime-id in the create runtime command, or was system-generated if unspecified. 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. diff --git a/gcloud/beta/colab/runtimes/describe b/gcloud/beta/colab/runtimes/describe index 75e6988c7..df6646735 100644 --- a/gcloud/beta/colab/runtimes/describe +++ b/gcloud/beta/colab/runtimes/describe @@ -15,7 +15,7 @@ EXAMPLES POSITIONAL ARGUMENTS Runtime resource - Unique name of the runtime to describe. This was - optionally provided by setting --runtime-id in the assign runtime command, + optionally provided by setting --runtime-id in the create runtime command, or was system-generated if unspecified. 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. diff --git a/gcloud/beta/colab/runtimes/help b/gcloud/beta/colab/runtimes/help index 6b579b5be..1b5771f62 100644 --- a/gcloud/beta/colab/runtimes/help +++ b/gcloud/beta/colab/runtimes/help @@ -17,7 +17,10 @@ COMMANDS COMMAND is one of the following: assign - (BETA) Assign a notebook runtime. + (BETA) (DEPRECATED) Assign a notebook runtime. + + create + (BETA) Create a notebook runtime. delete (BETA) Delete a runtime. diff --git a/gcloud/beta/colab/runtimes/start b/gcloud/beta/colab/runtimes/start index 1e2861ae2..48b0a7187 100644 --- a/gcloud/beta/colab/runtimes/start +++ b/gcloud/beta/colab/runtimes/start @@ -15,7 +15,7 @@ EXAMPLES POSITIONAL ARGUMENTS Runtime resource - Unique name of the runtime to start. This was - optionally provided by setting --runtime-id in the assign runtime command, + optionally provided by setting --runtime-id in the create runtime command, or was system-generated if unspecified. 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. diff --git a/gcloud/beta/colab/runtimes/upgrade b/gcloud/beta/colab/runtimes/upgrade index 25cfbe36f..5de96dce2 100644 --- a/gcloud/beta/colab/runtimes/upgrade +++ b/gcloud/beta/colab/runtimes/upgrade @@ -15,7 +15,7 @@ EXAMPLES POSITIONAL ARGUMENTS Runtime resource - Unique name of the runtime to upgrade. This was - optionally provided by setting --runtime-id in the assign runtime command, + optionally provided by setting --runtime-id in the create runtime command, or was system-generated if unspecified. 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. diff --git a/gcloud/beta/compute/backend-services/add-backend b/gcloud/beta/compute/backend-services/add-backend index f3c9471aa..29840bb3b 100644 --- a/gcloud/beta/compute/backend-services/add-backend +++ b/gcloud/beta/compute/backend-services/add-backend @@ -14,6 +14,8 @@ SYNOPSIS [--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER] [--description=DESCRIPTION] [--failover] [--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE] + [--custom-metrics=[CUSTOM_METRICS,...] + | --custom-metrics-file=[CUSTOM_METRICS,...]] [--global | --region=REGION] [--max-connections=MAX_CONNECTIONS | --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT @@ -254,6 +256,80 @@ OPTIONAL FLAGS Backends with this preference setting are used up to their capacity limits first, while optimizing overall network latency. + At most one of these can be specified: + + --custom-metrics=[CUSTOM_METRICS,...] + List of custom metrics that are used for CUSTOM_METRICS BalancingMode + and WEIGHTED_ROUND_ROBIN BackendService locality_lb_policy. + + Example: + + $ gcloud beta compute backend-services add-backend \ + --custom-metrics='name=my-signal,maxUtilization=0.8,dryRun=true' + $ gcloud beta compute backend-services add-backend \ + --custom-metrics='name=my-signal,maxUtilization=0.8,dryRun=true'\ + --custom-metrics='name=my-signal2,maxUtilization=0.2' + $ gcloud beta compute backend-services add-backend \ + --custom-metrics='[{"name" : "my-signal", "maxUtilization" : + 0.8, "dryRun" : true}, {"name" : "my-signal2", "maxUtilization" : + 0.1}]' + + Sets custom_metrics value. + + dryRun + Sets dryRun value. + + maxUtilization + Sets maxUtilization value. + + name + Required, Sets name value. + + Shorthand Example: + + --custom-metrics=dryRun=boolean,maxUtilization=float,name=string --custom-metrics=dryRun=boolean,maxUtilization=float,name=string + + JSON Example: + + --custom-metrics='[{"dryRun": boolean, "maxUtilization": float, "name": "string"}]' + + File Example: + + --custom-metrics=path_to_file.(yaml|json) + + --custom-metrics-file=[CUSTOM_METRICS,...] + File path to json file with custom metrics that are used for + CUSTOM_METRICS BalancingMode and WEIGHTED_ROUND_ROBIN BackendService + locality_lb_policy. + + Example: + + $ gcloud beta compute backend-services add-backend \ + --custom-metrics-file='customMetric.json' + + Sets custom_metrics_file value. + + dryRun + Sets dryRun value. + + maxUtilization + Sets maxUtilization value. + + name + Required, Sets name value. + + Shorthand Example: + + --custom-metrics-file=dryRun=boolean,maxUtilization=float,name=string --custom-metrics-file=dryRun=boolean,maxUtilization=float,name=string + + JSON Example: + + --custom-metrics-file='[{"dryRun": boolean, "maxUtilization": float, "name": "string"}]' + + File Example: + + --custom-metrics-file=path_to_file.(yaml|json) + At most one of these can be specified: --global diff --git a/gcloud/beta/compute/backend-services/create b/gcloud/beta/compute/backend-services/create index 4f052e2a7..3e63bebec 100644 --- a/gcloud/beta/compute/backend-services/create +++ b/gcloud/beta/compute/backend-services/create @@ -44,6 +44,8 @@ SYNOPSIS [--timeout=TIMEOUT; default="30s"] [--tracking-mode=TRACKING_MODE] [--cache-key-query-string-blacklist=[QUERY_STRING,...] | --cache-key-query-string-whitelist=QUERY_STRING,[...]] + [--custom-metrics=[CUSTOM_METRICS,...] + | --custom-metrics-file=[CUSTOM_METRICS,...]] [--global | --region=REGION] [--global-health-checks | --health-checks-region=HEALTH_CHECKS_REGION] [GCLOUD_WIDE_FLAG ...] @@ -755,6 +757,72 @@ FLAGS percent encoded and not treated as delimiters. Can only be applied for global resources. + At most one of these can be specified: + + --custom-metrics=[CUSTOM_METRICS,...] + List of custom metrics that are used for WEIGHTED_ROUND_ROBIN + BackendService locality_lb_policy. + + Example: + + $ gcloud beta compute backend-services create \ + --custom-metrics='name=my-signal,dryRun=true' + $ gcloud beta compute backend-services create \ + --custom-metrics='name=my-signal,dryRun=true' \ + --custom-metrics='name=my-signal2' + $ gcloud beta compute backend-services create \ + --custom-metrics='[{"name" : "my-signal", "dryRun" : true}, + {"name" : "my-signal2"}]' + + Sets custom_metrics value. + + dryRun + Sets dryRun value. + + name + Required, Sets name value. + + Shorthand Example: + + --custom-metrics=dryRun=boolean,name=string --custom-metrics=dryRun=boolean,name=string + + JSON Example: + + --custom-metrics='[{"dryRun": boolean, "name": "string"}]' + + File Example: + + --custom-metrics=path_to_file.(yaml|json) + + --custom-metrics-file=[CUSTOM_METRICS,...] + File path to json file with custom metrics that are used for + WEIGHTED_ROUND_ROBIN BackendService locality_lb_policy. + + Example: + + $ gcloud beta compute backend-services create \ + --custom-metrics-file='customMetric.json' + + Sets custom_metrics_file value. + + dryRun + Sets dryRun value. + + name + Required, Sets name value. + + Shorthand Example: + + --custom-metrics-file=dryRun=boolean,name=string --custom-metrics-file=dryRun=boolean,name=string + + JSON Example: + + --custom-metrics-file='[{"dryRun": boolean, "name": "string"}]' + + File Example: + + --custom-metrics-file=path_to_file.(yaml|json) + At most one of these can be specified: --global diff --git a/gcloud/beta/compute/backend-services/update b/gcloud/beta/compute/backend-services/update index 33ebbe857..709c43b3b 100644 --- a/gcloud/beta/compute/backend-services/update +++ b/gcloud/beta/compute/backend-services/update @@ -40,6 +40,8 @@ SYNOPSIS | --no-bypass-cache-on-request-headers] [--cache-key-query-string-blacklist=[QUERY_STRING,...] | --cache-key-query-string-whitelist=QUERY_STRING,[...]] + [--clear-custom-metrics | --custom-metrics=[CUSTOM_METRICS,...] + | --custom-metrics-file=[CUSTOM_METRICS,...]] [--clear-external-managed-migration-state | --external-managed-migration-state=EXTERNAL_MANAGED_MIGRATION_STATE] [--client-ttl=CLIENT_TTL | --no-client-ttl] @@ -596,6 +598,75 @@ FLAGS percent encoded and not treated as delimiters. Can only be applied for global resources. + At most one of these can be specified: + + --clear-custom-metrics + Clears current list of CUSTOM_METRICS. + + --custom-metrics=[CUSTOM_METRICS,...] + List of custom metrics that are used for WEIGHTED_ROUND_ROBIN + BackendService locality_lb_policy. + + Example: + + $ gcloud beta compute backend-services update \ + --custom-metrics='name=my-signal,dryRun=true' + $ gcloud beta compute backend-services update \ + --custom-metrics='name=my-signal,dryRun=true' \ + --custom-metrics='name=my-signal2' + $ gcloud beta compute backend-services update \ + --custom-metrics='[{"name" : "my-signal", "dryRun" : true}, + {"name" : "my-signal2"}]' + + Sets custom_metrics value. + + dryRun + Sets dryRun value. + + name + Required, Sets name value. + + Shorthand Example: + + --custom-metrics=dryRun=boolean,name=string --custom-metrics=dryRun=boolean,name=string + + JSON Example: + + --custom-metrics='[{"dryRun": boolean, "name": "string"}]' + + File Example: + + --custom-metrics=path_to_file.(yaml|json) + + --custom-metrics-file=[CUSTOM_METRICS,...] + File path to json file with custom metrics that are used for + WEIGHTED_ROUND_ROBIN BackendService locality_lb_policy. + + Example: + + $ gcloud beta compute backend-services update \ + --custom-metrics-file='customMetric.json' + + Sets custom_metrics_file value. + + dryRun + Sets dryRun value. + + name + Required, Sets name value. + + Shorthand Example: + + --custom-metrics-file=dryRun=boolean,name=string --custom-metrics-file=dryRun=boolean,name=string + + JSON Example: + + --custom-metrics-file='[{"dryRun": boolean, "name": "string"}]' + + File Example: + + --custom-metrics-file=path_to_file.(yaml|json) + At most one of these can be specified: --clear-external-managed-migration-state diff --git a/gcloud/beta/compute/backend-services/update-backend b/gcloud/beta/compute/backend-services/update-backend index bd2d40d7d..3e7243160 100644 --- a/gcloud/beta/compute/backend-services/update-backend +++ b/gcloud/beta/compute/backend-services/update-backend @@ -12,6 +12,8 @@ SYNOPSIS [--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER] [--description=DESCRIPTION] [--failover] [--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE] + [--clear-custom-metrics | --custom-metrics=[CUSTOM_METRICS,...] + | --custom-metrics-file=[CUSTOM_METRICS,...]] [--global | --region=REGION] [--max-connections=MAX_CONNECTIONS | --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT @@ -223,6 +225,83 @@ OPTIONAL FLAGS Backends with this preference setting are used up to their capacity limits first, while optimizing overall network latency. + At most one of these can be specified: + + --clear-custom-metrics + Clears current list of CUSTOM_METRICS. + + --custom-metrics=[CUSTOM_METRICS,...] + List of custom metrics that are used for CUSTOM_METRICS BalancingMode + and WEIGHTED_ROUND_ROBIN BackendService locality_lb_policy. + + Example: + + $ gcloud beta compute backend-services update-backend \ + --custom-metrics='name=my-signal,maxUtilization=0.8,dryRun=true' + $ gcloud beta compute backend-services update-backend \ + --custom-metrics='name=my-signal,maxUtilization=0.8,dryRun=true'\ + --custom-metrics='name=my-signal2,maxUtilization=0.2' + $ gcloud beta compute backend-services update-backend \ + --custom-metrics='[{"name" : "my-signal", "maxUtilization" : + 0.8, "dryRun" : true}, {"name" : "my-signal2", "maxUtilization" : + 0.1}]' + + Sets custom_metrics value. + + dryRun + Sets dryRun value. + + maxUtilization + Sets maxUtilization value. + + name + Required, Sets name value. + + Shorthand Example: + + --custom-metrics=dryRun=boolean,maxUtilization=float,name=string --custom-metrics=dryRun=boolean,maxUtilization=float,name=string + + JSON Example: + + --custom-metrics='[{"dryRun": boolean, "maxUtilization": float, "name": "string"}]' + + File Example: + + --custom-metrics=path_to_file.(yaml|json) + + --custom-metrics-file=[CUSTOM_METRICS,...] + File path to json file with custom metrics that are used for + CUSTOM_METRICS BalancingMode and WEIGHTED_ROUND_ROBIN BackendService + locality_lb_policy. + + Example: + + $ gcloud beta compute backend-services update-backend \ + --custom-metrics-file='customMetric.json' + + Sets custom_metrics_file value. + + dryRun + Sets dryRun value. + + maxUtilization + Sets maxUtilization value. + + name + Required, Sets name value. + + Shorthand Example: + + --custom-metrics-file=dryRun=boolean,maxUtilization=float,name=string --custom-metrics-file=dryRun=boolean,maxUtilization=float,name=string + + JSON Example: + + --custom-metrics-file='[{"dryRun": boolean, "maxUtilization": float, "name": "string"}]' + + File Example: + + --custom-metrics-file=path_to_file.(yaml|json) + At most one of these can be specified: --global diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index ce1de8d92..f253c05d5 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -752,6 +752,10 @@ FLAGS available range with the specified netmask and allocate it to this network interface. + network-attachment + Specifies the network attachment that this interface should connect + to. Mutually exclusive with --network and --subnet flags. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/beta/compute/instance-templates/create-with-container b/gcloud/beta/compute/instance-templates/create-with-container index 3ba57962c..612139a30 100644 --- a/gcloud/beta/compute/instance-templates/create-with-container +++ b/gcloud/beta/compute/instance-templates/create-with-container @@ -662,6 +662,10 @@ FLAGS available range with the specified netmask and allocate it to this network interface. + network-attachment + Specifies the network attachment that this interface should connect + to. Mutually exclusive with --network and --subnet flags. + --network-tier=NETWORK_TIER Specifies the network tier that will be used to configure the instance. NETWORK_TIER must be one of: PREMIUM, STANDARD. The default value is diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index b633b919c..cd3c524f8 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -819,6 +819,10 @@ FLAGS available range with the specified netmask and allocate it to this network interface. + network-attachment + Specifies the network attachment that this interface should connect + to. Mutually exclusive with --network and --subnet flags. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index d73940974..a249ef6c0 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -752,6 +752,10 @@ FLAGS available range with the specified netmask and allocate it to this network interface. + network-attachment + Specifies the network attachment that this interface should connect + to. Mutually exclusive with --network and --subnet flags. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/beta/compute/network-endpoint-groups/update b/gcloud/beta/compute/network-endpoint-groups/update index 8c401beb7..4ec779d23 100644 --- a/gcloud/beta/compute/network-endpoint-groups/update +++ b/gcloud/beta/compute/network-endpoint-groups/update @@ -5,9 +5,9 @@ NAME SYNOPSIS gcloud beta compute network-endpoint-groups update NAME (--add-endpoint=[client-destination-port=CLIENT-DESTINATION-PORT], - [fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT] + [fqdn=FQDN],[instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT] | --remove-endpoint=[client-destination-port=CLIENT-DESTINATION-PORT], - [fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT]) + [fqdn=FQDN],[instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT]) [--global | --region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -38,7 +38,7 @@ REQUIRED FLAGS Exactly one of these must be specified: - --add-endpoint=[client-destination-port=CLIENT-DESTINATION-PORT],[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT] + --add-endpoint=[client-destination-port=CLIENT-DESTINATION-PORT],[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT] The network endpoint to add to the network endpoint group. Keys used depend on the endpoint type of the NEG. @@ -59,6 +59,10 @@ REQUIRED FLAGS the network that the network endpoint group belongs to is used. + *ipv6* - Optional IPv6 address of the network endpoint. The IPv6 + address must belong to a VM in compute engine (either the internal + or external IPv6 address). + *port* - Required endpoint port unless NEG default port is set. *client-destination-port* - Required endpoint client destination port only for the port @@ -111,7 +115,7 @@ REQUIRED FLAGS IP address must be the VM's network interface address. If not specified, the primary NIC address is used. - --remove-endpoint=[client-destination-port=CLIENT-DESTINATION-PORT],[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT] + --remove-endpoint=[client-destination-port=CLIENT-DESTINATION-PORT],[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT] The network endpoint to detach from the network endpoint group. Keys used depend on the endpoint type of the NEG. @@ -124,6 +128,9 @@ REQUIRED FLAGS *ip* - Optional IPv4 address of the network endpoint to detach. If specified port must be provided as well. + *ipv6* - Optional IPv6 address of the network endpoint to detach. + If specified port must be provided as well. + *port* - Optional port of the network endpoint to detach. *client-destination-port* - Optional client destination port, only for port mapping NEGs. diff --git a/gcloud/beta/compute/url-maps/invalidate-cdn-cache b/gcloud/beta/compute/url-maps/invalidate-cdn-cache index 9cd58745a..062da2528 100644 --- a/gcloud/beta/compute/url-maps/invalidate-cdn-cache +++ b/gcloud/beta/compute/url-maps/invalidate-cdn-cache @@ -4,8 +4,7 @@ NAME SYNOPSIS gcloud beta compute url-maps invalidate-cdn-cache URLMAP --path=PATH - [--async] [--host=HOST] [--global | --region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--async] [--global] [--host=HOST] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute url-maps invalidate-cdn-cache requests that @@ -45,35 +44,13 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --global + (Default) The URL map is global. Regional URL maps are not supported. + --host=HOST If set, this invalidation will apply only to requests to the specified host. - At most one of these can be specified: - - --global - If set, the URL map is global. - - --region=REGION - Region of the URL map to operate on. If not specified, you might be - prompted to select a region (interactive mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/region property: - - $ gcloud config set compute/region REGION - - A list of regions can be fetched by running: - - $ gcloud compute regions list - - To unset the property, run: - - $ gcloud config unset compute/region - - Alternatively, the region can be stored in the environment variable - CLOUDSDK_COMPUTE_REGION. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/url-maps/list-cdn-cache-invalidations b/gcloud/beta/compute/url-maps/list-cdn-cache-invalidations index 7e4295e36..a91b60096 100644 --- a/gcloud/beta/compute/url-maps/list-cdn-cache-invalidations +++ b/gcloud/beta/compute/url-maps/list-cdn-cache-invalidations @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta compute url-maps list-cdn-cache-invalidations URL_MAP - [--limit=LIMIT] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] + [--global] [--limit=LIMIT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) List Cloud CDN cache invalidations for a URL map. A cache @@ -16,34 +16,12 @@ POSITIONAL ARGUMENTS Name of the URL map to describe. FLAGS + --global + (Default) The URL map is global. Regional URL maps are not supported. + --limit=LIMIT The maximum number of invalidations to list. - At most one of these can be specified: - - --global - If set, the URL map is global. - - --region=REGION - Region of the URL map to describe. If not specified, you might be - prompted to select a region (interactive mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/region property: - - $ gcloud config set compute/region REGION - - A list of regions can be fetched by running: - - $ gcloud compute regions list - - To unset the property, run: - - $ gcloud config unset compute/region - - Alternatively, the region can be stored in the environment variable - CLOUDSDK_COMPUTE_REGION. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 58f482567..dbdd402ae 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -10,6 +10,7 @@ SYNOPSIS gpu-sharing-strategy=GPU_SHARING_STRATEGY, max-shared-clients-per-gpu=MAX_SHARED_CLIENTS_PER_GPU],...]] [--addons=[ADDON,...]] [--allow-route-overlap] [--async] + [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] [--autoprovisioning-enable-insecure-kubelet-readonly-port] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] @@ -205,7 +206,7 @@ FLAGS ADDON must be one of: HttpLoadBalancing, HorizontalPodAutoscaling, KubernetesDashboard, NetworkPolicy, NodeLocalDNS, ConfigConnector, GcePersistentDiskCsiDriver, GcpFilestoreCsiDriver, BackupRestore, - GcsFuseCsiDriver, RayOperator, Istio, CloudRun. + GcsFuseCsiDriver, ParallelstoreCsiDriver, RayOperator, Istio, CloudRun. --allow-route-overlap Allows the provided cluster CIDRs to overlap with existing routes that @@ -223,6 +224,12 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --auto-monitoring-scope=AUTO_MONITORING_SCOPE + Enables Auto-Monitoring for a specific scope within the cluster. ALL: + Enables Auto-Monitoring for all supported workloads within the cluster. + NONE: Disables Auto-Monitoring. AUTO_MONITORING_SCOPE must be one of: + ALL, NONE. + --autoprovisioning-enable-insecure-kubelet-readonly-port Enables the Kubelet's insecure read only port for Autoprovisioned Node Pools. @@ -1294,6 +1301,11 @@ FLAGS net.ipv4.tcp_rmem Any positive integer tuple net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + kernel.shmmni Must be [4096, 32768] + kernel.shmmax Must be [0, + 18446744073692774399] + kernel.shmall Must be [0, + 18446744073692774399] List of supported hugepage size in 'hugepageConfig'. diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 0df3f937e..d8ec7cb9d 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud beta container clusters create-auto NAME [--async] + [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] [--autoprovisioning-enable-insecure-kubelet-readonly-port] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] @@ -68,6 +69,12 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --auto-monitoring-scope=AUTO_MONITORING_SCOPE + Enables Auto-Monitoring for a specific scope within the cluster. ALL: + Enables Auto-Monitoring for all supported workloads within the cluster. + NONE: Disables Auto-Monitoring. AUTO_MONITORING_SCOPE must be one of: + ALL, NONE. + --autoprovisioning-enable-insecure-kubelet-readonly-port Enables the Kubelet's insecure read only port for Autoprovisioned Node Pools. diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index 828f2eec6..1806da486 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -48,7 +48,8 @@ SYNOPSIS | --additional-pod-ipv4-ranges=NAME,[NAME,...] --remove-additional-pod-ipv4-ranges=NAME,[NAME,...] | --additional-zones=[ZONE,...] | --node-locations=ZONE,[ZONE,...] - | --logging=[COMPONENT,...] + | --auto-monitoring-scope=AUTO_MONITORING_SCOPE + --logging=[COMPONENT,...] --monitoring=[COMPONENT,...] --disable-managed-prometheus | --enable-managed-prometheus | --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] @@ -831,6 +832,12 @@ REQUIRED FLAGS --location us-central1-a \ --node-locations us-central1-a,us-central1-b + --auto-monitoring-scope=AUTO_MONITORING_SCOPE + Enables Auto-Monitoring for a specific scope within the cluster. ALL: + Enables Auto-Monitoring for all supported workloads within the + cluster. NONE: Disables Auto-Monitoring. AUTO_MONITORING_SCOPE must + be one of: ALL, NONE. + --logging=[COMPONENT,...] Set the components that have logging enabled. Valid component values are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, diff --git a/gcloud/beta/container/fleet/memberships/register b/gcloud/beta/container/fleet/memberships/register index 4ebf5fe9a..4eceec27f 100644 --- a/gcloud/beta/container/fleet/memberships/register +++ b/gcloud/beta/container/fleet/memberships/register @@ -52,7 +52,8 @@ DESCRIPTION Rerunning this command against the same cluster with the same MEMBERSHIP_NAME and target fleet is successful, and will upgrade the Connect agent if it is supposed to be installed and a newer version is - avaible. + available. Rerunning with --enable-workload-identity ensures that Workload + Identity is enabled on the cluster. EXAMPLES Register a non-GKE cluster referenced from a specific kubeconfig file, and diff --git a/gcloud/beta/container/hub/memberships/register b/gcloud/beta/container/hub/memberships/register index 7908d61e4..28bf43663 100644 --- a/gcloud/beta/container/hub/memberships/register +++ b/gcloud/beta/container/hub/memberships/register @@ -52,7 +52,8 @@ DESCRIPTION Rerunning this command against the same cluster with the same MEMBERSHIP_NAME and target fleet is successful, and will upgrade the Connect agent if it is supposed to be installed and a newer version is - avaible. + available. Rerunning with --enable-workload-identity ensures that Workload + Identity is enabled on the cluster. EXAMPLES Register a non-GKE cluster referenced from a specific kubeconfig file, and diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 1f6655d48..718eb4b17 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -708,6 +708,11 @@ FLAGS net.ipv4.tcp_rmem Any positive integer tuple net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + kernel.shmmni Must be [4096, 32768] + kernel.shmmax Must be [0, + 18446744073692774399] + kernel.shmall Must be [0, + 18446744073692774399] List of supported hugepage size in 'hugepageConfig'. diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index 8a17dd780..2e13feea0 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -306,6 +306,11 @@ REQUIRED FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + kernel.shmmni Must be [4096, 32768] + kernel.shmmax Must be [0, + 18446744073692774399] + kernel.shmall Must be [0, + 18446744073692774399] List of supported hugepage size in 'hugepageConfig'. diff --git a/gcloud/beta/dataproc/clusters/create b/gcloud/beta/dataproc/clusters/create index b80d726e1..3d8627f32 100644 --- a/gcloud/beta/dataproc/clusters/create +++ b/gcloud/beta/dataproc/clusters/create @@ -17,6 +17,8 @@ SYNOPSIS [--initialization-actions=CLOUD_STORAGE_URI,[...]] [--labels=[KEY=VALUE,...]] [--master-accelerator=[type=TYPE,[count=COUNT],...]] + [--master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS] + [--master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--master-boot-disk-size=MASTER_BOOT_DISK_SIZE] [--master-boot-disk-type=MASTER_BOOT_DISK_TYPE] [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] @@ -43,6 +45,8 @@ SYNOPSIS [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] + [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] [--worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE] @@ -218,6 +222,22 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the disk. This sets the limit for disk I/O operations per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + + --master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) to + provision for the disk. This sets the limit for throughput in MiB per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + --master-boot-disk-size=MASTER_BOOT_DISK_SIZE The size of the boot 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 @@ -414,6 +434,22 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the disk. This sets the limit for disk I/O operations per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + + --worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) to + provision for the disk. This sets the limit for throughput in MiB per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + --worker-boot-disk-size=WORKER_BOOT_DISK_SIZE The size of the boot 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 diff --git a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster index bdeed39ab..b079e4762 100644 --- a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster @@ -11,6 +11,8 @@ SYNOPSIS [--initialization-actions=CLOUD_STORAGE_URI,[...]] [--labels=[KEY=VALUE,...]] [--master-accelerator=[type=TYPE,[count=COUNT],...]] + [--master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS] + [--master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--master-boot-disk-size=MASTER_BOOT_DISK_SIZE] [--master-boot-disk-type=MASTER_BOOT_DISK_TYPE] [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] @@ -36,6 +38,8 @@ SYNOPSIS [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] + [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] [--worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE] @@ -158,6 +162,22 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the disk. This sets the limit for disk I/O operations per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + + --master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) to + provision for the disk. This sets the limit for throughput in MiB per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + --master-boot-disk-size=MASTER_BOOT_DISK_SIZE The size of the boot 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 @@ -346,6 +366,22 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the disk. This sets the limit for disk I/O operations per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + + --worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) to + provision for the disk. This sets the limit for throughput in MiB per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + --worker-boot-disk-size=WORKER_BOOT_DISK_SIZE The size of the boot 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 diff --git a/gcloud/beta/eventarc/enrollments/create b/gcloud/beta/eventarc/enrollments/create new file mode 100644 index 000000000..547f69a7a --- /dev/null +++ b/gcloud/beta/eventarc/enrollments/create @@ -0,0 +1,119 @@ +NAME + gcloud beta eventarc enrollments create - create an Eventarc enrollment + +SYNOPSIS + gcloud beta eventarc enrollments create (ENROLLMENT : --location=LOCATION) + --cel-match=CEL_MATCH --destination-pipeline=DESTINATION_PIPELINE + (--message-bus=MESSAGE_BUS : --message-bus-project=MESSAGE_BUS_PROJECT) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create an Eventarc enrollment. + +EXAMPLES + To create a new enrollment my-enrollment in location us-central1 for + message-bus my-message-bus with cel matching expression message.type == + "google.cloud.pubsub.topic.v1.messagePublished" and destination pipeline + my-pipeline, run: + + $ gcloud beta eventarc enrollments create my-enrollment \ + --location=us-central1 --message-bus=my-message-bus \ + --cel-match="message.type == \ + 'google.cloud.pubsub.topic.v1.messagePublished'" \ + --destination-pipeline=my-pipeline + +POSITIONAL ARGUMENTS + Enrollment resource - The enrollment 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 enrollment 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. + + ENROLLMENT + ID of the enrollment or fully qualified identifier for the + enrollment. + + To set the enrollment attribute: + ▸ provide the argument enrollment on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc enrollment, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument enrollment on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +REQUIRED FLAGS + --cel-match=CEL_MATCH + The cel match expression for the enrollment. + + --destination-pipeline=DESTINATION_PIPELINE + ID of the destination pipeline or fully qualified identifier for the + destination pipeline. + + To set the pipeline attribute: + ◆ provide the argument --destination-pipeline on the command line. + + Message bus resource - The message bus to which the enrollment attaches. + 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 location attribute: + ◆ provide the argument --message-bus on the command line with a fully + specified name; + ◆ provide the argument --location on the command line; + ◆ set the property eventarc/location. + + This must be specified. + + --message-bus=MESSAGE_BUS + ID of the message bus or fully qualified identifier for the message + bus. + + To set the message-bus attribute: + ▸ provide the argument --message-bus on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --message-bus-project=MESSAGE_BUS_PROJECT + Project ID of the Google Cloud project for the message bus. + + To set the project attribute: + ▸ provide the argument --message-bus on the command line with a + fully specified name; + ▸ provide the argument --message-bus-project on the command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/enrollments/delete b/gcloud/beta/eventarc/enrollments/delete new file mode 100644 index 000000000..930817aa2 --- /dev/null +++ b/gcloud/beta/eventarc/enrollments/delete @@ -0,0 +1,67 @@ +NAME + gcloud beta eventarc enrollments delete - delete an Eventarc enrollment + +SYNOPSIS + gcloud beta eventarc enrollments delete (ENROLLMENT : --location=LOCATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete an Eventarc enrollment. + +EXAMPLES + To delete the enrollment my-enrollment in location us-central1, run: + + $ gcloud beta eventarc enrollments delete my-enrollment \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Enrollment resource - Enrollment 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 enrollment 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. + + ENROLLMENT + ID of the enrollment or fully qualified identifier for the + enrollment. + + To set the enrollment attribute: + ▸ provide the argument enrollment on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc enrollment, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument enrollment on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/enrollments/describe b/gcloud/beta/eventarc/enrollments/describe new file mode 100644 index 000000000..01ff11127 --- /dev/null +++ b/gcloud/beta/eventarc/enrollments/describe @@ -0,0 +1,62 @@ +NAME + gcloud beta eventarc enrollments describe - describe an Eventarc enrollment + +SYNOPSIS + gcloud beta eventarc enrollments describe + (ENROLLMENT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an Eventarc enrollment. + +EXAMPLES + To describe the enrollment my-enrollment in location us-central1, run: + + $ gcloud beta eventarc enrollments describe my-enrollment \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Enrollment resource - Enrollment 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 enrollment 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. + + ENROLLMENT + ID of the enrollment or fully qualified identifier for the + enrollment. + + To set the enrollment attribute: + ▸ provide the argument enrollment on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc enrollment, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument enrollment on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/enrollments/help b/gcloud/beta/eventarc/enrollments/help new file mode 100644 index 000000000..27005873e --- /dev/null +++ b/gcloud/beta/eventarc/enrollments/help @@ -0,0 +1,35 @@ +NAME + gcloud beta eventarc enrollments - manage Eventarc enrollments + +SYNOPSIS + gcloud beta eventarc enrollments COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Eventarc enrollments. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create an Eventarc enrollment. + + delete + (BETA) Delete an Eventarc enrollment. + + describe + (BETA) Describe an Eventarc enrollment. + + list + (BETA) List Eventarc enrollments. + + update + (BETA) Update an Eventarc enrollment. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/enrollments/list b/gcloud/beta/eventarc/enrollments/list new file mode 100644 index 000000000..c4fca6880 --- /dev/null +++ b/gcloud/beta/eventarc/enrollments/list @@ -0,0 +1,90 @@ +NAME + gcloud beta eventarc enrollments list - list Eventarc enrollments + +SYNOPSIS + gcloud beta eventarc enrollments list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Eventarc enrollments. + +EXAMPLES + To list all enrollments in location us-central1, run: + + $ gcloud beta eventarc enrollments list --location=us-central1 + + To list all enrollments in all locations, run: + + $ gcloud beta eventarc enrollments list --location=- + + or + + $ gcloud beta eventarc enrollments list + +FLAGS + Location resource - The location for which to list enrollments. This + should be one of the supported regions. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property eventarc/location with a fully specified name; + ◆ use '-' location to aggregate results for all Eventarc locations with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location; + ▸ use '-' location to aggregate results for all Eventarc locations. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/enrollments/update b/gcloud/beta/eventarc/enrollments/update new file mode 100644 index 000000000..fb42a6b69 --- /dev/null +++ b/gcloud/beta/eventarc/enrollments/update @@ -0,0 +1,80 @@ +NAME + gcloud beta eventarc enrollments update - update an Eventarc enrollment + +SYNOPSIS + gcloud beta eventarc enrollments update (ENROLLMENT : --location=LOCATION) + [--async] [--cel-match=CEL_MATCH] + [--destination-pipeline=DESTINATION_PIPELINE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an Eventarc enrollment. + +EXAMPLES + To update the enrollment my-enrollment with a new CEL expression + message.type == 'google.cloud.pubsub.topic.v1.messagePublished', run: + + $ gcloud beta eventarc enrollments update my-enrollment \ + --location=us-central1 \ + --cel-match="message.type == \ + 'google.cloud.pubsub.topic.v1.messagePublished'" + +POSITIONAL ARGUMENTS + Enrollment resource - The enrollment to update. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument enrollment 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. + + ENROLLMENT + ID of the enrollment or fully qualified identifier for the + enrollment. + + To set the enrollment attribute: + ▸ provide the argument enrollment on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc enrollment, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument enrollment on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --cel-match=CEL_MATCH + The cel match expression for the enrollment. + + --destination-pipeline=DESTINATION_PIPELINE + ID of the pipeline or fully qualified identifier for the pipeline. + + To set the pipeline attribute: + ◆ provide the argument --destination-pipeline on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/google-api-sources/create b/gcloud/beta/eventarc/google-api-sources/create new file mode 100644 index 000000000..583ead195 --- /dev/null +++ b/gcloud/beta/eventarc/google-api-sources/create @@ -0,0 +1,120 @@ +NAME + gcloud beta eventarc google-api-sources create - create an Eventarc Google + API source + +SYNOPSIS + gcloud beta eventarc google-api-sources create + (GOOGLE_API_SOURCE : --location=LOCATION) + (--destination-message-bus=DESTINATION_MESSAGE_BUS + : --destination-message-bus-project=DESTINATION_MESSAGE_BUS_PROJECT) + [--async] [--crypto-key=CRYPTO_KEY] [--logging-config=LOGGING_CONFIG] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create an Eventarc Google API source. + +EXAMPLES + To create a new Google API source my-google-api-source in location + us-central1 with a destination message bus my-message-bus, run: + + $ gcloud beta eventarc google-api-sources create \ + my-google-api-source --location=us-central1 \ + --destination-message-bus=my-message-bus + +POSITIONAL ARGUMENTS + Google API source resource - The Google API source 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 google_api_source 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. + + GOOGLE_API_SOURCE + ID of the Google API source or fully qualified identifier for the + Google API source. + + To set the google-api-source attribute: + ▸ provide the argument google_api_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc Google API source, which should be one + of the supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument google_api_source on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +REQUIRED FLAGS + Message bus resource - The destination message bus of the Google API + source. 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 location attribute: + ◆ provide the argument --destination-message-bus on the command line + with a fully specified name; + ◆ provide the argument --location on the command line; + ◆ set the property eventarc/location. + + This must be specified. + + --destination-message-bus=DESTINATION_MESSAGE_BUS + ID of the message bus or fully qualified identifier for the message + bus. + + To set the message-bus attribute: + ▸ provide the argument --destination-message-bus on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --destination-message-bus-project=DESTINATION_MESSAGE_BUS_PROJECT + Project ID of the Google Cloud project for the message bus. + + To set the project attribute: + ▸ provide the argument --destination-message-bus on the command + line with a fully specified name; + ▸ provide the argument --destination-message-bus-project on the + command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --crypto-key=CRYPTO_KEY + Fully qualified name of the crypto key to use for customer-managed + encryption. If this is unspecified, Google-managed keys will be used + for encryption. + + --logging-config=LOGGING_CONFIG + The logging config for the Google API source. LOGGING_CONFIG must be + one of: NONE, DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, + EMERGENCY. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/google-api-sources/delete b/gcloud/beta/eventarc/google-api-sources/delete new file mode 100644 index 000000000..42536322f --- /dev/null +++ b/gcloud/beta/eventarc/google-api-sources/delete @@ -0,0 +1,70 @@ +NAME + gcloud beta eventarc google-api-sources delete - delete an Eventarc Google + API source + +SYNOPSIS + gcloud beta eventarc google-api-sources delete + (GOOGLE_API_SOURCE : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete an Eventarc Google API source. + +EXAMPLES + To delete the Google API source my-google-api-source in location + us-central1, run: + + $ gcloud beta eventarc google-api-sources delete \ + my-google-api-source --location=us-central1 + +POSITIONAL ARGUMENTS + Google API source resource - Google API source 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 google_api_source 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. + + GOOGLE_API_SOURCE + ID of the Google API source or fully qualified identifier for the + Google API source. + + To set the google-api-source attribute: + ▸ provide the argument google_api_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc Google API source, which should be one + of the supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument google_api_source on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/google-api-sources/describe b/gcloud/beta/eventarc/google-api-sources/describe new file mode 100644 index 000000000..aef57600a --- /dev/null +++ b/gcloud/beta/eventarc/google-api-sources/describe @@ -0,0 +1,64 @@ +NAME + gcloud beta eventarc google-api-sources describe - describe an Eventarc + Google API source + +SYNOPSIS + gcloud beta eventarc google-api-sources describe + (GOOGLE_API_SOURCE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an Eventarc Google API source. + +EXAMPLES + To describe the google API source my-google-api-source in location + us-central1, run: + + $ gcloud beta eventarc google-api-sources describe \ + my-google-api-source --location=us-central1 + +POSITIONAL ARGUMENTS + Google API source resource - Google API source 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 google_api_source 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. + + GOOGLE_API_SOURCE + ID of the Google API source or fully qualified identifier for the + Google API source. + + To set the google-api-source attribute: + ▸ provide the argument google_api_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc Google API source, which should be one + of the supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument google_api_source on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/google-api-sources/help b/gcloud/beta/eventarc/google-api-sources/help new file mode 100644 index 000000000..33f09f175 --- /dev/null +++ b/gcloud/beta/eventarc/google-api-sources/help @@ -0,0 +1,36 @@ +NAME + gcloud beta eventarc google-api-sources - manage Eventarc Google API + sources + +SYNOPSIS + gcloud beta eventarc google-api-sources COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Eventarc Google API sources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create an Eventarc Google API source. + + delete + (BETA) Delete an Eventarc Google API source. + + describe + (BETA) Describe an Eventarc Google API source. + + list + (BETA) List Eventarc Google API sources. + + update + (BETA) Update an Eventarc Google API source. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/google-api-sources/list b/gcloud/beta/eventarc/google-api-sources/list new file mode 100644 index 000000000..f677bf109 --- /dev/null +++ b/gcloud/beta/eventarc/google-api-sources/list @@ -0,0 +1,91 @@ +NAME + gcloud beta eventarc google-api-sources list - list Eventarc Google API + sources + +SYNOPSIS + gcloud beta eventarc google-api-sources list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Eventarc Google API sources. + +EXAMPLES + To list all Google API sources in location us-central1, run: + + $ gcloud beta eventarc google-api-sources list --location=us-central1 + + To list all Google API sources in all locations, run: + + $ gcloud beta eventarc google-api-sources list --location=- + + or + + $ gcloud beta eventarc google-api-sources list + +FLAGS + Location resource - The location for which to list Google API sources. + This should be one of the supported regions. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property eventarc/location with a fully specified name; + ◆ use '-' location to aggregate results for all Eventarc locations with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location; + ▸ use '-' location to aggregate results for all Eventarc locations. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/google-api-sources/update b/gcloud/beta/eventarc/google-api-sources/update new file mode 100644 index 000000000..3aa98d881 --- /dev/null +++ b/gcloud/beta/eventarc/google-api-sources/update @@ -0,0 +1,139 @@ +NAME + gcloud beta eventarc google-api-sources update - update an Eventarc Google + API source + +SYNOPSIS + gcloud beta eventarc google-api-sources update + (GOOGLE_API_SOURCE : --location=LOCATION) [--async] + [--logging-config=LOGGING_CONFIG] + [--clear-crypto-key | --crypto-key=CRYPTO_KEY] + [--destination-message-bus=DESTINATION_MESSAGE_BUS + : --destination-message-bus-project=DESTINATION_MESSAGE_BUS_PROJECT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an Eventarc Google API source. + +EXAMPLES + To update the Google API source my-google-api-source in location + us-central1 with destination message bus my-message-bus, run: + + $ gcloud beta eventarc google-api-sources update \ + my-google-api-source --location=us-central1 \ + --destination-message-bus=my-message-bus + + To update the Google API source my-google-api-source in location + us-central1 with INFO level logging, run: + + $ gcloud beta eventarc google-api-sources update \ + my-google-api-source --location=us-central1 \ + --logging-config=INFO + + To update the Google API source my-google-api-source in location + us-central1 with a Cloud KMS CryptoKey, run: + + $ gcloud beta eventarc google-api-sources update \ + my-google-api-source --location=us-central1 \ + --crypto-key=projects/PROJECT_ID/locations/KMS_LOCATION/\ + keyRings/KEYRING/cryptoKeys/KEY + +POSITIONAL ARGUMENTS + Google API source resource - The Google API source to update. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument google_api_source 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. + + GOOGLE_API_SOURCE + ID of the Google API source or fully qualified identifier for the + Google API source. + + To set the google-api-source attribute: + ▸ provide the argument google_api_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc Google API source, which should be one + of the supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument google_api_source on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --logging-config=LOGGING_CONFIG + The logging config of the Google API source. LOGGING_CONFIG must be one + of: NONE, DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, + EMERGENCY. + + At most one of these can be specified: + + --clear-crypto-key + Remove the previously configured crypto key. The channel will + continue to be encrypted using Google-managed keys. + + --crypto-key=CRYPTO_KEY + Fully qualified name of the crypto key to use for customer-managed + encryption. If this is unspecified, Google-managed keys will be used + for encryption. + + Message bus resource - The destination message bus of the Google API + source. 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 location attribute: + ◆ provide the argument --destination-message-bus on the command line + with a fully specified name; + ◆ provide the argument --location on the command line; + ◆ set the property eventarc/location. + + --destination-message-bus=DESTINATION_MESSAGE_BUS + ID of the message bus or fully qualified identifier for the message + bus. + + To set the message-bus attribute: + ▸ provide the argument --destination-message-bus on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --destination-message-bus-project=DESTINATION_MESSAGE_BUS_PROJECT + Project ID of the Google Cloud project for the message bus. + + To set the project attribute: + ▸ provide the argument --destination-message-bus on the command + line with a fully specified name; + ▸ provide the argument --destination-message-bus-project on the + command line; + ▸ provide the argument --project on the command line; + ▸ set the 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. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/help b/gcloud/beta/eventarc/help index 0a22918c2..04a4f2f0b 100644 --- a/gcloud/beta/eventarc/help +++ b/gcloud/beta/eventarc/help @@ -12,6 +12,21 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + enrollments + (BETA) Manage Eventarc enrollments. + + google-api-sources + (BETA) Manage Eventarc Google API sources. + + message-buses + (BETA) Manage Eventarc message buses. + + pipelines + (BETA) Manage Eventarc pipelines. + NOTES This command is currently in beta and might change without notice. This variant is also available: diff --git a/gcloud/beta/eventarc/message-buses/create b/gcloud/beta/eventarc/message-buses/create new file mode 100644 index 000000000..67d31f465 --- /dev/null +++ b/gcloud/beta/eventarc/message-buses/create @@ -0,0 +1,77 @@ +NAME + gcloud beta eventarc message-buses create - create an Eventarc message bus + +SYNOPSIS + gcloud beta eventarc message-buses create + (MESSAGE_BUS : --location=LOCATION) [--async] [--crypto-key=CRYPTO_KEY] + [--logging-config=LOGGING_CONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create an Eventarc message bus. + +EXAMPLES + To create a new message bus my-message-bus in location us-central1, run: + + $ gcloud beta eventarc message-buses create my-message-bus \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Message bus resource - The message bus 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 message_bus 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. + + MESSAGE_BUS + ID of the message bus or fully qualified identifier for the message + bus. + + To set the message-bus attribute: + ▸ provide the argument message_bus on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc message bus, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument message_bus on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --crypto-key=CRYPTO_KEY + Fully qualified name of the crypto key to use for customer-managed + encryption. If this is unspecified, Google-managed keys will be used + for encryption. + + --logging-config=LOGGING_CONFIG + The logging config of the message bus. LOGGING_CONFIG must be one of: + NONE, DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/message-buses/delete b/gcloud/beta/eventarc/message-buses/delete new file mode 100644 index 000000000..621210b7f --- /dev/null +++ b/gcloud/beta/eventarc/message-buses/delete @@ -0,0 +1,67 @@ +NAME + gcloud beta eventarc message-buses delete - delete an Eventarc message bus + +SYNOPSIS + gcloud beta eventarc message-buses delete + (MESSAGE_BUS : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete an Eventarc message bus. + +EXAMPLES + To delete the message bus my-message-bus in location us-central1, run: + + $ gcloud beta eventarc message-buses delete my-message-bus \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Message bus resource - Message bus 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 message_bus 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. + + MESSAGE_BUS + ID of the message bus or fully qualified identifier for the message + bus. + + To set the message-bus attribute: + ▸ provide the argument message_bus on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc message bus, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument message_bus on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/message-buses/describe b/gcloud/beta/eventarc/message-buses/describe new file mode 100644 index 000000000..10387aaf2 --- /dev/null +++ b/gcloud/beta/eventarc/message-buses/describe @@ -0,0 +1,63 @@ +NAME + gcloud beta eventarc message-buses describe - describe an Eventarc message + bus + +SYNOPSIS + gcloud beta eventarc message-buses describe + (MESSAGE_BUS : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an Eventarc message bus. + +EXAMPLES + To describe the message bus my-message-bus in location us-central1, run: + + $ gcloud beta eventarc message-buses describe my-message-bus \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Message bus resource - Message bus 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 message_bus 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. + + MESSAGE_BUS + ID of the message bus or fully qualified identifier for the message + bus. + + To set the message-bus attribute: + ▸ provide the argument message_bus on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc message bus, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument message_bus on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/message-buses/help b/gcloud/beta/eventarc/message-buses/help new file mode 100644 index 000000000..96df4b7e6 --- /dev/null +++ b/gcloud/beta/eventarc/message-buses/help @@ -0,0 +1,41 @@ +NAME + gcloud beta eventarc message-buses - manage Eventarc message buses + +SYNOPSIS + gcloud beta eventarc message-buses COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Eventarc message buses. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create an Eventarc message bus. + + delete + (BETA) Delete an Eventarc message bus. + + describe + (BETA) Describe an Eventarc message bus. + + list + (BETA) List Eventarc message buses. + + list-enrollments + (BETA) List Eventarc enrollments attached to an Eventarc message bus. + + publish + (BETA) Publish to an Eventarc message bus. + + update + (BETA) Update an Eventarc message bus. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/message-buses/list b/gcloud/beta/eventarc/message-buses/list new file mode 100644 index 000000000..6357af00e --- /dev/null +++ b/gcloud/beta/eventarc/message-buses/list @@ -0,0 +1,90 @@ +NAME + gcloud beta eventarc message-buses list - list Eventarc message buses + +SYNOPSIS + gcloud beta eventarc message-buses list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Eventarc message buses. + +EXAMPLES + To list all message buses in location us-central1, run: + + $ gcloud beta eventarc message-buses list --location=us-central1 + + To list all message buses in all locations, run: + + $ gcloud beta eventarc message-buses list --location=- + + or + + $ gcloud beta eventarc message-buses list + +FLAGS + Location resource - The location for which to list message buses. This + should be one of the supported regions. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property eventarc/location with a fully specified name; + ◆ use '-' location to aggregate results for all Eventarc locations with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location; + ▸ use '-' location to aggregate results for all Eventarc locations. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/message-buses/list-enrollments b/gcloud/beta/eventarc/message-buses/list-enrollments new file mode 100644 index 000000000..67e8832da --- /dev/null +++ b/gcloud/beta/eventarc/message-buses/list-enrollments @@ -0,0 +1,97 @@ +NAME + gcloud beta eventarc message-buses list-enrollments - list Eventarc + enrollments attached to an Eventarc message bus + +SYNOPSIS + gcloud beta eventarc message-buses list-enrollments + (MESSAGE_BUS : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Eventarc enrollments attached to an Eventarc message bus. + +EXAMPLES + To list all enrollments in message-bus my-message-bus in us-central1, run: + + $ gcloud beta eventarc message-buses list-enrollments \ + my-message-bus --location=us-central1 + +POSITIONAL ARGUMENTS + Message bus resource - The message bus on which to list enrollments. 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 message_bus 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. + + MESSAGE_BUS + ID of the message bus or fully qualified identifier for the message + bus. + + To set the message-bus attribute: + ▸ provide the argument message_bus on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc message bus, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument message_bus on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/message-buses/publish b/gcloud/beta/eventarc/message-buses/publish new file mode 100644 index 000000000..12322df33 --- /dev/null +++ b/gcloud/beta/eventarc/message-buses/publish @@ -0,0 +1,121 @@ +NAME + gcloud beta eventarc message-buses publish - publish to an Eventarc message + bus + +SYNOPSIS + gcloud beta eventarc message-buses publish + (MESSAGE_BUS : --location=LOCATION) + (--avro-message=AVRO_MESSAGE | --json-message=JSON_MESSAGE + | [--event-data=EVENT_DATA --event-id=EVENT_ID + --event-source=EVENT_SOURCE --event-type=EVENT_TYPE + : --event-attributes=[ATTRIBUTE=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Publish to an Eventarc message bus. + +EXAMPLES + To publish an event to the message bus my-message-bus with event id 1234, + event type event-provider.event.v1.eventType, event source + //event-provider/event/source, event data { "key": "value" } and event + attributes of attribute1=value, run: + + $ gcloud beta eventarc message-buses publish my-message-bus \ + --location=us-central1 --event-id=1234 \ + --event-type=event-provider.event.v1.eventType \ + --event-source="//event-provider/event/source" \ + --event-data='{"key": "value"}' \ + --event-attributes=attribute1=value + + To publish an event to the message bus my-message-bus with a json message, + run: + + $ gcloud beta eventarc message-buses publish my-message-bus \ + --location=us-central1 \ + --json-message='{"id": 1234, "type": + "event-provider.event.v1.eventType", "source": + "//event-provider/event/source", "specversion": "1.0", "data": + {"key": "value"}}' + +POSITIONAL ARGUMENTS + Message bus resource - Message bus to publish to. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument message_bus 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. + + MESSAGE_BUS + ID of the message bus or fully qualified identifier for the message + bus. + + To set the message-bus attribute: + ▸ provide the argument message_bus on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc message bus, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument message_bus on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --avro-message=AVRO_MESSAGE + An Avro message to publish to the message bus. + + --json-message=JSON_MESSAGE + A JSON message to publish to the message bus. + + --event-data=EVENT_DATA + An event data. The event data of a published event. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --event-id=EVENT_ID + An event id. The id of a published event. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --event-source=EVENT_SOURCE + An event source. The event source of a published event. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --event-type=EVENT_TYPE + An event type. The event type of a published event. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --event-attributes=[ATTRIBUTE=VALUE,...] + Event attributes. The event attributes of a published event.This flag + can be repeated to add more attributes. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/message-buses/update b/gcloud/beta/eventarc/message-buses/update new file mode 100644 index 000000000..955c75b03 --- /dev/null +++ b/gcloud/beta/eventarc/message-buses/update @@ -0,0 +1,92 @@ +NAME + gcloud beta eventarc message-buses update - update an Eventarc message bus + +SYNOPSIS + gcloud beta eventarc message-buses update + (MESSAGE_BUS : --location=LOCATION) [--async] + [--logging-config=LOGGING_CONFIG] + [--clear-crypto-key | --crypto-key=CRYPTO_KEY] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an Eventarc message bus. + +EXAMPLES + To update the message bus my-message-bus in location us-central1, run: + + $ gcloud beta eventarc message-buses update my-message-bus \ + --location=us-central1 + + To configure the message bus my-message-bus in location us-central1 with a + Cloud KMS CryptoKey, run: + + $ gcloud beta eventarc message-buses update my-message-bus \ + --location=us-central1 \ + --crypto-key=projects/PROJECT_ID/locations/KMS_LOCATION/\ + keyRings/KEYRING/cryptoKeys/KEY + +POSITIONAL ARGUMENTS + Message bus resource - Message bus to update. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument message_bus 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. + + MESSAGE_BUS + ID of the message bus or fully qualified identifier for the message + bus. + + To set the message-bus attribute: + ▸ provide the argument message_bus on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc message bus, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument message_bus on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --logging-config=LOGGING_CONFIG + The logging config of the message bus. LOGGING_CONFIG must be one of: + NONE, DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY. + + At most one of these can be specified: + + --clear-crypto-key + Remove the previously configured crypto key. The channel will + continue to be encrypted using Google-managed keys. + + --crypto-key=CRYPTO_KEY + Fully qualified name of the crypto key to use for customer-managed + encryption. If this is unspecified, Google-managed keys will be used + for encryption. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/pipelines/create b/gcloud/beta/eventarc/pipelines/create new file mode 100644 index 000000000..8d6bafeb0 --- /dev/null +++ b/gcloud/beta/eventarc/pipelines/create @@ -0,0 +1,608 @@ +NAME + gcloud beta eventarc pipelines create - create an Eventarc pipeline + +SYNOPSIS + gcloud beta eventarc pipelines create (PIPELINE : --location=LOCATION) + --destinations=http_endpoint_uri=URI, + http_endpoint_message_binding_template=HTTP_ENDPOINT_MESSAGE_BINDING_TEMPLATE, + workflow=WORKFLOW,message_bus=MESSAGE_BUS,pubsub_topic=PUBSUB_TOPIC, + project=PROJECT,location=LOCATION, + network_attachment=NETWORK_ATTACHMENT, + google_oidc_authentication_service_account=GOOGLE_OIDC_AUTHENTICATION_SERVICE_ACCOUNT, + google_oidc_authentication_audience=GOOGLE_OIDC_AUTHENTICATION_AUDIENCE, + oauth_token_authentication_service_account=OAUTH_TOKEN_AUTHENTICATION_SERVICE_ACCOUNT, + oauth_token_authentication_scope=OAUTH_TOKEN_AUTHENTICATION_SCOPE, + output_payload_format_json=OUTPUT_PAYLOAD_FORMAT_JSON, + output_payload_format_avro_schema_definition=OUTPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION, + output_payload_format_protobuf_schema_definition=OUTPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION|[...] + [--async] [--crypto-key=CRYPTO_KEY] [--logging-config=LOGGING_CONFIG] + [--mediations=[transformation_template=TRANSFORMATION_TEMPLATE|...]] + [--input-payload-format-avro-schema-definition=INPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION | --input-payload-format-json=INPUT_PAYLOAD_FORMAT_JSON | --input-payload-format-protobuf-schema-definition=INPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION] + [--max-retry-attempts=MAX_RETRY_ATTEMPTS + --max-retry-delay=MAX_RETRY_DELAY --min-retry-delay=MIN_RETRY_DELAY] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create an Eventarc pipeline. + +EXAMPLES + To create a new pipeline my-pipeline in location us-central1 with its + destination targeting HTTP endpoint URI 'https://example-endpoint.com' and + network attachment 'my-network-attachment', run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + network_attachment=my-network-attachment + + To create a new pipeline my-pipeline in location us-central1 with an HTTP + endpoint URI destination and a message binding template, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + http_endpoint_message_binding_template='{"headers": + {"new-header-key": + "new-header-value"}}',network_attachment=my-network-attachment + + To create a new pipeline my-pipeline in location us-central1 with a Cloud + Workflow destination my-workflow and network attachment + my-network-attachment, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=workflow=my-workflow,\ + network_attachment=my-network-attachment + + To create a new pipeline my-pipeline in location us-central1 with a message + bus destination my-message-bus and network attachment + my-network-attachment, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=message_bus=my-message-bus,\ + network_attachment=my-network-attachment + + To create a new pipeline my-pipeline in location us-central1 with a Cloud + Pub/Sub Topic destination my-topic and network attachment + my-network-attachment, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=pubsub_topic=my-topic,\ + network_attachment=my-network-attachment + + To create a new pipeline my-pipeline in location us-central1 with a Cloud + Workflow in project example-project and location us-east1, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=workflow=my-workflow,project=example-project,\ + location=us-east1,network_attachment=my-network-attachment + + To create a new pipeline my-pipeline in location us-central1 with an HTTP + endpoint URI destination https://example-endpoint.com and a service account + example-service-account@example-project.gserviceaccount.iam.com for OIDC + authentication, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + network_attachment=my-network-attachment,\ + google_oidc_authentication_service_account=example-service-account@e\ + xample-project.gserviceaccount.iam.com + + To create a new pipeline my-pipeline in location us-central1 with an HTTP + endpoint URI destination https://example-endpoint.com and a service account + example-service-account@example-project.gserviceaccount.iam.com for OIDC + authentication with audience https://example.com, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + network_attachment=my-network-attachment,\ + google_oidc_authentication_service_account=example-service-account@e\ + xample-project.gserviceaccount.iam.com,\ + google_oidc_authentication_audience='https://example.com' + + To create a new pipeline my-pipeline in location us-central1 with an HTTP + endpoint URI destination https://example-endpoint.com and a service account + example-service-account@example-project.gserviceaccount.iam.com for OAuth + token authentication, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + network_attachment=my-network-attachment,\ + oauth_token_authentication_service_account=example-service-account@e\ + xample-project.gserviceaccount.iam.com + + To create a new pipeline my-pipeline in location us-central1 with an HTTP + endpoint URI destination https://example-endpoint.com and a service account + example-service-account@example-project.gserviceaccount.iam.com for OAuth + token authentication with scope + https://www.googleapis.com/auth/cloud-platform, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + network_attachment=my-network-attachment,\ + oauth_token_authentication_service_account=example-service-account@e\ + xample-project.gserviceaccount.iam.com,\ + oauth_token_authentication_scope='https://www.googleapis.com/auth/cl\ + oud-platform' + + To create a new pipeline my-pipeline in location us-central1 with an HTTP + endpoint URI destination https://example-endpoint.com and the JSON input + and output payload formats, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + network_attachment=my-network-attachment,\ + output_payload_format_json= --input-payload-format-json= + + To create a new pipeline my-pipeline in location us-central1 with an HTTP + endpoint URI destination https://example-endpoint.com and the Avro input + and output payload formats, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + network_attachment=my-network-attachment,\ + output_payload_format_avro_schema_definition='{"type": "record", + "name": "my_record", "fields": [{"name": "my_field", "type": + "string"}]}' \ + --input-payload-format-avro-schema-definition='{"type": + "record", "name": "my_record", "fields": [{"name": "my_field", + "type": "string"}]}' + + To create a new pipeline my-pipeline in location us-central1 with an HTTP + endpoint URI destination https://example-endpoint.com and the Protobuf + input and output payload formats, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + network_attachment=my-network-attachment,\ + output_payload_format_protobuf_schema_definition='syntax = + "proto3"; message Location { string home_address = 1; }' \ + --input-payload-format-protobuf-schema-definition='syntax = + "proto3"; message Location { string home_address = 1; }' + + To create a new pipeline my-pipeline in location us-central1 with an HTTP + endpoint URI destination https://example-endpoint.com and a transformation + mediation, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + network_attachment=my-network-attachment \ + --mediations=transformation_template='message.removeFields(["dat\ + a.credit_card_number","data.ssn"])' + + To create a new pipeline my-pipeline in location us-central1 with an HTTP + endpoint URI destination https://example-endpoint.com and a INFO level + logging configuration, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + network_attachment=my-network-attachment --logging_config=INFO + + To create a new pipeline my-pipeline in location us-central1 with an HTTP + endpoint URI destination https://example-endpoint.com and a custom retry + policy, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + network_attachment=my-network-attachment --max-retry-attempts=10 \ + --min-retry-delay=2s --max-retry-delay=64s + + To create a new pipeline my-pipeline in location us-central1 with an HTTP + endpoint URI destination https://example-endpoint.com and a Cloud KMS + CryptoKey, run: + + $ gcloud beta eventarc pipelines create my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + network_attachment=my-network-attachment \ + --crypto-key=projects/PROJECT_ID/locations/KMS_LOCATION/\ + keyRings/KEYRING/cryptoKeys/KEY + +POSITIONAL ARGUMENTS + Pipeline resource - The pipeline 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 pipeline 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. + + PIPELINE + ID of the pipeline or fully qualified identifier for the pipeline. + + To set the pipeline attribute: + ▸ provide the argument pipeline on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc pipeline, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument pipeline on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +REQUIRED FLAGS + --destinations=http_endpoint_uri=URI,http_endpoint_message_binding_template=HTTP_ENDPOINT_MESSAGE_BINDING_TEMPLATE,workflow=WORKFLOW,message_bus=MESSAGE_BUS,pubsub_topic=PUBSUB_TOPIC,project=PROJECT,location=LOCATION,network_attachment=NETWORK_ATTACHMENT,google_oidc_authentication_service_account=GOOGLE_OIDC_AUTHENTICATION_SERVICE_ACCOUNT,google_oidc_authentication_audience=GOOGLE_OIDC_AUTHENTICATION_AUDIENCE,oauth_token_authentication_service_account=OAUTH_TOKEN_AUTHENTICATION_SERVICE_ACCOUNT,oauth_token_authentication_scope=OAUTH_TOKEN_AUTHENTICATION_SCOPE,output_payload_format_json=OUTPUT_PAYLOAD_FORMAT_JSON,output_payload_format_avro_schema_definition=OUTPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION,output_payload_format_protobuf_schema_definition=OUTPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION|[...] + The pipeline's destinations. This flag can be repeated to add more + destinations to the list. Currently, only one destination is supported + per pipeline. + + A destination is specified in a dict format. The valid choices of keys + are + ◆ http_endpoint_uri + ◆ http_endpoint_message_binding_template + ◆ workflow + ◆ message_bus + ◆ pubsub_topic + ◆ project + ◆ location + ◆ network_attachment + ◆ google_oidc_authentication_service_account + ◆ google_oidc_authentication_audience + ◆ oauth_token_authentication_service_account + ◆ oauth_token_authentication_scope + ◆ output_payload_format_json + ◆ output_payload_format_avro_schema_definition + ◆ output_payload_format_protobuf_schema_definition + + The detailed explanations for each key are as follows: + + 1.http_endpoint_uri: the URI of the HTTP endpoint. + + The value must be a RFC2396 URI string. Only HTTPS protocol is supported. + The host can be either a static IP addressable from the VPC specified by the network config, or an internal DNS hostname of the service resolvable via Cloud DNS. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment + + 2.http_endpoint_message_binding_template: the CEL expression used to + construct a new HTTP request to be sent to the final destination. + + It can be optionally specified alongside with `http_endpoint_uri`. + It represents a configuration used to bind a message to the final HTTP request that will be sent to the destination. + If a binding is not specified, by default the message is treated as a CloudEvent and is mapped to the HTTP request according to the CloudEvent HTTP Protocol Binding Binary Content Mode. + The Pipeline converts the data field of the message to the format provided in `output_payload_format` and maps it to the body field of the result. + It also sets the corresponding Content-Type header to the `output_payload_format` type. + If the `output_payload_format` is unspecified, then the Pipeline will treat the data field of the message as opaque binary data and attach it to the request body as bytes. + In this case, the Content-Type header will be set to the value of the datacontenttype attribute set on the incoming CloudEvent message if present, or the `application/octet-stream` MIME type otherwise. + The Pipeline expects that the content of the message will adhere to the standard CloudEvent format. If not then the outgoing message request may fail with a persistent error. + + The result of the CEL expression must be a map of key-value pairs such that: + 1. If a map named `headers` exists on the result of the expression, then its key-value pairs are directly mapped to the HTTP request headers. + The headers values are constructed from the corresponding value type's canonical representation. + If the `headers` field does not exist, then the resulting HTTP request will not contain headers. + 2. If a field named `body` exists on the result of the expression, then its value is directly mapped to the body of the request. + If the value of the `body` field is of type bytes or string, then it is used as the HTTP request body as-is withouth any conversion. + If the `body` field is of any other type, then it is converted to a JSON string. + If the `body` field does not exist, then the resulting HTTP request will not contain a body. + 3. Any other fields in the resulting expression will be ignored. + + The CEL expression may access the incoming CloudEvent message in its definition, as follows: + 1. The `data` field of the incoming CloudEvent message can be accessed using the `message.data` value. + 2. Each attribute of the incoming CloudEvent message can be accessed using the `message.` value, where is the name of the attribute. + + Headers added to the request by previous filters in the chain can be accessed in the CEL expression using the `headers` variable. + The `headers` variable defines a map of key-value pairs corresponding to the HTTP headers added by previous mediation steps and not the headers present on the original incoming request. + For example, the following CEL expression can be used to construct a headers-only HTTP request by adding an additional header to the headers added by previous mediations in the Pipeline: + + {"headers": headers.merge({"new-header-key": "new-header-value"})} + + Additionally, the following CEL extension functions can be used in this CEL expression: + 1. toBase64Url: + map.toBase64Url() -> string + Converts a CelValue to a base64url encoded string. + 2. toJsonString: + map.toJsonString() -> string + Converts a CelValue to a JSON string. + 3. merge: + map1.merge(map2) -> map3 + Merges the passed CEL map with the existing CEL map the function is applied to. + If the same key exists in both maps, or if the key's value is type map, then both maps are merged; Otherwise, the value from the passed map is used. + 4. toMap: + list(map).toMap() -> map + Converts a CEL list of CEL maps to a single CEL map. + 5. toDestinationPayloadFormat: + message.data.toDestinationPayloadFormat() -> string or bytes + Converts the message data to the destination payload format specified in `output_payload_format`. + This function is meant to be applied to the message.data field. + If the destination payload format is not set, the function will return the message data unchanged. + 6. toCloudEventJsonWithPayloadFormat: + message.toCloudEventJsonWithPayloadFormat() -> map + Converts a message to the corresponding structure of JSON format for CloudEvents. + This function applies toDestinationPayloadFormat() to the message data. + It also sets the corresponding datacontenttype of the CloudEvent, as indicated by the `output_payload_format` field. + If `output_payload_format` is not set, it will use the existing datacontenttype on the CloudEvent if present; Otherwise, it leaves the datacontenttype unset. + This function expects that the content of the message will adhere to the standard CloudEvent format. If it doesn't then this function will fail. + The result is a CEL map that corresponds to the JSON representation of the CloudEvent. To convert that data to a JSON string it can be chained with the toJsonString() function. + + Note that `http_endpoint_message_binding_template` cannot be set when `http_endpoint_uri` is not set. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + http_endpoint_message_binding_template='{"headers": + {"new-header-key": + "new-header-value"}}',network_attachment=example-network-attachment + + 3.workflow: the destination Workflow ID. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=workflow=my-workflow,\ + network_attachment=example-network-attachment + + 4.message_bus: the destination Message Bus ID. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=message_bus=my-message-bus,\ + network_attachment=example-network-attachment + + 5.pubsub_topic: the destination Pub/Sub topic ID. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=pubsub_topic=my-topic,\ + network_attachment=example-network-attachment + + NOTE: Exactly one of the http_endpoint_uri, workflow, message_bus, or + pubsub_topic key must be set. + + 6.project: the project ID of the destination resource. If project is + not set, then the project ID of the Pipeline will be used. NOTE: + project cannot be set when http_endpoint_uri is set. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=project=example-project,workflow=my-workflow,\ + network_attachment=example-network-attachment + + 7.location: the location of the destination resource. If location is + not set, then the location of the Pipeline will be used. NOTE: location + cannot be set when http_endpoint_uri is set. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=location=us-east1,workflow=my-workflow,\ + network_attachment=example-network-attachment + + 8.network_attachment: the ID of the Network Attachment that allows + access to the consumer VPC. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=network_attachment=my-network-attachment,\ + http_endpoint_uri='https://example.com' + + NOTE: network_attachment must be specified for a Pipeline. + + 9.google_oidc_authentication_service_account: the service account email + used to generate the OIDC token. The token can be used to invoke Cloud + Run and Cloud Function destinations or HTTP endpoints that support + Google OIDC. Note that the principal who calls this API must have + iam.serviceAccounts.actAs permission in the service account. See + https://cloud.google.com/iam/docs/understanding-service-accounts?hl=en#sa_common + for more information. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + google_oidc_authentication_service_account=example-service-account@e\ + xample-project.gserviceaccount.iam.com + + 10.google_oidc_authentication_audience: the audience claim which + identifies the recipient that the JWT is intended for. If unspecified, + the destination URI will be used. NOTE: + google_oidc_authentication_audience can only be set if + google_oidc_authentication_service_account is set. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + google_oidc_authentication_service_account=example-service-account@e\ + xample-project.gserviceaccount.iam.com,\ + google_oidc_authentication_audience='https://example.com' + + 11.oauth_token_authentication_service_account: the service account + email used to generate the OAuth token. OAuth authorization should + generally only be used when calling Google APIs hosted on + *.googleapis.com. Note that the principal who calls this API must have + iam.serviceAccounts.actAs permission in the service account. See + https://cloud.google.com/iam/docs/understanding-service-accounts?hl=en#sa_common + for more information. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + oauth_token_authentication_service_account=example-service-account@e\ + xample-project.gserviceaccount.iam.com + + 12.oauth_token_authentication_scope: the scope used to generate the + OAuth token. If unspecified, + "https://www.googleapis.com/auth/cloud-platform" will be used. NOTE: + oauth_token_authentication_scope can only be set if + oauth_token_authentication_service_account is set. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + oauth_token_authentication_service_account=example-service-account@e\ + xample-project.gserviceaccount.iam.com,\ + oauth_token_authentication_scope=https://www.googleapis.com/auth/\ + cloud-platform + + NOTE: At most one of google_oidc_authentication_service_account or + oauth_token_authentication_service_account can be set. + + 13.output_payload_format_json: indicates that the output payload format + is JSON. NOTE: JSON schema is not supported currently. Any value + specified by this key will be ignored. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + output_payload_format_json= --input-payload-format-json= + + 14.output_payload_format_avro_schema_definition: the schema definition + of the Avro output payload format. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + output_payload_format_avro_schema_definition='{"type": "record", + "name": "my_record", "fields": [{"name": "field1", "type": + "string"}]}' \ + --input-payload-format-avro-schema-definition='{"type": + "record", "name": "my_record", "fields": [{"name": "field1", + "type": "string"}]}' + + 15.output_payload_format_protobuf_schema_definition: the schema + definition of the Protobuf output payload format. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + output_payload_format_protobuf_schema_definition='syntax = + "proto3"; message Location { string home_address = 1; }' \ + --input-payload-format-protobuf-schema-definition='syntax = + "proto3"; message Location { string home_address = 1; }' + + NOTE: If none of the input_payload_format_json, + input_payload_format_avro_schema_definition, or + input_payload_format_protobuf_schema_definition is set, then the + message data will be treated as an opaque binary and no output format + can be set on the Pipeline through the output_payload_format_json, + output_payload_format_avro_schema_definition, or + output_payload_format_protobuf_schema_definition field. Any Mediations + on the Pipeline that involve access to the data field will fail as + persistent errors. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --crypto-key=CRYPTO_KEY + Fully qualified name of the crypto key to use for customer-managed + encryption. If this is unspecified, Google-managed keys will be used + for encryption. + + --logging-config=LOGGING_CONFIG + The logging config of the pipeline. LOGGING_CONFIG must be one of: + NONE, DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY. + + --mediations=[transformation_template=TRANSFORMATION_TEMPLATE|...] + The different ways to modify the Pipeline. Currently, only one + mediation is supported per pipeline. + + A mediation is specified in a dict format. Currently, the only valid + choice is transformation_template. + + This is the template to apply to transform messages. + + For complex transformations, shell parameter processing may fail to + parse the CEL expressions. Please see gcloud topic flags-file for how + to use https://cloud.google.com/sdk/gcloud/reference/topic/flags-file + feature of gcloud to pass in CEL expressions. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --mediations=transformation_template='message.removeFields(["dat\ + a.credit_card_number","data.ssn"])' + + At most one of these can be specified: + + --input-payload-format-avro-schema-definition=INPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION + The pipeline's input payload Avro schema definition. If this is set, + then any messages not matching this format will be treated as + persistent errors. + + --input-payload-format-json=INPUT_PAYLOAD_FORMAT_JSON + The pipeline's input payload format is JSON. If this is set, then any + messages not matching this format will be treated as persistent + errors. + + --input-payload-format-protobuf-schema-definition=INPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION + The pipeline's input payload Protobuf schema definition. If this is + set, then any messages not matching this format will be treated as + persistent errors. + + The retry policy configuration for the Pipeline. The pipeline exponentially + backs off if the destination is non-responsive or returns a retryable error + code. The backoff starts with a 1 second delay and doubles the delay after + each failed attempt. The delay is capped at 60 seconds. If the + max-retry-delay and min-retry-delay are set to the same value, then the + duration between retries is constant. + + --max-retry-attempts=MAX_RETRY_ATTEMPTS + The maximum number of retry attempts. If not set, the default value + is 5. + + --max-retry-delay=MAX_RETRY_DELAY + The maximum retry delay in seconds. If not set, the default value + is 60. + + --min-retry-delay=MIN_RETRY_DELAY + The minimum retry delay in seconds. If not set, the default value + is 1. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/pipelines/delete b/gcloud/beta/eventarc/pipelines/delete new file mode 100644 index 000000000..3705b2cfa --- /dev/null +++ b/gcloud/beta/eventarc/pipelines/delete @@ -0,0 +1,65 @@ +NAME + gcloud beta eventarc pipelines delete - delete an Eventarc pipeline + +SYNOPSIS + gcloud beta eventarc pipelines delete (PIPELINE : --location=LOCATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete an Eventarc pipeline. + +EXAMPLES + To delete the pipeline my-pipeline in location us-central1, run: + + $ gcloud beta eventarc pipelines delete my-pipeline \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Pipeline resource - Pipeline 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 pipeline 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. + + PIPELINE + ID of the pipeline or fully qualified identifier for the pipeline. + + To set the pipeline attribute: + ▸ provide the argument pipeline on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc pipeline, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument pipeline on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/pipelines/describe b/gcloud/beta/eventarc/pipelines/describe new file mode 100644 index 000000000..fb9b04518 --- /dev/null +++ b/gcloud/beta/eventarc/pipelines/describe @@ -0,0 +1,60 @@ +NAME + gcloud beta eventarc pipelines describe - describe an Eventarc pipeline + +SYNOPSIS + gcloud beta eventarc pipelines describe (PIPELINE : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an Eventarc pipeline. + +EXAMPLES + To describe the pipeline my-pipeline in location us-central1, run: + + $ gcloud beta eventarc pipelines describe my-pipeline \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Pipeline resource - Pipeline 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 pipeline 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. + + PIPELINE + ID of the pipeline or fully qualified identifier for the pipeline. + + To set the pipeline attribute: + ▸ provide the argument pipeline on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc pipeline, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument pipeline on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/pipelines/help b/gcloud/beta/eventarc/pipelines/help new file mode 100644 index 000000000..a9ef1e9a7 --- /dev/null +++ b/gcloud/beta/eventarc/pipelines/help @@ -0,0 +1,35 @@ +NAME + gcloud beta eventarc pipelines - manage Eventarc pipelines + +SYNOPSIS + gcloud beta eventarc pipelines COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Eventarc pipelines. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create an Eventarc pipeline. + + delete + (BETA) Delete an Eventarc pipeline. + + describe + (BETA) Describe an Eventarc pipeline. + + list + (BETA) List Eventarc pipelines. + + update + (BETA) Update an Eventarc pipeline. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/pipelines/list b/gcloud/beta/eventarc/pipelines/list new file mode 100644 index 000000000..659282892 --- /dev/null +++ b/gcloud/beta/eventarc/pipelines/list @@ -0,0 +1,90 @@ +NAME + gcloud beta eventarc pipelines list - list Eventarc pipelines + +SYNOPSIS + gcloud beta eventarc pipelines list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Eventarc pipelines. + +EXAMPLES + To list all pipelines in location us-central1, run: + + $ gcloud beta eventarc pipelines list --location=us-central1 + + To list all pipelines in all locations, run: + + $ gcloud beta eventarc pipelines list --location=- + + or + + $ gcloud beta eventarc pipelines list + +FLAGS + Location resource - Location for which to list pipelines. This should be + one of the supported regions. This represents a Cloud resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property eventarc/location with a fully specified name; + ◆ use '-' location to aggregate results for all Eventarc locations with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location; + ▸ use '-' location to aggregate results for all Eventarc locations. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/eventarc/pipelines/update b/gcloud/beta/eventarc/pipelines/update new file mode 100644 index 000000000..fe6683b03 --- /dev/null +++ b/gcloud/beta/eventarc/pipelines/update @@ -0,0 +1,439 @@ +NAME + gcloud beta eventarc pipelines update - update an Eventarc pipeline + +SYNOPSIS + gcloud beta eventarc pipelines update (PIPELINE : --location=LOCATION) + [--async] + [--destinations=http_endpoint_uri=URI, + http_endpoint_message_binding_template=HTTP_ENDPOINT_MESSAGE_BINDING_TEMPLATE, + workflow=WORKFLOW,message_bus=MESSAGE_BUS,pubsub_topic=PUBSUB_TOPIC, + project=PROJECT,location=LOCATION, + network_attachment=NETWORK_ATTACHMENT, + google_oidc_authentication_service_account=GOOGLE_OIDC_AUTHENTICATION_SERVICE_ACCOUNT, + google_oidc_authentication_audience=GOOGLE_OIDC_AUTHENTICATION_AUDIENCE, + oauth_token_authentication_service_account=OAUTH_TOKEN_AUTHENTICATION_SERVICE_ACCOUNT, + oauth_token_authentication_scope=OAUTH_TOKEN_AUTHENTICATION_SCOPE, + output_payload_format_json=OUTPUT_PAYLOAD_FORMAT_JSON, + output_payload_format_avro_schema_definition=OUTPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION, + output_payload_format_protobuf_schema_definition=OUTPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION|[...]] + [--logging-config=LOGGING_CONFIG] + [--mediations=[transformation_template=TRANSFORMATION_TEMPLATE|...]] + [--clear-crypto-key | --crypto-key=CRYPTO_KEY] + [--input-payload-format-avro-schema-definition=INPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION | --input-payload-format-json=INPUT_PAYLOAD_FORMAT_JSON | --input-payload-format-protobuf-schema-definition=INPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION] + [--max-retry-attempts=MAX_RETRY_ATTEMPTS + --max-retry-delay=MAX_RETRY_DELAY --min-retry-delay=MIN_RETRY_DELAY] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an Eventarc pipeline. + +EXAMPLES + To update the pipeline my-pipeline with its destination targeting HTTP + endpoint URI 'https://example-endpoint.com' and network attachment + 'my-network-attachment', run: + + $ gcloud beta eventarc pipelines update my-pipeline \ + --location=us-central1 \ + --destinations=http_endpoint_uri='https://example-endpoint.com',\ + network_attachment=my-network-attachment + +POSITIONAL ARGUMENTS + Pipeline resource - The pipeline to update. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument pipeline 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. + + PIPELINE + ID of the pipeline or fully qualified identifier for the pipeline. + + To set the pipeline attribute: + ▸ provide the argument pipeline on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the Eventarc pipeline, which should be one of the + supported regions. Alternatively, set the [eventarc/location] + property. + + To set the location attribute: + ▸ provide the argument pipeline on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property eventarc/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --destinations=http_endpoint_uri=URI,http_endpoint_message_binding_template=HTTP_ENDPOINT_MESSAGE_BINDING_TEMPLATE,workflow=WORKFLOW,message_bus=MESSAGE_BUS,pubsub_topic=PUBSUB_TOPIC,project=PROJECT,location=LOCATION,network_attachment=NETWORK_ATTACHMENT,google_oidc_authentication_service_account=GOOGLE_OIDC_AUTHENTICATION_SERVICE_ACCOUNT,google_oidc_authentication_audience=GOOGLE_OIDC_AUTHENTICATION_AUDIENCE,oauth_token_authentication_service_account=OAUTH_TOKEN_AUTHENTICATION_SERVICE_ACCOUNT,oauth_token_authentication_scope=OAUTH_TOKEN_AUTHENTICATION_SCOPE,output_payload_format_json=OUTPUT_PAYLOAD_FORMAT_JSON,output_payload_format_avro_schema_definition=OUTPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION,output_payload_format_protobuf_schema_definition=OUTPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION|[...] + The pipeline's destinations. This flag can be repeated to add more + destinations to the list. Currently, only one destination is supported + per pipeline. + + A destination is specified in a dict format. The valid choices of keys + are + ◆ http_endpoint_uri + ◆ http_endpoint_message_binding_template + ◆ workflow + ◆ message_bus + ◆ pubsub_topic + ◆ project + ◆ location + ◆ network_attachment + ◆ google_oidc_authentication_service_account + ◆ google_oidc_authentication_audience + ◆ oauth_token_authentication_service_account + ◆ oauth_token_authentication_scope + ◆ output_payload_format_json + ◆ output_payload_format_avro_schema_definition + ◆ output_payload_format_protobuf_schema_definition + + The detailed explanations for each key are as follows: + + 1.http_endpoint_uri: the URI of the HTTP endpoint. + + The value must be a RFC2396 URI string. Only HTTPS protocol is supported. + The host can be either a static IP addressable from the VPC specified by the network config, or an internal DNS hostname of the service resolvable via Cloud DNS. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment + + 2.http_endpoint_message_binding_template: the CEL expression used to + construct a new HTTP request to be sent to the final destination. + + It can be optionally specified alongside with `http_endpoint_uri`. + It represents a configuration used to bind a message to the final HTTP request that will be sent to the destination. + If a binding is not specified, by default the message is treated as a CloudEvent and is mapped to the HTTP request according to the CloudEvent HTTP Protocol Binding Binary Content Mode. + The Pipeline converts the data field of the message to the format provided in `output_payload_format` and maps it to the body field of the result. + It also sets the corresponding Content-Type header to the `output_payload_format` type. + If the `output_payload_format` is unspecified, then the Pipeline will treat the data field of the message as opaque binary data and attach it to the request body as bytes. + In this case, the Content-Type header will be set to the value of the datacontenttype attribute set on the incoming CloudEvent message if present, or the `application/octet-stream` MIME type otherwise. + The Pipeline expects that the content of the message will adhere to the standard CloudEvent format. If not then the outgoing message request may fail with a persistent error. + + The result of the CEL expression must be a map of key-value pairs such that: + 1. If a map named `headers` exists on the result of the expression, then its key-value pairs are directly mapped to the HTTP request headers. + The headers values are constructed from the corresponding value type's canonical representation. + If the `headers` field does not exist, then the resulting HTTP request will not contain headers. + 2. If a field named `body` exists on the result of the expression, then its value is directly mapped to the body of the request. + If the value of the `body` field is of type bytes or string, then it is used as the HTTP request body as-is withouth any conversion. + If the `body` field is of any other type, then it is converted to a JSON string. + If the `body` field does not exist, then the resulting HTTP request will not contain a body. + 3. Any other fields in the resulting expression will be ignored. + + The CEL expression may access the incoming CloudEvent message in its definition, as follows: + 1. The `data` field of the incoming CloudEvent message can be accessed using the `message.data` value. + 2. Each attribute of the incoming CloudEvent message can be accessed using the `message.` value, where is the name of the attribute. + + Headers added to the request by previous filters in the chain can be accessed in the CEL expression using the `headers` variable. + The `headers` variable defines a map of key-value pairs corresponding to the HTTP headers added by previous mediation steps and not the headers present on the original incoming request. + For example, the following CEL expression can be used to construct a headers-only HTTP request by adding an additional header to the headers added by previous mediations in the Pipeline: + + {"headers": headers.merge({"new-header-key": "new-header-value"})} + + Additionally, the following CEL extension functions can be used in this CEL expression: + 1. toBase64Url: + map.toBase64Url() -> string + Converts a CelValue to a base64url encoded string. + 2. toJsonString: + map.toJsonString() -> string + Converts a CelValue to a JSON string. + 3. merge: + map1.merge(map2) -> map3 + Merges the passed CEL map with the existing CEL map the function is applied to. + If the same key exists in both maps, or if the key's value is type map, then both maps are merged; Otherwise, the value from the passed map is used. + 4. toMap: + list(map).toMap() -> map + Converts a CEL list of CEL maps to a single CEL map. + 5. toDestinationPayloadFormat: + message.data.toDestinationPayloadFormat() -> string or bytes + Converts the message data to the destination payload format specified in `output_payload_format`. + This function is meant to be applied to the message.data field. + If the destination payload format is not set, the function will return the message data unchanged. + 6. toCloudEventJsonWithPayloadFormat: + message.toCloudEventJsonWithPayloadFormat() -> map + Converts a message to the corresponding structure of JSON format for CloudEvents. + This function applies toDestinationPayloadFormat() to the message data. + It also sets the corresponding datacontenttype of the CloudEvent, as indicated by the `output_payload_format` field. + If `output_payload_format` is not set, it will use the existing datacontenttype on the CloudEvent if present; Otherwise, it leaves the datacontenttype unset. + This function expects that the content of the message will adhere to the standard CloudEvent format. If it doesn't then this function will fail. + The result is a CEL map that corresponds to the JSON representation of the CloudEvent. To convert that data to a JSON string it can be chained with the toJsonString() function. + + Note that `http_endpoint_message_binding_template` cannot be set when `http_endpoint_uri` is not set. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + http_endpoint_message_binding_template='{"headers": + {"new-header-key": + "new-header-value"}}',network_attachment=example-network-attachment + + 3.workflow: the destination Workflow ID. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=workflow=my-workflow,\ + network_attachment=example-network-attachment + + 4.message_bus: the destination Message Bus ID. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=message_bus=my-message-bus,\ + network_attachment=example-network-attachment + + 5.pubsub_topic: the destination Pub/Sub topic ID. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=pubsub_topic=my-topic,\ + network_attachment=example-network-attachment + + NOTE: Exactly one of the http_endpoint_uri, workflow, message_bus, or + pubsub_topic key must be set. + + 6.project: the project ID of the destination resource. If project is + not set, then the project ID of the Pipeline will be used. NOTE: + project cannot be set when http_endpoint_uri is set. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=project=example-project,workflow=my-workflow,\ + network_attachment=example-network-attachment + + 7.location: the location of the destination resource. If location is + not set, then the location of the Pipeline will be used. NOTE: location + cannot be set when http_endpoint_uri is set. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=location=us-east1,workflow=my-workflow,\ + network_attachment=example-network-attachment + + 8.network_attachment: the ID of the Network Attachment that allows + access to the consumer VPC. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=network_attachment=my-network-attachment,\ + http_endpoint_uri='https://example.com' + + NOTE: network_attachment must be specified for a Pipeline. + + 9.google_oidc_authentication_service_account: the service account email + used to generate the OIDC token. The token can be used to invoke Cloud + Run and Cloud Function destinations or HTTP endpoints that support + Google OIDC. Note that the principal who calls this API must have + iam.serviceAccounts.actAs permission in the service account. See + https://cloud.google.com/iam/docs/understanding-service-accounts?hl=en#sa_common + for more information. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + google_oidc_authentication_service_account=example-service-account@e\ + xample-project.gserviceaccount.iam.com + + 10.google_oidc_authentication_audience: the audience claim which + identifies the recipient that the JWT is intended for. If unspecified, + the destination URI will be used. NOTE: + google_oidc_authentication_audience can only be set if + google_oidc_authentication_service_account is set. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + google_oidc_authentication_service_account=example-service-account@e\ + xample-project.gserviceaccount.iam.com,\ + google_oidc_authentication_audience='https://example.com' + + 11.oauth_token_authentication_service_account: the service account + email used to generate the OAuth token. OAuth authorization should + generally only be used when calling Google APIs hosted on + *.googleapis.com. Note that the principal who calls this API must have + iam.serviceAccounts.actAs permission in the service account. See + https://cloud.google.com/iam/docs/understanding-service-accounts?hl=en#sa_common + for more information. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + oauth_token_authentication_service_account=example-service-account@e\ + xample-project.gserviceaccount.iam.com + + 12.oauth_token_authentication_scope: the scope used to generate the + OAuth token. If unspecified, + "https://www.googleapis.com/auth/cloud-platform" will be used. NOTE: + oauth_token_authentication_scope can only be set if + oauth_token_authentication_service_account is set. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + oauth_token_authentication_service_account=example-service-account@e\ + xample-project.gserviceaccount.iam.com,\ + oauth_token_authentication_scope=https://www.googleapis.com/auth/\ + cloud-platform + + NOTE: At most one of google_oidc_authentication_service_account or + oauth_token_authentication_service_account can be set. + + 13.output_payload_format_json: indicates that the output payload format + is JSON. NOTE: JSON schema is not supported currently. Any value + specified by this key will be ignored. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + output_payload_format_json= --input-payload-format-json= + + 14.output_payload_format_avro_schema_definition: the schema definition + of the Avro output payload format. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + output_payload_format_avro_schema_definition='{"type": "record", + "name": "my_record", "fields": [{"name": "field1", "type": + "string"}]}' \ + --input-payload-format-avro-schema-definition='{"type": + "record", "name": "my_record", "fields": [{"name": "field1", + "type": "string"}]}' + + 15.output_payload_format_protobuf_schema_definition: the schema + definition of the Protobuf output payload format. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --destinations=http_endpoint_uri='https://example.com',\ + network_attachment=example-network-attachment,\ + output_payload_format_protobuf_schema_definition='syntax = + "proto3"; message Location { string home_address = 1; }' \ + --input-payload-format-protobuf-schema-definition='syntax = + "proto3"; message Location { string home_address = 1; }' + + NOTE: If none of the input_payload_format_json, + input_payload_format_avro_schema_definition, or + input_payload_format_protobuf_schema_definition is set, then the + message data will be treated as an opaque binary and no output format + can be set on the Pipeline through the output_payload_format_json, + output_payload_format_avro_schema_definition, or + output_payload_format_protobuf_schema_definition field. Any Mediations + on the Pipeline that involve access to the data field will fail as + persistent errors. + + --logging-config=LOGGING_CONFIG + The logging config of the pipeline. LOGGING_CONFIG must be one of: + NONE, DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY. + + --mediations=[transformation_template=TRANSFORMATION_TEMPLATE|...] + The different ways to modify the Pipeline. Currently, only one + mediation is supported per pipeline. + + A mediation is specified in a dict format. Currently, the only valid + choice is transformation_template. + + This is the template to apply to transform messages. + + For complex transformations, shell parameter processing may fail to + parse the CEL expressions. Please see gcloud topic flags-file for how + to use https://cloud.google.com/sdk/gcloud/reference/topic/flags-file + feature of gcloud to pass in CEL expressions. + + Examples: + + $ gcloud eventarc pipelines create example-pipeline \ + --mediations=transformation_template='message.removeFields(["dat\ + a.credit_card_number","data.ssn"])' + + At most one of these can be specified: + + --clear-crypto-key + Remove the previously configured crypto key. The channel will + continue to be encrypted using Google-managed keys. + + --crypto-key=CRYPTO_KEY + Fully qualified name of the crypto key to use for customer-managed + encryption. If this is unspecified, Google-managed keys will be used + for encryption. + + At most one of these can be specified: + + --input-payload-format-avro-schema-definition=INPUT_PAYLOAD_FORMAT_AVRO_SCHEMA_DEFINITION + The pipeline's input payload Avro schema definition. If this is set, + then any messages not matching this format will be treated as + persistent errors. + + --input-payload-format-json=INPUT_PAYLOAD_FORMAT_JSON + The pipeline's input payload format is JSON. If this is set, then any + messages not matching this format will be treated as persistent + errors. + + --input-payload-format-protobuf-schema-definition=INPUT_PAYLOAD_FORMAT_PROTOBUF_SCHEMA_DEFINITION + The pipeline's input payload Protobuf schema definition. If this is + set, then any messages not matching this format will be treated as + persistent errors. + + The retry policy configuration for the Pipeline. The pipeline exponentially + backs off if the destination is non-responsive or returns a retryable error + code. The backoff starts with a 1 second delay and doubles the delay after + each failed attempt. The delay is capped at 60 seconds. If the + max-retry-delay and min-retry-delay are set to the same value, then the + duration between retries is constant. + + --max-retry-attempts=MAX_RETRY_ATTEMPTS + The maximum number of retry attempts. If not set, the default value + is 5. + + --max-retry-delay=MAX_RETRY_DELAY + The maximum retry delay in seconds. If not set, the default value + is 60. + + --min-retry-delay=MIN_RETRY_DELAY + The minimum retry delay in seconds. If not set, the default value + is 1. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/memorystore/instances/create b/gcloud/beta/memorystore/instances/create index e226e0f9b..9d264896e 100644 --- a/gcloud/beta/memorystore/instances/create +++ b/gcloud/beta/memorystore/instances/create @@ -4,12 +4,11 @@ NAME SYNOPSIS gcloud beta memorystore instances create (INSTANCE : --location=LOCATION) --psc-auto-connections=[network=NETWORK],[projectId=PROJECTID] - --shard-count=SHARD_COUNT [--async] - [--authorization-mode=AUTHORIZATION_MODE] + [--async] [--authorization-mode=AUTHORIZATION_MODE] [--deletion-protection-enabled] [--engine-configs=[ENGINE_CONFIGS,...]] - [--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]] + [--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]] [--mode=MODE] [--node-type=NODE_TYPE] [--replica-count=REPLICA_COUNT] - [--request-id=REQUEST_ID] + [--request-id=REQUEST_ID] [--shard-count=SHARD_COUNT] [--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE] [--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC --persistence-config-mode=PERSISTENCE_CONFIG_MODE @@ -101,9 +100,6 @@ REQUIRED FLAGS --psc-auto-connections=path_to_file.(yaml|json) - --shard-count=SHARD_COUNT - Number of shards for the instance. - OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to @@ -169,6 +165,14 @@ OPTIONAL FLAGS --labels=path_to_file.(yaml|json) + --mode=MODE + The mode config for the instance. MODE must be one of: + + cluster + Instance is in cluster mode. + standalone + Instance is in standalone mode. + --node-type=NODE_TYPE Machine type for individual nodes of the instance. NODE_TYPE must be one of: @@ -203,6 +207,9 @@ OPTIONAL FLAGS The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). + --shard-count=SHARD_COUNT + Number of shards for the instance. + --transit-encryption-mode=TRANSIT_ENCRYPTION_MODE In-transit encryption mode of the instance. TRANSIT_ENCRYPTION_MODE must be one of: diff --git a/gcloud/beta/network-connectivity/hubs/create b/gcloud/beta/network-connectivity/hubs/create index 3f708b0ec..72064d2d7 100644 --- a/gcloud/beta/network-connectivity/hubs/create +++ b/gcloud/beta/network-connectivity/hubs/create @@ -62,8 +62,8 @@ FLAGS --preset-topology=PRESET_TOPOLOGY Topology of the hub. Only applicable when --policy-mode=PRESET. - PRESET_TOPOLOGY must be one of: mesh, preset-topology-unspecified, - star. + PRESET_TOPOLOGY must be one of: hybrid-inspection, mesh, + preset-topology-unspecified, star. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/network-connectivity/spokes/help b/gcloud/beta/network-connectivity/spokes/help index e9ecab420..76689176b 100644 --- a/gcloud/beta/network-connectivity/spokes/help +++ b/gcloud/beta/network-connectivity/spokes/help @@ -20,6 +20,9 @@ GROUPS linked-interconnect-attachments (BETA) Manage VLAN attachment spokes. + linked-producer-vpc-network + (BETA) Manage Producer VPC spokes. + linked-router-appliances (BETA) Manage Router appliance spokes. diff --git a/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/create b/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/create new file mode 100644 index 000000000..dc01c2752 --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/create @@ -0,0 +1,109 @@ +NAME + gcloud beta network-connectivity spokes linked-producer-vpc-network create + - create a new Producer VPC spoke + +SYNOPSIS + gcloud beta network-connectivity spokes linked-producer-vpc-network create + SPOKE --hub=HUB --network=NETWORK --peering=PEERING [--async] + [--description=DESCRIPTION] [--exclude-export-ranges=[CIDR_RANGE,...]] + [--global] [--include-export-ranges=[CIDR_RANGE,...]] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new Producer VPC spoke. + +EXAMPLES + To create a Producer VPC spoke named myspoke, run: + + $ gcloud beta network-connectivity spokes \ + linked-producer-vpc-network create myspoke \ + --hub="https://www.googleapis.com/networkconnectivity/v1/project\ + s/my-project/locations/global/hubs/my-hub" --global \ + --network="https://www.googleapis.com/compute/v1/projects/my-pro\ + ject/global/networks/my-vpc" --peering="my-peering-name" \ + +POSITIONAL ARGUMENTS + Spoke resource - Name of the spoke to create. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --global on the command line. + + This must be specified. + + SPOKE + ID of the spoke or fully qualified identifier for the spoke. + + To set the spoke attribute: + ▸ provide the argument spoke on the command line. + +REQUIRED FLAGS + --hub=HUB + Hub that the spoke will attach to. The hub must already exist. + + --network=NETWORK + Your VPC network that contains the peering to the Producer VPC, which + this spoke connects to the Hub. The peering must already exist and be + in the ACTIVE state. + + --peering=PEERING + Peering between your network and the Producer VPC, which this spoke + connects to the Hub. The peering must already exist and be in the + ACTIVATE state. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description of the spoke to create. + + --exclude-export-ranges=[CIDR_RANGE,...] + Subnet IP address range(s) to hide from other VPC networks that are + connected through Network Connectivity Center. + + --global + Indicates that the spoke is global. + + --include-export-ranges=[CIDR_RANGE,...] + Subnet IP address range(s) to export to other VPC networks that are + connected through Network Connectivity Center. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity spokes linked-producer-vpc-network \ + create + diff --git a/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/help b/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/help new file mode 100644 index 000000000..0bdc45303 --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/help @@ -0,0 +1,31 @@ +NAME + gcloud beta network-connectivity spokes linked-producer-vpc-network - + manage Producer VPC spokes + +SYNOPSIS + gcloud beta network-connectivity spokes linked-producer-vpc-network COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Producer VPC spokes. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a new Producer VPC spoke. + + update + (BETA) Update a Producer VPC spoke. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity spokes linked-producer-vpc-network + diff --git a/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/update b/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/update new file mode 100644 index 000000000..5d805fc65 --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/update @@ -0,0 +1,106 @@ +NAME + gcloud beta network-connectivity spokes linked-producer-vpc-network update + - update a Producer VPC spoke + +SYNOPSIS + gcloud beta network-connectivity spokes linked-producer-vpc-network update + SPOKE [--async] [--description=DESCRIPTION] [--global] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the details of a Producer VPC spoke. + +EXAMPLES + To update the description of a Producer VPC spoke named my-spoke, run: + + $ gcloud beta network-connectivity spokes \ + linked-producer-vpc-network update myspoke --global \ + --description="new spoke description" + +POSITIONAL ARGUMENTS + Spoke resource - Name of the spoke to update. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --global on the command line. + + This must be specified. + + SPOKE + ID of the spoke or fully qualified identifier for the spoke. + + To set the spoke attribute: + ▸ provide the argument spoke on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + New description of the spoke. + + --global + Indicates that the spoke is global. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta network-connectivity spokes \ + linked-producer-vpc-network update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta network-connectivity spokes \ + linked-producer-vpc-network update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity spokes linked-producer-vpc-network \ + update + diff --git a/gcloud/beta/redis/clusters/add-cluster-endpoints b/gcloud/beta/redis/clusters/add-cluster-endpoints new file mode 100644 index 000000000..4f1b9213e --- /dev/null +++ b/gcloud/beta/redis/clusters/add-cluster-endpoints @@ -0,0 +1,131 @@ +NAME + gcloud beta redis clusters add-cluster-endpoints - add more cluster + endpoints + +SYNOPSIS + gcloud beta redis clusters add-cluster-endpoints + (CLUSTER : --region=REGION) + --cluster-endpoint=[psc-connection=PSC-CONNECTION] [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This is required to enable multi-vpc for Redis cluster. + + To add one cluster endpoint to an existing Redis cluster, two PSC + connections MUST be added as a pair: one for the Redis cluster's discovery + service attachment and the other for the additional service attachment. + + Multiple cluster endpoints COULD be added simultaneously. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The number of connections provided to a cluster endpoint are not in + pairs. + ▪ One of the connections is not found. + +EXAMPLES + To connect redis cluster to one additional VPC, run: + + $ gcloud beta redis clusters add-cluster-endpoints \ + my-redis-cluster add-cluster-endpoints \ + --cluster-endpoint='["psc-connection":[{"psc-connection-id":"$ID\ + ","address":"$IP","network":"projects/$PROJECT/global/networks/$NETW\ + ORK","forwarding-rule":"projects/$PROJECT/regions/us-east1/forwardin\ + gRules/$FR_NAME","service-attachment":"projects/$PROJECT/regions/$RE\ + GION/serviceAttachments/$SA_NAME"},{$ADDITIONAL_PSC_CONNECTION}]]' \ + --cluster_endpoint=$ADDITIONAL_CLUSTER_ENDPOINT \ + $PSCConnectionID SHOULD be extracted from forwarding rules. \ + E.g. 75311697652483351 + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Memorystore Redis + cluster you want to update. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +REQUIRED FLAGS + --cluster-endpoint=[psc-connection=PSC-CONNECTION] + Required, Resource details of a redis cluster endpoint. + + psc-connection + Sets psc-connection value. + + address + Sets address value. + + forwarding-rule + Sets forwarding-rule value. + + network + Sets network value. + + psc-connection-id + Sets psc-connection-id value. + + service-attachment + Sets service-attachment value. + + Shorthand Example: + + --cluster-endpoint='psc-connection=[{"address": "string", "forwarding-rule": "string", "network": "string", "psc-connection-id": "string", "service-attachment": "string"}]' --cluster-endpoint='psc-connection=[{"address": "string", "forwarding-rule": "string", "network": "string", "psc-connection-id": "string", "service-attachment": "string"}]' + + JSON Example: + + --cluster-endpoint='[{"psc-connection": [{"address": "string", "forwarding-rule": "string", "network": "string", "psc-connection-id": "string", "service-attachment": "string"}]}]' + + File Example: + + --cluster-endpoint=path_to_file.(yaml|json) + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud redis clusters add-cluster-endpoints + + $ gcloud alpha redis clusters add-cluster-endpoints + diff --git a/gcloud/beta/redis/clusters/help b/gcloud/beta/redis/clusters/help index f1610caa0..9d7388594 100644 --- a/gcloud/beta/redis/clusters/help +++ b/gcloud/beta/redis/clusters/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add-cluster-endpoints + (BETA) Add more cluster endpoints. + create (BETA) Create a new Memorystore for Redis Cluster instance. @@ -37,6 +40,9 @@ COMMANDS list (BETA) List Memorystore for Redis Cluster instances. + remove-cluster-endpoints + (BETA) Remove existing Memorystore cluster endpoints. + reschedule-maintenance (BETA) Reschedule maintenance window for a Memorystore for Redis Cluster instance. diff --git a/gcloud/beta/redis/clusters/remove-cluster-endpoints b/gcloud/beta/redis/clusters/remove-cluster-endpoints new file mode 100644 index 000000000..25ff679d6 --- /dev/null +++ b/gcloud/beta/redis/clusters/remove-cluster-endpoints @@ -0,0 +1,113 @@ +NAME + gcloud beta redis clusters remove-cluster-endpoints - remove existing + Memorystore cluster endpoints + +SYNOPSIS + gcloud beta redis clusters remove-cluster-endpoints + (CLUSTER : --region=REGION) + --cluster-endpoint=[psc-connection=PSC-CONNECTION] [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) To remove one cluster endpoint from an existing Redis cluster, two + PSC connections MUST be removed as a pair: one to the Redis cluster's + discovery service attachment and the other to its additional service + attachment. + + Multiple cluster endpoints COULD be removed simultaneously. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ Some connections in the to be removed list do not exist. + +EXAMPLES + To remove an endpoint from redis cluster, run: + + $ gcloud beta redis clusters remove-cluster-endpoints \ + my-redis-cluster remove-cluster-endpoints \ + --cluster-endpoint='["psc-connection":[{"psc-connection-id":"$PS\ + C_CONNECTION_ID"},{$ADDITIONAL_PSC_CONNECTION}]]' \ + --cluster_endpoint=$ADDITIONAL_CLUSTER_ENDPOINT \ + $PSCConnectionID SHOULD be extracted from forwarding rules. \ + E.g. 75311697652483351 + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Memorystore Redis + cluster you want to update. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +REQUIRED FLAGS + --cluster-endpoint=[psc-connection=PSC-CONNECTION] + Required, Resource details of a redis cluster endpoint. + + psc-connection + Sets psc-connection value. + + psc-connection-id + Sets psc-connection-id value. + + Shorthand Example: + + --cluster-endpoint='psc-connection=[{"psc-connection-id": "string"}]' --cluster-endpoint='psc-connection=[{"psc-connection-id": "string"}]' + + JSON Example: + + --cluster-endpoint='[{"psc-connection": [{"psc-connection-id": "string"}]}]' + + File Example: + + --cluster-endpoint=path_to_file.(yaml|json) + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud redis clusters remove-cluster-endpoints + + $ gcloud alpha redis clusters remove-cluster-endpoints + diff --git a/gcloud/beta/redis/instances/create b/gcloud/beta/redis/instances/create index 8d4191d88..caef301e3 100644 --- a/gcloud/beta/redis/instances/create +++ b/gcloud/beta/redis/instances/create @@ -163,7 +163,7 @@ FLAGS parameters are: Redis version 3.2 and newer: maxmemory-policy, notify-keyspace-events, - timeout. + timeout, databases. Redis version 4.0 and newer: activedefrag, lfu-decay-time, lfu-log-factor, maxmemory-gb. diff --git a/gcloud/beta/source/repos/update b/gcloud/beta/source/repos/update index dcf9eb13e..09ae6b012 100644 --- a/gcloud/beta/source/repos/update +++ b/gcloud/beta/source/repos/update @@ -13,7 +13,7 @@ EXAMPLES To associate a Cloud Pub/Sub topic to receive repository update notifications, run: - $ gcloud beta source repos update --add-topic=TOPIC_NAME \ + $ gcloud beta source repos update REPO_NAME --add-topic=TOPIC_NAME \ --service-account=SERVICE_ACCOUNT_EMAIL --message-format=json POSITIONAL ARGUMENTS diff --git a/gcloud/beta/workstations/configs/create b/gcloud/beta/workstations/configs/create index d13d6597f..02003fe9b 100644 --- a/gcloud/beta/workstations/configs/create +++ b/gcloud/beta/workstations/configs/create @@ -18,6 +18,7 @@ SYNOPSIS [--disable-tcp-connections] [--enable-audit-agent] [--enable-confidential-compute] [--enable-nested-virtualization] [--enable-ssh-to-vm] [--ephemeral-directory=[PROPERTY=VALUE,...]] + [--grant-workstation-admin-role-on-create] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] @@ -265,6 +266,11 @@ FLAGS --ephemeral-directory=[PROPERTY=VALUE,...] Ephemeral directory which won't persist across workstation sessions. + --grant-workstation-admin-role-on-create + Default value is false. If set, creator of a workstation will get + roles/workstations.policyAdmin role along with roles/workstations.user + role on the workstation created by them. + --idle-timeout=IDLE_TIMEOUT; default=7200 How long (in seconds) to wait before automatically stopping an instance that hasn't received any user traffic. A value of 0 indicates that this diff --git a/gcloud/beta/workstations/configs/update b/gcloud/beta/workstations/configs/update index 559c6629f..fb0d3c040 100644 --- a/gcloud/beta/workstations/configs/update +++ b/gcloud/beta/workstations/configs/update @@ -14,6 +14,7 @@ SYNOPSIS [--container-working-dir=CONTAINER_WORKING_DIR] [--disable-public-ip-addresses] [--enable-audit-agent] [--enable-confidential-compute] [--enable-nested-virtualization] + [--grant-workstation-admin-role-on-create] [--idle-timeout=IDLE_TIMEOUT] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE] [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] @@ -226,6 +227,11 @@ FLAGS Default value is false. If set, instances will have nested virtualization enabled. + --grant-workstation-admin-role-on-create + Default value is false. If set, creator of a workstation will get + roles/workstations.policyAdmin role along with roles/workstations.user + role on the workstation created by them. + --idle-timeout=IDLE_TIMEOUT How long (in seconds) to wait before automatically stopping an instance that hasn't received any user traffic. A value of 0 indicates that this diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index 15eed6408..c5f32e383 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -696,6 +696,10 @@ FLAGS available range with the specified netmask and allocate it to this network interface. + network-attachment + Specifies the network attachment that this interface should connect + to. Mutually exclusive with --network and --subnet flags. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/compute/instance-templates/create-with-container b/gcloud/compute/instance-templates/create-with-container index d85367de2..ed36e4ecf 100644 --- a/gcloud/compute/instance-templates/create-with-container +++ b/gcloud/compute/instance-templates/create-with-container @@ -615,6 +615,10 @@ FLAGS available range with the specified netmask and allocate it to this network interface. + network-attachment + Specifies the network attachment that this interface should connect + to. Mutually exclusive with --network and --subnet flags. + --network-tier=NETWORK_TIER Specifies the network tier that will be used to configure the instance. NETWORK_TIER must be one of: PREMIUM, STANDARD. The default value is diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index e74722295..fe9f2b542 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -793,6 +793,10 @@ FLAGS available range with the specified netmask and allocate it to this network interface. + network-attachment + Specifies the network attachment that this interface should connect + to. Mutually exclusive with --network and --subnet flags. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index 7b3cd0545..d6e0116c2 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -713,6 +713,10 @@ FLAGS available range with the specified netmask and allocate it to this network interface. + network-attachment + Specifies the network attachment that this interface should connect + to. Mutually exclusive with --network and --subnet flags. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/compute/network-endpoint-groups/update b/gcloud/compute/network-endpoint-groups/update index f12239fe0..929314c65 100644 --- a/gcloud/compute/network-endpoint-groups/update +++ b/gcloud/compute/network-endpoint-groups/update @@ -4,9 +4,10 @@ NAME SYNOPSIS gcloud compute network-endpoint-groups update NAME - (--add-endpoint=[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT] + (--add-endpoint=[fqdn=FQDN], + [instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT] | --remove-endpoint=[fqdn=FQDN], - [instance=INSTANCE],[ip=IP],[port=PORT]) + [instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT]) [--global | --region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -37,7 +38,7 @@ REQUIRED FLAGS Exactly one of these must be specified: - --add-endpoint=[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT] + --add-endpoint=[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT] The network endpoint to add to the network endpoint group. Keys used depend on the endpoint type of the NEG. @@ -58,6 +59,10 @@ REQUIRED FLAGS the network that the network endpoint group belongs to is used. + *ipv6* - Optional IPv6 address of the network endpoint. The IPv6 + address must belong to a VM in compute engine (either the internal + or external IPv6 address). + *port* - Required endpoint port unless NEG default port is set. internet-ip-port @@ -107,7 +112,7 @@ REQUIRED FLAGS IP address must be the VM's network interface address. If not specified, the primary NIC address is used. - --remove-endpoint=[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[port=PORT] + --remove-endpoint=[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT] The network endpoint to detach from the network endpoint group. Keys used depend on the endpoint type of the NEG. @@ -120,6 +125,9 @@ REQUIRED FLAGS *ip* - Optional IPv4 address of the network endpoint to detach. If specified port must be provided as well. + *ipv6* - Optional IPv6 address of the network endpoint to detach. + If specified port must be provided as well. + *port* - Optional port of the network endpoint to detach. internet-ip-port diff --git a/gcloud/compute/url-maps/invalidate-cdn-cache b/gcloud/compute/url-maps/invalidate-cdn-cache index e1f997a75..a5716df72 100644 --- a/gcloud/compute/url-maps/invalidate-cdn-cache +++ b/gcloud/compute/url-maps/invalidate-cdn-cache @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud compute url-maps invalidate-cdn-cache URLMAP --path=PATH [--async] - [--host=HOST] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] + [--global] [--host=HOST] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute url-maps invalidate-cdn-cache requests that Cloud CDN stop @@ -44,35 +44,13 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --global + (Default) The URL map is global. Regional URL maps are not supported. + --host=HOST If set, this invalidation will apply only to requests to the specified host. - At most one of these can be specified: - - --global - If set, the URL map is global. - - --region=REGION - Region of the URL map to operate on. If not specified, you might be - prompted to select a region (interactive mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/region property: - - $ gcloud config set compute/region REGION - - A list of regions can be fetched by running: - - $ gcloud compute regions list - - To unset the property, run: - - $ gcloud config unset compute/region - - Alternatively, the region can be stored in the environment variable - CLOUDSDK_COMPUTE_REGION. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/compute/url-maps/list-cdn-cache-invalidations b/gcloud/compute/url-maps/list-cdn-cache-invalidations index cfd419524..61e9d2c30 100644 --- a/gcloud/compute/url-maps/list-cdn-cache-invalidations +++ b/gcloud/compute/url-maps/list-cdn-cache-invalidations @@ -3,8 +3,8 @@ NAME invalidations for a URL map SYNOPSIS - gcloud compute url-maps list-cdn-cache-invalidations URL_MAP - [--limit=LIMIT] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] + gcloud compute url-maps list-cdn-cache-invalidations URL_MAP [--global] + [--limit=LIMIT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION List Cloud CDN cache invalidations for a URL map. A cache invalidation @@ -16,34 +16,12 @@ POSITIONAL ARGUMENTS Name of the URL map to describe. FLAGS + --global + (Default) The URL map is global. Regional URL maps are not supported. + --limit=LIMIT The maximum number of invalidations to list. - At most one of these can be specified: - - --global - If set, the URL map is global. - - --region=REGION - Region of the URL map to describe. If not specified, you might be - prompted to select a region (interactive mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/region property: - - $ gcloud config set compute/region REGION - - A list of regions can be fetched by running: - - $ gcloud compute regions list - - To unset the property, run: - - $ gcloud config unset compute/region - - Alternatively, the region can be stored in the environment variable - CLOUDSDK_COMPUTE_REGION. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index c1224800d..b2af8aa8e 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -217,7 +217,7 @@ FLAGS ADDON must be one of: HttpLoadBalancing, HorizontalPodAutoscaling, KubernetesDashboard, NetworkPolicy, NodeLocalDNS, ConfigConnector, GcePersistentDiskCsiDriver, GcpFilestoreCsiDriver, BackupRestore, - GcsFuseCsiDriver, RayOperator, CloudRun. + GcsFuseCsiDriver, ParallelstoreCsiDriver, RayOperator, CloudRun. --async Return immediately, without waiting for the operation in progress to @@ -1254,6 +1254,11 @@ FLAGS net.ipv4.tcp_rmem Any positive integer tuple net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + kernel.shmmni Must be [4096, 32768] + kernel.shmmax Must be [0, + 18446744073692774399] + kernel.shmall Must be [0, + 18446744073692774399] List of supported hugepage size in 'hugepageConfig'. diff --git a/gcloud/container/fleet/memberships/register b/gcloud/container/fleet/memberships/register index 8729ce75c..d2b89d7e2 100644 --- a/gcloud/container/fleet/memberships/register +++ b/gcloud/container/fleet/memberships/register @@ -52,7 +52,8 @@ DESCRIPTION Rerunning this command against the same cluster with the same MEMBERSHIP_NAME and target fleet is successful, and will upgrade the Connect agent if it is supposed to be installed and a newer version is - avaible. + available. Rerunning with --enable-workload-identity ensures that Workload + Identity is enabled on the cluster. EXAMPLES Register a non-GKE cluster referenced from a specific kubeconfig file, and diff --git a/gcloud/container/hub/memberships/register b/gcloud/container/hub/memberships/register index 2acbe1683..1e16f9e59 100644 --- a/gcloud/container/hub/memberships/register +++ b/gcloud/container/hub/memberships/register @@ -51,7 +51,8 @@ DESCRIPTION Rerunning this command against the same cluster with the same MEMBERSHIP_NAME and target fleet is successful, and will upgrade the Connect agent if it is supposed to be installed and a newer version is - avaible. + available. Rerunning with --enable-workload-identity ensures that Workload + Identity is enabled on the cluster. EXAMPLES Register a non-GKE cluster referenced from a specific kubeconfig file, and diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index 929573550..5b8030cd8 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -702,6 +702,11 @@ FLAGS net.ipv4.tcp_rmem Any positive integer tuple net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + kernel.shmmni Must be [4096, 32768] + kernel.shmmax Must be [0, + 18446744073692774399] + kernel.shmall Must be [0, + 18446744073692774399] List of supported hugepage size in 'hugepageConfig'. diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index 07679b341..fbd9ff256 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -307,6 +307,11 @@ REQUIRED FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + kernel.shmmni Must be [4096, 32768] + kernel.shmmax Must be [0, + 18446744073692774399] + kernel.shmall Must be [0, + 18446744073692774399] List of supported hugepage size in 'hugepageConfig'. diff --git a/gcloud/dataproc/clusters/create b/gcloud/dataproc/clusters/create index 2dd63be6d..b749dc55c 100644 --- a/gcloud/dataproc/clusters/create +++ b/gcloud/dataproc/clusters/create @@ -18,6 +18,8 @@ SYNOPSIS [--initialization-actions=CLOUD_STORAGE_URI,[...]] [--labels=[KEY=VALUE,...]] [--master-accelerator=[type=TYPE,[count=COUNT],...]] + [--master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS] + [--master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--master-boot-disk-size=MASTER_BOOT_DISK_SIZE] [--master-boot-disk-type=MASTER_BOOT_DISK_TYPE] [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] @@ -44,6 +46,8 @@ SYNOPSIS [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] + [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] [--worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE] @@ -242,6 +246,22 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the disk. This sets the limit for disk I/O operations per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + + --master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) to + provision for the disk. This sets the limit for throughput in MiB per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + --master-boot-disk-size=MASTER_BOOT_DISK_SIZE The size of the boot 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 @@ -438,6 +458,22 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the disk. This sets the limit for disk I/O operations per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + + --worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) to + provision for the disk. This sets the limit for throughput in MiB per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + --worker-boot-disk-size=WORKER_BOOT_DISK_SIZE The size of the boot 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 diff --git a/gcloud/dataproc/workflow-templates/set-managed-cluster b/gcloud/dataproc/workflow-templates/set-managed-cluster index a93a5319f..5ab3baa94 100644 --- a/gcloud/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/dataproc/workflow-templates/set-managed-cluster @@ -12,6 +12,8 @@ SYNOPSIS [--initialization-actions=CLOUD_STORAGE_URI,[...]] [--labels=[KEY=VALUE,...]] [--master-accelerator=[type=TYPE,[count=COUNT],...]] + [--master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS] + [--master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--master-boot-disk-size=MASTER_BOOT_DISK_SIZE] [--master-boot-disk-type=MASTER_BOOT_DISK_TYPE] [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] @@ -37,6 +39,8 @@ SYNOPSIS [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] + [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] [--worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE] @@ -172,6 +176,22 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the disk. This sets the limit for disk I/O operations per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + + --master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) to + provision for the disk. This sets the limit for throughput in MiB per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + --master-boot-disk-size=MASTER_BOOT_DISK_SIZE The size of the boot 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 @@ -360,6 +380,22 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the disk. This sets the limit for disk I/O operations per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + + --worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) to + provision for the disk. This sets the limit for throughput in MiB per + second. This is only supported if the bootdisk type is + hyperdisk-balanced + (https://cloud.google.com/compute/docs/disks/hyperdisks). + --worker-boot-disk-size=WORKER_BOOT_DISK_SIZE The size of the boot 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 diff --git a/gcloud/network-connectivity/service-connection-policies/create b/gcloud/network-connectivity/service-connection-policies/create index e923e1f38..57afa2ec9 100644 --- a/gcloud/network-connectivity/service-connection-policies/create +++ b/gcloud/network-connectivity/service-connection-policies/create @@ -6,8 +6,11 @@ SYNOPSIS gcloud network-connectivity service-connection-policies create SERVICE_CONNECTION_POLICY --network=NETWORK --service-class=SERVICE_CLASS - (--subnets=[SUBNETS,...] : --psc-connection-limit=PSC_CONNECTION_LIMIT) - [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + (--subnets=[SUBNETS,...] + : --allowed-google-producers-resource-hierarchy-level=[ALLOWED_GOOGLE_PRODUCERS_RESOURCE_HIERARCHY_LEVEL, + ...] --producer-instance-location=PRODUCER_INSTANCE_LOCATION + --psc-connection-limit=PSC_CONNECTION_LIMIT) [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -16,12 +19,20 @@ DESCRIPTION EXAMPLES Create a Service Connection Policy with name my-service-conn-policy for network projects/my-project/global/networks/net1 and service class - my-service-class-ad32fa4b in region us-central1. + my-service-class-ad32fa4b in region us-central1 using subnet + projects/my-project/regions/us-central1/subnetworks/subnet1 subject to + custom-resource-hierarchy-levels that allows connections from + Google-managed producer instances in projects/my-project. $ gcloud network-connectivity service-connection-policies create \ my-service-conn-policy \ --network="projects/my-project/global/networks/net1" \ - --service-class=my-service-class-ad32fa4b --region=us-central1 + --service-class=my-service-class-ad32fa4b --region=us-central1 \ + --subnets=projects/my-project/regions/us-central1/subnetworks/\ + subnet1 --psc-connection-limit=100 \ + --producer-instance-location=custom-resource-hierarchy-levels \ + --allowed-google-producers-resource-hierarchy-level=projects/\ + my-project POSITIONAL ARGUMENTS Service connection policy resource - Name of the Service Connection Policy @@ -99,6 +110,24 @@ REQUIRED FLAGS To set the subnetwork attribute: ▫ provide the argument --subnets on the command line. + --allowed-google-producers-resource-hierarchy-level=[ALLOWED_GOOGLE_PRODUCERS_RESOURCE_HIERARCHY_LEVEL,...] + List of projects, folders, or orgs where the producer instance can be + located in the form "projects/123456789", folders/123456789", or + "organizations/123456789". + + --producer-instance-location=PRODUCER_INSTANCE_LOCATION + Option that determines where the producer instances can be located + for which connections can be created in the network controlled by + this policy. PRODUCER_INSTANCE_LOCATION must be one of: + + custom-resource-hierarchy-levels + The producer instance must be located in one of the values + provided in the allowed-google-producers-resource-hierarchy-level + flag. + none + The producer instance must be within the same project as this + connection policy. + --psc-connection-limit=PSC_CONNECTION_LIMIT Max number of PSC connections for this policy. diff --git a/gcloud/network-connectivity/spokes/linked-producer-vpc-network/create b/gcloud/network-connectivity/spokes/linked-producer-vpc-network/create index 1ab55a2fb..8d983fb10 100644 --- a/gcloud/network-connectivity/spokes/linked-producer-vpc-network/create +++ b/gcloud/network-connectivity/spokes/linked-producer-vpc-network/create @@ -6,7 +6,8 @@ SYNOPSIS gcloud network-connectivity spokes linked-producer-vpc-network create SPOKE --hub=HUB --network=NETWORK --peering=PEERING [--async] [--description=DESCRIPTION] [--exclude-export-ranges=[CIDR_RANGE,...]] - [--global] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--global] [--include-export-ranges=[CIDR_RANGE,...]] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a new Producer VPC spoke. @@ -74,6 +75,10 @@ OPTIONAL FLAGS --global Indicates that the spoke is global. + --include-export-ranges=[CIDR_RANGE,...] + Subnet IP address range(s) to export to other VPC networks that are + connected through Network Connectivity Center. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. @@ -94,3 +99,10 @@ API REFERENCE This command uses the networkconnectivity/v1 API. The full documentation for this API can be found at: https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity spokes \ + linked-producer-vpc-network create + diff --git a/gcloud/network-connectivity/spokes/linked-producer-vpc-network/help b/gcloud/network-connectivity/spokes/linked-producer-vpc-network/help index 35a0add2b..a3301aacf 100644 --- a/gcloud/network-connectivity/spokes/linked-producer-vpc-network/help +++ b/gcloud/network-connectivity/spokes/linked-producer-vpc-network/help @@ -22,3 +22,9 @@ COMMANDS update Update a Producer VPC spoke. + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity spokes linked-producer-vpc-network + diff --git a/gcloud/network-connectivity/spokes/linked-producer-vpc-network/update b/gcloud/network-connectivity/spokes/linked-producer-vpc-network/update index 2d862c50e..1abb92c72 100644 --- a/gcloud/network-connectivity/spokes/linked-producer-vpc-network/update +++ b/gcloud/network-connectivity/spokes/linked-producer-vpc-network/update @@ -94,3 +94,10 @@ API REFERENCE This command uses the networkconnectivity/v1 API. The full documentation for this API can be found at: https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity spokes \ + linked-producer-vpc-network update + diff --git a/gcloud/recaptcha/keys/add-ip-override b/gcloud/recaptcha/keys/add-ip-override new file mode 100644 index 000000000..3010283ab --- /dev/null +++ b/gcloud/recaptcha/keys/add-ip-override @@ -0,0 +1,59 @@ +NAME + gcloud recaptcha keys add-ip-override - add an IP override to a key + +SYNOPSIS + gcloud recaptcha keys add-ip-override KEY --ip=IP --override=OVERRIDE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Add an IP override to a key. + +EXAMPLES + $ gcloud recaptcha keys add-ip-override test-key --ip=1.2.3.4 \ + --override=allow + +POSITIONAL ARGUMENTS + Key resource - The reCAPTCHA key to add the IP override to. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument key 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. + + KEY + ID of the key or fully qualified identifier for the key. + + To set the key attribute: + ▸ provide the argument key on the command line. + +REQUIRED FLAGS + --ip=IP + IP address to override for the key. + + --override=OVERRIDE + If set to allow, the IP address/CIDR range will be allowlisted for the + key. OVERRIDE must be one of: allow, override-type-unspecified. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the recaptchaenterprise/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/recaptcha-enterprise/ + +NOTES + This variant is also available: + + $ gcloud alpha recaptcha keys add-ip-override + diff --git a/gcloud/recaptcha/keys/help b/gcloud/recaptcha/keys/help index 412853741..fb60f9ede 100644 --- a/gcloud/recaptcha/keys/help +++ b/gcloud/recaptcha/keys/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add-ip-override + Add an IP override to a key. + create Create a Key. @@ -30,6 +33,9 @@ COMMANDS migrate Migrate a key to reCAPTCHA Enterprise. + remove-ip-override + Remove an IP override from a key. + update Update a Key. diff --git a/gcloud/recaptcha/keys/remove-ip-override b/gcloud/recaptcha/keys/remove-ip-override new file mode 100644 index 000000000..d1c912b01 --- /dev/null +++ b/gcloud/recaptcha/keys/remove-ip-override @@ -0,0 +1,60 @@ +NAME + gcloud recaptcha keys remove-ip-override - remove an IP override from a key + +SYNOPSIS + gcloud recaptcha keys remove-ip-override KEY --ip=IP --override=OVERRIDE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Remove an IP override from a key. + +EXAMPLES + $ gcloud recaptcha keys remove-ip-override test-key --ip=1.2.3.4 \ + --override=allow + +POSITIONAL ARGUMENTS + Key resource - The reCAPTCHA key from which to remove the IP override. + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument key 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. + + KEY + ID of the key or fully qualified identifier for the key. + + To set the key attribute: + ▸ provide the argument key on the command line. + +REQUIRED FLAGS + --ip=IP + IP address to override for the key. + + --override=OVERRIDE + If set to allow, the IP address/CIDR range will be removed from the + allowlisted IPs. OVERRIDE must be one of: allow, + override-type-unspecified. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the recaptchaenterprise/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/recaptcha-enterprise/ + +NOTES + This variant is also available: + + $ gcloud alpha recaptcha keys remove-ip-override + diff --git a/gcloud/redis/clusters/add-cluster-endpoints b/gcloud/redis/clusters/add-cluster-endpoints new file mode 100644 index 000000000..d2aecf481 --- /dev/null +++ b/gcloud/redis/clusters/add-cluster-endpoints @@ -0,0 +1,128 @@ +NAME + gcloud redis clusters add-cluster-endpoints - add more cluster endpoints + +SYNOPSIS + gcloud redis clusters add-cluster-endpoints (CLUSTER : --region=REGION) + --cluster-endpoint=[psc-connection=PSC-CONNECTION] [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This is required to enable multi-vpc for Redis cluster. + + To add one cluster endpoint to an existing Redis cluster, two PSC + connections MUST be added as a pair: one for the Redis cluster's discovery + service attachment and the other for the additional service attachment. + + Multiple cluster endpoints COULD be added simultaneously. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The number of connections provided to a cluster endpoint are not in + pairs. + ▪ One of the connections is not found. + +EXAMPLES + To connect redis cluster to one additional VPC, run: + + $ gcloud redis clusters add-cluster-endpoints my-redis-cluster \ + add-cluster-endpoints \ + --cluster-endpoint='["psc-connection":[{"psc-connection-id":"$ID\ + ","address":"$IP","network":"projects/$PROJECT/global/networks/$NETW\ + ORK","forwarding-rule":"projects/$PROJECT/regions/us-east1/forwardin\ + gRules/$FR_NAME","service-attachment":"projects/$PROJECT/regions/$RE\ + GION/serviceAttachments/$SA_NAME"},{$ADDITIONAL_PSC_CONNECTION}]]' \ + --cluster_endpoint=$ADDITIONAL_CLUSTER_ENDPOINT \ + $PSCConnectionID SHOULD be extracted from forwarding rules. \ + E.g. 75311697652483351 + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Memorystore Redis + cluster you want to update. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +REQUIRED FLAGS + --cluster-endpoint=[psc-connection=PSC-CONNECTION] + Required, Resource details of a redis cluster endpoint. + + psc-connection + Sets psc-connection value. + + address + Sets address value. + + forwarding-rule + Sets forwarding-rule value. + + network + Sets network value. + + psc-connection-id + Sets psc-connection-id value. + + service-attachment + Sets service-attachment value. + + Shorthand Example: + + --cluster-endpoint='psc-connection=[{"address": "string", "forwarding-rule": "string", "network": "string", "psc-connection-id": "string", "service-attachment": "string"}]' --cluster-endpoint='psc-connection=[{"address": "string", "forwarding-rule": "string", "network": "string", "psc-connection-id": "string", "service-attachment": "string"}]' + + JSON Example: + + --cluster-endpoint='[{"psc-connection": [{"address": "string", "forwarding-rule": "string", "network": "string", "psc-connection-id": "string", "service-attachment": "string"}]}]' + + File Example: + + --cluster-endpoint=path_to_file.(yaml|json) + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + These variants are also available: + + $ gcloud alpha redis clusters add-cluster-endpoints + + $ gcloud beta redis clusters add-cluster-endpoints + diff --git a/gcloud/redis/clusters/help b/gcloud/redis/clusters/help index ed0bb6c42..db1e54d7d 100644 --- a/gcloud/redis/clusters/help +++ b/gcloud/redis/clusters/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add-cluster-endpoints + Add more cluster endpoints. + create Create a new Memorystore for Redis Cluster instance. @@ -37,6 +40,9 @@ COMMANDS list List Memorystore for Redis Cluster instances. + remove-cluster-endpoints + Remove existing Memorystore cluster endpoints. + reschedule-maintenance Reschedule maintenance window for a Memorystore for Redis Cluster instance. diff --git a/gcloud/redis/clusters/remove-cluster-endpoints b/gcloud/redis/clusters/remove-cluster-endpoints new file mode 100644 index 000000000..b5634debd --- /dev/null +++ b/gcloud/redis/clusters/remove-cluster-endpoints @@ -0,0 +1,110 @@ +NAME + gcloud redis clusters remove-cluster-endpoints - remove existing + Memorystore cluster endpoints + +SYNOPSIS + gcloud redis clusters remove-cluster-endpoints (CLUSTER : --region=REGION) + --cluster-endpoint=[psc-connection=PSC-CONNECTION] [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + To remove one cluster endpoint from an existing Redis cluster, two PSC + connections MUST be removed as a pair: one to the Redis cluster's discovery + service attachment and the other to its additional service attachment. + + Multiple cluster endpoints COULD be removed simultaneously. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ Some connections in the to be removed list do not exist. + +EXAMPLES + To remove an endpoint from redis cluster, run: + + $ gcloud redis clusters remove-cluster-endpoints my-redis-cluster \ + remove-cluster-endpoints \ + --cluster-endpoint='["psc-connection":[{"psc-connection-id":"$PS\ + C_CONNECTION_ID"},{$ADDITIONAL_PSC_CONNECTION}]]' \ + --cluster_endpoint=$ADDITIONAL_CLUSTER_ENDPOINT \ + $PSCConnectionID SHOULD be extracted from forwarding rules. \ + E.g. 75311697652483351 + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Memorystore Redis + cluster you want to update. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +REQUIRED FLAGS + --cluster-endpoint=[psc-connection=PSC-CONNECTION] + Required, Resource details of a redis cluster endpoint. + + psc-connection + Sets psc-connection value. + + psc-connection-id + Sets psc-connection-id value. + + Shorthand Example: + + --cluster-endpoint='psc-connection=[{"psc-connection-id": "string"}]' --cluster-endpoint='psc-connection=[{"psc-connection-id": "string"}]' + + JSON Example: + + --cluster-endpoint='[{"psc-connection": [{"psc-connection-id": "string"}]}]' + + File Example: + + --cluster-endpoint=path_to_file.(yaml|json) + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + These variants are also available: + + $ gcloud alpha redis clusters remove-cluster-endpoints + + $ gcloud beta redis clusters remove-cluster-endpoints + diff --git a/gcloud/redis/instances/create b/gcloud/redis/instances/create index 7837c4ab0..9b366f4e0 100644 --- a/gcloud/redis/instances/create +++ b/gcloud/redis/instances/create @@ -163,7 +163,7 @@ FLAGS parameters are: Redis version 3.2 and newer: maxmemory-policy, notify-keyspace-events, - timeout. + timeout, databases. Redis version 4.0 and newer: activedefrag, lfu-decay-time, lfu-log-factor, maxmemory-gb. diff --git a/gcloud/source/repos/update b/gcloud/source/repos/update index dc877eb1b..ed8be2bb3 100644 --- a/gcloud/source/repos/update +++ b/gcloud/source/repos/update @@ -13,7 +13,7 @@ EXAMPLES To associate a Cloud Pub/Sub topic to receive repository update notifications, run: - $ gcloud source repos update --add-topic=TOPIC_NAME \ + $ gcloud source repos update REPO_NAME --add-topic=TOPIC_NAME \ --service-account=SERVICE_ACCOUNT_EMAIL --message-format=json POSITIONAL ARGUMENTS diff --git a/gcloud/workstations/configs/create b/gcloud/workstations/configs/create index 5c4cea146..d72c8fa5e 100644 --- a/gcloud/workstations/configs/create +++ b/gcloud/workstations/configs/create @@ -15,6 +15,7 @@ SYNOPSIS [--disable-tcp-connections] [--enable-audit-agent] [--enable-confidential-compute] [--enable-nested-virtualization] [--enable-ssh-to-vm] [--ephemeral-directory=[PROPERTY=VALUE,...]] + [--grant-workstation-admin-role-on-create] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] @@ -204,6 +205,11 @@ FLAGS --ephemeral-directory=[PROPERTY=VALUE,...] Ephemeral directory which won't persist across workstation sessions. + --grant-workstation-admin-role-on-create + Default value is false. If set, creator of a workstation will get + roles/workstations.policyAdmin role along with roles/workstations.user + role on the workstation created by them. + --idle-timeout=IDLE_TIMEOUT; default=7200 How long (in seconds) to wait before automatically stopping an instance that hasn't received any user traffic. A value of 0 indicates that this diff --git a/gcloud/workstations/configs/update b/gcloud/workstations/configs/update index 488174fcb..4f522bb5d 100644 --- a/gcloud/workstations/configs/update +++ b/gcloud/workstations/configs/update @@ -13,6 +13,7 @@ SYNOPSIS [--container-working-dir=CONTAINER_WORKING_DIR] [--disable-public-ip-addresses] [--enable-audit-agent] [--enable-confidential-compute] [--enable-nested-virtualization] + [--grant-workstation-admin-role-on-create] [--idle-timeout=IDLE_TIMEOUT] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE] [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] @@ -174,6 +175,11 @@ FLAGS Default value is false. If set, instances will have nested virtualization enabled. + --grant-workstation-admin-role-on-create + Default value is false. If set, creator of a workstation will get + roles/workstations.policyAdmin role along with roles/workstations.user + role on the workstation created by them. + --idle-timeout=IDLE_TIMEOUT How long (in seconds) to wait before automatically stopping an instance that hasn't received any user traffic. A value of 0 indicates that this