From 6d07e70b12aa811ae8ff1f7fdb30ae56b7347aff Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 10 Dec 2025 10:54:29 +0000 Subject: [PATCH] gcloud: Wed Dec 10 10:54:29 UTC 2025 --- gcloud/_version | 8 +- gcloud/ai/endpoints/deploy-model | 15 +- gcloud/ai/index-endpoints/deploy-index | 9 +- gcloud/alloydb/instances/create | 6 +- gcloud/alloydb/instances/update | 6 +- gcloud/alpha/ai/endpoints/deploy-model | 8 +- gcloud/alpha/ai/index-endpoints/deploy-index | 9 +- gcloud/alpha/alloydb/instances/create | 6 +- gcloud/alpha/alloydb/instances/update | 6 +- gcloud/alpha/api-registry/help | 28 + gcloud/alpha/api-registry/mcp/disable | 30 ++ gcloud/alpha/api-registry/mcp/enable | 30 ++ gcloud/alpha/api-registry/mcp/help | 41 ++ gcloud/alpha/api-registry/mcp/servers/help | 29 + gcloud/alpha/api-registry/mcp/servers/list | 69 +++ gcloud/alpha/api-registry/mcp/tools/help | 28 + gcloud/alpha/api-registry/mcp/tools/list | 69 +++ gcloud/alpha/apphub/boundary/describe | 46 ++ gcloud/alpha/apphub/boundary/help | 31 ++ gcloud/alpha/apphub/boundary/update | 57 ++ gcloud/alpha/apphub/help | 3 + gcloud/alpha/beyondcorp/help | 4 +- .../alpha/biglake/iceberg/catalogs/failover | 63 +++ gcloud/alpha/biglake/iceberg/catalogs/help | 3 + .../blockchain-validator-configs/create | 52 +- .../blockchain-validator-configs/update | 104 ++-- .../cloud-locations/describe | 3 +- gcloud/alpha/compute/commitments/create | 7 +- gcloud/alpha/compute/reservations/help | 3 + .../alpha/compute/reservations/slots/describe | 70 +++ gcloud/alpha/compute/reservations/slots/help | 30 ++ gcloud/alpha/compute/reservations/slots/list | 109 ++++ .../backup-restore/restore-plans/create | 6 +- .../backup-restore/restore-plans/update | 6 +- .../clusters/complete-control-plane-upgrade | 56 ++ gcloud/alpha/container/clusters/help | 3 + gcloud/alpha/container/clusters/upgrade | 12 +- .../spaces/application-templates/create | 48 +- .../spaces/application-templates/update | 162 +++++- .../design-center/spaces/applications/help | 3 + .../spaces/applications/register | 114 ++++ gcloud/alpha/design-center/spaces/help | 3 + .../spaces/register-deployed-resources | 109 ++++ .../developer-connect/connections/create | 284 ++++++++-- .../developer-connect/connections/update | 208 +++++-- gcloud/alpha/firebase-data-connect/help | 22 + gcloud/alpha/lustre/instances/create | 4 +- gcloud/alpha/lustre/instances/update | 4 +- gcloud/alpha/managed-kafka/clusters/describe | 10 +- .../managed-kafka/connect-clusters/create | 11 +- .../managed-kafka/connect-clusters/update | 13 +- gcloud/alpha/managed-kafka/connectors/create | 8 +- gcloud/alpha/managed-kafka/connectors/update | 8 +- gcloud/alpha/model-armor/floorsettings/update | 17 +- .../monitoring/policies/conditions/create | 6 +- .../monitoring/policies/conditions/delete | 6 +- .../monitoring/policies/conditions/describe | 6 +- .../alpha/monitoring/policies/conditions/help | 6 +- .../monitoring/policies/conditions/update | 6 +- gcloud/alpha/monitoring/policies/create | 6 +- gcloud/alpha/monitoring/policies/delete | 6 +- gcloud/alpha/monitoring/policies/describe | 6 +- gcloud/alpha/monitoring/policies/help | 6 +- gcloud/alpha/monitoring/policies/list | 6 +- gcloud/alpha/monitoring/policies/migrate | 6 +- gcloud/alpha/monitoring/policies/update | 6 +- gcloud/alpha/netapp/volumes/create | 28 +- gcloud/alpha/netapp/volumes/update | 32 +- .../dns-threat-detectors/create | 9 +- .../dns-threat-detectors/describe | 2 +- .../dns-threat-detectors/list | 4 +- .../dns-threat-detectors/update | 8 +- .../resource-manager/capabilities/describe | 45 ++ .../alpha/resource-manager/capabilities/help | 34 ++ .../resource-manager/capabilities/update | 62 +++ gcloud/alpha/resource-manager/help | 3 + gcloud/alpha/run/deploy | 9 +- gcloud/alpha/run/multi-region-services/update | 9 +- gcloud/alpha/services/disable | 4 +- gcloud/alpha/services/enable | 6 +- .../alpha/services/mcp/content-security/add | 4 +- .../alpha/services/mcp/content-security/get | 4 +- .../alpha/services/mcp/content-security/help | 4 +- .../services/mcp/content-security/remove | 4 +- gcloud/alpha/services/mcp/disable | 4 +- gcloud/alpha/services/mcp/enable | 9 +- gcloud/alpha/services/mcp/help | 4 +- gcloud/alpha/services/mcp/list | 4 +- gcloud/alpha/sql/instances/create | 26 + gcloud/alpha/sql/instances/patch | 31 +- gcloud/alpha/sql/ssl/entraid-certs/create | 36 ++ gcloud/alpha/sql/ssl/entraid-certs/help | 42 ++ gcloud/alpha/sql/ssl/entraid-certs/list | 64 +++ gcloud/alpha/sql/ssl/entraid-certs/rollback | 37 ++ gcloud/alpha/sql/ssl/entraid-certs/rotate | 37 ++ gcloud/alpha/sql/ssl/help | 4 + gcloud/alpha/workstations/configs/create | 64 ++- gcloud/alpha/workstations/configs/update | 29 +- gcloud/apphub/boundary/describe | 42 ++ gcloud/apphub/boundary/help | 28 + gcloud/apphub/boundary/update | 54 ++ gcloud/apphub/help | 3 + gcloud/beta/ai/endpoints/deploy-model | 8 +- gcloud/beta/ai/index-endpoints/deploy-index | 9 +- gcloud/beta/alloydb/instances/create | 6 +- gcloud/beta/alloydb/instances/update | 6 +- gcloud/beta/api-registry/help | 26 + gcloud/beta/api-registry/mcp/disable | 28 + .../help => api-registry/mcp/enable} | 16 +- gcloud/beta/api-registry/mcp/help | 39 ++ gcloud/beta/api-registry/mcp/servers/help | 27 + gcloud/beta/api-registry/mcp/servers/list | 67 +++ gcloud/beta/api-registry/mcp/tools/help | 26 + gcloud/beta/api-registry/mcp/tools/list | 67 +++ gcloud/beta/beyondcorp/help | 9 +- .../security-gateways/applications/create | 74 +-- .../security-gateways/applications/delete | 5 +- .../security-gateways/applications/describe | 5 +- .../applications/get-iam-policy | 13 +- .../security-gateways/applications/help | 5 +- .../security-gateways/applications/list | 5 +- .../applications/set-iam-policy | 13 +- .../security-gateways/applications/update | 137 ++--- .../beta/beyondcorp/security-gateways/create | 30 +- .../beta/beyondcorp/security-gateways/delete | 5 +- .../beyondcorp/security-gateways/describe | 5 +- .../security-gateways/get-iam-policy | 5 +- gcloud/beta/beyondcorp/security-gateways/help | 5 +- gcloud/beta/beyondcorp/security-gateways/list | 5 +- .../security-gateways/set-iam-policy | 5 +- .../beta/beyondcorp/security-gateways/update | 37 +- gcloud/beta/composer/environments/create | 4 +- gcloud/beta/composer/environments/update | 4 +- .../backup-restore/restore-plans/create | 6 +- .../backup-restore/restore-plans/update | 6 +- .../clusters/complete-control-plane-upgrade | 54 ++ gcloud/beta/container/clusters/help | 3 + gcloud/beta/container/clusters/upgrade | 12 +- gcloud/beta/datastream/streams/create | 50 +- gcloud/beta/datastream/streams/update | 48 +- .../beta/developer-connect/connections/create | 284 ++++++++-- .../beta/developer-connect/connections/update | 208 +++++-- gcloud/beta/filestore/instances/help | 6 + gcloud/beta/filestore/instances/pause-replica | 78 +++ .../beta/filestore/instances/resume-replica | 78 +++ gcloud/beta/firebase-data-connect/help | 20 + gcloud/beta/iam/access-policies/create | 67 ++- gcloud/beta/iam/access-policies/update | 170 +++--- gcloud/beta/iam/policy-bindings/create | 6 +- gcloud/beta/managed-kafka/clusters/describe | 7 +- .../managed-kafka/connect-clusters/create | 11 +- .../managed-kafka/connect-clusters/update | 13 +- gcloud/beta/managed-kafka/connectors/create | 8 +- gcloud/beta/managed-kafka/connectors/update | 8 +- gcloud/beta/model-armor/floorsettings/update | 17 +- gcloud/beta/monitoring/help | 3 + .../monitoring/policies/conditions/create | 96 ++++ .../monitoring/policies/conditions/delete | 60 +++ .../monitoring/policies/conditions/describe | 58 ++ .../beta/monitoring/policies/conditions/help | 41 ++ .../monitoring/policies/conditions/update | 79 +++ gcloud/beta/monitoring/policies/create | 171 ++++++ gcloud/beta/monitoring/policies/delete | 49 ++ gcloud/beta/monitoring/policies/describe | 48 ++ gcloud/beta/monitoring/policies/help | 52 ++ gcloud/beta/monitoring/policies/list | 87 +++ gcloud/beta/monitoring/policies/migrate | 45 ++ gcloud/beta/monitoring/policies/update | 183 +++++++ gcloud/beta/netapp/backup-vaults/create | 28 +- gcloud/beta/netapp/volumes/create | 28 +- gcloud/beta/netapp/volumes/update | 32 +- .../dns-threat-detectors/create | 9 +- .../dns-threat-detectors/describe | 2 +- .../dns-threat-detectors/list | 4 +- .../dns-threat-detectors/update | 8 +- .../resource-manager/capabilities/describe | 43 ++ .../beta/resource-manager/capabilities/help | 32 ++ .../beta/resource-manager/capabilities/update | 60 +++ gcloud/beta/resource-manager/help | 3 + gcloud/beta/run/deploy | 33 +- gcloud/beta/run/jobs/create | 24 +- gcloud/beta/run/jobs/deploy | 24 +- gcloud/beta/run/jobs/update | 24 +- gcloud/beta/run/multi-region-services/update | 9 +- gcloud/beta/run/services/update | 24 +- gcloud/beta/run/worker-pools/deploy | 24 +- gcloud/beta/run/worker-pools/update | 24 +- gcloud/beta/services/disable | 4 +- gcloud/beta/services/enable | 6 +- gcloud/beta/services/help | 3 + gcloud/beta/services/mcp/content-security/add | 40 ++ gcloud/beta/services/mcp/content-security/get | 33 ++ .../beta/services/mcp/content-security/help | 33 ++ .../beta/services/mcp/content-security/remove | 40 ++ gcloud/beta/services/mcp/disable | 80 +++ gcloud/beta/services/mcp/enable | 79 +++ gcloud/beta/services/mcp/help | 38 ++ gcloud/beta/services/mcp/list | 95 ++++ gcloud/beta/sql/instances/create | 26 + gcloud/beta/sql/instances/patch | 31 +- gcloud/beta/sql/ssl/entraid-certs/create | 34 ++ gcloud/beta/sql/ssl/entraid-certs/help | 40 ++ gcloud/beta/sql/ssl/entraid-certs/list | 62 +++ gcloud/beta/sql/ssl/entraid-certs/rollback | 35 ++ gcloud/beta/sql/ssl/entraid-certs/rotate | 35 ++ gcloud/beta/sql/ssl/help | 4 + gcloud/beta/workstations/configs/create | 64 ++- gcloud/beta/workstations/configs/update | 29 +- gcloud/beyondcorp/help | 30 ++ gcloud/beyondcorp/operations/describe | 57 ++ gcloud/beyondcorp/operations/help | 22 + gcloud/beyondcorp/operations/list | 78 +++ .../security-gateways/applications/create | 226 ++++++++ .../security-gateways/applications/delete | 100 ++++ .../security-gateways/applications/describe | 77 +++ .../applications/get-iam-policy | 106 ++++ .../security-gateways/applications/help | 45 ++ .../security-gateways/applications/list | 101 ++++ .../applications/set-iam-policy | 86 +++ .../security-gateways/applications/update | 509 ++++++++++++++++++ gcloud/beyondcorp/security-gateways/create | 218 ++++++++ gcloud/beyondcorp/security-gateways/delete | 91 ++++ gcloud/beyondcorp/security-gateways/describe | 67 +++ .../security-gateways/get-iam-policy | 96 ++++ gcloud/beyondcorp/security-gateways/help | 49 ++ gcloud/beyondcorp/security-gateways/list | 85 +++ .../security-gateways/set-iam-policy | 77 +++ gcloud/beyondcorp/security-gateways/update | 359 ++++++++++++ gcloud/composer/environments/create | 4 +- gcloud/composer/environments/update | 4 +- .../attachments/dedicated/create | 24 + .../attachments/dedicated/update | 15 +- .../interconnects/attachments/partner/create | 24 + .../interconnects/attachments/partner/update | 12 + gcloud/container/ai/profiles/benchmarks/list | 22 +- gcloud/container/ai/profiles/help | 9 + gcloud/container/ai/profiles/list | 40 +- gcloud/container/ai/profiles/manifests/create | 29 +- .../ai/profiles/serving-stack-versions/help | 22 + .../ai/profiles/serving-stack-versions/list | 66 +++ .../container/ai/profiles/serving-stacks/help | 21 + .../container/ai/profiles/serving-stacks/list | 60 +++ gcloud/container/ai/profiles/use-case/help | 21 + gcloud/container/ai/profiles/use-case/list | 51 ++ gcloud/datastream/streams/create | 50 +- gcloud/datastream/streams/update | 48 +- .../spaces/application-templates/create | 48 +- .../spaces/application-templates/update | 162 +++++- gcloud/developer-connect/connections/create | 284 ++++++++-- gcloud/developer-connect/connections/update | 208 +++++-- .../repository-groups/create | 106 +++- .../repository-groups/update | 171 +++++- .../setting-bindings/create | 2 + .../setting-bindings/update | 2 + .../setting-bindings/create | 5 +- .../setting-bindings/delete | 3 +- .../setting-bindings/describe | 3 +- .../setting-bindings/list | 3 +- .../setting-bindings/update | 5 +- .../gemini-gcp-enablement-settings/create | 15 +- .../setting-bindings/create | 5 +- .../setting-bindings/delete | 3 +- .../setting-bindings/describe | 3 +- .../setting-bindings/update | 5 +- .../gemini-gcp-enablement-settings/update | 18 +- .../logging-settings/setting-bindings/create | 2 + .../logging-settings/setting-bindings/update | 2 + .../setting-bindings/create | 2 + .../setting-bindings/update | 2 + gcloud/iam/policy-bindings/create | 48 +- gcloud/iam/policy-bindings/update | 13 +- .../principal-access-boundary-policies/create | 15 +- .../principal-access-boundary-policies/delete | 4 +- .../principal-access-boundary-policies/update | 36 +- gcloud/looker/instances/update | 24 + gcloud/lustre/instances/create | 4 +- gcloud/lustre/instances/update | 4 +- gcloud/managed-kafka/clusters/describe | 7 +- gcloud/managed-kafka/connect-clusters/create | 11 +- gcloud/managed-kafka/connect-clusters/update | 13 +- gcloud/managed-kafka/connectors/create | 8 +- gcloud/managed-kafka/connectors/update | 8 +- gcloud/model-armor/floorsettings/update | 17 +- gcloud/monitoring/help | 3 + gcloud/monitoring/policies/conditions/create | 95 ++++ gcloud/monitoring/policies/conditions/delete | 59 ++ .../monitoring/policies/conditions/describe | 57 ++ gcloud/monitoring/policies/conditions/help | 40 ++ gcloud/monitoring/policies/conditions/update | 77 +++ gcloud/monitoring/policies/create | 170 ++++++ gcloud/monitoring/policies/delete | 48 ++ gcloud/monitoring/policies/describe | 47 ++ gcloud/monitoring/policies/help | 51 ++ gcloud/monitoring/policies/list | 86 +++ gcloud/monitoring/policies/migrate | 44 ++ gcloud/monitoring/policies/update | 182 +++++++ gcloud/netapp/backup-vaults/create | 29 +- gcloud/netapp/volumes/create | 28 +- gcloud/netapp/volumes/update | 32 +- gcloud/privateca/pools/create | 9 +- gcloud/privateca/pools/update | 9 +- gcloud/resource-manager/capabilities/describe | 42 ++ gcloud/resource-manager/capabilities/help | 30 ++ gcloud/resource-manager/capabilities/update | 58 ++ gcloud/resource-manager/help | 3 + gcloud/run/jobs/logs/help | 4 - gcloud/run/multi-region-services/update | 9 +- gcloud/scheduler/cmek-config/update | 4 +- gcloud/services/disable | 4 +- gcloud/services/enable | 5 +- gcloud/workbench/instances/create | 9 +- gcloud/workstations/configs/create | 48 +- gcloud/workstations/configs/update | 27 +- 313 files changed, 11521 insertions(+), 1088 deletions(-) create mode 100644 gcloud/alpha/api-registry/help create mode 100644 gcloud/alpha/api-registry/mcp/disable create mode 100644 gcloud/alpha/api-registry/mcp/enable create mode 100644 gcloud/alpha/api-registry/mcp/help create mode 100644 gcloud/alpha/api-registry/mcp/servers/help create mode 100644 gcloud/alpha/api-registry/mcp/servers/list create mode 100644 gcloud/alpha/api-registry/mcp/tools/help create mode 100644 gcloud/alpha/api-registry/mcp/tools/list create mode 100644 gcloud/alpha/apphub/boundary/describe create mode 100644 gcloud/alpha/apphub/boundary/help create mode 100644 gcloud/alpha/apphub/boundary/update create mode 100644 gcloud/alpha/biglake/iceberg/catalogs/failover create mode 100644 gcloud/alpha/compute/reservations/slots/describe create mode 100644 gcloud/alpha/compute/reservations/slots/help create mode 100644 gcloud/alpha/compute/reservations/slots/list create mode 100644 gcloud/alpha/container/clusters/complete-control-plane-upgrade create mode 100644 gcloud/alpha/design-center/spaces/applications/register create mode 100644 gcloud/alpha/design-center/spaces/register-deployed-resources create mode 100644 gcloud/alpha/firebase-data-connect/help create mode 100644 gcloud/alpha/resource-manager/capabilities/describe create mode 100644 gcloud/alpha/resource-manager/capabilities/help create mode 100644 gcloud/alpha/resource-manager/capabilities/update create mode 100644 gcloud/alpha/sql/ssl/entraid-certs/create create mode 100644 gcloud/alpha/sql/ssl/entraid-certs/help create mode 100644 gcloud/alpha/sql/ssl/entraid-certs/list create mode 100644 gcloud/alpha/sql/ssl/entraid-certs/rollback create mode 100644 gcloud/alpha/sql/ssl/entraid-certs/rotate create mode 100644 gcloud/apphub/boundary/describe create mode 100644 gcloud/apphub/boundary/help create mode 100644 gcloud/apphub/boundary/update create mode 100644 gcloud/beta/api-registry/help create mode 100644 gcloud/beta/api-registry/mcp/disable rename gcloud/beta/{beyondcorp/operations/help => api-registry/mcp/enable} (51%) create mode 100644 gcloud/beta/api-registry/mcp/help create mode 100644 gcloud/beta/api-registry/mcp/servers/help create mode 100644 gcloud/beta/api-registry/mcp/servers/list create mode 100644 gcloud/beta/api-registry/mcp/tools/help create mode 100644 gcloud/beta/api-registry/mcp/tools/list create mode 100644 gcloud/beta/container/clusters/complete-control-plane-upgrade create mode 100644 gcloud/beta/filestore/instances/pause-replica create mode 100644 gcloud/beta/filestore/instances/resume-replica create mode 100644 gcloud/beta/firebase-data-connect/help create mode 100644 gcloud/beta/monitoring/policies/conditions/create create mode 100644 gcloud/beta/monitoring/policies/conditions/delete create mode 100644 gcloud/beta/monitoring/policies/conditions/describe create mode 100644 gcloud/beta/monitoring/policies/conditions/help create mode 100644 gcloud/beta/monitoring/policies/conditions/update create mode 100644 gcloud/beta/monitoring/policies/create create mode 100644 gcloud/beta/monitoring/policies/delete create mode 100644 gcloud/beta/monitoring/policies/describe create mode 100644 gcloud/beta/monitoring/policies/help create mode 100644 gcloud/beta/monitoring/policies/list create mode 100644 gcloud/beta/monitoring/policies/migrate create mode 100644 gcloud/beta/monitoring/policies/update create mode 100644 gcloud/beta/resource-manager/capabilities/describe create mode 100644 gcloud/beta/resource-manager/capabilities/help create mode 100644 gcloud/beta/resource-manager/capabilities/update create mode 100644 gcloud/beta/services/mcp/content-security/add create mode 100644 gcloud/beta/services/mcp/content-security/get create mode 100644 gcloud/beta/services/mcp/content-security/help create mode 100644 gcloud/beta/services/mcp/content-security/remove create mode 100644 gcloud/beta/services/mcp/disable create mode 100644 gcloud/beta/services/mcp/enable create mode 100644 gcloud/beta/services/mcp/help create mode 100644 gcloud/beta/services/mcp/list create mode 100644 gcloud/beta/sql/ssl/entraid-certs/create create mode 100644 gcloud/beta/sql/ssl/entraid-certs/help create mode 100644 gcloud/beta/sql/ssl/entraid-certs/list create mode 100644 gcloud/beta/sql/ssl/entraid-certs/rollback create mode 100644 gcloud/beta/sql/ssl/entraid-certs/rotate create mode 100644 gcloud/beyondcorp/help create mode 100644 gcloud/beyondcorp/operations/describe create mode 100644 gcloud/beyondcorp/operations/help create mode 100644 gcloud/beyondcorp/operations/list create mode 100644 gcloud/beyondcorp/security-gateways/applications/create create mode 100644 gcloud/beyondcorp/security-gateways/applications/delete create mode 100644 gcloud/beyondcorp/security-gateways/applications/describe create mode 100644 gcloud/beyondcorp/security-gateways/applications/get-iam-policy create mode 100644 gcloud/beyondcorp/security-gateways/applications/help create mode 100644 gcloud/beyondcorp/security-gateways/applications/list create mode 100644 gcloud/beyondcorp/security-gateways/applications/set-iam-policy create mode 100644 gcloud/beyondcorp/security-gateways/applications/update create mode 100644 gcloud/beyondcorp/security-gateways/create create mode 100644 gcloud/beyondcorp/security-gateways/delete create mode 100644 gcloud/beyondcorp/security-gateways/describe create mode 100644 gcloud/beyondcorp/security-gateways/get-iam-policy create mode 100644 gcloud/beyondcorp/security-gateways/help create mode 100644 gcloud/beyondcorp/security-gateways/list create mode 100644 gcloud/beyondcorp/security-gateways/set-iam-policy create mode 100644 gcloud/beyondcorp/security-gateways/update create mode 100644 gcloud/container/ai/profiles/serving-stack-versions/help create mode 100644 gcloud/container/ai/profiles/serving-stack-versions/list create mode 100644 gcloud/container/ai/profiles/serving-stacks/help create mode 100644 gcloud/container/ai/profiles/serving-stacks/list create mode 100644 gcloud/container/ai/profiles/use-case/help create mode 100644 gcloud/container/ai/profiles/use-case/list create mode 100644 gcloud/monitoring/policies/conditions/create create mode 100644 gcloud/monitoring/policies/conditions/delete create mode 100644 gcloud/monitoring/policies/conditions/describe create mode 100644 gcloud/monitoring/policies/conditions/help create mode 100644 gcloud/monitoring/policies/conditions/update create mode 100644 gcloud/monitoring/policies/create create mode 100644 gcloud/monitoring/policies/delete create mode 100644 gcloud/monitoring/policies/describe create mode 100644 gcloud/monitoring/policies/help create mode 100644 gcloud/monitoring/policies/list create mode 100644 gcloud/monitoring/policies/migrate create mode 100644 gcloud/monitoring/policies/update create mode 100644 gcloud/resource-manager/capabilities/describe create mode 100644 gcloud/resource-manager/capabilities/help create mode 100644 gcloud/resource-manager/capabilities/update diff --git a/gcloud/_version b/gcloud/_version index 72f4eaf7c..0f7cb566b 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 548.0.0 -alpha 2025.11.17 -beta 2025.11.17 +Google Cloud SDK 549.0.0 +alpha 2025.12.05 +beta 2025.12.05 bq 2.1.25 bundled-python3-unix 3.13.7 -core 2025.11.17 +core 2025.12.05 gcloud-crc32c 1.0.0 gsutil 5.35 diff --git a/gcloud/ai/endpoints/deploy-model b/gcloud/ai/endpoints/deploy-model index 1a6e4f3ab..ed4a142ff 100644 --- a/gcloud/ai/endpoints/deploy-model +++ b/gcloud/ai/endpoints/deploy-model @@ -8,8 +8,8 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--autoscaling-metric-specs=[METRIC-NAME=TARGET,...]] [--deployed-model-id=DEPLOYED_MODEL_ID] [--disable-container-logging] - [--enable-access-logging] [--machine-type=MACHINE_TYPE] - [--max-replica-count=MAX_REPLICA_COUNT] + [--enable-access-logging] [--gpu-partition-size=GPU_PARTITION_SIZE] + [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] [--required-replica-count=REQUIRED_REPLICA_COUNT] [--reservation-affinity=[key=KEY], @@ -75,8 +75,9 @@ OPTIONAL FLAGS The type of the accelerator. Choices are 'nvidia-a100-80gb', 'nvidia-b200', 'nvidia-gb200', 'nvidia-h100-80gb', 'nvidia-h100-mega-80gb', 'nvidia-h200-141gb', 'nvidia-l4', - 'nvidia-tesla-a100', 'nvidia-tesla-k80', 'nvidia-tesla-p100', - 'nvidia-tesla-p4', 'nvidia-tesla-t4', 'nvidia-tesla-v100'. + 'nvidia-rtx-pro-6000', 'nvidia-tesla-a100', 'nvidia-tesla-k80', + 'nvidia-tesla-p100', 'nvidia-tesla-p4', 'nvidia-tesla-t4', + 'nvidia-tesla-v100'. count The number of accelerators to attach to each machine running the @@ -120,6 +121,12 @@ OPTIONAL FLAGS These logs are standard server access logs, containing information like timestamp and latency for each prediction request. + --gpu-partition-size=GPU_PARTITION_SIZE + The partition size of the GPU accelerator. This can be used to + partition a single GPU into multiple smaller GPU instances. See + https://cloud.google.com/kubernetes-engine/docs/how-to/gpus-multi#multi-instance_gpu_partitions + for more details. + --machine-type=MACHINE_TYPE The machine resources to be used for each node of this deployment. For available machine types, see diff --git a/gcloud/ai/index-endpoints/deploy-index b/gcloud/ai/index-endpoints/deploy-index index d623ba7f4..a2acdc8eb 100644 --- a/gcloud/ai/index-endpoints/deploy-index +++ b/gcloud/ai/index-endpoints/deploy-index @@ -7,8 +7,8 @@ SYNOPSIS --deployed-index-id=DEPLOYED_INDEX_ID --display-name=DISPLAY_NAME --index=INDEX [--allowed-issuers=[ALLOWED_ISSUERS,...]] [--audiences=[AUDIENCES,...]] [--deployment-group=DEPLOYMENT_GROUP] - [--enable-access-logging] [--machine-type=MACHINE_TYPE] - [--max-replica-count=MAX_REPLICA_COUNT] + [--deployment-tier=DEPLOYMENT_TIER] [--enable-access-logging] + [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] [--psc-automation-configs=[network=NETWORK],[project-id=PROJECT-ID]] [--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...] @@ -95,6 +95,11 @@ OPTIONAL FLAGS creates your deployments from predictable IP spaces for easier traffic administration. + --deployment-tier=DEPLOYMENT_TIER + The deployment tier that the deployed index is deployed to. If not + specified, a system-chosen default tier is used. DEPLOYMENT_TIER must + be (only one value is supported): storage. + --enable-access-logging If true, online prediction access logs are sent to Cloud Logging. diff --git a/gcloud/alloydb/instances/create b/gcloud/alloydb/instances/create index 735b98ef9..29c6cbf41 100644 --- a/gcloud/alloydb/instances/create +++ b/gcloud/alloydb/instances/create @@ -176,7 +176,7 @@ OPTIONAL FLAGS instance has a machine-type, cpu-count must have the same value as the vCPU count in the machine-type. Eg: if machine-type is c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, - 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. + 2, 4, 8, 14, 16, 22, 32, 44, 48, 64, 72, 88, 96, 128, 144, 192, 288. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an @@ -223,7 +223,9 @@ OPTIONAL FLAGS c4-highmem-48-lssd, c4-highmem-96-lssd, c4-highmem-144-lssd, c4-highmem-192-lssd, c4-highmem-288-lssd, z3-highmem-14-standardlssd, z3-highmem-22-standardlssd, z3-highmem-44-standardlssd, - z3-highmem-88-standardlssd. + z3-highmem-88-standardlssd, z3-highmem-8-highlssd, + z3-highmem-16-highlssd, z3-highmem-22-highlssd, z3-highmem-32-highlssd, + z3-highmem-44-highlssd. --[no-]outbound-public-ip Add outbound Public IP connectivity to an AlloyDB instance. Use diff --git a/gcloud/alloydb/instances/update b/gcloud/alloydb/instances/update index 20e3f8997..5874809c2 100644 --- a/gcloud/alloydb/instances/update +++ b/gcloud/alloydb/instances/update @@ -162,7 +162,7 @@ OPTIONAL FLAGS instance has a machine-type, cpu-count must have the same value as the vCPU count in the machine-type. Eg: if machine-type is c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, - 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. + 2, 4, 8, 14, 16, 22, 32, 44, 48, 64, 72, 88, 96, 128, 144, 192, 288. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an @@ -209,7 +209,9 @@ OPTIONAL FLAGS c4-highmem-48-lssd, c4-highmem-96-lssd, c4-highmem-144-lssd, c4-highmem-192-lssd, c4-highmem-288-lssd, z3-highmem-14-standardlssd, z3-highmem-22-standardlssd, z3-highmem-44-standardlssd, - z3-highmem-88-standardlssd. + z3-highmem-88-standardlssd, z3-highmem-8-highlssd, + z3-highmem-16-highlssd, z3-highmem-22-highlssd, z3-highmem-32-highlssd, + z3-highmem-44-highlssd. --[no-]outbound-public-ip Add outbound Public IP connectivity to an AlloyDB instance. Use diff --git a/gcloud/alpha/ai/endpoints/deploy-model b/gcloud/alpha/ai/endpoints/deploy-model index 6342dfd35..ce0b95fbc 100644 --- a/gcloud/alpha/ai/endpoints/deploy-model +++ b/gcloud/alpha/ai/endpoints/deploy-model @@ -8,7 +8,7 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--autoscaling-metric-specs=[METRIC-NAME=TARGET,...]] [--deployed-model-id=DEPLOYED_MODEL_ID] [--enable-access-logging] - [--enable-container-logging] + [--enable-container-logging] [--gpu-partition-size=GPU_PARTITION_SIZE] [--idle-scaledown-period=IDLE_SCALEDOWN_PERIOD] [--initial-replica-count=INITIAL_REPLICA_COUNT] [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] @@ -128,6 +128,12 @@ OPTIONAL FLAGS Currently, only supported for custom-trained Models and AutoML Tabular Models. + --gpu-partition-size=GPU_PARTITION_SIZE + The partition size of the GPU accelerator. This can be used to + partition a single GPU into multiple smaller GPU instances. See + https://cloud.google.com/kubernetes-engine/docs/how-to/gpus-multi#multi-instance_gpu_partitions + for more details. + --idle-scaledown-period=IDLE_SCALEDOWN_PERIOD Duration (in seconds) without traffic before a deployment is scaled down to zero replicas. Defaults to 1 hour if min replica count is 0. diff --git a/gcloud/alpha/ai/index-endpoints/deploy-index b/gcloud/alpha/ai/index-endpoints/deploy-index index 928b7eeb1..12709c339 100644 --- a/gcloud/alpha/ai/index-endpoints/deploy-index +++ b/gcloud/alpha/ai/index-endpoints/deploy-index @@ -8,8 +8,8 @@ SYNOPSIS --deployed-index-id=DEPLOYED_INDEX_ID --display-name=DISPLAY_NAME --index=INDEX [--allowed-issuers=[ALLOWED_ISSUERS,...]] [--audiences=[AUDIENCES,...]] [--deployment-group=DEPLOYMENT_GROUP] - [--enable-access-logging] [--machine-type=MACHINE_TYPE] - [--max-replica-count=MAX_REPLICA_COUNT] + [--deployment-tier=DEPLOYMENT_TIER] [--enable-access-logging] + [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] [--psc-automation-configs=[network=NETWORK],[project-id=PROJECT-ID]] [--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...] @@ -96,6 +96,11 @@ OPTIONAL FLAGS creates your deployments from predictable IP spaces for easier traffic administration. + --deployment-tier=DEPLOYMENT_TIER + The deployment tier that the deployed index is deployed to. If not + specified, a system-chosen default tier is used. DEPLOYMENT_TIER must + be (only one value is supported): storage. + --enable-access-logging If true, online prediction access logs are sent to Cloud Logging. diff --git a/gcloud/alpha/alloydb/instances/create b/gcloud/alpha/alloydb/instances/create index 375812dcc..63e8b9fa5 100644 --- a/gcloud/alpha/alloydb/instances/create +++ b/gcloud/alpha/alloydb/instances/create @@ -183,7 +183,7 @@ OPTIONAL FLAGS instance has a machine-type, cpu-count must have the same value as the vCPU count in the machine-type. Eg: if machine-type is c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, - 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. + 2, 4, 8, 14, 16, 22, 32, 44, 48, 64, 72, 88, 96, 128, 144, 192, 288. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an @@ -230,7 +230,9 @@ OPTIONAL FLAGS c4-highmem-48-lssd, c4-highmem-96-lssd, c4-highmem-144-lssd, c4-highmem-192-lssd, c4-highmem-288-lssd, z3-highmem-14-standardlssd, z3-highmem-22-standardlssd, z3-highmem-44-standardlssd, - z3-highmem-88-standardlssd. + z3-highmem-88-standardlssd, z3-highmem-8-highlssd, + z3-highmem-16-highlssd, z3-highmem-22-highlssd, z3-highmem-32-highlssd, + z3-highmem-44-highlssd. --[no-]observability-config-enabled Enable enhanced query insights feature. Use diff --git a/gcloud/alpha/alloydb/instances/update b/gcloud/alpha/alloydb/instances/update index 440db0c50..81a5c8a22 100644 --- a/gcloud/alpha/alloydb/instances/update +++ b/gcloud/alpha/alloydb/instances/update @@ -169,7 +169,7 @@ OPTIONAL FLAGS instance has a machine-type, cpu-count must have the same value as the vCPU count in the machine-type. Eg: if machine-type is c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, - 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. + 2, 4, 8, 14, 16, 22, 32, 44, 48, 64, 72, 88, 96, 128, 144, 192, 288. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an @@ -216,7 +216,9 @@ OPTIONAL FLAGS c4-highmem-48-lssd, c4-highmem-96-lssd, c4-highmem-144-lssd, c4-highmem-192-lssd, c4-highmem-288-lssd, z3-highmem-14-standardlssd, z3-highmem-22-standardlssd, z3-highmem-44-standardlssd, - z3-highmem-88-standardlssd. + z3-highmem-88-standardlssd, z3-highmem-8-highlssd, + z3-highmem-16-highlssd, z3-highmem-22-highlssd, z3-highmem-32-highlssd, + z3-highmem-44-highlssd. --[no-]observability-config-enabled Enable enhanced query insights feature. Use diff --git a/gcloud/alpha/api-registry/help b/gcloud/alpha/api-registry/help new file mode 100644 index 000000000..f6e82ce62 --- /dev/null +++ b/gcloud/alpha/api-registry/help @@ -0,0 +1,28 @@ +NAME + gcloud alpha api-registry - manage Cloud API Registry Command Group + +SYNOPSIS + gcloud alpha api-registry GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Commands for managing Cloud API Registry. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + mcp + (ALPHA) Manage MCP Command Group. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta api-registry + diff --git a/gcloud/alpha/api-registry/mcp/disable b/gcloud/alpha/api-registry/mcp/disable new file mode 100644 index 000000000..fb4625981 --- /dev/null +++ b/gcloud/alpha/api-registry/mcp/disable @@ -0,0 +1,30 @@ +NAME + gcloud alpha api-registry mcp disable - disables MCP server for a given + service in the current project + +SYNOPSIS + gcloud alpha api-registry mcp disable SERVICE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Disables MCP server for a given service in the current project. + +POSITIONAL ARGUMENTS + SERVICE + The MCP server to disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta api-registry mcp disable + diff --git a/gcloud/alpha/api-registry/mcp/enable b/gcloud/alpha/api-registry/mcp/enable new file mode 100644 index 000000000..a872bb844 --- /dev/null +++ b/gcloud/alpha/api-registry/mcp/enable @@ -0,0 +1,30 @@ +NAME + gcloud alpha api-registry mcp enable - enables MCP server for a given + service in the current project + +SYNOPSIS + gcloud alpha api-registry mcp enable SERVICE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Enables MCP server for a given service in the current project. + +POSITIONAL ARGUMENTS + SERVICE + The MCP server to enable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta api-registry mcp enable + diff --git a/gcloud/alpha/api-registry/mcp/help b/gcloud/alpha/api-registry/mcp/help new file mode 100644 index 000000000..c40463dc2 --- /dev/null +++ b/gcloud/alpha/api-registry/mcp/help @@ -0,0 +1,41 @@ +NAME + gcloud alpha api-registry mcp - manage MCP Command Group + +SYNOPSIS + gcloud alpha api-registry mcp GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Commands for managing MCP enablement and disablement for a given + service in the current project. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + servers + (ALPHA) Manage Cloud API Registry MCP servers. + + tools + (ALPHA) Manage Cloud API Registry MCP tools. + +COMMANDS + COMMAND is one of the following: + + disable + (ALPHA) Disables MCP server for a given service in the current project. + + enable + (ALPHA) Enables MCP server for a given service in the current project. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta api-registry mcp + diff --git a/gcloud/alpha/api-registry/mcp/servers/help b/gcloud/alpha/api-registry/mcp/servers/help new file mode 100644 index 000000000..8a340743a --- /dev/null +++ b/gcloud/alpha/api-registry/mcp/servers/help @@ -0,0 +1,29 @@ +NAME + gcloud alpha api-registry mcp servers - manage Cloud API Registry MCP + servers + +SYNOPSIS + gcloud alpha api-registry mcp servers COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud API Registry MCP servers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (ALPHA) List MCP servers. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta api-registry mcp servers + diff --git a/gcloud/alpha/api-registry/mcp/servers/list b/gcloud/alpha/api-registry/mcp/servers/list new file mode 100644 index 000000000..b0fa3ea74 --- /dev/null +++ b/gcloud/alpha/api-registry/mcp/servers/list @@ -0,0 +1,69 @@ +NAME + gcloud alpha api-registry mcp servers list - list MCP servers + +SYNOPSIS + gcloud alpha api-registry mcp servers list [--all] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List MCP servers. + +EXAMPLES + To list all MCP servers in a project, run: + + $ gcloud alpha api-registry mcp servers list + +FLAGS + --all + If provided, list all the available (both enabled and non-enabled) MCP + servers for the project. + +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. This variant is also available: + + $ gcloud beta api-registry mcp servers list + diff --git a/gcloud/alpha/api-registry/mcp/tools/help b/gcloud/alpha/api-registry/mcp/tools/help new file mode 100644 index 000000000..7c6891b77 --- /dev/null +++ b/gcloud/alpha/api-registry/mcp/tools/help @@ -0,0 +1,28 @@ +NAME + gcloud alpha api-registry mcp tools - manage Cloud API Registry MCP tools + +SYNOPSIS + gcloud alpha api-registry mcp tools COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud API Registry MCP tools. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (ALPHA) List MCP tools. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta api-registry mcp tools + diff --git a/gcloud/alpha/api-registry/mcp/tools/list b/gcloud/alpha/api-registry/mcp/tools/list new file mode 100644 index 000000000..436a91bb2 --- /dev/null +++ b/gcloud/alpha/api-registry/mcp/tools/list @@ -0,0 +1,69 @@ +NAME + gcloud alpha api-registry mcp tools list - list MCP tools + +SYNOPSIS + gcloud alpha api-registry mcp tools list [--all] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List MCP tools. + +EXAMPLES + To list MCP tools, run: + + $ gcloud alpha api-registry mcp tools list + +FLAGS + --all + If provided, list all the available MCP tools for all (both enabled and + non-enabled) the MCP Servers for the project. + +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. This variant is also available: + + $ gcloud beta api-registry mcp tools list + diff --git a/gcloud/alpha/apphub/boundary/describe b/gcloud/alpha/apphub/boundary/describe new file mode 100644 index 000000000..202de2d11 --- /dev/null +++ b/gcloud/alpha/apphub/boundary/describe @@ -0,0 +1,46 @@ +NAME + gcloud alpha apphub boundary describe - show metadata for an App Hub + boundary + +SYNOPSIS + gcloud alpha apphub boundary describe [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show metadata for an App Hub boundary. + +FLAGS + Location resource - Location of the Boundary. 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; + ◆ Boundaries only support global location 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; + ▸ Boundaries only support global 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 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 apphub boundary describe + diff --git a/gcloud/alpha/apphub/boundary/help b/gcloud/alpha/apphub/boundary/help new file mode 100644 index 000000000..56879680a --- /dev/null +++ b/gcloud/alpha/apphub/boundary/help @@ -0,0 +1,31 @@ +NAME + gcloud alpha apphub boundary - manage App Hub boundaries + +SYNOPSIS + gcloud alpha apphub boundary COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage App Hub boundaries. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Show metadata for an App Hub boundary. + + update + (ALPHA) Update an App Hub boundary. + +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 apphub boundary + diff --git a/gcloud/alpha/apphub/boundary/update b/gcloud/alpha/apphub/boundary/update new file mode 100644 index 000000000..4e5e8f1be --- /dev/null +++ b/gcloud/alpha/apphub/boundary/update @@ -0,0 +1,57 @@ +NAME + gcloud alpha apphub boundary update - update an App Hub boundary + +SYNOPSIS + gcloud alpha apphub boundary update [--async] [--crm-node=CRM_NODE] + [--location=LOCATION] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an App Hub boundary. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + Update Boundary Options + + --crm-node=CRM_NODE + The CRM node to associate with the boundary. + + Location resource - Location of the Boundary. 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; + ◆ Boundaries only support global location 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; + ▸ Boundaries only support global location. + + --request-id=REQUEST_ID + An optional request ID to identify requests. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud apphub boundary update + diff --git a/gcloud/alpha/apphub/help b/gcloud/alpha/apphub/help index dc3715f96..620682015 100644 --- a/gcloud/alpha/apphub/help +++ b/gcloud/alpha/apphub/help @@ -18,6 +18,9 @@ GROUPS applications (ALPHA) Manage App Hub Applications. + boundary + (ALPHA) Manage App Hub boundaries. + discovered-services (ALPHA) Manage App Hub Discovered Services. diff --git a/gcloud/alpha/beyondcorp/help b/gcloud/alpha/beyondcorp/help index d898c8816..8d11f80f0 100644 --- a/gcloud/alpha/beyondcorp/help +++ b/gcloud/alpha/beyondcorp/help @@ -34,7 +34,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud beyondcorp $ gcloud beta beyondcorp diff --git a/gcloud/alpha/biglake/iceberg/catalogs/failover b/gcloud/alpha/biglake/iceberg/catalogs/failover new file mode 100644 index 000000000..9057eae4c --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/catalogs/failover @@ -0,0 +1,63 @@ +NAME + gcloud alpha biglake iceberg catalogs failover - failover a BigLake Iceberg + REST catalog + +SYNOPSIS + gcloud alpha biglake iceberg catalogs failover CATALOG + --primary-replica=PRIMARY_REPLICA + [--conditional-failover-replication-time=CONDITIONAL_FAILOVER_REPLICATION_TIME] + [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Failover a BigLake Iceberg REST catalog. + +POSITIONAL ARGUMENTS + Catalog resource - The Iceberg Catalog to failover. 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 catalog 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. + + CATALOG + ID of the catalog or fully qualified identifier for the catalog. + + To set the catalog attribute: + ▸ provide the argument catalog on the command line. + +REQUIRED FLAGS + --primary-replica=PRIMARY_REPLICA + The primary replica region to failover to. + +OPTIONAL FLAGS + --conditional-failover-replication-time=CONDITIONAL_FAILOVER_REPLICATION_TIME + If not specified, wait for all data from the source region to replicate + to the new primary region before completing the failover, with no data + loss. If specified, the failover will be executed immediately, + accepting data loss of any data commited after the specified timestamp. + This timestamp must be in UTC format, e.g. + "2025-10-09T01:13:34.038262Z". See $ gcloud topic datetimes for more + information. + + --validate-only + If true, the failover will be validated but not executed. + +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/biglake/iceberg/catalogs/help b/gcloud/alpha/biglake/iceberg/catalogs/help index 56ae1ee28..ee3a13934 100644 --- a/gcloud/alpha/biglake/iceberg/catalogs/help +++ b/gcloud/alpha/biglake/iceberg/catalogs/help @@ -25,6 +25,9 @@ COMMANDS describe (ALPHA) Describe a BigLake Iceberg REST catalog. + failover + (ALPHA) Failover a BigLake Iceberg REST catalog. + get-iam-policy (ALPHA) Get the IAM policy for a BigLake Iceberg REST catalog. diff --git a/gcloud/alpha/blockchain-validator/blockchain-validator-configs/create b/gcloud/alpha/blockchain-validator/blockchain-validator-configs/create index 5b6eba1f0..3bdc11261 100644 --- a/gcloud/alpha/blockchain-validator/blockchain-validator-configs/create +++ b/gcloud/alpha/blockchain-validator/blockchain-validator-configs/create @@ -8,7 +8,7 @@ SYNOPSIS --key-source=KEY_SOURCE --[no-]validation-work-enabled [--async] [--blockchain-node-id=BLOCKCHAIN_NODE_ID] [--labels=[LABELS,...]] [--location=LOCATION] [--request-id=REQUEST_ID] - [--ethereum-protocol-details-gas-limit=ETHEREUM_PROTOCOL_DETAILS_GAS_LIMIT --ethereum-protocol-details-graffiti=ETHEREUM_PROTOCOL_DETAILS_GRAFFITI --ethereum-protocol-details-suggested-fee-recipient=ETHEREUM_PROTOCOL_DETAILS_SUGGESTED_FEE_RECIPIENT --ethereum-protocol-details-use-block-builder-proposals] + [--ethereum-protocol-details-suggested-fee-recipient=ETHEREUM_PROTOCOL_DETAILS_SUGGESTED_FEE_RECIPIENT : --ethereum-protocol-details-deposit-gwei=ETHEREUM_PROTOCOL_DETAILS_DEPOSIT_GWEI --ethereum-protocol-details-eth1-withdrawal-address=ETHEREUM_PROTOCOL_DETAILS_ETH1_WITHDRAWAL_ADDRESS --ethereum-protocol-details-gas-limit=ETHEREUM_PROTOCOL_DETAILS_GAS_LIMIT --ethereum-protocol-details-graffiti=ETHEREUM_PROTOCOL_DETAILS_GRAFFITI --ethereum-protocol-details-use-block-builder-proposals] [[--existing-seed-phrase-reference-secret=EXISTING_SEED_PHRASE_REFERENCE_SECRET : --existing-seed-phrase-reference-derivation-index=EXISTING_SEED_PHRASE_REFERENCE_DERIVATION_INDEX] | [--remote-web3-signer-voting-public-key=REMOTE_WEB3_SIGNER_VOTING_PUBLIC_KEY --remote-web3-signer-web3signer-uri=REMOTE_WEB3_SIGNER_WEB3SIGNER_URI : --remote-web3-signer-timeout-duration=REMOTE_WEB3_SIGNER_TIMEOUT_DURATION] | [--seed-phrase-reference-secret=SEED_PHRASE_REFERENCE_SECRET : --seed-phrase-reference-export]] [GCLOUD_WIDE_FLAG ...] @@ -31,12 +31,15 @@ EXAMPLES blockchainNodes/my-node POSITIONAL ARGUMENTS - BlockchainValidatorConfig resource - Blockchain Validator Config Name The - name of the Blockchain Validator Config. The fully specified name must - have the format - projects/{project}/locations/{location}/blockchainValidatorConfigs/{validator}. - This represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + BlockchainValidatorConfig resource - Identifier. The name of the + validator. It must have the format + "projects/{project}/locations/{location}/blockchainValidatorConfigs/{validator}". + {validator} must contain only letters ([A-Za-z]), numbers ([0-9]), dashes + (-), underscores (), periods (.), tildes (~), plus (+) or percent signs + (%). It must be between 3 and 255 characters in length, and it must not + start with "goog". 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 blockchain_validator_config on the command line @@ -152,6 +155,30 @@ OPTIONAL FLAGS Blockchain validator configuration unique to Ethereum blockchains. + --ethereum-protocol-details-suggested-fee-recipient=ETHEREUM_PROTOCOL_DETAILS_SUGGESTED_FEE_RECIPIENT + The Ethereum address to which fee rewards should be sent. This can + only be set when creating the validator. If no blockchain node is + specified for the validator, this has no effect as no validator + client is run. See also + https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html + for more context. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + Arguments for the deposit gwei. + + --ethereum-protocol-details-deposit-gwei=ETHEREUM_PROTOCOL_DETAILS_DEPOSIT_GWEI + The number of Gwei (Ethereum currency unit) initially deposited + for the validator. This is set when the deposit is made and + cannot be changed. + + Arguments for the eth1 withdrawal address. + + --ethereum-protocol-details-eth1-withdrawal-address=ETHEREUM_PROTOCOL_DETAILS_ETH1_WITHDRAWAL_ADDRESS + The Ethereum wallet address to which withdrawals are sent. Once + set this cannot be changed. + Arguments for the gas limit. --ethereum-protocol-details-gas-limit=ETHEREUM_PROTOCOL_DETAILS_GAS_LIMIT @@ -172,14 +199,6 @@ OPTIONAL FLAGS default is used. If no blockchain node is specified, this has no effect as no validator client is run. - --ethereum-protocol-details-suggested-fee-recipient=ETHEREUM_PROTOCOL_DETAILS_SUGGESTED_FEE_RECIPIENT - The Ethereum address to which fee rewards should be sent. This can - only be set when creating the validator. If no blockchain node is - specified for the validator, this has no effect as no validator - client is run. See also - https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html - for more context. - Arguments for the use block builder proposals. --ethereum-protocol-details-use-block-builder-proposals @@ -251,7 +270,8 @@ OPTIONAL FLAGS Arguments for the timeout duration. --remote-web3-signer-timeout-duration=REMOTE_WEB3_SIGNER_TIMEOUT_DURATION - Timeout for requests to the Web3Signer service. + Timeout for requests to the Web3Signer service. If not set, a + default timeout of 12 seconds is used. Derivation path used to generate the voting key, and optionally Secret Manager secret to backup the seed phrase to. diff --git a/gcloud/alpha/blockchain-validator/blockchain-validator-configs/update b/gcloud/alpha/blockchain-validator/blockchain-validator-configs/update index 927b95fb9..6ad38a535 100644 --- a/gcloud/alpha/blockchain-validator/blockchain-validator-configs/update +++ b/gcloud/alpha/blockchain-validator/blockchain-validator-configs/update @@ -5,14 +5,15 @@ NAME SYNOPSIS gcloud alpha blockchain-validator blockchain-validator-configs update (BLOCKCHAIN_VALIDATOR_CONFIG : --location=LOCATION) [--async] - [--blockchain-node-id=BLOCKCHAIN_NODE_ID] - [--ethereum-protocol-details-graffiti=ETHEREUM_PROTOCOL_DETAILS_GRAFFITI] - [--request-id=REQUEST_ID] [--[no-]validation-work-enabled] + [--blockchain-node-id=BLOCKCHAIN_NODE_ID] [--request-id=REQUEST_ID] + [--[no-]validation-work-enabled] + [--clear-ethereum-protocol-details + --ethereum-protocol-details-graffiti=ETHEREUM_PROTOCOL_DETAILS_GRAFFITI] + [--clear-remote-web3-signer + --remote-web3-signer-timeout-duration=REMOTE_WEB3_SIGNER_TIMEOUT_DURATION --remote-web3-signer-web3signer-uri=REMOTE_WEB3_SIGNER_WEB3SIGNER_URI] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=REMOVE_LABELS] - [--remote-web3-signer-timeout-duration=REMOTE_WEB3_SIGNER_TIMEOUT_DURATION --remote-web3-signer-web3signer-uri=REMOTE_WEB3_SIGNER_WEB3SIGNER_URI] - [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update the configuration of a single blockchain validator. @@ -25,13 +26,15 @@ EXAMPLES --project=my-project --validation-work-enabled=true POSITIONAL ARGUMENTS - BlockchainValidatorConfig resource - Blockchain Validator Config Name The - name of the Blockchain Validator Config. The fully specified name must - have the format - projects/{project}/locations/{location}/blockchainValidatorConfigs/{validator}. - 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. + BlockchainValidatorConfig resource - Identifier. The name of the + validator. It must have the format + "projects/{project}/locations/{location}/blockchainValidatorConfigs/{validator}". + {validator} must contain only letters ([A-Za-z]), numbers ([0-9]), dashes + (-), underscores (), periods (.), tildes (~), plus (+) or percent signs + (%). It must be between 3 and 255 characters in length, and it must not + start with "goog". 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 blockchain_validator_config on the command line @@ -74,21 +77,6 @@ FLAGS will be offline (no attestations or blocks will be produced). If this node is offline or deleted, the validator will be offline. - Arguments for the blockchain type details. - - Blockchain validator configuration unique to Ethereum blockchains. - - Arguments for the graffiti. - - --ethereum-protocol-details-graffiti=ETHEREUM_PROTOCOL_DETAILS_GRAFFITI - Graffiti is a custom string published in blocks proposed by the - validator. This can only be written, as the current value cannot - be read back from the validator client API. See - https://lighthouse-book.sigmaprime.io/graffiti.html for an - example of how this is used. If not set, the validator client's - default is used. If no blockchain node is specified, this has no - effect as no validator client is run. - --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to @@ -114,6 +102,48 @@ FLAGS paused during the migration. Use --validation-work-enabled to enable and --no-validation-work-enabled to disable. + Arguments for the blockchain type details. + + Blockchain validator configuration unique to Ethereum blockchains. + + --clear-ethereum-protocol-details + Set blockchainValidatorConfig.ethereumProtocolDetails back to + default value. + + Arguments for the graffiti. + + --ethereum-protocol-details-graffiti=ETHEREUM_PROTOCOL_DETAILS_GRAFFITI + Graffiti is a custom string published in blocks proposed by the + validator. This can only be written, as the current value cannot + be read back from the validator client API. See + https://lighthouse-book.sigmaprime.io/graffiti.html for an + example of how this is used. If not set, the validator client's + default is used. If no blockchain node is specified, this has no + effect as no validator client is run. + + Arguments for the key source config. + + Configuration to use an external key signing service, such as the + service endpoint. The external key signer is expected to be managed + entirely by the customer. For reference see + https://docs.web3signer.consensys.net/ for details on Web3Signer and + https://docs.web3signer.consensys.net/reference/api/json-rpc for the API + exposed by the external service. + + --clear-remote-web3-signer + Set blockchainValidatorConfig.remoteWeb3Signer back to default + value. + + Arguments for the timeout duration. + + --remote-web3-signer-timeout-duration=REMOTE_WEB3_SIGNER_TIMEOUT_DURATION + Timeout for requests to the Web3Signer service. If not set, a + default timeout of 12 seconds is used. + + --remote-web3-signer-web3signer-uri=REMOTE_WEB3_SIGNER_WEB3SIGNER_URI + URI of the Web3Signer service the validator client connects to, to + request signing of attestations, blocks, etc. + Update labels. At most one of these can be specified: @@ -184,24 +214,6 @@ FLAGS --remove-labels=path_to_file.(yaml|json) - Arguments for the key source config. - - Configuration to use an external key signing service, such as the - service endpoint. The external key signer is expected to be managed - entirely by the customer. For reference see - https://docs.web3signer.consensys.net/ for details on Web3Signer and - https://docs.web3signer.consensys.net/reference/api/json-rpc for the API - exposed by the external service. - - Arguments for the timeout duration. - - --remote-web3-signer-timeout-duration=REMOTE_WEB3_SIGNER_TIMEOUT_DURATION - Timeout for requests to the Web3Signer service. - - --remote-web3-signer-web3signer-uri=REMOTE_WEB3_SIGNER_WEB3SIGNER_URI - URI of the Web3Signer service the validator client connects to, to - request signing of attestations, blocks, etc. - 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/cloudlocationfinder/cloud-locations/describe b/gcloud/alpha/cloudlocationfinder/cloud-locations/describe index 38f856fb1..e983e800b 100644 --- a/gcloud/alpha/cloudlocationfinder/cloud-locations/describe +++ b/gcloud/alpha/cloudlocationfinder/cloud-locations/describe @@ -44,8 +44,7 @@ POSITIONAL ARGUMENTS To set the location attribute: ▸ provide the argument cloud_location on the command line with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ default is global . + ▸ provide the argument --location on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/commitments/create b/gcloud/alpha/compute/commitments/create index 2c6bc1475..35f496767 100644 --- a/gcloud/alpha/compute/commitments/create +++ b/gcloud/alpha/compute/commitments/create @@ -118,8 +118,11 @@ OPTIONAL FLAGS general-purpose-n4d, general-purpose-t2d, graphics-optimized, graphics-optimized-g4, memory-optimized, memory-optimized-m3, memory-optimized-m4, memory-optimized-m4-6tb, memory-optimized-x4, - memory-optimized-x4-16tb, memory-optimized-x4-24tb, - memory-optimized-x4-32tb, storage-optimized-z3. + memory-optimized-x4-1440-24t, memory-optimized-x4-16tb, + memory-optimized-x4-1920-32t, memory-optimized-x4-24tb, + memory-optimized-x4-32tb, memory-optimized-x4-480-6t, + memory-optimized-x4-480-8t, memory-optimized-x4-960-12t, + memory-optimized-x4-960-16t, storage-optimized-z3. Manage the reservations to be created with the commitment. diff --git a/gcloud/alpha/compute/reservations/help b/gcloud/alpha/compute/reservations/help index 0940e26ac..89746bd2d 100644 --- a/gcloud/alpha/compute/reservations/help +++ b/gcloud/alpha/compute/reservations/help @@ -24,6 +24,9 @@ GROUPS blocks (ALPHA) Manage Compute Engine reservation blocks. + slots + (ALPHA) Manage Compute Engine reservation slots. + sub-blocks (ALPHA) Manage Compute Engine reservation sub blocks. diff --git a/gcloud/alpha/compute/reservations/slots/describe b/gcloud/alpha/compute/reservations/slots/describe new file mode 100644 index 000000000..f7254cc49 --- /dev/null +++ b/gcloud/alpha/compute/reservations/slots/describe @@ -0,0 +1,70 @@ +NAME + gcloud alpha compute reservations slots describe - describe a Compute + Engine reservation slot + +SYNOPSIS + gcloud alpha compute reservations slots describe RESERVATION + --block-name=BLOCK_NAME --slot-name=SLOT_NAME + --sub-block-name=SUB_BLOCK_NAME [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Compute Engine reservation slot. + +EXAMPLES + To describe a reservation slot in reservation exr1 in my-zone with block + name my-block, sub-block name my-sub-block, and slot name my-slot, run: + + $ gcloud alpha compute reservations slots describe exr1 \ + --zone=my-zone --block-name=my-block \ + --sub-block-name=my-sub-block --slot-name=my-slot + +POSITIONAL ARGUMENTS + RESERVATION + Name of the reservation to describe. + +REQUIRED FLAGS + --block-name=BLOCK_NAME + The name of the reservation block. + + --slot-name=SLOT_NAME + The name of the reservation slot. + + --sub-block-name=SUB_BLOCK_NAME + The name of the reservation sub block. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the reservation to describe. If not specified and the + compute/zone property isn't set, you might be prompted to select a zone + (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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/reservations/slots/help b/gcloud/alpha/compute/reservations/slots/help new file mode 100644 index 000000000..02760ee1e --- /dev/null +++ b/gcloud/alpha/compute/reservations/slots/help @@ -0,0 +1,30 @@ +NAME + gcloud alpha compute reservations slots - manage Compute Engine reservation + slots + +SYNOPSIS + gcloud alpha compute reservations slots COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Compute Engine reservation slots. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe a Compute Engine reservation slot. + + list + (ALPHA) List Compute Engine reservation slots. + +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/reservations/slots/list b/gcloud/alpha/compute/reservations/slots/list new file mode 100644 index 000000000..b4cafd5e5 --- /dev/null +++ b/gcloud/alpha/compute/reservations/slots/list @@ -0,0 +1,109 @@ +NAME + gcloud alpha compute reservations slots list - list Compute Engine + reservation slots + +SYNOPSIS + gcloud alpha compute reservations slots list RESERVATION + --block-name=BLOCK_NAME --sub-block-name=SUB_BLOCK_NAME [--zone=ZONE] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute reservations slots list displays all Compute + Engine reservation slots in an extended reservation's sub-block. + +EXAMPLES + To list all reservation slots in an extended reservation's block my-block + and sub-block my-sub-block in table form, run: + + $ gcloud alpha compute reservations slots list \ + extended-reservation --block-name=my-block \ + --sub-block-name=my-sub-block --zone=us-central1-a \ + --project=my-project + + To list the URIs of all reservation slots in an extended reservation, run: + + $ gcloud alpha compute reservations slots list \ + extended-reservation --block-name=my-block \ + --sub-block-name=my-sub-block --zone=us-central1-a \ + --project=my-project --uri + +POSITIONAL ARGUMENTS + RESERVATION + Name of the reservation to list. + +REQUIRED FLAGS + --block-name=BLOCK_NAME + The name of the reservation block. + + --sub-block-name=SUB_BLOCK_NAME + The name of the reservation sub block. + +FLAGS + --zone=ZONE + Zone of the reservation to list. If not specified and the compute/zone + property isn't set, you might be prompted to select a zone (interactive + mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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/container/backup-restore/restore-plans/create b/gcloud/alpha/container/backup-restore/restore-plans/create index af779fa2e..54a4b725a 100644 --- a/gcloud/alpha/container/backup-restore/restore-plans/create +++ b/gcloud/alpha/container/backup-restore/restore-plans/create @@ -130,9 +130,9 @@ OPTIONAL FLAGS resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: use-backup-version - Selecting 'use-existing-version' means deleting the existing - version of the conflicting resources before re-creating them from - the Backup. + Selecting 'use-backup-version' means deleting the existing version + of the conflicting resources before re-creating them from the + Backup. Note that this is a dangerous option which could cause unintentional data loss if used inappropriately. For example, diff --git a/gcloud/alpha/container/backup-restore/restore-plans/update b/gcloud/alpha/container/backup-restore/restore-plans/update index 5dbd48172..5e0dcae0d 100644 --- a/gcloud/alpha/container/backup-restore/restore-plans/update +++ b/gcloud/alpha/container/backup-restore/restore-plans/update @@ -84,9 +84,9 @@ FLAGS resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: use-backup-version - Selecting 'use-existing-version' means deleting the existing - version of the conflicting resources before re-creating them from - the Backup. + Selecting 'use-backup-version' means deleting the existing version + of the conflicting resources before re-creating them from the + Backup. Note that this is a dangerous option which could cause unintentional data loss if used inappropriately. For example, diff --git a/gcloud/alpha/container/clusters/complete-control-plane-upgrade b/gcloud/alpha/container/clusters/complete-control-plane-upgrade new file mode 100644 index 000000000..6b04748b0 --- /dev/null +++ b/gcloud/alpha/container/clusters/complete-control-plane-upgrade @@ -0,0 +1,56 @@ +NAME + gcloud alpha container clusters complete-control-plane-upgrade - complete + the control plane upgrade for an existing cluster + +SYNOPSIS + gcloud alpha container clusters complete-control-plane-upgrade NAME + [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Complete the control plane upgrade for an existing cluster. + +EXAMPLES + To complete the control plane upgrade for an existing cluster, run: + + $ gcloud alpha container clusters complete-control-plane-upgrade \ + sample-cluster + +POSITIONAL ARGUMENTS + NAME + The name of your existing cluster. + +FLAGS + At most one of these can be specified: + + --location=LOCATION + Compute zone or region (e.g. us-central1-a or us-central1) for the + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. + + --region=REGION + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. + + --zone=ZONE, -z ZONE + Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the + default compute/zone property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container clusters complete-control-plane-upgrade + diff --git a/gcloud/alpha/container/clusters/help b/gcloud/alpha/container/clusters/help index 189f00613..abf3de0d2 100644 --- a/gcloud/alpha/container/clusters/help +++ b/gcloud/alpha/container/clusters/help @@ -49,6 +49,9 @@ COMMANDS check-autopilot-compatibility (ALPHA) Check autopilot compatibility of a running cluster. + complete-control-plane-upgrade + (ALPHA) Complete the control plane upgrade for an existing cluster. + create (ALPHA) Create a cluster for running containers. diff --git a/gcloud/alpha/container/clusters/upgrade b/gcloud/alpha/container/clusters/upgrade index f01e71887..e0003d3a6 100644 --- a/gcloud/alpha/container/clusters/upgrade +++ b/gcloud/alpha/container/clusters/upgrade @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha container clusters upgrade NAME [--async] - [--cluster-version=CLUSTER_VERSION] [--image-type=IMAGE_TYPE] - [--master] [--node-pool=NODE_POOL] + [--cluster-version=CLUSTER_VERSION] + [--control-plane-soak-duration=CONTROL_PLANE_SOAK_DURATION] + [--image-type=IMAGE_TYPE] [--master] [--node-pool=NODE_POOL] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [--security-profile=SECURITY_PROFILE --security-profile-runtime-rules] [GCLOUD_WIDE_FLAG ...] @@ -70,6 +71,13 @@ FLAGS $ gcloud container get-server-config + --control-plane-soak-duration=CONTROL_PLANE_SOAK_DURATION + The soak duration for the rollback-able control plane upgrade. It only + applies to minor version upgrades. Setting this flag will trigger a + control plane upgrade with emulated version. The cluster is + rollback-able during the soak period. The soak period can be set + between 6 hours and 7 days. + --image-type=IMAGE_TYPE The image type to use for the cluster/node pool. Defaults to server-specified. diff --git a/gcloud/alpha/design-center/spaces/application-templates/create b/gcloud/alpha/design-center/spaces/application-templates/create index 0d6da2f1b..627d814ac 100644 --- a/gcloud/alpha/design-center/spaces/application-templates/create +++ b/gcloud/alpha/design-center/spaces/application-templates/create @@ -7,7 +7,11 @@ SYNOPSIS (APPLICATION_TEMPLATE : --location=LOCATION --space=SPACE) [--application-parameters=[key=KEY],[value=VALUE]] [--composition-type=COMPOSITION_TYPE] [--description=DESCRIPTION] - [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + [--display-name=DISPLAY_NAME] + [--root-input-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE]] + [--root-output-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create an application template. @@ -144,6 +148,48 @@ FLAGS --display-name=DISPLAY_NAME Application template display name. + --root-input-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Root level input variables of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --root-input-variables=componentUri=string,variable=string --root-input-variables=componentUri=string,variable=string + + JSON Example: + + --root-input-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --root-input-variables=path_to_file.(yaml|json) + + --root-output-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Root level output variables of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --root-output-variables=componentUri=string,variable=string --root-output-variables=componentUri=string,variable=string + + JSON Example: + + --root-output-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --root-output-variables=path_to_file.(yaml|json) + 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/design-center/spaces/application-templates/update b/gcloud/alpha/design-center/spaces/application-templates/update index be806ff9d..cda33321e 100644 --- a/gcloud/alpha/design-center/spaces/application-templates/update +++ b/gcloud/alpha/design-center/spaces/application-templates/update @@ -11,7 +11,17 @@ SYNOPSIS | --add-application-parameters=[key=KEY],[value=VALUE] --clear-application-parameters | --remove-application-parameters=[key=KEY],[value=VALUE]] - [GCLOUD_WIDE_FLAG ...] + [--root-input-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + | --add-root-input-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE] --clear-root-input-variables + | --remove-root-input-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE]] + [--root-output-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE] + | --add-root-output-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE] --clear-root-output-variables + | --remove-root-output-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update an application template. @@ -197,6 +207,156 @@ FLAGS --remove-application-parameters=path_to_file.(yaml|json) + Update root_input_variables. + + At most one of these can be specified: + + --root-input-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Set root_input_variables to new value. Root level input variables of + the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --root-input-variables=componentUri=string,variable=string --root-input-variables=componentUri=string,variable=string + + JSON Example: + + --root-input-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --root-input-variables=path_to_file.(yaml|json) + + --add-root-input-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Add new value to root_input_variables list. Root level input + variables of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --add-root-input-variables=componentUri=string,variable=string --add-root-input-variables=componentUri=string,variable=string + + JSON Example: + + --add-root-input-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --add-root-input-variables=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-root-input-variables + Clear root_input_variables value and set to empty list. + + --remove-root-input-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Remove existing value from root_input_variables list. Root level + input variables of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --remove-root-input-variables=componentUri=string,variable=string --remove-root-input-variables=componentUri=string,variable=string + + JSON Example: + + --remove-root-input-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --remove-root-input-variables=path_to_file.(yaml|json) + + Update root_output_variables. + + At most one of these can be specified: + + --root-output-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Set root_output_variables to new value. Root level output variables + of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --root-output-variables=componentUri=string,variable=string --root-output-variables=componentUri=string,variable=string + + JSON Example: + + --root-output-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --root-output-variables=path_to_file.(yaml|json) + + --add-root-output-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Add new value to root_output_variables list. Root level output + variables of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --add-root-output-variables=componentUri=string,variable=string --add-root-output-variables=componentUri=string,variable=string + + JSON Example: + + --add-root-output-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --add-root-output-variables=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-root-output-variables + Clear root_output_variables value and set to empty list. + + --remove-root-output-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Remove existing value from root_output_variables list. Root level + output variables of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --remove-root-output-variables=componentUri=string,variable=string --remove-root-output-variables=componentUri=string,variable=string + + JSON Example: + + --remove-root-output-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --remove-root-output-variables=path_to_file.(yaml|json) + 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/design-center/spaces/applications/help b/gcloud/alpha/design-center/spaces/applications/help index 0e19ef345..fc4ff69e6 100644 --- a/gcloud/alpha/design-center/spaces/applications/help +++ b/gcloud/alpha/design-center/spaces/applications/help @@ -41,6 +41,9 @@ COMMANDS preview (ALPHA) Preview an application. + register + (ALPHA) Register resources with a deployed application in App Hub. + update (ALPHA) Update an application. diff --git a/gcloud/alpha/design-center/spaces/applications/register b/gcloud/alpha/design-center/spaces/applications/register new file mode 100644 index 000000000..559264c57 --- /dev/null +++ b/gcloud/alpha/design-center/spaces/applications/register @@ -0,0 +1,114 @@ +NAME + gcloud alpha design-center spaces applications register - register + resources with a deployed application in App Hub + +SYNOPSIS + gcloud alpha design-center spaces applications register + (APPLICATION : --location=LOCATION --space=SPACE) + (--terraform-state=TERRAFORM_STATE + | --tfstate-signed-gcs-uri=TFSTATE_SIGNED_GCS_URI) [--async] + [--service-account=SERVICE_ACCOUNT] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Register deployed resources with an AppHub application using an + Application Design Center application as source. + +EXAMPLES + To register a deployed application with App Hub, using the application + my-application in the space my-space, in the project my-project and + location us-central1, run: + + $ gcloud alpha design-center spaces applications register \ + my-application --space=my-space --project=my-project \ + --location=us-central1 \ + --terraform-state='{"version":4, "resources": [...]}' + + To register a deployed application with App Hub, using a signed GCS URI for + the Terraform state file, run: + + $ gcloud alpha design-center spaces applications register \ + my-application --space=my-space --project=my-project \ + --location=us-central1 \ + --tfstate-signed-gcs-uri=`https://storage.googleapis.com/\ + my-bucket/tfstate.json?x-goog-signature=...` + +POSITIONAL ARGUMENTS + Application resource - The application with which the resources will be + registered. 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 APPLICATION 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument APPLICATION on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the application. + + To set the location attribute: + ▸ provide the argument APPLICATION on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --space=SPACE + The ID of the space. + + To set the space attribute: + ▸ provide the argument APPLICATION on the command line with a fully + specified name; + ▸ provide the argument --space on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --terraform-state=TERRAFORM_STATE + The Terraform state (tfstate) content as a raw JSON string. Example: + '{"version":4, "resources": [...]}' + + --tfstate-signed-gcs-uri=TFSTATE_SIGNED_GCS_URI + A securely signed Cloud Storage URI pointing to the tfstate file. + Example: + https://storage.googleapis.com/my-bucket/tfstate.json?x-goog-signature=... + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --service-account=SERVICE_ACCOUNT + The email address of the service account to use for this operation. + Format: projects/{PROJECT}/serviceAccounts/{EMAIL_ADDRESS} + +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 designcenter/v1alpha API. The full documentation for + this API can be found at: + http://cloud.google.com/application-design-center/docs + +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/design-center/spaces/help b/gcloud/alpha/design-center/spaces/help index 4b7363175..97ef55bfb 100644 --- a/gcloud/alpha/design-center/spaces/help +++ b/gcloud/alpha/design-center/spaces/help @@ -48,6 +48,9 @@ COMMANDS list (ALPHA) List spaces. + register-deployed-resources + (ALPHA) Register resources with a deployed application in App Hub. + set-iam-policy (ALPHA) Set the IAM policy for a Design Center space as defined in a JSON/YAML file. diff --git a/gcloud/alpha/design-center/spaces/register-deployed-resources b/gcloud/alpha/design-center/spaces/register-deployed-resources new file mode 100644 index 000000000..c6b94437d --- /dev/null +++ b/gcloud/alpha/design-center/spaces/register-deployed-resources @@ -0,0 +1,109 @@ +NAME + gcloud alpha design-center spaces register-deployed-resources - register + resources with a deployed application in App Hub + +SYNOPSIS + gcloud alpha design-center spaces register-deployed-resources + (SPACE : --location=LOCATION) --apphub-application=APPHUB_APPLICATION + (--terraform-state=TERRAFORM_STATE + | --tfstate-signed-gcs-uri=TFSTATE_SIGNED_GCS_URI) [--async] + [--service-account=SERVICE_ACCOUNT] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Register deployed resources with an AppHub application in a space. + +EXAMPLES + To register deployed resources with an AppHub application using the AppHub + application URI my-app in the space my-space, in the project my-project and + location us-central1, run: + + $ gcloud alpha design-center spaces register-deployed-resources \ + my-space --project=my-project --location=us-central1 \ + --apphub-application=`projects/my-project/locations/\ + us-central1/applications/my-app` \ + --terraform-state='{"version":4, "resources": [...]}' + + To register deployed resources with an AppHub application using a signed + GCS URI for the Terraform state file, run: + + $ gcloud alpha design-center spaces register-deployed-resources \ + my-space --project=my-project --location=us-central1 \ + --apphub-application=`projects/my-project/locations/\ + us-central1/applications/my-app` \ + --tfstate-signed-gcs-uri=`https://storage.googleapis.com/\ + my-bucket/tfstate.json?x-goog-signature=...` + +POSITIONAL ARGUMENTS + Space resource - The parent space. 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 space 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. + + SPACE + ID of the space or fully qualified identifier for the space. + + To set the space attribute: + ▸ provide the argument space on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the space. + + To set the location attribute: + ▸ provide the argument space on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --apphub-application=APPHUB_APPLICATION + The name of the AppHub Application. Format: + projects/{project}/locations/{location}/applications/{application} + + Exactly one of these must be specified: + + --terraform-state=TERRAFORM_STATE + The Terraform state (tfstate) content as a raw JSON string. Example: + '{"version":4, "resources": [...]}' + + --tfstate-signed-gcs-uri=TFSTATE_SIGNED_GCS_URI + A securely signed Cloud Storage URI pointing to the tfstate file. + Example: + https://storage.googleapis.com/my-bucket/tfstate.json?x-goog-signature=... + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --service-account=SERVICE_ACCOUNT + The email address of the service account to use for this operation. + Format: projects/{PROJECT}/serviceAccounts/{EMAIL_ADDRESS} + +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 designcenter/v1alpha API. The full documentation for + this API can be found at: + http://cloud.google.com/application-design-center/docs + +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/developer-connect/connections/create b/gcloud/alpha/developer-connect/connections/create index 1b998067d..fecab6335 100644 --- a/gcloud/alpha/developer-connect/connections/create +++ b/gcloud/alpha/developer-connect/connections/create @@ -118,10 +118,27 @@ FLAGS --location=LOCATION For resources [connection, + bitbucket-cloud-config-authorizer-credential-user-token-secret-version, + bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version, + bitbucket-cloud-config-webhook-secret-version, + bitbucket-data-center-config-authorizer-credential-user-token-secret-version, + bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version, bitbucket-data-center-config-service-directory, + bitbucket-data-center-config-webhook-secret-version, crypto-key-config-reference, + github-config-authorizer-credential-oauth-token-secret-version, + github-enterprise-config-private-key-secret-version, github-enterprise-config-service-directory, + github-enterprise-config-webhook-secret-version, + gitlab-config-authorizer-credential-user-token-secret-version, + gitlab-config-read-authorizer-credential-user-token-secret-version, + gitlab-config-webhook-secret-version, + gitlab-enterprise-config-authorizer-credential-user-token-secret-version, + gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version, gitlab-enterprise-config-service-directory, + gitlab-enterprise-config-webhook-secret-version, + http-config-basic-authentication-password-secret-version, + http-config-bearer-token-authentication-secret-version, http-config-service-directory], provides fallback value for resource location attribute. When the resource's full URI path is not provided, location will fallback to this flag value. @@ -187,7 +204,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -198,11 +217,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-cloud-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-cloud-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -210,7 +238,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-cloud-config-authorizer-credential-user-token-secret-version on the command line. @@ -222,7 +250,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -233,11 +263,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -245,14 +284,16 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version on the command line. SecretVersion resource - SecretManager resource containing the webhook secret used to verify webhook events, formatted as - projects/*/secrets/*/versions/*. This is used to validate and create + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This is used to validate and create webhooks. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -263,11 +304,20 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --bitbucket-cloud-config-webhook-secret-version on the command line + with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --bitbucket-cloud-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -275,7 +325,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --bitbucket-cloud-config-webhook-secret-version on the command line. @@ -293,7 +343,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -304,11 +356,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-data-center-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-data-center-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -316,7 +377,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-data-center-config-authorizer-credential-user-token-secret-version on the command line. @@ -331,7 +392,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -342,11 +405,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -354,15 +426,17 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version on the command line. SecretVersion resource - SecretManager resource containing the webhook secret used to verify webhook events, formatted as - projects/*/secrets/*/versions/*. This is used to validate webhooks. - This represents a Cloud resource. (NOTE) Some attributes are not given + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This is used to validate webhooks. 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: @@ -372,11 +446,20 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --bitbucket-data-center-config-webhook-secret-version on the + command line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --bitbucket-data-center-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -384,7 +467,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --bitbucket-data-center-config-webhook-secret-version on the command line. @@ -441,6 +524,8 @@ FLAGS The Developer Connect GitHub Application. firebase The Firebase GitHub Application. + gemini-code-assist + The Gemini Code Assist Application. This flag argument must be specified if any of the other arguments in this group are specified. @@ -453,7 +538,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the OAuth token that authorizes the connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -464,11 +551,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --github-config-authorizer-credential-oauth-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --github-config-authorizer-credential-oauth-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -476,7 +572,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --github-config-authorizer-credential-oauth-token-secret-version on the command line. @@ -496,9 +592,11 @@ FLAGS ID of the installation of the GitHub App. SecretVersion resource - SecretManager resource containing the private - key of the GitHub App, formatted as projects/*/secrets/*/versions/*. - This represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + key of the GitHub App, formatted as projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) + Some attributes are not given arguments in this group but can be set + in other ways. To set the project attribute: ▫ provide the argument @@ -507,17 +605,26 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --github-enterprise-config-private-key-secret-version on the + command line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --github-enterprise-config-private-key-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --github-enterprise-config-private-key-secret-version on the command line. @@ -564,8 +671,9 @@ FLAGS SSL certificate to use for requests to GitHub Enterprise. SecretVersion resource - SecretManager resource containing the webhook - secret of the GitHub App, formatted as - projects/*/secrets/*/versions/*. This represents a Cloud resource. + secret of the GitHub App, formatted as projects/*/secrets/*/versions/* + or projects/*/locations/*/secrets/*/versions/* (if regional secrets + are supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -576,17 +684,26 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --github-enterprise-config-webhook-secret-version on the command + line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --github-enterprise-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --github-enterprise-config-webhook-secret-version on the command line. @@ -600,7 +717,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -611,11 +730,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -623,7 +751,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-config-authorizer-credential-user-token-secret-version on the command line. @@ -635,7 +763,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -646,11 +776,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -658,15 +797,17 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-config-read-authorizer-credential-user-token-secret-version on the command line. SecretVersion resource - SecretManager resource containing the webhook secret of a GitLab project, formatted as - projects/*/secrets/*/versions/*. This is used to validate webhooks. - This represents a Cloud resource. (NOTE) Some attributes are not given + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This is used to validate webhooks. 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: @@ -675,10 +816,18 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument --gitlab-config-webhook-secret-version on + the command line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --gitlab-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -686,7 +835,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --gitlab-config-webhook-secret-version on the command line. @@ -699,7 +848,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -710,11 +861,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-enterprise-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-enterprise-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -722,7 +882,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-enterprise-config-authorizer-credential-user-token-secret-version on the command line. @@ -737,7 +897,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -748,11 +910,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -760,15 +931,17 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version on the command line. SecretVersion resource - SecretManager resource containing the webhook secret of a GitLab project, formatted as - projects/*/secrets/*/versions/*. This is used to validate webhooks. - This represents a Cloud resource. (NOTE) Some attributes are not given + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This is used to validate webhooks. 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: @@ -778,11 +951,20 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --gitlab-enterprise-config-webhook-secret-version on the command + line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --gitlab-enterprise-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -790,7 +972,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --gitlab-enterprise-config-webhook-secret-version on the command line. diff --git a/gcloud/alpha/developer-connect/connections/update b/gcloud/alpha/developer-connect/connections/update index 10c92e3cc..0e4d763cf 100644 --- a/gcloud/alpha/developer-connect/connections/update +++ b/gcloud/alpha/developer-connect/connections/update @@ -82,10 +82,23 @@ FLAGS --location=LOCATION For resources [connection, + bitbucket-cloud-config-authorizer-credential-user-token-secret-version, + bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version, + bitbucket-data-center-config-authorizer-credential-user-token-secret-version, + bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version, bitbucket-data-center-config-service-directory, crypto-key-config-reference, + github-config-authorizer-credential-oauth-token-secret-version, + github-enterprise-config-private-key-secret-version, github-enterprise-config-service-directory, + github-enterprise-config-webhook-secret-version, + gitlab-config-authorizer-credential-user-token-secret-version, + gitlab-config-read-authorizer-credential-user-token-secret-version, + gitlab-enterprise-config-authorizer-credential-user-token-secret-version, + gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version, gitlab-enterprise-config-service-directory, + http-config-basic-authentication-password-secret-version, + http-config-bearer-token-authentication-secret-version, http-config-service-directory], provides fallback value for resource location attribute. When the resource's full URI path is not provided, location will fallback to this flag value. @@ -215,7 +228,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -226,17 +241,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-cloud-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-cloud-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-cloud-config-authorizer-credential-user-token-secret-version on the command line. @@ -246,7 +270,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -257,17 +283,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version on the command line. @@ -286,7 +321,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -297,17 +334,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-data-center-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-data-center-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-data-center-config-authorizer-credential-user-token-secret-version on the command line. @@ -320,7 +366,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -331,17 +379,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version on the command line. @@ -402,7 +459,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the OAuth token that authorizes the connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -413,17 +472,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --github-config-authorizer-credential-oauth-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --github-config-authorizer-credential-oauth-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --github-config-authorizer-credential-oauth-token-secret-version on the command line. @@ -493,9 +561,11 @@ FLAGS github_enterprise_config_private_key_secret_version to new value. SecretManager resource containing the private key of the GitHub App, - formatted as projects/*/secrets/*/versions/*. This represents a - Cloud resource. (NOTE) Some attributes are not given arguments in - this group but can be set in other ways. + formatted as projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can + be set in other ways. To set the project attribute: ◇ provide the argument @@ -504,17 +574,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --github-enterprise-config-private-key-secret-version on the + command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --github-enterprise-config-private-key-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --github-enterprise-config-private-key-secret-version on the command line. @@ -531,9 +610,11 @@ FLAGS github_enterprise_config_webhook_secret_version to new value. SecretManager resource containing the webhook secret of the GitHub - App, formatted as projects/*/secrets/*/versions/*. This represents a - Cloud resource. (NOTE) Some attributes are not given arguments in - this group but can be set in other ways. + App, formatted as projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can + be set in other ways. To set the project attribute: ◇ provide the argument @@ -542,17 +623,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --github-enterprise-config-webhook-secret-version on the command + line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --github-enterprise-config-webhook-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --github-enterprise-config-webhook-secret-version on the command line. @@ -567,7 +657,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -578,17 +670,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-config-authorizer-credential-user-token-secret-version on the command line. @@ -598,7 +699,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -609,17 +712,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-config-read-authorizer-credential-user-token-secret-version on the command line. @@ -634,7 +746,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -645,17 +759,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-enterprise-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-enterprise-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-enterprise-config-authorizer-credential-user-token-secret-version on the command line. @@ -668,7 +791,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -679,17 +804,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version on the command line. diff --git a/gcloud/alpha/firebase-data-connect/help b/gcloud/alpha/firebase-data-connect/help new file mode 100644 index 000000000..f045a2086 --- /dev/null +++ b/gcloud/alpha/firebase-data-connect/help @@ -0,0 +1,22 @@ +NAME + gcloud alpha firebase-data-connect - manage Firebase Data Connect resources + +SYNOPSIS + gcloud alpha firebase-data-connect GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Firebase Data Connect resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta firebase-data-connect + diff --git a/gcloud/alpha/lustre/instances/create b/gcloud/alpha/lustre/instances/create index 4f95e6a14..af2d2d3b9 100644 --- a/gcloud/alpha/lustre/instances/create +++ b/gcloud/alpha/lustre/instances/create @@ -94,8 +94,8 @@ REQUIRED FLAGS ▸ provide the argument --network on the command line. --per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT - The throughput of the instance in MB/s/TiB. Valid values are 125, 250, - 500, 1000. See Performance tiers and maximum storage capacities + The throughput of the instance in MBps per TiB. Valid values are 125, + 250, 500, 1000. See Performance tiers and maximum storage capacities (https://cloud.google.com/managed-lustre/docs/create-instance#performance-tiers) for more information. diff --git a/gcloud/alpha/lustre/instances/update b/gcloud/alpha/lustre/instances/update index 6ba679559..42b71de4a 100644 --- a/gcloud/alpha/lustre/instances/update +++ b/gcloud/alpha/lustre/instances/update @@ -92,8 +92,8 @@ FLAGS --no-gke-support-enabled to disable. --per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT - The throughput of the instance in MB/s/TiB. Valid values are 125, 250, - 500, 1000. See Performance tiers and maximum storage capacities + The throughput of the instance in MBps per TiB. Valid values are 125, + 250, 500, 1000. See Performance tiers and maximum storage capacities (https://cloud.google.com/managed-lustre/docs/create-instance#performance-tiers) for more information. diff --git a/gcloud/alpha/managed-kafka/clusters/describe b/gcloud/alpha/managed-kafka/clusters/describe index 0cd3f1a92..e3f50d7dd 100644 --- a/gcloud/alpha/managed-kafka/clusters/describe +++ b/gcloud/alpha/managed-kafka/clusters/describe @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha managed-kafka clusters describe - (CLUSTER : --location=LOCATION) [--full-view] [GCLOUD_WIDE_FLAG ...] + (CLUSTER : --location=LOCATION) [--full] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Describe a Managed Service for Apache Kafka cluster. @@ -51,11 +51,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line. FLAGS - --full-view - Whether full cluster view is returned. If provided, the cluster view - will include everything, including data fetched from the Kafka cluster - source of truth. If not provided, the API will default to the basic - view that only includes the basic metadata of the cluster. + --full + Show detailed information about individual brokers, such as broker id + and zone, as well as the Kafka version running on the cluster. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/managed-kafka/connect-clusters/create b/gcloud/alpha/managed-kafka/connect-clusters/create index 27754c272..2e155b2af 100644 --- a/gcloud/alpha/managed-kafka/connect-clusters/create +++ b/gcloud/alpha/managed-kafka/connect-clusters/create @@ -83,10 +83,17 @@ REQUIRED FLAGS OPTIONAL FLAGS --additional-subnet=ADDITIONAL_SUBNET - Additional subnet to make available to the Kafka Connect cluster. - Structured like: + (DEPRECATED) Additional subnet to make available to the Kafka Connect + cluster. Structured like: projects/{project}/regions/{region}/subnetworks/{subnet_id}. + The --additional-subnet flag is deprecated and will be removed in a + future version. Managed Kafka Connect clusters can now reach any + endpoint accessible from the primary subnet without the need to define + additional subnets. Please see + https://cloud.google.com/managed-service-for-apache-kafka/docs/connect-cluster/create-connect-cluster#worker-subnet + for more information. + --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/alpha/managed-kafka/connect-clusters/update b/gcloud/alpha/managed-kafka/connect-clusters/update index 6c1e68504..4122e1bde 100644 --- a/gcloud/alpha/managed-kafka/connect-clusters/update +++ b/gcloud/alpha/managed-kafka/connect-clusters/update @@ -27,8 +27,6 @@ EXAMPLES --config-file=my-config-file.yaml --cpu=3 --memory=3GiB \ --primary-subnet=projects/my-project/regions/us-central1/\ subnetworks/default/1 \ - --additional-subnet=projects/my-project/regions/us-central1/\ - subnetworks/default/2 \ --dns-name=bootstrap.myconnectorCluster.us-central1.managedkafka\ .my-project.cloud.goog:9092 \ --secret=projects/my-project/secrets/my-secret/versions/1 \ @@ -145,10 +143,17 @@ REQUIRED FLAGS this group are specified. --additional-subnet=ADDITIONAL_SUBNET - Additional subnet to make available to the Kafka Connect cluster. - Structured like: + (DEPRECATED) Additional subnet to make available to the Kafka Connect + cluster. Structured like: projects/{project}/regions/{region}/subnetworks/{subnet_id}. + The --additional-subnet flag is deprecated and will be removed in a + future version. Managed Kafka Connect clusters can now reach any + endpoint accessible from the primary subnet without the need to + define additional subnets. Please see + https://cloud.google.com/managed-service-for-apache-kafka/docs/connect-cluster/create-connect-cluster#worker-subnet + for more information. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alpha/managed-kafka/connectors/create b/gcloud/alpha/managed-kafka/connectors/create index 044cd9eba..4f216b890 100644 --- a/gcloud/alpha/managed-kafka/connectors/create +++ b/gcloud/alpha/managed-kafka/connectors/create @@ -6,6 +6,7 @@ SYNOPSIS gcloud alpha managed-kafka connectors create (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) (--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]) + [--task-retry-disabled] [--task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF] [GCLOUD_WIDE_FLAG ...] @@ -21,12 +22,12 @@ EXAMPLES --configs=connector.class="com.google.pubsub.kafka.source.CloudP\ ubSubSourceConnector",cps.subscription="my-subscription",... \ [--task-restart-min-backoff=60s] \ - [--task-restart-max-backoff=30m] OR + [--task-restart-max-backoff=30m] [--task-retry-disabled=true] OR $ gcloud alpha managed-kafka connectors create myconnector \ --location=us-central1 --connect-cluster=mycluster \ --config-file=my-config-file.yaml \ [--task-restart-min-backoff=60s] \ - [--task-restart-max-backoff=30m] + [--task-restart-max-backoff=30m] [--task-retry-disabled=true] POSITIONAL ARGUMENTS Connector resource - Identifies the connector for which the command runs. @@ -92,6 +93,9 @@ REQUIRED FLAGS name, for example: cleanup.policy=compact,compression.type=producer. OPTIONAL FLAGS + --task-retry-disabled + Disable default task retry policy. + --task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF The maximum amount of time to wait before retrying a failed task in seconds. This sets an upper bound for the backoff delay. The default diff --git a/gcloud/alpha/managed-kafka/connectors/update b/gcloud/alpha/managed-kafka/connectors/update index fe1169544..4e550ca74 100644 --- a/gcloud/alpha/managed-kafka/connectors/update +++ b/gcloud/alpha/managed-kafka/connectors/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha managed-kafka connectors update (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [--task-retry-disabled] [--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]] [--task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF] @@ -19,11 +20,11 @@ EXAMPLES $ gcloud alpha managed-kafka connectors update myconnector \ --location=us-central1 --configs=KEY1=VALUE1,KEY2=VALUE2... \ --connect-cluster=mycluster [--task-restart-min-backoff=60s] \ - [--task-restart-max-backoff=30m] OR + [--task-restart-max-backoff=30m] [--task-retry-disabled=true] OR $ gcloud alpha managed-kafka connectors update myconnector \ --location=us-central1 --config-file=my-config-file.yaml \ --connect-cluster=mycluster [--task-restart-min-backoff=60s] \ - [--task-restart-max-backoff=30m] + [--task-restart-max-backoff=30m] [--task-retry-disabled=true] POSITIONAL ARGUMENTS Connector resource - Identifies the connector for which the command runs. @@ -68,6 +69,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line. FLAGS + --task-retry-disabled + Disable default task retry policy. + At most one of these can be specified: --config-file=JSON|YAML|FILE diff --git a/gcloud/alpha/model-armor/floorsettings/update b/gcloud/alpha/model-armor/floorsettings/update index c0e24764c..32d05f128 100644 --- a/gcloud/alpha/model-armor/floorsettings/update +++ b/gcloud/alpha/model-armor/floorsettings/update @@ -33,7 +33,8 @@ REQUIRED FLAGS OPTIONAL FLAGS --enable-floor-setting-enforcement=ENABLE_FLOOR_SETTING_ENFORCEMENT - Enable or disable the floor setting enforcement + Enable or disable the floor setting enforcement. Set the value to + "TRUE" to enable the floor setting enforcement, "FALSE" to disable it. Multi language detection enablement. @@ -120,16 +121,18 @@ OPTIONAL FLAGS SDP filter settings. --advanced-config-deidentify-template=ADVANCED_CONFIG_DEIDENTIFY_TEMPLATE - The sdp filter settings enforcement. The value can be either "enable" - or "disable". + The sdp filter settings enforcement. The value has to be a valid + template name. e.g. + projects/{project}/locations/{location}/deidentifyTemplates/{deidentify_template} --advanced-config-inspect-template=ADVANCED_CONFIG_INSPECT_TEMPLATE - The sdp filter settings enforcement. The value can be either "enable" - or "disable". + The sdp filter settings enforcement. The value has to be a valid + template name. e.g. + projects/{project}/locations/{location}/inspectTemplates/{inspect_template} --basic-config-filter-enforcement=BASIC_CONFIG_FILTER_ENFORCEMENT - The sdp filter settings enforcement. The value can be either - "ENABLED" or "DISABLED" + The sdp filter settings enforcement. The value can be either ENABLED + or DISABLED. Options for Google MCP server sanitization. diff --git a/gcloud/alpha/monitoring/policies/conditions/create b/gcloud/alpha/monitoring/policies/conditions/create index cf93a5f2d..679d67d04 100644 --- a/gcloud/alpha/monitoring/policies/conditions/create +++ b/gcloud/alpha/monitoring/policies/conditions/create @@ -90,5 +90,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud monitoring policies conditions create + + $ gcloud beta monitoring policies conditions create diff --git a/gcloud/alpha/monitoring/policies/conditions/delete b/gcloud/alpha/monitoring/policies/conditions/delete index 915eb87a6..ea7637320 100644 --- a/gcloud/alpha/monitoring/policies/conditions/delete +++ b/gcloud/alpha/monitoring/policies/conditions/delete @@ -54,5 +54,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud monitoring policies conditions delete + + $ gcloud beta monitoring policies conditions delete diff --git a/gcloud/alpha/monitoring/policies/conditions/describe b/gcloud/alpha/monitoring/policies/conditions/describe index ec3cf7ad7..4438fb307 100644 --- a/gcloud/alpha/monitoring/policies/conditions/describe +++ b/gcloud/alpha/monitoring/policies/conditions/describe @@ -52,5 +52,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud monitoring policies conditions describe + + $ gcloud beta monitoring policies conditions describe diff --git a/gcloud/alpha/monitoring/policies/conditions/help b/gcloud/alpha/monitoring/policies/conditions/help index f234b0279..0b578977b 100644 --- a/gcloud/alpha/monitoring/policies/conditions/help +++ b/gcloud/alpha/monitoring/policies/conditions/help @@ -35,5 +35,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud monitoring policies conditions + + $ gcloud beta monitoring policies conditions diff --git a/gcloud/alpha/monitoring/policies/conditions/update b/gcloud/alpha/monitoring/policies/conditions/update index dff8d0101..3cdfd807e 100644 --- a/gcloud/alpha/monitoring/policies/conditions/update +++ b/gcloud/alpha/monitoring/policies/conditions/update @@ -73,5 +73,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud monitoring policies conditions update + + $ gcloud beta monitoring policies conditions update diff --git a/gcloud/alpha/monitoring/policies/create b/gcloud/alpha/monitoring/policies/create index fb9ff79f0..339285e0c 100644 --- a/gcloud/alpha/monitoring/policies/create +++ b/gcloud/alpha/monitoring/policies/create @@ -165,5 +165,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud monitoring policies create + + $ gcloud beta monitoring policies create diff --git a/gcloud/alpha/monitoring/policies/delete b/gcloud/alpha/monitoring/policies/delete index 6a60254f5..8fee1df84 100644 --- a/gcloud/alpha/monitoring/policies/delete +++ b/gcloud/alpha/monitoring/policies/delete @@ -43,5 +43,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud monitoring policies delete + + $ gcloud beta monitoring policies delete diff --git a/gcloud/alpha/monitoring/policies/describe b/gcloud/alpha/monitoring/policies/describe index 5ca6c05b8..884318f32 100644 --- a/gcloud/alpha/monitoring/policies/describe +++ b/gcloud/alpha/monitoring/policies/describe @@ -42,5 +42,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud monitoring policies describe + + $ gcloud beta monitoring policies describe diff --git a/gcloud/alpha/monitoring/policies/help b/gcloud/alpha/monitoring/policies/help index caf022c95..9e620bc6d 100644 --- a/gcloud/alpha/monitoring/policies/help +++ b/gcloud/alpha/monitoring/policies/help @@ -50,5 +50,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud monitoring policies + + $ gcloud beta monitoring policies diff --git a/gcloud/alpha/monitoring/policies/list b/gcloud/alpha/monitoring/policies/list index 102dd8a63..984dc9f5a 100644 --- a/gcloud/alpha/monitoring/policies/list +++ b/gcloud/alpha/monitoring/policies/list @@ -82,5 +82,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud monitoring policies list + + $ gcloud beta monitoring policies list diff --git a/gcloud/alpha/monitoring/policies/migrate b/gcloud/alpha/monitoring/policies/migrate index 8937c160f..e9e9e3953 100644 --- a/gcloud/alpha/monitoring/policies/migrate +++ b/gcloud/alpha/monitoring/policies/migrate @@ -39,5 +39,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud monitoring policies migrate + + $ gcloud beta monitoring policies migrate diff --git a/gcloud/alpha/monitoring/policies/update b/gcloud/alpha/monitoring/policies/update index d44960d83..e7c54019f 100644 --- a/gcloud/alpha/monitoring/policies/update +++ b/gcloud/alpha/monitoring/policies/update @@ -177,5 +177,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud monitoring policies update + + $ gcloud beta monitoring policies update diff --git a/gcloud/alpha/netapp/volumes/create b/gcloud/alpha/netapp/volumes/create index e65c81260..370e1c42f 100644 --- a/gcloud/alpha/netapp/volumes/create +++ b/gcloud/alpha/netapp/volumes/create @@ -12,16 +12,19 @@ SYNOPSIS [peer-cluster-name=PEER-CLUSTER-NAME], [peer-ip-addresses=PEER-IP-ADDRESSES], [peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME]] + [--cache-pre-populate=[exclude-path-list=EXCLUDE-PATH-LIST], + [path-list=PATH-LIST],[recursion=RECURSION]] [--description=DESCRIPTION] [--enable-kerberos=ENABLE_KERBEROS] [--export-policy=[access-type=ACCESS-TYPE], - [allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS], + [allowed-clients=ALLOWED-CLIENTS],[anon-uid=ANON-UID], + [has-root-access=HAS-ROOT-ACCESS], [kerberos-5-read-only=KERBEROS-5-READ-ONLY], [kerberos-5-read-write=KERBEROS-5-READ-WRITE], [kerberos-5i-read-only=KERBEROS-5I-READ-ONLY], [kerberos-5i-read-write=KERBEROS-5I-READ-WRITE], [kerberos-5p-read-only=KERBEROS-5P-READ-ONLY], [kerberos-5p-read-write=KERBEROS-5P-READ-WRITE], - [nfsv3=NFSV3],[nfsv4=NFSV4]] + [nfsv3=NFSV3],[nfsv4=NFSV4],[squash-mode=SQUASH-MODE]] [--hybrid-replication-parameters=[cluster-location=CLUSTER-LOCATION], [description=DESCRIPTION], [hybrid-replication-type=HYBRID-REPLICATION-TYPE],[labels=LABELS], @@ -178,13 +181,29 @@ OPTIONAL FLAGS *enable-global-file-lock*::: If true, enable global file lock *cache-config*::: Cache-config as a hashtag-separated(#) list of key-value pairs + --cache-pre-populate=[exclude-path-list=EXCLUDE-PATH-LIST],[path-list=PATH-LIST],[recursion=RECURSION] + Cache Pre-populate contains cache pre-populate parameters of a volume. + + Cache Pre-populate will have the following format + --cache-pre-populate=path-list=PATH_LIST1#PATH_LIST2, + exclude-path-list=EXCLUDE_PATH_LIST1#EXCLUDE_PATH_LIST2, + recursion=RECURSION + + path-list + Hashtag-separated(#) list of paths to be pre-populated + exclude-path-list + Hashtag-separated(#) list of paths to be excluded from + pre-population + recursion + Boolean value indicating pre-populate recursion. + --description=DESCRIPTION A description of the Cloud NetApp Volume --enable-kerberos=ENABLE_KERBEROS Boolean flag indicating whether Volume is a kerberos Volume or not - --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4] + --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[anon-uid=ANON-UID],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4],[squash-mode=SQUASH-MODE] Export Policy of a Cloud NetApp Files Volume. This will be a field similar to network in which export policy fields can be specified as such: --export-policy=allowed-clients=ALLOWED_CLIENTS_IP_ADDRESSES, @@ -194,7 +213,8 @@ OPTIONAL FLAGS kerberos-5i-read-only=KERBEROS_5I_READ_ONLY, kerberos-5i-read-write=KERBEROS_5I_READ_WRITE, kerberos-5p-read-only=KERBEROS_5P_READ_ONLY, - kerberos-5p-read-write=KERBEROS_5P_READ_WRITE + kerberos-5p-read-write=KERBEROS_5P_READ_WRITE, + squash-mode=SQUASH_MODE,anon-uid=ANON_UID --hybrid-replication-parameters=[cluster-location=CLUSTER-LOCATION],[description=DESCRIPTION],[hybrid-replication-type=HYBRID-REPLICATION-TYPE],[labels=LABELS],[large-volume-constituent-count=LARGE-VOLUME-CONSTITUENT-COUNT],[peer-cluster-name=PEER-CLUSTER-NAME],[peer-ip-addresses=PEER-IP-ADDRESSES],[peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME],[replication=REPLICATION],[replication-schedule=REPLICATION-SCHEDULE] Hybrid Replication Parameters contains hybrid replication parameters on diff --git a/gcloud/alpha/netapp/volumes/update b/gcloud/alpha/netapp/volumes/update index 6be454de8..17bc62ea4 100644 --- a/gcloud/alpha/netapp/volumes/update +++ b/gcloud/alpha/netapp/volumes/update @@ -10,17 +10,20 @@ SYNOPSIS [peer-cluster-name=PEER-CLUSTER-NAME], [peer-ip-addresses=PEER-IP-ADDRESSES], [peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME]] - [--capacity=CAPACITY] [--description=DESCRIPTION] - [--enable-kerberos=ENABLE_KERBEROS] + [--cache-pre-populate=[exclude-path-list=EXCLUDE-PATH-LIST], + [path-list=PATH-LIST],[recursion=RECURSION]] [--capacity=CAPACITY] + [--description=DESCRIPTION] [--enable-kerberos=ENABLE_KERBEROS] [--export-policy=[access-type=ACCESS-TYPE], - [allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS], + [allowed-clients=ALLOWED-CLIENTS],[anon-uid=ANON-UID], + [has-root-access=HAS-ROOT-ACCESS], [kerberos-5-read-only=KERBEROS-5-READ-ONLY], [kerberos-5-read-write=KERBEROS-5-READ-WRITE], [kerberos-5i-read-only=KERBEROS-5I-READ-ONLY], [kerberos-5i-read-write=KERBEROS-5I-READ-WRITE], [kerberos-5p-read-only=KERBEROS-5P-READ-ONLY], [kerberos-5p-read-write=KERBEROS-5P-READ-WRITE], - [nfsv3=NFSV3],[nfsv4=NFSV4]] [--protocols=PROTOCOL,[PROTOCOL,...]] + [nfsv3=NFSV3],[nfsv4=NFSV4],[squash-mode=SQUASH-MODE]] + [--protocols=PROTOCOL,[PROTOCOL,...]] [--restricted-actions=RESTRICTED_ACTION,[...]] [--security-style=SECURITY_STYLE; default="SECURITY_STYLE_UNSPECIFIED"] [--share-name=SHARE_NAME] @@ -125,6 +128,22 @@ FLAGS *enable-global-file-lock*::: If true, enable global file lock *cache-config*::: Cache-config as a hashtag-separated(#) list of key-value pairs + --cache-pre-populate=[exclude-path-list=EXCLUDE-PATH-LIST],[path-list=PATH-LIST],[recursion=RECURSION] + Cache Pre-populate contains cache pre-populate parameters of a volume. + + Cache Pre-populate will have the following format + --cache-pre-populate=path-list=PATH_LIST1#PATH_LIST2, + exclude-path-list=EXCLUDE_PATH_LIST1#EXCLUDE_PATH_LIST2, + recursion=RECURSION + + path-list + Hashtag-separated(#) list of paths to be pre-populated + exclude-path-list + Hashtag-separated(#) list of paths to be excluded from + pre-population + recursion + Boolean value indicating pre-populate recursion. + --capacity=CAPACITY The desired capacity of the Volume in GiB or TiB units.If no capacity unit is specified, GiB is assumed. @@ -135,7 +154,7 @@ FLAGS --enable-kerberos=ENABLE_KERBEROS Boolean flag indicating whether Volume is a kerberos Volume or not - --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4] + --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[anon-uid=ANON-UID],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4],[squash-mode=SQUASH-MODE] Export Policy of a Cloud NetApp Files Volume. This will be a field similar to network in which export policy fields can be specified as such: --export-policy=allowed-clients=ALLOWED_CLIENTS_IP_ADDRESSES, @@ -145,7 +164,8 @@ FLAGS kerberos-5i-read-only=KERBEROS_5I_READ_ONLY, kerberos-5i-read-write=KERBEROS_5I_READ_WRITE, kerberos-5p-read-only=KERBEROS_5P_READ_ONLY, - kerberos-5p-read-write=KERBEROS_5P_READ_WRITE + kerberos-5p-read-write=KERBEROS_5P_READ_WRITE, + squash-mode=SQUASH_MODE,anon-uid=ANON_UID --protocols=PROTOCOL,[PROTOCOL,...] Type of File System protocols for the Cloud NetApp Files Volume. Valid diff --git a/gcloud/alpha/network-security/dns-threat-detectors/create b/gcloud/alpha/network-security/dns-threat-detectors/create index 085e41892..62bdcb3d1 100644 --- a/gcloud/alpha/network-security/dns-threat-detectors/create +++ b/gcloud/alpha/network-security/dns-threat-detectors/create @@ -56,17 +56,18 @@ REQUIRED FLAGS value is supported): infoblox - The Infoblox DNS threat detecter. + The Infoblox DNS threat detector provider. OPTIONAL FLAGS --excluded-networks=[EXCLUDED_NETWORKS,...] - A list of Network resource names which are exempt from the - configuration in this DnsThreatDetector. + A list of network resource names which aren't monitored by this + DnsThreatDetector. Example: projects/PROJECT_ID/global/networks/NETWORK_NAME. --labels=[LABELS,...] - Labels as key value pairs. + Any labels associated with the DnsThreatDetector, listed as key value + pairs. KEY Keys must start with a lowercase character and contain only hyphens diff --git a/gcloud/alpha/network-security/dns-threat-detectors/describe b/gcloud/alpha/network-security/dns-threat-detectors/describe index f44964144..6e4f4f505 100644 --- a/gcloud/alpha/network-security/dns-threat-detectors/describe +++ b/gcloud/alpha/network-security/dns-threat-detectors/describe @@ -16,7 +16,7 @@ EXAMPLES --location=global my-dns-threat-detector POSITIONAL ARGUMENTS - DnsThreatDetector resource - Name of the DnsThreatDetector resource The + DnsThreatDetector resource - Name of the DnsThreatDetector resource. 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/alpha/network-security/dns-threat-detectors/list b/gcloud/alpha/network-security/dns-threat-detectors/list index 81276bc98..b8b676ca1 100644 --- a/gcloud/alpha/network-security/dns-threat-detectors/list +++ b/gcloud/alpha/network-security/dns-threat-detectors/list @@ -17,8 +17,8 @@ EXAMPLES --location=global REQUIRED FLAGS - Location resource - Parent value for ListDnsThreatDetectorsRequest This - represents a Cloud resource. (NOTE) Some attributes are not given + Location resource - The parent value for ListDnsThreatDetectorsRequest. + 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: diff --git a/gcloud/alpha/network-security/dns-threat-detectors/update b/gcloud/alpha/network-security/dns-threat-detectors/update index 5dfb017b7..0d56043ad 100644 --- a/gcloud/alpha/network-security/dns-threat-detectors/update +++ b/gcloud/alpha/network-security/dns-threat-detectors/update @@ -63,7 +63,7 @@ FLAGS value is supported): infoblox - The Infoblox DNS threat detecter. + The Infoblox DNS threat detector provider. Update excluded_networks. @@ -88,7 +88,8 @@ FLAGS At most one of these can be specified: --labels=[LABELS,...] - Set labels to new value. Labels as key value pairs. + Set labels to new value. Any labels associated with the + DnsThreatDetector, listed as key value pairs. KEY Keys must start with a lowercase character and contain only @@ -111,7 +112,8 @@ FLAGS --labels=path_to_file.(yaml|json) --update-labels=[UPDATE_LABELS,...] - Update labels value or add key value pair. Labels as key value pairs. + Update labels value or add key value pair. Any labels associated with + the DnsThreatDetector, listed as key value pairs. KEY Keys must start with a lowercase character and contain only diff --git a/gcloud/alpha/resource-manager/capabilities/describe b/gcloud/alpha/resource-manager/capabilities/describe new file mode 100644 index 000000000..bdb9f8699 --- /dev/null +++ b/gcloud/alpha/resource-manager/capabilities/describe @@ -0,0 +1,45 @@ +NAME + gcloud alpha resource-manager capabilities describe - show whether a + Capability is enabled + +SYNOPSIS + gcloud alpha resource-manager capabilities describe CAPABILITY_ID + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Command to show whether a Capability is enabled. + + This command can fail for the following reasons: + ▪ The capability specified does not exist. + ▪ The active account does not have permission to access the given + folder/capability. + +EXAMPLES + The following command prints metadata for a capability with the ID + folders/123/capabilities/app-management: + + $ gcloud alpha resource-manager capabilities describe \ + "folders/123/capabilities/app-management" + +POSITIONAL ARGUMENTS + CAPABILITY_ID + ID for the capability you want 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. These variants are also available: + + $ gcloud resource-manager capabilities describe + + $ gcloud beta resource-manager capabilities describe + diff --git a/gcloud/alpha/resource-manager/capabilities/help b/gcloud/alpha/resource-manager/capabilities/help new file mode 100644 index 000000000..b1dca84f7 --- /dev/null +++ b/gcloud/alpha/resource-manager/capabilities/help @@ -0,0 +1,34 @@ +NAME + gcloud alpha resource-manager capabilities - manage Cloud Folder + Capabilities + +SYNOPSIS + gcloud alpha resource-manager capabilities COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Commands to query and update your Cloud Folder's Capabilities. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Show whether a Capability is enabled. + + update + (ALPHA) Update a folder capability. + +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 resource-manager capabilities + + $ gcloud beta resource-manager capabilities + diff --git a/gcloud/alpha/resource-manager/capabilities/update b/gcloud/alpha/resource-manager/capabilities/update new file mode 100644 index 000000000..da969c0f6 --- /dev/null +++ b/gcloud/alpha/resource-manager/capabilities/update @@ -0,0 +1,62 @@ +NAME + gcloud alpha resource-manager capabilities update - update a folder + capability + +SYNOPSIS + gcloud alpha resource-manager capabilities update CAPABILITY_ID + --[no-]enable [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Command to Update/Set the value field of the Folder capability. + This can be done by using the --enable flag to set the value to True, and + the --no-enable flag to set the value to False. + + This command can fail for the following reasons: + ▪ There is no folder parenting the given capability name. + ▪ The active account does not have permission to update the given + folder/capability. + +EXAMPLES + The following command updates a capability with the ID + folders/123/capabilities/app-management to have the value True: + + $ gcloud alpha resource-manager capabilities update \ + "folders/123/capabilities/app-management" --enable + + In order to set the value to False, the following command can be used: + + $ gcloud alpha resource-manager capabilities update \ + "folders/123/capabilities/app-management" --no-enable + +POSITIONAL ARGUMENTS + CAPABILITY_ID + ID for the capability you want to update. + +REQUIRED FLAGS + --[no-]enable + Enable the Capability. Use --enable to enable and --no-enable to + disable. + +OPTIONAL FLAGS + --update-mask=UPDATE_MASK + Update Mask. This is an optional field, and the only valid value this + can be set to currently is "value". + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud resource-manager capabilities update + + $ gcloud beta resource-manager capabilities update + diff --git a/gcloud/alpha/resource-manager/help b/gcloud/alpha/resource-manager/help index 3b707dee0..550d925b0 100644 --- a/gcloud/alpha/resource-manager/help +++ b/gcloud/alpha/resource-manager/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + capabilities + (ALPHA) Manage Cloud Folder Capabilities. + folders (ALPHA) Manage Cloud Folders. diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index 779473a6d..4fce2632d 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -50,7 +50,7 @@ SYNOPSIS --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...] --command=[COMMAND,...] - | --function=FUNCTION --image=IMAGE --source=SOURCE] + | --function=FUNCTION --no-build --image=IMAGE --source=SOURCE] [--binary-authorization=POLICY | --clear-binary-authorization] [--clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] @@ -717,6 +717,13 @@ FLAGS Specifies that the deployed object is a function. If a value is provided, that value is used as the entrypoint. + --no-build + When set, the cloud build step will be skipped and the provided + source code will be extracted directly on the base image. Your + source code must contain all the dependencies for your application. + See https://cloud.google.com/run/docs/deploying-source-code for + more details. + --image=IMAGE Name of the container image to deploy (e.g. us-docker.pkg.dev/cloudrun/container/hello:latest). When used with diff --git a/gcloud/alpha/run/multi-region-services/update b/gcloud/alpha/run/multi-region-services/update index 6a1cf113a..85e8eefc6 100644 --- a/gcloud/alpha/run/multi-region-services/update +++ b/gcloud/alpha/run/multi-region-services/update @@ -351,10 +351,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: --clear-volumes Remove all existing volumes from the Cloud Run resource, including diff --git a/gcloud/alpha/services/disable b/gcloud/alpha/services/disable index 7111eddbd..d5f6cd684 100644 --- a/gcloud/alpha/services/disable +++ b/gcloud/alpha/services/disable @@ -3,7 +3,7 @@ NAME project, folder or organization SYNOPSIS - gcloud alpha services disable [SERVICE ...] [--async] + gcloud alpha services disable SERVICE [SERVICE ...] [--async] [--bypass-api-usage-check] [--force] [--validate-only] [--bypass-dependency-service-check | --disable-dependency-services] [--folder=FOLDER_ID | --organization=ORGANIZATION_ID @@ -50,7 +50,7 @@ EXAMPLES $ gcloud alpha services disable my-consumed-service --async POSITIONAL ARGUMENTS - [SERVICE ...] + SERVICE [SERVICE ...] The name of the service(s) to disable. FLAGS diff --git a/gcloud/alpha/services/enable b/gcloud/alpha/services/enable index ffe7d9dbf..550939a1b 100644 --- a/gcloud/alpha/services/enable +++ b/gcloud/alpha/services/enable @@ -3,8 +3,8 @@ NAME project, folder or organization SYNOPSIS - gcloud alpha services enable [SERVICE ...] [--async] [--skip-dependency] - [--validate-only] + gcloud alpha services enable SERVICE [SERVICE ...] [--async] + [--skip-dependency] [--validate-only] [--folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] @@ -52,7 +52,7 @@ EXAMPLES $ gcloud alpha services enable service1 service2 service3 POSITIONAL ARGUMENTS - [SERVICE ...] + SERVICE [SERVICE ...] The name of the service(s) to enable. FLAGS diff --git a/gcloud/alpha/services/mcp/content-security/add b/gcloud/alpha/services/mcp/content-security/add index 8724ff9f9..8e22dcec0 100644 --- a/gcloud/alpha/services/mcp/content-security/add +++ b/gcloud/alpha/services/mcp/content-security/add @@ -36,5 +36,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services mcp content-security add diff --git a/gcloud/alpha/services/mcp/content-security/get b/gcloud/alpha/services/mcp/content-security/get index 040748c85..3dff51e4d 100644 --- a/gcloud/alpha/services/mcp/content-security/get +++ b/gcloud/alpha/services/mcp/content-security/get @@ -29,5 +29,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services mcp content-security get diff --git a/gcloud/alpha/services/mcp/content-security/help b/gcloud/alpha/services/mcp/content-security/help index 90dabf7f4..6438348cb 100644 --- a/gcloud/alpha/services/mcp/content-security/help +++ b/gcloud/alpha/services/mcp/content-security/help @@ -29,5 +29,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services mcp content-security diff --git a/gcloud/alpha/services/mcp/content-security/remove b/gcloud/alpha/services/mcp/content-security/remove index 5be0f59ac..f643fa67b 100644 --- a/gcloud/alpha/services/mcp/content-security/remove +++ b/gcloud/alpha/services/mcp/content-security/remove @@ -36,5 +36,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services mcp content-security remove diff --git a/gcloud/alpha/services/mcp/disable b/gcloud/alpha/services/mcp/disable index dac244b0a..68f7e471e 100644 --- a/gcloud/alpha/services/mcp/disable +++ b/gcloud/alpha/services/mcp/disable @@ -76,5 +76,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services mcp disable diff --git a/gcloud/alpha/services/mcp/enable b/gcloud/alpha/services/mcp/enable index 450b853fb..d968345eb 100644 --- a/gcloud/alpha/services/mcp/enable +++ b/gcloud/alpha/services/mcp/enable @@ -4,7 +4,6 @@ NAME SYNOPSIS gcloud alpha services mcp enable SERVICE [--async] - [--skip-mcp-endpoint-check] [--folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] @@ -44,10 +43,6 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. - --skip-mcp-endpoint-check - If true, the system will bypass the check for MCP endpoint while - enabling a service. - At most one of these can be specified: --folder=FOLDER_ID @@ -80,5 +75,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services mcp enable diff --git a/gcloud/alpha/services/mcp/help b/gcloud/alpha/services/mcp/help index 91ba4a795..263fa8f7d 100644 --- a/gcloud/alpha/services/mcp/help +++ b/gcloud/alpha/services/mcp/help @@ -34,5 +34,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services mcp diff --git a/gcloud/alpha/services/mcp/list b/gcloud/alpha/services/mcp/list index e28d8bcfd..09fe112c6 100644 --- a/gcloud/alpha/services/mcp/list +++ b/gcloud/alpha/services/mcp/list @@ -91,5 +91,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services mcp list diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index 10869ddc4..a3dec3e7d 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -52,6 +52,7 @@ SYNOPSIS [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] + [--performance-capture-config=KEY=VALUE,[KEY=VALUE,...]] [--psc-auto-connections=[network=NETWORK],[project=PROJECT]] [--[no-]recreate-replicas-on-primary-crash] [--replica-type=REPLICA_TYPE] [--replication=REPLICATION] @@ -75,6 +76,8 @@ SYNOPSIS : --disk-encryption-key-keyring=DISK_ENCRYPTION_KEY_KEYRING --disk-encryption-key-location=DISK_ENCRYPTION_KEY_LOCATION --disk-encryption-key-project=DISK_ENCRYPTION_KEY_PROJECT] + [--entra-id-application-id=ENTRA_ID_APPLICATION_ID + --entra-id-tenant-id=ENTRA_ID_TENANT_ID] [--master-dump-file-path=MASTER_DUMP_FILE_PATH --master-username=MASTER_USERNAME : [--master-ca-certificate-path=MASTER_CA_CERTIFICATE_PATH @@ -503,6 +506,15 @@ FLAGS Number of previous passwords that cannot be reused. The valid range is 0 to 100. + --performance-capture-config=KEY=VALUE,[KEY=VALUE,...] + A comma-separated list of performance capture settings to add to the + MySQL instance. The input should be in a format of key=value. Available + case-sensitive keys are: enabled (boolean), probing-interval-seconds + (integer), probe-threshold (integer), running-threads-threshold + (integer), seconds-behind-source-threshold (integer), and + transaction-duration-threshold (integer). Example: + --performance-capture-config enabled=true,probe-threshold=5 + --psc-auto-connections=[network=NETWORK],[project=PROJECT] A comma-separated list of networks or network-project pairs. Each project is represented by a project number (numeric) or by a project ID @@ -716,6 +728,20 @@ FLAGS line; ▸ set the property core/project. + Entraid configuration for the SQL Server instance. + + --entra-id-application-id=ENTRA_ID_APPLICATION_ID + Set the Entraid application ID. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --entra-id-tenant-id=ENTRA_ID_TENANT_ID + Set the Entraid tenant ID. + + This flag argument must be specified if any of the other arguments in + this group are specified. + Options for creating an internal replica of an external data source. --master-dump-file-path=MASTER_DUMP_FILE_PATH diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index be8de6e1f..05c93bd62 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -15,7 +15,7 @@ SYNOPSIS [--audit-retention-interval=AUDIT_RETENTION_INTERVAL] [--audit-upload-interval=AUDIT_UPLOAD_INTERVAL] [--availability-type=AVAILABILITY_TYPE] [--clear-active-directory] - [--clear-active-directory-dns-servers] + [--clear-active-directory-dns-servers] [--clear-entra-id-config] [--clear-failover-dr-replica-name] [--clear-password-policy] [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] [--data-api-access=DATA_API_ACCESS] @@ -53,6 +53,7 @@ SYNOPSIS [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] + [--performance-capture-config=KEY=VALUE,[KEY=VALUE,...]] [--pricing-plan=PRICING_PLAN, -p PRICING_PLAN] [--reconcile-psa-networking] [--[no-]recreate-replicas-on-primary-crash] @@ -85,6 +86,8 @@ SYNOPSIS | --psc-auto-connections=[network=NETWORK],[project=PROJECT]] [--clear-psc-network-attachment-uri | --psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI] + [--entra-id-application-id=ENTRA_ID_APPLICATION_ID + --entra-id-tenant-id=ENTRA_ID_TENANT_ID] [--gce-zone=GCE_ZONE | --secondary-zone=SECONDARY_ZONE --zone=ZONE] [--[no-]auto-scale-disable-scale-in --[no-]auto-scale-enabled --auto-scale-in-cooldown-seconds=AUTO_SCALE_IN_COOLDOWN_SECONDS @@ -182,6 +185,9 @@ FLAGS --clear-active-directory-dns-servers Removes the list of DNS Servers from the Active Directory Config. + --clear-entra-id-config + Clear the Entra ID config for the SQL Server instance. + --clear-failover-dr-replica-name Clear the DR replica setting for the primary instance. Flag is only available for MySQL and PostgreSQL database instances. @@ -465,6 +471,15 @@ FLAGS Number of previous passwords that cannot be reused. The valid range is 0 to 100. + --performance-capture-config=KEY=VALUE,[KEY=VALUE,...] + A comma-separated list of performance capture settings to add to the + MySQL instance. The input should be in a format of key=value. Available + case-sensitive keys are: enabled (boolean), probing-interval-seconds + (integer), probe-threshold (integer), running-threads-threshold + (integer), seconds-behind-source-threshold (integer), and + transaction-duration-threshold (integer). Example: + --performance-capture-config enabled=true,probe-threshold=5 + --pricing-plan=PRICING_PLAN, -p PRICING_PLAN First Generation instances only. The pricing plan for this instance. PRICING_PLAN must be one of: PER_USE, PACKAGE. @@ -753,6 +768,20 @@ FLAGS Service Connect (PSC). For example, this would be of the form:--psc-network-attachment-uri=projects/test-project/regions/us-central1/networkAttachments/my-na + Entraid configuration for the SQL Server instance. + + --entra-id-application-id=ENTRA_ID_APPLICATION_ID + Set the Entraid application ID. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --entra-id-tenant-id=ENTRA_ID_TENANT_ID + Set the Entraid tenant ID. + + This flag argument must be specified if any of the other arguments in + this group are specified. + At most one of these can be specified: --gce-zone=GCE_ZONE diff --git a/gcloud/alpha/sql/ssl/entraid-certs/create b/gcloud/alpha/sql/ssl/entraid-certs/create new file mode 100644 index 000000000..df1ffd753 --- /dev/null +++ b/gcloud/alpha/sql/ssl/entraid-certs/create @@ -0,0 +1,36 @@ +NAME + gcloud alpha sql ssl entraid-certs create - create an Entra ID certificate + for a Cloud SQL instance + +SYNOPSIS + gcloud alpha sql ssl entraid-certs create --instance=INSTANCE, -i INSTANCE + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create an Entra ID certificate for a Cloud SQL instance. + +REQUIRED FLAGS + --instance=INSTANCE, -i INSTANCE + Cloud SQL instance ID. + +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 alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta sql ssl entraid-certs create + diff --git a/gcloud/alpha/sql/ssl/entraid-certs/help b/gcloud/alpha/sql/ssl/entraid-certs/help new file mode 100644 index 000000000..d03f05c34 --- /dev/null +++ b/gcloud/alpha/sql/ssl/entraid-certs/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha sql ssl entraid-certs - provide commands for managing Entra ID + certificates of Cloud SQL instances + +SYNOPSIS + gcloud alpha sql ssl entraid-certs COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Provide commands for managing Entra ID certificates of Cloud SQL + instances, including creating, listing, rotating in, and rolling back + certificates. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create an Entra ID certificate for a Cloud SQL instance. + + list + (ALPHA) List all Entra ID certificates for a Cloud SQL instance. + + rollback + (ALPHA) Roll back to the previous Entra ID certificate for a Cloud SQL + instance. + + rotate + (ALPHA) Rotate in the upcoming Entra ID certificate for a Cloud SQL + instance. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta sql ssl entraid-certs + diff --git a/gcloud/alpha/sql/ssl/entraid-certs/list b/gcloud/alpha/sql/ssl/entraid-certs/list new file mode 100644 index 000000000..72c108530 --- /dev/null +++ b/gcloud/alpha/sql/ssl/entraid-certs/list @@ -0,0 +1,64 @@ +NAME + gcloud alpha sql ssl entraid-certs list - list all Entra ID certificates + for a Cloud SQL instance + +SYNOPSIS + gcloud alpha sql ssl entraid-certs list --instance=INSTANCE, -i INSTANCE + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all Entra ID certificates for a Cloud SQL instance. + +REQUIRED FLAGS + --instance=INSTANCE, -i INSTANCE + Cloud SQL instance ID. + +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. This variant is also available: + + $ gcloud beta sql ssl entraid-certs list + diff --git a/gcloud/alpha/sql/ssl/entraid-certs/rollback b/gcloud/alpha/sql/ssl/entraid-certs/rollback new file mode 100644 index 000000000..08df72a2a --- /dev/null +++ b/gcloud/alpha/sql/ssl/entraid-certs/rollback @@ -0,0 +1,37 @@ +NAME + gcloud alpha sql ssl entraid-certs rollback - roll back to the previous + Entra ID certificate for a Cloud SQL instance + +SYNOPSIS + gcloud alpha sql ssl entraid-certs rollback --instance=INSTANCE, -i + INSTANCE [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Roll back to the previous Entra ID certificate for a Cloud SQL + instance. + +REQUIRED FLAGS + --instance=INSTANCE, -i INSTANCE + Cloud SQL instance ID. + +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 alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta sql ssl entraid-certs rollback + diff --git a/gcloud/alpha/sql/ssl/entraid-certs/rotate b/gcloud/alpha/sql/ssl/entraid-certs/rotate new file mode 100644 index 000000000..bbf459f82 --- /dev/null +++ b/gcloud/alpha/sql/ssl/entraid-certs/rotate @@ -0,0 +1,37 @@ +NAME + gcloud alpha sql ssl entraid-certs rotate - rotate in the upcoming Entra ID + certificate for a Cloud SQL instance + +SYNOPSIS + gcloud alpha sql ssl entraid-certs rotate --instance=INSTANCE, -i INSTANCE + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Rotate in the upcoming Entra ID certificate for a Cloud SQL + instance. + +REQUIRED FLAGS + --instance=INSTANCE, -i INSTANCE + Cloud SQL instance ID. + +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 alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta sql ssl entraid-certs rotate + diff --git a/gcloud/alpha/sql/ssl/help b/gcloud/alpha/sql/ssl/help index f66c16740..df4f2d92a 100644 --- a/gcloud/alpha/sql/ssl/help +++ b/gcloud/alpha/sql/ssl/help @@ -21,6 +21,10 @@ GROUPS (ALPHA) Provide commands for managing client certificates of Cloud SQL instances. + entraid-certs + (ALPHA) Provide commands for managing Entra ID certificates of Cloud + SQL instances. + server-ca-certs (ALPHA) Provide commands for managing server CA certs of Cloud SQL instances. diff --git a/gcloud/alpha/workstations/configs/create b/gcloud/alpha/workstations/configs/create index 34a95ccae..bd5f00b10 100644 --- a/gcloud/alpha/workstations/configs/create +++ b/gcloud/alpha/workstations/configs/create @@ -38,8 +38,11 @@ SYNOPSIS | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE; default="codeoss"] [--kms-key=KMS_KEY : --kms-key-service-account=KMS_KEY_SERVICE_ACCOUNT] - [--no-persistent-storage | --pd-disk-type=PD_DISK_TYPE; - default="pd-standard" --pd-reclaim-policy=PD_RECLAIM_POLICY; + [--no-persistent-storage | --disk-reclaim-policy=DISK_RECLAIM_POLICY; + default="delete" --disk-type=DISK_TYPE --disk-size=DISK_SIZE + | --disk-source-snapshot=DISK_SOURCE_SNAPSHOT + | --pd-disk-type=PD_DISK_TYPE; default="pd-standard" + --pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete" --pd-disk-size=PD_DISK_SIZE; default=200 | --pd-source-snapshot=PD_SOURCE_SNAPSHOT] [GCLOUD_WIDE_FLAG ...] @@ -516,30 +519,51 @@ FLAGS If set, workstations under this configuration will not have a persistent directory. - Persistent directory configuration. + --disk-reclaim-policy=DISK_RECLAIM_POLICY; default="delete" + What should happen to the disk after the Workstation is deleted. + DISK_RECLAIM_POLICY must be one of: - --pd-disk-type=PD_DISK_TYPE; default="pd-standard" - Type of the persistent directory. PD_DISK_TYPE must be one of: - pd-standard, pd-balanced, pd-ssd. + delete + The persistent disk will be deleted with the Workstation. + retain + The persistent disk will be remain after the workstation is + deleted and the administrator must manually delete the disk. - --pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete" - What should happen to the disk after the Workstation is deleted. - PD_RECLAIM_POLICY must be one of: + --disk-type=DISK_TYPE + Type of the persistent directory. DISK_TYPE must be one of: + pd-standard, pd-balanced, pd-ssd, hyperdisk-balanced-ha. - delete - The persistent disk will be deleted with the Workstation. - retain - The persistent disk will be remain after the workstation is - deleted and the administrator must manually delete the disk. + At most one of these can be specified: - At most one of these can be specified: + --disk-size=DISK_SIZE + Size of the persistent directory in GB. DISK_SIZE must be one of: + 10, 50, 100, 200, 500, 1000. - --pd-disk-size=PD_DISK_SIZE; default=200 - Size of the persistent directory in GB. PD_DISK_SIZE must be one - of: 10, 50, 100, 200, 500, 1000. + --disk-source-snapshot=DISK_SOURCE_SNAPSHOT + Name of the snapshot to use as the source for the home disk. - --pd-source-snapshot=PD_SOURCE_SNAPSHOT - Name of the snapshot to use as the source for the home disk. + --pd-disk-type=PD_DISK_TYPE; default="pd-standard" + Type of the persistent directory. PD_DISK_TYPE must be one of: + pd-standard, pd-balanced, pd-ssd. + + --pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete" + What should happen to the disk after the Workstation is deleted. + PD_RECLAIM_POLICY must be one of: + + delete + The persistent disk will be deleted with the Workstation. + retain + The persistent disk will be remain after the workstation is + deleted and the administrator must manually delete the disk. + + At most one of these can be specified: + + --pd-disk-size=PD_DISK_SIZE; default=200 + Size of the persistent directory in GB. PD_DISK_SIZE must be one + of: 10, 50, 100, 200, 500, 1000. + + --pd-source-snapshot=PD_SOURCE_SNAPSHOT + Name of the snapshot to use as the source for the home disk. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/workstations/configs/update b/gcloud/alpha/workstations/configs/update index 257d9ee3c..4b83f4860 100644 --- a/gcloud/alpha/workstations/configs/update +++ b/gcloud/alpha/workstations/configs/update @@ -34,7 +34,10 @@ SYNOPSIS [--disable-localhost-replacement | --enable-localhost-replacement] [--disable-ssh-to-vm | --enable-ssh-to-vm] [--disable-tcp-connections | --enable-tcp-connections] - [--pd-source-snapshot=PD_SOURCE_SNAPSHOT | --pd-disk-size=PD_DISK_SIZE + [--disk-source-snapshot=DISK_SOURCE_SNAPSHOT + | --pd-source-snapshot=PD_SOURCE_SNAPSHOT + | --disk-size=DISK_SIZE --disk-type=DISK_TYPE + | --pd-disk-size=PD_DISK_SIZE --pd-disk-type=PD_DISK_TYPE; default="pd-standard"] [GCLOUD_WIDE_FLAG ...] @@ -460,20 +463,28 @@ FLAGS At most one of these can be specified: + --disk-source-snapshot=DISK_SOURCE_SNAPSHOT + Name of the snapshot to use as the source for the home disk. + --pd-source-snapshot=PD_SOURCE_SNAPSHOT Name of the snapshot to use as the source for the persistent directory. - --pd-source-snapshot cannot be specified when --pd-disk-size or - --pd-disk-type is specified. + --disk-size=DISK_SIZE + Size of the persistent directory in GB. DISK_SIZE must be one of: 10, + 50, 100, 200, 500, 1000. - --pd-disk-size=PD_DISK_SIZE - Size of the persistent directory in GB. PD_DISK_SIZE must be one - of: 10, 50, 100, 200, 500, 1000. + --disk-type=DISK_TYPE + Type of the persistent directory. DISK_TYPE must be one of: + pd-standard, pd-balanced, pd-ssd, hyperdisk-balanced-ha. - --pd-disk-type=PD_DISK_TYPE; default="pd-standard" - Type of the persistent directory. PD_DISK_TYPE must be one of: - pd-standard, pd-balanced, pd-ssd. + --pd-disk-size=PD_DISK_SIZE + Size of the persistent directory in GB. PD_DISK_SIZE must be one of: + 10, 50, 100, 200, 500, 1000. + + --pd-disk-type=PD_DISK_TYPE; default="pd-standard" + Type of the persistent directory. PD_DISK_TYPE must be one of: + pd-standard, pd-balanced, pd-ssd. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/apphub/boundary/describe b/gcloud/apphub/boundary/describe new file mode 100644 index 000000000..e03033524 --- /dev/null +++ b/gcloud/apphub/boundary/describe @@ -0,0 +1,42 @@ +NAME + gcloud apphub boundary describe - show metadata for an App Hub boundary + +SYNOPSIS + gcloud apphub boundary describe [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show metadata for an App Hub boundary. + +FLAGS + Location resource - Location of the Boundary. 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; + ◆ Boundaries only support global location 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; + ▸ Boundaries only support global 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 variant is also available: + + $ gcloud alpha apphub boundary describe + diff --git a/gcloud/apphub/boundary/help b/gcloud/apphub/boundary/help new file mode 100644 index 000000000..2836f486f --- /dev/null +++ b/gcloud/apphub/boundary/help @@ -0,0 +1,28 @@ +NAME + gcloud apphub boundary - manage App Hub boundaries + +SYNOPSIS + gcloud apphub boundary COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing App Hub Boundaries. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Show metadata for an App Hub boundary. + + update + Update an App Hub boundary. + +NOTES + This variant is also available: + + $ gcloud alpha apphub boundary + diff --git a/gcloud/apphub/boundary/update b/gcloud/apphub/boundary/update new file mode 100644 index 000000000..fef1cbcf5 --- /dev/null +++ b/gcloud/apphub/boundary/update @@ -0,0 +1,54 @@ +NAME + gcloud apphub boundary update - update an App Hub boundary + +SYNOPSIS + gcloud apphub boundary update [--async] [--crm-node=CRM_NODE] + [--location=LOCATION] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an App Hub boundary. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + Update Boundary Options + + --crm-node=CRM_NODE + The CRM node to associate with the boundary. + + Location resource - Location of the Boundary. 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; + ◆ Boundaries only support global location 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; + ▸ Boundaries only support global location. + + --request-id=REQUEST_ID + An optional request ID to identify requests. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha apphub boundary update + diff --git a/gcloud/apphub/help b/gcloud/apphub/help index 6e8d92c5c..80ca4ee36 100644 --- a/gcloud/apphub/help +++ b/gcloud/apphub/help @@ -18,6 +18,9 @@ GROUPS applications Manage App Hub Applications. + boundary + Manage App Hub boundaries. + discovered-services Manage App Hub Discovered Services. diff --git a/gcloud/beta/ai/endpoints/deploy-model b/gcloud/beta/ai/endpoints/deploy-model index 30ec69217..37c0ae10f 100644 --- a/gcloud/beta/ai/endpoints/deploy-model +++ b/gcloud/beta/ai/endpoints/deploy-model @@ -8,7 +8,7 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--autoscaling-metric-specs=[METRIC-NAME=TARGET,...]] [--deployed-model-id=DEPLOYED_MODEL_ID] [--enable-access-logging] - [--enable-container-logging] + [--enable-container-logging] [--gpu-partition-size=GPU_PARTITION_SIZE] [--idle-scaledown-period=IDLE_SCALEDOWN_PERIOD] [--initial-replica-count=INITIAL_REPLICA_COUNT] [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] @@ -128,6 +128,12 @@ OPTIONAL FLAGS Currently, only supported for custom-trained Models and AutoML Tabular Models. + --gpu-partition-size=GPU_PARTITION_SIZE + The partition size of the GPU accelerator. This can be used to + partition a single GPU into multiple smaller GPU instances. See + https://cloud.google.com/kubernetes-engine/docs/how-to/gpus-multi#multi-instance_gpu_partitions + for more details. + --idle-scaledown-period=IDLE_SCALEDOWN_PERIOD Duration (in seconds) without traffic before a deployment is scaled down to zero replicas. Defaults to 1 hour if min replica count is 0. diff --git a/gcloud/beta/ai/index-endpoints/deploy-index b/gcloud/beta/ai/index-endpoints/deploy-index index 80c59424c..79b30d732 100644 --- a/gcloud/beta/ai/index-endpoints/deploy-index +++ b/gcloud/beta/ai/index-endpoints/deploy-index @@ -8,8 +8,8 @@ SYNOPSIS --deployed-index-id=DEPLOYED_INDEX_ID --display-name=DISPLAY_NAME --index=INDEX [--allowed-issuers=[ALLOWED_ISSUERS,...]] [--audiences=[AUDIENCES,...]] [--deployment-group=DEPLOYMENT_GROUP] - [--enable-access-logging] [--machine-type=MACHINE_TYPE] - [--max-replica-count=MAX_REPLICA_COUNT] + [--deployment-tier=DEPLOYMENT_TIER] [--enable-access-logging] + [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] [--psc-automation-configs=[network=NETWORK],[project-id=PROJECT-ID]] [--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...] @@ -96,6 +96,11 @@ OPTIONAL FLAGS creates your deployments from predictable IP spaces for easier traffic administration. + --deployment-tier=DEPLOYMENT_TIER + The deployment tier that the deployed index is deployed to. If not + specified, a system-chosen default tier is used. DEPLOYMENT_TIER must + be (only one value is supported): storage. + --enable-access-logging If true, online prediction access logs are sent to Cloud Logging. diff --git a/gcloud/beta/alloydb/instances/create b/gcloud/beta/alloydb/instances/create index c92013e87..554acc141 100644 --- a/gcloud/beta/alloydb/instances/create +++ b/gcloud/beta/alloydb/instances/create @@ -183,7 +183,7 @@ OPTIONAL FLAGS instance has a machine-type, cpu-count must have the same value as the vCPU count in the machine-type. Eg: if machine-type is c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, - 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. + 2, 4, 8, 14, 16, 22, 32, 44, 48, 64, 72, 88, 96, 128, 144, 192, 288. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an @@ -230,7 +230,9 @@ OPTIONAL FLAGS c4-highmem-48-lssd, c4-highmem-96-lssd, c4-highmem-144-lssd, c4-highmem-192-lssd, c4-highmem-288-lssd, z3-highmem-14-standardlssd, z3-highmem-22-standardlssd, z3-highmem-44-standardlssd, - z3-highmem-88-standardlssd. + z3-highmem-88-standardlssd, z3-highmem-8-highlssd, + z3-highmem-16-highlssd, z3-highmem-22-highlssd, z3-highmem-32-highlssd, + z3-highmem-44-highlssd. --[no-]observability-config-enabled Enable enhanced query insights feature. Use diff --git a/gcloud/beta/alloydb/instances/update b/gcloud/beta/alloydb/instances/update index f298f5035..1db7b0e5c 100644 --- a/gcloud/beta/alloydb/instances/update +++ b/gcloud/beta/alloydb/instances/update @@ -169,7 +169,7 @@ OPTIONAL FLAGS instance has a machine-type, cpu-count must have the same value as the vCPU count in the machine-type. Eg: if machine-type is c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, - 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. + 2, 4, 8, 14, 16, 22, 32, 44, 48, 64, 72, 88, 96, 128, 144, 192, 288. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an @@ -216,7 +216,9 @@ OPTIONAL FLAGS c4-highmem-48-lssd, c4-highmem-96-lssd, c4-highmem-144-lssd, c4-highmem-192-lssd, c4-highmem-288-lssd, z3-highmem-14-standardlssd, z3-highmem-22-standardlssd, z3-highmem-44-standardlssd, - z3-highmem-88-standardlssd. + z3-highmem-88-standardlssd, z3-highmem-8-highlssd, + z3-highmem-16-highlssd, z3-highmem-22-highlssd, z3-highmem-32-highlssd, + z3-highmem-44-highlssd. --[no-]observability-config-enabled Enable enhanced query insights feature. Use diff --git a/gcloud/beta/api-registry/help b/gcloud/beta/api-registry/help new file mode 100644 index 000000000..207c49671 --- /dev/null +++ b/gcloud/beta/api-registry/help @@ -0,0 +1,26 @@ +NAME + gcloud beta api-registry - manage Cloud API Registry Command Group + +SYNOPSIS + gcloud beta api-registry GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Commands for managing Cloud API Registry. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + mcp + (BETA) Manage MCP Command Group. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha api-registry + diff --git a/gcloud/beta/api-registry/mcp/disable b/gcloud/beta/api-registry/mcp/disable new file mode 100644 index 000000000..f774d6cfb --- /dev/null +++ b/gcloud/beta/api-registry/mcp/disable @@ -0,0 +1,28 @@ +NAME + gcloud beta api-registry mcp disable - disables MCP server for a given + service in the current project + +SYNOPSIS + gcloud beta api-registry mcp disable SERVICE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Disables MCP server for a given service in the current project. + +POSITIONAL ARGUMENTS + SERVICE + The MCP server to disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha api-registry mcp disable + diff --git a/gcloud/beta/beyondcorp/operations/help b/gcloud/beta/api-registry/mcp/enable similarity index 51% rename from gcloud/beta/beyondcorp/operations/help rename to gcloud/beta/api-registry/mcp/enable index 78c51407a..e1609dd35 100644 --- a/gcloud/beta/beyondcorp/operations/help +++ b/gcloud/beta/api-registry/mcp/enable @@ -1,11 +1,16 @@ NAME - gcloud beta beyondcorp operations - manage Operation resources + gcloud beta api-registry mcp enable - enables MCP server for a given + service in the current project SYNOPSIS - gcloud beta beyondcorp operations [GCLOUD_WIDE_FLAG ...] + gcloud beta api-registry mcp enable SERVICE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Manage Operation resources. + (BETA) Enables MCP server for a given service in the current project. + +POSITIONAL ARGUMENTS + SERVICE + The MCP server to enable. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -16,5 +21,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha api-registry mcp enable diff --git a/gcloud/beta/api-registry/mcp/help b/gcloud/beta/api-registry/mcp/help new file mode 100644 index 000000000..994742a4f --- /dev/null +++ b/gcloud/beta/api-registry/mcp/help @@ -0,0 +1,39 @@ +NAME + gcloud beta api-registry mcp - manage MCP Command Group + +SYNOPSIS + gcloud beta api-registry mcp GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Commands for managing MCP enablement and disablement for a given + service in the current project. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + servers + (BETA) Manage Cloud API Registry MCP servers. + + tools + (BETA) Manage Cloud API Registry MCP tools. + +COMMANDS + COMMAND is one of the following: + + disable + (BETA) Disables MCP server for a given service in the current project. + + enable + (BETA) Enables MCP server for a given service in the current project. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha api-registry mcp + diff --git a/gcloud/beta/api-registry/mcp/servers/help b/gcloud/beta/api-registry/mcp/servers/help new file mode 100644 index 000000000..119048a81 --- /dev/null +++ b/gcloud/beta/api-registry/mcp/servers/help @@ -0,0 +1,27 @@ +NAME + gcloud beta api-registry mcp servers - manage Cloud API Registry MCP + servers + +SYNOPSIS + gcloud beta api-registry mcp servers COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Cloud API Registry MCP servers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (BETA) List MCP servers. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha api-registry mcp servers + diff --git a/gcloud/beta/api-registry/mcp/servers/list b/gcloud/beta/api-registry/mcp/servers/list new file mode 100644 index 000000000..bc662a97c --- /dev/null +++ b/gcloud/beta/api-registry/mcp/servers/list @@ -0,0 +1,67 @@ +NAME + gcloud beta api-registry mcp servers list - list MCP servers + +SYNOPSIS + gcloud beta api-registry mcp servers list [--all] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List MCP servers. + +EXAMPLES + To list all MCP servers in a project, run: + + $ gcloud beta api-registry mcp servers list + +FLAGS + --all + If provided, list all the available (both enabled and non-enabled) MCP + servers for the project. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha api-registry mcp servers list + diff --git a/gcloud/beta/api-registry/mcp/tools/help b/gcloud/beta/api-registry/mcp/tools/help new file mode 100644 index 000000000..cd6fc958c --- /dev/null +++ b/gcloud/beta/api-registry/mcp/tools/help @@ -0,0 +1,26 @@ +NAME + gcloud beta api-registry mcp tools - manage Cloud API Registry MCP tools + +SYNOPSIS + gcloud beta api-registry mcp tools COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Cloud API Registry MCP tools. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (BETA) List MCP tools. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha api-registry mcp tools + diff --git a/gcloud/beta/api-registry/mcp/tools/list b/gcloud/beta/api-registry/mcp/tools/list new file mode 100644 index 000000000..6c87a7d2c --- /dev/null +++ b/gcloud/beta/api-registry/mcp/tools/list @@ -0,0 +1,67 @@ +NAME + gcloud beta api-registry mcp tools list - list MCP tools + +SYNOPSIS + gcloud beta api-registry mcp tools list [--all] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List MCP tools. + +EXAMPLES + To list MCP tools, run: + + $ gcloud beta api-registry mcp tools list + +FLAGS + --all + If provided, list all the available MCP tools for all (both enabled and + non-enabled) the MCP Servers for the project. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha api-registry mcp tools list + diff --git a/gcloud/beta/beyondcorp/help b/gcloud/beta/beyondcorp/help index 253870bb2..e2911ed52 100644 --- a/gcloud/beta/beyondcorp/help +++ b/gcloud/beta/beyondcorp/help @@ -34,15 +34,14 @@ GROUPS (BETA) Provides context-aware access to non-web applications (Deprecated). - operations - (BETA) Manage Operation resources. - security-gateways (BETA) Manage Security Gateway resources. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud beyondcorp $ gcloud alpha beyondcorp diff --git a/gcloud/beta/beyondcorp/security-gateways/applications/create b/gcloud/beta/beyondcorp/security-gateways/applications/create index 36e331df8..dc3bdcb9a 100644 --- a/gcloud/beta/beyondcorp/security-gateways/applications/create +++ b/gcloud/beta/beyondcorp/security-gateways/applications/create @@ -5,9 +5,9 @@ NAME SYNOPSIS gcloud beta beyondcorp security-gateways applications create (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) - --endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] [--async] - [--display-name=DISPLAY_NAME] [--request-id=REQUEST_ID] - [--schema=SCHEMA] + [--async] [--display-name=DISPLAY_NAME] + [--endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS]] + [--request-id=REQUEST_ID] [--schema=SCHEMA] [--upstreams=[egressPolicy=EGRESSPOLICY], [external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL]] [GCLOUD_WIDE_FLAG ...] @@ -61,23 +61,33 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --security-gateway on the command line. -REQUIRED FLAGS - --endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] - Required, Endpoint matchers associated with an application. A - combination of hostname and ports as endpoint matchers is used to match - the application. Match conditions for OR logic. An array of match - conditions to allow for multiple matching criteria. The rule is - considered a match if one of the conditions is met. The conditions - should be the following combination: (Hostname & Ports) +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. - EXAMPLES: Hostname and Ports - (".example.com", "443"), ("example.com" - and "22"), ("example.com" and "22,33") etc. + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the application resource. Cannot + exceed 64 characters. + + --endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] + An array of conditions to match the application's network endpoint. + Each element in the array is an EndpointMatcher object, which defines a + specific combination of a hostname pattern and one or more ports. The + application is considered matched if at least one of the + EndpointMatcher conditions in this array is met (the conditions are + combined using OR logic). Each EndpointMatcher must contain a hostname + pattern, such as "example.com", and one or more port numbers specified + as a string, such as "443". + + Hostname and port number examples: ".example.com", "443" "example.com" + and "22" "example.com" and "22,33". hostname Hostname of the application. ports - Ports of the application. + The ports of the application. Shorthand Example: @@ -91,15 +101,6 @@ REQUIRED FLAGS --endpoint-matchers=path_to_file.(yaml|json) -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --display-name=DISPLAY_NAME - An arbitrary user-provided name for the application resource. Cannot - exceed 64 characters. - --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to @@ -158,35 +159,35 @@ OPTIONAL FLAGS Configuration for the contextual headers. deviceInfo - Device info configuration. + The device information configuration. outputType - The output type of the delegated device info. + The output type details for the delegated device. groupInfo - Group info configuration. + Group details. outputType - The output type of the delegated group info. + The output type of the delegated group information. outputType Default output type for all enabled headers. userInfo - User info configuration. + User details. outputType - The output type of the delegated user info. + The delegated user's information. gatewayIdentity - Gateway identity configuration. + The security gateway identity configuration. metadataHeaders Custom resource specific headers along with the values. The - names should conform to RFC 9110: > Field names SHOULD - constrain themselves to alphanumeric characters, "-", and ".", - and SHOULD begin with a letter. Field values SHOULD contain - only ASCII printable characters and tab. + names should conform to RFC 9110: >Field names can contain + alphanumeric characters, hyphens, and periods, can contain only + ASCII-printable characters and tabs, and must start with a + letter. KEY Sets KEY value. @@ -219,5 +220,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways applications create diff --git a/gcloud/beta/beyondcorp/security-gateways/applications/delete b/gcloud/beta/beyondcorp/security-gateways/applications/delete index f55200fec..25b1b884d 100644 --- a/gcloud/beta/beyondcorp/security-gateways/applications/delete +++ b/gcloud/beta/beyondcorp/security-gateways/applications/delete @@ -94,5 +94,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways applications delete diff --git a/gcloud/beta/beyondcorp/security-gateways/applications/describe b/gcloud/beta/beyondcorp/security-gateways/applications/describe index b09e95edb..3af089133 100644 --- a/gcloud/beta/beyondcorp/security-gateways/applications/describe +++ b/gcloud/beta/beyondcorp/security-gateways/applications/describe @@ -71,5 +71,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways applications describe diff --git a/gcloud/beta/beyondcorp/security-gateways/applications/get-iam-policy b/gcloud/beta/beyondcorp/security-gateways/applications/get-iam-policy index 0c484e182..f21675995 100644 --- a/gcloud/beta/beyondcorp/security-gateways/applications/get-iam-policy +++ b/gcloud/beta/beyondcorp/security-gateways/applications/get-iam-policy @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta beyondcorp security-gateways applications get-iam-policy - (APPLICATION : --location=LOCATION --security_gateway=SECURITY_GATEWAY) + (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -51,13 +51,13 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --location on the command line. - --security_gateway=SECURITY_GATEWAY + --security-gateway=SECURITY_GATEWAY The securityGateway id of the application resource. - To set the security_gateway attribute: + To set the security-gateway attribute: ▸ provide the argument application on the command line with a fully specified name; - ▸ provide the argument --security_gateway on the command line. + ▸ provide the argument --security-gateway on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -98,5 +98,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways applications get-iam-policy diff --git a/gcloud/beta/beyondcorp/security-gateways/applications/help b/gcloud/beta/beyondcorp/security-gateways/applications/help index dfe2f85a8..1a3efb90b 100644 --- a/gcloud/beta/beyondcorp/security-gateways/applications/help +++ b/gcloud/beta/beyondcorp/security-gateways/applications/help @@ -39,5 +39,8 @@ COMMANDS (BETA) Update applications. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways applications diff --git a/gcloud/beta/beyondcorp/security-gateways/applications/list b/gcloud/beta/beyondcorp/security-gateways/applications/list index 8a3ef6424..3a8414d0a 100644 --- a/gcloud/beta/beyondcorp/security-gateways/applications/list +++ b/gcloud/beta/beyondcorp/security-gateways/applications/list @@ -96,5 +96,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways applications list diff --git a/gcloud/beta/beyondcorp/security-gateways/applications/set-iam-policy b/gcloud/beta/beyondcorp/security-gateways/applications/set-iam-policy index 28aee09f8..16283a7ea 100644 --- a/gcloud/beta/beyondcorp/security-gateways/applications/set-iam-policy +++ b/gcloud/beta/beyondcorp/security-gateways/applications/set-iam-policy @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta beyondcorp security-gateways applications set-iam-policy - (APPLICATION : --location=LOCATION --security_gateway=SECURITY_GATEWAY) + (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) POLICY_FILE [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -52,13 +52,13 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --location on the command line. - --security_gateway=SECURITY_GATEWAY + --security-gateway=SECURITY_GATEWAY The securityGateway id of the application resource. - To set the security_gateway attribute: + To set the security-gateway attribute: ▸ provide the argument application on the command line with a fully specified name; - ▸ provide the argument --security_gateway on the command line. + ▸ provide the argument --security-gateway on the command line. POLICY_FILE Path to a local JSON or YAML formatted file containing a valid policy. @@ -80,5 +80,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways applications set-iam-policy diff --git a/gcloud/beta/beyondcorp/security-gateways/applications/update b/gcloud/beta/beyondcorp/security-gateways/applications/update index 198307eb5..98f0fc407 100644 --- a/gcloud/beta/beyondcorp/security-gateways/applications/update +++ b/gcloud/beta/beyondcorp/security-gateways/applications/update @@ -108,22 +108,24 @@ FLAGS At most one of these can be specified: --endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] - Set endpoint_matchers to new value. Endpoint matchers associated with - an application. A combination of hostname and ports as endpoint - matchers is used to match the application. Match conditions for OR - logic. An array of match conditions to allow for multiple matching - criteria. The rule is considered a match if one of the conditions is - met. The conditions should be the following combination: (Hostname & - Ports) + Set endpoint_matchers to new value. An array of conditions to match + the application's network endpoint. Each element in the array is an + EndpointMatcher object, which defines a specific combination of a + hostname pattern and one or more ports. The application is considered + matched if at least one of the EndpointMatcher conditions in this + array is met (the conditions are combined using OR logic). Each + EndpointMatcher must contain a hostname pattern, such as + "example.com", and one or more port numbers specified as a string, + such as "443". - EXAMPLES: Hostname and Ports - (".example.com", "443"), - ("example.com" and "22"), ("example.com" and "22,33") etc. + Hostname and port number examples: ".example.com", "443" + "example.com" and "22" "example.com" and "22,33". hostname Hostname of the application. ports - Ports of the application. + The ports of the application. Shorthand Example: @@ -138,22 +140,24 @@ FLAGS --endpoint-matchers=path_to_file.(yaml|json) --add-endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] - Add new value to endpoint_matchers list. Endpoint matchers associated - with an application. A combination of hostname and ports as endpoint - matchers is used to match the application. Match conditions for OR - logic. An array of match conditions to allow for multiple matching - criteria. The rule is considered a match if one of the conditions is - met. The conditions should be the following combination: (Hostname & - Ports) + Add new value to endpoint_matchers list. An array of conditions to + match the application's network endpoint. Each element in the array + is an EndpointMatcher object, which defines a specific combination of + a hostname pattern and one or more ports. The application is + considered matched if at least one of the EndpointMatcher conditions + in this array is met (the conditions are combined using OR logic). + Each EndpointMatcher must contain a hostname pattern, such as + "example.com", and one or more port numbers specified as a string, + such as "443". - EXAMPLES: Hostname and Ports - (".example.com", "443"), - ("example.com" and "22"), ("example.com" and "22,33") etc. + Hostname and port number examples: ".example.com", "443" + "example.com" and "22" "example.com" and "22,33". hostname Hostname of the application. ports - Ports of the application. + The ports of the application. Shorthand Example: @@ -173,22 +177,24 @@ FLAGS Clear endpoint_matchers value and set to empty list. --remove-endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] - Remove existing value from endpoint_matchers list. Endpoint - matchers associated with an application. A combination of hostname - and ports as endpoint matchers is used to match the application. - Match conditions for OR logic. An array of match conditions to - allow for multiple matching criteria. The rule is considered a - match if one of the conditions is met. The conditions should be the - following combination: (Hostname & Ports) + Remove existing value from endpoint_matchers list. An array of + conditions to match the application's network endpoint. Each + element in the array is an EndpointMatcher object, which defines a + specific combination of a hostname pattern and one or more ports. + The application is considered matched if at least one of the + EndpointMatcher conditions in this array is met (the conditions are + combined using OR logic). Each EndpointMatcher must contain a + hostname pattern, such as "example.com", and one or more port + numbers specified as a string, such as "443". - EXAMPLES: Hostname and Ports - (".example.com", "443"), - ("example.com" and "22"), ("example.com" and "22,33") etc. + Hostname and port number examples: ".example.com", "443" + "example.com" and "22" "example.com" and "22,33". hostname Hostname of the application. ports - Ports of the application. + The ports of the application. Shorthand Example: @@ -249,35 +255,35 @@ FLAGS Configuration for the contextual headers. deviceInfo - Device info configuration. + The device information configuration. outputType - The output type of the delegated device info. + The output type details for the delegated device. groupInfo - Group info configuration. + Group details. outputType - The output type of the delegated group info. + The output type of the delegated group information. outputType Default output type for all enabled headers. userInfo - User info configuration. + User details. outputType - The output type of the delegated user info. + The delegated user's information. gatewayIdentity - Gateway identity configuration. + The security gateway identity configuration. metadataHeaders Custom resource specific headers along with the values. The - names should conform to RFC 9110: > Field names SHOULD - constrain themselves to alphanumeric characters, "-", and - ".", and SHOULD begin with a letter. Field values SHOULD - contain only ASCII printable characters and tab. + names should conform to RFC 9110: >Field names can contain + alphanumeric characters, hyphens, and periods, can contain + only ASCII-printable characters and tabs, and must start with + a letter. KEY Sets KEY value. @@ -340,35 +346,35 @@ FLAGS Configuration for the contextual headers. deviceInfo - Device info configuration. + The device information configuration. outputType - The output type of the delegated device info. + The output type details for the delegated device. groupInfo - Group info configuration. + Group details. outputType - The output type of the delegated group info. + The output type of the delegated group information. outputType Default output type for all enabled headers. userInfo - User info configuration. + User details. outputType - The output type of the delegated user info. + The delegated user's information. gatewayIdentity - Gateway identity configuration. + The security gateway identity configuration. metadataHeaders Custom resource specific headers along with the values. The - names should conform to RFC 9110: > Field names SHOULD - constrain themselves to alphanumeric characters, "-", and - ".", and SHOULD begin with a letter. Field values SHOULD - contain only ASCII printable characters and tab. + names should conform to RFC 9110: >Field names can contain + alphanumeric characters, hyphens, and periods, can contain + only ASCII-printable characters and tabs, and must start with + a letter. KEY Sets KEY value. @@ -436,35 +442,35 @@ FLAGS Configuration for the contextual headers. deviceInfo - Device info configuration. + The device information configuration. outputType - The output type of the delegated device info. + The output type details for the delegated device. groupInfo - Group info configuration. + Group details. outputType - The output type of the delegated group info. + The output type of the delegated group information. outputType Default output type for all enabled headers. userInfo - User info configuration. + User details. outputType - The output type of the delegated user info. + The delegated user's information. gatewayIdentity - Gateway identity configuration. + The security gateway identity configuration. metadataHeaders Custom resource specific headers along with the values. The - names should conform to RFC 9110: > Field names SHOULD - constrain themselves to alphanumeric characters, "-", and - ".", and SHOULD begin with a letter. Field values SHOULD - contain only ASCII printable characters and tab. + names should conform to RFC 9110: >Field names can contain + alphanumeric characters, hyphens, and periods, can contain + only ASCII-printable characters and tabs, and must start + with a letter. KEY Sets KEY value. @@ -497,5 +503,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways applications update diff --git a/gcloud/beta/beyondcorp/security-gateways/create b/gcloud/beta/beyondcorp/security-gateways/create index f41f17041..df3195ccc 100644 --- a/gcloud/beta/beyondcorp/security-gateways/create +++ b/gcloud/beta/beyondcorp/security-gateways/create @@ -104,7 +104,7 @@ FLAGS This must be specified. --resource-override-path=RESOURCE_OVERRIDE_PATH - Contains uri path fragment where HTTP request is sent. + Contains the URI path fragment where HTTP request is sent. The configuration for the proxy. @@ -115,7 +115,7 @@ FLAGS Client IP configuration. The client IP address is included if true. --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY - Gateway identity configuration. + The security gateway identity configuration. PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY must be (only one value is supported): @@ -125,10 +125,9 @@ FLAGS --proxy-protocol-config-metadata-headers=[PROXY_PROTOCOL_CONFIG_METADATA_HEADERS,...] Custom resource specific headers along with the values. The names - should conform to RFC 9110: > Field names SHOULD constrain themselves - to alphanumeric characters, "-", and ".", and SHOULD begin with a - letter. Field values SHOULD contain only ASCII printable characters - and tab. + should conform to RFC 9110: >Field names can contain alphanumeric + characters, hyphens, and periods, can contain only ASCII-printable + characters and tabs, and must start with a letter. KEY Sets KEY value. @@ -161,10 +160,10 @@ FLAGS protobuf Protobuf output type. - Delegated device info configuration. + The delegated device information configuration. --device-info-output-type=DEVICE_INFO_OUTPUT_TYPE - The output type of the delegated device info. + The output type details for the delegated device. DEVICE_INFO_OUTPUT_TYPE must be one of: json @@ -174,10 +173,10 @@ FLAGS protobuf Protobuf output type. - Delegated group info configuration. + The delegated group configuration details. --group-info-output-type=GROUP_INFO_OUTPUT_TYPE - The output type of the delegated group info. + The output type of the delegated group information. GROUP_INFO_OUTPUT_TYPE must be one of: json @@ -187,11 +186,11 @@ FLAGS protobuf Protobuf output type. - Delegated user info configuration. + The configuration information for the delegated user. --user-info-output-type=USER_INFO_OUTPUT_TYPE - The output type of the delegated user info. USER_INFO_OUTPUT_TYPE - must be one of: + The delegated user's information. USER_INFO_OUTPUT_TYPE must be + one of: json JSON output type. @@ -213,5 +212,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways create diff --git a/gcloud/beta/beyondcorp/security-gateways/delete b/gcloud/beta/beyondcorp/security-gateways/delete index 21dcd7c98..610fc63f8 100644 --- a/gcloud/beta/beyondcorp/security-gateways/delete +++ b/gcloud/beta/beyondcorp/security-gateways/delete @@ -85,5 +85,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways delete diff --git a/gcloud/beta/beyondcorp/security-gateways/describe b/gcloud/beta/beyondcorp/security-gateways/describe index 4d8c86ad3..30c784b96 100644 --- a/gcloud/beta/beyondcorp/security-gateways/describe +++ b/gcloud/beta/beyondcorp/security-gateways/describe @@ -62,5 +62,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways describe diff --git a/gcloud/beta/beyondcorp/security-gateways/get-iam-policy b/gcloud/beta/beyondcorp/security-gateways/get-iam-policy index 7bf5073db..356f738a0 100644 --- a/gcloud/beta/beyondcorp/security-gateways/get-iam-policy +++ b/gcloud/beta/beyondcorp/security-gateways/get-iam-policy @@ -90,5 +90,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways get-iam-policy diff --git a/gcloud/beta/beyondcorp/security-gateways/help b/gcloud/beta/beyondcorp/security-gateways/help index 84825ecc8..738ef5c9e 100644 --- a/gcloud/beta/beyondcorp/security-gateways/help +++ b/gcloud/beta/beyondcorp/security-gateways/help @@ -45,5 +45,8 @@ COMMANDS (BETA) Update securityGateways. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways diff --git a/gcloud/beta/beyondcorp/security-gateways/list b/gcloud/beta/beyondcorp/security-gateways/list index dd943006d..017209175 100644 --- a/gcloud/beta/beyondcorp/security-gateways/list +++ b/gcloud/beta/beyondcorp/security-gateways/list @@ -81,5 +81,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways list diff --git a/gcloud/beta/beyondcorp/security-gateways/set-iam-policy b/gcloud/beta/beyondcorp/security-gateways/set-iam-policy index 8c79c0426..fee656c74 100644 --- a/gcloud/beta/beyondcorp/security-gateways/set-iam-policy +++ b/gcloud/beta/beyondcorp/security-gateways/set-iam-policy @@ -71,5 +71,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways set-iam-policy diff --git a/gcloud/beta/beyondcorp/security-gateways/update b/gcloud/beta/beyondcorp/security-gateways/update index 76b2bd7e7..d94950725 100644 --- a/gcloud/beta/beyondcorp/security-gateways/update +++ b/gcloud/beta/beyondcorp/security-gateways/update @@ -100,7 +100,7 @@ FLAGS --no-proxy-protocol-config-client-ip to disable. --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY - Gateway identity configuration. + The security gateway identity configuration. PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY must be (only one value is supported): @@ -121,10 +121,10 @@ FLAGS protobuf Protobuf output type. - Delegated device info configuration. + The delegated device information configuration. --device-info-output-type=DEVICE_INFO_OUTPUT_TYPE - The output type of the delegated device info. + The output type details for the delegated device. DEVICE_INFO_OUTPUT_TYPE must be one of: json @@ -134,10 +134,10 @@ FLAGS protobuf Protobuf output type. - Delegated group info configuration. + The delegated group configuration details. --group-info-output-type=GROUP_INFO_OUTPUT_TYPE - The output type of the delegated group info. + The output type of the delegated group information. GROUP_INFO_OUTPUT_TYPE must be one of: json @@ -147,11 +147,11 @@ FLAGS protobuf Protobuf output type. - Delegated user info configuration. + The configuration information for the delegated user. --user-info-output-type=USER_INFO_OUTPUT_TYPE - The output type of the delegated user info. USER_INFO_OUTPUT_TYPE - must be one of: + The delegated user's information. USER_INFO_OUTPUT_TYPE must be + one of: json JSON output type. @@ -187,10 +187,9 @@ FLAGS --proxy-protocol-config-metadata-headers=[PROXY_PROTOCOL_CONFIG_METADATA_HEADERS,...] Set proxy_protocol_config_metadata_headers to new value. Custom resource specific headers along with the values. The names should - conform to RFC 9110: > Field names SHOULD constrain themselves to - alphanumeric characters, "-", and ".", and SHOULD begin with a - letter. Field values SHOULD contain only ASCII printable characters - and tab. + conform to RFC 9110: >Field names can contain alphanumeric + characters, hyphens, and periods, can contain only ASCII-printable + characters and tabs, and must start with a letter. KEY Sets KEY value. @@ -213,10 +212,9 @@ FLAGS --update-proxy-protocol-config-metadata-headers=[UPDATE_PROXY_PROTOCOL_CONFIG_METADATA_HEADERS,...] Update proxy_protocol_config_metadata_headers value or add key value pair. Custom resource specific headers along with the values. - The names should conform to RFC 9110: > Field names SHOULD - constrain themselves to alphanumeric characters, "-", and ".", and - SHOULD begin with a letter. Field values SHOULD contain only ASCII - printable characters and tab. + The names should conform to RFC 9110: >Field names can contain + alphanumeric characters, hyphens, and periods, can contain only + ASCII-printable characters and tabs, and must start with a letter. KEY Sets KEY value. @@ -271,7 +269,7 @@ FLAGS API operation descriptor. --resource-override-path=RESOURCE_OVERRIDE_PATH - Contains uri path fragment where HTTP request is sent. + Contains the URI path fragment where HTTP request is sent. Update hubs. @@ -355,5 +353,8 @@ API REFERENCE API can be found at: https://cloud.google.com/ NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways update diff --git a/gcloud/beta/composer/environments/create b/gcloud/beta/composer/environments/create index 68ff0f07b..6f5cd63ff 100644 --- a/gcloud/beta/composer/environments/create +++ b/gcloud/beta/composer/environments/create @@ -173,8 +173,8 @@ FLAGS --environment-size=ENVIRONMENT_SIZE Size of the environment. Unspecified means that the default option will - be chosen. ENVIRONMENT_SIZE must be one of: large, medium, small, - unspecified. + be chosen. ENVIRONMENT_SIZE must be one of: extra-large, large, medium, + small, unspecified. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/beta/composer/environments/update b/gcloud/beta/composer/environments/update index 3891978c5..fd0200098 100644 --- a/gcloud/beta/composer/environments/update +++ b/gcloud/beta/composer/environments/update @@ -140,8 +140,8 @@ REQUIRED FLAGS --environment-size=ENVIRONMENT_SIZE Size of the environment. Unspecified means that the default option - will be chosen. ENVIRONMENT_SIZE must be one of: large, medium, - small, unspecified. + will be chosen. ENVIRONMENT_SIZE must be one of: extra-large, large, + medium, small, unspecified. --node-count=NODE_COUNT The new number of nodes running the environment. Must be >= 3. diff --git a/gcloud/beta/container/backup-restore/restore-plans/create b/gcloud/beta/container/backup-restore/restore-plans/create index 9b3f95fa4..8194ae913 100644 --- a/gcloud/beta/container/backup-restore/restore-plans/create +++ b/gcloud/beta/container/backup-restore/restore-plans/create @@ -130,9 +130,9 @@ OPTIONAL FLAGS resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: use-backup-version - Selecting 'use-existing-version' means deleting the existing - version of the conflicting resources before re-creating them from - the Backup. + Selecting 'use-backup-version' means deleting the existing version + of the conflicting resources before re-creating them from the + Backup. Note that this is a dangerous option which could cause unintentional data loss if used inappropriately. For example, diff --git a/gcloud/beta/container/backup-restore/restore-plans/update b/gcloud/beta/container/backup-restore/restore-plans/update index a2b25626b..aa500ba47 100644 --- a/gcloud/beta/container/backup-restore/restore-plans/update +++ b/gcloud/beta/container/backup-restore/restore-plans/update @@ -84,9 +84,9 @@ FLAGS resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: use-backup-version - Selecting 'use-existing-version' means deleting the existing - version of the conflicting resources before re-creating them from - the Backup. + Selecting 'use-backup-version' means deleting the existing version + of the conflicting resources before re-creating them from the + Backup. Note that this is a dangerous option which could cause unintentional data loss if used inappropriately. For example, diff --git a/gcloud/beta/container/clusters/complete-control-plane-upgrade b/gcloud/beta/container/clusters/complete-control-plane-upgrade new file mode 100644 index 000000000..defc42e18 --- /dev/null +++ b/gcloud/beta/container/clusters/complete-control-plane-upgrade @@ -0,0 +1,54 @@ +NAME + gcloud beta container clusters complete-control-plane-upgrade - complete + the control plane upgrade for an existing cluster + +SYNOPSIS + gcloud beta container clusters complete-control-plane-upgrade NAME + [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Complete the control plane upgrade for an existing cluster. + +EXAMPLES + To complete the control plane upgrade for an existing cluster, run: + + $ gcloud beta container clusters complete-control-plane-upgrade \ + sample-cluster + +POSITIONAL ARGUMENTS + NAME + The name of your existing cluster. + +FLAGS + At most one of these can be specified: + + --location=LOCATION + Compute zone or region (e.g. us-central1-a or us-central1) for the + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. + + --region=REGION + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. + + --zone=ZONE, -z ZONE + Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the + default compute/zone property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container clusters complete-control-plane-upgrade + diff --git a/gcloud/beta/container/clusters/help b/gcloud/beta/container/clusters/help index b1194ba53..eb7320747 100644 --- a/gcloud/beta/container/clusters/help +++ b/gcloud/beta/container/clusters/help @@ -43,6 +43,9 @@ COMMANDS check-autopilot-compatibility (BETA) Check autopilot compatibility of a running cluster. + complete-control-plane-upgrade + (BETA) Complete the control plane upgrade for an existing cluster. + create (BETA) Create a cluster for running containers. diff --git a/gcloud/beta/container/clusters/upgrade b/gcloud/beta/container/clusters/upgrade index 5ed9e62bf..b70042757 100644 --- a/gcloud/beta/container/clusters/upgrade +++ b/gcloud/beta/container/clusters/upgrade @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud beta container clusters upgrade NAME [--async] - [--cluster-version=CLUSTER_VERSION] [--image-type=IMAGE_TYPE] - [--master] [--node-pool=NODE_POOL] + [--cluster-version=CLUSTER_VERSION] + [--control-plane-soak-duration=CONTROL_PLANE_SOAK_DURATION] + [--image-type=IMAGE_TYPE] [--master] [--node-pool=NODE_POOL] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...] @@ -69,6 +70,13 @@ FLAGS $ gcloud container get-server-config + --control-plane-soak-duration=CONTROL_PLANE_SOAK_DURATION + The soak duration for the rollback-able control plane upgrade. It only + applies to minor version upgrades. Setting this flag will trigger a + control plane upgrade with emulated version. The cluster is + rollback-able during the soak period. The soak period can be set + between 6 hours and 7 days. + --image-type=IMAGE_TYPE The image type to use for the cluster/node pool. Defaults to server-specified. diff --git a/gcloud/beta/datastream/streams/create b/gcloud/beta/datastream/streams/create index fc8df13e5..83b822ce4 100644 --- a/gcloud/beta/datastream/streams/create +++ b/gcloud/beta/datastream/streams/create @@ -21,8 +21,8 @@ SYNOPSIS | --postgresql-source-config=POSTGRESQL_SOURCE_CONFIG | --salesforce-source-config=SALESFORCE_SOURCE_CONFIG | --sqlserver-source-config=SQLSERVER_SOURCE_CONFIG)) - [--labels=[KEY=VALUE,...]] [--force | --validate-only] - [GCLOUD_WIDE_FLAG ...] + [--labels=[KEY=VALUE,...]] [--rule-sets=RULE_SETS] + [--force | --validate-only] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) (DEPRECATED) Datastream beta version is deprecated. Please @@ -538,6 +538,52 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --rule-sets=RULE_SETS + Path to a JSON file containing a list of rule sets to be applied to the + stream. + + The JSON file is formatted as follows, with camelCase field naming: + + [ + { + "objectFilter": { + "sourceObjectIdentifier": { + "oracleIdentifier": { + "schema": "schema1", + "table": "table1" + } + } + }, + "customizationRules": [ + { + "bigqueryClustering": { + "columns": ["COL_A"] + } + } + ] + }, + { + "objectFilter": { + "sourceObjectIdentifier": { + "oracleIdentifier": { + "schema": "schema2", + "table": "table2" + } + } + }, + "customizationRules": [ + { + "bigqueryPartitioning": { + "timeUnitPartition": { + "column": "TIME_COL", + "partitioningTimeGranularity": "PARTITIONING_TIME_GRANULARITY_DAY" + } + } + } + ] + } + ] + At most one of these can be specified: --force diff --git a/gcloud/beta/datastream/streams/update b/gcloud/beta/datastream/streams/update index 1890f621e..14356eac2 100644 --- a/gcloud/beta/datastream/streams/update +++ b/gcloud/beta/datastream/streams/update @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud beta datastream streams update (STREAM : --location=LOCATION) - [--display-name=DISPLAY_NAME] [--state=STATE] + [--display-name=DISPLAY_NAME] [--rule-sets=RULE_SETS] [--state=STATE] [--update-labels=[KEY=VALUE,...]] [--update-mask=UPDATE_MASK] [--backfill-none | --backfill-all --mongodb-excluded-objects=MONGODB_EXCLUDED_OBJECTS @@ -87,6 +87,52 @@ FLAGS --display-name=DISPLAY_NAME Friendly name for the stream. + --rule-sets=RULE_SETS + Path to a JSON file containing a list of rule sets to be applied to the + stream. + + The JSON file is formatted as follows, with camelCase field naming: + + [ + { + "objectFilter": { + "sourceObjectIdentifier": { + "oracleIdentifier": { + "schema": "schema1", + "table": "table1" + } + } + }, + "customizationRules": [ + { + "bigqueryClustering": { + "columns": ["COL_A"] + } + } + ] + }, + { + "objectFilter": { + "sourceObjectIdentifier": { + "oracleIdentifier": { + "schema": "schema2", + "table": "table2" + } + } + }, + "customizationRules": [ + { + "bigqueryPartitioning": { + "timeUnitPartition": { + "column": "TIME_COL", + "partitioningTimeGranularity": "PARTITIONING_TIME_GRANULARITY_DAY" + } + } + } + ] + } + ] + --state=STATE Stream state, can be set to: "RUNNING" or "PAUSED". diff --git a/gcloud/beta/developer-connect/connections/create b/gcloud/beta/developer-connect/connections/create index e3e9133ce..ab113de48 100644 --- a/gcloud/beta/developer-connect/connections/create +++ b/gcloud/beta/developer-connect/connections/create @@ -118,10 +118,27 @@ FLAGS --location=LOCATION For resources [connection, + bitbucket-cloud-config-authorizer-credential-user-token-secret-version, + bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version, + bitbucket-cloud-config-webhook-secret-version, + bitbucket-data-center-config-authorizer-credential-user-token-secret-version, + bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version, bitbucket-data-center-config-service-directory, + bitbucket-data-center-config-webhook-secret-version, crypto-key-config-reference, + github-config-authorizer-credential-oauth-token-secret-version, + github-enterprise-config-private-key-secret-version, github-enterprise-config-service-directory, + github-enterprise-config-webhook-secret-version, + gitlab-config-authorizer-credential-user-token-secret-version, + gitlab-config-read-authorizer-credential-user-token-secret-version, + gitlab-config-webhook-secret-version, + gitlab-enterprise-config-authorizer-credential-user-token-secret-version, + gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version, gitlab-enterprise-config-service-directory, + gitlab-enterprise-config-webhook-secret-version, + http-config-basic-authentication-password-secret-version, + http-config-bearer-token-authentication-secret-version, http-config-service-directory], provides fallback value for resource location attribute. When the resource's full URI path is not provided, location will fallback to this flag value. @@ -187,7 +204,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -198,11 +217,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-cloud-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-cloud-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -210,7 +238,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-cloud-config-authorizer-credential-user-token-secret-version on the command line. @@ -222,7 +250,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -233,11 +263,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -245,14 +284,16 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version on the command line. SecretVersion resource - SecretManager resource containing the webhook secret used to verify webhook events, formatted as - projects/*/secrets/*/versions/*. This is used to validate and create + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This is used to validate and create webhooks. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -263,11 +304,20 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --bitbucket-cloud-config-webhook-secret-version on the command line + with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --bitbucket-cloud-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -275,7 +325,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --bitbucket-cloud-config-webhook-secret-version on the command line. @@ -293,7 +343,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -304,11 +356,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-data-center-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-data-center-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -316,7 +377,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-data-center-config-authorizer-credential-user-token-secret-version on the command line. @@ -331,7 +392,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -342,11 +405,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -354,15 +426,17 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version on the command line. SecretVersion resource - SecretManager resource containing the webhook secret used to verify webhook events, formatted as - projects/*/secrets/*/versions/*. This is used to validate webhooks. - This represents a Cloud resource. (NOTE) Some attributes are not given + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This is used to validate webhooks. 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: @@ -372,11 +446,20 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --bitbucket-data-center-config-webhook-secret-version on the + command line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --bitbucket-data-center-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -384,7 +467,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --bitbucket-data-center-config-webhook-secret-version on the command line. @@ -441,6 +524,8 @@ FLAGS The Developer Connect GitHub Application. firebase The Firebase GitHub Application. + gemini-code-assist + The Gemini Code Assist Application. This flag argument must be specified if any of the other arguments in this group are specified. @@ -453,7 +538,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the OAuth token that authorizes the connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -464,11 +551,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --github-config-authorizer-credential-oauth-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --github-config-authorizer-credential-oauth-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -476,7 +572,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --github-config-authorizer-credential-oauth-token-secret-version on the command line. @@ -496,9 +592,11 @@ FLAGS ID of the installation of the GitHub App. SecretVersion resource - SecretManager resource containing the private - key of the GitHub App, formatted as projects/*/secrets/*/versions/*. - This represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + key of the GitHub App, formatted as projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) + Some attributes are not given arguments in this group but can be set + in other ways. To set the project attribute: ▫ provide the argument @@ -507,17 +605,26 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --github-enterprise-config-private-key-secret-version on the + command line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --github-enterprise-config-private-key-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --github-enterprise-config-private-key-secret-version on the command line. @@ -564,8 +671,9 @@ FLAGS SSL certificate to use for requests to GitHub Enterprise. SecretVersion resource - SecretManager resource containing the webhook - secret of the GitHub App, formatted as - projects/*/secrets/*/versions/*. This represents a Cloud resource. + secret of the GitHub App, formatted as projects/*/secrets/*/versions/* + or projects/*/locations/*/secrets/*/versions/* (if regional secrets + are supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -576,17 +684,26 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --github-enterprise-config-webhook-secret-version on the command + line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --github-enterprise-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --github-enterprise-config-webhook-secret-version on the command line. @@ -600,7 +717,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -611,11 +730,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -623,7 +751,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-config-authorizer-credential-user-token-secret-version on the command line. @@ -635,7 +763,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -646,11 +776,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -658,15 +797,17 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-config-read-authorizer-credential-user-token-secret-version on the command line. SecretVersion resource - SecretManager resource containing the webhook secret of a GitLab project, formatted as - projects/*/secrets/*/versions/*. This is used to validate webhooks. - This represents a Cloud resource. (NOTE) Some attributes are not given + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This is used to validate webhooks. 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: @@ -675,10 +816,18 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument --gitlab-config-webhook-secret-version on + the command line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --gitlab-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -686,7 +835,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --gitlab-config-webhook-secret-version on the command line. @@ -699,7 +848,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -710,11 +861,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-enterprise-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-enterprise-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -722,7 +882,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-enterprise-config-authorizer-credential-user-token-secret-version on the command line. @@ -737,7 +897,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -748,11 +910,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -760,15 +931,17 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version on the command line. SecretVersion resource - SecretManager resource containing the webhook secret of a GitLab project, formatted as - projects/*/secrets/*/versions/*. This is used to validate webhooks. - This represents a Cloud resource. (NOTE) Some attributes are not given + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This is used to validate webhooks. 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: @@ -778,11 +951,20 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --gitlab-enterprise-config-webhook-secret-version on the command + line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --gitlab-enterprise-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -790,7 +972,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --gitlab-enterprise-config-webhook-secret-version on the command line. diff --git a/gcloud/beta/developer-connect/connections/update b/gcloud/beta/developer-connect/connections/update index 9e7f69e35..a36dab1cf 100644 --- a/gcloud/beta/developer-connect/connections/update +++ b/gcloud/beta/developer-connect/connections/update @@ -82,10 +82,23 @@ FLAGS --location=LOCATION For resources [connection, + bitbucket-cloud-config-authorizer-credential-user-token-secret-version, + bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version, + bitbucket-data-center-config-authorizer-credential-user-token-secret-version, + bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version, bitbucket-data-center-config-service-directory, crypto-key-config-reference, + github-config-authorizer-credential-oauth-token-secret-version, + github-enterprise-config-private-key-secret-version, github-enterprise-config-service-directory, + github-enterprise-config-webhook-secret-version, + gitlab-config-authorizer-credential-user-token-secret-version, + gitlab-config-read-authorizer-credential-user-token-secret-version, + gitlab-enterprise-config-authorizer-credential-user-token-secret-version, + gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version, gitlab-enterprise-config-service-directory, + http-config-basic-authentication-password-secret-version, + http-config-bearer-token-authentication-secret-version, http-config-service-directory], provides fallback value for resource location attribute. When the resource's full URI path is not provided, location will fallback to this flag value. @@ -215,7 +228,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -226,17 +241,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-cloud-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-cloud-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-cloud-config-authorizer-credential-user-token-secret-version on the command line. @@ -246,7 +270,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -257,17 +283,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version on the command line. @@ -286,7 +321,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -297,17 +334,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-data-center-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-data-center-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-data-center-config-authorizer-credential-user-token-secret-version on the command line. @@ -320,7 +366,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -331,17 +379,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version on the command line. @@ -402,7 +459,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the OAuth token that authorizes the connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -413,17 +472,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --github-config-authorizer-credential-oauth-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --github-config-authorizer-credential-oauth-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --github-config-authorizer-credential-oauth-token-secret-version on the command line. @@ -493,9 +561,11 @@ FLAGS github_enterprise_config_private_key_secret_version to new value. SecretManager resource containing the private key of the GitHub App, - formatted as projects/*/secrets/*/versions/*. This represents a - Cloud resource. (NOTE) Some attributes are not given arguments in - this group but can be set in other ways. + formatted as projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can + be set in other ways. To set the project attribute: ◇ provide the argument @@ -504,17 +574,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --github-enterprise-config-private-key-secret-version on the + command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --github-enterprise-config-private-key-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --github-enterprise-config-private-key-secret-version on the command line. @@ -531,9 +610,11 @@ FLAGS github_enterprise_config_webhook_secret_version to new value. SecretManager resource containing the webhook secret of the GitHub - App, formatted as projects/*/secrets/*/versions/*. This represents a - Cloud resource. (NOTE) Some attributes are not given arguments in - this group but can be set in other ways. + App, formatted as projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can + be set in other ways. To set the project attribute: ◇ provide the argument @@ -542,17 +623,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --github-enterprise-config-webhook-secret-version on the command + line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --github-enterprise-config-webhook-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --github-enterprise-config-webhook-secret-version on the command line. @@ -567,7 +657,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -578,17 +670,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-config-authorizer-credential-user-token-secret-version on the command line. @@ -598,7 +699,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -609,17 +712,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-config-read-authorizer-credential-user-token-secret-version on the command line. @@ -634,7 +746,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -645,17 +759,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-enterprise-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-enterprise-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-enterprise-config-authorizer-credential-user-token-secret-version on the command line. @@ -668,7 +791,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -679,17 +804,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version on the command line. diff --git a/gcloud/beta/filestore/instances/help b/gcloud/beta/filestore/instances/help index 1e69926ac..0dfbc5cc8 100644 --- a/gcloud/beta/filestore/instances/help +++ b/gcloud/beta/filestore/instances/help @@ -33,12 +33,18 @@ COMMANDS list (BETA) List Filestore instances. + pause-replica + (BETA) Pause a Filestore replica instance. + promote-replica (BETA) Promote a Filestore standby replication instance. restore (BETA) Restore a Filestore instance from a backup. + resume-replica + (BETA) Resume a Filestore replica instance. + revert (BETA) Revert a Filestore instance. diff --git a/gcloud/beta/filestore/instances/pause-replica b/gcloud/beta/filestore/instances/pause-replica new file mode 100644 index 000000000..32b631c30 --- /dev/null +++ b/gcloud/beta/filestore/instances/pause-replica @@ -0,0 +1,78 @@ +NAME + gcloud beta filestore instances pause-replica - pause a Filestore replica + instance + +SYNOPSIS + gcloud beta filestore instances pause-replica (INSTANCE : --zone=ZONE) + [--async] [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Pause a Filestore replica instance. This command can be called only + on a standby instance. After calling the command, the NFS file system of + the standby instance becomes writeable. Any data changed on the standby + instance while it is paused will be lost when the replica is resumed or + promoted. + +EXAMPLES + To pause a replica instance with the name my-replica-instance located + inus-central1-c, run: + + $ gcloud beta filestore instances pause-replica \ + my-replica-instance --zone=us-central1 + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Filestore + instance to pause. 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 instance 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. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --zone=ZONE + The zone of the Filestore instance. + + To set the zone attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line; + ▸ set the property filestore/zone. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --location=LOCATION + Location of the Filestore instance to pause. + +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 file/v1beta1 API. The full documentation for this API + can be found at: https://cloud.google.com/filestore/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/filestore/instances/resume-replica b/gcloud/beta/filestore/instances/resume-replica new file mode 100644 index 000000000..87e926b19 --- /dev/null +++ b/gcloud/beta/filestore/instances/resume-replica @@ -0,0 +1,78 @@ +NAME + gcloud beta filestore instances resume-replica - resume a Filestore replica + instance + +SYNOPSIS + gcloud beta filestore instances resume-replica (INSTANCE : --zone=ZONE) + [--async] [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Resume a Filestore replica instance. This command can be called only + on a paused standby instance. Any data written to the standby instance + while being paused will be lost when the replica is resumed. The NFS file + system of the standby instance becomes inaccessible and replication is + resumed. + +EXAMPLES + To resume a replica instance with the name my-replica-instance located + inus-central1-c , run: + + $ gcloud beta filestore instances resume-replica \ + my-replica-instance --zone=us-central1-c + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Filestore + instance to resume. 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 instance 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. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --zone=ZONE + The zone of the Filestore instance. + + To set the zone attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line; + ▸ set the property filestore/zone. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --location=LOCATION + Location of the Filestore instance to resume. + +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 file/v1beta1 API. The full documentation for this API + can be found at: https://cloud.google.com/filestore/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/firebase-data-connect/help b/gcloud/beta/firebase-data-connect/help new file mode 100644 index 000000000..3f9c194af --- /dev/null +++ b/gcloud/beta/firebase-data-connect/help @@ -0,0 +1,20 @@ +NAME + gcloud beta firebase-data-connect - manage Firebase Data Connect resources + +SYNOPSIS + gcloud beta firebase-data-connect GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Firebase Data Connect resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha firebase-data-connect + diff --git a/gcloud/beta/iam/access-policies/create b/gcloud/beta/iam/access-policies/create index 48bf214e5..13857c6df 100644 --- a/gcloud/beta/iam/access-policies/create +++ b/gcloud/beta/iam/access-policies/create @@ -26,13 +26,14 @@ POSITIONAL ARGUMENTS policy. The following formats are supported: - projects/{project_id}/locations/{location}/accessPolicies/{policy_id} - projects/{project_number}/locations/{location}/accessPolicies/{policy_id} - folders/{folder_id}/locations/{location}/accessPolicies/{policy_id} - organizations/{organization_id}/locations/{location}/accessPolicies/{policy_id} - 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. + + ◆ projects/{project_id}/locations/{location}/accessPolicies/{policy_id} + ◆ projects/{project_number}/locations/{location}/accessPolicies/{policy_id} + ◆ folders/{folder_id}/locations/{location}/accessPolicies/{policy_id} + ◆ organizations/{organization_id}/locations/{location}/accessPolicies/{policy_id} + 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 access_policy on the command line with a fully @@ -118,28 +119,20 @@ FLAGS conditions The conditions that determine whether this rule applies to a request. Conditions are identified by their key, which is the - FQDN of the service that they are relevant to, e.g.: + FQDN of the service that they are relevant to. For example: + "conditions": { "iam.googleapis.com": }. Each + rule is evaluated independently. If this rule does not apply to a + request, other rules might still apply. Currently supported keys + are as follows: - "conditions": { "iam.googleapis.com": } + ▫ eventarc.googleapis.com: Can use CEL functions that evaluate + resource fields. - Each rule is evaluated independently. If this rule does not apply - to a request, other rules might still apply. Currently supported - keys are: - - ▫ eventarc.googleapis.com// The conditions that determine - whether this rule applies to a request. Conditions are - identified by their key, which is the FQDN of the service that - they are relevant to, e.g.: - - "conditions": { "iam.googleapis.com": { "cel_condition": } } - - Each rule is evaluated independently. If this rule does not apply - to a request, other rules might still apply. Currently supported - keys are: - - ▫ eventarc.googleapis.com - ▫ iam.googleapis.com. + ▫ iam.googleapis.com: Can use CEL functions that evaluate + resource tags + (https://cloud.google.com/iam/help/conditions/resource-tags) + and combine them using boolean and logical operators. Other + functions and operators are not supported. KEY Sets KEY value. @@ -197,7 +190,7 @@ FLAGS Each permission uses the format {service_fqdn}/{resource}.{verb}, where {service_fqdn} is the fully qualified domain name for the service. Currently - supported permissions are: + supported permissions are as follows: ◇ eventarc.googleapis.com/messageBuses.publish. @@ -211,14 +204,16 @@ FLAGS user accounts. For example, principal://goog/subject/alice@example.com. - If an identifier that was previously set on a policy is soft deleted, then - calls to read that policy will return the identifier with a deleted - prefix. Users cannot set identifiers with this syntax. - * `deleted:principal://goog/subject/{email_id}?uid={uid}`: A specific - Google Account that was deleted recently. For example, - `deleted:principal://goog/subject/alice@example.com?uid=1234567890`. If - the Google Account is recovered, this identifier reverts to the standard - identifier for a Google Account. + If an identifier that was previously set on a policy is soft + deleted, then calls to read that policy will return the + identifier with a deleted prefix. Users cannot set identifiers + with this syntax. + + ▫ deleted:principal://goog/subject/{email_id}?uid={uid}: A + specific Google Account that was deleted recently. For example, + deleted:principal://goog/subject/alice@example.com?uid=1234567890. + If the Google Account is recovered, this identifier reverts to + the standard identifier for a Google Account. ▫ deleted:principalSet://goog/group/{group_id}?uid={uid}: A Google group that was deleted recently. For example, diff --git a/gcloud/beta/iam/access-policies/update b/gcloud/beta/iam/access-policies/update index c587667b9..75b781a2b 100644 --- a/gcloud/beta/iam/access-policies/update +++ b/gcloud/beta/iam/access-policies/update @@ -38,13 +38,14 @@ POSITIONAL ARGUMENTS policy. The following formats are supported: - projects/{project_id}/locations/{location}/accessPolicies/{policy_id} - projects/{project_number}/locations/{location}/accessPolicies/{policy_id} - folders/{folder_id}/locations/{location}/accessPolicies/{policy_id} - organizations/{organization_id}/locations/{location}/accessPolicies/{policy_id} - 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. + + ◆ projects/{project_id}/locations/{location}/accessPolicies/{policy_id} + ◆ projects/{project_number}/locations/{location}/accessPolicies/{policy_id} + ◆ folders/{folder_id}/locations/{location}/accessPolicies/{policy_id} + ◆ organizations/{organization_id}/locations/{location}/accessPolicies/{policy_id} + 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 access_policy on the command line with a fully @@ -199,28 +200,20 @@ FLAGS conditions The conditions that determine whether this rule applies to a request. Conditions are identified by their key, which is the - FQDN of the service that they are relevant to, e.g.: + FQDN of the service that they are relevant to. For example: + "conditions": { "iam.googleapis.com": }. Each + rule is evaluated independently. If this rule does not apply to + a request, other rules might still apply. Currently supported + keys are as follows: - "conditions": { "iam.googleapis.com": } + ◇ eventarc.googleapis.com: Can use CEL functions that + evaluate resource fields. - Each rule is evaluated independently. If this rule does not - apply to a request, other rules might still apply. Currently - supported keys are: - - ◇ eventarc.googleapis.com// The conditions that determine - whether this rule applies to a request. Conditions are - identified by their key, which is the FQDN of the service - that they are relevant to, e.g.: - - "conditions": { "iam.googleapis.com": { "cel_condition": } } - - Each rule is evaluated independently. If this rule does not - apply to a request, other rules might still apply. Currently - supported keys are: - - ◇ eventarc.googleapis.com - ◇ iam.googleapis.com. + ◇ iam.googleapis.com: Can use CEL functions that evaluate + resource tags + (https://cloud.google.com/iam/help/conditions/resource-tags) + and combine them using boolean and logical operators. Other + functions and operators are not supported. KEY Sets KEY value. @@ -279,7 +272,7 @@ FLAGS Each permission uses the format {service_fqdn}/{resource}.{verb}, where {service_fqdn} is the fully qualified domain name for the service. Currently - supported permissions are: + supported permissions are as follows: ▹ eventarc.googleapis.com/messageBuses.publish. @@ -293,14 +286,17 @@ FLAGS user accounts. For example, principal://goog/subject/alice@example.com. - If an identifier that was previously set on a policy is soft deleted, then - calls to read that policy will return the identifier with a deleted - prefix. Users cannot set identifiers with this syntax. - * `deleted:principal://goog/subject/{email_id}?uid={uid}`: A specific - Google Account that was deleted recently. For example, - `deleted:principal://goog/subject/alice@example.com?uid=1234567890`. If - the Google Account is recovered, this identifier reverts to the standard - identifier for a Google Account. + If an identifier that was previously set on a policy is soft + deleted, then calls to read that policy will return the + identifier with a deleted prefix. Users cannot set identifiers + with this syntax. + + ◇ deleted:principal://goog/subject/{email_id}?uid={uid}: A + specific Google Account that was deleted recently. For + example, + deleted:principal://goog/subject/alice@example.com?uid=1234567890. + If the Google Account is recovered, this identifier reverts + to the standard identifier for a Google Account. ◇ deleted:principalSet://goog/group/{group_id}?uid={uid}: A Google group that was deleted recently. For example, @@ -333,28 +329,20 @@ FLAGS conditions The conditions that determine whether this rule applies to a request. Conditions are identified by their key, which is the - FQDN of the service that they are relevant to, e.g.: + FQDN of the service that they are relevant to. For example: + "conditions": { "iam.googleapis.com": }. Each + rule is evaluated independently. If this rule does not apply to + a request, other rules might still apply. Currently supported + keys are as follows: - "conditions": { "iam.googleapis.com": } + ◇ eventarc.googleapis.com: Can use CEL functions that + evaluate resource fields. - Each rule is evaluated independently. If this rule does not - apply to a request, other rules might still apply. Currently - supported keys are: - - ◇ eventarc.googleapis.com// The conditions that determine - whether this rule applies to a request. Conditions are - identified by their key, which is the FQDN of the service - that they are relevant to, e.g.: - - "conditions": { "iam.googleapis.com": { "cel_condition": } } - - Each rule is evaluated independently. If this rule does not - apply to a request, other rules might still apply. Currently - supported keys are: - - ◇ eventarc.googleapis.com - ◇ iam.googleapis.com. + ◇ iam.googleapis.com: Can use CEL functions that evaluate + resource tags + (https://cloud.google.com/iam/help/conditions/resource-tags) + and combine them using boolean and logical operators. Other + functions and operators are not supported. KEY Sets KEY value. @@ -413,7 +401,7 @@ FLAGS Each permission uses the format {service_fqdn}/{resource}.{verb}, where {service_fqdn} is the fully qualified domain name for the service. Currently - supported permissions are: + supported permissions are as follows: ▹ eventarc.googleapis.com/messageBuses.publish. @@ -427,14 +415,17 @@ FLAGS user accounts. For example, principal://goog/subject/alice@example.com. - If an identifier that was previously set on a policy is soft deleted, then - calls to read that policy will return the identifier with a deleted - prefix. Users cannot set identifiers with this syntax. - * `deleted:principal://goog/subject/{email_id}?uid={uid}`: A specific - Google Account that was deleted recently. For example, - `deleted:principal://goog/subject/alice@example.com?uid=1234567890`. If - the Google Account is recovered, this identifier reverts to the standard - identifier for a Google Account. + If an identifier that was previously set on a policy is soft + deleted, then calls to read that policy will return the + identifier with a deleted prefix. Users cannot set identifiers + with this syntax. + + ◇ deleted:principal://goog/subject/{email_id}?uid={uid}: A + specific Google Account that was deleted recently. For + example, + deleted:principal://goog/subject/alice@example.com?uid=1234567890. + If the Google Account is recovered, this identifier reverts + to the standard identifier for a Google Account. ◇ deleted:principalSet://goog/group/{group_id}?uid={uid}: A Google group that was deleted recently. For example, @@ -473,28 +464,20 @@ FLAGS conditions The conditions that determine whether this rule applies to a request. Conditions are identified by their key, which is the - FQDN of the service that they are relevant to, e.g.: - - "conditions": { "iam.googleapis.com": } - + FQDN of the service that they are relevant to. For example: + "conditions": { "iam.googleapis.com": }. Each rule is evaluated independently. If this rule does not apply to a request, other rules might still apply. Currently - supported keys are: + supported keys are as follows: - ▹ eventarc.googleapis.com// The conditions that determine - whether this rule applies to a request. Conditions are - identified by their key, which is the FQDN of the service - that they are relevant to, e.g.: + ▹ eventarc.googleapis.com: Can use CEL functions that + evaluate resource fields. - "conditions": { "iam.googleapis.com": { "cel_condition": } } - - Each rule is evaluated independently. If this rule does not - apply to a request, other rules might still apply. Currently - supported keys are: - - ▹ eventarc.googleapis.com - ▹ iam.googleapis.com. + ▹ iam.googleapis.com: Can use CEL functions that evaluate + resource tags + (https://cloud.google.com/iam/help/conditions/resource-tags) + and combine them using boolean and logical operators. Other + functions and operators are not supported. KEY Sets KEY value. @@ -553,7 +536,7 @@ FLAGS rule. Each permission uses the format {service_fqdn}/{resource}.{verb}, where {service_fqdn} is the fully qualified domain name for the service. - Currently supported permissions are: + Currently supported permissions are as follows: ▪ eventarc.googleapis.com/messageBuses.publish. @@ -567,14 +550,17 @@ FLAGS Workspace user accounts. For example, principal://goog/subject/alice@example.com. - If an identifier that was previously set on a policy is soft deleted, then - calls to read that policy will return the identifier with a deleted - prefix. Users cannot set identifiers with this syntax. - * `deleted:principal://goog/subject/{email_id}?uid={uid}`: A specific - Google Account that was deleted recently. For example, - `deleted:principal://goog/subject/alice@example.com?uid=1234567890`. If - the Google Account is recovered, this identifier reverts to the standard - identifier for a Google Account. + If an identifier that was previously set on a policy is soft + deleted, then calls to read that policy will return the + identifier with a deleted prefix. Users cannot set + identifiers with this syntax. + + ▹ deleted:principal://goog/subject/{email_id}?uid={uid}: A + specific Google Account that was deleted recently. For + example, + deleted:principal://goog/subject/alice@example.com?uid=1234567890. + If the Google Account is recovered, this identifier reverts + to the standard identifier for a Google Account. ▹ deleted:principalSet://goog/group/{group_id}?uid={uid}: A Google group that was deleted recently. For example, diff --git a/gcloud/beta/iam/policy-bindings/create b/gcloud/beta/iam/policy-bindings/create index 897976c27..4a1d05aee 100644 --- a/gcloud/beta/iam/policy-bindings/create +++ b/gcloud/beta/iam/policy-bindings/create @@ -135,7 +135,8 @@ REQUIRED FLAGS //iam.googleapis.com/projects/PROJECT_NUMBER/locations/LOCATION/workloadIdentityPools/WORKLOAD_POOL_ID --target-resource=TARGET_RESOURCE - The full resource name that's used for access policy bindings + The full resource name that's used for access policy bindings. + Examples: ▹ Organization: @@ -191,8 +192,7 @@ OPTIONAL FLAGS POLICY_KIND must be one of: access - Access policy kind. Keep behind visibility label until Access - Policy launch. + Access policy kind. principal-access-boundary Principal access boundary policy kind diff --git a/gcloud/beta/managed-kafka/clusters/describe b/gcloud/beta/managed-kafka/clusters/describe index a536805ed..10e785683 100644 --- a/gcloud/beta/managed-kafka/clusters/describe +++ b/gcloud/beta/managed-kafka/clusters/describe @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta managed-kafka clusters describe (CLUSTER : --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] + [--full] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Describe a Managed Service for Apache Kafka cluster. @@ -50,6 +50,11 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --location on the command line. +FLAGS + --full + Show detailed information about individual brokers, such as broker id + and zone, as well as the Kafka version running on the cluster. + 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/managed-kafka/connect-clusters/create b/gcloud/beta/managed-kafka/connect-clusters/create index f1f2f13df..87dad00e5 100644 --- a/gcloud/beta/managed-kafka/connect-clusters/create +++ b/gcloud/beta/managed-kafka/connect-clusters/create @@ -83,10 +83,17 @@ REQUIRED FLAGS OPTIONAL FLAGS --additional-subnet=ADDITIONAL_SUBNET - Additional subnet to make available to the Kafka Connect cluster. - Structured like: + (DEPRECATED) Additional subnet to make available to the Kafka Connect + cluster. Structured like: projects/{project}/regions/{region}/subnetworks/{subnet_id}. + The --additional-subnet flag is deprecated and will be removed in a + future version. Managed Kafka Connect clusters can now reach any + endpoint accessible from the primary subnet without the need to define + additional subnets. Please see + https://cloud.google.com/managed-service-for-apache-kafka/docs/connect-cluster/create-connect-cluster#worker-subnet + for more information. + --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/beta/managed-kafka/connect-clusters/update b/gcloud/beta/managed-kafka/connect-clusters/update index 0bdbf5ad0..1a3ce6fdb 100644 --- a/gcloud/beta/managed-kafka/connect-clusters/update +++ b/gcloud/beta/managed-kafka/connect-clusters/update @@ -27,8 +27,6 @@ EXAMPLES --config-file=my-config-file.yaml --cpu=3 --memory=3GiB \ --primary-subnet=projects/my-project/regions/us-central1/\ subnetworks/default/1 \ - --additional-subnet=projects/my-project/regions/us-central1/\ - subnetworks/default/2 \ --dns-name=bootstrap.myconnectorCluster.us-central1.managedkafka\ .my-project.cloud.goog:9092 \ --secret=projects/my-project/secrets/my-secret/versions/1 \ @@ -145,10 +143,17 @@ REQUIRED FLAGS this group are specified. --additional-subnet=ADDITIONAL_SUBNET - Additional subnet to make available to the Kafka Connect cluster. - Structured like: + (DEPRECATED) Additional subnet to make available to the Kafka Connect + cluster. Structured like: projects/{project}/regions/{region}/subnetworks/{subnet_id}. + The --additional-subnet flag is deprecated and will be removed in a + future version. Managed Kafka Connect clusters can now reach any + endpoint accessible from the primary subnet without the need to + define additional subnets. Please see + https://cloud.google.com/managed-service-for-apache-kafka/docs/connect-cluster/create-connect-cluster#worker-subnet + for more information. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/beta/managed-kafka/connectors/create b/gcloud/beta/managed-kafka/connectors/create index 636ceeb0d..e59a882e9 100644 --- a/gcloud/beta/managed-kafka/connectors/create +++ b/gcloud/beta/managed-kafka/connectors/create @@ -6,6 +6,7 @@ SYNOPSIS gcloud beta managed-kafka connectors create (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) (--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]) + [--task-retry-disabled] [--task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF] [GCLOUD_WIDE_FLAG ...] @@ -21,12 +22,12 @@ EXAMPLES --configs=connector.class="com.google.pubsub.kafka.source.CloudP\ ubSubSourceConnector",cps.subscription="my-subscription",... \ [--task-restart-min-backoff=60s] \ - [--task-restart-max-backoff=30m] OR + [--task-restart-max-backoff=30m] [--task-retry-disabled=true] OR $ gcloud beta managed-kafka connectors create myconnector \ --location=us-central1 --connect-cluster=mycluster \ --config-file=my-config-file.yaml \ [--task-restart-min-backoff=60s] \ - [--task-restart-max-backoff=30m] + [--task-restart-max-backoff=30m] [--task-retry-disabled=true] POSITIONAL ARGUMENTS Connector resource - Identifies the connector for which the command runs. @@ -92,6 +93,9 @@ REQUIRED FLAGS name, for example: cleanup.policy=compact,compression.type=producer. OPTIONAL FLAGS + --task-retry-disabled + Disable default task retry policy. + --task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF The maximum amount of time to wait before retrying a failed task in seconds. This sets an upper bound for the backoff delay. The default diff --git a/gcloud/beta/managed-kafka/connectors/update b/gcloud/beta/managed-kafka/connectors/update index 637654f2b..ad9ed36eb 100644 --- a/gcloud/beta/managed-kafka/connectors/update +++ b/gcloud/beta/managed-kafka/connectors/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta managed-kafka connectors update (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [--task-retry-disabled] [--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]] [--task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF] @@ -19,11 +20,11 @@ EXAMPLES $ gcloud beta managed-kafka connectors update myconnector \ --location=us-central1 --configs=KEY1=VALUE1,KEY2=VALUE2... \ --connect-cluster=mycluster [--task-restart-min-backoff=60s] \ - [--task-restart-max-backoff=30m] OR + [--task-restart-max-backoff=30m] [--task-retry-disabled=true] OR $ gcloud beta managed-kafka connectors update myconnector \ --location=us-central1 --config-file=my-config-file.yaml \ --connect-cluster=mycluster [--task-restart-min-backoff=60s] \ - [--task-restart-max-backoff=30m] + [--task-restart-max-backoff=30m] [--task-retry-disabled=true] POSITIONAL ARGUMENTS Connector resource - Identifies the connector for which the command runs. @@ -68,6 +69,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line. FLAGS + --task-retry-disabled + Disable default task retry policy. + At most one of these can be specified: --config-file=JSON|YAML|FILE diff --git a/gcloud/beta/model-armor/floorsettings/update b/gcloud/beta/model-armor/floorsettings/update index 754f824d9..0f74b42d6 100644 --- a/gcloud/beta/model-armor/floorsettings/update +++ b/gcloud/beta/model-armor/floorsettings/update @@ -33,7 +33,8 @@ REQUIRED FLAGS OPTIONAL FLAGS --enable-floor-setting-enforcement=ENABLE_FLOOR_SETTING_ENFORCEMENT - Enable or disable the floor setting enforcement + Enable or disable the floor setting enforcement. Set the value to + "TRUE" to enable the floor setting enforcement, "FALSE" to disable it. Multi language detection enablement. @@ -120,16 +121,18 @@ OPTIONAL FLAGS SDP filter settings. --advanced-config-deidentify-template=ADVANCED_CONFIG_DEIDENTIFY_TEMPLATE - The sdp filter settings enforcement. The value can be either "enable" - or "disable". + The sdp filter settings enforcement. The value has to be a valid + template name. e.g. + projects/{project}/locations/{location}/deidentifyTemplates/{deidentify_template} --advanced-config-inspect-template=ADVANCED_CONFIG_INSPECT_TEMPLATE - The sdp filter settings enforcement. The value can be either "enable" - or "disable". + The sdp filter settings enforcement. The value has to be a valid + template name. e.g. + projects/{project}/locations/{location}/inspectTemplates/{inspect_template} --basic-config-filter-enforcement=BASIC_CONFIG_FILTER_ENFORCEMENT - The sdp filter settings enforcement. The value can be either - "ENABLED" or "DISABLED" + The sdp filter settings enforcement. The value can be either ENABLED + or DISABLED. Options for Google MCP server sanitization. diff --git a/gcloud/beta/monitoring/help b/gcloud/beta/monitoring/help index 87eaef368..013a16a34 100644 --- a/gcloud/beta/monitoring/help +++ b/gcloud/beta/monitoring/help @@ -36,6 +36,9 @@ GROUPS metrics-scopes (BETA) Manage Cloud Monitoring Metrics Scopes. + policies + (BETA) Manage Cloud Monitoring alerting policies. + snoozes (BETA) Manage Cloud Monitoring snoozes. diff --git a/gcloud/beta/monitoring/policies/conditions/create b/gcloud/beta/monitoring/policies/conditions/create new file mode 100644 index 000000000..5931e9aba --- /dev/null +++ b/gcloud/beta/monitoring/policies/conditions/create @@ -0,0 +1,96 @@ +NAME + gcloud beta monitoring policies conditions create - create a condition in + an alerting policy + +SYNOPSIS + gcloud beta monitoring policies conditions create ALERT_POLICY + [--aggregation=AGGREGATION + --condition-display-name=CONDITION_DISPLAY_NAME + --condition-filter=CONDITION_FILTER + --duration=DURATION --if=IF_VALUE --trigger-count=TRIGGER_COUNT + | --trigger-percent=TRIGGER_PERCENT] + [--condition=CONDITION | --condition-from-file=PATH_TO_FILE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a condition in an alerting policy. + +POSITIONAL ARGUMENTS + Alert Policy resource - Name of the Alert Policy to add a condition 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 alert_policy 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. + + ALERT_POLICY + ID of the Alert Policy or fully qualified identifier for the Alert + Policy. + + To set the policy attribute: + ▸ provide the argument alert_policy on the command line. + +FLAGS + Condition Settings. This will add a condition to the created policy. If + any conditions are already specified, this condition will be appended. + + --aggregation=AGGREGATION + Specifies an Aggregation message as a JSON/YAML value to be applied + to the condition. For more information about the format: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.alertPolicies + + --condition-display-name=CONDITION_DISPLAY_NAME + The display name for the condition. + + --condition-filter=CONDITION_FILTER + Specifies the "filter" in a metric absence or metric threshold + condition. + + --duration=DURATION + The duration (e.g. "60s", "2min", etc.) that the condition must hold + in order to trigger as true. + + --if=IF_VALUE + One of "absent", "< THRESHOLD", "> THRESHOLD" where "THRESHOLD" is an + integer or float. + + At most one of these can be specified: + + --trigger-count=TRIGGER_COUNT + The absolute number of time series that must fail the predicate for + the condition to be triggered. + + --trigger-percent=TRIGGER_PERCENT + The percentage of time series that must fail the predicate for the + condition to be triggered. + + At most one of these can be specified: + + --condition=CONDITION + The condition as a string. In either JSON or YAML format. + + --condition-from-file=PATH_TO_FILE + The path to a JSON or YAML file containing the condition. Use a full + or relative path to a local file containing the value of condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring policies conditions create + + $ gcloud alpha monitoring policies conditions create + diff --git a/gcloud/beta/monitoring/policies/conditions/delete b/gcloud/beta/monitoring/policies/conditions/delete new file mode 100644 index 000000000..413aa5ba0 --- /dev/null +++ b/gcloud/beta/monitoring/policies/conditions/delete @@ -0,0 +1,60 @@ +NAME + gcloud beta monitoring policies conditions delete - delete a condition in + an alerting policy + +SYNOPSIS + gcloud beta monitoring policies conditions delete + (CONDITION : --policy=POLICY) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a condition in an alerting policy. If the specified condition + does not exist, this command will fail with an error. This will not delete + the policy if no conditions exist. + +POSITIONAL ARGUMENTS + Condition resource - The name of the Condition 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 condition 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. + + CONDITION + ID of the condition or fully qualified identifier for the condition. + + To set the condition attribute: + ▸ provide the argument condition on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --policy=POLICY + Name of the alerting policy. + + To set the policy attribute: + ▸ provide the argument condition on the command line with a fully + specified name; + ▸ provide the argument --policy on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring policies conditions delete + + $ gcloud alpha monitoring policies conditions delete + diff --git a/gcloud/beta/monitoring/policies/conditions/describe b/gcloud/beta/monitoring/policies/conditions/describe new file mode 100644 index 000000000..715f745b0 --- /dev/null +++ b/gcloud/beta/monitoring/policies/conditions/describe @@ -0,0 +1,58 @@ +NAME + gcloud beta monitoring policies conditions describe - describe a condition + in a Cloud Monitoring alerting policy + +SYNOPSIS + gcloud beta monitoring policies conditions describe + (CONDITION : --policy=POLICY) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a condition in a Cloud Monitoring alerting policy. + +POSITIONAL ARGUMENTS + Condition resource - The name of the Condition 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 condition 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. + + CONDITION + ID of the condition or fully qualified identifier for the condition. + + To set the condition attribute: + ▸ provide the argument condition on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --policy=POLICY + Name of the alerting policy. + + To set the policy attribute: + ▸ provide the argument condition on the command line with a fully + specified name; + ▸ provide the argument --policy on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring policies conditions describe + + $ gcloud alpha monitoring policies conditions describe + diff --git a/gcloud/beta/monitoring/policies/conditions/help b/gcloud/beta/monitoring/policies/conditions/help new file mode 100644 index 000000000..43fe0791c --- /dev/null +++ b/gcloud/beta/monitoring/policies/conditions/help @@ -0,0 +1,41 @@ +NAME + gcloud beta monitoring policies conditions - manage Cloud Monitoring + alerting policy conditions + +SYNOPSIS + gcloud beta monitoring policies conditions COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Monitoring alerting policies conditions. + + More information can be found here: + https://cloud.google.com/monitoring/api/v3/ + +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 condition in an alerting policy. + + delete + (BETA) Delete a condition in an alerting policy. + + describe + (BETA) Describe a condition in a Cloud Monitoring alerting policy. + + update + (BETA) Update a condition in an alerting policy. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring policies conditions + + $ gcloud alpha monitoring policies conditions + diff --git a/gcloud/beta/monitoring/policies/conditions/update b/gcloud/beta/monitoring/policies/conditions/update new file mode 100644 index 000000000..2b6721ab8 --- /dev/null +++ b/gcloud/beta/monitoring/policies/conditions/update @@ -0,0 +1,79 @@ +NAME + gcloud beta monitoring policies conditions update - update a condition in + an alerting policy + +SYNOPSIS + gcloud beta monitoring policies conditions update + (CONDITION : --policy=POLICY) [--display-name=DISPLAY_NAME] + [--if=IF_VALUE] + [--trigger-count=TRIGGER_COUNT | --trigger-percent=TRIGGER_PERCENT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a condition in an alerting policy. + +POSITIONAL ARGUMENTS + Condition resource - The name of the Condition 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 condition 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. + + CONDITION + ID of the condition or fully qualified identifier for the condition. + + To set the condition attribute: + ▸ provide the argument condition on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --policy=POLICY + Name of the alerting policy. + + To set the policy attribute: + ▸ provide the argument condition on the command line with a fully + specified name; + ▸ provide the argument --policy on the command line. + +FLAGS + --display-name=DISPLAY_NAME + The display name for the Condition. + + --if=IF_VALUE + One of "absent", "< THRESHOLD", "> THRESHOLD" where "THRESHOLD" is an + integer or float. + + At most one of these can be specified: + + --trigger-count=TRIGGER_COUNT + The absolute number of time series that must fail the predicate for + the condition to be triggered. + + --trigger-percent=TRIGGER_PERCENT + The percentage of time series that must fail the predicate for the + condition to be triggered. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring policies conditions update + + $ gcloud alpha monitoring policies conditions update + diff --git a/gcloud/beta/monitoring/policies/create b/gcloud/beta/monitoring/policies/create new file mode 100644 index 000000000..a8b2b6e31 --- /dev/null +++ b/gcloud/beta/monitoring/policies/create @@ -0,0 +1,171 @@ +NAME + gcloud beta monitoring policies create - create a new alerting policy + +SYNOPSIS + gcloud beta monitoring policies create + [--notification-channels=[NOTIFICATION_CHANNELS,...]] + [--aggregation=AGGREGATION + --condition-display-name=CONDITION_DISPLAY_NAME + --condition-filter=CONDITION_FILTER + --duration=DURATION --if=IF_VALUE --trigger-count=TRIGGER_COUNT + | --trigger-percent=TRIGGER_PERCENT] + [--combiner=COMBINER --display-name=DISPLAY_NAME --no-enabled + --user-labels=[KEY=VALUE,...] + --documentation-format=DOCUMENTATION_FORMAT; + default="text/markdown" --documentation=DOCUMENTATION + | --documentation-from-file=PATH_TO_FILE] + [--policy=POLICY | --policy-from-file=PATH_TO_FILE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Creates a new alerting policy. An alert policy can be specified as a + JSON/YAML value passed in as a string through the --policy flag or as a + file through the --policy-from-file flag. A basic policy can also be + specified through command line flags. If a policy is specified through + --policy or --policy-from-file, and additional flags are supplied, the + flags will override the policy's settings and a specified condition will be + appended to the list of conditions. + + For information about the JSON/YAML format of an alerting policy: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.alertPolicies + +FLAGS + Notification Channel resource - Names of one or more Notification Channels + to be added to the policy. These should be the resource names (not the + display name) of the channels. Acceptable formats are: + + ◆ Channel Name: my-channel + ▸ The project specified through --project or the default project + defined by the core/project property will be used, in that order. + ◆ Channel Relative Name: + projects/my-project/notificationChannels/channel-id0 + ◆ Channel URI: + https://monitoring.googleapis.com/v3/projects/my-project/notificationChannels/channel-id0 + 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 --notification-channels on the command line with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --notification-channels=[NOTIFICATION_CHANNELS,...] + IDs of the Notification Channels or fully qualified identifiers for + the Notification Channels. + + To set the notification_channels attribute: + ▸ provide the argument --notification-channels on the command line. + + Condition Settings. This will add a condition to the created policy. If + any conditions are already specified, this condition will be appended. + + --aggregation=AGGREGATION + Specifies an Aggregation message as a JSON/YAML value to be applied + to the condition. For more information about the format: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.alertPolicies + + --condition-display-name=CONDITION_DISPLAY_NAME + The display name for the condition. + + --condition-filter=CONDITION_FILTER + Specifies the "filter" in a metric absence or metric threshold + condition. + + --duration=DURATION + The duration (e.g. "60s", "2min", etc.) that the condition must hold + in order to trigger as true. + + --if=IF_VALUE + One of "absent", "< THRESHOLD", "> THRESHOLD" where "THRESHOLD" is an + integer or float. + + At most one of these can be specified: + + --trigger-count=TRIGGER_COUNT + The absolute number of time series that must fail the predicate for + the condition to be triggered. + + --trigger-percent=TRIGGER_PERCENT + The percentage of time series that must fail the predicate for the + condition to be triggered. + + Policy Settings. If any of these are specified, they will overwrite fields + in the --policy or --policy-from-file flags if specified. + + --combiner=COMBINER + The combiner for the Alert Policy. COMBINER must be one of: + + AND + An incident is created only if all conditions are met + simultaneously. This combiner is satisfied if all conditions are + met, even if they are met on completely different resources. + AND_WITH_MATCHING_RESOURCE + Combine conditions using logical AND operator, but unlike the + regular AND option, an incident is created only if all conditions + are met simultaneously on at least one resource. + COMBINE_UNSPECIFIED + An unspecified combiner + OR + An incident is created if any of the listed conditions is met. + + --display-name=DISPLAY_NAME + The display name for the Alert Policy. + + --enabled + If the policy is enabled. Enabled by default, use --no-enabled to + disable. + + --user-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. + + If the policy was given as a JSON/YAML object from a string or file, + this flag will replace the labels value in the given policy. + + Documentation + + --documentation-format=DOCUMENTATION_FORMAT; default="text/markdown" + The MIME type that should be used with --documentation or + --documentation-from-file. Currently, only "text/markdown" is + supported. + + At most one of these can be specified: + + --documentation=DOCUMENTATION + The documentation to be included with the policy. + + --documentation-from-file=PATH_TO_FILE + The path to a file containing the documentation to be included + with the policy. Use a full or relative path to a local file + containing the value of documentation. + + At most one of these can be specified: + + --policy=POLICY + The policy as a string. In either JSON or YAML format. + + --policy-from-file=PATH_TO_FILE + The path to a JSON or YAML file containing the policy. Use a full or + relative path to a local file containing the value of policy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring policies create + + $ gcloud alpha monitoring policies create + diff --git a/gcloud/beta/monitoring/policies/delete b/gcloud/beta/monitoring/policies/delete new file mode 100644 index 000000000..bd452e9a3 --- /dev/null +++ b/gcloud/beta/monitoring/policies/delete @@ -0,0 +1,49 @@ +NAME + gcloud beta monitoring policies delete - delete a Cloud Monitoring alerting + policy + +SYNOPSIS + gcloud beta monitoring policies delete POLICY [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Monitoring alerting policy. + +POSITIONAL ARGUMENTS + Policy resource - The alerting policy to delete. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument policy 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. + + POLICY + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring policies delete + + $ gcloud alpha monitoring policies delete + diff --git a/gcloud/beta/monitoring/policies/describe b/gcloud/beta/monitoring/policies/describe new file mode 100644 index 000000000..5194b8a56 --- /dev/null +++ b/gcloud/beta/monitoring/policies/describe @@ -0,0 +1,48 @@ +NAME + gcloud beta monitoring policies describe - describe an alerting policy + +SYNOPSIS + gcloud beta monitoring policies describe POLICY [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an alerting policy. + +POSITIONAL ARGUMENTS + Policy resource - The alerting policy to describe. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument policy 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. + + POLICY + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring policies describe + + $ gcloud alpha monitoring policies describe + diff --git a/gcloud/beta/monitoring/policies/help b/gcloud/beta/monitoring/policies/help new file mode 100644 index 000000000..00a7e2a6a --- /dev/null +++ b/gcloud/beta/monitoring/policies/help @@ -0,0 +1,52 @@ +NAME + gcloud beta monitoring policies - manage Cloud Monitoring alerting policies + +SYNOPSIS + gcloud beta monitoring policies GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Monitoring alerting policies. + + More information can be found here: + https://cloud.google.com/monitoring/api/v3/ + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + conditions + (BETA) Manage Cloud Monitoring alerting policy conditions. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a new alerting policy. + + delete + (BETA) Delete a Cloud Monitoring alerting policy. + + describe + (BETA) Describe an alerting policy. + + list + (BETA) List alerting policies. + + migrate + (BETA) Migrate a Prometheus configuration file to Cloud Monitoring. + + update + (BETA) Updates an alerting policy. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring policies + + $ gcloud alpha monitoring policies + diff --git a/gcloud/beta/monitoring/policies/list b/gcloud/beta/monitoring/policies/list new file mode 100644 index 000000000..7cc7804d8 --- /dev/null +++ b/gcloud/beta/monitoring/policies/list @@ -0,0 +1,87 @@ +NAME + gcloud beta monitoring policies list - list alerting policies + +SYNOPSIS + gcloud beta monitoring policies list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List alerting policies. + +EXAMPLES + To order your results first by the team key in user_labels and then the + policy's display name: + + $ gcloud beta monitoring policies list \ + --sort-by user_label.team,display_name + + To order your results in reverse order, you can add either '~' or '-' in + front of the field name: + + $ gcloud beta monitoring policies list --sort-by "-display_name" + + To return results with non-empty display names or descriptions: + + $ gcloud beta monitoring policies list \ + --filter "(NOT display_name.empty OR NOT description.empty)" + + To return results whose descriptions contain the word 'cloud': + + $ gcloud beta monitoring policies list --filter "description:(cloud)" + + Please find all supported fields at + https://cloud.google.com/monitoring/api/v3/sorting-and-filtering#alertpolicy. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring policies list + + $ gcloud alpha monitoring policies list + diff --git a/gcloud/beta/monitoring/policies/migrate b/gcloud/beta/monitoring/policies/migrate new file mode 100644 index 000000000..9d2d86b12 --- /dev/null +++ b/gcloud/beta/monitoring/policies/migrate @@ -0,0 +1,45 @@ +NAME + gcloud beta monitoring policies migrate - migrate a Prometheus + configuration file to Cloud Monitoring + +SYNOPSIS + gcloud beta monitoring policies migrate + [--channels-from-prometheus-alertmanager-yaml=PROMETHEUS_ALERT_MANAGER_FILE_PATH --policies-from-prometheus-alert-rules-yaml=[PROMETHEUS_ALERT_RULE_FILE_PATHS, + ...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Creates new alerting policies and/or notification channels based on + provided Prometheus files. The rules YAML file, which holds the alert + rules, must be specified as a file through the + --policies-from-prometheus-alert-rules-yaml flag. + +FLAGS + --channels-from-prometheus-alertmanager-yaml=PROMETHEUS_ALERT_MANAGER_FILE_PATH + Prometheus alert manager YAML file to be converted to Cloud Monitoring + notification channels. Specifying this flag with the + --policies-from-prometheus-alert-rules-yaml flag puts the newly created + notification channels into the translated Alert Policies' definition. + Use a full or relative path to a local file containing the value of + channels_from_prometheus_alertmanager_yaml. + + --policies-from-prometheus-alert-rules-yaml=[PROMETHEUS_ALERT_RULE_FILE_PATHS,...] + One or more Prometheus alert rule YAML files (separated by commas if + multiple) to be converted to Cloud Alerting Policies. Example: + --policies-from-prometheus-alert-rules-yaml=rules_1.yaml,rules_2.yaml + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring policies migrate + + $ gcloud alpha monitoring policies migrate + diff --git a/gcloud/beta/monitoring/policies/update b/gcloud/beta/monitoring/policies/update new file mode 100644 index 000000000..33a644b97 --- /dev/null +++ b/gcloud/beta/monitoring/policies/update @@ -0,0 +1,183 @@ +NAME + gcloud beta monitoring policies update - updates an alerting policy + +SYNOPSIS + gcloud beta monitoring policies update ALERT_POLICY + [--fields=[field,...] | --combiner=COMBINER --display-name=DISPLAY_NAME + --[no-]enabled + --add-notification-channels=[NOTIFICATION-CHANNELS,...] + | --clear-notification-channels + | --remove-notification-channels=[NOTIFICATION-CHANNELS,...] + | --set-notification-channels=[NOTIFICATION-CHANNELS,...] + --documentation-format=DOCUMENTATION_FORMAT + --documentation=DOCUMENTATION + | --documentation-from-file=PATH_TO_FILE + --update-user-labels=[KEY=VALUE,...] --clear-user-labels + | --remove-user-labels=[KEY,...]] + [--policy=POLICY | --policy-from-file=PATH_TO_FILE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Updates an alerting policy. + + If --policy or --policy-from-file are specified: + + ▪ If --fields is specified, the only the specified fields will be + updated. + ▪ Else, the policy will be replaced with the provided policy. The + policy can be modified further using the flags from the Policy Settings + group below. + + Otherwise, the policy will be updated with the values specified in the + flags from the Policy Settings group. + + For information about the JSON/YAML format of an alerting policy: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.alertPolicies + +POSITIONAL ARGUMENTS + Alert Policy resource - Name of the Alert Policy to be updated. 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 alert_policy 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. + + ALERT_POLICY + ID of the Alert Policy or fully qualified identifier for the Alert + Policy. + + To set the policy attribute: + ▸ provide the argument alert_policy on the command line. + +FLAGS + At most one of these can be specified: + + --fields=[field,...] + The list of fields to update. Must specify --policy or + --policy-from-file if using this flag. field must be one of: + disabled, notificationChannels. + + Policy Settings. If any of these are specified, they will overwrite + fields in the --policy or --policy-from-file flags if specified. + + --combiner=COMBINER + The combiner for the Alert Policy. COMBINER must be one of: + + AND + An incident is created only if all conditions are met + simultaneously. This combiner is satisfied if all conditions + are met, even if they are met on completely different + resources. + AND_WITH_MATCHING_RESOURCE + Combine conditions using logical AND operator, but unlike the + regular AND option, an incident is created only if all + conditions are met simultaneously on at least one resource. + COMBINE_UNSPECIFIED + An unspecified combiner + OR + An incident is created if any of the listed conditions is met. + + --display-name=DISPLAY_NAME + The display name for the Alert Policy. + + --[no-]enabled + If the policy is enabled. Use --enabled to enable and --no-enabled + to disable. + + These flags modify the member Notification Channels of this Alert + Policy. + + At most one of these can be specified: + + --add-notification-channels=[NOTIFICATION-CHANNELS,...] + Append the given values to the current Notification Channels. + + --clear-notification-channels + Empty the current Notification Channels. + + --remove-notification-channels=[NOTIFICATION-CHANNELS,...] + Remove the given values from the current Notification Channels. + + --set-notification-channels=[NOTIFICATION-CHANNELS,...] + Completely replace the current Notification Channels with the + given values. + + Documentation + + --documentation-format=DOCUMENTATION_FORMAT + The MIME type that should be used with --documentation or + --documentation-from-file. Currently, only "text/markdown" is + supported. + + At most one of these can be specified: + + --documentation=DOCUMENTATION + The documentation to be included with the policy. + + --documentation-from-file=PATH_TO_FILE + The path to a file containing the documentation to be included + with the policy. Use a full or relative path to a local file + containing the value of documentation. + + User Labels + + --update-user-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-user-labels + Remove all labels. If --update-user-labels is also specified + then --clear-user-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta monitoring policies update --clear-user-labels + + To remove all existing labels and create two new labels, foo + and baz: + + $ gcloud beta monitoring policies update --clear-user-labels \ + --update-user-labels foo=bar,baz=qux + + --remove-user-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-user-labels is also specified + then --update-user-labels is applied first. + + At most one of these can be specified: + + --policy=POLICY + The policy as a string. In either JSON or YAML format. + + --policy-from-file=PATH_TO_FILE + The path to a JSON or YAML file containing the policy. Use a full or + relative path to a local file containing the value of policy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring policies update + + $ gcloud alpha monitoring policies update + diff --git a/gcloud/beta/netapp/backup-vaults/create b/gcloud/beta/netapp/backup-vaults/create index a02b79449..0ae35d986 100644 --- a/gcloud/beta/netapp/backup-vaults/create +++ b/gcloud/beta/netapp/backup-vaults/create @@ -12,7 +12,8 @@ SYNOPSIS [monthly-backup-immutable=MONTHLY-BACKUP-IMMUTABLE], [weekly-backup-immutable=WEEKLY-BACKUP-IMMUTABLE]] [--backup-vault-type=BACKUP_VAULT_TYPE] [--description=DESCRIPTION] - [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a Cloud NetApp Backup Vault. @@ -87,6 +88,31 @@ FLAGS --description=DESCRIPTION A description of the Cloud NetApp Backup Vault + Kms config resource - The resource name of the KMS Config to use for + encrypting backups within this backup vault. Format: + projects/{project_id}/locations/{location}/kmsConfigs/{kms_config_id} 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 --kms-config 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 --kms-config on the command line with a fully + specified name; + ◆ provide the argument --location on the command line; + ◆ set the property netapp/location. + + --kms-config=KMS_CONFIG + ID of the kms_config or fully qualified identifier for the + kms_config. + + To set the kms_config attribute: + ▸ provide the argument --kms-config on the command line. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/beta/netapp/volumes/create b/gcloud/beta/netapp/volumes/create index 9583280ad..b53d3da8c 100644 --- a/gcloud/beta/netapp/volumes/create +++ b/gcloud/beta/netapp/volumes/create @@ -15,16 +15,19 @@ SYNOPSIS [peer-cluster-name=PEER-CLUSTER-NAME], [peer-ip-addresses=PEER-IP-ADDRESSES], [peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME]] + [--cache-pre-populate=[exclude-path-list=EXCLUDE-PATH-LIST], + [path-list=PATH-LIST],[recursion=RECURSION]] [--description=DESCRIPTION] [--enable-kerberos=ENABLE_KERBEROS] [--export-policy=[access-type=ACCESS-TYPE], - [allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS], + [allowed-clients=ALLOWED-CLIENTS],[anon-uid=ANON-UID], + [has-root-access=HAS-ROOT-ACCESS], [kerberos-5-read-only=KERBEROS-5-READ-ONLY], [kerberos-5-read-write=KERBEROS-5-READ-WRITE], [kerberos-5i-read-only=KERBEROS-5I-READ-ONLY], [kerberos-5i-read-write=KERBEROS-5I-READ-WRITE], [kerberos-5p-read-only=KERBEROS-5P-READ-ONLY], [kerberos-5p-read-write=KERBEROS-5P-READ-WRITE], - [nfsv3=NFSV3],[nfsv4=NFSV4]] + [nfsv3=NFSV3],[nfsv4=NFSV4],[squash-mode=SQUASH-MODE]] [--hybrid-replication-parameters=[cluster-location=CLUSTER-LOCATION], [description=DESCRIPTION], [hybrid-replication-type=HYBRID-REPLICATION-TYPE],[labels=LABELS], @@ -196,13 +199,29 @@ OPTIONAL FLAGS *enable-global-file-lock*::: If true, enable global file lock *cache-config*::: Cache-config as a hashtag-separated(#) list of key-value pairs + --cache-pre-populate=[exclude-path-list=EXCLUDE-PATH-LIST],[path-list=PATH-LIST],[recursion=RECURSION] + Cache Pre-populate contains cache pre-populate parameters of a volume. + + Cache Pre-populate will have the following format + --cache-pre-populate=path-list=PATH_LIST1#PATH_LIST2, + exclude-path-list=EXCLUDE_PATH_LIST1#EXCLUDE_PATH_LIST2, + recursion=RECURSION + + path-list + Hashtag-separated(#) list of paths to be pre-populated + exclude-path-list + Hashtag-separated(#) list of paths to be excluded from + pre-population + recursion + Boolean value indicating pre-populate recursion. + --description=DESCRIPTION A description of the Cloud NetApp Volume --enable-kerberos=ENABLE_KERBEROS Boolean flag indicating whether Volume is a kerberos Volume or not - --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4] + --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[anon-uid=ANON-UID],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4],[squash-mode=SQUASH-MODE] Export Policy of a Cloud NetApp Files Volume. This will be a field similar to network in which export policy fields can be specified as such: --export-policy=allowed-clients=ALLOWED_CLIENTS_IP_ADDRESSES, @@ -212,7 +231,8 @@ OPTIONAL FLAGS kerberos-5i-read-only=KERBEROS_5I_READ_ONLY, kerberos-5i-read-write=KERBEROS_5I_READ_WRITE, kerberos-5p-read-only=KERBEROS_5P_READ_ONLY, - kerberos-5p-read-write=KERBEROS_5P_READ_WRITE + kerberos-5p-read-write=KERBEROS_5P_READ_WRITE, + squash-mode=SQUASH_MODE,anon-uid=ANON_UID --hybrid-replication-parameters=[cluster-location=CLUSTER-LOCATION],[description=DESCRIPTION],[hybrid-replication-type=HYBRID-REPLICATION-TYPE],[labels=LABELS],[large-volume-constituent-count=LARGE-VOLUME-CONSTITUENT-COUNT],[peer-cluster-name=PEER-CLUSTER-NAME],[peer-ip-addresses=PEER-IP-ADDRESSES],[peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME],[replication=REPLICATION],[replication-schedule=REPLICATION-SCHEDULE] Hybrid Replication Parameters contains hybrid replication parameters on diff --git a/gcloud/beta/netapp/volumes/update b/gcloud/beta/netapp/volumes/update index 3ef766938..f76cf57dd 100644 --- a/gcloud/beta/netapp/volumes/update +++ b/gcloud/beta/netapp/volumes/update @@ -13,17 +13,20 @@ SYNOPSIS [peer-cluster-name=PEER-CLUSTER-NAME], [peer-ip-addresses=PEER-IP-ADDRESSES], [peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME]] - [--capacity=CAPACITY] [--description=DESCRIPTION] - [--enable-kerberos=ENABLE_KERBEROS] + [--cache-pre-populate=[exclude-path-list=EXCLUDE-PATH-LIST], + [path-list=PATH-LIST],[recursion=RECURSION]] [--capacity=CAPACITY] + [--description=DESCRIPTION] [--enable-kerberos=ENABLE_KERBEROS] [--export-policy=[access-type=ACCESS-TYPE], - [allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS], + [allowed-clients=ALLOWED-CLIENTS],[anon-uid=ANON-UID], + [has-root-access=HAS-ROOT-ACCESS], [kerberos-5-read-only=KERBEROS-5-READ-ONLY], [kerberos-5-read-write=KERBEROS-5-READ-WRITE], [kerberos-5i-read-only=KERBEROS-5I-READ-ONLY], [kerberos-5i-read-write=KERBEROS-5I-READ-WRITE], [kerberos-5p-read-only=KERBEROS-5P-READ-ONLY], [kerberos-5p-read-write=KERBEROS-5P-READ-WRITE], - [nfsv3=NFSV3],[nfsv4=NFSV4]] [--protocols=PROTOCOL,[PROTOCOL,...]] + [nfsv3=NFSV3],[nfsv4=NFSV4],[squash-mode=SQUASH-MODE]] + [--protocols=PROTOCOL,[PROTOCOL,...]] [--restricted-actions=RESTRICTED_ACTION,[...]] [--security-style=SECURITY_STYLE; default="SECURITY_STYLE_UNSPECIFIED"] [--share-name=SHARE_NAME] @@ -143,6 +146,22 @@ FLAGS *enable-global-file-lock*::: If true, enable global file lock *cache-config*::: Cache-config as a hashtag-separated(#) list of key-value pairs + --cache-pre-populate=[exclude-path-list=EXCLUDE-PATH-LIST],[path-list=PATH-LIST],[recursion=RECURSION] + Cache Pre-populate contains cache pre-populate parameters of a volume. + + Cache Pre-populate will have the following format + --cache-pre-populate=path-list=PATH_LIST1#PATH_LIST2, + exclude-path-list=EXCLUDE_PATH_LIST1#EXCLUDE_PATH_LIST2, + recursion=RECURSION + + path-list + Hashtag-separated(#) list of paths to be pre-populated + exclude-path-list + Hashtag-separated(#) list of paths to be excluded from + pre-population + recursion + Boolean value indicating pre-populate recursion. + --capacity=CAPACITY The desired capacity of the Volume in GiB or TiB units.If no capacity unit is specified, GiB is assumed. @@ -153,7 +172,7 @@ FLAGS --enable-kerberos=ENABLE_KERBEROS Boolean flag indicating whether Volume is a kerberos Volume or not - --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4] + --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[anon-uid=ANON-UID],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4],[squash-mode=SQUASH-MODE] Export Policy of a Cloud NetApp Files Volume. This will be a field similar to network in which export policy fields can be specified as such: --export-policy=allowed-clients=ALLOWED_CLIENTS_IP_ADDRESSES, @@ -163,7 +182,8 @@ FLAGS kerberos-5i-read-only=KERBEROS_5I_READ_ONLY, kerberos-5i-read-write=KERBEROS_5I_READ_WRITE, kerberos-5p-read-only=KERBEROS_5P_READ_ONLY, - kerberos-5p-read-write=KERBEROS_5P_READ_WRITE + kerberos-5p-read-write=KERBEROS_5P_READ_WRITE, + squash-mode=SQUASH_MODE,anon-uid=ANON_UID --protocols=PROTOCOL,[PROTOCOL,...] Type of File System protocols for the Cloud NetApp Files Volume. Valid diff --git a/gcloud/beta/network-security/dns-threat-detectors/create b/gcloud/beta/network-security/dns-threat-detectors/create index 347ed3539..2a2fbcd9b 100644 --- a/gcloud/beta/network-security/dns-threat-detectors/create +++ b/gcloud/beta/network-security/dns-threat-detectors/create @@ -56,17 +56,18 @@ REQUIRED FLAGS value is supported): infoblox - The Infoblox DNS threat detecter. + The Infoblox DNS threat detector provider. OPTIONAL FLAGS --excluded-networks=[EXCLUDED_NETWORKS,...] - A list of Network resource names which are exempt from the - configuration in this DnsThreatDetector. + A list of network resource names which aren't monitored by this + DnsThreatDetector. Example: projects/PROJECT_ID/global/networks/NETWORK_NAME. --labels=[LABELS,...] - Labels as key value pairs. + Any labels associated with the DnsThreatDetector, listed as key value + pairs. KEY Keys must start with a lowercase character and contain only hyphens diff --git a/gcloud/beta/network-security/dns-threat-detectors/describe b/gcloud/beta/network-security/dns-threat-detectors/describe index abb41926c..2cb385ba4 100644 --- a/gcloud/beta/network-security/dns-threat-detectors/describe +++ b/gcloud/beta/network-security/dns-threat-detectors/describe @@ -16,7 +16,7 @@ EXAMPLES --location=global my-dns-threat-detector POSITIONAL ARGUMENTS - DnsThreatDetector resource - Name of the DnsThreatDetector resource The + DnsThreatDetector resource - Name of the DnsThreatDetector resource. 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/network-security/dns-threat-detectors/list b/gcloud/beta/network-security/dns-threat-detectors/list index 2ff005ba0..79f26a555 100644 --- a/gcloud/beta/network-security/dns-threat-detectors/list +++ b/gcloud/beta/network-security/dns-threat-detectors/list @@ -17,8 +17,8 @@ EXAMPLES --location=global REQUIRED FLAGS - Location resource - Parent value for ListDnsThreatDetectorsRequest This - represents a Cloud resource. (NOTE) Some attributes are not given + Location resource - The parent value for ListDnsThreatDetectorsRequest. + 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: diff --git a/gcloud/beta/network-security/dns-threat-detectors/update b/gcloud/beta/network-security/dns-threat-detectors/update index e46cdfa0d..eb7c5c650 100644 --- a/gcloud/beta/network-security/dns-threat-detectors/update +++ b/gcloud/beta/network-security/dns-threat-detectors/update @@ -63,7 +63,7 @@ FLAGS value is supported): infoblox - The Infoblox DNS threat detecter. + The Infoblox DNS threat detector provider. Update excluded_networks. @@ -88,7 +88,8 @@ FLAGS At most one of these can be specified: --labels=[LABELS,...] - Set labels to new value. Labels as key value pairs. + Set labels to new value. Any labels associated with the + DnsThreatDetector, listed as key value pairs. KEY Keys must start with a lowercase character and contain only @@ -111,7 +112,8 @@ FLAGS --labels=path_to_file.(yaml|json) --update-labels=[UPDATE_LABELS,...] - Update labels value or add key value pair. Labels as key value pairs. + Update labels value or add key value pair. Any labels associated with + the DnsThreatDetector, listed as key value pairs. KEY Keys must start with a lowercase character and contain only diff --git a/gcloud/beta/resource-manager/capabilities/describe b/gcloud/beta/resource-manager/capabilities/describe new file mode 100644 index 000000000..ccc3b584b --- /dev/null +++ b/gcloud/beta/resource-manager/capabilities/describe @@ -0,0 +1,43 @@ +NAME + gcloud beta resource-manager capabilities describe - show whether a + Capability is enabled + +SYNOPSIS + gcloud beta resource-manager capabilities describe CAPABILITY_ID + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Command to show whether a Capability is enabled. + + This command can fail for the following reasons: + ▪ The capability specified does not exist. + ▪ The active account does not have permission to access the given + folder/capability. + +EXAMPLES + The following command prints metadata for a capability with the ID + folders/123/capabilities/app-management: + + $ gcloud beta resource-manager capabilities describe \ + "folders/123/capabilities/app-management" + +POSITIONAL ARGUMENTS + CAPABILITY_ID + ID for the capability you want 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 beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager capabilities describe + + $ gcloud alpha resource-manager capabilities describe + diff --git a/gcloud/beta/resource-manager/capabilities/help b/gcloud/beta/resource-manager/capabilities/help new file mode 100644 index 000000000..79b9714cb --- /dev/null +++ b/gcloud/beta/resource-manager/capabilities/help @@ -0,0 +1,32 @@ +NAME + gcloud beta resource-manager capabilities - manage Cloud Folder + Capabilities + +SYNOPSIS + gcloud beta resource-manager capabilities COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Commands to query and update your Cloud Folder's Capabilities. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Show whether a Capability is enabled. + + update + (BETA) Update a folder capability. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager capabilities + + $ gcloud alpha resource-manager capabilities + diff --git a/gcloud/beta/resource-manager/capabilities/update b/gcloud/beta/resource-manager/capabilities/update new file mode 100644 index 000000000..ac1bb8fa3 --- /dev/null +++ b/gcloud/beta/resource-manager/capabilities/update @@ -0,0 +1,60 @@ +NAME + gcloud beta resource-manager capabilities update - update a folder + capability + +SYNOPSIS + gcloud beta resource-manager capabilities update CAPABILITY_ID + --[no-]enable [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Command to Update/Set the value field of the Folder capability. This + can be done by using the --enable flag to set the value to True, and the + --no-enable flag to set the value to False. + + This command can fail for the following reasons: + ▪ There is no folder parenting the given capability name. + ▪ The active account does not have permission to update the given + folder/capability. + +EXAMPLES + The following command updates a capability with the ID + folders/123/capabilities/app-management to have the value True: + + $ gcloud beta resource-manager capabilities update \ + "folders/123/capabilities/app-management" --enable + + In order to set the value to False, the following command can be used: + + $ gcloud beta resource-manager capabilities update \ + "folders/123/capabilities/app-management" --no-enable + +POSITIONAL ARGUMENTS + CAPABILITY_ID + ID for the capability you want to update. + +REQUIRED FLAGS + --[no-]enable + Enable the Capability. Use --enable to enable and --no-enable to + disable. + +OPTIONAL FLAGS + --update-mask=UPDATE_MASK + Update Mask. This is an optional field, and the only valid value this + can be set to currently is "value". + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager capabilities update + + $ gcloud alpha resource-manager capabilities update + diff --git a/gcloud/beta/resource-manager/help b/gcloud/beta/resource-manager/help index 5e2eb1765..b13b4762b 100644 --- a/gcloud/beta/resource-manager/help +++ b/gcloud/beta/resource-manager/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + capabilities + (BETA) Manage Cloud Folder Capabilities. + folders (BETA) Manage Cloud Folders. diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 90a826a10..371c71fcf 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -48,7 +48,7 @@ SYNOPSIS --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...] --command=[COMMAND,...] - | --function=FUNCTION --image=IMAGE --source=SOURCE] + | --function=FUNCTION --no-build --image=IMAGE --source=SOURCE] [--binary-authorization=POLICY | --clear-binary-authorization] [--clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] @@ -362,10 +362,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: cloud-storage: A volume representing a Cloud Storage bucket. This volume type is mounted using Cloud Storage FUSE. See @@ -378,11 +379,21 @@ FLAGS ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags should be specified without leading dashes and separated by semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ size-limit: (optional) A quantity representing the maximum amount of memory allocated to this volume, such as "512Mi" or "3G". Data stored in an in-memory volume consumes the memory allocation of the @@ -392,6 +403,11 @@ FLAGS nfs: Represents a volume backed by an NFS server. Additional keys: ◆ location: (required) The location of the NFS Server, in the form SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ readonly: (optional) A boolean. If true, this volume will be read-only from all mounts. @@ -644,6 +660,13 @@ FLAGS Specifies that the deployed object is a function. If a value is provided, that value is used as the entrypoint. + --no-build + When set, the cloud build step will be skipped and the provided + source code will be extracted directly on the base image. Your + source code must contain all the dependencies for your application. + See https://cloud.google.com/run/docs/deploying-source-code for + more details. + --image=IMAGE Name of the container image to deploy (e.g. us-docker.pkg.dev/cloudrun/container/hello:latest). When used with diff --git a/gcloud/beta/run/jobs/create b/gcloud/beta/run/jobs/create index 36397ee5c..a48f7cc15 100644 --- a/gcloud/beta/run/jobs/create +++ b/gcloud/beta/run/jobs/create @@ -156,10 +156,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: cloud-storage: A volume representing a Cloud Storage bucket. This volume type is mounted using Cloud Storage FUSE. See @@ -172,11 +173,21 @@ FLAGS ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags should be specified without leading dashes and separated by semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ size-limit: (optional) A quantity representing the maximum amount of memory allocated to this volume, such as "512Mi" or "3G". Data stored in an in-memory volume consumes the memory allocation of the @@ -186,6 +197,11 @@ FLAGS nfs: Represents a volume backed by an NFS server. Additional keys: ◆ location: (required) The location of the NFS Server, in the form SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ readonly: (optional) A boolean. If true, this volume will be read-only from all mounts. diff --git a/gcloud/beta/run/jobs/deploy b/gcloud/beta/run/jobs/deploy index f6ca17e73..12ddff0e0 100644 --- a/gcloud/beta/run/jobs/deploy +++ b/gcloud/beta/run/jobs/deploy @@ -161,10 +161,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: cloud-storage: A volume representing a Cloud Storage bucket. This volume type is mounted using Cloud Storage FUSE. See @@ -177,11 +178,21 @@ FLAGS ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags should be specified without leading dashes and separated by semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ size-limit: (optional) A quantity representing the maximum amount of memory allocated to this volume, such as "512Mi" or "3G". Data stored in an in-memory volume consumes the memory allocation of the @@ -191,6 +202,11 @@ FLAGS nfs: Represents a volume backed by an NFS server. Additional keys: ◆ location: (required) The location of the NFS Server, in the form SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ readonly: (optional) A boolean. If true, this volume will be read-only from all mounts. diff --git a/gcloud/beta/run/jobs/update b/gcloud/beta/run/jobs/update index eedde27d2..e693448b4 100644 --- a/gcloud/beta/run/jobs/update +++ b/gcloud/beta/run/jobs/update @@ -172,10 +172,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: cloud-storage: A volume representing a Cloud Storage bucket. This volume type is mounted using Cloud Storage FUSE. See @@ -188,11 +189,21 @@ FLAGS ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags should be specified without leading dashes and separated by semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ size-limit: (optional) A quantity representing the maximum amount of memory allocated to this volume, such as "512Mi" or "3G". Data stored in an in-memory volume consumes the memory allocation of the @@ -202,6 +213,11 @@ FLAGS nfs: Represents a volume backed by an NFS server. Additional keys: ◆ location: (required) The location of the NFS Server, in the form SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ readonly: (optional) A boolean. If true, this volume will be read-only from all mounts. diff --git a/gcloud/beta/run/multi-region-services/update b/gcloud/beta/run/multi-region-services/update index 2c5c3ea1b..2ad0b6654 100644 --- a/gcloud/beta/run/multi-region-services/update +++ b/gcloud/beta/run/multi-region-services/update @@ -334,10 +334,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: --clear-volumes Remove all existing volumes from the Cloud Run resource, including diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 4b92b83b0..a6384b5d2 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -332,10 +332,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: cloud-storage: A volume representing a Cloud Storage bucket. This volume type is mounted using Cloud Storage FUSE. See @@ -348,11 +349,21 @@ FLAGS ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags should be specified without leading dashes and separated by semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ size-limit: (optional) A quantity representing the maximum amount of memory allocated to this volume, such as "512Mi" or "3G". Data stored in an in-memory volume consumes the memory allocation of the @@ -362,6 +373,11 @@ FLAGS nfs: Represents a volume backed by an NFS server. Additional keys: ◆ location: (required) The location of the NFS Server, in the form SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ readonly: (optional) A boolean. If true, this volume will be read-only from all mounts. diff --git a/gcloud/beta/run/worker-pools/deploy b/gcloud/beta/run/worker-pools/deploy index 18f230d7c..09baa2475 100644 --- a/gcloud/beta/run/worker-pools/deploy +++ b/gcloud/beta/run/worker-pools/deploy @@ -194,10 +194,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: cloud-storage: A volume representing a Cloud Storage bucket. This volume type is mounted using Cloud Storage FUSE. See @@ -210,11 +211,21 @@ FLAGS ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags should be specified without leading dashes and separated by semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ size-limit: (optional) A quantity representing the maximum amount of memory allocated to this volume, such as "512Mi" or "3G". Data stored in an in-memory volume consumes the memory allocation of the @@ -224,6 +235,11 @@ FLAGS nfs: Represents a volume backed by an NFS server. Additional keys: ◆ location: (required) The location of the NFS Server, in the form SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ readonly: (optional) A boolean. If true, this volume will be read-only from all mounts. diff --git a/gcloud/beta/run/worker-pools/update b/gcloud/beta/run/worker-pools/update index 91be80c27..827a79ac0 100644 --- a/gcloud/beta/run/worker-pools/update +++ b/gcloud/beta/run/worker-pools/update @@ -190,10 +190,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: cloud-storage: A volume representing a Cloud Storage bucket. This volume type is mounted using Cloud Storage FUSE. See @@ -206,11 +207,21 @@ FLAGS ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags should be specified without leading dashes and separated by semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ size-limit: (optional) A quantity representing the maximum amount of memory allocated to this volume, such as "512Mi" or "3G". Data stored in an in-memory volume consumes the memory allocation of the @@ -220,6 +231,11 @@ FLAGS nfs: Represents a volume backed by an NFS server. Additional keys: ◆ location: (required) The location of the NFS Server, in the form SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ readonly: (optional) A boolean. If true, this volume will be read-only from all mounts. diff --git a/gcloud/beta/services/disable b/gcloud/beta/services/disable index 15685705f..f446d8424 100644 --- a/gcloud/beta/services/disable +++ b/gcloud/beta/services/disable @@ -3,7 +3,7 @@ NAME project, folder or organization SYNOPSIS - gcloud beta services disable [SERVICE ...] [--async] + gcloud beta services disable SERVICE [SERVICE ...] [--async] [--bypass-api-usage-check] [--force] [--validate-only] [--bypass-dependency-service-check | --disable-dependency-services] [--folder=FOLDER_ID | --organization=ORGANIZATION_ID @@ -49,7 +49,7 @@ EXAMPLES $ gcloud beta services disable my-consumed-service --async POSITIONAL ARGUMENTS - [SERVICE ...] + SERVICE [SERVICE ...] The name of the service(s) to disable. FLAGS diff --git a/gcloud/beta/services/enable b/gcloud/beta/services/enable index 94a21aa28..ade4b67c1 100644 --- a/gcloud/beta/services/enable +++ b/gcloud/beta/services/enable @@ -3,8 +3,8 @@ NAME project, folder or organization SYNOPSIS - gcloud beta services enable [SERVICE ...] [--async] [--skip-dependency] - [--validate-only] + gcloud beta services enable SERVICE [SERVICE ...] [--async] + [--skip-dependency] [--validate-only] [--folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] @@ -52,7 +52,7 @@ EXAMPLES $ gcloud beta services enable service1 service2 service3 POSITIONAL ARGUMENTS - [SERVICE ...] + SERVICE [SERVICE ...] The name of the service(s) to enable. FLAGS diff --git a/gcloud/beta/services/help b/gcloud/beta/services/help index 68439dd93..f8347660b 100644 --- a/gcloud/beta/services/help +++ b/gcloud/beta/services/help @@ -38,6 +38,9 @@ GROUPS identity (BETA) Manage service identity. + mcp + (BETA) List, enable and disable MCP endpoints. + operations (BETA) Manage Operation for various services. diff --git a/gcloud/beta/services/mcp/content-security/add b/gcloud/beta/services/mcp/content-security/add new file mode 100644 index 000000000..3cc5e0782 --- /dev/null +++ b/gcloud/beta/services/mcp/content-security/add @@ -0,0 +1,40 @@ +NAME + gcloud beta services mcp content-security add - add MCP content security + provider of a project + +SYNOPSIS + gcloud beta services mcp content-security add MCP_CONTENT_SECURITY_PROVIDER + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Add MCP content security provider of a project. + +EXAMPLES + Add MCP content security provider of a project: + + $ gcloud beta services mcp content-security add \ + my-mcp-content-security-provider + + Add MCP content security provider of a project my-project: + + $ gcloud beta services mcp content-security add \ + my-mcp-content-security-provider --project=my-project + +POSITIONAL ARGUMENTS + MCP_CONTENT_SECURITY_PROVIDER + The MCP content security provider to add. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp content-security add + diff --git a/gcloud/beta/services/mcp/content-security/get b/gcloud/beta/services/mcp/content-security/get new file mode 100644 index 000000000..77f9afa23 --- /dev/null +++ b/gcloud/beta/services/mcp/content-security/get @@ -0,0 +1,33 @@ +NAME + gcloud beta services mcp content-security get - get MCP content security + providers for a project + +SYNOPSIS + gcloud beta services mcp content-security get [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get MCP content security providers for a project. + +EXAMPLES + Get MCP content security providers for a project: + + $ gcloud beta services mcp content-security get + + Get MCP content security providers for a project my-project: + + $ gcloud beta services mcp content-security get --project=my-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. This + variant is also available: + + $ gcloud alpha services mcp content-security get + diff --git a/gcloud/beta/services/mcp/content-security/help b/gcloud/beta/services/mcp/content-security/help new file mode 100644 index 000000000..8f79a2872 --- /dev/null +++ b/gcloud/beta/services/mcp/content-security/help @@ -0,0 +1,33 @@ +NAME + gcloud beta services mcp content-security - get/add/remove MCP content + security + +SYNOPSIS + gcloud beta services mcp content-security COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get/add/remove MCP content security. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add + (BETA) Add MCP content security provider of a project. + + get + (BETA) Get MCP content security providers for a project. + + remove + (BETA) Remove MCP content security provider of a project. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp content-security + diff --git a/gcloud/beta/services/mcp/content-security/remove b/gcloud/beta/services/mcp/content-security/remove new file mode 100644 index 000000000..eec8566d3 --- /dev/null +++ b/gcloud/beta/services/mcp/content-security/remove @@ -0,0 +1,40 @@ +NAME + gcloud beta services mcp content-security remove - remove MCP content + security provider of a project + +SYNOPSIS + gcloud beta services mcp content-security remove + MCP_CONTENT_SECURITY_PROVIDER [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Remove MCP content security provider of a project. + +EXAMPLES + Remove MCP content security provider of a project: + + $ gcloud beta services mcp content-security remove \ + my-mcp-content-security-provider + + Remove MCP content security provider of a project my-project: + + $ gcloud beta services mcp content-security remove \ + my-mcp-content-security-provider --project=my-project + +POSITIONAL ARGUMENTS + MCP_CONTENT_SECURITY_PROVIDER + The MCP content security provider to remove. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp content-security remove + diff --git a/gcloud/beta/services/mcp/disable b/gcloud/beta/services/mcp/disable new file mode 100644 index 000000000..f368ac286 --- /dev/null +++ b/gcloud/beta/services/mcp/disable @@ -0,0 +1,80 @@ +NAME + gcloud beta services mcp disable - disable a service for MCP on a project, + folder or organization + +SYNOPSIS + gcloud beta services mcp disable SERVICE [--async] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Disable a service for MCP on a project, folder or organization + +EXAMPLES + To disable a service for MCP called my-service on the current project, run: + + $ gcloud beta services mcp disable my-service + + To disable a service for MCP called my-service on the project my-project, + run: + + $ gcloud beta services mcp disable my-service --project=my-project + + To disable a service for MCP called my-service on the folder my-folder, + run: + + $ gcloud beta services mcp disable my-service --folder=my-folder + + To disable a service for MCP called my-service on the organization + my-organization, run: + + $ gcloud beta services mcp disable my-service \ + --organization=my-organization + + To run the same command asynchronously (non-blocking), run: + + $ gcloud beta services mcp disable my-service --async + +POSITIONAL ARGUMENTS + SERVICE + The name of the service to disable MCP. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp disable + diff --git a/gcloud/beta/services/mcp/enable b/gcloud/beta/services/mcp/enable new file mode 100644 index 000000000..e2fec92ef --- /dev/null +++ b/gcloud/beta/services/mcp/enable @@ -0,0 +1,79 @@ +NAME + gcloud beta services mcp enable - enable a service for MCP on a project, + folder or organization + +SYNOPSIS + gcloud beta services mcp enable SERVICE [--async] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Enable a service for MCP on a project, folder or organization + +EXAMPLES + To enable a service for MCP called my-service on the current project, run: + + $ gcloud beta services mcp enable my-service + + To enable a service for MCP called my-service on the project my-project, + run: + + $ gcloud beta services mcp enable my-service --project=my-project + + To enable a service for MCP called my-service on the folder my-folder, run: + + $ gcloud beta services mcp enable my-service --folder=my-folder + + To enable a service for MCP called my-service on the organization + my-organization, run: + + $ gcloud beta services mcp enable my-service \ + --organization=my-organization + + To run the same command asynchronously (non-blocking), run: + + $ gcloud beta services mcp enable my-service --async + +POSITIONAL ARGUMENTS + SERVICE + The name of the service to enable MCP. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp enable + diff --git a/gcloud/beta/services/mcp/help b/gcloud/beta/services/mcp/help new file mode 100644 index 000000000..d43fa8518 --- /dev/null +++ b/gcloud/beta/services/mcp/help @@ -0,0 +1,38 @@ +NAME + gcloud beta services mcp - list, enable and disable MCP endpoints + +SYNOPSIS + gcloud beta services mcp GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List, enable and disable MCP endpoints. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + content-security + (BETA) Get/add/remove MCP content security. + +COMMANDS + COMMAND is one of the following: + + disable + (BETA) Disable a service for MCP on a project, folder or organization. + + enable + (BETA) Enable a service for MCP on a project, folder or organization. + + list + (BETA) List MCP services for a project, folder or organization. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp + diff --git a/gcloud/beta/services/mcp/list b/gcloud/beta/services/mcp/list new file mode 100644 index 000000000..322d22b10 --- /dev/null +++ b/gcloud/beta/services/mcp/list @@ -0,0 +1,95 @@ +NAME + gcloud beta services mcp list - list MCP services for a project, folder or + organization + +SYNOPSIS + gcloud beta services mcp list [--available | --enabled] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE; default=1000] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command lists the MCP services that are enabled or available + (with MCP endpoints) to be MCP enabled by a project, folder or + organization. + +EXAMPLES + To list the services the current project has enabled for MCP, run: + + $ gcloud beta services mcp list --enabled + + To list the services the current project can enable for MCP, run: + + $ gcloud beta services mcp list --available + +FLAGS + At most one of these can be specified: + + --available + Return the services available to the project, folder or organization + to enable for MCP. + + --enabled + (DEFAULT) Return the MCP services which the project, folder or + organization has enabled. + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +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; default=1000 + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + 1000. Paging may be applied before or after --filter and --limit + depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp list + diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index 8eb1dc132..9efa1b64c 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -52,6 +52,7 @@ SYNOPSIS [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] + [--performance-capture-config=KEY=VALUE,[KEY=VALUE,...]] [--psc-auto-connections=[network=NETWORK],[project=PROJECT]] [--[no-]recreate-replicas-on-primary-crash] [--replica-type=REPLICA_TYPE] [--replication=REPLICATION] @@ -75,6 +76,8 @@ SYNOPSIS : --disk-encryption-key-keyring=DISK_ENCRYPTION_KEY_KEYRING --disk-encryption-key-location=DISK_ENCRYPTION_KEY_LOCATION --disk-encryption-key-project=DISK_ENCRYPTION_KEY_PROJECT] + [--entra-id-application-id=ENTRA_ID_APPLICATION_ID + --entra-id-tenant-id=ENTRA_ID_TENANT_ID] [--master-dump-file-path=MASTER_DUMP_FILE_PATH --master-username=MASTER_USERNAME : [--master-ca-certificate-path=MASTER_CA_CERTIFICATE_PATH @@ -503,6 +506,15 @@ FLAGS Number of previous passwords that cannot be reused. The valid range is 0 to 100. + --performance-capture-config=KEY=VALUE,[KEY=VALUE,...] + A comma-separated list of performance capture settings to add to the + MySQL instance. The input should be in a format of key=value. Available + case-sensitive keys are: enabled (boolean), probing-interval-seconds + (integer), probe-threshold (integer), running-threads-threshold + (integer), seconds-behind-source-threshold (integer), and + transaction-duration-threshold (integer). Example: + --performance-capture-config enabled=true,probe-threshold=5 + --psc-auto-connections=[network=NETWORK],[project=PROJECT] A comma-separated list of networks or network-project pairs. Each project is represented by a project number (numeric) or by a project ID @@ -716,6 +728,20 @@ FLAGS line; ▸ set the property core/project. + Entraid configuration for the SQL Server instance. + + --entra-id-application-id=ENTRA_ID_APPLICATION_ID + Set the Entraid application ID. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --entra-id-tenant-id=ENTRA_ID_TENANT_ID + Set the Entraid tenant ID. + + This flag argument must be specified if any of the other arguments in + this group are specified. + Options for creating an internal replica of an external data source. --master-dump-file-path=MASTER_DUMP_FILE_PATH diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index c822b6364..0c948b86f 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -15,7 +15,7 @@ SYNOPSIS [--audit-retention-interval=AUDIT_RETENTION_INTERVAL] [--audit-upload-interval=AUDIT_UPLOAD_INTERVAL] [--availability-type=AVAILABILITY_TYPE] [--clear-active-directory] - [--clear-active-directory-dns-servers] + [--clear-active-directory-dns-servers] [--clear-entra-id-config] [--clear-failover-dr-replica-name] [--clear-password-policy] [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] [--data-api-access=DATA_API_ACCESS] @@ -53,6 +53,7 @@ SYNOPSIS [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] + [--performance-capture-config=KEY=VALUE,[KEY=VALUE,...]] [--pricing-plan=PRICING_PLAN, -p PRICING_PLAN] [--reconcile-psa-networking] [--[no-]recreate-replicas-on-primary-crash] @@ -85,6 +86,8 @@ SYNOPSIS | --psc-auto-connections=[network=NETWORK],[project=PROJECT]] [--clear-psc-network-attachment-uri | --psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI] + [--entra-id-application-id=ENTRA_ID_APPLICATION_ID + --entra-id-tenant-id=ENTRA_ID_TENANT_ID] [--gce-zone=GCE_ZONE | --secondary-zone=SECONDARY_ZONE --zone=ZONE] [--[no-]auto-scale-disable-scale-in --[no-]auto-scale-enabled --auto-scale-in-cooldown-seconds=AUTO_SCALE_IN_COOLDOWN_SECONDS @@ -182,6 +185,9 @@ FLAGS --clear-active-directory-dns-servers Removes the list of DNS Servers from the Active Directory Config. + --clear-entra-id-config + Clear the Entra ID config for the SQL Server instance. + --clear-failover-dr-replica-name Clear the DR replica setting for the primary instance. Flag is only available for MySQL and PostgreSQL database instances. @@ -465,6 +471,15 @@ FLAGS Number of previous passwords that cannot be reused. The valid range is 0 to 100. + --performance-capture-config=KEY=VALUE,[KEY=VALUE,...] + A comma-separated list of performance capture settings to add to the + MySQL instance. The input should be in a format of key=value. Available + case-sensitive keys are: enabled (boolean), probing-interval-seconds + (integer), probe-threshold (integer), running-threads-threshold + (integer), seconds-behind-source-threshold (integer), and + transaction-duration-threshold (integer). Example: + --performance-capture-config enabled=true,probe-threshold=5 + --pricing-plan=PRICING_PLAN, -p PRICING_PLAN First Generation instances only. The pricing plan for this instance. PRICING_PLAN must be one of: PER_USE, PACKAGE. @@ -753,6 +768,20 @@ FLAGS Service Connect (PSC). For example, this would be of the form:--psc-network-attachment-uri=projects/test-project/regions/us-central1/networkAttachments/my-na + Entraid configuration for the SQL Server instance. + + --entra-id-application-id=ENTRA_ID_APPLICATION_ID + Set the Entraid application ID. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --entra-id-tenant-id=ENTRA_ID_TENANT_ID + Set the Entraid tenant ID. + + This flag argument must be specified if any of the other arguments in + this group are specified. + At most one of these can be specified: --gce-zone=GCE_ZONE diff --git a/gcloud/beta/sql/ssl/entraid-certs/create b/gcloud/beta/sql/ssl/entraid-certs/create new file mode 100644 index 000000000..fba19a6d8 --- /dev/null +++ b/gcloud/beta/sql/ssl/entraid-certs/create @@ -0,0 +1,34 @@ +NAME + gcloud beta sql ssl entraid-certs create - create an Entra ID certificate + for a Cloud SQL instance + +SYNOPSIS + gcloud beta sql ssl entraid-certs create --instance=INSTANCE, -i INSTANCE + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create an Entra ID certificate for a Cloud SQL instance. + +REQUIRED FLAGS + --instance=INSTANCE, -i INSTANCE + Cloud SQL instance ID. + +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. This + variant is also available: + + $ gcloud alpha sql ssl entraid-certs create + diff --git a/gcloud/beta/sql/ssl/entraid-certs/help b/gcloud/beta/sql/ssl/entraid-certs/help new file mode 100644 index 000000000..d977f2de6 --- /dev/null +++ b/gcloud/beta/sql/ssl/entraid-certs/help @@ -0,0 +1,40 @@ +NAME + gcloud beta sql ssl entraid-certs - provide commands for managing Entra ID + certificates of Cloud SQL instances + +SYNOPSIS + gcloud beta sql ssl entraid-certs COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Provide commands for managing Entra ID certificates of Cloud SQL + instances, including creating, listing, rotating in, and rolling back + certificates. + +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 Entra ID certificate for a Cloud SQL instance. + + list + (BETA) List all Entra ID certificates for a Cloud SQL instance. + + rollback + (BETA) Roll back to the previous Entra ID certificate for a Cloud SQL + instance. + + rotate + (BETA) Rotate in the upcoming Entra ID certificate for a Cloud SQL + instance. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha sql ssl entraid-certs + diff --git a/gcloud/beta/sql/ssl/entraid-certs/list b/gcloud/beta/sql/ssl/entraid-certs/list new file mode 100644 index 000000000..48a57ca7e --- /dev/null +++ b/gcloud/beta/sql/ssl/entraid-certs/list @@ -0,0 +1,62 @@ +NAME + gcloud beta sql ssl entraid-certs list - list all Entra ID certificates for + a Cloud SQL instance + +SYNOPSIS + gcloud beta sql ssl entraid-certs list --instance=INSTANCE, -i INSTANCE + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all Entra ID certificates for a Cloud SQL instance. + +REQUIRED FLAGS + --instance=INSTANCE, -i INSTANCE + Cloud SQL instance ID. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha sql ssl entraid-certs list + diff --git a/gcloud/beta/sql/ssl/entraid-certs/rollback b/gcloud/beta/sql/ssl/entraid-certs/rollback new file mode 100644 index 000000000..ba723e86b --- /dev/null +++ b/gcloud/beta/sql/ssl/entraid-certs/rollback @@ -0,0 +1,35 @@ +NAME + gcloud beta sql ssl entraid-certs rollback - roll back to the previous + Entra ID certificate for a Cloud SQL instance + +SYNOPSIS + gcloud beta sql ssl entraid-certs rollback --instance=INSTANCE, -i INSTANCE + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Roll back to the previous Entra ID certificate for a Cloud SQL + instance. + +REQUIRED FLAGS + --instance=INSTANCE, -i INSTANCE + Cloud SQL instance ID. + +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. This + variant is also available: + + $ gcloud alpha sql ssl entraid-certs rollback + diff --git a/gcloud/beta/sql/ssl/entraid-certs/rotate b/gcloud/beta/sql/ssl/entraid-certs/rotate new file mode 100644 index 000000000..93c99885a --- /dev/null +++ b/gcloud/beta/sql/ssl/entraid-certs/rotate @@ -0,0 +1,35 @@ +NAME + gcloud beta sql ssl entraid-certs rotate - rotate in the upcoming Entra ID + certificate for a Cloud SQL instance + +SYNOPSIS + gcloud beta sql ssl entraid-certs rotate --instance=INSTANCE, -i INSTANCE + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Rotate in the upcoming Entra ID certificate for a Cloud SQL + instance. + +REQUIRED FLAGS + --instance=INSTANCE, -i INSTANCE + Cloud SQL instance ID. + +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. This + variant is also available: + + $ gcloud alpha sql ssl entraid-certs rotate + diff --git a/gcloud/beta/sql/ssl/help b/gcloud/beta/sql/ssl/help index 06b1f9c2e..afc643a21 100644 --- a/gcloud/beta/sql/ssl/help +++ b/gcloud/beta/sql/ssl/help @@ -21,6 +21,10 @@ GROUPS (BETA) Provide commands for managing client certificates of Cloud SQL instances. + entraid-certs + (BETA) Provide commands for managing Entra ID certificates of Cloud SQL + instances. + server-ca-certs (BETA) Provide commands for managing server CA certs of Cloud SQL instances. diff --git a/gcloud/beta/workstations/configs/create b/gcloud/beta/workstations/configs/create index f1ae716fb..e7332284a 100644 --- a/gcloud/beta/workstations/configs/create +++ b/gcloud/beta/workstations/configs/create @@ -38,8 +38,11 @@ SYNOPSIS | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE; default="codeoss"] [--kms-key=KMS_KEY : --kms-key-service-account=KMS_KEY_SERVICE_ACCOUNT] - [--no-persistent-storage | --pd-disk-type=PD_DISK_TYPE; - default="pd-standard" --pd-reclaim-policy=PD_RECLAIM_POLICY; + [--no-persistent-storage | --disk-reclaim-policy=DISK_RECLAIM_POLICY; + default="delete" --disk-type=DISK_TYPE --disk-size=DISK_SIZE + | --disk-source-snapshot=DISK_SOURCE_SNAPSHOT + | --pd-disk-type=PD_DISK_TYPE; default="pd-standard" + --pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete" --pd-disk-size=PD_DISK_SIZE; default=200 | --pd-source-snapshot=PD_SOURCE_SNAPSHOT] [GCLOUD_WIDE_FLAG ...] @@ -516,30 +519,51 @@ FLAGS If set, workstations under this configuration will not have a persistent directory. - Persistent directory configuration. + --disk-reclaim-policy=DISK_RECLAIM_POLICY; default="delete" + What should happen to the disk after the Workstation is deleted. + DISK_RECLAIM_POLICY must be one of: - --pd-disk-type=PD_DISK_TYPE; default="pd-standard" - Type of the persistent directory. PD_DISK_TYPE must be one of: - pd-standard, pd-balanced, pd-ssd. + delete + The persistent disk will be deleted with the Workstation. + retain + The persistent disk will be remain after the workstation is + deleted and the administrator must manually delete the disk. - --pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete" - What should happen to the disk after the Workstation is deleted. - PD_RECLAIM_POLICY must be one of: + --disk-type=DISK_TYPE + Type of the persistent directory. DISK_TYPE must be one of: + pd-standard, pd-balanced, pd-ssd, hyperdisk-balanced-ha. - delete - The persistent disk will be deleted with the Workstation. - retain - The persistent disk will be remain after the workstation is - deleted and the administrator must manually delete the disk. + At most one of these can be specified: - At most one of these can be specified: + --disk-size=DISK_SIZE + Size of the persistent directory in GB. DISK_SIZE must be one of: + 10, 50, 100, 200, 500, 1000. - --pd-disk-size=PD_DISK_SIZE; default=200 - Size of the persistent directory in GB. PD_DISK_SIZE must be one - of: 10, 50, 100, 200, 500, 1000. + --disk-source-snapshot=DISK_SOURCE_SNAPSHOT + Name of the snapshot to use as the source for the home disk. - --pd-source-snapshot=PD_SOURCE_SNAPSHOT - Name of the snapshot to use as the source for the home disk. + --pd-disk-type=PD_DISK_TYPE; default="pd-standard" + Type of the persistent directory. PD_DISK_TYPE must be one of: + pd-standard, pd-balanced, pd-ssd. + + --pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete" + What should happen to the disk after the Workstation is deleted. + PD_RECLAIM_POLICY must be one of: + + delete + The persistent disk will be deleted with the Workstation. + retain + The persistent disk will be remain after the workstation is + deleted and the administrator must manually delete the disk. + + At most one of these can be specified: + + --pd-disk-size=PD_DISK_SIZE; default=200 + Size of the persistent directory in GB. PD_DISK_SIZE must be one + of: 10, 50, 100, 200, 500, 1000. + + --pd-source-snapshot=PD_SOURCE_SNAPSHOT + Name of the snapshot to use as the source for the home disk. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/workstations/configs/update b/gcloud/beta/workstations/configs/update index 29efbe38b..102c8638e 100644 --- a/gcloud/beta/workstations/configs/update +++ b/gcloud/beta/workstations/configs/update @@ -34,7 +34,10 @@ SYNOPSIS [--disable-localhost-replacement | --enable-localhost-replacement] [--disable-ssh-to-vm | --enable-ssh-to-vm] [--disable-tcp-connections | --enable-tcp-connections] - [--pd-source-snapshot=PD_SOURCE_SNAPSHOT | --pd-disk-size=PD_DISK_SIZE + [--disk-source-snapshot=DISK_SOURCE_SNAPSHOT + | --pd-source-snapshot=PD_SOURCE_SNAPSHOT + | --disk-size=DISK_SIZE --disk-type=DISK_TYPE + | --pd-disk-size=PD_DISK_SIZE --pd-disk-type=PD_DISK_TYPE; default="pd-standard"] [GCLOUD_WIDE_FLAG ...] @@ -460,20 +463,28 @@ FLAGS At most one of these can be specified: + --disk-source-snapshot=DISK_SOURCE_SNAPSHOT + Name of the snapshot to use as the source for the home disk. + --pd-source-snapshot=PD_SOURCE_SNAPSHOT Name of the snapshot to use as the source for the persistent directory. - --pd-source-snapshot cannot be specified when --pd-disk-size or - --pd-disk-type is specified. + --disk-size=DISK_SIZE + Size of the persistent directory in GB. DISK_SIZE must be one of: 10, + 50, 100, 200, 500, 1000. - --pd-disk-size=PD_DISK_SIZE - Size of the persistent directory in GB. PD_DISK_SIZE must be one - of: 10, 50, 100, 200, 500, 1000. + --disk-type=DISK_TYPE + Type of the persistent directory. DISK_TYPE must be one of: + pd-standard, pd-balanced, pd-ssd, hyperdisk-balanced-ha. - --pd-disk-type=PD_DISK_TYPE; default="pd-standard" - Type of the persistent directory. PD_DISK_TYPE must be one of: - pd-standard, pd-balanced, pd-ssd. + --pd-disk-size=PD_DISK_SIZE + Size of the persistent directory in GB. PD_DISK_SIZE must be one of: + 10, 50, 100, 200, 500, 1000. + + --pd-disk-type=PD_DISK_TYPE; default="pd-standard" + Type of the persistent directory. PD_DISK_TYPE must be one of: + pd-standard, pd-balanced, pd-ssd. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beyondcorp/help b/gcloud/beyondcorp/help new file mode 100644 index 000000000..4eb30dd6b --- /dev/null +++ b/gcloud/beyondcorp/help @@ -0,0 +1,30 @@ +NAME + gcloud beyondcorp - manage Beyondcorp resources + +SYNOPSIS + gcloud beyondcorp GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Beyondcorp resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + operations + Manage Operation resources. + + security-gateways + Manage Security Gateway resources. + +NOTES + These variants are also available: + + $ gcloud alpha beyondcorp + + $ gcloud beta beyondcorp + diff --git a/gcloud/beyondcorp/operations/describe b/gcloud/beyondcorp/operations/describe new file mode 100644 index 000000000..50455f0cd --- /dev/null +++ b/gcloud/beyondcorp/operations/describe @@ -0,0 +1,57 @@ +NAME + gcloud beyondcorp operations describe - describe operations + +SYNOPSIS + gcloud beyondcorp operations describe (OPERATION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an operation + +EXAMPLES + To describe the operation, run: + + $ gcloud beyondcorp operations describe + +POSITIONAL ARGUMENTS + Operation resource - The name of the operation resource. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument operation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the operation resource. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +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 beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ diff --git a/gcloud/beyondcorp/operations/help b/gcloud/beyondcorp/operations/help new file mode 100644 index 000000000..1dc1d89c7 --- /dev/null +++ b/gcloud/beyondcorp/operations/help @@ -0,0 +1,22 @@ +NAME + gcloud beyondcorp operations - manage Operation resources + +SYNOPSIS + gcloud beyondcorp operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Operation resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe operations. + + list + List operations. diff --git a/gcloud/beyondcorp/operations/list b/gcloud/beyondcorp/operations/list new file mode 100644 index 000000000..f0b41678e --- /dev/null +++ b/gcloud/beyondcorp/operations/list @@ -0,0 +1,78 @@ +NAME + gcloud beyondcorp operations list - list operations + +SYNOPSIS + gcloud beyondcorp operations list --location=LOCATION [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List operations + +EXAMPLES + To list all operations, run: + + $ gcloud beyondcorp operations list + +REQUIRED FLAGS + Location resource - The name of the operation's parent resource. 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --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. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ diff --git a/gcloud/beyondcorp/security-gateways/applications/create b/gcloud/beyondcorp/security-gateways/applications/create new file mode 100644 index 000000000..f3a1d4ca8 --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/applications/create @@ -0,0 +1,226 @@ +NAME + gcloud beyondcorp security-gateways applications create - create + applications + +SYNOPSIS + gcloud beyondcorp security-gateways applications create + (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) + [--async] [--display-name=DISPLAY_NAME] + [--endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS]] + [--request-id=REQUEST_ID] [--schema=SCHEMA] + [--upstreams=[egressPolicy=EGRESSPOLICY], + [external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create an application + +EXAMPLES + To create the application, run: + + $ gcloud beyondcorp security-gateways applications create + +POSITIONAL ARGUMENTS + Application resource - Identifier. Name of the resource. 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application 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 id of the application resource. We support only global + location. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --security-gateway=SECURITY_GATEWAY + The securityGateway id of the application resource. + + To set the security-gateway attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --security-gateway on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the application resource. Cannot + exceed 64 characters. + + --endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] + An array of conditions to match the application's network endpoint. + Each element in the array is an EndpointMatcher object, which defines a + specific combination of a hostname pattern and one or more ports. The + application is considered matched if at least one of the + EndpointMatcher conditions in this array is met (the conditions are + combined using OR logic). Each EndpointMatcher must contain a hostname + pattern, such as "example.com", and one or more port numbers specified + as a string, such as "443". + + Hostname and port number examples: ".example.com", "443" "example.com" + and "22" "example.com" and "22,33". + + hostname + Hostname of the application. + + ports + The ports of the application. + + Shorthand Example: + + --endpoint-matchers=hostname=string,ports=[int] --endpoint-matchers=hostname=string,ports=[int] + + JSON Example: + + --endpoint-matchers='[{"hostname": "string", "ports": [int]}]' + + File Example: + + --endpoint-matchers=path_to_file.(yaml|json) + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + --schema=SCHEMA + Type of the external application. SCHEMA must be one of: + + api-gateway + Service Discovery API endpoint when Service Discovery is enabled in + Gateway. + proxy-gateway + Proxy which routes traffic to actual applications, like Netscaler + Gateway. + + --upstreams=[egressPolicy=EGRESSPOLICY],[external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL] + Which upstream resources to forward traffic to. + + egressPolicy + Routing policy information. + + regions + List of the regions where the application sends traffic. + + external + List of the external endpoints to forward traffic to. + + endpoints + List of the endpoints to forward traffic to. + + hostname + Hostname of the endpoint. + + port + Port of the endpoint. + + network + Network to forward traffic to. + + name + Network name is of the format: + projects/{project}/global/networks/{network}. + + proxyProtocol + Enables proxy protocol configuration for the upstream. + + allowedClientHeaders + List of the allowed client header names. + + clientIp + Client IP configuration. The client IP address is included if + true. + + contextualHeaders + Configuration for the contextual headers. + + deviceInfo + The device information configuration. + + outputType + The output type details for the delegated device. + + groupInfo + Group details. + + outputType + The output type of the delegated group information. + + outputType + Default output type for all enabled headers. + + userInfo + User details. + + outputType + The delegated user's information. + + gatewayIdentity + The security gateway identity configuration. + + metadataHeaders + Custom resource specific headers along with the values. The + names should conform to RFC 9110: >Field names can contain + alphanumeric characters, hyphens, and periods, can contain only + ASCII-printable characters and tabs, and must start with a + letter. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} --upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} + + JSON Example: + + --upstreams='[{"egressPolicy": {"regions": ["string"]}, "external": {"endpoints": [{"hostname": "string", "port": int}]}, "network": {"name": "string"}, "proxyProtocol": {"allowedClientHeaders": ["string"], "clientIp": boolean, "contextualHeaders": {"deviceInfo": {"outputType": "string"}, "groupInfo": {"outputType": "string"}, "outputType": "string", "userInfo": {"outputType": "string"}}, "gatewayIdentity": "string", "metadataHeaders": {"string": "string"}}}]' + + File Example: + + --upstreams=path_to_file.(yaml|json) + +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 beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways applications create + diff --git a/gcloud/beyondcorp/security-gateways/applications/delete b/gcloud/beyondcorp/security-gateways/applications/delete new file mode 100644 index 000000000..364dcb521 --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/applications/delete @@ -0,0 +1,100 @@ +NAME + gcloud beyondcorp security-gateways applications delete - delete + applications + +SYNOPSIS + gcloud beyondcorp security-gateways applications delete + (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) + [--async] [--request-id=REQUEST_ID] [--validate-only] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an application + +EXAMPLES + To delete the application, run: + + $ gcloud beyondcorp security-gateways applications delete + +POSITIONAL ARGUMENTS + Application resource - Name of the resource. 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application 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 id of the application resource. We support only global + location. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --security-gateway=SECURITY_GATEWAY + The securityGateway id of the application resource. + + To set the security-gateway attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --security-gateway on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --validate-only + If set, validates request by executing a dry-run which would not alter + the resource in any way. + +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 beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways applications delete + diff --git a/gcloud/beyondcorp/security-gateways/applications/describe b/gcloud/beyondcorp/security-gateways/applications/describe new file mode 100644 index 000000000..9a06c81ac --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/applications/describe @@ -0,0 +1,77 @@ +NAME + gcloud beyondcorp security-gateways applications describe - describe + applications + +SYNOPSIS + gcloud beyondcorp security-gateways applications describe + (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an application + +EXAMPLES + To describe the application, run: + + $ gcloud beyondcorp security-gateways applications describe + +POSITIONAL ARGUMENTS + Application resource - The resource name of the Application using the + form: + projects/{project_id}/locations/global/securityGateway/{security_gateway_id}/applications/{application_id} + 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application 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 id of the application resource. We support only global + location. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --security-gateway=SECURITY_GATEWAY + The securityGateway id of the application resource. + + To set the security-gateway attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --security-gateway on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways applications describe + diff --git a/gcloud/beyondcorp/security-gateways/applications/get-iam-policy b/gcloud/beyondcorp/security-gateways/applications/get-iam-policy new file mode 100644 index 000000000..4689bea2e --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/applications/get-iam-policy @@ -0,0 +1,106 @@ +NAME + gcloud beyondcorp security-gateways applications get-iam-policy - get the + IAM policy for a security gateway application + +SYNOPSIS + gcloud beyondcorp security-gateways applications get-iam-policy + (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Gets the IAM policy for the given security gateway application. + +EXAMPLES + To get the IAM policy for a security gateway application + my-security-gateway-application run: + + $ gcloud beyondcorp security-gateways applications get-iam-policy \ + my-security-gateway-application --project=consumer-project-id \ + --location=global + +POSITIONAL ARGUMENTS + Application resource - The security gateway application for which to get + the IAM policy. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application 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 id of the application resource. We support only global + location. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --security-gateway=SECURITY_GATEWAY + The securityGateway id of the application resource. + + To set the security-gateway attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --security-gateway on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways applications \ + get-iam-policy + diff --git a/gcloud/beyondcorp/security-gateways/applications/help b/gcloud/beyondcorp/security-gateways/applications/help new file mode 100644 index 000000000..b99ba420a --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/applications/help @@ -0,0 +1,45 @@ +NAME + gcloud beyondcorp security-gateways applications - manage Application + resources + +SYNOPSIS + gcloud beyondcorp security-gateways applications COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Application resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create applications. + + delete + Delete applications. + + describe + Describe applications. + + get-iam-policy + Get the IAM policy for a security gateway application. + + list + List applications. + + set-iam-policy + Set the IAM policy for a security gateway application. + + update + Update applications. + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways applications + diff --git a/gcloud/beyondcorp/security-gateways/applications/list b/gcloud/beyondcorp/security-gateways/applications/list new file mode 100644 index 000000000..8bd86e73f --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/applications/list @@ -0,0 +1,101 @@ +NAME + gcloud beyondcorp security-gateways applications list - list applications + +SYNOPSIS + gcloud beyondcorp security-gateways applications list + (--security-gateway=SECURITY_GATEWAY : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List applications + +EXAMPLES + To list all applications, run: + + $ gcloud beyondcorp security-gateways applications list + +REQUIRED FLAGS + SecurityGateway resource - The parent location to which the resources + belong. + projects/{project_id}/locations/global/securityGateways/{security_gateway_id} + 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 --security-gateway 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. + + --security-gateway=SECURITY_GATEWAY + ID of the securityGateway or fully qualified identifier for the + securityGateway. + + To set the security-gateway attribute: + ▸ provide the argument --security-gateway on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location id of the securityGateway resource. We support only + global location. + + To set the location attribute: + ▸ provide the argument --security-gateway on the command line with + a fully specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways applications list + diff --git a/gcloud/beyondcorp/security-gateways/applications/set-iam-policy b/gcloud/beyondcorp/security-gateways/applications/set-iam-policy new file mode 100644 index 000000000..e27550b8d --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/applications/set-iam-policy @@ -0,0 +1,86 @@ +NAME + gcloud beyondcorp security-gateways applications set-iam-policy - set the + IAM policy for a security gateway application + +SYNOPSIS + gcloud beyondcorp security-gateways applications set-iam-policy + (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) + POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Sets the IAM policy for the given security gateway application. + +EXAMPLES + The following command will read an IAM policy defined in a JSON file + 'policy.json' and set it for the security gateway application with ID + my-security-gateway-application: + + $ gcloud beyondcorp security-gateways applications set-iam-policy \ + my-security-gateway-application policy.json --location=global + +POSITIONAL ARGUMENTS + Application resource - The security gateway application for which to set + the IAM policy. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application 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 id of the application resource. We support only global + location. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --security-gateway=SECURITY_GATEWAY + The securityGateway id of the application resource. + + To set the security-gateway attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --security-gateway on the command line. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +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 beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways applications \ + set-iam-policy + diff --git a/gcloud/beyondcorp/security-gateways/applications/update b/gcloud/beyondcorp/security-gateways/applications/update new file mode 100644 index 000000000..9dffd3ea0 --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/applications/update @@ -0,0 +1,509 @@ +NAME + gcloud beyondcorp security-gateways applications update - update + applications + +SYNOPSIS + gcloud beyondcorp security-gateways applications update + (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) + [--async] [--display-name=DISPLAY_NAME] [--request-id=REQUEST_ID] + [--schema=SCHEMA] + [--endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] + | --add-endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] + --clear-endpoint-matchers + | --remove-endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS]] + [--upstreams=[egressPolicy=EGRESSPOLICY], + [external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL] + | --add-upstreams=[egressPolicy=EGRESSPOLICY], + [external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL] + --clear-upstreams + | --remove-upstreams=[egressPolicy=EGRESSPOLICY], + [external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an application + +EXAMPLES + To update the application, run: + + $ gcloud beyondcorp security-gateways applications update + +POSITIONAL ARGUMENTS + Application resource - Identifier. Name of the resource. 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application 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 id of the application resource. We support only global + location. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --security-gateway=SECURITY_GATEWAY + The securityGateway id of the application resource. + + To set the security-gateway attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --security-gateway on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the application resource. Cannot + exceed 64 characters. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request timed out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --schema=SCHEMA + Type of the external application. SCHEMA must be one of: + + api-gateway + Service Discovery API endpoint when Service Discovery is enabled in + Gateway. + proxy-gateway + Proxy which routes traffic to actual applications, like Netscaler + Gateway. + + Update endpoint_matchers. + + At most one of these can be specified: + + --endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] + Set endpoint_matchers to new value. An array of conditions to match + the application's network endpoint. Each element in the array is an + EndpointMatcher object, which defines a specific combination of a + hostname pattern and one or more ports. The application is considered + matched if at least one of the EndpointMatcher conditions in this + array is met (the conditions are combined using OR logic). Each + EndpointMatcher must contain a hostname pattern, such as + "example.com", and one or more port numbers specified as a string, + such as "443". + + Hostname and port number examples: ".example.com", "443" + "example.com" and "22" "example.com" and "22,33". + + hostname + Hostname of the application. + + ports + The ports of the application. + + Shorthand Example: + + --endpoint-matchers=hostname=string,ports=[int] --endpoint-matchers=hostname=string,ports=[int] + + JSON Example: + + --endpoint-matchers='[{"hostname": "string", "ports": [int]}]' + + File Example: + + --endpoint-matchers=path_to_file.(yaml|json) + + --add-endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] + Add new value to endpoint_matchers list. An array of conditions to + match the application's network endpoint. Each element in the array + is an EndpointMatcher object, which defines a specific combination of + a hostname pattern and one or more ports. The application is + considered matched if at least one of the EndpointMatcher conditions + in this array is met (the conditions are combined using OR logic). + Each EndpointMatcher must contain a hostname pattern, such as + "example.com", and one or more port numbers specified as a string, + such as "443". + + Hostname and port number examples: ".example.com", "443" + "example.com" and "22" "example.com" and "22,33". + + hostname + Hostname of the application. + + ports + The ports of the application. + + Shorthand Example: + + --add-endpoint-matchers=hostname=string,ports=[int] --add-endpoint-matchers=hostname=string,ports=[int] + + JSON Example: + + --add-endpoint-matchers='[{"hostname": "string", "ports": [int]}]' + + File Example: + + --add-endpoint-matchers=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-endpoint-matchers + Clear endpoint_matchers value and set to empty list. + + --remove-endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] + Remove existing value from endpoint_matchers list. An array of + conditions to match the application's network endpoint. Each + element in the array is an EndpointMatcher object, which defines a + specific combination of a hostname pattern and one or more ports. + The application is considered matched if at least one of the + EndpointMatcher conditions in this array is met (the conditions are + combined using OR logic). Each EndpointMatcher must contain a + hostname pattern, such as "example.com", and one or more port + numbers specified as a string, such as "443". + + Hostname and port number examples: ".example.com", "443" + "example.com" and "22" "example.com" and "22,33". + + hostname + Hostname of the application. + + ports + The ports of the application. + + Shorthand Example: + + --remove-endpoint-matchers=hostname=string,ports=[int] --remove-endpoint-matchers=hostname=string,ports=[int] + + JSON Example: + + --remove-endpoint-matchers='[{"hostname": "string", "ports": [int]}]' + + File Example: + + --remove-endpoint-matchers=path_to_file.(yaml|json) + + Update upstreams. + + At most one of these can be specified: + + --upstreams=[egressPolicy=EGRESSPOLICY],[external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL] + Set upstreams to new value. Which upstream resources to forward + traffic to. + + egressPolicy + Routing policy information. + + regions + List of the regions where the application sends traffic. + + external + List of the external endpoints to forward traffic to. + + endpoints + List of the endpoints to forward traffic to. + + hostname + Hostname of the endpoint. + + port + Port of the endpoint. + + network + Network to forward traffic to. + + name + Network name is of the format: + projects/{project}/global/networks/{network}. + + proxyProtocol + Enables proxy protocol configuration for the upstream. + + allowedClientHeaders + List of the allowed client header names. + + clientIp + Client IP configuration. The client IP address is included if + true. + + contextualHeaders + Configuration for the contextual headers. + + deviceInfo + The device information configuration. + + outputType + The output type details for the delegated device. + + groupInfo + Group details. + + outputType + The output type of the delegated group information. + + outputType + Default output type for all enabled headers. + + userInfo + User details. + + outputType + The delegated user's information. + + gatewayIdentity + The security gateway identity configuration. + + metadataHeaders + Custom resource specific headers along with the values. The + names should conform to RFC 9110: >Field names can contain + alphanumeric characters, hyphens, and periods, can contain + only ASCII-printable characters and tabs, and must start with + a letter. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} --upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} + + JSON Example: + + --upstreams='[{"egressPolicy": {"regions": ["string"]}, "external": {"endpoints": [{"hostname": "string", "port": int}]}, "network": {"name": "string"}, "proxyProtocol": {"allowedClientHeaders": ["string"], "clientIp": boolean, "contextualHeaders": {"deviceInfo": {"outputType": "string"}, "groupInfo": {"outputType": "string"}, "outputType": "string", "userInfo": {"outputType": "string"}}, "gatewayIdentity": "string", "metadataHeaders": {"string": "string"}}}]' + + File Example: + + --upstreams=path_to_file.(yaml|json) + + --add-upstreams=[egressPolicy=EGRESSPOLICY],[external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL] + Add new value to upstreams list. Which upstream resources to forward + traffic to. + + egressPolicy + Routing policy information. + + regions + List of the regions where the application sends traffic. + + external + List of the external endpoints to forward traffic to. + + endpoints + List of the endpoints to forward traffic to. + + hostname + Hostname of the endpoint. + + port + Port of the endpoint. + + network + Network to forward traffic to. + + name + Network name is of the format: + projects/{project}/global/networks/{network}. + + proxyProtocol + Enables proxy protocol configuration for the upstream. + + allowedClientHeaders + List of the allowed client header names. + + clientIp + Client IP configuration. The client IP address is included if + true. + + contextualHeaders + Configuration for the contextual headers. + + deviceInfo + The device information configuration. + + outputType + The output type details for the delegated device. + + groupInfo + Group details. + + outputType + The output type of the delegated group information. + + outputType + Default output type for all enabled headers. + + userInfo + User details. + + outputType + The delegated user's information. + + gatewayIdentity + The security gateway identity configuration. + + metadataHeaders + Custom resource specific headers along with the values. The + names should conform to RFC 9110: >Field names can contain + alphanumeric characters, hyphens, and periods, can contain + only ASCII-printable characters and tabs, and must start with + a letter. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --add-upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} --add-upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} + + JSON Example: + + --add-upstreams='[{"egressPolicy": {"regions": ["string"]}, "external": {"endpoints": [{"hostname": "string", "port": int}]}, "network": {"name": "string"}, "proxyProtocol": {"allowedClientHeaders": ["string"], "clientIp": boolean, "contextualHeaders": {"deviceInfo": {"outputType": "string"}, "groupInfo": {"outputType": "string"}, "outputType": "string", "userInfo": {"outputType": "string"}}, "gatewayIdentity": "string", "metadataHeaders": {"string": "string"}}}]' + + File Example: + + --add-upstreams=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-upstreams + Clear upstreams value and set to empty list. + + --remove-upstreams=[egressPolicy=EGRESSPOLICY],[external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL] + Remove existing value from upstreams list. Which upstream resources + to forward traffic to. + + egressPolicy + Routing policy information. + + regions + List of the regions where the application sends traffic. + + external + List of the external endpoints to forward traffic to. + + endpoints + List of the endpoints to forward traffic to. + + hostname + Hostname of the endpoint. + + port + Port of the endpoint. + + network + Network to forward traffic to. + + name + Network name is of the format: + projects/{project}/global/networks/{network}. + + proxyProtocol + Enables proxy protocol configuration for the upstream. + + allowedClientHeaders + List of the allowed client header names. + + clientIp + Client IP configuration. The client IP address is included + if true. + + contextualHeaders + Configuration for the contextual headers. + + deviceInfo + The device information configuration. + + outputType + The output type details for the delegated device. + + groupInfo + Group details. + + outputType + The output type of the delegated group information. + + outputType + Default output type for all enabled headers. + + userInfo + User details. + + outputType + The delegated user's information. + + gatewayIdentity + The security gateway identity configuration. + + metadataHeaders + Custom resource specific headers along with the values. The + names should conform to RFC 9110: >Field names can contain + alphanumeric characters, hyphens, and periods, can contain + only ASCII-printable characters and tabs, and must start + with a letter. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --remove-upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} --remove-upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} + + JSON Example: + + --remove-upstreams='[{"egressPolicy": {"regions": ["string"]}, "external": {"endpoints": [{"hostname": "string", "port": int}]}, "network": {"name": "string"}, "proxyProtocol": {"allowedClientHeaders": ["string"], "clientIp": boolean, "contextualHeaders": {"deviceInfo": {"outputType": "string"}, "groupInfo": {"outputType": "string"}, "outputType": "string", "userInfo": {"outputType": "string"}}, "gatewayIdentity": "string", "metadataHeaders": {"string": "string"}}}]' + + File Example: + + --remove-upstreams=path_to_file.(yaml|json) + +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 beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways applications update + diff --git a/gcloud/beyondcorp/security-gateways/create b/gcloud/beyondcorp/security-gateways/create new file mode 100644 index 000000000..6d70ce631 --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/create @@ -0,0 +1,218 @@ +NAME + gcloud beyondcorp security-gateways create - create securityGateways + +SYNOPSIS + gcloud beyondcorp security-gateways create + (SECURITY_GATEWAY : --location=LOCATION) [--async] + [--display-name=DISPLAY_NAME] [--hubs=[HUBS,...]] + [--request-id=REQUEST_ID] + [--resource-override-path=RESOURCE_OVERRIDE_PATH] + [--proxy-protocol-config-allowed-client-headers=[PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS, + ...] --proxy-protocol-config-client-ip + --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY --proxy-protocol-config-metadata-headers=[PROXY_PROTOCOL_CONFIG_METADATA_HEADERS, + ...] --contextual-headers-output-type=CONTEXTUAL_HEADERS_OUTPUT_TYPE + --device-info-output-type=DEVICE_INFO_OUTPUT_TYPE + --group-info-output-type=GROUP_INFO_OUTPUT_TYPE + --user-info-output-type=USER_INFO_OUTPUT_TYPE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a securityGateway + +EXAMPLES + To create the securityGateway, run: + + $ gcloud beyondcorp security-gateways create + +POSITIONAL ARGUMENTS + SecurityGateway resource - Identifier. Name of the resource. 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 security_gateway 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. + + SECURITY_GATEWAY + ID of the securityGateway or fully qualified identifier for the + securityGateway. + + To set the security_gateway attribute: + ▸ provide the argument security_gateway 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 id of the securityGateway resource. We support only + global location. + + To set the location attribute: + ▸ provide the argument security_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the SecurityGateway. Cannot exceed + 64 characters. + + --hubs=[HUBS,...] + Map of Hubs that represents regional data path deployment with Google + Cloud Platform region as a key. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --hubs=string + + JSON Example: + + --hubs='{"string": {}}' + + File Example: + + --hubs=path_to_file.(yaml|json) + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + Settings related to the Service Discovery. + + If Service Discovery is done through API, defines its settings. + + This must be specified. + + API operation descriptor. + + This must be specified. + + --resource-override-path=RESOURCE_OVERRIDE_PATH + Contains the URI path fragment where HTTP request is sent. + + The configuration for the proxy. + + --proxy-protocol-config-allowed-client-headers=[PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS,...] + List of the allowed client header names. + + --proxy-protocol-config-client-ip + Client IP configuration. The client IP address is included if true. + + --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY + The security gateway identity configuration. + PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY must be (only one value is + supported): + + resource-name + Resource name for gateway identity, in the format: + projects/{project_id}/locations/{location_id}/securityGateways/{security_gateway_id} + + --proxy-protocol-config-metadata-headers=[PROXY_PROTOCOL_CONFIG_METADATA_HEADERS,...] + Custom resource specific headers along with the values. The names + should conform to RFC 9110: >Field names can contain alphanumeric + characters, hyphens, and periods, can contain only ASCII-printable + characters and tabs, and must start with a letter. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --proxy-protocol-config-metadata-headers=string=string + + JSON Example: + + --proxy-protocol-config-metadata-headers='{"string": "string"}' + + File Example: + + --proxy-protocol-config-metadata-headers=path_to_file.(yaml|json) + + Contextual headers configuration. + + --contextual-headers-output-type=CONTEXTUAL_HEADERS_OUTPUT_TYPE + Default output type for all enabled headers. + CONTEXTUAL_HEADERS_OUTPUT_TYPE must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + The delegated device information configuration. + + --device-info-output-type=DEVICE_INFO_OUTPUT_TYPE + The output type details for the delegated device. + DEVICE_INFO_OUTPUT_TYPE must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + The delegated group configuration details. + + --group-info-output-type=GROUP_INFO_OUTPUT_TYPE + The output type of the delegated group information. + GROUP_INFO_OUTPUT_TYPE must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + The configuration information for the delegated user. + + --user-info-output-type=USER_INFO_OUTPUT_TYPE + The delegated user's information. USER_INFO_OUTPUT_TYPE must be + one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + +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 beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways create + diff --git a/gcloud/beyondcorp/security-gateways/delete b/gcloud/beyondcorp/security-gateways/delete new file mode 100644 index 000000000..c2ac3406b --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/delete @@ -0,0 +1,91 @@ +NAME + gcloud beyondcorp security-gateways delete - delete securityGateways + +SYNOPSIS + gcloud beyondcorp security-gateways delete + (SECURITY_GATEWAY : --location=LOCATION) [--async] + [--request-id=REQUEST_ID] [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a securityGateway + +EXAMPLES + To delete the securityGateway, run: + + $ gcloud beyondcorp security-gateways delete + +POSITIONAL ARGUMENTS + SecurityGateway resource - BeyondCorp SecurityGateway name using the form: + projects/{project_id}/locations/{location_id}/securityGateways/{security_gateway_id} + 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 security_gateway 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. + + SECURITY_GATEWAY + ID of the securityGateway or fully qualified identifier for the + securityGateway. + + To set the security_gateway attribute: + ▸ provide the argument security_gateway 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 id of the securityGateway resource. We support only + global location. + + To set the location attribute: + ▸ provide the argument security_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --validate-only + If set, validates request by executing a dry-run which would not alter + the resource in any way. + +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 beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways delete + diff --git a/gcloud/beyondcorp/security-gateways/describe b/gcloud/beyondcorp/security-gateways/describe new file mode 100644 index 000000000..4e8031248 --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/describe @@ -0,0 +1,67 @@ +NAME + gcloud beyondcorp security-gateways describe - describe securityGateways + +SYNOPSIS + gcloud beyondcorp security-gateways describe + (SECURITY_GATEWAY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a securityGateway + +EXAMPLES + To describe the securityGateway, run: + + $ gcloud beyondcorp security-gateways describe + +POSITIONAL ARGUMENTS + SecurityGateway resource - The resource name of the PartnerTenant using + the form: + projects/{project_id}/locations/{location_id}/securityGateway/{security_gateway_id} + 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 security_gateway 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. + + SECURITY_GATEWAY + ID of the securityGateway or fully qualified identifier for the + securityGateway. + + To set the security_gateway attribute: + ▸ provide the argument security_gateway 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 id of the securityGateway resource. We support only + global location. + + To set the location attribute: + ▸ provide the argument security_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways describe + diff --git a/gcloud/beyondcorp/security-gateways/get-iam-policy b/gcloud/beyondcorp/security-gateways/get-iam-policy new file mode 100644 index 000000000..898f2bbb1 --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/get-iam-policy @@ -0,0 +1,96 @@ +NAME + gcloud beyondcorp security-gateways get-iam-policy - get the IAM policy for + a security gateway + +SYNOPSIS + gcloud beyondcorp security-gateways get-iam-policy + (SECURITY_GATEWAY : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Gets the IAM policy for the given security gateway. + +EXAMPLES + To get the IAM policy for a security gateway my-security-gateway run: + + $ gcloud beyondcorp security-gateways get-iam-policy \ + my-security-gateway --project=consumer-project-id \ + --location=global + +POSITIONAL ARGUMENTS + SecurityGateway resource - The security gateway for which to get the IAM + policy. The arguments in this group can be used to specify the attributes + of this resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument security_gateway 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. + + SECURITY_GATEWAY + ID of the securityGateway or fully qualified identifier for the + securityGateway. + + To set the security_gateway attribute: + ▸ provide the argument security_gateway 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 id of the securityGateway resource. We support only + global location. + + To set the location attribute: + ▸ provide the argument security_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways get-iam-policy + diff --git a/gcloud/beyondcorp/security-gateways/help b/gcloud/beyondcorp/security-gateways/help new file mode 100644 index 000000000..f7be751aa --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/help @@ -0,0 +1,49 @@ +NAME + gcloud beyondcorp security-gateways - manage Security Gateway resources + +SYNOPSIS + gcloud beyondcorp security-gateways GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Security Gateway resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + applications + Manage Application resources. + +COMMANDS + COMMAND is one of the following: + + create + Create securityGateways. + + delete + Delete securityGateways. + + describe + Describe securityGateways. + + get-iam-policy + Get the IAM policy for a security gateway. + + list + List securityGateways. + + set-iam-policy + Set the IAM policy for a security gateway. + + update + Update securityGateways. + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways + diff --git a/gcloud/beyondcorp/security-gateways/list b/gcloud/beyondcorp/security-gateways/list new file mode 100644 index 000000000..2832a1d95 --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/list @@ -0,0 +1,85 @@ +NAME + gcloud beyondcorp security-gateways list - list securityGateways + +SYNOPSIS + gcloud beyondcorp security-gateways list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List securityGateways + +EXAMPLES + To list all securityGateways, run: + + $ gcloud beyondcorp security-gateways list + +REQUIRED FLAGS + Location resource - The parent location to which the resources belong. + projects/{project_id}/locations/{location_id}/ 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --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. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways list + diff --git a/gcloud/beyondcorp/security-gateways/set-iam-policy b/gcloud/beyondcorp/security-gateways/set-iam-policy new file mode 100644 index 000000000..d2e9bcb93 --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/set-iam-policy @@ -0,0 +1,77 @@ +NAME + gcloud beyondcorp security-gateways set-iam-policy - set the IAM policy for + a security gateway + +SYNOPSIS + gcloud beyondcorp security-gateways set-iam-policy + (SECURITY_GATEWAY : --location=LOCATION) POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Sets the IAM policy for the given security gateway. + +EXAMPLES + The following command will read an IAM policy defined in a JSON file + 'policy.json' and set it for the security gateway with ID + my-security-gateway: + + $ gcloud beyondcorp security-gateways set-iam-policy \ + my-security-gateway policy.json --location=global + +POSITIONAL ARGUMENTS + SecurityGateway resource - The security gateway for which to set the IAM + policy. The arguments in this group can be used to specify the attributes + of this resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument security_gateway 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. + + SECURITY_GATEWAY + ID of the securityGateway or fully qualified identifier for the + securityGateway. + + To set the security_gateway attribute: + ▸ provide the argument security_gateway 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 id of the securityGateway resource. We support only + global location. + + To set the location attribute: + ▸ provide the argument security_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +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 beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways set-iam-policy + diff --git a/gcloud/beyondcorp/security-gateways/update b/gcloud/beyondcorp/security-gateways/update new file mode 100644 index 000000000..e86ccfe8d --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/update @@ -0,0 +1,359 @@ +NAME + gcloud beyondcorp security-gateways update - update securityGateways + +SYNOPSIS + gcloud beyondcorp security-gateways update + (SECURITY_GATEWAY : --location=LOCATION) [--async] + [--display-name=DISPLAY_NAME] [--request-id=REQUEST_ID] + [--clear-proxy-protocol-config --[no-]proxy-protocol-config-client-ip + --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY --contextual-headers-output-type=CONTEXTUAL_HEADERS_OUTPUT_TYPE --device-info-output-type=DEVICE_INFO_OUTPUT_TYPE --group-info-output-type=GROUP_INFO_OUTPUT_TYPE --user-info-output-type=USER_INFO_OUTPUT_TYPE --proxy-protocol-config-allowed-client-headers=[PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS, + ...] + | --add-proxy-protocol-config-allowed-client-headers=[ADD_PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS, + ...] --clear-proxy-protocol-config-allowed-client-headers + | --remove-proxy-protocol-config-allowed-client-headers=[REMOVE_PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS, + ...] + --proxy-protocol-config-metadata-headers=[PROXY_PROTOCOL_CONFIG_METADATA_HEADERS, + ...] + | --update-proxy-protocol-config-metadata-headers=[UPDATE_PROXY_PROTOCOL_CONFIG_METADATA_HEADERS, + ...] --clear-proxy-protocol-config-metadata-headers + | --remove-proxy-protocol-config-metadata-headers=REMOVE_PROXY_PROTOCOL_CONFIG_METADATA_HEADERS] + [--clear-service-discovery + --resource-override-path=RESOURCE_OVERRIDE_PATH] + [--hubs=[HUBS,...] | --update-hubs=[UPDATE_HUBS,...] --clear-hubs + | --remove-hubs=REMOVE_HUBS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a securityGateway + +EXAMPLES + To update the securityGateway, run: + + $ gcloud beyondcorp security-gateways update + +POSITIONAL ARGUMENTS + SecurityGateway resource - Identifier. Name of the resource. 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 security_gateway 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. + + SECURITY_GATEWAY + ID of the securityGateway or fully qualified identifier for the + securityGateway. + + To set the security_gateway attribute: + ▸ provide the argument security_gateway 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 id of the securityGateway resource. We support only + global location. + + To set the location attribute: + ▸ provide the argument security_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the SecurityGateway. Cannot exceed + 64 characters. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request timed out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + The configuration for the proxy. + + --clear-proxy-protocol-config + Set + googleCloudBeyondcorpSecuritygatewaysV1SecurityGateway.proxyProtocolConfig + back to default value. + + --[no-]proxy-protocol-config-client-ip + Client IP configuration. The client IP address is included if true. + Use --proxy-protocol-config-client-ip to enable and + --no-proxy-protocol-config-client-ip to disable. + + --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY + The security gateway identity configuration. + PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY must be (only one value is + supported): + + resource-name + Resource name for gateway identity, in the format: + projects/{project_id}/locations/{location_id}/securityGateways/{security_gateway_id} + + Contextual headers configuration. + + --contextual-headers-output-type=CONTEXTUAL_HEADERS_OUTPUT_TYPE + Default output type for all enabled headers. + CONTEXTUAL_HEADERS_OUTPUT_TYPE must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + The delegated device information configuration. + + --device-info-output-type=DEVICE_INFO_OUTPUT_TYPE + The output type details for the delegated device. + DEVICE_INFO_OUTPUT_TYPE must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + The delegated group configuration details. + + --group-info-output-type=GROUP_INFO_OUTPUT_TYPE + The output type of the delegated group information. + GROUP_INFO_OUTPUT_TYPE must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + The configuration information for the delegated user. + + --user-info-output-type=USER_INFO_OUTPUT_TYPE + The delegated user's information. USER_INFO_OUTPUT_TYPE must be + one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + Update proxy_protocol_config_allowed_client_headers. + + At most one of these can be specified: + + --proxy-protocol-config-allowed-client-headers=[PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS,...] + Set proxy_protocol_config_allowed_client_headers to new value. + + --add-proxy-protocol-config-allowed-client-headers=[ADD_PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS,...] + Add new value to proxy_protocol_config_allowed_client_headers list. + + At most one of these can be specified: + + --clear-proxy-protocol-config-allowed-client-headers + Clear proxy_protocol_config_allowed_client_headers value and set + to empty list. + + --remove-proxy-protocol-config-allowed-client-headers=[REMOVE_PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS,...] + Remove existing value from + proxy_protocol_config_allowed_client_headers list. + + Update proxy_protocol_config_metadata_headers. + + At most one of these can be specified: + + --proxy-protocol-config-metadata-headers=[PROXY_PROTOCOL_CONFIG_METADATA_HEADERS,...] + Set proxy_protocol_config_metadata_headers to new value. Custom + resource specific headers along with the values. The names should + conform to RFC 9110: >Field names can contain alphanumeric + characters, hyphens, and periods, can contain only ASCII-printable + characters and tabs, and must start with a letter. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --proxy-protocol-config-metadata-headers=string=string + + JSON Example: + + --proxy-protocol-config-metadata-headers='{"string": "string"}' + + File Example: + + --proxy-protocol-config-metadata-headers=path_to_file.(yaml|json) + + --update-proxy-protocol-config-metadata-headers=[UPDATE_PROXY_PROTOCOL_CONFIG_METADATA_HEADERS,...] + Update proxy_protocol_config_metadata_headers value or add key + value pair. Custom resource specific headers along with the values. + The names should conform to RFC 9110: >Field names can contain + alphanumeric characters, hyphens, and periods, can contain only + ASCII-printable characters and tabs, and must start with a letter. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --update-proxy-protocol-config-metadata-headers=string=string + + JSON Example: + + --update-proxy-protocol-config-metadata-headers='{"string": "string"}' + + File Example: + + --update-proxy-protocol-config-metadata-headers=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-proxy-protocol-config-metadata-headers + Clear proxy_protocol_config_metadata_headers value and set to + empty map. + + --remove-proxy-protocol-config-metadata-headers=REMOVE_PROXY_PROTOCOL_CONFIG_METADATA_HEADERS + Remove existing value from map + proxy_protocol_config_metadata_headers. Sets + remove_proxy_protocol_config_metadata_headers value. + + Shorthand Example: + + --remove-proxy-protocol-config-metadata-headers=string,string + + JSON Example: + + --remove-proxy-protocol-config-metadata-headers=["string"] + + File Example: + + --remove-proxy-protocol-config-metadata-headers=path_to_file.(yaml|json) + + Settings related to the Service Discovery. + + --clear-service-discovery + Set + googleCloudBeyondcorpSecuritygatewaysV1SecurityGateway.serviceDiscovery + back to default value. + + If Service Discovery is done through API, defines its settings. + + API operation descriptor. + + --resource-override-path=RESOURCE_OVERRIDE_PATH + Contains the URI path fragment where HTTP request is sent. + + Update hubs. + + At most one of these can be specified: + + --hubs=[HUBS,...] + Set hubs to new value. Map of Hubs that represents regional data path + deployment with Google Cloud Platform region as a key. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --hubs=string + + JSON Example: + + --hubs='{"string": {}}' + + File Example: + + --hubs=path_to_file.(yaml|json) + + --update-hubs=[UPDATE_HUBS,...] + Update hubs value or add key value pair. Map of Hubs that represents + regional data path deployment with Google Cloud Platform region as a + key. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --update-hubs=string + + JSON Example: + + --update-hubs='{"string": {}}' + + File Example: + + --update-hubs=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-hubs + Clear hubs value and set to empty map. + + --remove-hubs=REMOVE_HUBS + Remove existing value from map hubs. Sets remove_hubs value. + + Shorthand Example: + + --remove-hubs=string,string + + JSON Example: + + --remove-hubs=["string"] + + File Example: + + --remove-hubs=path_to_file.(yaml|json) + +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 beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways update + diff --git a/gcloud/composer/environments/create b/gcloud/composer/environments/create index 0096ff1a1..230abc01f 100644 --- a/gcloud/composer/environments/create +++ b/gcloud/composer/environments/create @@ -171,8 +171,8 @@ FLAGS --environment-size=ENVIRONMENT_SIZE Size of the environment. Unspecified means that the default option will - be chosen. ENVIRONMENT_SIZE must be one of: large, medium, small, - unspecified. + be chosen. ENVIRONMENT_SIZE must be one of: extra-large, large, medium, + small, unspecified. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/composer/environments/update b/gcloud/composer/environments/update index 4f93972db..c44115482 100644 --- a/gcloud/composer/environments/update +++ b/gcloud/composer/environments/update @@ -138,8 +138,8 @@ REQUIRED FLAGS --environment-size=ENVIRONMENT_SIZE Size of the environment. Unspecified means that the default option - will be chosen. ENVIRONMENT_SIZE must be one of: large, medium, - small, unspecified. + will be chosen. ENVIRONMENT_SIZE must be one of: extra-large, large, + medium, small, unspecified. Group of arguments for performing in-place environment upgrades. diff --git a/gcloud/compute/interconnects/attachments/dedicated/create b/gcloud/compute/interconnects/attachments/dedicated/create index 3f5120feb..e62aa0ff3 100644 --- a/gcloud/compute/interconnects/attachments/dedicated/create +++ b/gcloud/compute/interconnects/attachments/dedicated/create @@ -5,6 +5,10 @@ NAME SYNOPSIS gcloud compute interconnects attachments dedicated create NAME --interconnect=INTERCONNECT --router=ROUTER [--bandwidth=BANDWIDTH] + [--candidate-cloud-router-ip-address=CANDIDATE_CLOUD_ROUTER_IP_ADDRESS] + [--candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS] + [--candidate-customer-router-ip-address=CANDIDATE_CUSTOMER_ROUTER_IP_ADDRESS] + [--candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS] [--candidate-ipv6-subnets=[IPV6_SUBNET,...]] [--candidate-subnets=[SUBNET,...]] [--cloud-router-ipv6-interface-id=INTERFACE_ID] @@ -62,6 +66,26 @@ OPTIONAL FLAGS 100g 100 Gbit/s + --candidate-cloud-router-ip-address=CANDIDATE_CLOUD_ROUTER_IP_ADDRESS + Single IPv4 address + prefix length to be configured on the cloud + router interface for this interconnect attachment. Example: + 203.0.113.1/29 + + --candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS + Single IPv6 address + prefix length to be configured on the cloud + router interface for this interconnect attachment. Example: + 2001:db8::1/125 + + --candidate-customer-router-ip-address=CANDIDATE_CUSTOMER_ROUTER_IP_ADDRESS + Single IPv4 address + prefix length to be configured on the customer + router interface for this interconnect attachment. Example: + 203.0.113.2/29 + + --candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS + Single IPv6 address + prefix length to be configured on the customer + router interface for this interconnect attachment. Example: + 2001:db8::2/125 + --candidate-ipv6-subnets=[IPV6_SUBNET,...] The candididate-ipv6-subnets field is not available. diff --git a/gcloud/compute/interconnects/attachments/dedicated/update b/gcloud/compute/interconnects/attachments/dedicated/update index fb85fc506..1e155e0d7 100644 --- a/gcloud/compute/interconnects/attachments/dedicated/update +++ b/gcloud/compute/interconnects/attachments/dedicated/update @@ -4,7 +4,10 @@ NAME SYNOPSIS gcloud compute interconnects attachments dedicated update NAME - [--bandwidth=BANDWIDTH] [--candidate-ipv6-subnets=[IPV6_SUBNET,...]] + [--bandwidth=BANDWIDTH] + [--candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS] + [--candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS] + [--candidate-ipv6-subnets=[IPV6_SUBNET,...]] [--cloud-router-ipv6-interface-id=INTERFACE_ID] [--customer-router-ipv6-interface-id=PEER_INTERFACE_ID] [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU] @@ -51,6 +54,16 @@ FLAGS 100g 100 Gbit/s + --candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS + Single IPv6 address + prefix length to be configured on the cloud + router interface for this interconnect attachment. Example: + 2001:db8::1/125 + + --candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS + Single IPv6 address + prefix length to be configured on the customer + router interface for this interconnect attachment. Example: + 2001:db8::2/125 + --candidate-ipv6-subnets=[IPV6_SUBNET,...] The candididate-ipv6-subnets field is not available. diff --git a/gcloud/compute/interconnects/attachments/partner/create b/gcloud/compute/interconnects/attachments/partner/create index ff833236f..1138dfc34 100644 --- a/gcloud/compute/interconnects/attachments/partner/create +++ b/gcloud/compute/interconnects/attachments/partner/create @@ -5,6 +5,10 @@ NAME SYNOPSIS gcloud compute interconnects attachments partner create NAME --edge-availability-domain=AVAILABILITY_DOMAIN --router=ROUTER + [--candidate-cloud-router-ip-address=CANDIDATE_CLOUD_ROUTER_IP_ADDRESS] + [--candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS] + [--candidate-customer-router-ip-address=CANDIDATE_CUSTOMER_ROUTER_IP_ADDRESS] + [--candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS] [--description=DESCRIPTION] [--enable-admin] [--encryption=ENCRYPTION] [--ipsec-internal-addresses=[ADDRESSES]] [--mtu=MTU] [--region=REGION] [--resource-manager-tags=[KEY=VALUE,...]] [--stack-type=STACK_TYPE] @@ -46,6 +50,26 @@ REQUIRED FLAGS Google Cloud Router to use for dynamic routing. OPTIONAL FLAGS + --candidate-cloud-router-ip-address=CANDIDATE_CLOUD_ROUTER_IP_ADDRESS + Single IPv4 address + prefix length to be configured on the cloud + router interface for this interconnect attachment. Example: + 203.0.113.1/29 + + --candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS + Single IPv6 address + prefix length to be configured on the cloud + router interface for this interconnect attachment. Example: + 2001:db8::1/125 + + --candidate-customer-router-ip-address=CANDIDATE_CUSTOMER_ROUTER_IP_ADDRESS + Single IPv4 address + prefix length to be configured on the customer + router interface for this interconnect attachment. Example: + 203.0.113.2/29 + + --candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS + Single IPv6 address + prefix length to be configured on the customer + router interface for this interconnect attachment. Example: + 2001:db8::2/125 + --description=DESCRIPTION Human-readable plain-text description of attachment. diff --git a/gcloud/compute/interconnects/attachments/partner/update b/gcloud/compute/interconnects/attachments/partner/update index 039e6928a..c4b6656e1 100644 --- a/gcloud/compute/interconnects/attachments/partner/update +++ b/gcloud/compute/interconnects/attachments/partner/update @@ -4,6 +4,8 @@ NAME SYNOPSIS gcloud compute interconnects attachments partner update NAME + [--candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS] + [--candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS] [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU] [--region=REGION] [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...] @@ -18,6 +20,16 @@ POSITIONAL ARGUMENTS Name of the interconnect attachment to patch. FLAGS + --candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS + Single IPv6 address + prefix length to be configured on the cloud + router interface for this interconnect attachment. Example: + 2001:db8::1/125 + + --candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS + Single IPv6 address + prefix length to be configured on the customer + router interface for this interconnect attachment. Example: + 2001:db8::2/125 + --description=DESCRIPTION Human-readable plain-text description of attachment. diff --git a/gcloud/container/ai/profiles/benchmarks/list b/gcloud/container/ai/profiles/benchmarks/list index 256fd0745..1b57fc973 100644 --- a/gcloud/container/ai/profiles/benchmarks/list +++ b/gcloud/container/ai/profiles/benchmarks/list @@ -7,9 +7,10 @@ SYNOPSIS --model-server=MODEL_SERVER [--format=FORMAT] [--instance-type=INSTANCE_TYPE] [--model-server-version=MODEL_SERVER_VERSION] - [--pricing-model=PRICING_MODEL] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + [--pricing-model=PRICING_MODEL] [--serving-stack=SERVING_STACK] + [--serving-stack-version=SERVING_STACK_VERSION] [--use-case=USE_CASE] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command lists all benchmarking data for a given model and model @@ -43,6 +44,21 @@ FLAGS The pricing model to use to calculate token cost. Currently, this supports on-demand, spot, 3-years-cud, 1-year-cud + --serving-stack=SERVING_STACK + The serving stack to filter benchmarking data by. If not provided, + benchmarking data for all serving stacks that support the given model + and model server will be returned. + + --serving-stack-version=SERVING_STACK_VERSION + The serving stack version to filter benchmarking data by. If not + provided, benchmarking data for all versions that support the given + model and model server will be returned. + + --use-case=USE_CASE + If specified, results will only show profiles that match the provided + use case. Options are: Advanced Customer Support, Code Completion, Text + Summarization, Chatbot (ShareGPT), Code Generation, Deep Research. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/container/ai/profiles/help b/gcloud/container/ai/profiles/help index 8e5e33490..bbcc69000 100644 --- a/gcloud/container/ai/profiles/help +++ b/gcloud/container/ai/profiles/help @@ -42,6 +42,15 @@ GROUPS models Manage supported models for GKE Inference Quickstart. + serving-stack-versions + List supported serving stack versions for GKE Inference Quickstart. + + serving-stacks + List supported serving stacks for GKE Inference Quickstart. + + use-case + List supported use cases for GKE Inference Quickstart. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/container/ai/profiles/list b/gcloud/container/ai/profiles/list index ddd182e43..0f33f73e9 100644 --- a/gcloud/container/ai/profiles/list +++ b/gcloud/container/ai/profiles/list @@ -5,13 +5,18 @@ SYNOPSIS gcloud container ai profiles list [--format=FORMAT] [--model=MODEL] [--model-server=MODEL_SERVER] [--model-server-version=MODEL_SERVER_VERSION] - [--pricing-model=PRICING_MODEL] + [--pricing-model=PRICING_MODEL] [--serving-stack=SERVING_STACK] + [--serving-stack-version=SERVING_STACK_VERSION] [--target-cost-per-million-input-tokens=TARGET_COST_PER_MILLION_INPUT_TOKENS] [--target-cost-per-million-output-tokens=TARGET_COST_PER_MILLION_OUTPUT_TOKENS] + [--target-input-length=TARGET_INPUT_LENGTH] + [--target-itl-milliseconds=TARGET_ITL_MILLISECONDS] [--target-ntpot-milliseconds=TARGET_NTPOT_MILLISECONDS] + [--target-output-length=TARGET_OUTPUT_LENGTH] [--target-ttft-milliseconds=TARGET_TTFT_MILLISECONDS] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--use-case=USE_CASE] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command lists all supported accelerators with their performance @@ -46,6 +51,16 @@ FLAGS The pricing model to use to calculate token cost. Currently, this supports on-demand, spot, 3-years-cud, 1-year-cud + --serving-stack=SERVING_STACK + The serving stack to filter profiles by. If not provided, profiles for + all serving stacks that support the given model and model server will + be returned. + + --serving-stack-version=SERVING_STACK_VERSION + The serving stack version to filter profiles by. If not provided, + profiles for all versions that support the given model and model server + will be returned. + --target-cost-per-million-input-tokens=TARGET_COST_PER_MILLION_INPUT_TOKENS The target cost per million input tokens to filter profiles by, unit is 1 USD up to 5 decimal places. @@ -54,6 +69,15 @@ FLAGS The target cost per million output tokens to filter profiles by, unit is 1 USD up to 5 decimal places. + --target-input-length=TARGET_INPUT_LENGTH + If specified, results will only show profiles that have an input length + within 20% of the specified one. Only works alongside output length. + + --target-itl-milliseconds=TARGET_ITL_MILLISECONDS + If specified, results will only show profiles with instance types that + can meet the latency target and will show their throughput performances + at the target inter-token latency (ITL). + --target-ntpot-milliseconds=TARGET_NTPOT_MILLISECONDS The target normalized time per output token (NTPOT) in milliseconds. NTPOT is measured as the request_latency / output_tokens. If this field @@ -62,6 +86,11 @@ FLAGS the target latency. Otherwise, the command will return all accelerators and display their highest throughput performance. + --target-output-length=TARGET_OUTPUT_LENGTH + If specified, results will only show profiles that have an output + length within 20% of the specified one. Only works alongside input + length. + --target-ttft-milliseconds=TARGET_TTFT_MILLISECONDS The target time to first token (TTFT) in milliseconds. TTFT is measured as the request_latency / output_tokens. If this field is set, the @@ -70,6 +99,11 @@ FLAGS latency. Otherwise, the command will return all profiles and display their highest throughput performance. + --use-case=USE_CASE + If specified, results will only show profiles that match the provided + use case. Options are: Advanced Customer Support, Code Completion, Text + Summarization, Chatbot (ShareGPT), Text Generation, Deep Research + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/container/ai/profiles/manifests/create b/gcloud/container/ai/profiles/manifests/create index d8f88d289..a2a807b8e 100644 --- a/gcloud/container/ai/profiles/manifests/create +++ b/gcloud/container/ai/profiles/manifests/create @@ -9,9 +9,12 @@ SYNOPSIS --model-server=MODEL_SERVER [--model-bucket-uri=MODEL_BUCKET_URI] [--model-server-version=MODEL_SERVER_VERSION] [--namespace=NAMESPACE] [--output=OUTPUT; default="all"] [--output-path=OUTPUT_PATH] + [--serving-stack=SERVING_STACK] + [--serving-stack-version=SERVING_STACK_VERSION] + [--target-itl-milliseconds=TARGET_ITL_MILLISECONDS] [--target-ntpot-milliseconds=TARGET_NTPOT_MILLISECONDS] [--target-ttft-milliseconds=TARGET_TTFT_MILLISECONDS] - [GCLOUD_WIDE_FLAG ...] + [--use-case=USE_CASE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION To get supported model, model servers, and model server versions, run @@ -52,6 +55,24 @@ OPTIONAL FLAGS The path to save the output to. If not specified, output to the terminal. + --serving-stack=SERVING_STACK + The serving stack to filter manifests by. If not provided, manifests + for all serving stacks that support the given model and model server + will be considered. + + --serving-stack-version=SERVING_STACK_VERSION + The serving stack version to filter manifests by. If not provided, + manifests for all versions that support the given model and model + server will be considered. + + --target-itl-milliseconds=TARGET_ITL_MILLISECONDS + The target inter-token latency (ITL) in milliseconds. If this is set, + the manifest will include Horizontal Pod Autoscaler (HPA) resources + which automatically adjust the model server replica count in response + to changes in model server load to keep p50 ITL below the specified + threshold. If the provided target-itl-milliseconds is too low to + achieve, the HPA manifest will not be generated. + --target-ntpot-milliseconds=TARGET_NTPOT_MILLISECONDS The maximum normalized time per output token (NTPOT) in milliseconds. NTPOT is measured as the request_latency / output_tokens. If this is @@ -66,6 +87,12 @@ OPTIONAL FLAGS latency target and will show their throughput performances at the target ttft target to achieve, the HPA manifest will not be generated. + --use-case=USE_CASE + The manifest will be optimized for this use case. Options are: Advanced + Customer Support, Code Completion, Text Summarization, Chatbot + (ShareGPT), Code Generation, Deep Research. Will default to Chatbot if + not specified. + 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/ai/profiles/serving-stack-versions/help b/gcloud/container/ai/profiles/serving-stack-versions/help new file mode 100644 index 000000000..c28bb9796 --- /dev/null +++ b/gcloud/container/ai/profiles/serving-stack-versions/help @@ -0,0 +1,22 @@ +NAME + gcloud container ai profiles serving-stack-versions - list supported + serving stack versions for GKE Inference Quickstart + +SYNOPSIS + gcloud container ai profiles serving-stack-versions COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List supported serving stack versions for GKE Inference Quickstart. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + List supported serving stack versions that were used to generate the + inference profiles. diff --git a/gcloud/container/ai/profiles/serving-stack-versions/list b/gcloud/container/ai/profiles/serving-stack-versions/list new file mode 100644 index 000000000..17d9e97a9 --- /dev/null +++ b/gcloud/container/ai/profiles/serving-stack-versions/list @@ -0,0 +1,66 @@ +NAME + gcloud container ai profiles serving-stack-versions list - list supported + serving stack versions that were used to generate the inference + profiles + +SYNOPSIS + gcloud container ai profiles serving-stack-versions list + --serving-stack=SERVING_STACK [--model=MODEL] + [--model-server=MODEL_SERVER] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List supported serving stack versions that were used to generate the + inference profiles. + +REQUIRED FLAGS + --serving-stack=SERVING_STACK + The serving stack to filter serving stack versions by. + +FLAGS + --model=MODEL + The model to filter serving stack versions by. + + --model-server=MODEL_SERVER + The model server to filter serving stack versions by. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/container/ai/profiles/serving-stacks/help b/gcloud/container/ai/profiles/serving-stacks/help new file mode 100644 index 000000000..9f7fe8e22 --- /dev/null +++ b/gcloud/container/ai/profiles/serving-stacks/help @@ -0,0 +1,21 @@ +NAME + gcloud container ai profiles serving-stacks - list supported serving stacks + for GKE Inference Quickstart + +SYNOPSIS + gcloud container ai profiles serving-stacks COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List supported serving stacks for GKE Inference Quickstart. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + List supported serving stacks that were used to generate the inference + profiles. diff --git a/gcloud/container/ai/profiles/serving-stacks/list b/gcloud/container/ai/profiles/serving-stacks/list new file mode 100644 index 000000000..3e27eb66a --- /dev/null +++ b/gcloud/container/ai/profiles/serving-stacks/list @@ -0,0 +1,60 @@ +NAME + gcloud container ai profiles serving-stacks list - list supported serving + stacks that were used to generate the inference profiles + +SYNOPSIS + gcloud container ai profiles serving-stacks list [--model=MODEL] + [--model-server=MODEL_SERVER] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List supported serving stacks that were used to generate the inference + profiles. + +FLAGS + --model=MODEL + The model to filter serving stacks by. + + --model-server=MODEL_SERVER + The model server to filter serving stacks by. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/container/ai/profiles/use-case/help b/gcloud/container/ai/profiles/use-case/help new file mode 100644 index 000000000..097dc942b --- /dev/null +++ b/gcloud/container/ai/profiles/use-case/help @@ -0,0 +1,21 @@ +NAME + gcloud container ai profiles use-case - list supported use cases for GKE + Inference Quickstart + +SYNOPSIS + gcloud container ai profiles use-case COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List supported use cases for GKE Inference Quickstart. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + List supported use cases that were used to generate the inference + profiles. diff --git a/gcloud/container/ai/profiles/use-case/list b/gcloud/container/ai/profiles/use-case/list new file mode 100644 index 000000000..8040fcd4c --- /dev/null +++ b/gcloud/container/ai/profiles/use-case/list @@ -0,0 +1,51 @@ +NAME + gcloud container ai profiles use-case list - list supported use cases that + were used to generate the inference profiles + +SYNOPSIS + gcloud container ai profiles use-case list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List supported use cases that were used to generate the inference profiles. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/datastream/streams/create b/gcloud/datastream/streams/create index 853ea913b..fea465c40 100644 --- a/gcloud/datastream/streams/create +++ b/gcloud/datastream/streams/create @@ -20,8 +20,8 @@ SYNOPSIS | --postgresql-source-config=POSTGRESQL_SOURCE_CONFIG | --salesforce-source-config=SALESFORCE_SOURCE_CONFIG | --sqlserver-source-config=SQLSERVER_SOURCE_CONFIG)) - [--labels=[KEY=VALUE,...]] [--force | --validate-only] - [GCLOUD_WIDE_FLAG ...] + [--labels=[KEY=VALUE,...]] [--rule-sets=RULE_SETS] + [--force | --validate-only] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a Datastream stream. If successful, the response body contains a @@ -560,6 +560,52 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --rule-sets=RULE_SETS + Path to a JSON file containing a list of rule sets to be applied to the + stream. + + The JSON file is formatted as follows, with camelCase field naming: + + [ + { + "objectFilter": { + "sourceObjectIdentifier": { + "oracleIdentifier": { + "schema": "schema1", + "table": "table1" + } + } + }, + "customizationRules": [ + { + "bigqueryClustering": { + "columns": ["COL_A"] + } + } + ] + }, + { + "objectFilter": { + "sourceObjectIdentifier": { + "oracleIdentifier": { + "schema": "schema2", + "table": "table2" + } + } + }, + "customizationRules": [ + { + "bigqueryPartitioning": { + "timeUnitPartition": { + "column": "TIME_COL", + "partitioningTimeGranularity": "PARTITIONING_TIME_GRANULARITY_DAY" + } + } + } + ] + } + ] + At most one of these can be specified: --force diff --git a/gcloud/datastream/streams/update b/gcloud/datastream/streams/update index 6d4584644..595141d1b 100644 --- a/gcloud/datastream/streams/update +++ b/gcloud/datastream/streams/update @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud datastream streams update (STREAM : --location=LOCATION) - [--display-name=DISPLAY_NAME] [--state=STATE] + [--display-name=DISPLAY_NAME] [--rule-sets=RULE_SETS] [--state=STATE] [--update-labels=[KEY=VALUE,...]] [--update-mask=UPDATE_MASK] [--backfill-none | --backfill-all --mongodb-excluded-objects=MONGODB_EXCLUDED_OBJECTS @@ -82,6 +82,52 @@ FLAGS --display-name=DISPLAY_NAME Friendly name for the stream. + --rule-sets=RULE_SETS + Path to a JSON file containing a list of rule sets to be applied to the + stream. + + The JSON file is formatted as follows, with camelCase field naming: + + [ + { + "objectFilter": { + "sourceObjectIdentifier": { + "oracleIdentifier": { + "schema": "schema1", + "table": "table1" + } + } + }, + "customizationRules": [ + { + "bigqueryClustering": { + "columns": ["COL_A"] + } + } + ] + }, + { + "objectFilter": { + "sourceObjectIdentifier": { + "oracleIdentifier": { + "schema": "schema2", + "table": "table2" + } + } + }, + "customizationRules": [ + { + "bigqueryPartitioning": { + "timeUnitPartition": { + "column": "TIME_COL", + "partitioningTimeGranularity": "PARTITIONING_TIME_GRANULARITY_DAY" + } + } + } + ] + } + ] + --state=STATE Stream state, can be set to: "RUNNING" or "PAUSED". diff --git a/gcloud/design-center/spaces/application-templates/create b/gcloud/design-center/spaces/application-templates/create index cf98193eb..6677e0890 100644 --- a/gcloud/design-center/spaces/application-templates/create +++ b/gcloud/design-center/spaces/application-templates/create @@ -7,7 +7,11 @@ SYNOPSIS (APPLICATION_TEMPLATE : --location=LOCATION --space=SPACE) [--application-parameters=[key=KEY],[value=VALUE]] [--composition-type=COMPOSITION_TYPE] [--description=DESCRIPTION] - [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + [--display-name=DISPLAY_NAME] + [--root-input-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE]] + [--root-output-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create an application template. @@ -144,6 +148,48 @@ FLAGS --display-name=DISPLAY_NAME Application template display name. + --root-input-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Root level input variables of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --root-input-variables=componentUri=string,variable=string --root-input-variables=componentUri=string,variable=string + + JSON Example: + + --root-input-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --root-input-variables=path_to_file.(yaml|json) + + --root-output-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Root level output variables of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --root-output-variables=componentUri=string,variable=string --root-output-variables=componentUri=string,variable=string + + JSON Example: + + --root-output-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --root-output-variables=path_to_file.(yaml|json) + 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/design-center/spaces/application-templates/update b/gcloud/design-center/spaces/application-templates/update index 4f6dadedc..11c8f44f4 100644 --- a/gcloud/design-center/spaces/application-templates/update +++ b/gcloud/design-center/spaces/application-templates/update @@ -11,7 +11,17 @@ SYNOPSIS | --add-application-parameters=[key=KEY],[value=VALUE] --clear-application-parameters | --remove-application-parameters=[key=KEY],[value=VALUE]] - [GCLOUD_WIDE_FLAG ...] + [--root-input-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + | --add-root-input-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE] --clear-root-input-variables + | --remove-root-input-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE]] + [--root-output-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE] + | --add-root-output-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE] --clear-root-output-variables + | --remove-root-output-variables=[componentUri=COMPONENTURI], + [variable=VARIABLE]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update an application template. @@ -197,6 +207,156 @@ FLAGS --remove-application-parameters=path_to_file.(yaml|json) + Update root_input_variables. + + At most one of these can be specified: + + --root-input-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Set root_input_variables to new value. Root level input variables of + the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --root-input-variables=componentUri=string,variable=string --root-input-variables=componentUri=string,variable=string + + JSON Example: + + --root-input-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --root-input-variables=path_to_file.(yaml|json) + + --add-root-input-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Add new value to root_input_variables list. Root level input + variables of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --add-root-input-variables=componentUri=string,variable=string --add-root-input-variables=componentUri=string,variable=string + + JSON Example: + + --add-root-input-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --add-root-input-variables=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-root-input-variables + Clear root_input_variables value and set to empty list. + + --remove-root-input-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Remove existing value from root_input_variables list. Root level + input variables of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --remove-root-input-variables=componentUri=string,variable=string --remove-root-input-variables=componentUri=string,variable=string + + JSON Example: + + --remove-root-input-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --remove-root-input-variables=path_to_file.(yaml|json) + + Update root_output_variables. + + At most one of these can be specified: + + --root-output-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Set root_output_variables to new value. Root level output variables + of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --root-output-variables=componentUri=string,variable=string --root-output-variables=componentUri=string,variable=string + + JSON Example: + + --root-output-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --root-output-variables=path_to_file.(yaml|json) + + --add-root-output-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Add new value to root_output_variables list. Root level output + variables of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --add-root-output-variables=componentUri=string,variable=string --add-root-output-variables=componentUri=string,variable=string + + JSON Example: + + --add-root-output-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --add-root-output-variables=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-root-output-variables + Clear root_output_variables value and set to empty list. + + --remove-root-output-variables=[componentUri=COMPONENTURI],[variable=VARIABLE] + Remove existing value from root_output_variables list. Root level + output variables of the application template. + + componentUri + Component to which this variable belongs. + + variable + Name of the variable. + + Shorthand Example: + + --remove-root-output-variables=componentUri=string,variable=string --remove-root-output-variables=componentUri=string,variable=string + + JSON Example: + + --remove-root-output-variables='[{"componentUri": "string", "variable": "string"}]' + + File Example: + + --remove-root-output-variables=path_to_file.(yaml|json) + 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/developer-connect/connections/create b/gcloud/developer-connect/connections/create index 500c51afa..2dba6831b 100644 --- a/gcloud/developer-connect/connections/create +++ b/gcloud/developer-connect/connections/create @@ -117,10 +117,27 @@ FLAGS --location=LOCATION For resources [connection, + bitbucket-cloud-config-authorizer-credential-user-token-secret-version, + bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version, + bitbucket-cloud-config-webhook-secret-version, + bitbucket-data-center-config-authorizer-credential-user-token-secret-version, + bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version, bitbucket-data-center-config-service-directory, + bitbucket-data-center-config-webhook-secret-version, crypto-key-config-reference, + github-config-authorizer-credential-oauth-token-secret-version, + github-enterprise-config-private-key-secret-version, github-enterprise-config-service-directory, + github-enterprise-config-webhook-secret-version, + gitlab-config-authorizer-credential-user-token-secret-version, + gitlab-config-read-authorizer-credential-user-token-secret-version, + gitlab-config-webhook-secret-version, + gitlab-enterprise-config-authorizer-credential-user-token-secret-version, + gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version, gitlab-enterprise-config-service-directory, + gitlab-enterprise-config-webhook-secret-version, + http-config-basic-authentication-password-secret-version, + http-config-bearer-token-authentication-secret-version, http-config-service-directory], provides fallback value for resource location attribute. When the resource's full URI path is not provided, location will fallback to this flag value. @@ -186,7 +203,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -197,11 +216,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-cloud-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-cloud-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -209,7 +237,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-cloud-config-authorizer-credential-user-token-secret-version on the command line. @@ -221,7 +249,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -232,11 +262,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -244,14 +283,16 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version on the command line. SecretVersion resource - SecretManager resource containing the webhook secret used to verify webhook events, formatted as - projects/*/secrets/*/versions/*. This is used to validate and create + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This is used to validate and create webhooks. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -262,11 +303,20 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --bitbucket-cloud-config-webhook-secret-version on the command line + with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --bitbucket-cloud-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -274,7 +324,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --bitbucket-cloud-config-webhook-secret-version on the command line. @@ -292,7 +342,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -303,11 +355,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-data-center-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-data-center-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -315,7 +376,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-data-center-config-authorizer-credential-user-token-secret-version on the command line. @@ -330,7 +391,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -341,11 +404,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -353,15 +425,17 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version on the command line. SecretVersion resource - SecretManager resource containing the webhook secret used to verify webhook events, formatted as - projects/*/secrets/*/versions/*. This is used to validate webhooks. - This represents a Cloud resource. (NOTE) Some attributes are not given + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This is used to validate webhooks. 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: @@ -371,11 +445,20 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --bitbucket-data-center-config-webhook-secret-version on the + command line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --bitbucket-data-center-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -383,7 +466,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --bitbucket-data-center-config-webhook-secret-version on the command line. @@ -440,6 +523,8 @@ FLAGS The Developer Connect GitHub Application. firebase The Firebase GitHub Application. + gemini-code-assist + The Gemini Code Assist Application. This flag argument must be specified if any of the other arguments in this group are specified. @@ -452,7 +537,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the OAuth token that authorizes the connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -463,11 +550,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --github-config-authorizer-credential-oauth-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --github-config-authorizer-credential-oauth-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -475,7 +571,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --github-config-authorizer-credential-oauth-token-secret-version on the command line. @@ -495,9 +591,11 @@ FLAGS ID of the installation of the GitHub App. SecretVersion resource - SecretManager resource containing the private - key of the GitHub App, formatted as projects/*/secrets/*/versions/*. - This represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + key of the GitHub App, formatted as projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) + Some attributes are not given arguments in this group but can be set + in other ways. To set the project attribute: ▫ provide the argument @@ -506,17 +604,26 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --github-enterprise-config-private-key-secret-version on the + command line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --github-enterprise-config-private-key-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --github-enterprise-config-private-key-secret-version on the command line. @@ -563,8 +670,9 @@ FLAGS SSL certificate to use for requests to GitHub Enterprise. SecretVersion resource - SecretManager resource containing the webhook - secret of the GitHub App, formatted as - projects/*/secrets/*/versions/*. This represents a Cloud resource. + secret of the GitHub App, formatted as projects/*/secrets/*/versions/* + or projects/*/locations/*/secrets/*/versions/* (if regional secrets + are supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -575,17 +683,26 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --github-enterprise-config-webhook-secret-version on the command + line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --github-enterprise-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --github-enterprise-config-webhook-secret-version on the command line. @@ -599,7 +716,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -610,11 +729,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -622,7 +750,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-config-authorizer-credential-user-token-secret-version on the command line. @@ -634,7 +762,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -645,11 +775,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -657,15 +796,17 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-config-read-authorizer-credential-user-token-secret-version on the command line. SecretVersion resource - SecretManager resource containing the webhook secret of a GitLab project, formatted as - projects/*/secrets/*/versions/*. This is used to validate webhooks. - This represents a Cloud resource. (NOTE) Some attributes are not given + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This is used to validate webhooks. 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: @@ -674,10 +815,18 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument --gitlab-config-webhook-secret-version on + the command line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --gitlab-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -685,7 +834,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --gitlab-config-webhook-secret-version on the command line. @@ -698,7 +847,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -709,11 +860,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-enterprise-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-enterprise-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -721,7 +881,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-enterprise-config-authorizer-credential-user-token-secret-version on the command line. @@ -736,7 +896,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -747,11 +909,20 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -759,15 +930,17 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version on the command line. SecretVersion resource - SecretManager resource containing the webhook secret of a GitLab project, formatted as - projects/*/secrets/*/versions/*. This is used to validate webhooks. - This represents a Cloud resource. (NOTE) Some attributes are not given + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This is used to validate webhooks. 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: @@ -777,11 +950,20 @@ FLAGS ▫ provide the argument --project on the command line; ▫ set the property core/project. + To set the location attribute: + ▫ provide the argument + --gitlab-enterprise-config-webhook-secret-version on the command + line with a fully specified name; + ▫ provide the argument --location on the command line. + To set the secret attribute: ▫ provide the argument --gitlab-enterprise-config-webhook-secret-version on the command line with a fully specified name; - ▫ provide the argument --secret on the command line. + ▫ provide the argument --secret on the command line. This resource + can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. This must be specified. @@ -789,7 +971,7 @@ FLAGS ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ◇ provide the argument --gitlab-enterprise-config-webhook-secret-version on the command line. diff --git a/gcloud/developer-connect/connections/update b/gcloud/developer-connect/connections/update index fd601cf29..026e7c714 100644 --- a/gcloud/developer-connect/connections/update +++ b/gcloud/developer-connect/connections/update @@ -82,10 +82,23 @@ FLAGS --location=LOCATION For resources [connection, + bitbucket-cloud-config-authorizer-credential-user-token-secret-version, + bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version, + bitbucket-data-center-config-authorizer-credential-user-token-secret-version, + bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version, bitbucket-data-center-config-service-directory, crypto-key-config-reference, + github-config-authorizer-credential-oauth-token-secret-version, + github-enterprise-config-private-key-secret-version, github-enterprise-config-service-directory, + github-enterprise-config-webhook-secret-version, + gitlab-config-authorizer-credential-user-token-secret-version, + gitlab-config-read-authorizer-credential-user-token-secret-version, + gitlab-enterprise-config-authorizer-credential-user-token-secret-version, + gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version, gitlab-enterprise-config-service-directory, + http-config-basic-authentication-password-secret-version, + http-config-bearer-token-authentication-secret-version, http-config-service-directory], provides fallback value for resource location attribute. When the resource's full URI path is not provided, location will fallback to this flag value. @@ -215,7 +228,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -226,17 +241,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-cloud-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-cloud-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-cloud-config-authorizer-credential-user-token-secret-version on the command line. @@ -246,7 +270,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -257,17 +283,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version on the command line. @@ -286,7 +321,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -297,17 +334,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-data-center-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-data-center-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-data-center-config-authorizer-credential-user-token-secret-version on the command line. @@ -320,7 +366,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -331,17 +379,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version on the command line. @@ -402,7 +459,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the OAuth token that authorizes the connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -413,17 +472,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --github-config-authorizer-credential-oauth-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --github-config-authorizer-credential-oauth-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --github-config-authorizer-credential-oauth-token-secret-version on the command line. @@ -493,9 +561,11 @@ FLAGS github_enterprise_config_private_key_secret_version to new value. SecretManager resource containing the private key of the GitHub App, - formatted as projects/*/secrets/*/versions/*. This represents a - Cloud resource. (NOTE) Some attributes are not given arguments in - this group but can be set in other ways. + formatted as projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can + be set in other ways. To set the project attribute: ◇ provide the argument @@ -504,17 +574,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --github-enterprise-config-private-key-secret-version on the + command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --github-enterprise-config-private-key-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --github-enterprise-config-private-key-secret-version on the command line. @@ -531,9 +610,11 @@ FLAGS github_enterprise_config_webhook_secret_version to new value. SecretManager resource containing the webhook secret of the GitHub - App, formatted as projects/*/secrets/*/versions/*. This represents a - Cloud resource. (NOTE) Some attributes are not given arguments in - this group but can be set in other ways. + App, formatted as projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can + be set in other ways. To set the project attribute: ◇ provide the argument @@ -542,17 +623,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --github-enterprise-config-webhook-secret-version on the command + line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --github-enterprise-config-webhook-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --github-enterprise-config-webhook-secret-version on the command line. @@ -567,7 +657,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -578,17 +670,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-config-authorizer-credential-user-token-secret-version on the command line. @@ -598,7 +699,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -609,17 +712,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-config-read-authorizer-credential-user-token-secret-version on the command line. @@ -634,7 +746,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -645,17 +759,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-enterprise-config-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-enterprise-config-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-enterprise-config-authorizer-credential-user-token-secret-version on the command line. @@ -668,7 +791,9 @@ FLAGS SecretVersion resource - A SecretManager resource containing the user token that authorizes the Developer Connect connection. Format: - projects/*/secrets/*/versions/*. This represents a Cloud resource. + projects/*/secrets/*/versions/* or + projects/*/locations/*/secrets/*/versions/* (if regional secrets are + supported in that location). This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -679,17 +804,26 @@ FLAGS ◇ provide the argument --project on the command line; ◇ set the property core/project. + To set the location attribute: + ◇ provide the argument + --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version + on the command line with a fully specified name; + ◇ provide the argument --location on the command line. + To set the secret attribute: ◇ provide the argument --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version on the command line with a fully specified name; - ◇ provide the argument --secret on the command line. + ◇ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION ID of the secretVersion or fully qualified identifier for the secretVersion. - To set the secret-version attribute: + To set the secret_version attribute: ▹ provide the argument --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version on the command line. diff --git a/gcloud/gemini/code-repository-indexes/repository-groups/create b/gcloud/gemini/code-repository-indexes/repository-groups/create index 11914e4e9..2df2d3310 100644 --- a/gcloud/gemini/code-repository-indexes/repository-groups/create +++ b/gcloud/gemini/code-repository-indexes/repository-groups/create @@ -6,8 +6,11 @@ SYNOPSIS gcloud gemini code-repository-indexes repository-groups create (REPOSITORY_GROUP : --code-repository-index=CODE_REPOSITORY_INDEX --location=LOCATION) - --repositories=[branchPattern=BRANCHPATTERN],[resource=RESOURCE] - [--async] [--labels=[LABELS,...]] [--request-id=REQUEST_ID] + [--async] [--labels=[LABELS,...]] + [--repositories=[branchPattern=BRANCHPATTERN],[resource=RESOURCE]] + [--request-id=REQUEST_ID] + [--resources=[authConfig=AUTHCONFIG], + [connection=CONNECTION],[sourceConfig=SOURCECONFIG],[type=TYPE]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -103,31 +106,7 @@ POSITIONAL ARGUMENTS fully specified name; ▸ provide the argument --location on the command line. -REQUIRED FLAGS - --repositories=[branchPattern=BRANCHPATTERN],[resource=RESOURCE] - Required, List of repositories to group. - - branchPattern - The Git branch pattern used for indexing in RE2 syntax. See - https://github.com/google/re2/wiki/syntax for syntax. - - resource - The DeveloperConnect repository full resource name, relative - resource name or resource URL to be indexed. - - Shorthand Example: - - --repositories=branchPattern=string,resource=string --repositories=branchPattern=string,resource=string - - JSON Example: - - --repositories='[{"branchPattern": "string", "resource": "string"}]' - - File Example: - - --repositories=path_to_file.(yaml|json) - -OPTIONAL FLAGS +FLAGS --async Return immediately, without waiting for the operation in progress to complete. @@ -155,6 +134,29 @@ OPTIONAL FLAGS --labels=path_to_file.(yaml|json) + --repositories=[branchPattern=BRANCHPATTERN],[resource=RESOURCE] + List of repositories to group. + + branchPattern + The Git branch pattern used for indexing in RE2 syntax. See + https://github.com/google/re2/wiki/syntax for syntax. + + resource + The DeveloperConnect repository full resource name, relative + resource name or resource URL to be indexed. + + Shorthand Example: + + --repositories=branchPattern=string,resource=string --repositories=branchPattern=string,resource=string + + JSON Example: + + --repositories='[{"branchPattern": "string", "resource": "string"}]' + + File Example: + + --repositories=path_to_file.(yaml|json) + --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to @@ -164,6 +166,56 @@ OPTIONAL FLAGS The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). + --resources=[authConfig=AUTHCONFIG],[connection=CONNECTION],[sourceConfig=SOURCECONFIG],[type=TYPE] + List of third party connection resources. + + authConfig + The authentication configuration for the resource. + + apiToken + API Token based authentication. + + tokenSecretResource + The secret key for the API token. Example: + projects//secrets//versions/. + + username + The username for the API token. + + connection + The DeveloperConnect connection full resource name, relative + resource name or resource URL to be indexed. + + sourceConfig + The source configuration for the resource. + + confluenceConfig + Confluence source configuration. + + pageId + The optional page ID of the Confluence page. + + spaceKey + The space key of the Confluence space. + + uri + The host address of the Confluence instance. + + type + The type of the 3p resource. + + Shorthand Example: + + --resources=authConfig={apiToken={tokenSecretResource=string,username=string}},connection=string,sourceConfig={confluenceConfig={pageId=string,spaceKey=string,uri=string}},type=string --resources=authConfig={apiToken={tokenSecretResource=string,username=string}},connection=string,sourceConfig={confluenceConfig={pageId=string,spaceKey=string,uri=string}},type=string + + JSON Example: + + --resources='[{"authConfig": {"apiToken": {"tokenSecretResource": "string", "username": "string"}}, "connection": "string", "sourceConfig": {"confluenceConfig": {"pageId": "string", "spaceKey": "string", "uri": "string"}}, "type": "string"}]' + + File Example: + + --resources=path_to_file.(yaml|json) + 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/gemini/code-repository-indexes/repository-groups/update b/gcloud/gemini/code-repository-indexes/repository-groups/update index a716bed55..766a47424 100644 --- a/gcloud/gemini/code-repository-indexes/repository-groups/update +++ b/gcloud/gemini/code-repository-indexes/repository-groups/update @@ -14,7 +14,15 @@ SYNOPSIS | --add-repositories=[branchPattern=BRANCHPATTERN], [resource=RESOURCE] --clear-repositories | --remove-repositories=[branchPattern=BRANCHPATTERN], - [resource=RESOURCE]] [GCLOUD_WIDE_FLAG ...] + [resource=RESOURCE]] + [--resources=[authConfig=AUTHCONFIG], + [connection=CONNECTION],[sourceConfig=SOURCECONFIG],[type=TYPE] + | --add-resources=[authConfig=AUTHCONFIG], + [connection=CONNECTION],[sourceConfig=SOURCECONFIG],[type=TYPE] + --clear-resources + | --remove-resources=[authConfig=AUTHCONFIG], + [connection=CONNECTION],[sourceConfig=SOURCECONFIG],[type=TYPE]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update the configuration of a repository group. @@ -235,6 +243,167 @@ FLAGS --remove-repositories=path_to_file.(yaml|json) + Update resources. + + At most one of these can be specified: + + --resources=[authConfig=AUTHCONFIG],[connection=CONNECTION],[sourceConfig=SOURCECONFIG],[type=TYPE] + Set resources to new value. List of third party connection resources. + + authConfig + The authentication configuration for the resource. + + apiToken + API Token based authentication. + + tokenSecretResource + The secret key for the API token. Example: + projects//secrets//versions/. + + username + The username for the API token. + + connection + The DeveloperConnect connection full resource name, relative + resource name or resource URL to be indexed. + + sourceConfig + The source configuration for the resource. + + confluenceConfig + Confluence source configuration. + + pageId + The optional page ID of the Confluence page. + + spaceKey + The space key of the Confluence space. + + uri + The host address of the Confluence instance. + + type + The type of the 3p resource. + + Shorthand Example: + + --resources=authConfig={apiToken={tokenSecretResource=string,username=string}},connection=string,sourceConfig={confluenceConfig={pageId=string,spaceKey=string,uri=string}},type=string --resources=authConfig={apiToken={tokenSecretResource=string,username=string}},connection=string,sourceConfig={confluenceConfig={pageId=string,spaceKey=string,uri=string}},type=string + + JSON Example: + + --resources='[{"authConfig": {"apiToken": {"tokenSecretResource": "string", "username": "string"}}, "connection": "string", "sourceConfig": {"confluenceConfig": {"pageId": "string", "spaceKey": "string", "uri": "string"}}, "type": "string"}]' + + File Example: + + --resources=path_to_file.(yaml|json) + + --add-resources=[authConfig=AUTHCONFIG],[connection=CONNECTION],[sourceConfig=SOURCECONFIG],[type=TYPE] + Add new value to resources list. List of third party connection + resources. + + authConfig + The authentication configuration for the resource. + + apiToken + API Token based authentication. + + tokenSecretResource + The secret key for the API token. Example: + projects//secrets//versions/. + + username + The username for the API token. + + connection + The DeveloperConnect connection full resource name, relative + resource name or resource URL to be indexed. + + sourceConfig + The source configuration for the resource. + + confluenceConfig + Confluence source configuration. + + pageId + The optional page ID of the Confluence page. + + spaceKey + The space key of the Confluence space. + + uri + The host address of the Confluence instance. + + type + The type of the 3p resource. + + Shorthand Example: + + --add-resources=authConfig={apiToken={tokenSecretResource=string,username=string}},connection=string,sourceConfig={confluenceConfig={pageId=string,spaceKey=string,uri=string}},type=string --add-resources=authConfig={apiToken={tokenSecretResource=string,username=string}},connection=string,sourceConfig={confluenceConfig={pageId=string,spaceKey=string,uri=string}},type=string + + JSON Example: + + --add-resources='[{"authConfig": {"apiToken": {"tokenSecretResource": "string", "username": "string"}}, "connection": "string", "sourceConfig": {"confluenceConfig": {"pageId": "string", "spaceKey": "string", "uri": "string"}}, "type": "string"}]' + + File Example: + + --add-resources=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-resources + Clear resources value and set to empty list. + + --remove-resources=[authConfig=AUTHCONFIG],[connection=CONNECTION],[sourceConfig=SOURCECONFIG],[type=TYPE] + Remove existing value from resources list. List of third party + connection resources. + + authConfig + The authentication configuration for the resource. + + apiToken + API Token based authentication. + + tokenSecretResource + The secret key for the API token. Example: + projects//secrets//versions/. + + username + The username for the API token. + + connection + The DeveloperConnect connection full resource name, relative + resource name or resource URL to be indexed. + + sourceConfig + The source configuration for the resource. + + confluenceConfig + Confluence source configuration. + + pageId + The optional page ID of the Confluence page. + + spaceKey + The space key of the Confluence space. + + uri + The host address of the Confluence instance. + + type + The type of the 3p resource. + + Shorthand Example: + + --remove-resources=authConfig={apiToken={tokenSecretResource=string,username=string}},connection=string,sourceConfig={confluenceConfig={pageId=string,spaceKey=string,uri=string}},type=string --remove-resources=authConfig={apiToken={tokenSecretResource=string,username=string}},connection=string,sourceConfig={confluenceConfig={pageId=string,spaceKey=string,uri=string}},type=string + + JSON Example: + + --remove-resources='[{"authConfig": {"apiToken": {"tokenSecretResource": "string", "username": "string"}}, "connection": "string", "sourceConfig": {"confluenceConfig": {"pageId": "string", "spaceKey": "string", "uri": "string"}}, "type": "string"}]' + + File Example: + + --remove-resources=path_to_file.(yaml|json) + 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/gemini/code-tools-settings/setting-bindings/create b/gcloud/gemini/code-tools-settings/setting-bindings/create index d34aca918..a63ca0691 100644 --- a/gcloud/gemini/code-tools-settings/setting-bindings/create +++ b/gcloud/gemini/code-tools-settings/setting-bindings/create @@ -99,6 +99,8 @@ OPTIONAL FLAGS Gemini Code Assist. gemini-in-bigquery Gemini in BigQuery. + gemini-in-looker + Gemini in Looker. --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request diff --git a/gcloud/gemini/code-tools-settings/setting-bindings/update b/gcloud/gemini/code-tools-settings/setting-bindings/update index 83ad58ab8..b74f6a75f 100644 --- a/gcloud/gemini/code-tools-settings/setting-bindings/update +++ b/gcloud/gemini/code-tools-settings/setting-bindings/update @@ -75,6 +75,8 @@ FLAGS Gemini Code Assist. gemini-in-bigquery Gemini in BigQuery. + gemini-in-looker + Gemini in Looker. --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request diff --git a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/create b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/create index db9c94f50..538a795a2 100644 --- a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/create +++ b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/create @@ -16,7 +16,8 @@ DESCRIPTION EXAMPLES To create the settingBinding, run: - $ gcloud gemini data-sharing-with-google-settings setting-bindings \ create + $ gcloud gemini data-sharing-with-google-settings setting-bindings \ + create POSITIONAL ARGUMENTS SettingBinding resource - Identifier. Name of the resource. @@ -101,6 +102,8 @@ OPTIONAL FLAGS Gemini Code Assist. gemini-in-bigquery Gemini in BigQuery. + gemini-in-looker + Gemini in Looker. --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request diff --git a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/delete b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/delete index 695927b16..f99c1cea1 100644 --- a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/delete +++ b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/delete @@ -15,7 +15,8 @@ DESCRIPTION EXAMPLES To delete the settingBinding, run: - $ gcloud gemini data-sharing-with-google-settings setting-bindings \ delete + $ gcloud gemini data-sharing-with-google-settings setting-bindings \ + delete POSITIONAL ARGUMENTS SettingBinding resource - Name of the resource. The arguments in this diff --git a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/describe b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/describe index 22cfd40b6..e4f8ac00f 100644 --- a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/describe +++ b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/describe @@ -14,7 +14,8 @@ DESCRIPTION EXAMPLES To describe the settingBinding, run: - $ gcloud gemini data-sharing-with-google-settings setting-bindings \ describe + $ gcloud gemini data-sharing-with-google-settings setting-bindings \ + describe POSITIONAL ARGUMENTS SettingBinding resource - Name of the resource. The arguments in this diff --git a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/list b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/list index 1f9254f1a..10c53bbb4 100644 --- a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/list +++ b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/list @@ -15,7 +15,8 @@ DESCRIPTION EXAMPLES To list all settingBindings, run: - $ gcloud gemini data-sharing-with-google-settings setting-bindings \ list + $ gcloud gemini data-sharing-with-google-settings setting-bindings \ + list REQUIRED FLAGS DataSharingWithGoogleSetting resource - Parent value for diff --git a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/update b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/update index de2afda58..7a57ae250 100644 --- a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/update +++ b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/update @@ -18,7 +18,8 @@ DESCRIPTION EXAMPLES To update the settingBinding, run: - $ gcloud gemini data-sharing-with-google-settings setting-bindings \ update + $ gcloud gemini data-sharing-with-google-settings setting-bindings \ + update POSITIONAL ARGUMENTS SettingBinding resource - Identifier. Name of the resource. @@ -76,6 +77,8 @@ FLAGS Gemini Code Assist. gemini-in-bigquery Gemini in BigQuery. + gemini-in-looker + Gemini in Looker. --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/create b/gcloud/gemini/gemini-gcp-enablement-settings/create index 550575aa6..2f32cc69f 100644 --- a/gcloud/gemini/gemini-gcp-enablement-settings/create +++ b/gcloud/gemini/gemini-gcp-enablement-settings/create @@ -7,7 +7,7 @@ SYNOPSIS (GEMINI_GCP_ENABLEMENT_SETTING : --location=LOCATION) [--disable-web-grounding] [--enable-customer-data-sharing] [--labels=[LABELS,...]] [--request-id=REQUEST_ID] - [GCLOUD_WIDE_FLAG ...] + [--web-grounding-type=WEB_GROUNDING_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a geminiGcpEnablementSetting @@ -53,10 +53,11 @@ POSITIONAL ARGUMENTS FLAGS --disable-web-grounding - Whether web grounding should be disabled. + Whether web grounding should be disabled. DEPRECATED: Use + web_grounding_type instead. --enable-customer-data-sharing - Whether customer data sharing should be enabled. + Not implemented. --labels=[LABELS,...] Labels as key value pairs. @@ -96,6 +97,14 @@ FLAGS The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). + --web-grounding-type=WEB_GROUNDING_TYPE + Web grounding type. WEB_GROUNDING_TYPE must be one of: + + grounding-with-google-search + Grounding with Google Search. + web-grounding-for-enterprise + Grounding with Google Search for Enterprise. + 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/gemini/gemini-gcp-enablement-settings/setting-bindings/create b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/create index 83ed1504b..6c2d812d0 100644 --- a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/create +++ b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/create @@ -16,7 +16,8 @@ DESCRIPTION EXAMPLES To create the settingBinding, run: - $ gcloud gemini gemini-gcp-enablement-settings setting-bindings \ create + $ gcloud gemini gemini-gcp-enablement-settings setting-bindings \ + create POSITIONAL ARGUMENTS SettingBinding resource - Identifier. Name of the resource. @@ -101,6 +102,8 @@ OPTIONAL FLAGS Gemini Code Assist. gemini-in-bigquery Gemini in BigQuery. + gemini-in-looker + Gemini in Looker. --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/delete b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/delete index f39d68555..9111f29ca 100644 --- a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/delete +++ b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/delete @@ -15,7 +15,8 @@ DESCRIPTION EXAMPLES To delete the settingBinding, run: - $ gcloud gemini gemini-gcp-enablement-settings setting-bindings \ delete + $ gcloud gemini gemini-gcp-enablement-settings setting-bindings \ + delete POSITIONAL ARGUMENTS SettingBinding resource - Name of the resource. The arguments in this diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/describe b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/describe index 6e4339e20..573bb497a 100644 --- a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/describe +++ b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/describe @@ -14,7 +14,8 @@ DESCRIPTION EXAMPLES To describe the settingBinding, run: - $ gcloud gemini gemini-gcp-enablement-settings setting-bindings \ describe + $ gcloud gemini gemini-gcp-enablement-settings setting-bindings \ + describe POSITIONAL ARGUMENTS SettingBinding resource - Name of the resource. The arguments in this diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/update b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/update index f412d6e49..b097a7b13 100644 --- a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/update +++ b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/update @@ -18,7 +18,8 @@ DESCRIPTION EXAMPLES To update the settingBinding, run: - $ gcloud gemini gemini-gcp-enablement-settings setting-bindings \ update + $ gcloud gemini gemini-gcp-enablement-settings setting-bindings \ + update POSITIONAL ARGUMENTS SettingBinding resource - Identifier. Name of the resource. @@ -76,6 +77,8 @@ FLAGS Gemini Code Assist. gemini-in-bigquery Gemini in BigQuery. + gemini-in-looker + Gemini in Looker. --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/update b/gcloud/gemini/gemini-gcp-enablement-settings/update index cce388a00..9e8e2dce1 100644 --- a/gcloud/gemini/gemini-gcp-enablement-settings/update +++ b/gcloud/gemini/gemini-gcp-enablement-settings/update @@ -6,7 +6,7 @@ SYNOPSIS gcloud gemini gemini-gcp-enablement-settings update (GEMINI_GCP_ENABLEMENT_SETTING : --location=LOCATION) [--[no-]disable-web-grounding] [--[no-]enable-customer-data-sharing] - [--request-id=REQUEST_ID] + [--request-id=REQUEST_ID] [--web-grounding-type=WEB_GROUNDING_TYPE] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] @@ -55,12 +55,12 @@ POSITIONAL ARGUMENTS FLAGS --[no-]disable-web-grounding - Whether web grounding should be disabled. Use --disable-web-grounding - to enable and --no-disable-web-grounding to disable. + Whether web grounding should be disabled. DEPRECATED: Use + web_grounding_type instead. Use --disable-web-grounding to enable and + --no-disable-web-grounding to disable. --[no-]enable-customer-data-sharing - Whether customer data sharing should be enabled. Use - --enable-customer-data-sharing to enable and + Not implemented. Use --enable-customer-data-sharing to enable and --no-enable-customer-data-sharing to disable. --request-id=REQUEST_ID @@ -78,6 +78,14 @@ FLAGS The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). + --web-grounding-type=WEB_GROUNDING_TYPE + Web grounding type. WEB_GROUNDING_TYPE must be one of: + + grounding-with-google-search + Grounding with Google Search. + web-grounding-for-enterprise + Grounding with Google Search for Enterprise. + Update labels. At most one of these can be specified: diff --git a/gcloud/gemini/logging-settings/setting-bindings/create b/gcloud/gemini/logging-settings/setting-bindings/create index 86c015fef..87aeac71b 100644 --- a/gcloud/gemini/logging-settings/setting-bindings/create +++ b/gcloud/gemini/logging-settings/setting-bindings/create @@ -99,6 +99,8 @@ OPTIONAL FLAGS Gemini Code Assist. gemini-in-bigquery Gemini in BigQuery. + gemini-in-looker + Gemini in Looker. --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request diff --git a/gcloud/gemini/logging-settings/setting-bindings/update b/gcloud/gemini/logging-settings/setting-bindings/update index 53dfc35e4..29afa26cb 100644 --- a/gcloud/gemini/logging-settings/setting-bindings/update +++ b/gcloud/gemini/logging-settings/setting-bindings/update @@ -74,6 +74,8 @@ FLAGS Gemini Code Assist. gemini-in-bigquery Gemini in BigQuery. + gemini-in-looker + Gemini in Looker. --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request diff --git a/gcloud/gemini/release-channel-settings/setting-bindings/create b/gcloud/gemini/release-channel-settings/setting-bindings/create index 3244323d2..0443ec123 100644 --- a/gcloud/gemini/release-channel-settings/setting-bindings/create +++ b/gcloud/gemini/release-channel-settings/setting-bindings/create @@ -100,6 +100,8 @@ OPTIONAL FLAGS Gemini Code Assist. gemini-in-bigquery Gemini in BigQuery. + gemini-in-looker + Gemini in Looker. --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request diff --git a/gcloud/gemini/release-channel-settings/setting-bindings/update b/gcloud/gemini/release-channel-settings/setting-bindings/update index 901f18ae1..229a00252 100644 --- a/gcloud/gemini/release-channel-settings/setting-bindings/update +++ b/gcloud/gemini/release-channel-settings/setting-bindings/update @@ -75,6 +75,8 @@ FLAGS Gemini Code Assist. gemini-in-bigquery Gemini in BigQuery. + gemini-in-looker + Gemini in Looker. --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request diff --git a/gcloud/iam/policy-bindings/create b/gcloud/iam/policy-bindings/create index 9a4f39f1e..3a20fd6fd 100644 --- a/gcloud/iam/policy-bindings/create +++ b/gcloud/iam/policy-bindings/create @@ -31,8 +31,8 @@ POSITIONAL ARGUMENTS PolicyBinding resource - Identifier. The name of the policy binding, in the format {binding_parent/locations/{location}/policyBindings/{policy_binding_id}. - The binding parent is the closest Resource Manager resource (i.e., - Project, Folder or Organization) to the binding target. + The binding parent is the closest Resource Manager resource (project, + folder, or organization) to the binding target. Format: @@ -96,35 +96,43 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --policy=POLICY The resource name of the policy to be bound. The binding parent and - policy must belong to the same Organization (or Project). + policy must belong to the same organization. - Target is the full resource name of the resource to which the policy will - be bound. Immutable once set. + The full resource name of the resource to which the policy will be bound. + Immutable once set. This must be specified. Arguments for the target. --target-principal-set=TARGET_PRINCIPAL_SET - Full Resource Name used for principal access boundary policy - bindings Examples: + The full resource name that's used for principal access boundary + policy bindings. The principal set must be directly parented by the + policy binding's parent or same as the parent if the target is a + project, folder, or organization. - ▫ Organization: - //cloudresourcemanager.googleapis.com/organizations/ORGANIZATION_ID - ▫ Folder: //cloudresourcemanager.googleapis.com/folders/FOLDER_ID - ▫ Project: - ◇ //cloudresourcemanager.googleapis.com/projects/PROJECT_NUMBER - ◇ //cloudresourcemanager.googleapis.com/projects/PROJECT_ID - ▫ Workload Identity Pool: - //iam.googleapis.com/projects/PROJECT_NUMBER/locations/LOCATION/workloadIdentityPools/WORKLOAD_POOL_ID - ▫ Workforce Identity: - //iam.googleapis.com/locations/global/workforcePools/WORKFORCE_POOL_ID - ▫ Workspace Identity: - //iam.googleapis.com/locations/global/workspace/WORKSPACE_ID + Examples: + + ▫ For bindings parented by an organization: + ◇ Organization: + //cloudresourcemanager.googleapis.com/organizations/ORGANIZATION_ID + ◇ Workforce Identity: + //iam.googleapis.com/locations/global/workforcePools/WORKFORCE_POOL_ID + ◇ Workspace Identity: + //iam.googleapis.com/locations/global/workspace/WORKSPACE_ID + ▫ For bindings parented by a folder: + ◇ Folder: + //cloudresourcemanager.googleapis.com/folders/FOLDER_ID + ▫ For bindings parented by a project: + ◇ Project: + ▹ //cloudresourcemanager.googleapis.com/projects/PROJECT_NUMBER + ▹ //cloudresourcemanager.googleapis.com/projects/PROJECT_ID + ◇ Workload Identity Pool: + //iam.googleapis.com/projects/PROJECT_NUMBER/locations/LOCATION/workloadIdentityPools/WORKLOAD_POOL_ID OPTIONAL FLAGS --annotations=[ANNOTATIONS,...] - User defined annotations. See https://google.aip.dev/148#annotations + User-defined annotations. See https://google.aip.dev/148#annotations for more details such as format and size limitations. KEY diff --git a/gcloud/iam/policy-bindings/update b/gcloud/iam/policy-bindings/update index 5cb4b8c54..a9f028b18 100644 --- a/gcloud/iam/policy-bindings/update +++ b/gcloud/iam/policy-bindings/update @@ -9,7 +9,7 @@ SYNOPSIS [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations | --remove-annotations=REMOVE_ANNOTATIONS] - [--condition-description=CONDITION_DESCRIPTION + [--clear-condition --condition-description=CONDITION_DESCRIPTION --condition-expression=CONDITION_EXPRESSION --condition-location=CONDITION_LOCATION --condition-title=CONDITION_TITLE] [GCLOUD_WIDE_FLAG ...] @@ -27,8 +27,8 @@ POSITIONAL ARGUMENTS PolicyBinding resource - Identifier. The name of the policy binding, in the format {binding_parent/locations/{location}/policyBindings/{policy_binding_id}. - The binding parent is the closest Resource Manager resource (i.e., - Project, Folder or Organization) to the binding target. + The binding parent is the closest Resource Manager resource (project, + folder, or organization) to the binding target. Format: @@ -107,7 +107,7 @@ FLAGS At most one of these can be specified: --annotations=[ANNOTATIONS,...] - Set annotations to new value. User defined annotations. See + Set annotations to new value. User-defined annotations. See https://google.aip.dev/148#annotations for more details such as format and size limitations. @@ -130,7 +130,7 @@ FLAGS --annotations=path_to_file.(yaml|json) --update-annotations=[UPDATE_ANNOTATIONS,...] - Update annotations value or add key value pair. User defined + Update annotations value or add key value pair. User-defined annotations. See https://google.aip.dev/148#annotations for more details such as format and size limitations. @@ -205,6 +205,9 @@ FLAGS expression are determined by the service that evaluates it. See the service documentation for additional information. + --clear-condition + Set googleIamV3PolicyBinding.condition back to default value. + --condition-description=CONDITION_DESCRIPTION Description of the expression. This is a longer text which describes the expression, e.g. when hovered over it in a UI. diff --git a/gcloud/iam/principal-access-boundary-policies/create b/gcloud/iam/principal-access-boundary-policies/create index 4bce7523f..6f4928270 100644 --- a/gcloud/iam/principal-access-boundary-policies/create +++ b/gcloud/iam/principal-access-boundary-policies/create @@ -110,9 +110,10 @@ FLAGS rule. resources - A list of Cloud Resource Manager resources. The resource and all - the descendants are included. The number of resources in a policy - is limited to 500 across all rules. + A list of Resource Manager resources. If a resource is listed in + the rule, then the rule applies for that resource and its + descendants. The number of resources in a policy is limited to + 500 across all rules in the policy. The following resource types are supported: @@ -140,10 +141,10 @@ FLAGS this group are specified. --details-enforcement-version=DETAILS_ENFORCEMENT_VERSION - The version number that indicates which Google Cloud services are - included in the enforcement (e.g. "latest", "1", ...). If empty, the - PAB policy version will be set to the current latest version, and - this version won't get updated when new versions are released. + The version number (for example, 1 or latest) that indicates which + permissions are able to be blocked by the policy. If empty, the PAB + policy version will be set to the most recent version number at the + time of the policy's creation. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/iam/principal-access-boundary-policies/delete b/gcloud/iam/principal-access-boundary-policies/delete index c4eda2dd6..b80a296d6 100644 --- a/gcloud/iam/principal-access-boundary-policies/delete +++ b/gcloud/iam/principal-access-boundary-policies/delete @@ -65,8 +65,8 @@ FLAGS it must match the server's etag. --force - If set to true, the request will force the deletion of the Policy even - if the Policy references PolicyBindings. + If set to true, the request will force the deletion of the policy even + if the policy is referenced in policy bindings. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/iam/principal-access-boundary-policies/update b/gcloud/iam/principal-access-boundary-policies/update index 987a5041b..6f2c13c17 100644 --- a/gcloud/iam/principal-access-boundary-policies/update +++ b/gcloud/iam/principal-access-boundary-policies/update @@ -10,7 +10,8 @@ SYNOPSIS [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations | --remove-annotations=REMOVE_ANNOTATIONS] - [--details-enforcement-version=DETAILS_ENFORCEMENT_VERSION + [--clear-details + --details-enforcement-version=DETAILS_ENFORCEMENT_VERSION --details-rules=[description=DESCRIPTION], [effect=EFFECT],[resources=RESOURCES] | --add-details-rules=[description=DESCRIPTION], @@ -152,11 +153,15 @@ FLAGS Principal access boundary policy details + --clear-details + Set googleIamV3PrincipalAccessBoundaryPolicy.details back to default + value. + --details-enforcement-version=DETAILS_ENFORCEMENT_VERSION - The version number that indicates which Google Cloud services are - included in the enforcement (e.g. "latest", "1", ...). If empty, the - PAB policy version will be set to the current latest version, and - this version won't get updated when new versions are released. + The version number (for example, 1 or latest) that indicates which + permissions are able to be blocked by the policy. If empty, the PAB + policy version will be set to the most recent version number at the + time of the policy's creation. Update details_rules. @@ -175,9 +180,10 @@ FLAGS rule. resources - A list of Cloud Resource Manager resources. The resource and - all the descendants are included. The number of resources in a - policy is limited to 500 across all rules. + A list of Resource Manager resources. If a resource is listed + in the rule, then the rule applies for that resource and its + descendants. The number of resources in a policy is limited to + 500 across all rules in the policy. The following resource types are supported: @@ -215,9 +221,10 @@ FLAGS rule. resources - A list of Cloud Resource Manager resources. The resource and - all the descendants are included. The number of resources in a - policy is limited to 500 across all rules. + A list of Resource Manager resources. If a resource is listed + in the rule, then the rule applies for that resource and its + descendants. The number of resources in a policy is limited to + 500 across all rules in the policy. The following resource types are supported: @@ -260,9 +267,10 @@ FLAGS this rule. resources - A list of Cloud Resource Manager resources. The resource and - all the descendants are included. The number of resources in - a policy is limited to 500 across all rules. + A list of Resource Manager resources. If a resource is listed + in the rule, then the rule applies for that resource and its + descendants. The number of resources in a policy is limited + to 500 across all rules in the policy. The following resource types are supported: diff --git a/gcloud/looker/instances/update b/gcloud/looker/instances/update index 0dc8a1908..4fe18e149 100644 --- a/gcloud/looker/instances/update +++ b/gcloud/looker/instances/update @@ -10,6 +10,10 @@ SYNOPSIS [--add-developer-users=ADD_DEVELOPER_USERS --add-standard-users=ADD_STANDARD_USERS --add-viewer-users=ADD_VIEWER_USERS] + [--clear-periodic-export-config + | --periodic-export-gcs-uri=PERIODIC_EXPORT_GCS_URI + --periodic-export-kms-key=PERIODIC_EXPORT_KMS_KEY + --periodic-export-start-time=PERIODIC_EXPORT_START_TIME] [--clear-psc-allowed-vpcs | --psc-allowed-vpcs=[PSC_ALLOWED_VPCS,...] --clear-psc-service-attachments | --psc-service-attachment=[attachment=ATTACHMENT], @@ -124,6 +128,26 @@ FLAGS --add-viewer-users=ADD_VIEWER_USERS Number of additional Viewer Users to allocate to the Looker Instance. + At most one of these can be specified: + + --clear-periodic-export-config + Clears all periodic export configuration from the instance. + + Configuration for periodic export. All flags in this group must be + provided to enable or update the configuration. + + --periodic-export-gcs-uri=PERIODIC_EXPORT_GCS_URI + Cloud Storage bucket URI for periodic export. Format: + gs://{bucket_name} + + --periodic-export-kms-key=PERIODIC_EXPORT_KMS_KEY + Name of the CMEK key in KMS. Format: + projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{crypto_key} + + --periodic-export-start-time=PERIODIC_EXPORT_START_TIME + Time in UTC when the periodic export job starts. A valid time of + day must be specified in 24hr format (ex: 13:00, 17:30, 23:45). + Private Service Connect - Private Service Connect allows the Looker Instance to be reached via a private connection from inside a VPC network, and for the Looker Instance to connect to managed services via private diff --git a/gcloud/lustre/instances/create b/gcloud/lustre/instances/create index 2ce712b27..40e06f497 100644 --- a/gcloud/lustre/instances/create +++ b/gcloud/lustre/instances/create @@ -92,8 +92,8 @@ REQUIRED FLAGS ▸ provide the argument --network on the command line. --per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT - The throughput of the instance in MB/s/TiB. Valid values are 125, 250, - 500, 1000. See Performance tiers and maximum storage capacities + The throughput of the instance in MBps per TiB. Valid values are 125, + 250, 500, 1000. See Performance tiers and maximum storage capacities (https://cloud.google.com/managed-lustre/docs/create-instance#performance-tiers) for more information. diff --git a/gcloud/lustre/instances/update b/gcloud/lustre/instances/update index 7d50e4ff6..2de23f78d 100644 --- a/gcloud/lustre/instances/update +++ b/gcloud/lustre/instances/update @@ -85,8 +85,8 @@ FLAGS --no-gke-support-enabled to disable. --per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT - The throughput of the instance in MB/s/TiB. Valid values are 125, 250, - 500, 1000. See Performance tiers and maximum storage capacities + The throughput of the instance in MBps per TiB. Valid values are 125, + 250, 500, 1000. See Performance tiers and maximum storage capacities (https://cloud.google.com/managed-lustre/docs/create-instance#performance-tiers) for more information. diff --git a/gcloud/managed-kafka/clusters/describe b/gcloud/managed-kafka/clusters/describe index 57a7015ab..211c20ab1 100644 --- a/gcloud/managed-kafka/clusters/describe +++ b/gcloud/managed-kafka/clusters/describe @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud managed-kafka clusters describe (CLUSTER : --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] + [--full] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Describe a Managed Service for Apache Kafka cluster. @@ -50,6 +50,11 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --location on the command line. +FLAGS + --full + Show detailed information about individual brokers, such as broker id + and zone, as well as the Kafka version running on the cluster. + 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/managed-kafka/connect-clusters/create b/gcloud/managed-kafka/connect-clusters/create index a1c9cce0d..587e20042 100644 --- a/gcloud/managed-kafka/connect-clusters/create +++ b/gcloud/managed-kafka/connect-clusters/create @@ -82,10 +82,17 @@ REQUIRED FLAGS OPTIONAL FLAGS --additional-subnet=ADDITIONAL_SUBNET - Additional subnet to make available to the Kafka Connect cluster. - Structured like: + (DEPRECATED) Additional subnet to make available to the Kafka Connect + cluster. Structured like: projects/{project}/regions/{region}/subnetworks/{subnet_id}. + The --additional-subnet flag is deprecated and will be removed in a + future version. Managed Kafka Connect clusters can now reach any + endpoint accessible from the primary subnet without the need to define + additional subnets. Please see + https://cloud.google.com/managed-service-for-apache-kafka/docs/connect-cluster/create-connect-cluster#worker-subnet + for more information. + --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/managed-kafka/connect-clusters/update b/gcloud/managed-kafka/connect-clusters/update index b73aeaa26..5a2c5f68b 100644 --- a/gcloud/managed-kafka/connect-clusters/update +++ b/gcloud/managed-kafka/connect-clusters/update @@ -25,8 +25,6 @@ EXAMPLES --config-file=my-config-file.yaml --cpu=3 --memory=3GiB \ --primary-subnet=projects/my-project/regions/us-central1/\ subnetworks/default/1 \ - --additional-subnet=projects/my-project/regions/us-central1/\ - subnetworks/default/2 \ --dns-name=bootstrap.myconnectorCluster.us-central1.managedkafka\ .my-project.cloud.goog:9092 \ --secret=projects/my-project/secrets/my-secret/versions/1 \ @@ -143,10 +141,17 @@ REQUIRED FLAGS this group are specified. --additional-subnet=ADDITIONAL_SUBNET - Additional subnet to make available to the Kafka Connect cluster. - Structured like: + (DEPRECATED) Additional subnet to make available to the Kafka Connect + cluster. Structured like: projects/{project}/regions/{region}/subnetworks/{subnet_id}. + The --additional-subnet flag is deprecated and will be removed in a + future version. Managed Kafka Connect clusters can now reach any + endpoint accessible from the primary subnet without the need to + define additional subnets. Please see + https://cloud.google.com/managed-service-for-apache-kafka/docs/connect-cluster/create-connect-cluster#worker-subnet + for more information. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/managed-kafka/connectors/create b/gcloud/managed-kafka/connectors/create index 5bfc08eb2..db572df59 100644 --- a/gcloud/managed-kafka/connectors/create +++ b/gcloud/managed-kafka/connectors/create @@ -6,6 +6,7 @@ SYNOPSIS gcloud managed-kafka connectors create (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) (--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]) + [--task-retry-disabled] [--task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF] [GCLOUD_WIDE_FLAG ...] @@ -21,12 +22,12 @@ EXAMPLES --configs=connector.class="com.google.pubsub.kafka.source.CloudP\ ubSubSourceConnector",cps.subscription="my-subscription",... \ [--task-restart-min-backoff=60s] \ - [--task-restart-max-backoff=30m] OR + [--task-restart-max-backoff=30m] [--task-retry-disabled=true] OR $ gcloud managed-kafka connectors create myconnector \ --location=us-central1 --connect-cluster=mycluster \ --config-file=my-config-file.yaml \ [--task-restart-min-backoff=60s] \ - [--task-restart-max-backoff=30m] + [--task-restart-max-backoff=30m] [--task-retry-disabled=true] POSITIONAL ARGUMENTS Connector resource - Identifies the connector for which the command runs. @@ -92,6 +93,9 @@ REQUIRED FLAGS name, for example: cleanup.policy=compact,compression.type=producer. OPTIONAL FLAGS + --task-retry-disabled + Disable default task retry policy. + --task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF The maximum amount of time to wait before retrying a failed task in seconds. This sets an upper bound for the backoff delay. The default diff --git a/gcloud/managed-kafka/connectors/update b/gcloud/managed-kafka/connectors/update index 2414e269d..3826a4ba5 100644 --- a/gcloud/managed-kafka/connectors/update +++ b/gcloud/managed-kafka/connectors/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud managed-kafka connectors update (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [--task-retry-disabled] [--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]] [--task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF] @@ -19,11 +20,11 @@ EXAMPLES $ gcloud managed-kafka connectors update myconnector \ --location=us-central1 --configs=KEY1=VALUE1,KEY2=VALUE2... \ --connect-cluster=mycluster [--task-restart-min-backoff=60s] \ - [--task-restart-max-backoff=30m] OR + [--task-restart-max-backoff=30m] [--task-retry-disabled=true] OR $ gcloud managed-kafka connectors update myconnector \ --location=us-central1 --config-file=my-config-file.yaml \ --connect-cluster=mycluster [--task-restart-min-backoff=60s] \ - [--task-restart-max-backoff=30m] + [--task-restart-max-backoff=30m] [--task-retry-disabled=true] POSITIONAL ARGUMENTS Connector resource - Identifies the connector for which the command runs. @@ -68,6 +69,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line. FLAGS + --task-retry-disabled + Disable default task retry policy. + At most one of these can be specified: --config-file=JSON|YAML|FILE diff --git a/gcloud/model-armor/floorsettings/update b/gcloud/model-armor/floorsettings/update index 357523dde..603eed589 100644 --- a/gcloud/model-armor/floorsettings/update +++ b/gcloud/model-armor/floorsettings/update @@ -32,7 +32,8 @@ REQUIRED FLAGS OPTIONAL FLAGS --enable-floor-setting-enforcement=ENABLE_FLOOR_SETTING_ENFORCEMENT - Enable or disable the floor setting enforcement + Enable or disable the floor setting enforcement. Set the value to + "TRUE" to enable the floor setting enforcement, "FALSE" to disable it. Multi language detection enablement. @@ -119,16 +120,18 @@ OPTIONAL FLAGS SDP filter settings. --advanced-config-deidentify-template=ADVANCED_CONFIG_DEIDENTIFY_TEMPLATE - The sdp filter settings enforcement. The value can be either "enable" - or "disable". + The sdp filter settings enforcement. The value has to be a valid + template name. e.g. + projects/{project}/locations/{location}/deidentifyTemplates/{deidentify_template} --advanced-config-inspect-template=ADVANCED_CONFIG_INSPECT_TEMPLATE - The sdp filter settings enforcement. The value can be either "enable" - or "disable". + The sdp filter settings enforcement. The value has to be a valid + template name. e.g. + projects/{project}/locations/{location}/inspectTemplates/{inspect_template} --basic-config-filter-enforcement=BASIC_CONFIG_FILTER_ENFORCEMENT - The sdp filter settings enforcement. The value can be either - "ENABLED" or "DISABLED" + The sdp filter settings enforcement. The value can be either ENABLED + or DISABLED. Options for Google MCP server sanitization. diff --git a/gcloud/monitoring/help b/gcloud/monitoring/help index cc24d5d40..5e774d845 100644 --- a/gcloud/monitoring/help +++ b/gcloud/monitoring/help @@ -21,6 +21,9 @@ GROUPS dashboards Manage Cloud Monitoring dashboards. + policies + Manage Cloud Monitoring alerting policies. + snoozes Manage Cloud Monitoring snoozes. diff --git a/gcloud/monitoring/policies/conditions/create b/gcloud/monitoring/policies/conditions/create new file mode 100644 index 000000000..e245e5249 --- /dev/null +++ b/gcloud/monitoring/policies/conditions/create @@ -0,0 +1,95 @@ +NAME + gcloud monitoring policies conditions create - create a condition in an + alerting policy + +SYNOPSIS + gcloud monitoring policies conditions create ALERT_POLICY + [--aggregation=AGGREGATION + --condition-display-name=CONDITION_DISPLAY_NAME + --condition-filter=CONDITION_FILTER + --duration=DURATION --if=IF_VALUE --trigger-count=TRIGGER_COUNT + | --trigger-percent=TRIGGER_PERCENT] + [--condition=CONDITION | --condition-from-file=PATH_TO_FILE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a condition in an alerting policy. + +POSITIONAL ARGUMENTS + Alert Policy resource - Name of the Alert Policy to add a condition 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 alert_policy 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. + + ALERT_POLICY + ID of the Alert Policy or fully qualified identifier for the Alert + Policy. + + To set the policy attribute: + ▸ provide the argument alert_policy on the command line. + +FLAGS + Condition Settings. This will add a condition to the created policy. If + any conditions are already specified, this condition will be appended. + + --aggregation=AGGREGATION + Specifies an Aggregation message as a JSON/YAML value to be applied + to the condition. For more information about the format: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.alertPolicies + + --condition-display-name=CONDITION_DISPLAY_NAME + The display name for the condition. + + --condition-filter=CONDITION_FILTER + Specifies the "filter" in a metric absence or metric threshold + condition. + + --duration=DURATION + The duration (e.g. "60s", "2min", etc.) that the condition must hold + in order to trigger as true. + + --if=IF_VALUE + One of "absent", "< THRESHOLD", "> THRESHOLD" where "THRESHOLD" is an + integer or float. + + At most one of these can be specified: + + --trigger-count=TRIGGER_COUNT + The absolute number of time series that must fail the predicate for + the condition to be triggered. + + --trigger-percent=TRIGGER_PERCENT + The percentage of time series that must fail the predicate for the + condition to be triggered. + + At most one of these can be specified: + + --condition=CONDITION + The condition as a string. In either JSON or YAML format. + + --condition-from-file=PATH_TO_FILE + The path to a JSON or YAML file containing the condition. Use a full + or relative path to a local file containing the value of condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha monitoring policies conditions create + + $ gcloud beta monitoring policies conditions create + diff --git a/gcloud/monitoring/policies/conditions/delete b/gcloud/monitoring/policies/conditions/delete new file mode 100644 index 000000000..59e449a55 --- /dev/null +++ b/gcloud/monitoring/policies/conditions/delete @@ -0,0 +1,59 @@ +NAME + gcloud monitoring policies conditions delete - delete a condition in an + alerting policy + +SYNOPSIS + gcloud monitoring policies conditions delete (CONDITION : --policy=POLICY) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a condition in an alerting policy. If the specified condition does + not exist, this command will fail with an error. This will not delete the + policy if no conditions exist. + +POSITIONAL ARGUMENTS + Condition resource - The name of the Condition 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 condition 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. + + CONDITION + ID of the condition or fully qualified identifier for the condition. + + To set the condition attribute: + ▸ provide the argument condition on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --policy=POLICY + Name of the alerting policy. + + To set the policy attribute: + ▸ provide the argument condition on the command line with a fully + specified name; + ▸ provide the argument --policy on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha monitoring policies conditions delete + + $ gcloud beta monitoring policies conditions delete + diff --git a/gcloud/monitoring/policies/conditions/describe b/gcloud/monitoring/policies/conditions/describe new file mode 100644 index 000000000..13a0bb2f8 --- /dev/null +++ b/gcloud/monitoring/policies/conditions/describe @@ -0,0 +1,57 @@ +NAME + gcloud monitoring policies conditions describe - describe a condition in a + Cloud Monitoring alerting policy + +SYNOPSIS + gcloud monitoring policies conditions describe + (CONDITION : --policy=POLICY) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a condition in a Cloud Monitoring alerting policy. + +POSITIONAL ARGUMENTS + Condition resource - The name of the Condition 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 condition 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. + + CONDITION + ID of the condition or fully qualified identifier for the condition. + + To set the condition attribute: + ▸ provide the argument condition on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --policy=POLICY + Name of the alerting policy. + + To set the policy attribute: + ▸ provide the argument condition on the command line with a fully + specified name; + ▸ provide the argument --policy on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha monitoring policies conditions describe + + $ gcloud beta monitoring policies conditions describe + diff --git a/gcloud/monitoring/policies/conditions/help b/gcloud/monitoring/policies/conditions/help new file mode 100644 index 000000000..c186c7f31 --- /dev/null +++ b/gcloud/monitoring/policies/conditions/help @@ -0,0 +1,40 @@ +NAME + gcloud monitoring policies conditions - manage Cloud Monitoring alerting + policy conditions + +SYNOPSIS + gcloud monitoring policies conditions COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Monitoring alerting policies conditions. + + More information can be found here: + https://cloud.google.com/monitoring/api/v3/ + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a condition in an alerting policy. + + delete + Delete a condition in an alerting policy. + + describe + Describe a condition in a Cloud Monitoring alerting policy. + + update + Update a condition in an alerting policy. + +NOTES + These variants are also available: + + $ gcloud alpha monitoring policies conditions + + $ gcloud beta monitoring policies conditions + diff --git a/gcloud/monitoring/policies/conditions/update b/gcloud/monitoring/policies/conditions/update new file mode 100644 index 000000000..1a24d8059 --- /dev/null +++ b/gcloud/monitoring/policies/conditions/update @@ -0,0 +1,77 @@ +NAME + gcloud monitoring policies conditions update - update a condition in an + alerting policy + +SYNOPSIS + gcloud monitoring policies conditions update (CONDITION : --policy=POLICY) + [--display-name=DISPLAY_NAME] [--if=IF_VALUE] + [--trigger-count=TRIGGER_COUNT | --trigger-percent=TRIGGER_PERCENT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a condition in an alerting policy. + +POSITIONAL ARGUMENTS + Condition resource - The name of the Condition 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 condition 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. + + CONDITION + ID of the condition or fully qualified identifier for the condition. + + To set the condition attribute: + ▸ provide the argument condition on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --policy=POLICY + Name of the alerting policy. + + To set the policy attribute: + ▸ provide the argument condition on the command line with a fully + specified name; + ▸ provide the argument --policy on the command line. + +FLAGS + --display-name=DISPLAY_NAME + The display name for the Condition. + + --if=IF_VALUE + One of "absent", "< THRESHOLD", "> THRESHOLD" where "THRESHOLD" is an + integer or float. + + At most one of these can be specified: + + --trigger-count=TRIGGER_COUNT + The absolute number of time series that must fail the predicate for + the condition to be triggered. + + --trigger-percent=TRIGGER_PERCENT + The percentage of time series that must fail the predicate for the + condition to be triggered. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha monitoring policies conditions update + + $ gcloud beta monitoring policies conditions update + diff --git a/gcloud/monitoring/policies/create b/gcloud/monitoring/policies/create new file mode 100644 index 000000000..40b972b66 --- /dev/null +++ b/gcloud/monitoring/policies/create @@ -0,0 +1,170 @@ +NAME + gcloud monitoring policies create - create a new alerting policy + +SYNOPSIS + gcloud monitoring policies create + [--notification-channels=[NOTIFICATION_CHANNELS,...]] + [--aggregation=AGGREGATION + --condition-display-name=CONDITION_DISPLAY_NAME + --condition-filter=CONDITION_FILTER + --duration=DURATION --if=IF_VALUE --trigger-count=TRIGGER_COUNT + | --trigger-percent=TRIGGER_PERCENT] + [--combiner=COMBINER --display-name=DISPLAY_NAME --no-enabled + --user-labels=[KEY=VALUE,...] + --documentation-format=DOCUMENTATION_FORMAT; + default="text/markdown" --documentation=DOCUMENTATION + | --documentation-from-file=PATH_TO_FILE] + [--policy=POLICY | --policy-from-file=PATH_TO_FILE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Creates a new alerting policy. An alert policy can be specified as a + JSON/YAML value passed in as a string through the --policy flag or as a + file through the --policy-from-file flag. A basic policy can also be + specified through command line flags. If a policy is specified through + --policy or --policy-from-file, and additional flags are supplied, the + flags will override the policy's settings and a specified condition will be + appended to the list of conditions. + + For information about the JSON/YAML format of an alerting policy: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.alertPolicies + +FLAGS + Notification Channel resource - Names of one or more Notification Channels + to be added to the policy. These should be the resource names (not the + display name) of the channels. Acceptable formats are: + + ◆ Channel Name: my-channel + ▸ The project specified through --project or the default project + defined by the core/project property will be used, in that order. + ◆ Channel Relative Name: + projects/my-project/notificationChannels/channel-id0 + ◆ Channel URI: + https://monitoring.googleapis.com/v3/projects/my-project/notificationChannels/channel-id0 + 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 --notification-channels on the command line with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --notification-channels=[NOTIFICATION_CHANNELS,...] + IDs of the Notification Channels or fully qualified identifiers for + the Notification Channels. + + To set the notification_channels attribute: + ▸ provide the argument --notification-channels on the command line. + + Condition Settings. This will add a condition to the created policy. If + any conditions are already specified, this condition will be appended. + + --aggregation=AGGREGATION + Specifies an Aggregation message as a JSON/YAML value to be applied + to the condition. For more information about the format: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.alertPolicies + + --condition-display-name=CONDITION_DISPLAY_NAME + The display name for the condition. + + --condition-filter=CONDITION_FILTER + Specifies the "filter" in a metric absence or metric threshold + condition. + + --duration=DURATION + The duration (e.g. "60s", "2min", etc.) that the condition must hold + in order to trigger as true. + + --if=IF_VALUE + One of "absent", "< THRESHOLD", "> THRESHOLD" where "THRESHOLD" is an + integer or float. + + At most one of these can be specified: + + --trigger-count=TRIGGER_COUNT + The absolute number of time series that must fail the predicate for + the condition to be triggered. + + --trigger-percent=TRIGGER_PERCENT + The percentage of time series that must fail the predicate for the + condition to be triggered. + + Policy Settings. If any of these are specified, they will overwrite fields + in the --policy or --policy-from-file flags if specified. + + --combiner=COMBINER + The combiner for the Alert Policy. COMBINER must be one of: + + AND + An incident is created only if all conditions are met + simultaneously. This combiner is satisfied if all conditions are + met, even if they are met on completely different resources. + AND_WITH_MATCHING_RESOURCE + Combine conditions using logical AND operator, but unlike the + regular AND option, an incident is created only if all conditions + are met simultaneously on at least one resource. + COMBINE_UNSPECIFIED + An unspecified combiner + OR + An incident is created if any of the listed conditions is met. + + --display-name=DISPLAY_NAME + The display name for the Alert Policy. + + --enabled + If the policy is enabled. Enabled by default, use --no-enabled to + disable. + + --user-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. + + If the policy was given as a JSON/YAML object from a string or file, + this flag will replace the labels value in the given policy. + + Documentation + + --documentation-format=DOCUMENTATION_FORMAT; default="text/markdown" + The MIME type that should be used with --documentation or + --documentation-from-file. Currently, only "text/markdown" is + supported. + + At most one of these can be specified: + + --documentation=DOCUMENTATION + The documentation to be included with the policy. + + --documentation-from-file=PATH_TO_FILE + The path to a file containing the documentation to be included + with the policy. Use a full or relative path to a local file + containing the value of documentation. + + At most one of these can be specified: + + --policy=POLICY + The policy as a string. In either JSON or YAML format. + + --policy-from-file=PATH_TO_FILE + The path to a JSON or YAML file containing the policy. Use a full or + relative path to a local file containing the value of policy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha monitoring policies create + + $ gcloud beta monitoring policies create + diff --git a/gcloud/monitoring/policies/delete b/gcloud/monitoring/policies/delete new file mode 100644 index 000000000..5e74de35f --- /dev/null +++ b/gcloud/monitoring/policies/delete @@ -0,0 +1,48 @@ +NAME + gcloud monitoring policies delete - delete a Cloud Monitoring alerting + policy + +SYNOPSIS + gcloud monitoring policies delete POLICY [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Monitoring alerting policy. + +POSITIONAL ARGUMENTS + Policy resource - The alerting policy to delete. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument policy 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. + + POLICY + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + These variants are also available: + + $ gcloud alpha monitoring policies delete + + $ gcloud beta monitoring policies delete + diff --git a/gcloud/monitoring/policies/describe b/gcloud/monitoring/policies/describe new file mode 100644 index 000000000..e8a3e46fa --- /dev/null +++ b/gcloud/monitoring/policies/describe @@ -0,0 +1,47 @@ +NAME + gcloud monitoring policies describe - describe an alerting policy + +SYNOPSIS + gcloud monitoring policies describe POLICY [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an alerting policy. + +POSITIONAL ARGUMENTS + Policy resource - The alerting policy to describe. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument policy 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. + + POLICY + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + These variants are also available: + + $ gcloud alpha monitoring policies describe + + $ gcloud beta monitoring policies describe + diff --git a/gcloud/monitoring/policies/help b/gcloud/monitoring/policies/help new file mode 100644 index 000000000..252f45871 --- /dev/null +++ b/gcloud/monitoring/policies/help @@ -0,0 +1,51 @@ +NAME + gcloud monitoring policies - manage Cloud Monitoring alerting policies + +SYNOPSIS + gcloud monitoring policies GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Monitoring alerting policies. + + More information can be found here: + https://cloud.google.com/monitoring/api/v3/ + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + conditions + Manage Cloud Monitoring alerting policy conditions. + +COMMANDS + COMMAND is one of the following: + + create + Create a new alerting policy. + + delete + Delete a Cloud Monitoring alerting policy. + + describe + Describe an alerting policy. + + list + List alerting policies. + + migrate + Migrate a Prometheus configuration file to Cloud Monitoring. + + update + Updates an alerting policy. + +NOTES + These variants are also available: + + $ gcloud alpha monitoring policies + + $ gcloud beta monitoring policies + diff --git a/gcloud/monitoring/policies/list b/gcloud/monitoring/policies/list new file mode 100644 index 000000000..3142825b9 --- /dev/null +++ b/gcloud/monitoring/policies/list @@ -0,0 +1,86 @@ +NAME + gcloud monitoring policies list - list alerting policies + +SYNOPSIS + gcloud monitoring policies list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List alerting policies. + +EXAMPLES + To order your results first by the team key in user_labels and then the + policy's display name: + + $ gcloud monitoring policies list \ + --sort-by user_label.team,display_name + + To order your results in reverse order, you can add either '~' or '-' in + front of the field name: + + $ gcloud monitoring policies list --sort-by "-display_name" + + To return results with non-empty display names or descriptions: + + $ gcloud monitoring policies list \ + --filter "(NOT display_name.empty OR NOT description.empty)" + + To return results whose descriptions contain the word 'cloud': + + $ gcloud monitoring policies list --filter "description:(cloud)" + + Please find all supported fields at + https://cloud.google.com/monitoring/api/v3/sorting-and-filtering#alertpolicy. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + These variants are also available: + + $ gcloud alpha monitoring policies list + + $ gcloud beta monitoring policies list + diff --git a/gcloud/monitoring/policies/migrate b/gcloud/monitoring/policies/migrate new file mode 100644 index 000000000..c2793a7ca --- /dev/null +++ b/gcloud/monitoring/policies/migrate @@ -0,0 +1,44 @@ +NAME + gcloud monitoring policies migrate - migrate a Prometheus configuration + file to Cloud Monitoring + +SYNOPSIS + gcloud monitoring policies migrate + [--channels-from-prometheus-alertmanager-yaml=PROMETHEUS_ALERT_MANAGER_FILE_PATH --policies-from-prometheus-alert-rules-yaml=[PROMETHEUS_ALERT_RULE_FILE_PATHS, + ...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Creates new alerting policies and/or notification channels based on + provided Prometheus files. The rules YAML file, which holds the alert + rules, must be specified as a file through the + --policies-from-prometheus-alert-rules-yaml flag. + +FLAGS + --channels-from-prometheus-alertmanager-yaml=PROMETHEUS_ALERT_MANAGER_FILE_PATH + Prometheus alert manager YAML file to be converted to Cloud Monitoring + notification channels. Specifying this flag with the + --policies-from-prometheus-alert-rules-yaml flag puts the newly created + notification channels into the translated Alert Policies' definition. + Use a full or relative path to a local file containing the value of + channels_from_prometheus_alertmanager_yaml. + + --policies-from-prometheus-alert-rules-yaml=[PROMETHEUS_ALERT_RULE_FILE_PATHS,...] + One or more Prometheus alert rule YAML files (separated by commas if + multiple) to be converted to Cloud Alerting Policies. Example: + --policies-from-prometheus-alert-rules-yaml=rules_1.yaml,rules_2.yaml + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha monitoring policies migrate + + $ gcloud beta monitoring policies migrate + diff --git a/gcloud/monitoring/policies/update b/gcloud/monitoring/policies/update new file mode 100644 index 000000000..55c77f12a --- /dev/null +++ b/gcloud/monitoring/policies/update @@ -0,0 +1,182 @@ +NAME + gcloud monitoring policies update - updates an alerting policy + +SYNOPSIS + gcloud monitoring policies update ALERT_POLICY + [--fields=[field,...] | --combiner=COMBINER --display-name=DISPLAY_NAME + --[no-]enabled + --add-notification-channels=[NOTIFICATION-CHANNELS,...] + | --clear-notification-channels + | --remove-notification-channels=[NOTIFICATION-CHANNELS,...] + | --set-notification-channels=[NOTIFICATION-CHANNELS,...] + --documentation-format=DOCUMENTATION_FORMAT + --documentation=DOCUMENTATION + | --documentation-from-file=PATH_TO_FILE + --update-user-labels=[KEY=VALUE,...] --clear-user-labels + | --remove-user-labels=[KEY,...]] + [--policy=POLICY | --policy-from-file=PATH_TO_FILE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates an alerting policy. + + If --policy or --policy-from-file are specified: + + ▪ If --fields is specified, the only the specified fields will be + updated. + ▪ Else, the policy will be replaced with the provided policy. The + policy can be modified further using the flags from the Policy Settings + group below. + + Otherwise, the policy will be updated with the values specified in the + flags from the Policy Settings group. + + For information about the JSON/YAML format of an alerting policy: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.alertPolicies + +POSITIONAL ARGUMENTS + Alert Policy resource - Name of the Alert Policy to be updated. 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 alert_policy 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. + + ALERT_POLICY + ID of the Alert Policy or fully qualified identifier for the Alert + Policy. + + To set the policy attribute: + ▸ provide the argument alert_policy on the command line. + +FLAGS + At most one of these can be specified: + + --fields=[field,...] + The list of fields to update. Must specify --policy or + --policy-from-file if using this flag. field must be one of: + disabled, notificationChannels. + + Policy Settings. If any of these are specified, they will overwrite + fields in the --policy or --policy-from-file flags if specified. + + --combiner=COMBINER + The combiner for the Alert Policy. COMBINER must be one of: + + AND + An incident is created only if all conditions are met + simultaneously. This combiner is satisfied if all conditions + are met, even if they are met on completely different + resources. + AND_WITH_MATCHING_RESOURCE + Combine conditions using logical AND operator, but unlike the + regular AND option, an incident is created only if all + conditions are met simultaneously on at least one resource. + COMBINE_UNSPECIFIED + An unspecified combiner + OR + An incident is created if any of the listed conditions is met. + + --display-name=DISPLAY_NAME + The display name for the Alert Policy. + + --[no-]enabled + If the policy is enabled. Use --enabled to enable and --no-enabled + to disable. + + These flags modify the member Notification Channels of this Alert + Policy. + + At most one of these can be specified: + + --add-notification-channels=[NOTIFICATION-CHANNELS,...] + Append the given values to the current Notification Channels. + + --clear-notification-channels + Empty the current Notification Channels. + + --remove-notification-channels=[NOTIFICATION-CHANNELS,...] + Remove the given values from the current Notification Channels. + + --set-notification-channels=[NOTIFICATION-CHANNELS,...] + Completely replace the current Notification Channels with the + given values. + + Documentation + + --documentation-format=DOCUMENTATION_FORMAT + The MIME type that should be used with --documentation or + --documentation-from-file. Currently, only "text/markdown" is + supported. + + At most one of these can be specified: + + --documentation=DOCUMENTATION + The documentation to be included with the policy. + + --documentation-from-file=PATH_TO_FILE + The path to a file containing the documentation to be included + with the policy. Use a full or relative path to a local file + containing the value of documentation. + + User Labels + + --update-user-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-user-labels + Remove all labels. If --update-user-labels is also specified + then --clear-user-labels is applied first. + + For example, to remove all labels: + + $ gcloud monitoring policies update --clear-user-labels + + To remove all existing labels and create two new labels, foo + and baz: + + $ gcloud monitoring policies update --clear-user-labels \ + --update-user-labels foo=bar,baz=qux + + --remove-user-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-user-labels is also specified + then --update-user-labels is applied first. + + At most one of these can be specified: + + --policy=POLICY + The policy as a string. In either JSON or YAML format. + + --policy-from-file=PATH_TO_FILE + The path to a JSON or YAML file containing the policy. Use a full or + relative path to a local file containing the value of policy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha monitoring policies update + + $ gcloud beta monitoring policies update + diff --git a/gcloud/netapp/backup-vaults/create b/gcloud/netapp/backup-vaults/create index 73ce1b1a1..c36187807 100644 --- a/gcloud/netapp/backup-vaults/create +++ b/gcloud/netapp/backup-vaults/create @@ -9,8 +9,8 @@ SYNOPSIS [manual-backup-immutable=MANUAL-BACKUP-IMMUTABLE], [monthly-backup-immutable=MONTHLY-BACKUP-IMMUTABLE], [weekly-backup-immutable=WEEKLY-BACKUP-IMMUTABLE]] - [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--kms-config=KMS_CONFIG] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a Cloud NetApp Backup Vault. @@ -78,6 +78,31 @@ FLAGS --description=DESCRIPTION A description of the Cloud NetApp Backup Vault + Kms config resource - The resource name of the KMS Config to use for + encrypting backups within this backup vault. Format: + projects/{project_id}/locations/{location}/kmsConfigs/{kms_config_id} 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 --kms-config 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 --kms-config on the command line with a fully + specified name; + ◆ provide the argument --location on the command line; + ◆ set the property netapp/location. + + --kms-config=KMS_CONFIG + ID of the kms_config or fully qualified identifier for the + kms_config. + + To set the kms_config attribute: + ▸ provide the argument --kms-config on the command line. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/netapp/volumes/create b/gcloud/netapp/volumes/create index 1968be663..d904530a0 100644 --- a/gcloud/netapp/volumes/create +++ b/gcloud/netapp/volumes/create @@ -15,16 +15,19 @@ SYNOPSIS [peer-cluster-name=PEER-CLUSTER-NAME], [peer-ip-addresses=PEER-IP-ADDRESSES], [peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME]] + [--cache-pre-populate=[exclude-path-list=EXCLUDE-PATH-LIST], + [path-list=PATH-LIST],[recursion=RECURSION]] [--description=DESCRIPTION] [--enable-kerberos=ENABLE_KERBEROS] [--export-policy=[access-type=ACCESS-TYPE], - [allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS], + [allowed-clients=ALLOWED-CLIENTS],[anon-uid=ANON-UID], + [has-root-access=HAS-ROOT-ACCESS], [kerberos-5-read-only=KERBEROS-5-READ-ONLY], [kerberos-5-read-write=KERBEROS-5-READ-WRITE], [kerberos-5i-read-only=KERBEROS-5I-READ-ONLY], [kerberos-5i-read-write=KERBEROS-5I-READ-WRITE], [kerberos-5p-read-only=KERBEROS-5P-READ-ONLY], [kerberos-5p-read-write=KERBEROS-5P-READ-WRITE], - [nfsv3=NFSV3],[nfsv4=NFSV4]] + [nfsv3=NFSV3],[nfsv4=NFSV4],[squash-mode=SQUASH-MODE]] [--hybrid-replication-parameters=[cluster-location=CLUSTER-LOCATION], [description=DESCRIPTION], [hybrid-replication-type=HYBRID-REPLICATION-TYPE],[labels=LABELS], @@ -196,13 +199,29 @@ OPTIONAL FLAGS *enable-global-file-lock*::: If true, enable global file lock *cache-config*::: Cache-config as a hashtag-separated(#) list of key-value pairs + --cache-pre-populate=[exclude-path-list=EXCLUDE-PATH-LIST],[path-list=PATH-LIST],[recursion=RECURSION] + Cache Pre-populate contains cache pre-populate parameters of a volume. + + Cache Pre-populate will have the following format + --cache-pre-populate=path-list=PATH_LIST1#PATH_LIST2, + exclude-path-list=EXCLUDE_PATH_LIST1#EXCLUDE_PATH_LIST2, + recursion=RECURSION + + path-list + Hashtag-separated(#) list of paths to be pre-populated + exclude-path-list + Hashtag-separated(#) list of paths to be excluded from + pre-population + recursion + Boolean value indicating pre-populate recursion. + --description=DESCRIPTION A description of the Cloud NetApp Volume --enable-kerberos=ENABLE_KERBEROS Boolean flag indicating whether Volume is a kerberos Volume or not - --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4] + --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[anon-uid=ANON-UID],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4],[squash-mode=SQUASH-MODE] Export Policy of a Cloud NetApp Files Volume. This will be a field similar to network in which export policy fields can be specified as such: --export-policy=allowed-clients=ALLOWED_CLIENTS_IP_ADDRESSES, @@ -212,7 +231,8 @@ OPTIONAL FLAGS kerberos-5i-read-only=KERBEROS_5I_READ_ONLY, kerberos-5i-read-write=KERBEROS_5I_READ_WRITE, kerberos-5p-read-only=KERBEROS_5P_READ_ONLY, - kerberos-5p-read-write=KERBEROS_5P_READ_WRITE + kerberos-5p-read-write=KERBEROS_5P_READ_WRITE, + squash-mode=SQUASH_MODE,anon-uid=ANON_UID --hybrid-replication-parameters=[cluster-location=CLUSTER-LOCATION],[description=DESCRIPTION],[hybrid-replication-type=HYBRID-REPLICATION-TYPE],[labels=LABELS],[large-volume-constituent-count=LARGE-VOLUME-CONSTITUENT-COUNT],[peer-cluster-name=PEER-CLUSTER-NAME],[peer-ip-addresses=PEER-IP-ADDRESSES],[peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME],[replication=REPLICATION],[replication-schedule=REPLICATION-SCHEDULE] Hybrid Replication Parameters contains hybrid replication parameters on diff --git a/gcloud/netapp/volumes/update b/gcloud/netapp/volumes/update index b480cf2d7..fafaa7430 100644 --- a/gcloud/netapp/volumes/update +++ b/gcloud/netapp/volumes/update @@ -13,17 +13,20 @@ SYNOPSIS [peer-cluster-name=PEER-CLUSTER-NAME], [peer-ip-addresses=PEER-IP-ADDRESSES], [peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME]] - [--capacity=CAPACITY] [--description=DESCRIPTION] - [--enable-kerberos=ENABLE_KERBEROS] + [--cache-pre-populate=[exclude-path-list=EXCLUDE-PATH-LIST], + [path-list=PATH-LIST],[recursion=RECURSION]] [--capacity=CAPACITY] + [--description=DESCRIPTION] [--enable-kerberos=ENABLE_KERBEROS] [--export-policy=[access-type=ACCESS-TYPE], - [allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS], + [allowed-clients=ALLOWED-CLIENTS],[anon-uid=ANON-UID], + [has-root-access=HAS-ROOT-ACCESS], [kerberos-5-read-only=KERBEROS-5-READ-ONLY], [kerberos-5-read-write=KERBEROS-5-READ-WRITE], [kerberos-5i-read-only=KERBEROS-5I-READ-ONLY], [kerberos-5i-read-write=KERBEROS-5I-READ-WRITE], [kerberos-5p-read-only=KERBEROS-5P-READ-ONLY], [kerberos-5p-read-write=KERBEROS-5P-READ-WRITE], - [nfsv3=NFSV3],[nfsv4=NFSV4]] [--protocols=PROTOCOL,[PROTOCOL,...]] + [nfsv3=NFSV3],[nfsv4=NFSV4],[squash-mode=SQUASH-MODE]] + [--protocols=PROTOCOL,[PROTOCOL,...]] [--restricted-actions=RESTRICTED_ACTION,[...]] [--security-style=SECURITY_STYLE; default="SECURITY_STYLE_UNSPECIFIED"] [--share-name=SHARE_NAME] @@ -143,6 +146,22 @@ FLAGS *enable-global-file-lock*::: If true, enable global file lock *cache-config*::: Cache-config as a hashtag-separated(#) list of key-value pairs + --cache-pre-populate=[exclude-path-list=EXCLUDE-PATH-LIST],[path-list=PATH-LIST],[recursion=RECURSION] + Cache Pre-populate contains cache pre-populate parameters of a volume. + + Cache Pre-populate will have the following format + --cache-pre-populate=path-list=PATH_LIST1#PATH_LIST2, + exclude-path-list=EXCLUDE_PATH_LIST1#EXCLUDE_PATH_LIST2, + recursion=RECURSION + + path-list + Hashtag-separated(#) list of paths to be pre-populated + exclude-path-list + Hashtag-separated(#) list of paths to be excluded from + pre-population + recursion + Boolean value indicating pre-populate recursion. + --capacity=CAPACITY The desired capacity of the Volume in GiB or TiB units.If no capacity unit is specified, GiB is assumed. @@ -153,7 +172,7 @@ FLAGS --enable-kerberos=ENABLE_KERBEROS Boolean flag indicating whether Volume is a kerberos Volume or not - --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4] + --export-policy=[access-type=ACCESS-TYPE],[allowed-clients=ALLOWED-CLIENTS],[anon-uid=ANON-UID],[has-root-access=HAS-ROOT-ACCESS],[kerberos-5-read-only=KERBEROS-5-READ-ONLY],[kerberos-5-read-write=KERBEROS-5-READ-WRITE],[kerberos-5i-read-only=KERBEROS-5I-READ-ONLY],[kerberos-5i-read-write=KERBEROS-5I-READ-WRITE],[kerberos-5p-read-only=KERBEROS-5P-READ-ONLY],[kerberos-5p-read-write=KERBEROS-5P-READ-WRITE],[nfsv3=NFSV3],[nfsv4=NFSV4],[squash-mode=SQUASH-MODE] Export Policy of a Cloud NetApp Files Volume. This will be a field similar to network in which export policy fields can be specified as such: --export-policy=allowed-clients=ALLOWED_CLIENTS_IP_ADDRESSES, @@ -163,7 +182,8 @@ FLAGS kerberos-5i-read-only=KERBEROS_5I_READ_ONLY, kerberos-5i-read-write=KERBEROS_5I_READ_WRITE, kerberos-5p-read-only=KERBEROS_5P_READ_ONLY, - kerberos-5p-read-write=KERBEROS_5P_READ_WRITE + kerberos-5p-read-write=KERBEROS_5P_READ_WRITE, + squash-mode=SQUASH_MODE,anon-uid=ANON_UID --protocols=PROTOCOL,[PROTOCOL,...] Type of File System protocols for the Cloud NetApp Files Volume. Valid diff --git a/gcloud/privateca/pools/create b/gcloud/privateca/pools/create index 6dfffe5ba..c3e16e72b 100644 --- a/gcloud/privateca/pools/create +++ b/gcloud/privateca/pools/create @@ -3,8 +3,8 @@ NAME SYNOPSIS gcloud privateca pools create (CA_POOL : --location=LOCATION) - [--issuance-policy=ISSUANCE_POLICY] [--labels=[KEY=VALUE,...]] - [--no-publish-ca-cert] [--no-publish-crl] + [--encryption-key=ENCRYPTION_KEY] [--issuance-policy=ISSUANCE_POLICY] + [--labels=[KEY=VALUE,...]] [--no-publish-ca-cert] [--no-publish-crl] [--publishing-encoding-format=PUBLISHING_ENCODING_FORMAT; default="pem"] [--tier=TIER; default="enterprise"] [GCLOUD_WIDE_FLAG ...] @@ -58,6 +58,11 @@ POSITIONAL ARGUMENTS ▸ set the property privateca/location. FLAGS + --encryption-key=ENCRYPTION_KEY + The full resource name of the Cloud KMS key to use for encrypting + certificate data at rest. The key must be in the same region as the CA + pool. + --issuance-policy=ISSUANCE_POLICY A YAML file describing this CA Pool's issuance policy. diff --git a/gcloud/privateca/pools/update b/gcloud/privateca/pools/update index c1e78466a..85f646a7a 100644 --- a/gcloud/privateca/pools/update +++ b/gcloud/privateca/pools/update @@ -3,8 +3,8 @@ NAME SYNOPSIS gcloud privateca pools update (CA_POOL : --location=LOCATION) - [--issuance-policy=ISSUANCE_POLICY] [--no-publish-ca-cert] - [--no-publish-crl] + [--encryption-key=ENCRYPTION_KEY] [--issuance-policy=ISSUANCE_POLICY] + [--no-publish-ca-cert] [--no-publish-crl] [--publishing-encoding-format=PUBLISHING_ENCODING_FORMAT; default="pem"] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -52,6 +52,11 @@ POSITIONAL ARGUMENTS ▸ set the property privateca/location. FLAGS + --encryption-key=ENCRYPTION_KEY + The full resource name of the Cloud KMS key to use for encrypting + certificate data at rest. The key must be in the same region as the CA + pool. + --issuance-policy=ISSUANCE_POLICY A YAML file describing this CA Pool's issuance policy. diff --git a/gcloud/resource-manager/capabilities/describe b/gcloud/resource-manager/capabilities/describe new file mode 100644 index 000000000..d61c85c9c --- /dev/null +++ b/gcloud/resource-manager/capabilities/describe @@ -0,0 +1,42 @@ +NAME + gcloud resource-manager capabilities describe - show whether a Capability + is enabled + +SYNOPSIS + gcloud resource-manager capabilities describe CAPABILITY_ID + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Command to show whether a Capability is enabled. + + This command can fail for the following reasons: + ▪ The capability specified does not exist. + ▪ The active account does not have permission to access the given + folder/capability. + +EXAMPLES + The following command prints metadata for a capability with the ID + folders/123/capabilities/app-management: + + $ gcloud resource-manager capabilities describe \ + "folders/123/capabilities/app-management" + +POSITIONAL ARGUMENTS + CAPABILITY_ID + ID for the capability you want 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 + These variants are also available: + + $ gcloud alpha resource-manager capabilities describe + + $ gcloud beta resource-manager capabilities describe + diff --git a/gcloud/resource-manager/capabilities/help b/gcloud/resource-manager/capabilities/help new file mode 100644 index 000000000..d2ce948f8 --- /dev/null +++ b/gcloud/resource-manager/capabilities/help @@ -0,0 +1,30 @@ +NAME + gcloud resource-manager capabilities - manage Cloud Folder Capabilities + +SYNOPSIS + gcloud resource-manager capabilities COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands to query and update your Cloud Folder's Capabilities. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Show whether a Capability is enabled. + + update + Update a folder capability. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager capabilities + + $ gcloud beta resource-manager capabilities + diff --git a/gcloud/resource-manager/capabilities/update b/gcloud/resource-manager/capabilities/update new file mode 100644 index 000000000..6085b9c5f --- /dev/null +++ b/gcloud/resource-manager/capabilities/update @@ -0,0 +1,58 @@ +NAME + gcloud resource-manager capabilities update - update a folder capability + +SYNOPSIS + gcloud resource-manager capabilities update CAPABILITY_ID --[no-]enable + [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Command to Update/Set the value field of the Folder capability. This can be + done by using the --enable flag to set the value to True, and the + --no-enable flag to set the value to False. + + This command can fail for the following reasons: + ▪ There is no folder parenting the given capability name. + ▪ The active account does not have permission to update the given + folder/capability. + +EXAMPLES + The following command updates a capability with the ID + folders/123/capabilities/app-management to have the value True: + + $ gcloud resource-manager capabilities update \ + "folders/123/capabilities/app-management" --enable + + In order to set the value to False, the following command can be used: + + $ gcloud resource-manager capabilities update \ + "folders/123/capabilities/app-management" --no-enable + +POSITIONAL ARGUMENTS + CAPABILITY_ID + ID for the capability you want to update. + +REQUIRED FLAGS + --[no-]enable + Enable the Capability. Use --enable to enable and --no-enable to + disable. + +OPTIONAL FLAGS + --update-mask=UPDATE_MASK + Update Mask. This is an optional field, and the only valid value this + can be set to currently is "value". + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager capabilities update + + $ gcloud beta resource-manager capabilities update + diff --git a/gcloud/resource-manager/help b/gcloud/resource-manager/help index 0a71c8d12..b8fa87acd 100644 --- a/gcloud/resource-manager/help +++ b/gcloud/resource-manager/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + capabilities + Manage Cloud Folder Capabilities. + folders Manage Cloud Folders. diff --git a/gcloud/run/jobs/logs/help b/gcloud/run/jobs/logs/help index ff83096dc..d501d1802 100644 --- a/gcloud/run/jobs/logs/help +++ b/gcloud/run/jobs/logs/help @@ -8,10 +8,6 @@ DESCRIPTION Read logs for Cloud Run jobs. EXAMPLES - To tail logs executions for a job, run: - - $ gcloud run jobs logs tail my-job - To read logs executions for a job, run: $ gcloud run jobs logs read my-job diff --git a/gcloud/run/multi-region-services/update b/gcloud/run/multi-region-services/update index faa7ae0a4..0fd80721d 100644 --- a/gcloud/run/multi-region-services/update +++ b/gcloud/run/multi-region-services/update @@ -321,10 +321,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: --clear-volumes Remove all existing volumes from the Cloud Run resource, including diff --git a/gcloud/scheduler/cmek-config/update b/gcloud/scheduler/cmek-config/update index 1e7cb93c7..54f874e32 100644 --- a/gcloud/scheduler/cmek-config/update +++ b/gcloud/scheduler/cmek-config/update @@ -13,8 +13,8 @@ DESCRIPTION EXAMPLES To update a CMEK config: $ gcloud scheduler cmek-config update --location=my-location \ - --kms-location=europe-southwest1 --kms-project=new-kms-project \ - --kms-keyring=kms-keyring2 --kms-key=crypto-key2 + --kms-project=new-kms-project --kms-keyring=kms-keyring2 \ + --kms-key-name=crypto-key2 FLAGS --location=LOCATION diff --git a/gcloud/services/disable b/gcloud/services/disable index 6a22e9389..98dd6714d 100644 --- a/gcloud/services/disable +++ b/gcloud/services/disable @@ -2,7 +2,7 @@ NAME gcloud services disable - disable a service for consumption for a project SYNOPSIS - gcloud services disable [SERVICE ...] [--async] [--force] + gcloud services disable SERVICE [SERVICE ...] [--async] [--force] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -28,7 +28,7 @@ EXAMPLES $ gcloud services disable my-consumed-service --async POSITIONAL ARGUMENTS - [SERVICE ...] + SERVICE [SERVICE ...] The name of the service(s) to disable. FLAGS diff --git a/gcloud/services/enable b/gcloud/services/enable index 425744ad4..14f94d942 100644 --- a/gcloud/services/enable +++ b/gcloud/services/enable @@ -2,7 +2,8 @@ NAME gcloud services enable - enables a service for consumption for a project SYNOPSIS - gcloud services enable [SERVICE ...] [--async] [GCLOUD_WIDE_FLAG ...] + gcloud services enable SERVICE [SERVICE ...] [--async] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command enables a service for consumption for a project. @@ -30,7 +31,7 @@ EXAMPLES $ gcloud services enable service1 service2 service3 POSITIONAL ARGUMENTS - [SERVICE ...] + SERVICE [SERVICE ...] The name of the service(s) to enable. FLAGS diff --git a/gcloud/workbench/instances/create b/gcloud/workbench/instances/create index e1f03daa2..2d05a65a1 100644 --- a/gcloud/workbench/instances/create +++ b/gcloud/workbench/instances/create @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud workbench instances create (INSTANCE : --location=LOCATION) - [--async] [--disable-proxy-access] [--enable-third-party-identity] - [--instance-owners=INSTANCE_OWNERS] [--labels=[KEY=VALUE,...]] + [--async] [--disable-proxy-access] [--enable-managed-euc] + [--enable-third-party-identity] [--instance-owners=INSTANCE_OWNERS] + [--labels=[KEY=VALUE,...]] [--confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE --disable-public-ip --enable-ip-forwarding --machine-type=MACHINE_TYPE; default="n1-standard-4" @@ -117,6 +118,10 @@ FLAGS --disable-proxy-access If true, the notebook instance will not register with the proxy. + --enable-managed-euc + If true, the notebook instance will be created with managed end user + credentials enabled. + --enable-third-party-identity If true, the notebook instance provide a proxy endpoint which allows for third party identity. diff --git a/gcloud/workstations/configs/create b/gcloud/workstations/configs/create index 5e607bfa9..0ab3187f7 100644 --- a/gcloud/workstations/configs/create +++ b/gcloud/workstations/configs/create @@ -25,7 +25,8 @@ SYNOPSIS [--service-account=SERVICE_ACCOUNT] [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--vm-tags=[VM_TAGS,...]] + [--shielded-vtpm] [--startup-script-uri=STARTUP_SCRIPT_URI] + [--vm-tags=[VM_TAGS,...]] [--accelerator-count=ACCELERATOR_COUNT : --accelerator-type=ACCELERATOR_TYPE] [--container-custom-image=CONTAINER_CUSTOM_IMAGE @@ -315,6 +316,15 @@ FLAGS --shielded-vtpm Default value is false. If set, instances will have vTPM enabled. + --startup-script-uri=STARTUP_SCRIPT_URI + Link to the startup script stored in Cloud Storage. The script is + executed on the workstation VM after it is booted. + + Example: + + $ gcloud workstations configs create \ + --startup-script-uri=gs://{bucket-name}/{object-name} + --vm-tags=[VM_TAGS,...] Resource manager tags to be bound to the instance. Tag keys and values have the same definition as @@ -392,30 +402,28 @@ FLAGS If set, workstations under this configuration will not have a persistent directory. - Persistent directory configuration. + --pd-disk-type=PD_DISK_TYPE; default="pd-standard" + Type of the persistent directory. PD_DISK_TYPE must be one of: + pd-standard, pd-balanced, pd-ssd. - --pd-disk-type=PD_DISK_TYPE; default="pd-standard" - Type of the persistent directory. PD_DISK_TYPE must be one of: - pd-standard, pd-balanced, pd-ssd. + --pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete" + What should happen to the disk after the Workstation is deleted. + PD_RECLAIM_POLICY must be one of: - --pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete" - What should happen to the disk after the Workstation is deleted. - PD_RECLAIM_POLICY must be one of: + delete + The persistent disk will be deleted with the Workstation. + retain + The persistent disk will be remain after the workstation is + deleted and the administrator must manually delete the disk. - delete - The persistent disk will be deleted with the Workstation. - retain - The persistent disk will be remain after the workstation is - deleted and the administrator must manually delete the disk. + At most one of these can be specified: - At most one of these can be specified: + --pd-disk-size=PD_DISK_SIZE; default=200 + Size of the persistent directory in GB. PD_DISK_SIZE must be one + of: 10, 50, 100, 200, 500, 1000. - --pd-disk-size=PD_DISK_SIZE; default=200 - Size of the persistent directory in GB. PD_DISK_SIZE must be one - of: 10, 50, 100, 200, 500, 1000. - - --pd-source-snapshot=PD_SOURCE_SNAPSHOT - Name of the snapshot to use as the source for the home disk. + --pd-source-snapshot=PD_SOURCE_SNAPSHOT + Name of the snapshot to use as the source for the home disk. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/workstations/configs/update b/gcloud/workstations/configs/update index 7bb6da46f..3d71d3635 100644 --- a/gcloud/workstations/configs/update +++ b/gcloud/workstations/configs/update @@ -21,7 +21,8 @@ SYNOPSIS [--running-timeout=RUNNING_TIMEOUT] [--service-account=SERVICE_ACCOUNT] [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--vm-tags=[VM_TAGS,...]] + [--shielded-vtpm] [--startup-script-uri=STARTUP_SCRIPT_URI] + [--vm-tags=[VM_TAGS,...]] [--accelerator-count=ACCELERATOR_COUNT : --accelerator-type=ACCELERATOR_TYPE] [--container-custom-image=CONTAINER_CUSTOM_IMAGE @@ -247,6 +248,15 @@ FLAGS --shielded-vtpm Default value is false. If set, instances will have vTPM enabled. + --startup-script-uri=STARTUP_SCRIPT_URI + Link to the startup script stored in Cloud Storage. The script is + executed on the workstation VM after it is booted. + + Example: + + $ gcloud workstations configs update \ + --startup-script-uri=gs://{bucket-name}/{object-name} + --vm-tags=[VM_TAGS,...] Resource manager tags to be bound to the instance. Tag keys and values have the same definition as @@ -327,16 +337,13 @@ FLAGS Name of the snapshot to use as the source for the persistent directory. - --pd-source-snapshot cannot be specified when --pd-disk-size or - --pd-disk-type is specified. + --pd-disk-size=PD_DISK_SIZE + Size of the persistent directory in GB. PD_DISK_SIZE must be one of: + 10, 50, 100, 200, 500, 1000. - --pd-disk-size=PD_DISK_SIZE - Size of the persistent directory in GB. PD_DISK_SIZE must be one - of: 10, 50, 100, 200, 500, 1000. - - --pd-disk-type=PD_DISK_TYPE; default="pd-standard" - Type of the persistent directory. PD_DISK_TYPE must be one of: - pd-standard, pd-balanced, pd-ssd. + --pd-disk-type=PD_DISK_TYPE; default="pd-standard" + Type of the persistent directory. PD_DISK_TYPE must be one of: + pd-standard, pd-balanced, pd-ssd. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account,