From fa40c10f6a9cb98c3a2ee951080f5a6477508291 Mon Sep 17 00:00:00 2001 From: Automated Date: Sat, 14 Jun 2025 05:31:37 +0000 Subject: [PATCH] gcloud: Sat Jun 14 05:31:37 UTC 2025 --- gcloud/_version | 10 +- gcloud/ai/endpoints/list | 14 +- gcloud/ai/help | 3 + gcloud/ai/model-garden/help | 28 ++ gcloud/ai/model-garden/models/deploy | 198 ++++++++++ gcloud/ai/model-garden/models/help | 34 ++ gcloud/ai/model-garden/models/list | 72 ++++ .../models/list-deployment-config | 68 ++++ gcloud/alloydb/clusters/create | 2 +- gcloud/alloydb/clusters/create-secondary | 2 +- gcloud/alloydb/clusters/help | 4 + gcloud/alloydb/clusters/migrate-cloud-sql | 351 ++++++++++++++++++ gcloud/alloydb/clusters/restore | 21 +- gcloud/alloydb/instances/update | 6 + gcloud/alpha/ai/endpoints/list | 2 +- gcloud/alpha/ai/model-garden/help | 4 +- gcloud/alpha/ai/model-garden/models/deploy | 4 +- gcloud/alpha/ai/model-garden/models/help | 4 +- gcloud/alpha/ai/model-garden/models/list | 4 +- .../models/list-deployment-config | 4 +- gcloud/alpha/alloydb/clusters/create | 4 +- .../alpha/alloydb/clusters/create-secondary | 2 +- gcloud/alpha/alloydb/clusters/help | 3 +- .../alpha/alloydb/clusters/migrate-cloud-sql | 14 +- gcloud/alpha/alloydb/clusters/restore | 21 +- gcloud/alpha/alloydb/instances/update | 4 +- gcloud/alpha/anthos/config/help | 3 - gcloud/alpha/anthos/config/sync/repo/describe | 89 ----- gcloud/alpha/anthos/config/sync/repo/list | 89 ----- .../alpha/anthos/config/sync/resources/list | 70 ---- gcloud/alpha/backup-dr/backups/restore/disk | 217 +++++++++++ gcloud/alpha/backup-dr/backups/restore/help | 3 + gcloud/alpha/bigtable/instances/tables/create | 2 +- gcloud/alpha/bigtable/tables/create | 2 +- .../blockchain-validator-configs/update | 18 +- .../cloud-locations/describe | 67 ++++ .../cloud-locations}/help | 18 +- .../cloudlocationfinder/cloud-locations/list | 75 ++++ .../cloud-locations/search | 88 +++++ .../config/sync => cloudlocationfinder}/help | 13 +- gcloud/alpha/compute/backend-buckets/create | 11 +- gcloud/alpha/compute/backend-buckets/delete | 13 +- gcloud/alpha/compute/backend-services/create | 9 +- gcloud/alpha/compute/backend-services/update | 9 +- gcloud/alpha/compute/disks/bulk/create | 35 +- gcloud/alpha/compute/disks/update | 12 +- gcloud/alpha/compute/help | 4 + .../compute/instance-groups/managed/create | 7 +- .../compute/instance-groups/managed/update | 11 + .../alpha/compute/instance-templates/create | 14 +- .../instance-templates/create-with-container | 27 +- gcloud/alpha/compute/instances/bulk/create | 3 +- gcloud/alpha/compute/instances/create | 7 +- .../compute/instances/create-with-container | 3 +- .../compute/instances/network-interfaces/add | 4 +- .../compute/instant-snapshot-groups/delete | 74 ++++ .../compute/instant-snapshot-groups/help | 6 + .../compute/instant-snapshot-groups/list | 96 +++++ .../configure-shaper-average-percentage | 60 +++ .../configure-strict-priority-policy | 52 +++ .../interconnects/application-awareness/help | 8 + .../attachments/dedicated/create | 8 +- .../attachments/dedicated/update | 4 +- .../interconnects/attachments/groups/update | 10 +- .../compute/interconnects/attachments/help | 3 + .../attachments/l2-forwarding/add-mapping | 73 ++++ .../attachments/l2-forwarding/create | 128 +++++++ .../l2-forwarding/describe-mapping | 59 +++ .../attachments/l2-forwarding/help | 55 +++ .../attachments/l2-forwarding/list-mapping | 107 ++++++ .../attachments/l2-forwarding/remove-mapping | 57 +++ .../attachments/l2-forwarding/update | 141 +++++++ .../attachments/l2-forwarding/update-mapping | 74 ++++ .../interconnects/attachments/partner/create | 8 +- .../interconnects/attachments/partner/update | 4 +- gcloud/alpha/compute/interconnects/create | 4 + .../interconnects/groups/create-members | 4 + .../alpha/compute/interconnects/groups/update | 11 +- .../compute/network-firewall-policies/create | 8 +- .../org-security-policies/associations/create | 4 + .../alpha/compute/preview-features/describe | 4 +- gcloud/alpha/compute/preview-features/help | 4 +- gcloud/alpha/compute/preview-features/list | 4 +- gcloud/alpha/compute/preview-features/update | 6 +- gcloud/alpha/compute/queued-resources/create | 3 +- gcloud/alpha/compute/reservations/help | 2 +- .../compute/reservations/sub-blocks/describe | 6 +- .../compute/reservations/sub-blocks/help | 13 +- .../compute/reservations/sub-blocks/list | 6 +- .../sub-blocks/perform-maintenance | 68 ++++ gcloud/alpha/compute/reservations/update | 12 +- .../resource-policies/create/workload-policy | 10 +- gcloud/alpha/compute/routers/create | 4 + gcloud/alpha/compute/security-policies/update | 11 + gcloud/alpha/compute/snapshot-groups/create | 58 +++ gcloud/alpha/compute/snapshot-groups/delete | 36 ++ gcloud/alpha/compute/snapshot-groups/describe | 29 ++ gcloud/alpha/compute/snapshot-groups/help | 36 ++ gcloud/alpha/compute/snapshot-groups/list | 68 ++++ gcloud/alpha/config/get | 11 +- gcloud/alpha/config/help | 11 +- gcloud/alpha/config/list | 11 +- gcloud/alpha/config/set | 11 +- gcloud/alpha/config/unset | 11 +- gcloud/alpha/container/ai/help | 3 + .../container/ai/profiles/accelerators/help | 28 ++ .../container/ai/profiles/accelerators/list | 97 +++++ gcloud/alpha/container/ai/profiles/help | 51 +++ .../container/ai/profiles/manifests/create | 70 ++++ .../container/ai/profiles/manifests/help | 28 ++ .../model-and-server-combinations/help | 29 ++ .../model-and-server-combinations/list | 72 ++++ .../ai/profiles/model-server-versions/help | 29 ++ .../ai/profiles/model-server-versions/list | 70 ++++ .../container/ai/profiles/model-servers/help | 28 ++ .../container/ai/profiles/model-servers/list | 64 ++++ .../ai/profiles/models}/help | 10 +- .../alpha/container/ai/profiles/models/list | 57 +++ .../backup-restore/backup-channels/create | 8 +- .../backup-restore/restore-channels/create | 9 +- .../clusters/check-autopilot-compatibility | 7 + gcloud/alpha/container/clusters/create | 38 ++ gcloud/alpha/container/clusters/create-auto | 21 +- gcloud/alpha/container/clusters/update | 33 +- gcloud/alpha/container/fleet/packages/create | 4 +- gcloud/alpha/container/fleet/packages/delete | 4 +- .../alpha/container/fleet/packages/describe | 4 +- gcloud/alpha/container/fleet/packages/help | 4 +- gcloud/alpha/container/fleet/packages/list | 4 +- .../fleet/packages/resource-bundles/create | 4 +- .../fleet/packages/resource-bundles/delete | 4 +- .../fleet/packages/resource-bundles/describe | 4 +- .../fleet/packages/resource-bundles/help | 4 +- .../fleet/packages/resource-bundles/list | 4 +- .../packages/resource-bundles/releases/create | 5 +- .../packages/resource-bundles/releases/delete | 5 +- .../resource-bundles/releases/describe | 5 +- .../packages/resource-bundles/releases/help | 4 +- .../packages/resource-bundles/releases/list | 4 +- .../packages/resource-bundles/releases/update | 36 +- .../fleet/packages/resource-bundles/update | 4 +- .../container/fleet/packages/rollouts/abort | 4 +- .../fleet/packages/rollouts/describe | 4 +- .../container/fleet/packages/rollouts/help | 4 +- .../container/fleet/packages/rollouts/list | 4 +- .../container/fleet/packages/rollouts/resume | 4 +- .../container/fleet/packages/rollouts/suspend | 4 +- gcloud/alpha/container/fleet/packages/update | 4 +- .../fleet/rbacrolebindingactuation/describe | 6 +- .../fleet/rbacrolebindingactuation/help | 6 +- .../fleet/rbacrolebindingactuation/update | 8 +- .../fleet/scopes/rbacrolebindings/create | 7 + .../fleet/scopes/rbacrolebindings/update | 6 + gcloud/alpha/container/hub/packages/create | 4 +- gcloud/alpha/container/hub/packages/delete | 4 +- gcloud/alpha/container/hub/packages/describe | 4 +- gcloud/alpha/container/hub/packages/help | 4 +- gcloud/alpha/container/hub/packages/list | 4 +- .../hub/packages/resource-bundles/create | 4 +- .../hub/packages/resource-bundles/delete | 4 +- .../hub/packages/resource-bundles/describe | 4 +- .../hub/packages/resource-bundles/help | 4 +- .../hub/packages/resource-bundles/list | 4 +- .../packages/resource-bundles/releases/create | 4 +- .../packages/resource-bundles/releases/delete | 4 +- .../resource-bundles/releases/describe | 5 +- .../packages/resource-bundles/releases/help | 4 +- .../packages/resource-bundles/releases/list | 4 +- .../packages/resource-bundles/releases/update | 35 +- .../hub/packages/resource-bundles/update | 4 +- .../container/hub/packages/rollouts/abort | 4 +- .../container/hub/packages/rollouts/describe | 4 +- .../container/hub/packages/rollouts/help | 4 +- .../container/hub/packages/rollouts/list | 4 +- .../container/hub/packages/rollouts/resume | 4 +- .../container/hub/packages/rollouts/suspend | 4 +- gcloud/alpha/container/hub/packages/update | 4 +- .../hub/rbacrolebindingactuation/describe | 6 +- .../hub/rbacrolebindingactuation/help | 6 +- .../hub/rbacrolebindingactuation/update | 8 +- .../hub/scopes/rbacrolebindings/create | 7 + .../hub/scopes/rbacrolebindings/update | 6 + gcloud/alpha/container/node-pools/create | 14 + .../dataplex/datascans/create/data-discovery | 4 +- .../dataplex/datascans/update/data-discovery | 4 +- .../entry-groups/add-iam-policy-binding | 2 +- gcloud/alpha/dataplex/entry-groups/create | 2 +- .../entry-groups/remove-iam-policy-binding | 2 +- .../dataplex/entry-groups/set-iam-policy | 2 +- gcloud/alpha/dataplex/entry-groups/update | 2 +- gcloud/alpha/dataplex/entry-links/create | 106 ++++++ gcloud/alpha/dataplex/entry-links/delete | 77 ++++ gcloud/alpha/dataplex/entry-links/describe | 81 ++++ gcloud/alpha/dataplex/entry-links/help | 33 ++ gcloud/alpha/dataplex/help | 3 + gcloud/alpha/dataplex/metadata-jobs/cancel | 4 +- gcloud/alpha/dataplex/metadata-jobs/create | 20 +- gcloud/alpha/dataplex/metadata-jobs/describe | 4 +- gcloud/alpha/dataplex/metadata-jobs/help | 4 +- gcloud/alpha/dataplex/metadata-jobs/list | 4 +- gcloud/alpha/dataproc/clusters/create | 25 +- gcloud/alpha/dataproc/clusters/update | 33 +- .../workflow-templates/set-managed-cluster | 5 +- .../account-connectors/update | 37 +- .../developer-connect/connections/update | 37 +- gcloud/alpha/developer-connect/help | 3 + .../developer-connect/insights-configs/create | 91 +++++ .../developer-connect/insights-configs/delete | 100 +++++ .../insights-configs/describe | 71 ++++ .../developer-connect/insights-configs/help | 44 +++ .../insights-configs}/list | 53 +-- .../developer-connect/insights-configs/update | 99 +++++ gcloud/alpha/dns/policies/update | 7 +- .../edge-cloud/container/clusters/create | 5 + gcloud/alpha/firebase/test/android/run | 2 +- gcloud/alpha/firestore/databases/create | 2 +- .../alpha/firestore/indexes/composite/create | 2 +- .../annotation-stores/add-iam-policy-binding | 147 -------- .../alpha/healthcare/annotation-stores/create | 79 ---- .../alpha/healthcare/annotation-stores/delete | 79 ---- .../healthcare/annotation-stores/describe | 79 ---- .../healthcare/annotation-stores/evaluate/bq | 114 ------ .../annotation-stores/evaluate/help | 31 -- .../healthcare/annotation-stores/export/bq | 105 ------ .../healthcare/annotation-stores/export/gcs | 94 ----- .../healthcare/annotation-stores/export/help | 34 -- .../annotation-stores/get-iam-policy | 108 ------ .../alpha/healthcare/annotation-stores/help | 69 ---- .../healthcare/annotation-stores/import/gcs | 95 ----- .../healthcare/annotation-stores/import/help | 31 -- .../remove-iam-policy-binding | 154 -------- .../annotation-stores/set-iam-policy | 90 ----- .../alpha/healthcare/annotation-stores/update | 79 ---- gcloud/alpha/healthcare/datasets/deidentify | 15 +- .../alpha/healthcare/dicom-stores/deidentify | 13 +- .../alpha/healthcare/fhir-stores/deidentify | 13 +- gcloud/alpha/healthcare/help | 3 - .../iam/workforce-pools/providers/create-oidc | 7 +- .../iam/workforce-pools/providers/update-oidc | 10 +- gcloud/alpha/iap/settings/get | 12 + gcloud/alpha/iap/settings/set | 74 ++-- gcloud/alpha/kms/keys/create | 3 +- gcloud/alpha/kms/keys/update | 3 +- gcloud/alpha/kms/keys/versions/import | 3 +- gcloud/alpha/logging/logs/delete | 10 +- gcloud/alpha/logging/logs/help | 3 +- gcloud/alpha/logging/operations/list | 48 ++- gcloud/alpha/lustre/instances/create | 24 +- gcloud/alpha/lustre/instances/export-data | 9 +- gcloud/alpha/lustre/instances/import-data | 8 +- gcloud/alpha/lustre/instances/update | 24 +- gcloud/alpha/managed-kafka/clusters/create | 31 +- gcloud/alpha/managed-kafka/clusters/update | 35 +- .../managed-kafka/schema-registries/create | 4 +- .../managed-kafka/schema-registries/delete | 4 +- .../managed-kafka/schema-registries/describe | 30 +- .../managed-kafka/schema-registries/help | 18 +- .../managed-kafka/schema-registries/list | 4 +- .../schema-registries/subject/describe | 80 ++++ .../schema-registries/subject/help | 31 ++ .../schema-registries/subject/update | 93 +++++ .../managed-kafka/schema-registries/update | 77 ++++ gcloud/alpha/memorystore/instances/update | 37 +- gcloud/alpha/model-armor/floorsettings/update | 6 +- gcloud/alpha/model-armor/templates/update | 18 +- gcloud/alpha/netapp/storage-pools/create | 12 +- gcloud/alpha/netapp/storage-pools/update | 17 +- .../alpha/network-services/operations/cancel | 6 +- .../network-services/operations/describe | 6 +- gcloud/alpha/network-services/operations/help | 6 +- gcloud/alpha/network-services/operations/list | 6 +- gcloud/alpha/network-services/operations/wait | 6 +- .../alpha/resource-manager/tags/keys/create | 6 +- .../alpha/resource-manager/tags/keys/update | 10 +- gcloud/alpha/run/worker-pools/help | 4 + gcloud/alpha/run/worker-pools/replace | 46 +++ gcloud/alpha/scc/iac-validation-reports/list | 35 +- gcloud/alpha/scc/manage/services/describe | 10 + gcloud/alpha/scc/manage/services/update | 10 + gcloud/alpha/scc/posture-deployments/list | 34 +- gcloud/alpha/scc/posture-templates/list | 7 +- gcloud/alpha/scheduler/jobs/create/app-engine | 37 +- gcloud/alpha/scheduler/jobs/create/http | 37 +- gcloud/alpha/scheduler/jobs/create/pubsub | 37 +- gcloud/alpha/scheduler/jobs/update/app-engine | 39 +- gcloud/alpha/scheduler/jobs/update/http | 39 +- gcloud/alpha/scheduler/jobs/update/pubsub | 39 +- gcloud/alpha/spanner/databases/help | 3 + gcloud/alpha/spanner/databases/import | 72 ++++ gcloud/alpha/spanner/databases/update | 24 +- gcloud/alpha/spanner/operations/describe | 4 +- gcloud/alpha/sql/backups/restore | 10 +- gcloud/alpha/sql/instances/clone | 32 +- gcloud/alpha/sql/instances/create | 10 +- .../sql/instances/get-latest-recovery-time | 5 + gcloud/alpha/sql/instances/patch | 17 +- gcloud/alpha/sql/users/create | 8 +- gcloud/alpha/sql/users/set-password-policy | 8 +- gcloud/alpha/storage/rm | 9 +- gcloud/alpha/workstations/configs/create | 88 +++-- gcloud/beta/ai/endpoints/list | 2 +- gcloud/beta/ai/model-garden/help | 6 +- gcloud/beta/ai/model-garden/models/deploy | 6 +- gcloud/beta/ai/model-garden/models/help | 6 +- gcloud/beta/ai/model-garden/models/list | 6 +- .../models/list-deployment-config | 6 +- gcloud/beta/alloydb/clusters/create | 4 +- gcloud/beta/alloydb/clusters/create-secondary | 2 +- gcloud/beta/alloydb/clusters/help | 3 +- .../beta/alloydb/clusters/migrate-cloud-sql | 16 +- gcloud/beta/alloydb/clusters/restore | 21 +- gcloud/beta/alloydb/instances/update | 8 +- gcloud/beta/bigtable/instances/tables/create | 2 +- gcloud/beta/bigtable/tables/create | 2 +- gcloud/beta/colab/runtime-templates/create | 25 +- gcloud/beta/compute/backend-services/create | 49 ++- gcloud/beta/compute/backend-services/update | 49 ++- gcloud/beta/compute/commitments/create | 2 +- gcloud/beta/compute/help | 3 + .../compute/instance-groups/managed/create | 7 +- .../compute/instance-groups/managed/update | 11 + gcloud/beta/compute/instance-templates/create | 13 +- .../instance-templates/create-with-container | 27 +- gcloud/beta/compute/instances/bulk/create | 3 +- gcloud/beta/compute/instances/create | 7 +- .../compute/instances/create-with-container | 3 +- .../compute/instances/network-interfaces/add | 4 +- .../attachments/dedicated/create | 24 ++ .../attachments/dedicated/update | 15 +- .../interconnects/attachments/groups/update | 10 +- .../interconnects/attachments/partner/create | 24 ++ .../interconnects/attachments/partner/update | 12 + gcloud/beta/compute/interconnects/create | 4 + .../interconnects/groups/create-members | 4 + .../beta/compute/interconnects/groups/update | 11 +- .../compute/network-firewall-policies/create | 8 +- .../org-security-policies/associations/create | 4 + gcloud/beta/compute/preview-features/describe | 54 +++ gcloud/beta/compute/preview-features/help | 33 ++ gcloud/beta/compute/preview-features/list | 66 ++++ gcloud/beta/compute/preview-features/update | 73 ++++ gcloud/beta/compute/reservations/help | 3 + .../compute/reservations/sub-blocks/describe | 69 ++++ .../beta/compute/reservations/sub-blocks/help | 32 ++ .../beta/compute/reservations/sub-blocks/list | 106 ++++++ .../resource-policies/create/workload-policy | 12 +- gcloud/beta/compute/routers/create | 12 +- gcloud/beta/compute/vpn-tunnels/create | 33 +- gcloud/beta/config/get | 11 +- gcloud/beta/config/help | 11 +- gcloud/beta/config/list | 11 +- gcloud/beta/config/set | 11 +- gcloud/beta/config/unset | 11 +- .../backup-restore/backup-channels/create | 8 +- .../backup-restore/restore-channels/create | 9 +- .../clusters/check-autopilot-compatibility | 7 + gcloud/beta/container/clusters/create | 38 ++ gcloud/beta/container/clusters/create-auto | 21 +- gcloud/beta/container/clusters/update | 33 +- gcloud/beta/container/fleet/help | 6 + gcloud/beta/container/fleet/packages/create | 43 +++ gcloud/beta/container/fleet/packages/delete | 68 ++++ gcloud/beta/container/fleet/packages/describe | 68 ++++ gcloud/beta/container/fleet/packages/help | 47 +++ gcloud/beta/container/fleet/packages/list | 67 ++++ .../fleet/packages/resource-bundles/create | 43 +++ .../fleet/packages/resource-bundles/delete | 43 +++ .../fleet/packages/resource-bundles/describe | 39 ++ .../fleet/packages/resource-bundles/help | 47 +++ .../fleet/packages/resource-bundles/list | 69 ++++ .../packages/resource-bundles/releases/create | 73 ++++ .../packages/resource-bundles/releases/delete | 50 +++ .../resource-bundles/releases/describe | 46 +++ .../packages/resource-bundles/releases/help | 41 ++ .../packages/resource-bundles/releases/list | 74 ++++ .../packages/resource-bundles/releases/update | 49 +++ .../fleet/packages/resource-bundles/update | 43 +++ .../container/fleet/packages/rollouts/abort | 74 ++++ .../fleet/packages/rollouts/describe | 47 +++ .../container/fleet/packages/rollouts/help | 40 ++ .../container/fleet/packages/rollouts/list | 77 ++++ .../container/fleet/packages/rollouts/resume | 74 ++++ .../container/fleet/packages/rollouts/suspend | 74 ++++ gcloud/beta/container/fleet/packages/update | 68 ++++ .../fleet/rbacrolebindingactuation/describe | 24 ++ .../fleet/rbacrolebindingactuation/help | 34 ++ .../fleet/rbacrolebindingactuation/update | 55 +++ .../fleet/scopes/rbacrolebindings/create | 24 +- .../fleet/scopes/rbacrolebindings/update | 24 +- gcloud/beta/container/hub/help | 6 + gcloud/beta/container/hub/packages/create | 43 +++ gcloud/beta/container/hub/packages/delete | 68 ++++ gcloud/beta/container/hub/packages/describe | 68 ++++ gcloud/beta/container/hub/packages/help | 47 +++ gcloud/beta/container/hub/packages/list | 67 ++++ .../hub/packages/resource-bundles/create | 43 +++ .../hub/packages/resource-bundles/delete | 43 +++ .../hub/packages/resource-bundles/describe | 39 ++ .../hub/packages/resource-bundles/help | 47 +++ .../hub/packages/resource-bundles/list | 69 ++++ .../packages/resource-bundles/releases/create | 73 ++++ .../packages/resource-bundles/releases/delete | 50 +++ .../resource-bundles/releases/describe | 46 +++ .../packages/resource-bundles/releases/help | 41 ++ .../packages/resource-bundles/releases/list | 73 ++++ .../packages/resource-bundles/releases/update | 49 +++ .../hub/packages/resource-bundles/update | 43 +++ .../container/hub/packages/rollouts/abort | 73 ++++ .../container/hub/packages/rollouts/describe | 47 +++ .../beta/container/hub/packages/rollouts/help | 39 ++ .../beta/container/hub/packages/rollouts/list | 77 ++++ .../container/hub/packages/rollouts/resume | 74 ++++ .../container/hub/packages/rollouts/suspend | 74 ++++ gcloud/beta/container/hub/packages/update | 68 ++++ .../hub/rbacrolebindingactuation/describe | 24 ++ .../hub/rbacrolebindingactuation/help | 34 ++ .../hub/rbacrolebindingactuation/update | 55 +++ .../hub/scopes/rbacrolebindings/create | 24 +- .../hub/scopes/rbacrolebindings/update | 24 +- gcloud/beta/container/node-pools/create | 14 + gcloud/beta/dataproc/clusters/create | 25 +- gcloud/beta/dataproc/clusters/update | 33 +- .../workflow-templates/set-managed-cluster | 5 +- .../datastream/connection-profiles/create | 9 +- .../datastream/connection-profiles/update | 11 +- .../beta/developer-connect/connections/update | 37 +- gcloud/beta/developer-connect/help | 3 + .../developer-connect/insights-configs/create | 89 +++++ .../developer-connect/insights-configs/delete | 98 +++++ .../insights-configs/describe | 69 ++++ .../developer-connect/insights-configs/help | 42 +++ .../developer-connect/insights-configs/list | 88 +++++ .../developer-connect/insights-configs/update | 97 +++++ gcloud/beta/dns/policies/update | 7 +- gcloud/beta/eventarc/pipelines/create | 15 +- gcloud/beta/eventarc/pipelines/update | 15 +- gcloud/beta/firebase/test/android/run | 2 +- gcloud/beta/firestore/databases/create | 2 +- .../beta/firestore/indexes/composite/create | 2 +- .../annotation-stores/add-iam-policy-binding | 145 -------- .../beta/healthcare/annotation-stores/create | 77 ---- .../beta/healthcare/annotation-stores/delete | 77 ---- .../healthcare/annotation-stores/describe | 77 ---- .../healthcare/annotation-stores/evaluate/bq | 112 ------ .../annotation-stores/evaluate/help | 29 -- .../healthcare/annotation-stores/export/bq | 103 ----- .../healthcare/annotation-stores/export/gcs | 92 ----- .../healthcare/annotation-stores/export/help | 32 -- gcloud/beta/healthcare/annotation-stores/help | 67 ---- .../healthcare/annotation-stores/import/gcs | 93 ----- .../healthcare/annotation-stores/import/help | 29 -- .../remove-iam-policy-binding | 151 -------- .../annotation-stores/set-iam-policy | 88 ----- .../beta/healthcare/annotation-stores/update | 77 ---- gcloud/beta/healthcare/datasets/deidentify | 15 +- .../beta/healthcare/dicom-stores/deidentify | 13 +- gcloud/beta/healthcare/fhir-stores/deidentify | 13 +- gcloud/beta/healthcare/help | 3 - gcloud/beta/iam/policy-bindings/create | 63 +++- gcloud/beta/iam/policy-bindings/update | 32 +- .../principal-access-boundary-policies/create | 15 +- .../principal-access-boundary-policies/delete | 4 +- .../principal-access-boundary-policies/update | 55 ++- .../iam/workforce-pools/providers/create-oidc | 7 +- .../iam/workforce-pools/providers/update-oidc | 10 +- gcloud/beta/iap/settings/get | 12 + gcloud/beta/iap/settings/set | 72 ++-- gcloud/beta/kms/keys/create | 3 +- gcloud/beta/kms/keys/update | 3 +- gcloud/beta/kms/keys/versions/import | 3 +- gcloud/beta/logging/logs/delete | 10 +- gcloud/beta/logging/logs/help | 2 +- gcloud/beta/logging/operations/list | 48 ++- gcloud/beta/managed-kafka/help | 3 + .../managed-kafka/schema-registries/create | 71 ++++ .../managed-kafka/schema-registries/delete | 72 ++++ .../managed-kafka/schema-registries/describe | 64 ++++ .../beta/managed-kafka/schema-registries/help | 37 ++ .../schema-registries/list} | 65 ++-- gcloud/beta/memorystore/instances/update | 37 +- gcloud/beta/netapp/backup-vaults/create | 19 +- gcloud/beta/netapp/backup-vaults/update | 13 + gcloud/beta/netapp/storage-pools/create | 12 +- gcloud/beta/netapp/storage-pools/update | 17 +- gcloud/beta/network-connectivity/help | 5 +- .../spokes/gateways/advertised-routes/create | 100 +++++ .../spokes/gateways/advertised-routes/delete | 82 ++++ .../gateways/advertised-routes/describe | 76 ++++ .../spokes/gateways/advertised-routes/help | 34 ++ .../spokes/gateways/advertised-routes/list | 105 ++++++ .../spokes/gateways/create | 115 ++++++ .../network-connectivity/spokes/gateways/help | 33 ++ .../spokes/gateways/update | 108 ++++++ gcloud/beta/network-connectivity/spokes/help | 3 + .../vpc-flow-logs-configs/create | 77 ++-- .../vpc-flow-logs-configs/delete | 28 +- .../vpc-flow-logs-configs/describe | 30 +- .../vpc-flow-logs-configs/help | 11 +- .../vpc-flow-logs-configs/list | 46 ++- .../query-org-vpc-flow-logs-configs | 83 +++++ .../vpc-flow-logs-configs/update | 77 +++- gcloud/beta/network-security/help | 3 + .../secure-access-connect/attachments/create | 102 +++++ .../secure-access-connect/attachments/delete | 70 ++++ .../attachments/describe | 65 ++++ .../secure-access-connect/attachments/help | 34 ++ .../secure-access-connect/attachments/list | 78 ++++ .../secure-access-connect/help | 28 ++ .../secure-access-connect/realms/create | 77 ++++ .../secure-access-connect/realms/delete | 68 ++++ .../secure-access-connect/realms/describe | 64 ++++ .../secure-access-connect/realms/help | 34 ++ .../secure-access-connect/realms/list | 78 ++++ gcloud/beta/network-services/help | 3 + .../beta/network-services/operations/cancel | 68 ++++ .../beta/network-services/operations/describe | 68 ++++ gcloud/beta/network-services/operations/help | 38 ++ .../operations}/list | 52 +-- gcloud/beta/network-services/operations/wait | 67 ++++ gcloud/beta/resource-manager/tags/keys/create | 6 +- gcloud/beta/resource-manager/tags/keys/update | 10 +- gcloud/beta/saas-runtime/releases/update | 18 +- gcloud/beta/saas-runtime/rollout-kinds/update | 18 +- gcloud/beta/saas-runtime/rollouts/update | 18 +- gcloud/beta/saas-runtime/saas/update | 18 +- gcloud/beta/saas-runtime/tenants/update | 18 +- gcloud/beta/saas-runtime/unit-kinds/update | 18 +- .../beta/saas-runtime/unit-operations/update | 18 +- gcloud/beta/saas-runtime/units/update | 18 +- gcloud/beta/scheduler/jobs/create/app-engine | 37 +- gcloud/beta/scheduler/jobs/create/http | 37 +- gcloud/beta/scheduler/jobs/create/pubsub | 37 +- gcloud/beta/scheduler/jobs/update/app-engine | 39 +- gcloud/beta/scheduler/jobs/update/http | 39 +- gcloud/beta/scheduler/jobs/update/pubsub | 39 +- gcloud/beta/service-extensions/help | 3 + .../lb-edge-extensions/delete | 70 ++++ .../lb-edge-extensions/describe | 65 ++++ .../lb-edge-extensions/help | 34 ++ .../lb-edge-extensions/import | 82 ++++ .../lb-edge-extensions/list | 85 +++++ gcloud/beta/spanner/databases/update | 24 +- gcloud/beta/spanner/operations/describe | 4 +- gcloud/beta/sql/backups/restore | 10 +- gcloud/beta/sql/instances/clone | 27 +- gcloud/beta/sql/instances/create | 10 +- .../sql/instances/get-latest-recovery-time | 5 + gcloud/beta/sql/instances/patch | 17 +- gcloud/beta/sql/users/create | 8 +- gcloud/beta/sql/users/set-password-policy | 8 +- gcloud/beta/workstations/configs/create | 88 +++-- gcloud/bigtable/instances/tables/create | 2 +- gcloud/bigtable/tables/create | 2 +- gcloud/colab/runtime-templates/create | 25 +- gcloud/compute/backend-buckets/create | 9 +- gcloud/compute/backend-services/create | 9 +- gcloud/compute/backend-services/update | 9 +- gcloud/compute/commitments/create | 2 +- gcloud/compute/instance-groups/managed/create | 7 +- gcloud/compute/instance-groups/managed/update | 11 + gcloud/compute/instance-templates/create | 3 +- .../instance-templates/create-with-container | 24 +- gcloud/compute/instances/bulk/create | 3 +- gcloud/compute/instances/create | 3 +- .../compute/instances/create-with-container | 3 +- .../interconnects/attachments/groups/update | 10 +- gcloud/compute/interconnects/create | 4 + .../interconnects/groups/create-members | 4 + gcloud/compute/interconnects/groups/update | 11 +- gcloud/compute/reservations/help | 3 + .../compute/reservations/sub-blocks/describe | 68 ++++ gcloud/compute/reservations/sub-blocks/help | 31 ++ gcloud/compute/reservations/sub-blocks/list | 104 ++++++ .../resource-policies/create/group-placement | 7 +- gcloud/compute/resource-policies/create/help | 3 + .../resource-policies/create/workload-policy | 100 +++++ gcloud/config/get | 11 +- gcloud/config/help | 11 +- gcloud/config/list | 11 +- gcloud/config/set | 11 +- gcloud/config/unset | 11 +- .../clusters/check-autopilot-compatibility | 7 + gcloud/container/clusters/create | 42 ++- gcloud/container/clusters/create-auto | 21 +- gcloud/container/clusters/update | 33 +- gcloud/container/fleet/help | 3 + .../fleet/rbacrolebindingactuation/describe | 23 ++ .../fleet/rbacrolebindingactuation/help | 33 ++ .../fleet/rbacrolebindingactuation/update | 54 +++ .../fleet/scopes/rbacrolebindings/create | 24 +- .../fleet/scopes/rbacrolebindings/update | 24 +- gcloud/container/hub/help | 3 + .../hub/rbacrolebindingactuation/describe | 23 ++ .../hub/rbacrolebindingactuation/help | 33 ++ .../hub/rbacrolebindingactuation/update | 54 +++ .../hub/scopes/rbacrolebindings/create | 24 +- .../hub/scopes/rbacrolebindings/update | 24 +- gcloud/container/node-pools/create | 14 + .../connection-profiles/create/alloydb | 2 +- .../connection-profiles/create/sqlserver | 8 +- .../conversion-workspaces/create | 19 +- .../conversion-workspaces/update | 9 +- .../database-migration/migration-jobs/restart | 2 + .../dataplex/datascans/create/data-discovery | 210 +++++++++++ gcloud/dataplex/datascans/create/help | 3 + .../dataplex/datascans/update/data-discovery | 193 ++++++++++ gcloud/dataplex/datascans/update/help | 3 + .../entry-groups/add-iam-policy-binding | 2 +- gcloud/dataplex/entry-groups/create | 2 +- .../entry-groups/remove-iam-policy-binding | 2 +- gcloud/dataplex/entry-groups/set-iam-policy | 2 +- gcloud/dataplex/entry-groups/update | 2 +- gcloud/dataplex/help | 3 + gcloud/dataplex/metadata-jobs/cancel | 67 ++++ gcloud/dataplex/metadata-jobs/create | 269 ++++++++++++++ gcloud/dataplex/metadata-jobs/describe | 68 ++++ gcloud/dataplex/metadata-jobs/help | 34 ++ gcloud/dataplex/metadata-jobs/list | 86 +++++ gcloud/dataproc/clusters/create | 25 +- gcloud/dataproc/clusters/update | 33 +- .../workflow-templates/set-managed-cluster | 5 +- gcloud/datastream/connection-profiles/create | 9 +- gcloud/datastream/connection-profiles/update | 11 +- gcloud/developer-connect/connections/update | 37 +- gcloud/developer-connect/help | 3 + .../developer-connect/insights-configs/create | 87 +++++ .../developer-connect/insights-configs/delete | 96 +++++ .../insights-configs/describe | 68 ++++ .../developer-connect/insights-configs/help | 40 ++ .../developer-connect/insights-configs/list | 87 +++++ .../developer-connect/insights-configs/update | 96 +++++ gcloud/dns/policies/create | 10 +- gcloud/dns/policies/update | 10 +- gcloud/filestore/instances/create | 17 +- gcloud/firebase/test/android/run | 2 +- gcloud/firestore/databases/create | 2 +- gcloud/firestore/indexes/composite/create | 2 +- .../repository-groups/update | 18 +- gcloud/gemini/code-repository-indexes/update | 18 +- .../setting-bindings/update | 18 +- gcloud/gemini/code-tools-settings/update | 18 +- .../setting-bindings/update | 18 +- .../data-sharing-with-google-settings/update | 18 +- .../gemini-gcp-enablement-settings/create | 8 +- .../setting-bindings/update | 18 +- .../gemini-gcp-enablement-settings/update | 25 +- .../logging-settings/setting-bindings/update | 18 +- gcloud/gemini/logging-settings/update | 18 +- .../setting-bindings/update | 18 +- gcloud/gemini/release-channel-settings/update | 18 +- gcloud/iam/policy-bindings/update | 19 +- .../principal-access-boundary-policies/update | 19 +- .../iam/workforce-pools/providers/create-oidc | 7 +- .../iam/workforce-pools/providers/create-saml | 8 +- .../iam/workforce-pools/providers/update-oidc | 10 +- .../iam/workforce-pools/providers/update-saml | 7 +- gcloud/iam/workload-identity-pools/create | 4 +- gcloud/iam/workload-identity-pools/update | 4 +- gcloud/kms/keys/create | 3 +- gcloud/kms/keys/update | 3 +- gcloud/kms/keys/versions/import | 3 +- gcloud/logging/logs/delete | 12 +- gcloud/logging/logs/help | 2 +- gcloud/logging/operations/list | 48 ++- gcloud/lustre/instances/update | 18 +- gcloud/memorystore/instances/update | 37 +- gcloud/model-armor/floorsettings/update | 6 +- gcloud/model-armor/templates/update | 18 +- gcloud/netapp/backup-vaults/create | 16 +- gcloud/netapp/backup-vaults/update | 16 +- gcloud/netapp/storage-pools/create | 16 +- gcloud/netapp/storage-pools/update | 10 +- .../internal-ranges/create | 43 ++- .../policy-based-routes/create | 2 +- .../vpc-flow-logs-configs/update | 18 +- gcloud/network-services/help | 3 + gcloud/network-services/operations/cancel | 67 ++++ gcloud/network-services/operations/describe | 67 ++++ gcloud/network-services/operations/help | 36 ++ gcloud/network-services/operations/list | 88 +++++ gcloud/network-services/operations/wait | 66 ++++ gcloud/observability/help | 19 + gcloud/observability/scopes/describe | 61 +++ gcloud/observability/scopes/help | 22 ++ gcloud/observability/scopes/update | 67 ++++ gcloud/parametermanager/parameters/update | 18 +- gcloud/privateca/certificates/create | 2 +- gcloud/resource-manager/tags/keys/update | 4 +- gcloud/run/services/add-iam-policy-binding | 42 ++- gcloud/run/services/remove-iam-policy-binding | 46 ++- gcloud/scc/iac-validation-reports/list | 40 +- gcloud/scc/manage/services/describe | 10 + gcloud/scc/manage/services/update | 10 + gcloud/scc/posture-deployments/list | 34 +- gcloud/scc/posture-templates/list | 7 +- gcloud/scheduler/jobs/create/app-engine | 37 +- gcloud/scheduler/jobs/create/http | 37 +- gcloud/scheduler/jobs/create/pubsub | 37 +- gcloud/scheduler/jobs/update/app-engine | 39 +- gcloud/scheduler/jobs/update/http | 39 +- gcloud/scheduler/jobs/update/pubsub | 39 +- gcloud/spanner/databases/update | 22 +- gcloud/spanner/operations/describe | 12 +- gcloud/sql/backups/restore | 10 +- gcloud/sql/instances/clone | 16 +- gcloud/sql/instances/create | 10 +- gcloud/sql/instances/get-latest-recovery-time | 5 + gcloud/sql/instances/patch | 10 +- gcloud/sql/users/create | 8 +- gcloud/sql/users/set-password-policy | 8 +- gcloud/storage/rm | 9 +- gcloud/workstations/configs/create | 88 +++-- 712 files changed, 17386 insertions(+), 4918 deletions(-) create mode 100644 gcloud/ai/model-garden/help create mode 100644 gcloud/ai/model-garden/models/deploy create mode 100644 gcloud/ai/model-garden/models/help create mode 100644 gcloud/ai/model-garden/models/list create mode 100644 gcloud/ai/model-garden/models/list-deployment-config create mode 100644 gcloud/alloydb/clusters/migrate-cloud-sql delete mode 100644 gcloud/alpha/anthos/config/sync/repo/describe delete mode 100644 gcloud/alpha/anthos/config/sync/repo/list delete mode 100644 gcloud/alpha/anthos/config/sync/resources/list create mode 100644 gcloud/alpha/backup-dr/backups/restore/disk create mode 100644 gcloud/alpha/cloudlocationfinder/cloud-locations/describe rename gcloud/alpha/{anthos/config/sync/repo => cloudlocationfinder/cloud-locations}/help (54%) create mode 100644 gcloud/alpha/cloudlocationfinder/cloud-locations/list create mode 100644 gcloud/alpha/cloudlocationfinder/cloud-locations/search rename gcloud/alpha/{anthos/config/sync => cloudlocationfinder}/help (58%) create mode 100644 gcloud/alpha/compute/instant-snapshot-groups/delete create mode 100644 gcloud/alpha/compute/instant-snapshot-groups/list create mode 100644 gcloud/alpha/compute/interconnects/application-awareness/configure-shaper-average-percentage create mode 100644 gcloud/alpha/compute/interconnects/application-awareness/configure-strict-priority-policy create mode 100644 gcloud/alpha/compute/interconnects/attachments/l2-forwarding/add-mapping create mode 100644 gcloud/alpha/compute/interconnects/attachments/l2-forwarding/create create mode 100644 gcloud/alpha/compute/interconnects/attachments/l2-forwarding/describe-mapping create mode 100644 gcloud/alpha/compute/interconnects/attachments/l2-forwarding/help create mode 100644 gcloud/alpha/compute/interconnects/attachments/l2-forwarding/list-mapping create mode 100644 gcloud/alpha/compute/interconnects/attachments/l2-forwarding/remove-mapping create mode 100644 gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update create mode 100644 gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update-mapping create mode 100644 gcloud/alpha/compute/reservations/sub-blocks/perform-maintenance create mode 100644 gcloud/alpha/compute/snapshot-groups/create create mode 100644 gcloud/alpha/compute/snapshot-groups/delete create mode 100644 gcloud/alpha/compute/snapshot-groups/describe create mode 100644 gcloud/alpha/compute/snapshot-groups/help create mode 100644 gcloud/alpha/compute/snapshot-groups/list create mode 100644 gcloud/alpha/container/ai/profiles/accelerators/help create mode 100644 gcloud/alpha/container/ai/profiles/accelerators/list create mode 100644 gcloud/alpha/container/ai/profiles/help create mode 100644 gcloud/alpha/container/ai/profiles/manifests/create create mode 100644 gcloud/alpha/container/ai/profiles/manifests/help create mode 100644 gcloud/alpha/container/ai/profiles/model-and-server-combinations/help create mode 100644 gcloud/alpha/container/ai/profiles/model-and-server-combinations/list create mode 100644 gcloud/alpha/container/ai/profiles/model-server-versions/help create mode 100644 gcloud/alpha/container/ai/profiles/model-server-versions/list create mode 100644 gcloud/alpha/container/ai/profiles/model-servers/help create mode 100644 gcloud/alpha/container/ai/profiles/model-servers/list rename gcloud/alpha/{anthos/config/sync/resources => container/ai/profiles/models}/help (61%) create mode 100644 gcloud/alpha/container/ai/profiles/models/list create mode 100644 gcloud/alpha/dataplex/entry-links/create create mode 100644 gcloud/alpha/dataplex/entry-links/delete create mode 100644 gcloud/alpha/dataplex/entry-links/describe create mode 100644 gcloud/alpha/dataplex/entry-links/help create mode 100644 gcloud/alpha/developer-connect/insights-configs/create create mode 100644 gcloud/alpha/developer-connect/insights-configs/delete create mode 100644 gcloud/alpha/developer-connect/insights-configs/describe create mode 100644 gcloud/alpha/developer-connect/insights-configs/help rename gcloud/alpha/{healthcare/annotation-stores => developer-connect/insights-configs}/list (61%) create mode 100644 gcloud/alpha/developer-connect/insights-configs/update delete mode 100644 gcloud/alpha/healthcare/annotation-stores/add-iam-policy-binding delete mode 100644 gcloud/alpha/healthcare/annotation-stores/create delete mode 100644 gcloud/alpha/healthcare/annotation-stores/delete delete mode 100644 gcloud/alpha/healthcare/annotation-stores/describe delete mode 100644 gcloud/alpha/healthcare/annotation-stores/evaluate/bq delete mode 100644 gcloud/alpha/healthcare/annotation-stores/evaluate/help delete mode 100644 gcloud/alpha/healthcare/annotation-stores/export/bq delete mode 100644 gcloud/alpha/healthcare/annotation-stores/export/gcs delete mode 100644 gcloud/alpha/healthcare/annotation-stores/export/help delete mode 100644 gcloud/alpha/healthcare/annotation-stores/get-iam-policy delete mode 100644 gcloud/alpha/healthcare/annotation-stores/help delete mode 100644 gcloud/alpha/healthcare/annotation-stores/import/gcs delete mode 100644 gcloud/alpha/healthcare/annotation-stores/import/help delete mode 100644 gcloud/alpha/healthcare/annotation-stores/remove-iam-policy-binding delete mode 100644 gcloud/alpha/healthcare/annotation-stores/set-iam-policy delete mode 100644 gcloud/alpha/healthcare/annotation-stores/update create mode 100644 gcloud/alpha/managed-kafka/schema-registries/subject/describe create mode 100644 gcloud/alpha/managed-kafka/schema-registries/subject/help create mode 100644 gcloud/alpha/managed-kafka/schema-registries/subject/update create mode 100644 gcloud/alpha/managed-kafka/schema-registries/update create mode 100644 gcloud/alpha/run/worker-pools/replace create mode 100644 gcloud/alpha/spanner/databases/import create mode 100644 gcloud/beta/compute/preview-features/describe create mode 100644 gcloud/beta/compute/preview-features/help create mode 100644 gcloud/beta/compute/preview-features/list create mode 100644 gcloud/beta/compute/preview-features/update create mode 100644 gcloud/beta/compute/reservations/sub-blocks/describe create mode 100644 gcloud/beta/compute/reservations/sub-blocks/help create mode 100644 gcloud/beta/compute/reservations/sub-blocks/list create mode 100644 gcloud/beta/container/fleet/packages/create create mode 100644 gcloud/beta/container/fleet/packages/delete create mode 100644 gcloud/beta/container/fleet/packages/describe create mode 100644 gcloud/beta/container/fleet/packages/help create mode 100644 gcloud/beta/container/fleet/packages/list create mode 100644 gcloud/beta/container/fleet/packages/resource-bundles/create create mode 100644 gcloud/beta/container/fleet/packages/resource-bundles/delete create mode 100644 gcloud/beta/container/fleet/packages/resource-bundles/describe create mode 100644 gcloud/beta/container/fleet/packages/resource-bundles/help create mode 100644 gcloud/beta/container/fleet/packages/resource-bundles/list create mode 100644 gcloud/beta/container/fleet/packages/resource-bundles/releases/create create mode 100644 gcloud/beta/container/fleet/packages/resource-bundles/releases/delete create mode 100644 gcloud/beta/container/fleet/packages/resource-bundles/releases/describe create mode 100644 gcloud/beta/container/fleet/packages/resource-bundles/releases/help create mode 100644 gcloud/beta/container/fleet/packages/resource-bundles/releases/list create mode 100644 gcloud/beta/container/fleet/packages/resource-bundles/releases/update create mode 100644 gcloud/beta/container/fleet/packages/resource-bundles/update create mode 100644 gcloud/beta/container/fleet/packages/rollouts/abort create mode 100644 gcloud/beta/container/fleet/packages/rollouts/describe create mode 100644 gcloud/beta/container/fleet/packages/rollouts/help create mode 100644 gcloud/beta/container/fleet/packages/rollouts/list create mode 100644 gcloud/beta/container/fleet/packages/rollouts/resume create mode 100644 gcloud/beta/container/fleet/packages/rollouts/suspend create mode 100644 gcloud/beta/container/fleet/packages/update create mode 100644 gcloud/beta/container/fleet/rbacrolebindingactuation/describe create mode 100644 gcloud/beta/container/fleet/rbacrolebindingactuation/help create mode 100644 gcloud/beta/container/fleet/rbacrolebindingactuation/update create mode 100644 gcloud/beta/container/hub/packages/create create mode 100644 gcloud/beta/container/hub/packages/delete create mode 100644 gcloud/beta/container/hub/packages/describe create mode 100644 gcloud/beta/container/hub/packages/help create mode 100644 gcloud/beta/container/hub/packages/list create mode 100644 gcloud/beta/container/hub/packages/resource-bundles/create create mode 100644 gcloud/beta/container/hub/packages/resource-bundles/delete create mode 100644 gcloud/beta/container/hub/packages/resource-bundles/describe create mode 100644 gcloud/beta/container/hub/packages/resource-bundles/help create mode 100644 gcloud/beta/container/hub/packages/resource-bundles/list create mode 100644 gcloud/beta/container/hub/packages/resource-bundles/releases/create create mode 100644 gcloud/beta/container/hub/packages/resource-bundles/releases/delete create mode 100644 gcloud/beta/container/hub/packages/resource-bundles/releases/describe create mode 100644 gcloud/beta/container/hub/packages/resource-bundles/releases/help create mode 100644 gcloud/beta/container/hub/packages/resource-bundles/releases/list create mode 100644 gcloud/beta/container/hub/packages/resource-bundles/releases/update create mode 100644 gcloud/beta/container/hub/packages/resource-bundles/update create mode 100644 gcloud/beta/container/hub/packages/rollouts/abort create mode 100644 gcloud/beta/container/hub/packages/rollouts/describe create mode 100644 gcloud/beta/container/hub/packages/rollouts/help create mode 100644 gcloud/beta/container/hub/packages/rollouts/list create mode 100644 gcloud/beta/container/hub/packages/rollouts/resume create mode 100644 gcloud/beta/container/hub/packages/rollouts/suspend create mode 100644 gcloud/beta/container/hub/packages/update create mode 100644 gcloud/beta/container/hub/rbacrolebindingactuation/describe create mode 100644 gcloud/beta/container/hub/rbacrolebindingactuation/help create mode 100644 gcloud/beta/container/hub/rbacrolebindingactuation/update create mode 100644 gcloud/beta/developer-connect/insights-configs/create create mode 100644 gcloud/beta/developer-connect/insights-configs/delete create mode 100644 gcloud/beta/developer-connect/insights-configs/describe create mode 100644 gcloud/beta/developer-connect/insights-configs/help create mode 100644 gcloud/beta/developer-connect/insights-configs/list create mode 100644 gcloud/beta/developer-connect/insights-configs/update delete mode 100644 gcloud/beta/healthcare/annotation-stores/add-iam-policy-binding delete mode 100644 gcloud/beta/healthcare/annotation-stores/create delete mode 100644 gcloud/beta/healthcare/annotation-stores/delete delete mode 100644 gcloud/beta/healthcare/annotation-stores/describe delete mode 100644 gcloud/beta/healthcare/annotation-stores/evaluate/bq delete mode 100644 gcloud/beta/healthcare/annotation-stores/evaluate/help delete mode 100644 gcloud/beta/healthcare/annotation-stores/export/bq delete mode 100644 gcloud/beta/healthcare/annotation-stores/export/gcs delete mode 100644 gcloud/beta/healthcare/annotation-stores/export/help delete mode 100644 gcloud/beta/healthcare/annotation-stores/help delete mode 100644 gcloud/beta/healthcare/annotation-stores/import/gcs delete mode 100644 gcloud/beta/healthcare/annotation-stores/import/help delete mode 100644 gcloud/beta/healthcare/annotation-stores/remove-iam-policy-binding delete mode 100644 gcloud/beta/healthcare/annotation-stores/set-iam-policy delete mode 100644 gcloud/beta/healthcare/annotation-stores/update create mode 100644 gcloud/beta/managed-kafka/schema-registries/create create mode 100644 gcloud/beta/managed-kafka/schema-registries/delete create mode 100644 gcloud/beta/managed-kafka/schema-registries/describe create mode 100644 gcloud/beta/managed-kafka/schema-registries/help rename gcloud/beta/{healthcare/annotation-stores/get-iam-policy => managed-kafka/schema-registries/list} (52%) create mode 100644 gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/create create mode 100644 gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/delete create mode 100644 gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/describe create mode 100644 gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/help create mode 100644 gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/list create mode 100644 gcloud/beta/network-connectivity/spokes/gateways/create create mode 100644 gcloud/beta/network-connectivity/spokes/gateways/help create mode 100644 gcloud/beta/network-connectivity/spokes/gateways/update create mode 100644 gcloud/beta/network-management/vpc-flow-logs-configs/query-org-vpc-flow-logs-configs create mode 100644 gcloud/beta/network-security/secure-access-connect/attachments/create create mode 100644 gcloud/beta/network-security/secure-access-connect/attachments/delete create mode 100644 gcloud/beta/network-security/secure-access-connect/attachments/describe create mode 100644 gcloud/beta/network-security/secure-access-connect/attachments/help create mode 100644 gcloud/beta/network-security/secure-access-connect/attachments/list create mode 100644 gcloud/beta/network-security/secure-access-connect/help create mode 100644 gcloud/beta/network-security/secure-access-connect/realms/create create mode 100644 gcloud/beta/network-security/secure-access-connect/realms/delete create mode 100644 gcloud/beta/network-security/secure-access-connect/realms/describe create mode 100644 gcloud/beta/network-security/secure-access-connect/realms/help create mode 100644 gcloud/beta/network-security/secure-access-connect/realms/list create mode 100644 gcloud/beta/network-services/operations/cancel create mode 100644 gcloud/beta/network-services/operations/describe create mode 100644 gcloud/beta/network-services/operations/help rename gcloud/beta/{healthcare/annotation-stores => network-services/operations}/list (62%) create mode 100644 gcloud/beta/network-services/operations/wait create mode 100644 gcloud/beta/service-extensions/lb-edge-extensions/delete create mode 100644 gcloud/beta/service-extensions/lb-edge-extensions/describe create mode 100644 gcloud/beta/service-extensions/lb-edge-extensions/help create mode 100644 gcloud/beta/service-extensions/lb-edge-extensions/import create mode 100644 gcloud/beta/service-extensions/lb-edge-extensions/list create mode 100644 gcloud/compute/reservations/sub-blocks/describe create mode 100644 gcloud/compute/reservations/sub-blocks/help create mode 100644 gcloud/compute/reservations/sub-blocks/list create mode 100644 gcloud/compute/resource-policies/create/workload-policy create mode 100644 gcloud/container/fleet/rbacrolebindingactuation/describe create mode 100644 gcloud/container/fleet/rbacrolebindingactuation/help create mode 100644 gcloud/container/fleet/rbacrolebindingactuation/update create mode 100644 gcloud/container/hub/rbacrolebindingactuation/describe create mode 100644 gcloud/container/hub/rbacrolebindingactuation/help create mode 100644 gcloud/container/hub/rbacrolebindingactuation/update create mode 100644 gcloud/dataplex/datascans/create/data-discovery create mode 100644 gcloud/dataplex/datascans/update/data-discovery create mode 100644 gcloud/dataplex/metadata-jobs/cancel create mode 100644 gcloud/dataplex/metadata-jobs/create create mode 100644 gcloud/dataplex/metadata-jobs/describe create mode 100644 gcloud/dataplex/metadata-jobs/help create mode 100644 gcloud/dataplex/metadata-jobs/list create mode 100644 gcloud/developer-connect/insights-configs/create create mode 100644 gcloud/developer-connect/insights-configs/delete create mode 100644 gcloud/developer-connect/insights-configs/describe create mode 100644 gcloud/developer-connect/insights-configs/help create mode 100644 gcloud/developer-connect/insights-configs/list create mode 100644 gcloud/developer-connect/insights-configs/update create mode 100644 gcloud/network-services/operations/cancel create mode 100644 gcloud/network-services/operations/describe create mode 100644 gcloud/network-services/operations/help create mode 100644 gcloud/network-services/operations/list create mode 100644 gcloud/network-services/operations/wait create mode 100644 gcloud/observability/help create mode 100644 gcloud/observability/scopes/describe create mode 100644 gcloud/observability/scopes/help create mode 100644 gcloud/observability/scopes/update diff --git a/gcloud/_version b/gcloud/_version index e3399c7f4..3c55c3aab 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 522.0.0 -alpha 2025.05.09 -beta 2025.05.09 -bq 2.1.16 +Google Cloud SDK 526.0.1 +alpha 2025.06.10 +beta 2025.06.10 +bq 2.1.18 bundled-python3-unix 3.12.9 -core 2025.05.09 +core 2025.06.10 gcloud-crc32c 1.0.0 gsutil 5.34 diff --git a/gcloud/ai/endpoints/list b/gcloud/ai/endpoints/list index 0bd06a92d..95e9cf736 100644 --- a/gcloud/ai/endpoints/list +++ b/gcloud/ai/endpoints/list @@ -2,8 +2,9 @@ NAME gcloud ai endpoints list - list existing Vertex AI endpoints SYNOPSIS - gcloud ai endpoints list [--region=REGION] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud ai endpoints list [--list-model-garden-endpoints-only] + [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] EXAMPLES @@ -11,7 +12,16 @@ EXAMPLES $ gcloud ai endpoints list --project=example --region=us-central1 + To list the endpoints under project example in region us-central1 that are + created from Model Garden, run: + + $ gcloud ai endpoints list --project=example --region=us-central1 \ + --list-model-garden-endpoints-only + FLAGS + --list-model-garden-endpoints-only + Whether to only list endpoints related to Model Garden. + Region resource - Cloud region to list endpoints. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. diff --git a/gcloud/ai/help b/gcloud/ai/help index dfea8b24b..013283fbc 100644 --- a/gcloud/ai/help +++ b/gcloud/ai/help @@ -30,6 +30,9 @@ GROUPS indexes Manage Vertex AI indexes. + model-garden + Interact with and manage resources in Vertex Model Garden. + model-monitoring-jobs Manage Vertex AI model monitoring jobs. diff --git a/gcloud/ai/model-garden/help b/gcloud/ai/model-garden/help new file mode 100644 index 000000000..f5d977149 --- /dev/null +++ b/gcloud/ai/model-garden/help @@ -0,0 +1,28 @@ +NAME + gcloud ai model-garden - interact with and manage resources in Vertex Model + Garden + +SYNOPSIS + gcloud ai model-garden GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Interact with and manage resources in Vertex Model Garden. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + models + List and use Model Garden models. + +NOTES + These variants are also available: + + $ gcloud alpha ai model-garden + + $ gcloud beta ai model-garden + diff --git a/gcloud/ai/model-garden/models/deploy b/gcloud/ai/model-garden/models/deploy new file mode 100644 index 000000000..161764482 --- /dev/null +++ b/gcloud/ai/model-garden/models/deploy @@ -0,0 +1,198 @@ +NAME + gcloud ai model-garden models deploy - deploy a model in Model Garden to a + Vertex AI endpoint + +SYNOPSIS + gcloud ai model-garden models deploy --model=MODEL + [--accelerator-type=ACCELERATOR_TYPE] [--accept-eula] [--asynchronous] + [--container-args=[ARG,...]] [--container-command=[COMMAND,...]] + [--container-deployment-timeout-seconds=CONTAINER_DEPLOYMENT_TIMEOUT_SECONDS] + [--container-env-vars=[KEY=VALUE,...]] + [--container-grpc-ports=[PORT,...]] + [--container-health-probe-exec=[HEALTH_PROBE_EXEC,...]] + [--container-health-probe-period-seconds=CONTAINER_HEALTH_PROBE_PERIOD_SECONDS] + [--container-health-probe-timeout-seconds=CONTAINER_HEALTH_PROBE_TIMEOUT_SECONDS] + [--container-health-route=CONTAINER_HEALTH_ROUTE] + [--container-image-uri=CONTAINER_IMAGE_URI] + [--container-ports=[PORT,...]] + [--container-predict-route=CONTAINER_PREDICT_ROUTE] + [--container-shared-memory-size-mb=CONTAINER_SHARED_MEMORY_SIZE_MB] + [--container-startup-probe-exec=[STARTUP_PROBE_EXEC,...]] + [--container-startup-probe-period-seconds=CONTAINER_STARTUP_PROBE_PERIOD_SECONDS] + [--container-startup-probe-timeout-seconds=CONTAINER_STARTUP_PROBE_TIMEOUT_SECONDS] + [--enable-fast-tryout] [--endpoint-display-name=ENDPOINT_DISPLAY_NAME] + [--hugging-face-access-token=HUGGING_FACE_ACCESS_TOKEN] + [--machine-type=MACHINE_TYPE] [--region=REGION] + [--reservation-affinity=[key=KEY], + [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], + [values=VALUES]] [--spot] [--use-dedicated-endpoint] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To deploy a Model Garden model google/gemma2/gemma2-9b under project + example in region us-central1, run: + + $ gcloud ai model-garden models deploy \ + --model=google/gemma2@gemma-2-9b --project=example \ + --region=us-central1 + + To deploy a Hugging Face model meta-llama/Meta-Llama-3-8B under project + example in region us-central1, run: + + $ gcloud ai model-garden models deploy \ + --model=meta-llama/Meta-Llama-3-8B \ + --hugging-face-access-token={hf_token} --project=example \ + --region=us-central1 + +REQUIRED FLAGS + --model=MODEL + The model to be deployed. If it is a Model Garden model, it should be + in the format of {publisher_name}/{model_name}@{model_version_name}, + e.g. google/gemma2@gemma-2-2b. If it is a Hugging Face model, it should + be in the convention of Hugging Face models, e.g. + meta-llama/Meta-Llama-3-8B. + +OPTIONAL FLAGS + --accelerator-type=ACCELERATOR_TYPE + The accelerator type to serve the model. It should be a supported + accelerator type from the verified deployment configurations of the + model. Use gcloud ai model-garden models list-deployment-config to + check the supported accelerator types. + + --accept-eula + When set, the user accepts the End User License Agreement (EULA) of the + model. + + --asynchronous + If set to true, the command will terminate immediately and not keep + polling the operation status. + + --container-args=[ARG,...] + Comma-separated arguments passed to the command run by the container + image. If not specified and no --command is provided, the container + image's default command is used. + + --container-command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default entrypoint is run. + + --container-deployment-timeout-seconds=CONTAINER_DEPLOYMENT_TIMEOUT_SECONDS + Deployment timeout in seconds. + + --container-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + --container-grpc-ports=[PORT,...] + Container ports to receive grpc requests at. Must be a number between 1 + and 65535, inclusive. + + --container-health-probe-exec=[HEALTH_PROBE_EXEC,...] + Exec specifies the action to take. Used by health probe. An example of + this argument would be ["cat", "/tmp/healthy"]. + + --container-health-probe-period-seconds=CONTAINER_HEALTH_PROBE_PERIOD_SECONDS + How often (in seconds) to perform the health probe. Default to 10 + seconds. Minimum value is 1. + + --container-health-probe-timeout-seconds=CONTAINER_HEALTH_PROBE_TIMEOUT_SECONDS + Number of seconds after which the health probe times out. Defaults to 1 + second. Minimum value is 1. + + --container-health-route=CONTAINER_HEALTH_ROUTE + HTTP path to send health checks to inside the container. + + --container-image-uri=CONTAINER_IMAGE_URI + URI of the Model serving container file in the Container Registry (e.g. + gcr.io/myproject/server:latest). + + --container-ports=[PORT,...] + Container ports to receive http requests at. Must be a number between 1 + and 65535, inclusive. + + --container-predict-route=CONTAINER_PREDICT_ROUTE + HTTP path to send prediction requests to inside the container. + + --container-shared-memory-size-mb=CONTAINER_SHARED_MEMORY_SIZE_MB + The amount of the VM memory to reserve as the shared memory for the + model in megabytes. + + --container-startup-probe-exec=[STARTUP_PROBE_EXEC,...] + Exec specifies the action to take. Used by startup probe. An example of + this argument would be ["cat", "/tmp/healthy"]. + + --container-startup-probe-period-seconds=CONTAINER_STARTUP_PROBE_PERIOD_SECONDS + How often (in seconds) to perform the startup probe. Default to 10 + seconds. Minimum value is 1. + + --container-startup-probe-timeout-seconds=CONTAINER_STARTUP_PROBE_TIMEOUT_SECONDS + Number of seconds after which the startup probe times out. Defaults to + 1 second. Minimum value is 1. + + --enable-fast-tryout + If True, model will be deployed using faster deployment path. Useful + for quick experiments. Not for production workloads. Only available for + most popular models with certain machine types. + + --endpoint-display-name=ENDPOINT_DISPLAY_NAME + Display name of the endpoint with the deployed model. + + --hugging-face-access-token=HUGGING_FACE_ACCESS_TOKEN + The access token from Hugging Face needed to read the model artifacts + of gated models. It is only needed when the Hugging Face model to + deploy is gated. + + --machine-type=MACHINE_TYPE + The machine type to deploy the model to. It should be a supported + machine type from the deployment configurations of the model. Use + gcloud ai model-garden models list-deployment-config to check the + supported machine types. + + Region resource - Cloud region to deploy the model. This represents a + Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --region on the command line with a fully + specified name; + ◆ set the property ai/region with a fully specified name; + ◆ choose one from the prompted list of available regions with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + + --reservation-affinity=[key=KEY],[reservation-affinity-type=RESERVATION-AFFINITY-TYPE],[values=VALUES] + A ReservationAffinity can be used to configure a Vertex AI resource + (e.g., a DeployedModel) to draw its Compute Engine resources from a + Shared Reservation, or exclusively from on-demand capacity. + + --spot + If true, schedule the deployment workload on Spot VM. + + --use-dedicated-endpoint + If true, the endpoint will be exposed through a dedicated DNS. Your + request to the dedicated DNS will be isolated from other users' traffic + and will have better performance and reliability. + +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 ai model-garden models deploy + + $ gcloud beta ai model-garden models deploy + diff --git a/gcloud/ai/model-garden/models/help b/gcloud/ai/model-garden/models/help new file mode 100644 index 000000000..a5cc4e335 --- /dev/null +++ b/gcloud/ai/model-garden/models/help @@ -0,0 +1,34 @@ +NAME + gcloud ai model-garden models - list and use Model Garden models + +SYNOPSIS + gcloud ai model-garden models COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List and use Model Garden models. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + deploy + Deploy a model in Model Garden to a Vertex AI endpoint. + + list + List the publisher models in Model Garden. + + list-deployment-config + List the machine specifications supported by and verified for a model + in Model Garden. + +NOTES + These variants are also available: + + $ gcloud alpha ai model-garden models + + $ gcloud beta ai model-garden models + diff --git a/gcloud/ai/model-garden/models/list b/gcloud/ai/model-garden/models/list new file mode 100644 index 000000000..c94e36148 --- /dev/null +++ b/gcloud/ai/model-garden/models/list @@ -0,0 +1,72 @@ +NAME + gcloud ai model-garden models list - list the publisher models in Model + Garden + +SYNOPSIS + gcloud ai model-garden models list [--can-deploy-hugging-face-models] + [--full-resource-name] [--model-filter=MODEL_FILTER] + [--filter=EXPRESSION] [--limit=LIMIT; default=1000] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command lists either all models in Model Garden or all Hugging Face + models supported by Model Garden. + + Note: Since the number of Hugging Face models is large, the default limit + is set to 500 with a page size of 100 when listing supported Hugging Face + models. To override the limit or page size, specify the --limit or + --page-size flags, respectively. To list all models in Model Garden, use + --limit=unlimited. + +FLAGS + --can-deploy-hugging-face-models + Whether to only list Hugging Face models that can be deployed. + + --full-resource-name + Whether to return the full resource name of the model. + + --model-filter=MODEL_FILTER + Filter to apply to the model names or the display names of the list of + models. + +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; default=1000 + Maximum number of resources to list. The default is 1000. This flag + interacts with other flags that are applied in this order: --flatten, + --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha ai model-garden models list + + $ gcloud beta ai model-garden models list + diff --git a/gcloud/ai/model-garden/models/list-deployment-config b/gcloud/ai/model-garden/models/list-deployment-config new file mode 100644 index 000000000..6b344a753 --- /dev/null +++ b/gcloud/ai/model-garden/models/list-deployment-config @@ -0,0 +1,68 @@ +NAME + gcloud ai model-garden models list-deployment-config - list the machine + specifications supported by and verified for a model in Model Garden + +SYNOPSIS + gcloud ai model-garden models list-deployment-config --model=MODEL + [--hugging-face-access-token=HUGGING_FACE_ACCESS_TOKEN] + [--filter=EXPRESSION] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list the supported machine specifications for google/gemma2@gemma-2-9b, + run: + + $ gcloud ai model-garden models list-deployment-config \ + --model=google/gemma2@gemma-2-9b + + To list the supported machine specifications for a Hugging Face model + meta-llama/Meta-Llama-3-8B, run: + + $ gcloud ai model-garden models list-deployment-config \ + --model=meta-llama/Meta-Llama-3-8B + +REQUIRED FLAGS + --model=MODEL + The model to be deployed. If it is a Model Garden model, it should be + in the format of {publisher_name}/{model_name}@{model_version_name}, + e.g. google/gemma2@gemma-2-2b. If it is a Hugging Face model, it should + be in the convention of Hugging Face models, e.g. + meta-llama/Meta-Llama-3-8B. + +FLAGS + --hugging-face-access-token=HUGGING_FACE_ACCESS_TOKEN + The access token from Hugging Face needed to read the model artifacts + of gated models in order to generate the deployment configs. It is only + needed when the Hugging Face model to deploy is gated and not verified + by Model Garden. You can use the gcloud ai alpha/beta model-garden + models list command to find out which ones are verified by Model + Garden. + +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. + + --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 + These variants are also available: + + $ gcloud alpha ai model-garden models list-deployment-config + + $ gcloud beta ai model-garden models list-deployment-config + diff --git a/gcloud/alloydb/clusters/create b/gcloud/alloydb/clusters/create index c5696f869..7ee141792 100644 --- a/gcloud/alloydb/clusters/create +++ b/gcloud/alloydb/clusters/create @@ -54,7 +54,7 @@ OPTIONAL FLAGS for this cluster will be created in the allocated range. The range name must comply with RFC 1035. Specifically, the name must be 1-63 characters long and match the regular expression - [a-z]([-a-z0-9][a-z0-9])?. + [a-z]([-a-z0-9]*[a-z0-9])?. --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alloydb/clusters/create-secondary b/gcloud/alloydb/clusters/create-secondary index 211316e18..699e969f4 100644 --- a/gcloud/alloydb/clusters/create-secondary +++ b/gcloud/alloydb/clusters/create-secondary @@ -50,7 +50,7 @@ OPTIONAL FLAGS for this cluster will be created in the allocated range. The range name must comply with RFC 1035. Specifically, the name must be 1-63 characters long and match the regular expression - [a-z]([-a-z0-9][a-z0-9])?. + [a-z]([-a-z0-9]*[a-z0-9])?. --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alloydb/clusters/help b/gcloud/alloydb/clusters/help index ba5ee74b0..4db843cba 100644 --- a/gcloud/alloydb/clusters/help +++ b/gcloud/alloydb/clusters/help @@ -37,6 +37,10 @@ COMMANDS list List AlloyDB clusters in a given project and region. + migrate-cloud-sql + Migrate Cloud SQL instance to an AlloyDB cluster using an existing + Cloud SQL backup. + promote Promote an AlloyDB SECONDARY cluster in a given project and region. diff --git a/gcloud/alloydb/clusters/migrate-cloud-sql b/gcloud/alloydb/clusters/migrate-cloud-sql new file mode 100644 index 000000000..f9b8d4e54 --- /dev/null +++ b/gcloud/alloydb/clusters/migrate-cloud-sql @@ -0,0 +1,351 @@ +NAME + gcloud alloydb clusters migrate-cloud-sql - migrate Cloud SQL instance to + an AlloyDB cluster using an existing Cloud SQL backup + +SYNOPSIS + gcloud alloydb clusters migrate-cloud-sql CLUSTER + --cloud-sql-backup-id=CLOUD_SQL_BACKUP_ID + --cloud-sql-instance-id=CLOUD_SQL_INSTANCE_ID + --cloud-sql-project-id=CLOUD_SQL_PROJECT_ID --password=PASSWORD + --region=REGION [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] + [--async] [--database-version=DATABASE_VERSION] + [--enable-private-service-connect] [--network=NETWORK] + [--subscription-type=SUBSCRIPTION_TYPE] [--tags=[KEY=VALUE,...]] + [--continuous-backup-recovery-window-days=RECOVERY_PERIOD + --enable-continuous-backup + [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY + : --continuous-backup-encryption-key-keyring=CONTINUOUS_BACKUP_ENCRYPTION_KEY_KEYRING --continuous-backup-encryption-key-location=CONTINUOUS_BACKUP_ENCRYPTION_KEY_LOCATION --continuous-backup-encryption-key-project=CONTINUOUS_BACKUP_ENCRYPTION_KEY_PROJECT]] + [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE + --deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] + [--disable-automated-backup + | [--automated-backup-days-of-week=[DAYS_OF_WEEK,...] + --automated-backup-start-times=[START_TIMES,...] + : --automated-backup-window=TIMEOUT_PERIOD + [--automated-backup-encryption-key=AUTOMATED_BACKUP_ENCRYPTION_KEY + : --automated-backup-encryption-key-keyring=AUTOMATED_BACKUP_ENCRYPTION_KEY_KEYRING --automated-backup-encryption-key-location=AUTOMATED_BACKUP_ENCRYPTION_KEY_LOCATION --automated-backup-encryption-key-project=AUTOMATED_BACKUP_ENCRYPTION_KEY_PROJECT] --automated-backup-retention-count=RETENTION_COUNT | --automated-backup-retention-period=RETENTION_PERIOD]] + [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] + [--maintenance-window-day=MAINTENANCE_WINDOW_DAY + --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Migrate Cloud SQL instance to an AlloyDB cluster using an existing Cloud + SQL backup. + +EXAMPLES + To migrate a Cloud SQL instance to an AlloyDB cluster from a backup, run: + + $ gcloud alloydb clusters migrate-cloud-sql my-alloydb-cluster \ + --region=us-central1 \ + --cloud-sql-project-id=my-cloud-sql-project-id \ + --cloud-sql-instance-id=my-cloud-sql-cluster-id \ + --cloud-sql-backup-id=my-cloud-sql-backup-id + +POSITIONAL ARGUMENTS + CLUSTER + AlloyDB cluster ID + +REQUIRED FLAGS + Migrate Cloud SQL strategy. + + This must be specified. + + Migrate CloudSQL instance to an AlloyDB cluster by restoring from an + existing backup. + + --cloud-sql-backup-id=CLOUD_SQL_BACKUP_ID + CloudSQL backup ID to migrate from. This must be the backup ID + (myBackup). + + --cloud-sql-instance-id=CLOUD_SQL_INSTANCE_ID + CloudSQL instance ID to migrate from. This must be the instance ID + (myInstance). + + --cloud-sql-project-id=CLOUD_SQL_PROJECT_ID + CloudSQL project to migrate from. This must be the project ID + (myProject). + + --password=PASSWORD + Initial postgres user password to set up during cluster creation. + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME + Name of the allocated IP range for the private IP AlloyDB cluster, for + example: "google-managed-services-default". If set, the instance IPs + for this cluster will be created in the allocated range. The range name + must comply with RFC 1035. Specifically, the name must be 1-63 + characters long and match the regular expression + [a-z]([-a-z0-9]*[a-z0-9])?. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --database-version=DATABASE_VERSION + Database version of the cluster. DATABASE_VERSION must be one of: + POSTGRES_14, POSTGRES_15, POSTGRES_16. + + --enable-private-service-connect + Enable Private Service Connect (PSC) connectivity for the cluster. + + --network=NETWORK + Network in the current project that the instance will be part of. To + specify using a network with a shared VPC, use the full URL of the + network. For an example host project, testproject, and shared network, + testsharednetwork, this would be of the + form:--network=projects/testproject/global/networks/testsharednetwork + + --subscription-type=SUBSCRIPTION_TYPE + Subscription type of the cluster. SUBSCRIPTION_TYPE must be one of: + STANDARD, TRIAL. + + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. + + Example: 123/environment=production,123/costCenter=marketing + + Continuous Backup configuration. If unspecified, continuous backups are + enabled. + + --continuous-backup-recovery-window-days=RECOVERY_PERIOD + Recovery window of the log files and backups saved to support + Continuous Backups. + + --enable-continuous-backup + Enables Continuous Backups on the cluster. + + Key resource - The Cloud KMS (Key Management Service) cryptokey that + will be used to protect the continuous backup. The 'AlloyDB Service + Agent's service account must hold permission 'Cloud KMS CryptoKey + Encrypter/Decrypter'. The arguments in this group can be used to specify + the attributes of this resource. + + --continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --continuous-backup-encryption-key-keyring=CONTINUOUS_BACKUP_ENCRYPTION_KEY_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line with a fully specified name; + ▫ provide the argument --continuous-backup-encryption-key-keyring + on the command line. + + --continuous-backup-encryption-key-location=CONTINUOUS_BACKUP_ENCRYPTION_KEY_LOCATION + The Google Cloud location for the key. + + To set the kms-location attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line with a fully specified name; + ▫ provide the argument + --continuous-backup-encryption-key-location on the command line. + + --continuous-backup-encryption-key-project=CONTINUOUS_BACKUP_ENCRYPTION_KEY_PROJECT + The Google Cloud project for the key. + + To set the kms-project attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line with a fully specified name; + ▫ provide the argument --continuous-backup-encryption-key-project + on the command line; + ▫ set the property core/project. + + Specify preferred day and time for maintenance deny period. + + --deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE + Date when the deny maintenance period ends, that is 2020-11-01 or + 11-01 for recurring. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE + Date when the deny maintenance period begins, that is 2020-11-01 or + 11-01 for recurring. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME + Time when the deny maintenance period starts and ends, for example + 05:00, in UTC time zone. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + Automated backup policy. If unspecified, automated backups are disabled. + + At most one of these can be specified: + + --disable-automated-backup + Disables automated backups on the cluster. + + Enable automated backup policy. + + --automated-backup-days-of-week=[DAYS_OF_WEEK,...] + Comma-separated list of days of the week to perform a backup. At + least one day of the week must be provided. (e.g., + --automated-backup-days-of-week=MONDAY,WEDNESDAY,SUNDAY). + DAYS_OF_WEEK must be one of: MONDAY, TUESDAY, WEDNESDAY, THURSDAY, + FRIDAY, SATURDAY, SUNDAY. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --automated-backup-start-times=[START_TIMES,...] + Comma-separated list of times during the day to start a backup. At + least one start time must be provided. The start times are assumed + to be in UTC and required to be an exact hour in the format HH:00. + (e.g., --automated-backup-start-times=01:00,13:00) + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --automated-backup-window=TIMEOUT_PERIOD + Length of the time window beginning at start time during which a + backup can be taken. If a backup does not succeed within this time + window, it will be canceled and considered failed. The backup + window must be at least 5 minutes long. There is no upper bound on + the window. If not set, it will default to 1 hour. + + Key resource - The Cloud KMS (Key Management Service) cryptokey that + will be used to protect the automated backups. The 'AlloyDB Service + Agent' service account must hold permission 'Cloud KMS CryptoKey + Encrypter/Decrypter'. The arguments in this group can be used to + specify the attributes of this resource. + + --automated-backup-encryption-key=AUTOMATED_BACKUP_ENCRYPTION_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ◇ provide the argument --automated-backup-encryption-key on the + command line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --automated-backup-encryption-key-keyring=AUTOMATED_BACKUP_ENCRYPTION_KEY_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ◇ provide the argument --automated-backup-encryption-key on the + command line with a fully specified name; + ◇ provide the argument + --automated-backup-encryption-key-keyring on the command line. + + --automated-backup-encryption-key-location=AUTOMATED_BACKUP_ENCRYPTION_KEY_LOCATION + The Google Cloud location for the key. + + To set the kms-location attribute: + ◇ provide the argument --automated-backup-encryption-key on the + command line with a fully specified name; + ◇ provide the argument + --automated-backup-encryption-key-location on the command line. + + --automated-backup-encryption-key-project=AUTOMATED_BACKUP_ENCRYPTION_KEY_PROJECT + The Google Cloud project for the key. + + To set the kms-project attribute: + ◇ provide the argument --automated-backup-encryption-key on the + command line with a fully specified name; + ◇ provide the argument + --automated-backup-encryption-key-project on the command line; + ◇ set the property core/project. + + Retention policy. If no retention policy is provided, all automated + backups will be retained. + + At most one of these can be specified: + + --automated-backup-retention-count=RETENTION_COUNT + Number of most recent successful backups retained. + + --automated-backup-retention-period=RETENTION_PERIOD + Retention period of the backup relative to creation time. See $ + gcloud topic datetimes for information on duration formats. + + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the cluster. The 'AlloyDB Service Agent' service + account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. + The arguments in this group can be used to specify the attributes of this + resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▸ provide the argument --kms-key on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --kms-keyring=KMS_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-keyring on the command line. + + --kms-location=KMS_LOCATION + The Google Cloud location for the key. + + To set the kms-location attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + The Google Cloud project for the key. + + To set the kms-project attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-project on the command line; + ▸ set the property core/project. + + Specify preferred day and time for maintenance. + + --maintenance-window-day=MAINTENANCE_WINDOW_DAY + Day of week for maintenance window, in UTC time zone. + MAINTENANCE_WINDOW_DAY must be one of: MONDAY, TUESDAY, WEDNESDAY, + THURSDAY, FRIDAY, SATURDAY, SUNDAY. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR + Hour of day for maintenance window, in UTC time zone. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +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 alloydb clusters migrate-cloud-sql + + $ gcloud beta alloydb clusters migrate-cloud-sql + diff --git a/gcloud/alloydb/clusters/restore b/gcloud/alloydb/clusters/restore index de88b8564..0a63cd238 100644 --- a/gcloud/alloydb/clusters/restore +++ b/gcloud/alloydb/clusters/restore @@ -58,16 +58,17 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. - --source-cluster=SOURCE_CLUSTER - AlloyDB source cluster to restore from. This must either be the - full cluster name - (projects/myProject/locations/us-central1/backups/myCluster) or the - cluster ID (myCluster). In the second case, the project and - location are assumed to be the same as the restored cluster that is - being created. + Source for a point in time restore operation. - This flag argument must be specified if any of the other arguments - in this group are specified. + This must be specified. + + --source-cluster=SOURCE_CLUSTER + AlloyDB source cluster to restore from. This must either be the + full cluster name + (projects/myProject/locations/us-central1/backups/myCluster) or + the cluster ID (myCluster). In the second case, the project and + location are assumed to be the same as the restored cluster that + is being created. OPTIONAL FLAGS --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME @@ -76,7 +77,7 @@ OPTIONAL FLAGS for this cluster will be created in the allocated range. The range name must comply with RFC 1035. Specifically, the name must be 1-63 characters long and match the regular expression - [a-z]([-a-z0-9][a-z0-9])?. + [a-z]([-a-z0-9]*[a-z0-9])?. --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alloydb/instances/update b/gcloud/alloydb/instances/update index 4983ac589..6ea9d5b4f 100644 --- a/gcloud/alloydb/instances/update +++ b/gcloud/alloydb/instances/update @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud alloydb instances update INSTANCE --cluster=CLUSTER --region=REGION + [--activation-policy=ACTIVATION_POLICY] [--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]] [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async] [--authorized-external-networks=[AUTHORIZED_NETWORK,...]] @@ -45,6 +46,11 @@ REQUIRED FLAGS regions at https://cloud.google.com/sql/docs/instance-locations. OPTIONAL FLAGS + --activation-policy=ACTIVATION_POLICY + Activation Policy for the instance. Required to START or STOP an + instance. ALWAYS - The instance is up and running. NEVER - The instance + is stopped. ACTIVATION_POLICY must be one of: ALWAYS, NEVER. + --allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...] Comma-separated list of allowed consumer projects to create endpoints for Private Service Connect (PSC) connectivity for the instance. Only diff --git a/gcloud/alpha/ai/endpoints/list b/gcloud/alpha/ai/endpoints/list index b63544427..e7ea851f7 100644 --- a/gcloud/alpha/ai/endpoints/list +++ b/gcloud/alpha/ai/endpoints/list @@ -21,7 +21,7 @@ EXAMPLES FLAGS --list-model-garden-endpoints-only - Whether to only list endpoints created from Model Garden. + Whether to only list endpoints related to Model Garden. Region resource - Cloud region to list endpoints. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but diff --git a/gcloud/alpha/ai/model-garden/help b/gcloud/alpha/ai/model-garden/help index 2aca0f266..cb1f3ad8c 100644 --- a/gcloud/alpha/ai/model-garden/help +++ b/gcloud/alpha/ai/model-garden/help @@ -23,7 +23,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 ai model-garden $ gcloud beta ai model-garden diff --git a/gcloud/alpha/ai/model-garden/models/deploy b/gcloud/alpha/ai/model-garden/models/deploy index a038faf52..5396926bb 100644 --- a/gcloud/alpha/ai/model-garden/models/deploy +++ b/gcloud/alpha/ai/model-garden/models/deploy @@ -193,7 +193,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 ai model-garden models deploy $ gcloud beta ai model-garden models deploy diff --git a/gcloud/alpha/ai/model-garden/models/help b/gcloud/alpha/ai/model-garden/models/help index 6c7d8ee3b..d4ccbcdbf 100644 --- a/gcloud/alpha/ai/model-garden/models/help +++ b/gcloud/alpha/ai/model-garden/models/help @@ -29,7 +29,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 ai model-garden models $ gcloud beta ai model-garden models diff --git a/gcloud/alpha/ai/model-garden/models/list b/gcloud/alpha/ai/model-garden/models/list index 51179cb53..5120fc7d2 100644 --- a/gcloud/alpha/ai/model-garden/models/list +++ b/gcloud/alpha/ai/model-garden/models/list @@ -67,7 +67,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 ai model-garden models list $ gcloud beta ai model-garden models list diff --git a/gcloud/alpha/ai/model-garden/models/list-deployment-config b/gcloud/alpha/ai/model-garden/models/list-deployment-config index 57d1816bd..0eaeda828 100644 --- a/gcloud/alpha/ai/model-garden/models/list-deployment-config +++ b/gcloud/alpha/ai/model-garden/models/list-deployment-config @@ -64,7 +64,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 ai model-garden models list-deployment-config $ gcloud beta ai model-garden models list-deployment-config diff --git a/gcloud/alpha/alloydb/clusters/create b/gcloud/alpha/alloydb/clusters/create index b82da6fbb..ca0b815f2 100644 --- a/gcloud/alpha/alloydb/clusters/create +++ b/gcloud/alpha/alloydb/clusters/create @@ -54,7 +54,7 @@ OPTIONAL FLAGS for this cluster will be created in the allocated range. The range name must comply with RFC 1035. Specifically, the name must be 1-63 characters long and match the regular expression - [a-z]([-a-z0-9][a-z0-9])?. + [a-z]([-a-z0-9]*[a-z0-9])?. --async Return immediately, without waiting for the operation in progress to @@ -62,7 +62,7 @@ OPTIONAL FLAGS --database-version=DATABASE_VERSION Database version of the cluster. DATABASE_VERSION must be one of: - POSTGRES_14, POSTGRES_15, POSTGRES_16. + POSTGRES_14, POSTGRES_15, POSTGRES_16, POSTGRES_17. --enable-private-service-connect Enable Private Service Connect (PSC) connectivity for the cluster. diff --git a/gcloud/alpha/alloydb/clusters/create-secondary b/gcloud/alpha/alloydb/clusters/create-secondary index 30938cbbe..660e28f5b 100644 --- a/gcloud/alpha/alloydb/clusters/create-secondary +++ b/gcloud/alpha/alloydb/clusters/create-secondary @@ -50,7 +50,7 @@ OPTIONAL FLAGS for this cluster will be created in the allocated range. The range name must comply with RFC 1035. Specifically, the name must be 1-63 characters long and match the regular expression - [a-z]([-a-z0-9][a-z0-9])?. + [a-z]([-a-z0-9]*[a-z0-9])?. --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alpha/alloydb/clusters/help b/gcloud/alpha/alloydb/clusters/help index 18e19defe..97675d7b3 100644 --- a/gcloud/alpha/alloydb/clusters/help +++ b/gcloud/alpha/alloydb/clusters/help @@ -39,8 +39,7 @@ COMMANDS (ALPHA) List AlloyDB clusters in a given project and region. migrate-cloud-sql - (ALPHA) Migrate Cloud SQL instance to an AlloyDB cluster using an - existing Cloud SQL backup. + (ALPHA) Migrate Cloud SQL instance to an AlloyDB cluster. promote (ALPHA) Promote an AlloyDB SECONDARY cluster in a given project and diff --git a/gcloud/alpha/alloydb/clusters/migrate-cloud-sql b/gcloud/alpha/alloydb/clusters/migrate-cloud-sql index 12185e114..78907e582 100644 --- a/gcloud/alpha/alloydb/clusters/migrate-cloud-sql +++ b/gcloud/alpha/alloydb/clusters/migrate-cloud-sql @@ -1,6 +1,6 @@ NAME gcloud alpha alloydb clusters migrate-cloud-sql - migrate Cloud SQL - instance to an AlloyDB cluster using an existing Cloud SQL backup + instance to an AlloyDB cluster SYNOPSIS gcloud alpha alloydb clusters migrate-cloud-sql CLUSTER @@ -30,8 +30,8 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Migrate Cloud SQL instance to an AlloyDB cluster using an existing - Cloud SQL backup. + (ALPHA) This command migrates a Cloud SQL instance to an AlloyDB cluster + using an existing Cloud SQL backup. EXAMPLES To migrate a Cloud SQL instance to an AlloyDB cluster from a backup, run: @@ -80,7 +80,7 @@ OPTIONAL FLAGS for this cluster will be created in the allocated range. The range name must comply with RFC 1035. Specifically, the name must be 1-63 characters long and match the regular expression - [a-z]([-a-z0-9][a-z0-9])?. + [a-z]([-a-z0-9]*[a-z0-9])?. --async Return immediately, without waiting for the operation in progress to @@ -88,7 +88,7 @@ OPTIONAL FLAGS --database-version=DATABASE_VERSION Database version of the cluster. DATABASE_VERSION must be one of: - POSTGRES_14, POSTGRES_15, POSTGRES_16. + POSTGRES_14, POSTGRES_15, POSTGRES_16, POSTGRES_17. --enable-private-service-connect Enable Private Service Connect (PSC) connectivity for the cluster. @@ -346,7 +346,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 alloydb clusters migrate-cloud-sql $ gcloud beta alloydb clusters migrate-cloud-sql diff --git a/gcloud/alpha/alloydb/clusters/restore b/gcloud/alpha/alloydb/clusters/restore index c9f984086..ba4f4b3e3 100644 --- a/gcloud/alpha/alloydb/clusters/restore +++ b/gcloud/alpha/alloydb/clusters/restore @@ -58,16 +58,17 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. - --source-cluster=SOURCE_CLUSTER - AlloyDB source cluster to restore from. This must either be the - full cluster name - (projects/myProject/locations/us-central1/backups/myCluster) or the - cluster ID (myCluster). In the second case, the project and - location are assumed to be the same as the restored cluster that is - being created. + Source for a point in time restore operation. - This flag argument must be specified if any of the other arguments - in this group are specified. + Exactly one of these must be specified: + + --source-cluster=SOURCE_CLUSTER + AlloyDB source cluster to restore from. This must either be the + full cluster name + (projects/myProject/locations/us-central1/backups/myCluster) or + the cluster ID (myCluster). In the second case, the project and + location are assumed to be the same as the restored cluster that + is being created. OPTIONAL FLAGS --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME @@ -76,7 +77,7 @@ OPTIONAL FLAGS for this cluster will be created in the allocated range. The range name must comply with RFC 1035. Specifically, the name must be 1-63 characters long and match the regular expression - [a-z]([-a-z0-9][a-z0-9])?. + [a-z]([-a-z0-9]*[a-z0-9])?. --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alpha/alloydb/instances/update b/gcloud/alpha/alloydb/instances/update index 76ea3b957..8339f83a0 100644 --- a/gcloud/alpha/alloydb/instances/update +++ b/gcloud/alpha/alloydb/instances/update @@ -64,8 +64,8 @@ REQUIRED FLAGS OPTIONAL FLAGS --activation-policy=ACTIVATION_POLICY - Activation Policy for the instance.Required to START or STOP an - instance.ALWAYS - The instance is up and running.NEVER - The instance + Activation Policy for the instance. Required to START or STOP an + instance. ALWAYS - The instance is up and running. NEVER - The instance is stopped. ACTIVATION_POLICY must be one of: ALWAYS, NEVER. --allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...] diff --git a/gcloud/alpha/anthos/config/help b/gcloud/alpha/anthos/config/help index 6598e0c1c..8a566aabb 100644 --- a/gcloud/alpha/anthos/config/help +++ b/gcloud/alpha/anthos/config/help @@ -21,9 +21,6 @@ GROUPS operations (ALPHA) Get and list operations for Anthos Config Controller instances. - sync - (ALPHA) Anthos config sync 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 diff --git a/gcloud/alpha/anthos/config/sync/repo/describe b/gcloud/alpha/anthos/config/sync/repo/describe deleted file mode 100644 index 9ab298823..000000000 --- a/gcloud/alpha/anthos/config/sync/repo/describe +++ /dev/null @@ -1,89 +0,0 @@ -NAME - gcloud alpha anthos config sync repo describe - describe a repository that - is synced across clusters in Config Sync - -SYNOPSIS - gcloud alpha anthos config sync repo describe [--cluster=CLUSTER] - [--managed-resources=MANAGED_RESOURCES; default="failed"] - [--source=SOURCE] [--sync-name=SYNC_NAME] - [--sync-namespace=SYNC_NAMESPACE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Describe a repository that is synced across clusters in Config - Sync. - -EXAMPLES - To describe a repository with source as where the source is from - the output of the list command: - - $ gcloud alpha anthos config sync repo describe describe \ - --source= - - To describe the repository that is synced by a RootSync or RepoSync CR in - the namespace with the name : - - $ gcloud alpha anthos config sync repo describe describe \ - --sync-namespace= --sync-name= - - To describe the repository that is synced by a RootSync or RepoSync CR in - the namespace with the name from a specific cluster - : - - $ gcloud alpha anthos config sync repo describe describe \ - --sync-namespace= --sync-name= \ - --cluster= - - To describe a repository with source as and list all the managed - resources from this repositry: - - $ gcloud alpha anthos config sync repo describe describe \ - --source= --managed-resources=all - - To describe a repository with source as and only print the failed - managed resources from this repositry: - - $ gcloud alpha anthos config sync repo describe describe \ - --source= --managed-resources=failed \ - --format="multi(statuses:format=none,managed_resources:format='t\ - able[box](group,kind,name,namespace,conditions)')" - -FLAGS - --cluster=CLUSTER - The cluster name or the membership name that a repository is synced to. - - --managed-resources=MANAGED_RESOURCES; default="failed" - Specify the managed resource status that should beincluded in the - describe output.The supported values areall, current, failed, - inprogress, notfound, unknown. - - --source=SOURCE - The source of the repository. It should be copied fromthe output of the - listing repo command. - - --sync-name=SYNC_NAME - Name of the RootSync or RepoSync CR to sync a repository. - - --sync-namespace=SYNC_NAMESPACE - Namespace of the RootSync or RepoSync CR to sync a repository. - -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. - -PREREQUISITES - Please setup Connect Gateway if your registered clusters are non-GKE - clusters. The instructions can be found at - https://cloud.google.com/anthos/multicluster-management/gateway/setup. For - registered clusters that are GKE clusters, no need to setup the Connect - Gateway. - -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/anthos/config/sync/repo/list b/gcloud/alpha/anthos/config/sync/repo/list deleted file mode 100644 index b1abe6925..000000000 --- a/gcloud/alpha/anthos/config/sync/repo/list +++ /dev/null @@ -1,89 +0,0 @@ -NAME - gcloud alpha anthos config sync repo list - list repositories and their - status that are synced by Config Sync - -SYNOPSIS - gcloud alpha anthos config sync repo list [--membership=MEMBERSHIP] - [--namespace=NAMESPACE] [--selector=SELECTOR] - [--status=STATUS; default="all"] [--targets=TARGETS; default="all"] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) List repositories and their status that are synced by Config Sync. - -EXAMPLES - To list all repositories synced to the registered clusters or to the Config - Controller cluster in the current project: - - $ gcloud alpha anthos config sync repo list list - - To list all repositories synced to the registered clusters to the fleet - hosted in the current project: - - $ gcloud alpha anthos config sync repo list list \ - --targets=fleet-clusters - - To list all repositories synced to the Config Controller cluster in the - current project: - - $ gcloud alpha anthos config sync repo list list \ - --targets=fleet-clusters - - To list repositories in namespace synced to the registered - clusters to the current fleet: - - $ gcloud alpha anthos config sync repo list list \ - --targets=fleet-clusters --namespace= - - To list repositories synced to the registered clusters that are in a - "pending" status: - - $ gcloud alpha anthos config sync repo list list \ - --targets=fleet-clusters --status=pending - -FLAGS - --membership=MEMBERSHIP - The membership name that the listed Config Sync repos are synced to.A - membership is for a registered cluster to a fleet. It supportsa single - membership or multiple memberships with the format - membership1,membership2 or membership.It can only be specified when - --targets=fleet-clusters is used. - - --namespace=NAMESPACE - The namespace that the listed Config Sync repos are from.It supports a - single namespace or multiple namespaces with the format - namespace1,namespace2 or namespace. - - --selector=SELECTOR - The label selector that the listed Config Sync repos should match. It - supports the selector with the format key1=value1,key2=value2 - - --status=STATUS; default="all" - The status for the Config Sync repos that the list command should - include. The supported values are all, synced, pending, error, stalled. - - --targets=TARGETS; default="all" - The targets of the clusters. It must be one of the three values: all, - fleet-clusters, config-controller. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -PREREQUISITES - Please setup Connect Gateway if your registered clusters are non-GKE - clusters. The instructions can be found at - https://cloud.google.com/anthos/multicluster-management/gateway/setup. For - registered clusters that are GKE clusters, no need to setup the Connect - Gateway. - -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/anthos/config/sync/resources/list b/gcloud/alpha/anthos/config/sync/resources/list deleted file mode 100644 index 7cf3314e4..000000000 --- a/gcloud/alpha/anthos/config/sync/resources/list +++ /dev/null @@ -1,70 +0,0 @@ -NAME - gcloud alpha anthos config sync resources list - list resources and their - status that are synced by Config Sync - -SYNOPSIS - gcloud alpha anthos config sync resources list [--cluster=CLUSTER] - [--membership=MEMBERSHIP] [--sync-name=SYNC_NAME] - [--sync-namespace=SYNC_NAMESPACE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) List resources and their status that are synced by Config Sync. - -EXAMPLES - To list all managed resources in the current project, run: - - $ gcloud alpha anthos config sync resources list list - - To list all managed resources in a specific Config Controller cluster, run: - - $ gcloud alpha anthos config sync resources list list \ - --cluster= - - To list managed resources from a Git repo synced by Config Sync across - multiple clusters, run: - - $ gcloud alpha anthos config sync resources list list \ - --sync-name=root-sync --sync-namespace=config-management-system - - To list managed resources from a Git repo synced by Config Sync from a - specific cluster, run: - - $ gcloud alpha anthos config sync resources list list \ - --sync-namespace= --sync-name=repo-sync \ - --cluster= - -FLAGS - --cluster=CLUSTER - The cluster name or the membership name that a repository is synced to. - - --membership=MEMBERSHIP - The membership name that the listed Config Sync repos are synced to. A - membership is for a registered cluster to a fleet. It supports a single - membership or multiple memberships with the format - membership1,membership2 or membership. - - --sync-name=SYNC_NAME - Name of the RootSync or RepoSync CR to sync a repository. - - --sync-namespace=SYNC_NAMESPACE - Namespace of the RootSync or RepoSync CR to sync a repository. - -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. - -PREREQUISITES - Please setup Connect Gateway in order to use this command with non-GKE - registered clusters. The instructions can be found at - https://cloud.google.com/anthos/multicluster-management/gateway/setup. - -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/backup-dr/backups/restore/disk b/gcloud/alpha/backup-dr/backups/restore/disk new file mode 100644 index 000000000..c7c5bfc15 --- /dev/null +++ b/gcloud/alpha/backup-dr/backups/restore/disk @@ -0,0 +1,217 @@ +NAME + gcloud alpha backup-dr backups restore disk - restores a Compute Disk + Backup + +SYNOPSIS + gcloud alpha backup-dr backups restore disk + (BACKUP : --backup-vault=BACKUP_VAULT + --data-source=DATA_SOURCE --location=LOCATION) --name=NAME + --target-project=TARGET_PROJECT [--access-mode=ACCESS_MODE] + [--architecture=ARCHITECTURE] [--async] [--confidential-compute] + [--description=DESCRIPTION] + [--guest-os-features=[GUEST_OS_FEATURES,...]] [--kms-key=KMS_KEY] + [--labels=[KEY=VALUE,...]] [--licenses=LICENSE,[LICENSE,...]] + [--provisioned-iops=PROVISIONED_IOPS] + [--provisioned-throughput=PROVISIONED_THROUGHPUT] + [--replica-zones=ZONE,ZONE] [--resource-policies=RESOURCE_POLICY,[...]] + [--size=SIZE] [--storage-pool=STORAGE_POOL] + [--target-region=TARGET_REGION] [--target-zone=TARGET_ZONE] + [--type=TYPE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Restores a Compute Disk Backup. + +EXAMPLES + To restore a backup sample-backup in project sample-project and location + us-central1, with sample-data-store and sample-backup-vault, and additional + target properties, run: + + $ gcloud alpha backup-dr backups restore disk sample-backup \ + --project=sample-project --location=us-central1 \ + --backup-vault=sample-backup-vault \ + --data-source=sample-data-source -- + +POSITIONAL ARGUMENTS + Backup resource - The backup of a resource to be restored. 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 backup 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. + + BACKUP + ID of the Backup or fully qualified identifier for the Backup. + + To set the name attribute: + ▸ provide the argument backup on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --backup-vault on the command line. + + --data-source=DATA_SOURCE + The ID of the Data Source. + + To set the data-source attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --data-source on the command line. + + --location=LOCATION + The location of the Backup. + + To set the location attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --name=NAME + Name of the restored Disk. + + --target-project=TARGET_PROJECT + Project where the restore should happen. + +OPTIONAL FLAGS + --access-mode=ACCESS_MODE + Specifies how VMs attached to the disk can access the data on the disk. + To grant read-only access to multiple VMs attached to the disk, set + access-mode to READ_ONLY_MANY. To grant read-write access to only one + VM attached to the disk, use READ_WRITE_SINGLE. READ_WRITE_SINGLE is + used if omitted. ACCESS_MODE must be one of: READ_ONLY_MANY, + READ_WRITE_MANY, READ_WRITE_SINGLE. ACCESS_MODE must be one of: + + READ_ONLY_MANY + The AccessMode means the disk can be attached to multiple instances + in RW mode. + READ_WRITE_MANY + The AccessMode means the disk can be attached to multiple instances + in RO mode. + READ_WRITE_SINGLE + The default AccessMode, means the disk can be attached to single + instance in RW mode. + + --architecture=ARCHITECTURE + Specifies the architecture or processor type that this disk can + support. For available processor types on Compute Engine, see + https://cloud.google.com/compute/docs/cpu-platforms. ARCHITECTURE must + be one of: ARM64, X86_64. ARCHITECTURE must be one of: + + ARM64 + The disk can only be used with ARM64 machines. + X86_64 + The disk can only be used with x86_64 machines. + + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --confidential-compute + Creates the disk with confidential compute mode enabled. Encryption + with a Cloud KMS key is required to enable this option. + + --description=DESCRIPTION + Specifies a textual description of the restored disk. + + --guest-os-features=[GUEST_OS_FEATURES,...] + Enables one or more features for VM instances that use the image for + their boot disks. See the descriptions of supported features at: + https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features. + GUEST_OS_FEATURE must be one of: VIRTIO_SCSI_MULTIQUEUE, WINDOWS, + MULTI_IP_SUBNET, UEFI_COMPATIBLE, SEV_CAPABLE, SEV_LIVE_MIGRATABLE, + SEV_LIVE_MIGRATABLE_V2, SEV_SNP_CAPABLE, GVNIC, IDPF, TDX_CAPABLE, + SUSPEND_RESUME_COMPATIBLE. + + --kms-key=KMS_KEY + The Cloud KMS (Key Management Service) cryptokey that will be used to + protect the disk Provide the full resource name of the cryptokey in the + format: + projects//locations//keyRings//cryptoKeys/ + + --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. + + --licenses=LICENSE,[LICENSE,...] + A list of URIs to license resources. The provided licenses will be + added onto the created disks to indicate the licensing and billing + policies. + + --provisioned-iops=PROVISIONED_IOPS + Provisioned IOPS of disk to create. Only for use with disks of type + pd-extreme and hyperdisk-extreme. + + --provisioned-throughput=PROVISIONED_THROUGHPUT + Provisioned throughput of disk to create. The throughput unit is MB per + sec. Only for use with disks of type hyperdisk-throughput. + + --replica-zones=ZONE,ZONE + A comma-separated list of exactly 2 URLs of the zones where the disk + should be replicated to. Required when restoring to a regional disk. + The zones must be in the same region as specified in the + --target-region flag. See available zones with gcloud compute zones + list. + + --resource-policies=RESOURCE_POLICY,[...] + A list of resource policy names to be added to the disk. The policies + must exist in the same region as the disk. + + --size=SIZE + Size of the disk in GB. Disk size must be a multiple of 1 GB. If disk + size is not specified, the default size of 500GB for pd-standard disks, + 100GB for pd-balanced disks, 100GB for pd-ssd disks, and 1000GB for + pd-extreme disks will be used. For details about disk size limits, + refer to: https://cloud.google.com/compute/docs/disks + + --storage-pool=STORAGE_POOL + Specifies the URI of the storage pool in which the disk is created. + + --target-region=TARGET_REGION + Region where the target disk is restored. This flag is mutually + exclusive with --target-zone. + + --target-zone=TARGET_ZONE + Zone where the target disk is restored. This flag is mutually exclusive + with --target-region. + + --type=TYPE + URL of the disk type describing which disk type to use to restore the + disk. For example: projects/project/zones/zone/diskTypes/pd-ssd. To get + a list of available disk types, run gcloud compute disk-types list. The + default disk type is pd-standard. + +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. + +BRIEF + Restores the specified backup + +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/backup-dr/backups/restore/help b/gcloud/alpha/backup-dr/backups/restore/help index 5281399a7..697f68226 100644 --- a/gcloud/alpha/backup-dr/backups/restore/help +++ b/gcloud/alpha/backup-dr/backups/restore/help @@ -19,6 +19,9 @@ COMMANDS compute (ALPHA) Restores a Compute Engine VM Backup. + disk + (ALPHA) Restores a Compute Disk Backup. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/bigtable/instances/tables/create b/gcloud/alpha/bigtable/instances/tables/create index c4f1614f2..41f721f3d 100644 --- a/gcloud/alpha/bigtable/instances/tables/create +++ b/gcloud/alpha/bigtable/instances/tables/create @@ -115,7 +115,7 @@ REQUIRED FLAGS --column-families=[COLUMN_FAMILIES,...] A double-quote (") wrapped list of family name and corresponding garbage collection rules concatenated by :, where the rules are - optional. For example: \ + optional. For example: "family_1,family_2:maxage=5d&&maxversions=2,family_3:maxage=10d||maxversions=5" OPTIONAL FLAGS diff --git a/gcloud/alpha/bigtable/tables/create b/gcloud/alpha/bigtable/tables/create index a8403b9f9..7233fee56 100644 --- a/gcloud/alpha/bigtable/tables/create +++ b/gcloud/alpha/bigtable/tables/create @@ -114,7 +114,7 @@ REQUIRED FLAGS --column-families=[COLUMN_FAMILIES,...] A double-quote (") wrapped list of family name and corresponding garbage collection rules concatenated by :, where the rules are - optional. For example: \ + optional. For example: "family_1,family_2:maxage=5d&&maxversions=2,family_3:maxage=10d||maxversions=5" OPTIONAL FLAGS diff --git a/gcloud/alpha/blockchain-validator/blockchain-validator-configs/update b/gcloud/alpha/blockchain-validator/blockchain-validator-configs/update index 1330948a9..927b95fb9 100644 --- a/gcloud/alpha/blockchain-validator/blockchain-validator-configs/update +++ b/gcloud/alpha/blockchain-validator/blockchain-validator-configs/update @@ -10,7 +10,7 @@ SYNOPSIS [--request-id=REQUEST_ID] [--[no-]validation-work-enabled] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_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 ...] @@ -169,8 +169,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) Arguments for the key source config. diff --git a/gcloud/alpha/cloudlocationfinder/cloud-locations/describe b/gcloud/alpha/cloudlocationfinder/cloud-locations/describe new file mode 100644 index 000000000..37e6d112e --- /dev/null +++ b/gcloud/alpha/cloudlocationfinder/cloud-locations/describe @@ -0,0 +1,67 @@ +NAME + gcloud alpha cloudlocationfinder cloud-locations describe - describe + cloudLocations + +SYNOPSIS + gcloud alpha cloudlocationfinder cloud-locations describe + (CLOUD_LOCATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a cloudLocation + +EXAMPLES + To describe the cloudLocation, run: + + $ gcloud alpha cloudlocationfinder cloud-locations describe + +POSITIONAL ARGUMENTS + CloudLocation 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 cloud_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. + + CLOUD_LOCATION + ID of the cloudLocation or fully qualified identifier for the + cloudLocation. + + To set the cloud_location attribute: + ▸ provide the argument cloud_location 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 cloudLocation resource. + + 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 . + +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 cloudlocationfinder/v1alpha API. The full + documentation for this API can be found at: + +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/anthos/config/sync/repo/help b/gcloud/alpha/cloudlocationfinder/cloud-locations/help similarity index 54% rename from gcloud/alpha/anthos/config/sync/repo/help rename to gcloud/alpha/cloudlocationfinder/cloud-locations/help index ab46d9f4f..9198f1274 100644 --- a/gcloud/alpha/anthos/config/sync/repo/help +++ b/gcloud/alpha/cloudlocationfinder/cloud-locations/help @@ -1,12 +1,13 @@ NAME - gcloud alpha anthos config sync repo - anthos config sync repo command - group + gcloud alpha cloudlocationfinder cloud-locations - manage Cloud Location + resources SYNOPSIS - gcloud alpha anthos config sync repo COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha cloudlocationfinder cloud-locations COMMAND + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Anthos config sync repo command group. + (ALPHA) Manage Cloud Location resources. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,12 +18,13 @@ COMMANDS COMMAND is one of the following: describe - (ALPHA) Describe a repository that is synced across clusters in Config - Sync. + (ALPHA) Describe cloudLocations. list - (ALPHA) List repositories and their status that are synced by Config - Sync. + (ALPHA) List cloudLocations. + + search + (ALPHA) Search cloudLocations. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/cloudlocationfinder/cloud-locations/list b/gcloud/alpha/cloudlocationfinder/cloud-locations/list new file mode 100644 index 000000000..f6c5b5ee5 --- /dev/null +++ b/gcloud/alpha/cloudlocationfinder/cloud-locations/list @@ -0,0 +1,75 @@ +NAME + gcloud alpha cloudlocationfinder cloud-locations list - list cloudLocations + +SYNOPSIS + gcloud alpha cloudlocationfinder cloud-locations list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Request for listing Cloudlocations. + +EXAMPLES + To list CloudLocations, run: + + $ gcloud alpha cloudlocationfinder cloud-locations list + +FLAGS + Location resource - The resource location. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ location is always global 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; + ▸ location is always global. + +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. + + --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/cloudlocationfinder/cloud-locations/search b/gcloud/alpha/cloudlocationfinder/cloud-locations/search new file mode 100644 index 000000000..4ab9b94ce --- /dev/null +++ b/gcloud/alpha/cloudlocationfinder/cloud-locations/search @@ -0,0 +1,88 @@ +NAME + gcloud alpha cloudlocationfinder cloud-locations search - search + cloudLocations + +SYNOPSIS + gcloud alpha cloudlocationfinder cloud-locations search + --source-cloud-location=SOURCE_CLOUD_LOCATION [--limit=LIMIT] + [--location=LOCATION] [--page-size=PAGE_SIZE] [--query=QUERY] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Search Cloudlocations. + +EXAMPLES + To search CloudLocations, run: + + $ gcloud alpha cloudlocationfinder cloud-locations search \ + --source-cloud-location=aws-us-east-1 \ + --query=displayName=us-east4 + +REQUIRED FLAGS + Source cloud location resource - The source Cloud 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 --source-cloud-location 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 --source-cloud-location on the command line with + a fully specified name; + ◆ provide the argument --location on the command line; + ◆ location is always global. + + This must be specified. + + --source-cloud-location=SOURCE_CLOUD_LOCATION + ID of the source_cloud_location or fully qualified identifier for the + source_cloud_location. + + To set the cloud_location attribute: + ▸ provide the argument --source-cloud-location on the command line. + +OPTIONAL FLAGS + --limit=LIMIT + Maximum number of resources to return. + + Location resource - The resource location. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ location is always global 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; + ▸ location is always global. + + --page-size=PAGE_SIZE + Maximum number of resources per page. + + --query=QUERY + Query to use for searching Cloudlocations. + +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/anthos/config/sync/help b/gcloud/alpha/cloudlocationfinder/help similarity index 58% rename from gcloud/alpha/anthos/config/sync/help rename to gcloud/alpha/cloudlocationfinder/help index 3d68dae43..7aef9b609 100644 --- a/gcloud/alpha/anthos/config/sync/help +++ b/gcloud/alpha/cloudlocationfinder/help @@ -1,11 +1,11 @@ NAME - gcloud alpha anthos config sync - anthos config sync command group + gcloud alpha cloudlocationfinder - manage Cloudlocationfinder resources SYNOPSIS - gcloud alpha anthos config sync GROUP [GCLOUD_WIDE_FLAG ...] + gcloud alpha cloudlocationfinder GROUP [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Anthos config sync command group. + (ALPHA) Manage Cloudlocationfinder resources. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -15,11 +15,8 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: - repo - (ALPHA) Anthos config sync repo command group. - - resources - (ALPHA) Anthos config sync resources command group. + cloud-locations + (ALPHA) Manage Cloud Location resources. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/compute/backend-buckets/create b/gcloud/alpha/compute/backend-buckets/create index 5e1df654d..0df1f487f 100644 --- a/gcloud/alpha/compute/backend-buckets/create +++ b/gcloud/alpha/compute/backend-buckets/create @@ -16,7 +16,7 @@ SYNOPSIS [--negative-caching-policy=[[CODE=TTL],...]] [--[no-]request-coalescing] [--serve-while-stale=SERVE_WHILE_STALE] [--signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE] - [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute backend-buckets create is used to create @@ -290,6 +290,15 @@ OPTIONAL FLAGS This flag only affects signed URL requests. + At most one of these can be specified: + + --global + If set, the backend bucket is global. + + --region=REGION + Region of the backend bucket to create. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/backend-buckets/delete b/gcloud/alpha/compute/backend-buckets/delete index b002d1f58..7085aed7e 100644 --- a/gcloud/alpha/compute/backend-buckets/delete +++ b/gcloud/alpha/compute/backend-buckets/delete @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud alpha compute backend-buckets delete BACKEND_BUCKET_NAME - [BACKEND_BUCKET_NAME ...] [GCLOUD_WIDE_FLAG ...] + [BACKEND_BUCKET_NAME ...] [--global | --region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute backend-buckets delete deletes one or more @@ -13,6 +14,16 @@ POSITIONAL ARGUMENTS BACKEND_BUCKET_NAME [BACKEND_BUCKET_NAME ...] Names of the backend buckets to delete. +FLAGS + At most one of these can be specified: + + --global + If set, the backend buckets are global. + + --region=REGION + Region of the backend buckets to delete. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/backend-services/create b/gcloud/alpha/compute/backend-services/create index c1f151782..597d2b1a5 100644 --- a/gcloud/alpha/compute/backend-services/create +++ b/gcloud/alpha/compute/backend-services/create @@ -543,12 +543,10 @@ FLAGS Load Balancer), the protocol must be one of: TCP, UDP, UNSPECIFIED. If the load-balancing-scheme is INTERNAL_SELF_MANAGED (Traffic - Director), the protocol must be one of: HTTP, HTTPS, HTTP2, GRPC, H2C - (beta only). + Director), the protocol must be one of: HTTP, HTTPS, HTTP2, GRPC, H2C. If the load-balancing-scheme is INTERNAL_MANAGED (Internal Application - Load Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C - (beta only). + Load Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C. If the load-balancing-scheme is INTERNAL_MANAGED (Internal proxy Network Load Balancer), the protocol must be only TCP. @@ -563,8 +561,7 @@ FLAGS If the load-balancing-scheme is EXTERNAL_MANAGED (Global external Application Load Balancer and regional external Application Load - Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C (beta - only). + Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C. If the load-balancing-scheme is EXTERNAL_MANAGED (Global external proxy Network Load Balancer), the protocol must be one of: TCP, SSL. diff --git a/gcloud/alpha/compute/backend-services/update b/gcloud/alpha/compute/backend-services/update index 6c8449b64..c99aa950b 100644 --- a/gcloud/alpha/compute/backend-services/update +++ b/gcloud/alpha/compute/backend-services/update @@ -382,12 +382,10 @@ FLAGS Load Balancer), the protocol must be one of: TCP, UDP, UNSPECIFIED. If the load-balancing-scheme is INTERNAL_SELF_MANAGED (Traffic - Director), the protocol must be one of: HTTP, HTTPS, HTTP2, GRPC, H2C - (beta only). + Director), the protocol must be one of: HTTP, HTTPS, HTTP2, GRPC, H2C. If the load-balancing-scheme is INTERNAL_MANAGED (Internal Application - Load Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C - (beta only). + Load Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C. If the load-balancing-scheme is INTERNAL_MANAGED (Internal proxy Network Load Balancer), the protocol must be only TCP. @@ -402,8 +400,7 @@ FLAGS If the load-balancing-scheme is EXTERNAL_MANAGED (Global external Application Load Balancer and regional external Application Load - Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C (beta - only). + Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C. If the load-balancing-scheme is EXTERNAL_MANAGED (Global external proxy Network Load Balancer), the protocol must be one of: TCP, SSL. diff --git a/gcloud/alpha/compute/disks/bulk/create b/gcloud/alpha/compute/disks/bulk/create index 0caa83790..a94350e1e 100644 --- a/gcloud/alpha/compute/disks/bulk/create +++ b/gcloud/alpha/compute/disks/bulk/create @@ -3,9 +3,12 @@ NAME disks SYNOPSIS - gcloud alpha compute disks bulk create - --source-consistency-group-policy=SOURCE_CONSISTENCY_GROUP_POLICY - (--region=REGION | --zone=ZONE) [GCLOUD_WIDE_FLAG ...] + gcloud alpha compute disks bulk create (--region=REGION | --zone=ZONE) + [--source-consistency-group-policy=SOURCE_CONSISTENCY_GROUP_POLICY] + [--source-instant-snapshot-group=SOURCE_INSTANT_SNAPSHOT_GROUP] + [--source-snapshot-group=SOURCE_SNAPSHOT_GROUP] + [--source-instant-snapshot-group-region=SOURCE_INSTANT_SNAPSHOT_GROUP_REGION | --source-instant-snapshot-group-zone=SOURCE_INSTANT_SNAPSHOT_GROUP_ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute disks bulk create facilitates the creation of @@ -24,10 +27,6 @@ EXAMPLES --zone=us-central1-a REQUIRED FLAGS - --source-consistency-group-policy=SOURCE_CONSISTENCY_GROUP_POLICY - URL of the source consistency group resource policy. The resource - policy is always the same region as the source disks. - Exactly one of these must be specified: --region=REGION @@ -72,6 +71,28 @@ REQUIRED FLAGS Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE. +OPTIONAL FLAGS + --source-consistency-group-policy=SOURCE_CONSISTENCY_GROUP_POLICY + URL of the source consistency group resource policy. The resource + policy is always the same region as the source disks. + + --source-instant-snapshot-group=SOURCE_INSTANT_SNAPSHOT_GROUP + Source instant snapshot group used to create the disks. + + --source-snapshot-group=SOURCE_SNAPSHOT_GROUP + Source snapshot group used to create the disks. + + At most one of these can be specified: + + --source-instant-snapshot-group-region=SOURCE_INSTANT_SNAPSHOT_GROUP_REGION + Region of the source instant snapshot group to operate on. Overrides + the default compute/region property value for this command + invocation. + + --source-instant-snapshot-group-zone=SOURCE_INSTANT_SNAPSHOT_GROUP_ZONE + Zone of the source instant snapshot group to operate on. 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, diff --git a/gcloud/alpha/compute/disks/update b/gcloud/alpha/compute/disks/update index 420d8b25d..3ed7b7eee 100644 --- a/gcloud/alpha/compute/disks/update +++ b/gcloud/alpha/compute/disks/update @@ -7,9 +7,9 @@ SYNOPSIS [--provisioned-iops=PROVISIONED_IOPS] [--provisioned-throughput=PROVISIONED_THROUGHPUT] [--size=SIZE] [--update-labels=[KEY=VALUE,...]] - [--append-licenses=[LICENSE,LICENSE...,...] - --remove-licenses=[LICENSE,LICENSE...,...] - --replace-license=OLD_LICENSE,NEW_LICENSE,...,[...]] + [--append-licenses=LICENSE,[LICENSE,...] + --remove-licenses=LICENSE,[LICENSE,...] + --replace-license=LICENSE,LICENSE] [--clear-architecture | --update-architecture=UPDATE_ARCHITECTURE] [--clear-labels | --remove-labels=[KEY,...]] [--clear-user-licenses | --update-user-licenses=[LICENSE,...]] @@ -102,18 +102,18 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - --append-licenses=[LICENSE,LICENSE...,...] + --append-licenses=LICENSE,[LICENSE,...] "A list of license URIs or license codes. These licenses will be appended to the existing licenses on the disk. Provided licenses can be either license URIs or license codes but not a mix of both. - --remove-licenses=[LICENSE,LICENSE...,...] + --remove-licenses=LICENSE,[LICENSE,...] A list of license URIs or license codes. If present in the set of existing licenses, these licenses will be removed. If not present, this is a no-op. Provided licenses can be either license URIs or license codes but not a mix of both. - --replace-license=OLD_LICENSE,NEW_LICENSE,...,[...] + --replace-license=LICENSE,LICENSE A list of license URIs or license codes. The first license is the license to be replaced and the second license is the replacement license. Provided licenses can be either license URIs or license codes diff --git a/gcloud/alpha/compute/help b/gcloud/alpha/compute/help index 2afbca548..314c27b3c 100644 --- a/gcloud/alpha/compute/help +++ b/gcloud/alpha/compute/help @@ -185,6 +185,10 @@ GROUPS shared-vpc (ALPHA) Configure shared VPC. + snapshot-groups + (ALPHA) Create, list, describe and delete Compute Engine snapshot + groups. + snapshot-settings (ALPHA) Describe and update Compute Engine snapshot settings. diff --git a/gcloud/alpha/compute/instance-groups/managed/create b/gcloud/alpha/compute/instance-groups/managed/create index 69a7ef44c..01ab3f9f3 100644 --- a/gcloud/alpha/compute/instance-groups/managed/create +++ b/gcloud/alpha/compute/instance-groups/managed/create @@ -25,7 +25,7 @@ SYNOPSIS [--stopped-size=STOPPED_SIZE] [--suspended-size=SUSPENDED_SIZE] [--target-distribution-shape=SHAPE] [--target-pool=[TARGET_POOL,...]] [--target-size-policy-mode=TARGET_SIZE_POLICY_MODE] - [--zones=ZONE,[ZONE,...]] + [--workload-policy=WORKLOAD_POLICY] [--zones=ZONE,[ZONE,...]] [--health-check=HEALTH_CHECK | --http-health-check=HTTP_HEALTH_CHECK | --https-health-check=HTTPS_HEALTH_CHECK] [--region=REGION | --zone=ZONE] @@ -345,6 +345,11 @@ OPTIONAL FLAGS something blocking part of VMs to be provisioned, the other part will be created. + --workload-policy=WORKLOAD_POLICY + Specifies the workload policy for the managed instance group. It can be + a full or partial URL to a resource policy containing the workload + policy. + --zones=ZONE,[ZONE,...] If this flag is specified a regional managed instance group will be created. The managed instance group will be in the same region as diff --git a/gcloud/alpha/compute/instance-groups/managed/update b/gcloud/alpha/compute/instance-groups/managed/update index 3a06a0f61..c52ed4d37 100644 --- a/gcloud/alpha/compute/instance-groups/managed/update +++ b/gcloud/alpha/compute/instance-groups/managed/update @@ -31,6 +31,7 @@ SYNOPSIS | --http-health-check=HTTP_HEALTH_CHECK | --https-health-check=HTTPS_HEALTH_CHECK] [--region=REGION | --zone=ZONE] + [--remove-workload-policy | --workload-policy=WORKLOAD_POLICY] [--update-policy-max-surge=MAX_SURGE --update-policy-max-unavailable=MAX_UNAVAILABLE --update-policy-min-ready=MIN_READY @@ -389,6 +390,16 @@ FLAGS Overrides the default compute/zone property value for this command invocation. + At most one of these can be specified: + + --remove-workload-policy + Detaches the workload policy from the managed instance group. + + --workload-policy=WORKLOAD_POLICY + Specifies the workload policy for the managed instance group. It can + be a full or partial URL to a resource policy containing the workload + policy. + Parameters for setting update policy for this managed instance group. --update-policy-max-surge=MAX_SURGE diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index 62863b4e2..41c21ea58 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -15,8 +15,8 @@ SYNOPSIS [--discard-local-ssds-at-termination-timestamp=DISCARD_LOCAL_SSDS_AT_TERMINATION_TIMESTAMP] [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], [interface=INTERFACE],[mode=MODE],[name=NAME]] - [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] - [--enable-watchdog-timer] + [--enable-display-device] [--[no-]enable-nested-virtualization] + [--[no-]enable-uefi-networking] [--enable-watchdog-timer] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] [--graceful-shutdown] @@ -135,8 +135,7 @@ FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the @@ -423,6 +422,9 @@ FLAGS ▸ SCSI ▸ NVME + --enable-display-device + Enable a display device on VM instances. Disabled by default. + --[no-]enable-nested-virtualization If set to true, enables nested virtualization for the instance. Use --enable-nested-virtualization to enable and @@ -783,6 +785,10 @@ FLAGS Specifies the network attachment that this interface should connect to. Mutually exclusive with --network and --subnet flags. + vlan + VLAN tag of a dynamic network interface, must be an integer in the + range from 2 to 255 inclusively. + igmp-query Determines if the Compute Engine Instance can receive and respond to IGMP query packets on the specified network interface. diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index 47d6a4352..971d1c4d4 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -42,7 +42,8 @@ SYNOPSIS [--network-interface=[PROPERTY=VALUE,...]] [--network-tier=NETWORK_TIER] [--preemptible] [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] - [--private-network-ip=PRIVATE_NETWORK_IP] [--region=REGION] + [--private-network-ip=PRIVATE_NETWORK_IP] + [--provisioning-model=PROVISIONING_MODEL] [--region=REGION] [--resource-policies=[RESOURCE_POLICY,...]] [--no-restart-on-failure] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--stack-type=STACK_TYPE] [--subnet=SUBNET] @@ -125,8 +126,7 @@ FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the @@ -706,6 +706,27 @@ FLAGS Specifies the RFC1918 IP to assign to the instance. The IP should be in the subnet or legacy network IP range. + --provisioning-model=PROVISIONING_MODEL + Specifies the provisioning model for your VM instances. This choice + affects the price, availability, and how long your VM instances can + run. PROVISIONING_MODEL must be one of: + + FLEX_START + Instance is provisioned using the Flex Start provisioning model and + has a limited runtime. + RESERVATION_BOUND + The VM instances run for the entire duration of their associated + reservation. You can only specify this provisioning model if you + want your VM instances to consume a specific reservation with + either a calendar reservation mode or a dense deployment type. + SPOT + Compute Engine may stop a Spot VM instance whenever it needs + capacity. Because Spot VM instances don't have a guaranteed + runtime, they come at a discounted price. + STANDARD + The default option. The STANDARD provisioning model gives you full + control over your VM instances' runtime. + --region=REGION Region of the instance template to create. If not specified, you might be prompted to select a region (interactive mode only). diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index a99819d85..942454fd9 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -175,8 +175,7 @@ OPTIONAL FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index fa7462ef3..2e7e3e75d 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -201,8 +201,7 @@ FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the @@ -1437,6 +1436,10 @@ FLAGS Specifies the network attachment that this interface should connect to. Mutually exclusive with --network and --subnet flags. + vlan + VLAN tag of a dynamic network interface, must be an integer in + the range from 2 to 255 inclusively. + igmp-query Determines if the Compute Engine Instance can receive and respond to IGMP query packets on the specified network interface. diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index 3b86d7b09..9c7a785b9 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -143,8 +143,7 @@ FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the diff --git a/gcloud/alpha/compute/instances/network-interfaces/add b/gcloud/alpha/compute/instances/network-interfaces/add index b7266898a..a17ce8056 100644 --- a/gcloud/alpha/compute/instances/network-interfaces/add +++ b/gcloud/alpha/compute/instances/network-interfaces/add @@ -143,8 +143,8 @@ FLAGS Specifies the subnetwork this network interface belongs to. --vlan=VLAN - VLAN tag of a dynamic network interface, must be in range from 2 to - 4094 inclusively. + VLAN tag of a dynamic network interface, must be an integer in the + range from 2 to 255 inclusively. --zone=ZONE Zone of the instance to operate on. If not specified, you might be diff --git a/gcloud/alpha/compute/instant-snapshot-groups/delete b/gcloud/alpha/compute/instant-snapshot-groups/delete new file mode 100644 index 000000000..e4a7c32a4 --- /dev/null +++ b/gcloud/alpha/compute/instant-snapshot-groups/delete @@ -0,0 +1,74 @@ +NAME + gcloud alpha compute instant-snapshot-groups delete - delete a Compute + Engine instant snapshot group + +SYNOPSIS + gcloud alpha compute instant-snapshot-groups delete + INSTANT_SNAPSHOT_GROUP_NAME [INSTANT_SNAPSHOT_GROUP_NAME ...] + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Compute Engine instant snapshot group. + +POSITIONAL ARGUMENTS + INSTANT_SNAPSHOT_GROUP_NAME [INSTANT_SNAPSHOT_GROUP_NAME ...] + Names of the instant snapshot groups to delete. + +FLAGS + At most one of these can be specified: + + --region=REGION + Region of the instant snapshot groups to delete. If not specified, + you might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --zone=ZONE + Zone of the instant snapshot groups to delete. 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/instant-snapshot-groups/help b/gcloud/alpha/compute/instant-snapshot-groups/help index 176e91d19..62992c8e9 100644 --- a/gcloud/alpha/compute/instant-snapshot-groups/help +++ b/gcloud/alpha/compute/instant-snapshot-groups/help @@ -19,9 +19,15 @@ COMMANDS create (ALPHA) Create a Compute Engine instant snapshot group. + delete + (ALPHA) Delete a Compute Engine instant snapshot group. + describe (ALPHA) Describe a Compute Engine instant snapshot group. + list + (ALPHA) List Google Compute Engine instant snapshot groups. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/compute/instant-snapshot-groups/list b/gcloud/alpha/compute/instant-snapshot-groups/list new file mode 100644 index 000000000..15fd7ed9c --- /dev/null +++ b/gcloud/alpha/compute/instant-snapshot-groups/list @@ -0,0 +1,96 @@ +NAME + gcloud alpha compute instant-snapshot-groups list - list Google Compute + Engine instant snapshot groups + +SYNOPSIS + gcloud alpha compute instant-snapshot-groups list + [--regions=[REGION,...] | --zones=[ZONE,...]] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute instant-snapshot-groups list displays all + Google Compute Engine instant snapshot groups in a project. + + By default, instant snapshot groups from all regions and instant snapshot + groups from all zones are listed. The results can be narrowed down by + providing the --regions or --zones flag. + +EXAMPLES + To list all instant snapshot groups in a project in table form, run: + + $ gcloud alpha compute instant-snapshot-groups list + + To list the URIs of all instant snapshot groups in a project, run: + + $ gcloud alpha compute instant-snapshot-groups list --uri + + To list all instant snapshot groups in the us-central1 and europe-west1 + regions, given they are regional resources, run: + + $ gcloud alpha compute instant-snapshot-groups list \ + --filter="region:( europe-west1 us-central1 )" + + To list all instant snapshot groups in zones us-central1-b and + europe-west1-d, given they are zonal resources, run: + + $ gcloud alpha compute instant-snapshot-groups list \ + --filter="zone:( europe-west1-d us-central1-b )" + +FLAGS + At most one of these can be specified: + + --regions=[REGION,...] + If provided, only regional resources are shown. If arguments are + provided, only resources from the given regions are shown. + + --zones=[ZONE,...] + If provided, only zonal resources are shown. If arguments are + provided, only resources from the given zones are shown. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/application-awareness/configure-shaper-average-percentage b/gcloud/alpha/compute/interconnects/application-awareness/configure-shaper-average-percentage new file mode 100644 index 000000000..c3c78ddb7 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/application-awareness/configure-shaper-average-percentage @@ -0,0 +1,60 @@ +NAME + gcloud alpha compute interconnects application-awareness + configure-shaper-average-percentage - configure shaper average + percentage for application awareness configuration of a Compute Engine + interconnect + +SYNOPSIS + gcloud alpha compute interconnects application-awareness + configure-shaper-average-percentage NAME + --bandwidth-percentages=[TC1=TC1], + [TC2=TC2],[TC3=TC3],[TC4=TC4],[TC5=TC5],[TC6=TC6] [--enabled] + [--profile-description=PROFILE_DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects application-awareness + configure-shaper-average-percentage is used to configure shaper average + percentage for using application awareness on interconnect. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To configure shaper average percentage for an interconnect + example-interconnect, run: + + $ gcloud alpha compute interconnects application-awareness \ configure-shaper-average-percentage example-interconnect \ + --bandwidth-percentages="TC1=11,TC2=10" --enabled \ + --profile_description="some string " + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect to patch. + +REQUIRED FLAGS + --bandwidth-percentages=[TC1=TC1],[TC2=TC2],[TC3=TC3],[TC4=TC4],[TC5=TC5],[TC6=TC6] + A list of bandwidth percentages for each application awareness profile. + The sum of all bandwidth percentages must be 100. + +OPTIONAL FLAGS + --enabled + Enable or disable application awareness on the interconnect. + Application awareness enablement will fail if the application awareness + configuration is not specified. Use --no-enabled to disable it. + + --profile-description=PROFILE_DESCRIPTION + Add profile description for application awareness. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/application-awareness/configure-strict-priority-policy b/gcloud/alpha/compute/interconnects/application-awareness/configure-strict-priority-policy new file mode 100644 index 000000000..26249d536 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/application-awareness/configure-strict-priority-policy @@ -0,0 +1,52 @@ +NAME + gcloud alpha compute interconnects application-awareness + configure-strict-priority-policy - configure strict priority policy for + application awareness configuration of a Compute Engine interconnect + +SYNOPSIS + gcloud alpha compute interconnects application-awareness + configure-strict-priority-policy NAME [--enabled] + [--profile-description=PROFILE_DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects application-awareness + configure-strict-priority-policy is used to configure strict priority + policy for using application awareness on interconnect. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To configure strict priority policy for an interconnect + example-interconnect, run: + + $ gcloud alpha compute interconnects application-awareness \ + configure-strict-priority-policy example-interconnect \ + --enabled --profile-description="some string" + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect to patch. + +FLAGS + --enabled + Enable or disable application awareness on the interconnect. + Application awareness enablement will fail if the application awareness + configuration is not specified. Use --no-enabled to disable it. + + --profile-description=PROFILE_DESCRIPTION + Add profile description for application awareness. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/application-awareness/help b/gcloud/alpha/compute/interconnects/application-awareness/help index c544d4407..f8429bc18 100644 --- a/gcloud/alpha/compute/interconnects/application-awareness/help +++ b/gcloud/alpha/compute/interconnects/application-awareness/help @@ -19,6 +19,14 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + configure-shaper-average-percentage + (ALPHA) Configure shaper average percentage for application awareness + configuration of a Compute Engine interconnect. + + configure-strict-priority-policy + (ALPHA) Configure strict priority policy for application awareness + configuration of a Compute Engine interconnect. + get-config (ALPHA) Get application awareness configuration of a Compute Engine interconnect. diff --git a/gcloud/alpha/compute/interconnects/attachments/dedicated/create b/gcloud/alpha/compute/interconnects/attachments/dedicated/create index 151d852d3..1b2f53fae 100644 --- a/gcloud/alpha/compute/interconnects/attachments/dedicated/create +++ b/gcloud/alpha/compute/interconnects/attachments/dedicated/create @@ -70,22 +70,22 @@ 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: - 74.133.16.1/30 + 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: - 2fff:eec0:3201:0:0:0:0:1/125 + 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: - 74.133.16.2/30 + 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: - 2fff:eec0:3201:0:0:0:0:2/125 + 2001:db8::2/125 --candidate-ipv6-subnets=[IPV6_SUBNET,...] The candididate-ipv6-subnets field is not available. diff --git a/gcloud/alpha/compute/interconnects/attachments/dedicated/update b/gcloud/alpha/compute/interconnects/attachments/dedicated/update index 4ac7960e7..0b2280d5a 100644 --- a/gcloud/alpha/compute/interconnects/attachments/dedicated/update +++ b/gcloud/alpha/compute/interconnects/attachments/dedicated/update @@ -59,12 +59,12 @@ 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: - 2fff:eec0:3201:0:0:0:0:1/125 + 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: - 2fff:eec0:3201:0:0:0:0:2/125 + 2001:db8::2/125 --candidate-ipv6-subnets=[IPV6_SUBNET,...] The candididate-ipv6-subnets field is not available. diff --git a/gcloud/alpha/compute/interconnects/attachments/groups/update b/gcloud/alpha/compute/interconnects/attachments/groups/update index ef087eff8..e29a73d36 100644 --- a/gcloud/alpha/compute/interconnects/attachments/groups/update +++ b/gcloud/alpha/compute/interconnects/attachments/groups/update @@ -7,7 +7,7 @@ SYNOPSIS [--attachments=[INTERCONNECT_ATTACHMENT,...]] [--description=DESCRIPTION] [--intended-availability-sla=INTENDED_AVAILABILITY_SLA] - [GCLOUD_WIDE_FLAG ...] + [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute interconnects attachments groups update is @@ -35,7 +35,8 @@ EXAMPLES $ gcloud alpha compute interconnects attachments groups update \ example-attachment-group \ - --attachments=region-1/attachment-1,region-2/attachment-2 + --attachments=region-1/attachment-1,region-2/attachment-2 \ + --update-mask=attachments Although you can add or remove member attachments using this command, it is recommended to add or remove member attachments using the add-members and @@ -56,6 +57,11 @@ FLAGS --intended-availability-sla=INTENDED_AVAILABILITY_SLA The availability SLA that the user intends this group to support. + --update-mask=UPDATE_MASK + Optional update mask to specify which fields to update. Use commas to + separate masks. If not specified, all fields present in the command + will be updated. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/interconnects/attachments/help b/gcloud/alpha/compute/interconnects/attachments/help index abd65f21a..c19426aee 100644 --- a/gcloud/alpha/compute/interconnects/attachments/help +++ b/gcloud/alpha/compute/interconnects/attachments/help @@ -23,6 +23,9 @@ GROUPS groups (ALPHA) Create or manipulate interconnect attachment groups. + l2-forwarding + (ALPHA) Create or manipulate dedicated interconnect attachments. + partner (ALPHA) Create or manipulate partner interconnect attachments. diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/add-mapping b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/add-mapping new file mode 100644 index 000000000..3f420abc2 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/add-mapping @@ -0,0 +1,73 @@ +NAME + gcloud alpha compute interconnects attachments l2-forwarding add-mapping - + add new vlan to ip mapping rule to an L2-forwarding attachment + +SYNOPSIS + gcloud alpha compute interconnects attachments l2-forwarding add-mapping + NAME --vlan-key=VLAN_KEY [--appliance-ip-address=ADDRESSES] + [--appliance-name=APPLIANCE_NAME] + [--inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS], + [innerVlanTags=INNERVLANTAGS]] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects attachments l2-forwarding + add-mapping add new vlan to ip mapping rule to an L2-forwarding attachment. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to patch. + +REQUIRED FLAGS + --vlan-key=VLAN_KEY + Desired VLAN key for L2 forwarding mapping for the attachment. If not + supplied, all mappings will be displayed. + +OPTIONAL FLAGS + --appliance-ip-address=ADDRESSES + A single IPv4 or IPv6 address used as the destination IP address for + ingress packets that match on a VLAN tag, but do not match a more + specific inner VLAN tag. + + --appliance-name=APPLIANCE_NAME + The name of the L2 appliance mapping rule. + + --inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS],[innerVlanTags=INNERVLANTAGS] + A list of mapping rules from inner VLAN tags to IP addresses. If the + inner VLAN is not explicitly mapped to an IP address range, the + applianceIpAddress is used. + + --region=REGION + Region of the interconnect attachment to patch. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/create b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/create new file mode 100644 index 000000000..ffc15c37d --- /dev/null +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/create @@ -0,0 +1,128 @@ +NAME + gcloud alpha compute interconnects attachments l2-forwarding create - + create a Compute Engine L2 forwarding interconnect attachment + +SYNOPSIS + gcloud alpha compute interconnects attachments l2-forwarding create NAME + --interconnect=INTERCONNECT --network=NETWORK + --tunnel-endpoint-ip-address=TUNNEL_ENDPOINT_IP_ADDRESS + [--bandwidth=BANDWIDTH] + [--default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS] + [--description=DESCRIPTION] [--dry-run] [--enable-admin] + [--geneve-vni=GENEVE_HEADER] [--mtu=MTU] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects attachments l2-forwarding create + is used to create a L2 forwarding interconnect attachments. An interconnect + attachment is what binds the underlying connectivity of an interconnect to + a path into and out of the customer's cloud network. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to create. + +REQUIRED FLAGS + --interconnect=INTERCONNECT + The interconnect for the interconnect attachment + + --network=NETWORK + The Google Network to use for L2 forwarding. + + --tunnel-endpoint-ip-address=TUNNEL_ENDPOINT_IP_ADDRESS + A single IPv4 or IPv6 address. This address will be used as the source + IP address for L2 forwarding packets sent to the appliances, and must + be used as the destination IP address for packets that should be sent + out through this attachment. + +OPTIONAL FLAGS + --bandwidth=BANDWIDTH + Provisioned capacity of the attachment. BANDWIDTH must be one of: + + 50m + 50 Mbit/s + 100m + 100 Mbit/s + 200m + 200 Mbit/s + 300m + 300 Mbit/s + 400m + 400 Mbit/s + 500m + 500 Mbit/s + 1g + 1 Gbit/s + 2g + 2 Gbit/s + 5g + 5 Gbit/s + 10g + 10 Gbit/s + 20g + 20 Gbit/s + 50g + 50 Gbit/s + 100g + 100 Gbit/s + + --default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS + A single IPv4 or IPv6 address used as the default destination IP when + there is no VLAN mapping result found for L2 forwarding. Unset field + indicates the unmatched packet should be dropped. + + --description=DESCRIPTION + Human-readable plain-text description of attachment. + + --dry-run + If supplied, validates the attachment without creating it. + + --enable-admin + Administrative status of the interconnect attachment. If not provided + on creation, defaults to enabled. When this is enabled, the attachment + is operational and will carry traffic. Use --no-enable-admin to disable + it. + + --geneve-vni=GENEVE_HEADER + A VNI identier for Geneve header, as defined in + https://datatracker.ietf.org/doc/html/rfc8926, used for L2 forwarding. + + --mtu=MTU + Maximum transmission unit (MTU) is the size of the largest IP packet + passing through this interconnect attachment. Must be one of 1440, + 1460, 1500, or 8896. If not specified, the value will default to 1440. + + --region=REGION + Region of the interconnect attachment to create. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/describe-mapping b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/describe-mapping new file mode 100644 index 000000000..5e3f59f35 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/describe-mapping @@ -0,0 +1,59 @@ +NAME + gcloud alpha compute interconnects attachments l2-forwarding + describe-mapping - describe a Compute Engine L2 forwarding interconnect + attachment + +SYNOPSIS + gcloud alpha compute interconnects attachments l2-forwarding + describe-mapping NAME --vlan-key=VLAN_KEY [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects attachments l2-forwarding + describe-mapping displays all data associated with Compute Engine + interconnect attachment in a project. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to describe. + +REQUIRED FLAGS + --vlan-key=VLAN_KEY + Desired VLAN key for L2 forwarding mapping for the attachment. If not + supplied, all mappings will be displayed. + +OPTIONAL FLAGS + --region=REGION + Region of the interconnect attachment to describe. If not specified, + you might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/help b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/help new file mode 100644 index 000000000..1e5c777db --- /dev/null +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/help @@ -0,0 +1,55 @@ +NAME + gcloud alpha compute interconnects attachments l2-forwarding - create or + manipulate dedicated interconnect attachments + +SYNOPSIS + gcloud alpha compute interconnects attachments l2-forwarding COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create or manipulate L2 Forwarding Interconnect attachments. + + For more information about about interconnect attachments for L2 Forwaring + Interconnect, see the documentation for L2 Forwarding interconnect + attachments + (https://cloud.google.com/network-connectivity/docs/interconnect/how-to/l2-forwarding/creating-l2-attachments). + + See also: Interconnect attachments API + (https://cloud.google.com/compute/docs/reference/rest/v1/interconnectAttachments). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-mapping + (ALPHA) Add new vlan to ip mapping rule to an L2-forwarding attachment. + + create + (ALPHA) Create a Compute Engine L2 forwarding interconnect attachment. + + describe-mapping + (ALPHA) Describe a Compute Engine L2 forwarding interconnect + attachment. + + list-mapping + (ALPHA) List Google Compute Engine interconnect attachments. + + remove-mapping + (ALPHA) Remove vlan to ip mapping rule to an L2-forwarding attachment. + + update + (ALPHA) Update a Compute Engine L2 forwarding interconnect attachment. + + update-mapping + (ALPHA) Update vlan to ip mapping rule to an L2-forwarding attachment. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/list-mapping b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/list-mapping new file mode 100644 index 000000000..d16fdaa56 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/list-mapping @@ -0,0 +1,107 @@ +NAME + gcloud alpha compute interconnects attachments l2-forwarding list-mapping - + list Google Compute Engine interconnect attachments + +SYNOPSIS + gcloud alpha compute interconnects attachments l2-forwarding list-mapping + NAME [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects attachments l2-forwarding + list-mapping displays all Google Compute Engine interconnect attachments in + a project. + + By default, interconnect attachments from all regions are listed. The + results can be narrowed down using a filter: --filter="region:( REGION ... + )". + +EXAMPLES + To list all interconnect attachments in a project in table form, run: + + $ gcloud alpha compute interconnects attachments l2-forwarding \ + list-mapping + + To list the URIs of all interconnect attachments in a project, run: + + $ gcloud alpha compute interconnects attachments l2-forwarding \ + list-mapping --uri + + To list all interconnect attachments in the us-central1 and europe-west1 + regions, run: + + $ gcloud alpha compute interconnects attachments l2-forwarding \ + list-mapping --filter="region:( us-central1 europe-west1 )" + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to describe. + +FLAGS + --region=REGION + Region of the interconnect attachment to describe. If not specified, + you might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/remove-mapping b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/remove-mapping new file mode 100644 index 000000000..be30b4234 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/remove-mapping @@ -0,0 +1,57 @@ +NAME + gcloud alpha compute interconnects attachments l2-forwarding remove-mapping + - remove vlan to ip mapping rule to an L2-forwarding attachment + +SYNOPSIS + gcloud alpha compute interconnects attachments l2-forwarding remove-mapping + NAME --vlan-key=VLAN_KEY [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects attachments l2-forwarding + remove-mapping remove vlan to ip mapping rule to an L2-forwarding + attachment. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to create. + +REQUIRED FLAGS + --vlan-key=VLAN_KEY + Desired VLAN key for L2 forwarding mapping for the attachment. If not + supplied, all mappings will be displayed. + +OPTIONAL FLAGS + --region=REGION + Region of the interconnect attachment to create. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update new file mode 100644 index 000000000..112a90c95 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update @@ -0,0 +1,141 @@ +NAME + gcloud alpha compute interconnects attachments l2-forwarding update - + update a Compute Engine L2 forwarding interconnect attachment + +SYNOPSIS + gcloud alpha compute interconnects attachments l2-forwarding update NAME + [--bandwidth=BANDWIDTH] + [--default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS] + [--description=DESCRIPTION] [--enable-admin] + [--geneve-vni=GENEVE_HEADER] [--mtu=MTU] [--region=REGION] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects attachments l2-forwarding update + is used to update interconnect attachments. An interconnect attachment is + what binds the underlying connectivity of an interconnect to a path into + and out of the customer's cloud network. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to patch. + +FLAGS + --bandwidth=BANDWIDTH + Provisioned capacity of the attachment. BANDWIDTH must be one of: + + 50m + 50 Mbit/s + 100m + 100 Mbit/s + 200m + 200 Mbit/s + 300m + 300 Mbit/s + 400m + 400 Mbit/s + 500m + 500 Mbit/s + 1g + 1 Gbit/s + 2g + 2 Gbit/s + 5g + 5 Gbit/s + 10g + 10 Gbit/s + 20g + 20 Gbit/s + 50g + 50 Gbit/s + 100g + 100 Gbit/s + + --default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS + A single IPv4 or IPv6 address used as the default destination IP when + there is no VLAN mapping result found for L2 forwarding. Unset field + indicates the unmatched packet should be dropped. + + --description=DESCRIPTION + Human-readable plain-text description of attachment. + + --enable-admin + Administrative status of the interconnect attachment. If not provided + on creation, defaults to enabled. When this is enabled, the attachment + is operational and will carry traffic. Use --no-enable-admin to disable + it. + + --geneve-vni=GENEVE_HEADER + A VNI identier for Geneve header, as defined in + https://datatracker.ietf.org/doc/html/rfc8926, used for L2 forwarding. + + --mtu=MTU + Maximum transmission unit (MTU) is the size of the largest IP packet + passing through this interconnect attachment. Must be one of 1440, + 1460, 1500, or 8896. If not specified, the value will default to 1440. + + --region=REGION + Region of the interconnect attachment to patch. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha compute interconnects attachments l2-forwarding \ + update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha compute interconnects attachments l2-forwarding \ + update --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update-mapping b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update-mapping new file mode 100644 index 000000000..915e275ce --- /dev/null +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update-mapping @@ -0,0 +1,74 @@ +NAME + gcloud alpha compute interconnects attachments l2-forwarding update-mapping + - update vlan to ip mapping rule to an L2-forwarding attachment + +SYNOPSIS + gcloud alpha compute interconnects attachments l2-forwarding update-mapping + NAME --vlan-key=VLAN_KEY [--appliance-ip-address=ADDRESSES] + [--appliance-name=APPLIANCE_NAME] + [--inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS], + [innerVlanTags=INNERVLANTAGS]] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects attachments l2-forwarding + update-mapping update vlan to ip mapping rule to an L2-forwarding + attachment. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to create. + +REQUIRED FLAGS + --vlan-key=VLAN_KEY + Desired VLAN key for L2 forwarding mapping for the attachment. If not + supplied, all mappings will be displayed. + +OPTIONAL FLAGS + --appliance-ip-address=ADDRESSES + A single IPv4 or IPv6 address used as the destination IP address for + ingress packets that match on a VLAN tag, but do not match a more + specific inner VLAN tag. + + --appliance-name=APPLIANCE_NAME + The name of the L2 appliance mapping rule. + + --inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS],[innerVlanTags=INNERVLANTAGS] + A list of mapping rules from inner VLAN tags to IP addresses. If the + inner VLAN is not explicitly mapped to an IP address range, the + applianceIpAddress is used. + + --region=REGION + Region of the interconnect attachment to create. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/attachments/partner/create b/gcloud/alpha/compute/interconnects/attachments/partner/create index 9444f65cf..2fefe4d70 100644 --- a/gcloud/alpha/compute/interconnects/attachments/partner/create +++ b/gcloud/alpha/compute/interconnects/attachments/partner/create @@ -53,22 +53,22 @@ 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: - 74.133.16.1/30 + 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: - 2fff:eec0:3201:0:0:0:0:1/125 + 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: - 74.133.16.2/30 + 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: - 2fff:eec0:3201:0:0:0:0:2/125 + 2001:db8::2/125 --description=DESCRIPTION Human-readable plain-text description of attachment. diff --git a/gcloud/alpha/compute/interconnects/attachments/partner/update b/gcloud/alpha/compute/interconnects/attachments/partner/update index ffecf7fe4..6febedf3b 100644 --- a/gcloud/alpha/compute/interconnects/attachments/partner/update +++ b/gcloud/alpha/compute/interconnects/attachments/partner/update @@ -25,12 +25,12 @@ 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: - 2fff:eec0:3201:0:0:0:0:1/125 + 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: - 2fff:eec0:3201:0:0:0:0:2/125 + 2001:db8::2/125 --description=DESCRIPTION Human-readable plain-text description of attachment. diff --git a/gcloud/alpha/compute/interconnects/create b/gcloud/alpha/compute/interconnects/create index 96298d8ab..325297067 100644 --- a/gcloud/alpha/compute/interconnects/create +++ b/gcloud/alpha/compute/interconnects/create @@ -107,6 +107,10 @@ OPTIONAL FLAGS If specified then the interconnect is created on Cross-Site Network capable hardware ports. This parameter can only be provided during interconnect INSERT and cannot be changed using interconnect PATCH. + L2_FORWARDING + If specified then the interconnect is created on L2 forwarding + capable hardware ports. This parameter can only be provided during + interconnect INSERT and cannot be changed using interconnect PATCH. MACSEC If specified then the interconnect is created on MACsec capable hardware ports. If not specified, the interconnect is created on diff --git a/gcloud/alpha/compute/interconnects/groups/create-members b/gcloud/alpha/compute/interconnects/groups/create-members index 2fa65006f..c041a7d2d 100644 --- a/gcloud/alpha/compute/interconnects/groups/create-members +++ b/gcloud/alpha/compute/interconnects/groups/create-members @@ -110,6 +110,10 @@ OPTIONAL FLAGS If specified then the interconnect is created on Cross-Site Network capable hardware ports. This parameter can only be provided during interconnect INSERT and cannot be changed using interconnect PATCH. + L2_FORWARDING + If specified then the interconnect is created on L2 forwarding + capable hardware ports. This parameter can only be provided during + interconnect INSERT and cannot be changed using interconnect PATCH. MACSEC If specified then the interconnect is created on MACsec capable hardware ports. If not specified, the interconnect is created on diff --git a/gcloud/alpha/compute/interconnects/groups/update b/gcloud/alpha/compute/interconnects/groups/update index 59b545978..5f34577a2 100644 --- a/gcloud/alpha/compute/interconnects/groups/update +++ b/gcloud/alpha/compute/interconnects/groups/update @@ -6,7 +6,8 @@ SYNOPSIS gcloud alpha compute interconnects groups update NAME [--description=DESCRIPTION] [--intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY] - [--interconnects=[INTERCONNECT,...]] [GCLOUD_WIDE_FLAG ...] + [--interconnects=[INTERCONNECT,...]] [--update-mask=UPDATE_MASK] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute interconnects groups update is used to update @@ -34,7 +35,8 @@ EXAMPLES $ gcloud alpha compute interconnects groups update \ example-interconnect-group \ - --interconnects=interconnect-1,interconnect-2 + --interconnects=interconnect-1,interconnect-2 \ + --update-mask=interconnects Although you can add or remove member interconnects using this command, it is recommended to add or remove member interconnects using the add-members @@ -55,6 +57,11 @@ FLAGS --interconnects=[INTERCONNECT,...] Member interconnects to set the interconnect group to contain. + --update-mask=UPDATE_MASK + Optional update mask to specify which fields to update. Use commas to + separate masks. If not specified, all fields present in the command + will be updated. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/network-firewall-policies/create b/gcloud/alpha/compute/network-firewall-policies/create index 348e732f8..ff372b890 100644 --- a/gcloud/alpha/compute/network-firewall-policies/create +++ b/gcloud/alpha/compute/network-firewall-policies/create @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha compute network-firewall-policies create FIREWALL_POLICY - [--description=DESCRIPTION] [--global | --region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--policy-type=POLICY_TYPE] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute network-firewall-policies create is used to @@ -33,6 +33,10 @@ FLAGS --description=DESCRIPTION An optional, textual description for the network firewall policy. + --policy-type=POLICY_TYPE + Network firewall policy type. POLICY_TYPE must be one of: VPC_POLICY, + RDMA_ROCE_POLICY. + At most one of these can be specified: --global diff --git a/gcloud/alpha/compute/org-security-policies/associations/create b/gcloud/alpha/compute/org-security-policies/associations/create index 8795b9d46..4fa39087f 100644 --- a/gcloud/alpha/compute/org-security-policies/associations/create +++ b/gcloud/alpha/compute/org-security-policies/associations/create @@ -18,6 +18,10 @@ DESCRIPTION security policy is a set of rules that controls access to various resources. + This command has billing implications. Projects in the hierarchy with + effective hierarchical security policies will be automatically enrolled + into Cloud Armor Enterprise if not already enrolled. + EXAMPLES To associate an organization security policy under folder with ID ``123456789" to folder ``987654321", run: diff --git a/gcloud/alpha/compute/preview-features/describe b/gcloud/alpha/compute/preview-features/describe index 5acd45a60..754672f27 100644 --- a/gcloud/alpha/compute/preview-features/describe +++ b/gcloud/alpha/compute/preview-features/describe @@ -50,5 +50,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute preview-features describe diff --git a/gcloud/alpha/compute/preview-features/help b/gcloud/alpha/compute/preview-features/help index 603fc690c..69d39bb98 100644 --- a/gcloud/alpha/compute/preview-features/help +++ b/gcloud/alpha/compute/preview-features/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 compute preview-features diff --git a/gcloud/alpha/compute/preview-features/list b/gcloud/alpha/compute/preview-features/list index 3e4cd1662..aa697c0a2 100644 --- a/gcloud/alpha/compute/preview-features/list +++ b/gcloud/alpha/compute/preview-features/list @@ -62,5 +62,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 compute preview-features list diff --git a/gcloud/alpha/compute/preview-features/update b/gcloud/alpha/compute/preview-features/update index 3e659c737..61718e611 100644 --- a/gcloud/alpha/compute/preview-features/update +++ b/gcloud/alpha/compute/preview-features/update @@ -51,7 +51,7 @@ REQUIRED FLAGS --rollout-plan=ROLLOUT_PLAN Use a predefined rollout plan. ROLLOUT_PLAN must be one of: - rollout-plan-fast-rollout, rollout-plan-two-day-rollout. + fast-rollout, two-day-rollout. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -69,5 +69,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute preview-features update diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index 2652bf3ee..b4a8519da 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -159,8 +159,7 @@ OPTIONAL FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the diff --git a/gcloud/alpha/compute/reservations/help b/gcloud/alpha/compute/reservations/help index 9dcfc96a7..0940e26ac 100644 --- a/gcloud/alpha/compute/reservations/help +++ b/gcloud/alpha/compute/reservations/help @@ -25,7 +25,7 @@ GROUPS (ALPHA) Manage Compute Engine reservation blocks. sub-blocks - (ALPHA) + (ALPHA) Manage Compute Engine reservation sub blocks. COMMANDS COMMAND is one of the following: diff --git a/gcloud/alpha/compute/reservations/sub-blocks/describe b/gcloud/alpha/compute/reservations/sub-blocks/describe index 16e62ab6c..60293b2f5 100644 --- a/gcloud/alpha/compute/reservations/sub-blocks/describe +++ b/gcloud/alpha/compute/reservations/sub-blocks/describe @@ -63,5 +63,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 compute reservations sub-blocks describe + + $ gcloud beta compute reservations sub-blocks describe diff --git a/gcloud/alpha/compute/reservations/sub-blocks/help b/gcloud/alpha/compute/reservations/sub-blocks/help index 44bc39455..bb60cd61c 100644 --- a/gcloud/alpha/compute/reservations/sub-blocks/help +++ b/gcloud/alpha/compute/reservations/sub-blocks/help @@ -1,5 +1,6 @@ NAME - gcloud alpha compute reservations sub-blocks - + gcloud alpha compute reservations sub-blocks - manage Compute Engine + reservation sub blocks SYNOPSIS gcloud alpha compute reservations sub-blocks COMMAND [GCLOUD_WIDE_FLAG ...] @@ -21,9 +22,17 @@ COMMANDS list (ALPHA) List Compute Engine reservation sub blocks. + perform-maintenance + (ALPHA) Perform maintenance on a reservation sub block within a + reservation. + 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 compute reservations sub-blocks + + $ gcloud beta compute reservations sub-blocks diff --git a/gcloud/alpha/compute/reservations/sub-blocks/list b/gcloud/alpha/compute/reservations/sub-blocks/list index 9c35654be..d5634a630 100644 --- a/gcloud/alpha/compute/reservations/sub-blocks/list +++ b/gcloud/alpha/compute/reservations/sub-blocks/list @@ -100,5 +100,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 compute reservations sub-blocks list + + $ gcloud beta compute reservations sub-blocks list diff --git a/gcloud/alpha/compute/reservations/sub-blocks/perform-maintenance b/gcloud/alpha/compute/reservations/sub-blocks/perform-maintenance new file mode 100644 index 000000000..8f1e4e40b --- /dev/null +++ b/gcloud/alpha/compute/reservations/sub-blocks/perform-maintenance @@ -0,0 +1,68 @@ +NAME + gcloud alpha compute reservations sub-blocks perform-maintenance - perform + maintenance on a reservation sub block within a reservation + +SYNOPSIS + gcloud alpha compute reservations sub-blocks perform-maintenance + RESERVATION --block-name=BLOCK_NAME --sub-block-name=SUB_BLOCK_NAME + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Perform maintenance on a reservation sub block within a + reservation. + +EXAMPLES + To perform maintenance on a reservation sub block in reservation exr-1 in + ZONE with block name block-1 and sub block name sub-block-1, run: + + $ gcloud alpha compute reservations sub-blocks perform-maintenance \ + exr-1 --zone=ZONE --block-name=block-1 \ + --sub-block-name=sub-block-1 + +POSITIONAL ARGUMENTS + RESERVATION + Name of the reservation to perform-maintenance. + +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. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the reservation to perform-maintenance. 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/update b/gcloud/alpha/compute/reservations/update index e4f1dd9f3..6f4f7d99c 100644 --- a/gcloud/alpha/compute/reservations/update +++ b/gcloud/alpha/compute/reservations/update @@ -8,7 +8,7 @@ SYNOPSIS [--[no-]enable-emergent-maintenance] [--remove-share-with=PROJECT,[PROJECT,...]] [--reservation-sharing-policy=RESERVATION_SHARING_POLICY] - [--share-setting=SHARE_SETTING] + [--scheduling-type=SCHEDULING_TYPE] [--share-setting=SHARE_SETTING] [--share-with=SHARE_WITH,[SHARE_WITH,...]] [--vm-count=VM_COUNT] [--zone=ZONE] [--delete-after-duration=DELETE_AFTER_DURATION @@ -78,6 +78,16 @@ FLAGS The reservation won't be shared with Google Cloud services. If you omit this flag during creation, the default value is DISALLOW_ALL. + --scheduling-type=SCHEDULING_TYPE + Maintenance for the reserved capacity. SCHEDULING_TYPE must be one of: + + GROUPED + In GROUPED mode, maintenance on all reserved instances is + synchronized. + INDEPENDENT + In INDEPENDENT mode, maintenance is not synchronized for this + reservation, and each instance has its own maintenance window. + --share-setting=SHARE_SETTING The projects that can use the reservation. SHARE_SETTING must be one of: diff --git a/gcloud/alpha/compute/resource-policies/create/workload-policy b/gcloud/alpha/compute/resource-policies/create/workload-policy index e11fb18a9..7613fdeaf 100644 --- a/gcloud/alpha/compute/resource-policies/create/workload-policy +++ b/gcloud/alpha/compute/resource-policies/create/workload-policy @@ -12,6 +12,12 @@ SYNOPSIS DESCRIPTION (ALPHA) Create a Compute Engine workload resource policy. +EXAMPLES + To create a workload policy: + + $ gcloud alpha compute resource-policies create workload-policy \ + NAME --type=TYPE + POSITIONAL ARGUMENTS NAME Name of the resource policy to operate on. @@ -89,7 +95,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 compute resource-policies create workload-policy $ gcloud beta compute resource-policies create workload-policy diff --git a/gcloud/alpha/compute/routers/create b/gcloud/alpha/compute/routers/create index 16b82a828..b43e5ca9f 100644 --- a/gcloud/alpha/compute/routers/create +++ b/gcloud/alpha/compute/routers/create @@ -8,6 +8,7 @@ SYNOPSIS [--bgp-identifier-range=BGP_IDENTIFIER_RANGE] [--description=DESCRIPTION] [--encrypted-interconnect-router] [--keepalive-interval=KEEPALIVE_INTERVAL] [--region=REGION] + [--resource-manager-tags=[KEY=VALUE,...]] [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] [GCLOUD_WIDE_FLAG ...] @@ -99,6 +100,9 @@ OPTIONAL FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the router. + --set-advertisement-groups=[GROUP,...] The list of pre-defined groups of IP ranges to dynamically advertise on this router. This list can only be specified in custom advertisement diff --git a/gcloud/alpha/compute/security-policies/update b/gcloud/alpha/compute/security-policies/update index a856b6fda..aff58f73d 100644 --- a/gcloud/alpha/compute/security-policies/update +++ b/gcloud/alpha/compute/security-policies/update @@ -14,6 +14,8 @@ SYNOPSIS [--layer7-ddos-defense-auto-deploy-load-threshold=LAYER7_DDOS_DEFENSE_AUTO_DEPLOY_LOAD_THRESHOLD] [--layer7-ddos-defense-rule-visibility=VISIBILITY_TYPE] [--log-level=LOG_LEVEL] + [--network-ddos-adaptive-protection=NETWORK_DDOS_ADAPTIVE_PROTECTION] + [--network-ddos-impacted-baseline-threshold=NETWORK_DDOS_IMPACTED_BASELINE_THRESHOLD] [--network-ddos-protection=NETWORK_DDOS_PROTECTION] [--recaptcha-redirect-site-key=RECAPTCHA_REDIRECT_SITE_KEY] [--request-body-inspection-size=REQUEST_BODY_INSPECTION_SIZE] @@ -84,6 +86,15 @@ FLAGS The level of detail to display for WAF logging. LOG_LEVEL must be one of: NORMAL, VERBOSE. + --network-ddos-adaptive-protection=NETWORK_DDOS_ADAPTIVE_PROTECTION + The DDoS adaptive protection level for network load balancing and + instances with external IPs. NETWORK_DDOS_ADAPTIVE_PROTECTION must be + one of: DISABLED, ENABLED, PREVIEW. + + --network-ddos-impacted-baseline-threshold=NETWORK_DDOS_IMPACTED_BASELINE_THRESHOLD + Threshold below which rules with collateral damage below this value + will be deployed + --network-ddos-protection=NETWORK_DDOS_PROTECTION The DDoS protection level for network load balancing and instances with external IPs. NETWORK_DDOS_PROTECTION must be one of: STANDARD, diff --git a/gcloud/alpha/compute/snapshot-groups/create b/gcloud/alpha/compute/snapshot-groups/create new file mode 100644 index 000000000..e387f752d --- /dev/null +++ b/gcloud/alpha/compute/snapshot-groups/create @@ -0,0 +1,58 @@ +NAME + gcloud alpha compute snapshot-groups create - create a Compute Engine + snapshot group + +SYNOPSIS + gcloud alpha compute snapshot-groups create NAME + --source-instant-snapshot-group=SOURCE_INSTANT_SNAPSHOT_GROUP [--async] + [--source-instant-snapshot-group-region=SOURCE_INSTANT_SNAPSHOT_GROUP_REGION | --source-instant-snapshot-group-zone=SOURCE_INSTANT_SNAPSHOT_GROUP_ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Compute Engine snapshot group. + +POSITIONAL ARGUMENTS + NAME + The name of the snapshot group. + +REQUIRED FLAGS + --source-instant-snapshot-group=SOURCE_INSTANT_SNAPSHOT_GROUP + The name or URL of the source instant snapshot group. If the name is + provided, the instant snapshot group's zone or region must be specified + with --source-instant-snapshot-group-zone or + --source-instant-snapshot-group-region accordingly. To create a + snapshot group from an instant snapshot group in a different project, + specify the full path to the instant snapshot group. If the URL is + provided, format should be: + https://www.googleapis.com/compute/v1/projects/MY-PROJECT/zones/MY-ZONE/instantSnapshotGroups/MY-INSTANT-SNAPSHOT-GROUP + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + At most one of these can be specified: + + --source-instant-snapshot-group-region=SOURCE_INSTANT_SNAPSHOT_GROUP_REGION + Region of the source instant snapshot group to operate on. Overrides + the default compute/region property value for this command + invocation. + + --source-instant-snapshot-group-zone=SOURCE_INSTANT_SNAPSHOT_GROUP_ZONE + Zone of the source instant snapshot group to operate on. 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. + diff --git a/gcloud/alpha/compute/snapshot-groups/delete b/gcloud/alpha/compute/snapshot-groups/delete new file mode 100644 index 000000000..7a45c4931 --- /dev/null +++ b/gcloud/alpha/compute/snapshot-groups/delete @@ -0,0 +1,36 @@ +NAME + gcloud alpha compute snapshot-groups delete - delete Compute Engine + snapshot groups + +SYNOPSIS + gcloud alpha compute snapshot-groups delete SNAPSHOT_GROUP_NAME + [SNAPSHOT_GROUP_NAME ...] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute snapshot-groups delete deletes one or more + Compute Engine snapshot groups. + +EXAMPLES + To delete Compute Engine snapshot groups with the names 'sg-1' and 'sg-2', + run: + + $ gcloud alpha compute snapshot-groups delete sg-1 sg-2 + +POSITIONAL ARGUMENTS + SNAPSHOT_GROUP_NAME [SNAPSHOT_GROUP_NAME ...] + Names of the snapshot-groups to delete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/snapshot-groups/describe b/gcloud/alpha/compute/snapshot-groups/describe new file mode 100644 index 000000000..5d5791df4 --- /dev/null +++ b/gcloud/alpha/compute/snapshot-groups/describe @@ -0,0 +1,29 @@ +NAME + gcloud alpha compute snapshot-groups describe - describe a Compute Engine + snapshot group + +SYNOPSIS + gcloud alpha compute snapshot-groups describe SNAPSHOT_GROUP_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Compute Engine snapshot group. + +POSITIONAL ARGUMENTS + SNAPSHOT_GROUP_NAME + Name of the snapshot-group to describe. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/snapshot-groups/help b/gcloud/alpha/compute/snapshot-groups/help new file mode 100644 index 000000000..304b691c1 --- /dev/null +++ b/gcloud/alpha/compute/snapshot-groups/help @@ -0,0 +1,36 @@ +NAME + gcloud alpha compute snapshot-groups - create, list, describe and delete + Compute Engine snapshot groups + +SYNOPSIS + gcloud alpha compute snapshot-groups COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create, list, describe and delete Compute Engine snapshot groups. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a Compute Engine snapshot group. + + delete + (ALPHA) Delete Compute Engine snapshot groups. + + describe + (ALPHA) Describe a Compute Engine snapshot group. + + list + (ALPHA) List Google Compute Engine snapshot groups. + +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/snapshot-groups/list b/gcloud/alpha/compute/snapshot-groups/list new file mode 100644 index 000000000..9d03ef6d1 --- /dev/null +++ b/gcloud/alpha/compute/snapshot-groups/list @@ -0,0 +1,68 @@ +NAME + gcloud alpha compute snapshot-groups list - list Google Compute Engine + snapshot groups + +SYNOPSIS + gcloud alpha compute snapshot-groups list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute snapshot-groups list displays all Google + Compute Engine snapshot groups in a project. + +EXAMPLES + To list all snapshot groups in a project in table form, run: + + $ gcloud alpha compute snapshot-groups list + + To list the URIs of all snapshot groups in a project, run: + + $ gcloud alpha compute snapshot-groups list --uri + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/config/get b/gcloud/alpha/config/get index 70eff43df..7bc2f3bf4 100644 --- a/gcloud/alpha/config/get +++ b/gcloud/alpha/config/get @@ -486,13 +486,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -501,6 +502,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index b19b38387..b0e147e11 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -518,13 +518,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -533,6 +534,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index 2a7e9c966..25b586f0b 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -530,13 +530,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -545,6 +546,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index fb4e5e8ab..57e3689e3 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -533,13 +533,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -548,6 +549,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index ec45af521..177ac20ef 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -494,13 +494,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -509,6 +510,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/alpha/container/ai/help b/gcloud/alpha/container/ai/help index bbe5f497a..5f523bd2d 100644 --- a/gcloud/alpha/container/ai/help +++ b/gcloud/alpha/container/ai/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + profiles + (ALPHA) Quickstart engine for GKE AI workloads. + recommender (ALPHA) Recommendation engine for GKE AI workloads. diff --git a/gcloud/alpha/container/ai/profiles/accelerators/help b/gcloud/alpha/container/ai/profiles/accelerators/help new file mode 100644 index 000000000..4518527e5 --- /dev/null +++ b/gcloud/alpha/container/ai/profiles/accelerators/help @@ -0,0 +1,28 @@ +NAME + gcloud alpha container ai profiles accelerators - manage supported + accelerators for GKE Inference Quickstart + +SYNOPSIS + gcloud alpha container ai profiles accelerators COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage supported accelerators 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 + (ALPHA) List compatible accelerator profiles. + +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/ai/profiles/accelerators/list b/gcloud/alpha/container/ai/profiles/accelerators/list new file mode 100644 index 000000000..ba8a01c0e --- /dev/null +++ b/gcloud/alpha/container/ai/profiles/accelerators/list @@ -0,0 +1,97 @@ +NAME + gcloud alpha container ai profiles accelerators list - list compatible + accelerator profiles + +SYNOPSIS + gcloud alpha container ai profiles accelerators list --model=MODEL + [--format=FORMAT; default="table"] + [--max-ntpot-milliseconds=MAX_NTPOT_MILLISECONDS] + [--model-server=MODEL_SERVER] + [--model-server-version=MODEL_SERVER_VERSION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command lists all supported accelerators with their + performance details. By default, the supported accelerators are displayed + in a table format with select information for each accelerator. To see all + details, use --format=yaml. + + To get supported model, model servers, and model server versions, run + gcloud alpha container ai profiles models list, gcloud alpha container ai + profiles model-servers list, and gcloud alpha container ai profiles + model-server-versions list. Alternatively, run gcloud alpha container ai + profiles model-and-server-combinations list to get all supported model and + server combinations. + +REQUIRED FLAGS + --model=MODEL + The model. + +FLAGS + --format=FORMAT; default="table" + The output format. Default is table, which displays select information + in a table format. Use --format=yaml to display all details. FORMAT + must be one of: table, yaml. + + --max-ntpot-milliseconds=MAX_NTPOT_MILLISECONDS + The maximum normalized time per output token (NTPOT) in milliseconds. + NTPOT is measured as the request_latency / output_tokens. If this field + is set, the command will only return accelerators that can meet the + target ntpot milliseconds and display their throughput performance at + the target latency. Otherwise, the command will return all accelerators + and display their highest throughput performance. + + --model-server=MODEL_SERVER + The model server. If not specified, this defaults to any model server. + + --model-server-version=MODEL_SERVER_VERSION + The model server version. If not specified, this defaults to the latest + version. + +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/ai/profiles/help b/gcloud/alpha/container/ai/profiles/help new file mode 100644 index 000000000..da7110667 --- /dev/null +++ b/gcloud/alpha/container/ai/profiles/help @@ -0,0 +1,51 @@ +NAME + gcloud alpha container ai profiles - quickstart engine for GKE AI workloads + +SYNOPSIS + gcloud alpha container ai profiles GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The GKE Inference Quickstart helps simplify deploying AI inference + on Google Kubernetes Engine (GKE). It provides tailored profiles based on + Google's internal benchmarks. Provide inputs like your preferred + open-source model (e.g. Llama, Gemma, or Mistral) and your application's + performance target. Based on these inputs, the quickstart generates + accelerator choices with performance metrics, and detailed, ready-to-deploy + profiles for compute, load balancing, and autoscaling. These profiles are + provided as standard Kubernetes YAML manifests, which you can deploy or + modify. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + accelerators + (ALPHA) Manage supported accelerators for GKE Inference Quickstart. + + manifests + (ALPHA) Generate optimized Kubernetes manifests. + + model-and-server-combinations + (ALPHA) Manage supported model and model servers for GKE Inference + Quickstart. + + model-server-versions + (ALPHA) Manage supported model server versions for GKE Inference + Quickstart. + + model-servers + (ALPHA) Manage supported model servers for GKE Inference Quickstart. + + models + (ALPHA) Manage supported models for GKE Inference Quickstart. + +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/ai/profiles/manifests/create b/gcloud/alpha/container/ai/profiles/manifests/create new file mode 100644 index 000000000..74ff267b2 --- /dev/null +++ b/gcloud/alpha/container/ai/profiles/manifests/create @@ -0,0 +1,70 @@ +NAME + gcloud alpha container ai profiles manifests create - generate + ready-to-deploy Kubernetes manifests with compute, load balancing, and + autoscaling capabilities + +SYNOPSIS + gcloud alpha container ai profiles manifests create + --accelerator-type=ACCELERATOR_TYPE --model=MODEL + --model-server=MODEL_SERVER + [--model-server-version=MODEL_SERVER_VERSION] [--namespace=NAMESPACE] + [--output=OUTPUT; default="all"] [--output-path=OUTPUT_PATH] + [--target-ntpot-milliseconds=TARGET_NTPOT_MILLISECONDS] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) To get supported model, model servers, and model server versions, + run gcloud alpha container ai profiles model-and-server-combinations list. + To get supported accelerators with their performance metrics, run gcloud + alpha container ai profiles accelerators list. + +REQUIRED FLAGS + --accelerator-type=ACCELERATOR_TYPE + The accelerator type. + + --model=MODEL + The model. + + --model-server=MODEL_SERVER + The model server. + +OPTIONAL FLAGS + --model-server-version=MODEL_SERVER_VERSION + The model server version. If not specified, this defaults to the latest + version. + + --namespace=NAMESPACE + The namespace to deploy the manifests in. Default namespace is + 'default'. + + --output=OUTPUT; default="all" + The output to display. Default is all. OUTPUT must be one of: manifest, + comments, all. + + --output-path=OUTPUT_PATH + The path to save the output to. If not specified, output to the + terminal. + + --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 + set, the manifests 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 NTPOT below the + specified threshold. If the provided target-ntpot-milliseconds is too + low to achieve, the HPA manifest will not be generated. + +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/ai/profiles/manifests/help b/gcloud/alpha/container/ai/profiles/manifests/help new file mode 100644 index 000000000..afb6ee9cf --- /dev/null +++ b/gcloud/alpha/container/ai/profiles/manifests/help @@ -0,0 +1,28 @@ +NAME + gcloud alpha container ai profiles manifests - generate optimized + Kubernetes manifests + +SYNOPSIS + gcloud alpha container ai profiles manifests COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Generate optimized Kubernetes manifests. + +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) Generate ready-to-deploy Kubernetes manifests with compute, + load balancing, and autoscaling capabilities. + +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/ai/profiles/model-and-server-combinations/help b/gcloud/alpha/container/ai/profiles/model-and-server-combinations/help new file mode 100644 index 000000000..5458471ed --- /dev/null +++ b/gcloud/alpha/container/ai/profiles/model-and-server-combinations/help @@ -0,0 +1,29 @@ +NAME + gcloud alpha container ai profiles model-and-server-combinations - manage + supported model and model servers for GKE Inference Quickstart + +SYNOPSIS + gcloud alpha container ai profiles model-and-server-combinations COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage supported model and model servers 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 + (ALPHA) List supported model and server combinations. + +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/ai/profiles/model-and-server-combinations/list b/gcloud/alpha/container/ai/profiles/model-and-server-combinations/list new file mode 100644 index 000000000..296775158 --- /dev/null +++ b/gcloud/alpha/container/ai/profiles/model-and-server-combinations/list @@ -0,0 +1,72 @@ +NAME + gcloud alpha container ai profiles model-and-server-combinations list - + list supported model and server combinations + +SYNOPSIS + gcloud alpha container ai profiles model-and-server-combinations list + [--model=MODEL] [--model-server=MODEL_SERVER] + [--model-server-version=MODEL_SERVER_VERSION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command lists all supported model, model server, and model + server version combinations. + +FLAGS + --model=MODEL + The model. If not specified, this defaults to any model. + + --model-server=MODEL_SERVER + The model server. If not specified, this defaults to any model server. + + --model-server-version=MODEL_SERVER_VERSION + The model server version. If not specified, this defaults to the any + model server version. + +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/ai/profiles/model-server-versions/help b/gcloud/alpha/container/ai/profiles/model-server-versions/help new file mode 100644 index 000000000..dfa97a43d --- /dev/null +++ b/gcloud/alpha/container/ai/profiles/model-server-versions/help @@ -0,0 +1,29 @@ +NAME + gcloud alpha container ai profiles model-server-versions - manage supported + model server versions for GKE Inference Quickstart + +SYNOPSIS + gcloud alpha container ai profiles model-server-versions COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage supported model server 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 + (ALPHA) List supported model server versions. + +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/ai/profiles/model-server-versions/list b/gcloud/alpha/container/ai/profiles/model-server-versions/list new file mode 100644 index 000000000..511323f74 --- /dev/null +++ b/gcloud/alpha/container/ai/profiles/model-server-versions/list @@ -0,0 +1,70 @@ +NAME + gcloud alpha container ai profiles model-server-versions list - list + supported model server versions + +SYNOPSIS + gcloud alpha container ai profiles model-server-versions list --model=MODEL + --model-server=MODEL_SERVER [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) To get supported model and model servers, run gcloud alpha + container ai profiles models list and gcloud alpha container ai profiles + model-servers list. Alternatively, run gcloud alpha container ai profiles + model-and-server-combinations list to get all supported model and server + combinations. + +REQUIRED FLAGS + --model=MODEL + The model. + + --model-server=MODEL_SERVER + The model server. If not specified, this defaults to any model server. + +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/ai/profiles/model-servers/help b/gcloud/alpha/container/ai/profiles/model-servers/help new file mode 100644 index 000000000..6a29ab9d5 --- /dev/null +++ b/gcloud/alpha/container/ai/profiles/model-servers/help @@ -0,0 +1,28 @@ +NAME + gcloud alpha container ai profiles model-servers - manage supported model + servers for GKE Inference Quickstart + +SYNOPSIS + gcloud alpha container ai profiles model-servers COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage supported model servers 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 + (ALPHA) List supported model servers for a given model. + +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/ai/profiles/model-servers/list b/gcloud/alpha/container/ai/profiles/model-servers/list new file mode 100644 index 000000000..9434e9b6e --- /dev/null +++ b/gcloud/alpha/container/ai/profiles/model-servers/list @@ -0,0 +1,64 @@ +NAME + gcloud alpha container ai profiles model-servers list - list supported + model servers for a given model + +SYNOPSIS + gcloud alpha container ai profiles model-servers list --model=MODEL + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) To get supported models, run gcloud alpha container ai profiles + models list or to get all supported model and server combinations, run + gcloud alpha container ai profiles model-and-server-combinations list. + +REQUIRED FLAGS + --model=MODEL + The model. + +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/anthos/config/sync/resources/help b/gcloud/alpha/container/ai/profiles/models/help similarity index 61% rename from gcloud/alpha/anthos/config/sync/resources/help rename to gcloud/alpha/container/ai/profiles/models/help index 6081d2958..952e402a2 100644 --- a/gcloud/alpha/anthos/config/sync/resources/help +++ b/gcloud/alpha/container/ai/profiles/models/help @@ -1,12 +1,12 @@ NAME - gcloud alpha anthos config sync resources - anthos config sync resources - command group + gcloud alpha container ai profiles models - manage supported models for GKE + Inference Quickstart SYNOPSIS - gcloud alpha anthos config sync resources COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha container ai profiles models COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Anthos config sync resources command group. + (ALPHA) Manage supported models for GKE Inference Quickstart. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,7 +17,7 @@ COMMANDS COMMAND is one of the following: list - (ALPHA) List resources and their status that are synced by Config Sync. + (ALPHA) List supported models. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/container/ai/profiles/models/list b/gcloud/alpha/container/ai/profiles/models/list new file mode 100644 index 000000000..3ef529ccf --- /dev/null +++ b/gcloud/alpha/container/ai/profiles/models/list @@ -0,0 +1,57 @@ +NAME + gcloud alpha container ai profiles models list - list supported models + +SYNOPSIS + gcloud alpha container ai profiles models list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List supported models. + +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/backup-channels/create b/gcloud/alpha/container/backup-restore/backup-channels/create index bfe5b9fef..2dea7cd9a 100644 --- a/gcloud/alpha/container/backup-restore/backup-channels/create +++ b/gcloud/alpha/container/backup-restore/backup-channels/create @@ -14,11 +14,11 @@ DESCRIPTION EXAMPLES To create a backup channel my-backup-channel in project my-project in - location us-central1 with destination project projects/1234567890, run: + location us-central1 with destination project projects/backup-project, run: $ gcloud alpha container backup-restore backup-channels create \ my-backup-channel --project=my-project --location=us-central1 \ - --destination-project=projects/1234567890 + --destination-project=projects/backup-project POSITIONAL ARGUMENTS Backup channel resource - Name of the backup channel to create. Once the @@ -62,8 +62,8 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --destination-project=DESTINATION_PROJECT The project where Backups are allowed to be created. The format is - projects/{project}. Currently, {project} can only be the project - number. e.g. projects/1234567890. + projects/{project}. Project can be project number or project ID. E.g. + projects/1234567890 or projects/my-project. OPTIONAL FLAGS --async diff --git a/gcloud/alpha/container/backup-restore/restore-channels/create b/gcloud/alpha/container/backup-restore/restore-channels/create index 4c2b95e41..514a980d7 100644 --- a/gcloud/alpha/container/backup-restore/restore-channels/create +++ b/gcloud/alpha/container/backup-restore/restore-channels/create @@ -14,11 +14,12 @@ DESCRIPTION EXAMPLES To create a restore channel my-restore-channel in project my-project in - location us-central1 with destination project projects/1234567890, run: + location us-central1 with destination project projects/restore-project, + run: $ gcloud alpha container backup-restore restore-channels create \ my-restore-channel --project=my-project --location=us-central1 \ - --destination-project=projects/1234567890 + --destination-project=projects/restore-project POSITIONAL ARGUMENTS Restore channel resource - Name of the restore channel to create. Once the @@ -62,8 +63,8 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --destination-project=DESTINATION_PROJECT The project where Restores are allowed to be created. The format is - projects/{project}. Currently, {project} can only be the project - number. e.g. projects/1234567890. + projects/{project}. Project can be project number or project ID. E.g. + projects/1234567890 or projects/my-project. OPTIONAL FLAGS --async diff --git a/gcloud/alpha/container/clusters/check-autopilot-compatibility b/gcloud/alpha/container/clusters/check-autopilot-compatibility index e3477bc32..6041017c3 100644 --- a/gcloud/alpha/container/clusters/check-autopilot-compatibility +++ b/gcloud/alpha/container/clusters/check-autopilot-compatibility @@ -11,6 +11,13 @@ SYNOPSIS DESCRIPTION (ALPHA) Check autopilot compatibility of a running cluster. + For clusters with GKE version 1.31.6-gke.1027000 or later, you must enable + the control plane component that performs the check by running the gcloud + container clusters update command with the + `--enable-autopilot-compatiblity-auditing` + (https://cloud.google.com/sdk/gcloud/reference/container/clusters/update#--%5Bno-%5Denable-autopilot-compatibility-auditing) + flag. + EXAMPLES To check autopilot compatibility of an existing cluster, run: diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 204f385dc..d34f3494d 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -10,6 +10,8 @@ SYNOPSIS gpu-sharing-strategy=GPU_SHARING_STRATEGY, max-shared-clients-per-gpu=MAX_SHARED_CLIENTS_PER_GPU],...]] [--addons=[ADDON[=ENABLED|DISABLED],...]] [--allow-route-overlap] + [--alpha-cluster-feature-gates=[FEATURE=true|false,...]] + [--anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG] [--async] [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] [--autoprovisioning-enable-insecure-kubelet-readonly-port] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] @@ -73,6 +75,7 @@ SYNOPSIS [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] [--notification-config=[pubsub=ENABLED|DISABLED, pubsub-topic=TOPIC,...]] [--num-nodes=NUM_NODES; default=3] + [--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT] [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] [--preemptible] [--private-endpoint-subnetwork=NAME] [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] @@ -238,6 +241,28 @@ FLAGS Must be used in conjunction with '--enable-ip-alias' or '--no-enable-ip-alias'. + --alpha-cluster-feature-gates=[FEATURE=true|false,...] + Selectively enable or disable Kubernetes alpha and beta + kubernetesfeature gates on alpha GKE cluster. Alpha clusters are not + covered by the Kubernetes Engine SLA and should not be used for + production workloads. + + --anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG + Enable or restrict anonymous access to the cluster. When enabled, + anonymous users will be authenticated as system:anonymous with the + group system:unauthenticated. Limiting access restricts anonymous + access to only the health check endpoints /readyz, /livez, and + /healthz. + + ANONYMOUS_AUTHENTICATION_CONFIG must be one of: + + ENABLED + 'ENABLED' enables anonymous calls. + LIMITED + 'LIMITED' restricts anonymous access to the cluster. Only calls to + the health check endpoints are allowed anonymously, all other calls + will be rejected. + --async Return immediately, without waiting for the operation in progress to complete. @@ -1111,6 +1136,19 @@ FLAGS --num-nodes=NUM_NODES; default=3 The number of nodes to be created in each of the cluster's zones. + --performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT + Sets the Performance Monitoring Unit level. Valid values are + architectural, standard and enhanced. PERFORMANCE_MONITORING_UNIT must + be one of: + + architectural + Enables architectural PMU events tied to non last level cache (LLC) + events. + enhanced + Enables most documented core/L2 and LLC PMU events. + standard + Enables most documented core/L2 PMU events. + --placement-policy=PLACEMENT_POLICY Indicates the desired resource policy to use. diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index 7c8399677..a3713a57e 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -3,8 +3,9 @@ NAME for running containers SYNOPSIS - gcloud alpha container clusters create-auto NAME [--async] - [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] + gcloud alpha container clusters create-auto NAME + [--anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG] + [--async] [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] [--autoprovisioning-enable-insecure-kubelet-readonly-port] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] @@ -74,6 +75,22 @@ POSITIONAL ARGUMENTS 40 characters. FLAGS + --anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG + Enable or restrict anonymous access to the cluster. When enabled, + anonymous users will be authenticated as system:anonymous with the + group system:unauthenticated. Limiting access restricts anonymous + access to only the health check endpoints /readyz, /livez, and + /healthz. + + ANONYMOUS_AUTHENTICATION_CONFIG must be one of: + + ENABLED + 'ENABLED' enables anonymous calls. + LIMITED + 'LIMITED' restricts anonymous access to the cluster. Only calls to + the health check endpoints are allowed anonymously, all other calls + will be rejected. + --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index c57ff0950..657817ce4 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha container clusters update NAME - (--autoprovisioning-cgroup-mode=AUTOPROVISIONING_CGROUP_MODE + (--anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG + | --autoprovisioning-cgroup-mode=AUTOPROVISIONING_CGROUP_MODE | --autoprovisioning-enable-insecure-kubelet-readonly-port | --autoprovisioning-network-tags=[TAGS,...] | --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] @@ -138,6 +139,22 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Exactly one of these must be specified: + --anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG + Enable or restrict anonymous access to the cluster. When enabled, + anonymous users will be authenticated as system:anonymous with the + group system:unauthenticated. Limiting access restricts anonymous + access to only the health check endpoints /readyz, /livez, and + /healthz. + + ANONYMOUS_AUTHENTICATION_CONFIG must be one of: + + ENABLED + 'ENABLED' enables anonymous calls. + LIMITED + 'LIMITED' restricts anonymous access to the cluster. Only calls + to the health check endpoints are allowed anonymously, all other + calls will be rejected. + --autoprovisioning-cgroup-mode=AUTOPROVISIONING_CGROUP_MODE Sets the cgroup mode for auto-provisioned nodes. @@ -312,10 +329,16 @@ REQUIRED FLAGS https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity --[no-]enable-autopilot-compatibility-auditing - Enables the Autopilot Compatibility Auditing Feature. See - https://cloud.google.com/sdk/gcloud/reference/container/clusters/check-autopilot-compatibility. - Only applicable to clusters with version >= 1.32. Use - --enable-autopilot-compatibility-auditing to enable and + Lets you run the gcloud container clusters + check-autopilot-compatibility + (https://cloud.google.com/sdk/gcloud/reference/container/clusters/check-autopilot-compatibility) + command to check whether your workloads are compatible with Autopilot + mode. This flag is only applicable to clusters that run version + 1.31.6-gke.1027000 or later. + + Note: This flag causes a control plane restart. + + Use --enable-autopilot-compatibility-auditing to enable and --no-enable-autopilot-compatibility-auditing to disable. --enable-autoscaling diff --git a/gcloud/alpha/container/fleet/packages/create b/gcloud/alpha/container/fleet/packages/create index 58c9ba553..44cad46b6 100644 --- a/gcloud/alpha/container/fleet/packages/create +++ b/gcloud/alpha/container/fleet/packages/create @@ -39,5 +39,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 container fleet packages create diff --git a/gcloud/alpha/container/fleet/packages/delete b/gcloud/alpha/container/fleet/packages/delete index e53106322..9c7093f2e 100644 --- a/gcloud/alpha/container/fleet/packages/delete +++ b/gcloud/alpha/container/fleet/packages/delete @@ -64,5 +64,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 container fleet packages delete diff --git a/gcloud/alpha/container/fleet/packages/describe b/gcloud/alpha/container/fleet/packages/describe index b57914703..ce9670533 100644 --- a/gcloud/alpha/container/fleet/packages/describe +++ b/gcloud/alpha/container/fleet/packages/describe @@ -64,5 +64,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 container fleet packages describe diff --git a/gcloud/alpha/container/fleet/packages/help b/gcloud/alpha/container/fleet/packages/help index 646ba04ec..1649f7cf2 100644 --- a/gcloud/alpha/container/fleet/packages/help +++ b/gcloud/alpha/container/fleet/packages/help @@ -44,5 +44,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 container fleet packages diff --git a/gcloud/alpha/container/fleet/packages/list b/gcloud/alpha/container/fleet/packages/list index 118eb5689..0fda9ed93 100644 --- a/gcloud/alpha/container/fleet/packages/list +++ b/gcloud/alpha/container/fleet/packages/list @@ -63,5 +63,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 container fleet packages list diff --git a/gcloud/alpha/container/fleet/packages/resource-bundles/create b/gcloud/alpha/container/fleet/packages/resource-bundles/create index 9061f0c9c..d8c5a8e78 100644 --- a/gcloud/alpha/container/fleet/packages/resource-bundles/create +++ b/gcloud/alpha/container/fleet/packages/resource-bundles/create @@ -39,5 +39,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 container fleet packages resource-bundles create diff --git a/gcloud/alpha/container/fleet/packages/resource-bundles/delete b/gcloud/alpha/container/fleet/packages/resource-bundles/delete index b70cca8bb..edc190a7b 100644 --- a/gcloud/alpha/container/fleet/packages/resource-bundles/delete +++ b/gcloud/alpha/container/fleet/packages/resource-bundles/delete @@ -39,5 +39,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 container fleet packages resource-bundles delete diff --git a/gcloud/alpha/container/fleet/packages/resource-bundles/describe b/gcloud/alpha/container/fleet/packages/resource-bundles/describe index f82db0635..a4daa12a9 100644 --- a/gcloud/alpha/container/fleet/packages/resource-bundles/describe +++ b/gcloud/alpha/container/fleet/packages/resource-bundles/describe @@ -35,5 +35,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 container fleet packages resource-bundles describe diff --git a/gcloud/alpha/container/fleet/packages/resource-bundles/help b/gcloud/alpha/container/fleet/packages/resource-bundles/help index 7c8413116..bb609c613 100644 --- a/gcloud/alpha/container/fleet/packages/resource-bundles/help +++ b/gcloud/alpha/container/fleet/packages/resource-bundles/help @@ -43,5 +43,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 container fleet packages resource-bundles diff --git a/gcloud/alpha/container/fleet/packages/resource-bundles/list b/gcloud/alpha/container/fleet/packages/resource-bundles/list index 354107ee9..bc9323b56 100644 --- a/gcloud/alpha/container/fleet/packages/resource-bundles/list +++ b/gcloud/alpha/container/fleet/packages/resource-bundles/list @@ -65,5 +65,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 container fleet packages resource-bundles list diff --git a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/create b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/create index 3b07548de..75481b5ca 100644 --- a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/create +++ b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/create @@ -68,5 +68,8 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta container fleet packages resource-bundles releases \ + create diff --git a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/delete b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/delete index fbcf6b7f2..221b8efa3 100644 --- a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/delete +++ b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/delete @@ -45,5 +45,8 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta container fleet packages resource-bundles releases \ + delete diff --git a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/describe b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/describe index a3b164323..91028ae9f 100644 --- a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/describe +++ b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/describe @@ -41,5 +41,8 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta container fleet packages resource-bundles releases \ + describe diff --git a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/help b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/help index c06ddd674..64df1a2b1 100644 --- a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/help +++ b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/help @@ -37,5 +37,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 container fleet packages resource-bundles releases diff --git a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/list b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/list index 525a84f98..dd61f671f 100644 --- a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/list +++ b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/list @@ -69,5 +69,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta container fleet packages resource-bundles releases list diff --git a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/update b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/update index 4eb89409b..2737c80a3 100644 --- a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/update +++ b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/update @@ -5,8 +5,7 @@ NAME SYNOPSIS gcloud alpha container fleet packages resource-bundles releases update RELEASE --resource-bundle=RESOURCE_BUNDLE [--lifecycle=LIFECYCLE] - [--location=LOCATION] [--source=SOURCE] - [--variants-pattern=VARIANTS_PATTERN] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update Package Rollouts Release. @@ -15,20 +14,8 @@ EXAMPLES To update Release v1.0.0 for Resource Bundle my-bundle in us-central1, run: $ gcloud alpha container fleet packages resource-bundles releases \ - update --version=v1.0.0 --resource-bundle=my-bundle \ - --source=manifest.yaml - - To update a Release with multiple variants in one directory, run: - - $ gcloud alpha container fleet packages resource-bundles releases \ - update --version=v1.0.0 --resource-bundle=my-bundle \ - --source=/manifests/ --variants-pattern=manifest-*.yaml - - To update a Release with multiple variants across multiple directories, ex: - - $ gcloud alpha container fleet packages resource-bundles releases \ - update --version=v1.0.0 --resource-bundle=my-bundle \ - --source=/manifests/ --variants-pattern=dir-*/ + update --version=v1.0.0 --resource-bundle=my-bundle \ + --lifecycle=PUBLISHED POSITIONAL ARGUMENTS RELEASE @@ -45,18 +32,6 @@ OPTIONAL FLAGS --location=LOCATION Google Cloud zone or region. - --source=SOURCE - Source file or directory to update the Release from. e.g. - --source=manifest.yaml, --source=/manifests-dir/ Can optionally be - paired with the --variants-pattern arg to create multiple variants of a - Release. - - --variants-pattern=VARIANTS_PATTERN - Glob pattern to Variants of the Release, to be paired with the --source - arg. ex: --source=/manifests-dir/ --variants-pattern=**, - --source=/manifests-dir/ --variants-pattern=us-*.yaml, - --source=/manifests/dir/ --variants-pattern=*/*.yaml - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -69,5 +44,8 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta container fleet packages resource-bundles releases \ + update diff --git a/gcloud/alpha/container/fleet/packages/resource-bundles/update b/gcloud/alpha/container/fleet/packages/resource-bundles/update index f173c3c46..1f1c3418c 100644 --- a/gcloud/alpha/container/fleet/packages/resource-bundles/update +++ b/gcloud/alpha/container/fleet/packages/resource-bundles/update @@ -39,5 +39,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 container fleet packages resource-bundles update diff --git a/gcloud/alpha/container/fleet/packages/rollouts/abort b/gcloud/alpha/container/fleet/packages/rollouts/abort index 6c4c728bd..7691f5255 100644 --- a/gcloud/alpha/container/fleet/packages/rollouts/abort +++ b/gcloud/alpha/container/fleet/packages/rollouts/abort @@ -70,5 +70,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 container fleet packages rollouts abort diff --git a/gcloud/alpha/container/fleet/packages/rollouts/describe b/gcloud/alpha/container/fleet/packages/rollouts/describe index ff7cf3f61..29a54d006 100644 --- a/gcloud/alpha/container/fleet/packages/rollouts/describe +++ b/gcloud/alpha/container/fleet/packages/rollouts/describe @@ -43,5 +43,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 container fleet packages rollouts describe diff --git a/gcloud/alpha/container/fleet/packages/rollouts/help b/gcloud/alpha/container/fleet/packages/rollouts/help index e62409f24..b9401afda 100644 --- a/gcloud/alpha/container/fleet/packages/rollouts/help +++ b/gcloud/alpha/container/fleet/packages/rollouts/help @@ -36,5 +36,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta container fleet packages rollouts diff --git a/gcloud/alpha/container/fleet/packages/rollouts/list b/gcloud/alpha/container/fleet/packages/rollouts/list index d8626de8c..ae74cda40 100644 --- a/gcloud/alpha/container/fleet/packages/rollouts/list +++ b/gcloud/alpha/container/fleet/packages/rollouts/list @@ -73,5 +73,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 container fleet packages rollouts list diff --git a/gcloud/alpha/container/fleet/packages/rollouts/resume b/gcloud/alpha/container/fleet/packages/rollouts/resume index d53cb07b3..31425a59d 100644 --- a/gcloud/alpha/container/fleet/packages/rollouts/resume +++ b/gcloud/alpha/container/fleet/packages/rollouts/resume @@ -70,5 +70,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 container fleet packages rollouts resume diff --git a/gcloud/alpha/container/fleet/packages/rollouts/suspend b/gcloud/alpha/container/fleet/packages/rollouts/suspend index 61e8ab525..39ec85d53 100644 --- a/gcloud/alpha/container/fleet/packages/rollouts/suspend +++ b/gcloud/alpha/container/fleet/packages/rollouts/suspend @@ -70,5 +70,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 container fleet packages rollouts suspend diff --git a/gcloud/alpha/container/fleet/packages/update b/gcloud/alpha/container/fleet/packages/update index 6256a62bf..880c88033 100644 --- a/gcloud/alpha/container/fleet/packages/update +++ b/gcloud/alpha/container/fleet/packages/update @@ -64,5 +64,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 container fleet packages update diff --git a/gcloud/alpha/container/fleet/rbacrolebindingactuation/describe b/gcloud/alpha/container/fleet/rbacrolebindingactuation/describe index 8096d6a1a..266805a67 100644 --- a/gcloud/alpha/container/fleet/rbacrolebindingactuation/describe +++ b/gcloud/alpha/container/fleet/rbacrolebindingactuation/describe @@ -18,5 +18,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 container fleet rbacrolebindingactuation describe + + $ gcloud beta container fleet rbacrolebindingactuation describe diff --git a/gcloud/alpha/container/fleet/rbacrolebindingactuation/help b/gcloud/alpha/container/fleet/rbacrolebindingactuation/help index 6f0e909c9..63678ee96 100644 --- a/gcloud/alpha/container/fleet/rbacrolebindingactuation/help +++ b/gcloud/alpha/container/fleet/rbacrolebindingactuation/help @@ -28,5 +28,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 container fleet rbacrolebindingactuation + + $ gcloud beta container fleet rbacrolebindingactuation diff --git a/gcloud/alpha/container/fleet/rbacrolebindingactuation/update b/gcloud/alpha/container/fleet/rbacrolebindingactuation/update index 51190c866..23f6973d6 100644 --- a/gcloud/alpha/container/fleet/rbacrolebindingactuation/update +++ b/gcloud/alpha/container/fleet/rbacrolebindingactuation/update @@ -17,8 +17,10 @@ EXAMPLES $ gcloud container fleet rbacrolebinding-actuation update \ --allowed-custom-roles=role1,role2 + $ gcloud container fleet rbacrolebinding-actuation update \ --add-allowed-custom-role=role1 + $ gcloud container fleet rbacrolebinding-actuation update \ --remove-allowed-custom-role=role2 @@ -47,5 +49,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 container fleet rbacrolebindingactuation update + + $ gcloud beta container fleet rbacrolebindingactuation update diff --git a/gcloud/alpha/container/fleet/scopes/rbacrolebindings/create b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/create index 6e3e14669..ac13ec7e3 100644 --- a/gcloud/alpha/container/fleet/scopes/rbacrolebindings/create +++ b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/create @@ -26,6 +26,13 @@ EXAMPLES $ gcloud alpha container fleet scopes rbacrolebindings create RBRB \ --scope=SCOPE --role=viewer --group=people@google.com + To create an RBAC RoleBinding with a custom role custom-role in scope SCOPE + for user person@google.com, run: + + $ gcloud alpha container fleet scopes rbacrolebindings create RBRB \ + --scope=SCOPE --role=admin --user=person@google.com \ + --custom-role=custom-role + POSITIONAL ARGUMENTS Rbacrolebinding resource - The group of arguments defining an RBACRoleBinding. The arguments in this group can be used to specify the diff --git a/gcloud/alpha/container/fleet/scopes/rbacrolebindings/update b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/update index c94ccb3eb..8acc29705 100644 --- a/gcloud/alpha/container/fleet/scopes/rbacrolebindings/update +++ b/gcloud/alpha/container/fleet/scopes/rbacrolebindings/update @@ -22,6 +22,12 @@ EXAMPLES $ gcloud alpha container fleet scopes rbacrolebindings update RBRB \ --scope=SCOPE --role=viewer + To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to + the custom role custom-role: + + $ gcloud alpha container fleet scopes rbacrolebindings update RBRB \ + --scope=SCOPE --custom-role=custom-role + To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to the user someone@google.com: diff --git a/gcloud/alpha/container/hub/packages/create b/gcloud/alpha/container/hub/packages/create index fbb6e0306..6904ea439 100644 --- a/gcloud/alpha/container/hub/packages/create +++ b/gcloud/alpha/container/hub/packages/create @@ -39,5 +39,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 container hub packages create diff --git a/gcloud/alpha/container/hub/packages/delete b/gcloud/alpha/container/hub/packages/delete index bf1a9c9d3..b38d7009e 100644 --- a/gcloud/alpha/container/hub/packages/delete +++ b/gcloud/alpha/container/hub/packages/delete @@ -64,5 +64,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 container hub packages delete diff --git a/gcloud/alpha/container/hub/packages/describe b/gcloud/alpha/container/hub/packages/describe index 28fc39482..f59179d0a 100644 --- a/gcloud/alpha/container/hub/packages/describe +++ b/gcloud/alpha/container/hub/packages/describe @@ -64,5 +64,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 container hub packages describe diff --git a/gcloud/alpha/container/hub/packages/help b/gcloud/alpha/container/hub/packages/help index c93fbfa82..0fae34db1 100644 --- a/gcloud/alpha/container/hub/packages/help +++ b/gcloud/alpha/container/hub/packages/help @@ -43,5 +43,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 container hub packages diff --git a/gcloud/alpha/container/hub/packages/list b/gcloud/alpha/container/hub/packages/list index d194b2417..cb7d6b5be 100644 --- a/gcloud/alpha/container/hub/packages/list +++ b/gcloud/alpha/container/hub/packages/list @@ -63,5 +63,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 container hub packages list diff --git a/gcloud/alpha/container/hub/packages/resource-bundles/create b/gcloud/alpha/container/hub/packages/resource-bundles/create index 701a5128a..2aa3b7232 100644 --- a/gcloud/alpha/container/hub/packages/resource-bundles/create +++ b/gcloud/alpha/container/hub/packages/resource-bundles/create @@ -39,5 +39,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 container hub packages resource-bundles create diff --git a/gcloud/alpha/container/hub/packages/resource-bundles/delete b/gcloud/alpha/container/hub/packages/resource-bundles/delete index 06b7d6416..cf33c6177 100644 --- a/gcloud/alpha/container/hub/packages/resource-bundles/delete +++ b/gcloud/alpha/container/hub/packages/resource-bundles/delete @@ -39,5 +39,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 container hub packages resource-bundles delete diff --git a/gcloud/alpha/container/hub/packages/resource-bundles/describe b/gcloud/alpha/container/hub/packages/resource-bundles/describe index 5f65d5aab..8d545a598 100644 --- a/gcloud/alpha/container/hub/packages/resource-bundles/describe +++ b/gcloud/alpha/container/hub/packages/resource-bundles/describe @@ -35,5 +35,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 container hub packages resource-bundles describe diff --git a/gcloud/alpha/container/hub/packages/resource-bundles/help b/gcloud/alpha/container/hub/packages/resource-bundles/help index 864e652c2..bbddae506 100644 --- a/gcloud/alpha/container/hub/packages/resource-bundles/help +++ b/gcloud/alpha/container/hub/packages/resource-bundles/help @@ -43,5 +43,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 container hub packages resource-bundles diff --git a/gcloud/alpha/container/hub/packages/resource-bundles/list b/gcloud/alpha/container/hub/packages/resource-bundles/list index 761bb4f11..3e2a43d1d 100644 --- a/gcloud/alpha/container/hub/packages/resource-bundles/list +++ b/gcloud/alpha/container/hub/packages/resource-bundles/list @@ -65,5 +65,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 container hub packages resource-bundles list diff --git a/gcloud/alpha/container/hub/packages/resource-bundles/releases/create b/gcloud/alpha/container/hub/packages/resource-bundles/releases/create index 5633e2fc6..578aad62b 100644 --- a/gcloud/alpha/container/hub/packages/resource-bundles/releases/create +++ b/gcloud/alpha/container/hub/packages/resource-bundles/releases/create @@ -68,5 +68,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 container hub packages resource-bundles releases create diff --git a/gcloud/alpha/container/hub/packages/resource-bundles/releases/delete b/gcloud/alpha/container/hub/packages/resource-bundles/releases/delete index b8be6869c..7fde570e5 100644 --- a/gcloud/alpha/container/hub/packages/resource-bundles/releases/delete +++ b/gcloud/alpha/container/hub/packages/resource-bundles/releases/delete @@ -45,5 +45,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 container hub packages resource-bundles releases delete diff --git a/gcloud/alpha/container/hub/packages/resource-bundles/releases/describe b/gcloud/alpha/container/hub/packages/resource-bundles/releases/describe index 7932dc229..7d51ad93b 100644 --- a/gcloud/alpha/container/hub/packages/resource-bundles/releases/describe +++ b/gcloud/alpha/container/hub/packages/resource-bundles/releases/describe @@ -41,5 +41,8 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta container hub packages resource-bundles releases \ + describe diff --git a/gcloud/alpha/container/hub/packages/resource-bundles/releases/help b/gcloud/alpha/container/hub/packages/resource-bundles/releases/help index 021dd2468..6a3d09ab8 100644 --- a/gcloud/alpha/container/hub/packages/resource-bundles/releases/help +++ b/gcloud/alpha/container/hub/packages/resource-bundles/releases/help @@ -37,5 +37,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 container hub packages resource-bundles releases diff --git a/gcloud/alpha/container/hub/packages/resource-bundles/releases/list b/gcloud/alpha/container/hub/packages/resource-bundles/releases/list index 49f79b117..a3623ccea 100644 --- a/gcloud/alpha/container/hub/packages/resource-bundles/releases/list +++ b/gcloud/alpha/container/hub/packages/resource-bundles/releases/list @@ -69,5 +69,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta container hub packages resource-bundles releases list diff --git a/gcloud/alpha/container/hub/packages/resource-bundles/releases/update b/gcloud/alpha/container/hub/packages/resource-bundles/releases/update index 86ac471d9..e4c5df912 100644 --- a/gcloud/alpha/container/hub/packages/resource-bundles/releases/update +++ b/gcloud/alpha/container/hub/packages/resource-bundles/releases/update @@ -5,8 +5,7 @@ NAME SYNOPSIS gcloud alpha container hub packages resource-bundles releases update RELEASE --resource-bundle=RESOURCE_BUNDLE [--lifecycle=LIFECYCLE] - [--location=LOCATION] [--source=SOURCE] - [--variants-pattern=VARIANTS_PATTERN] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update Package Rollouts Release. @@ -15,20 +14,8 @@ EXAMPLES To update Release v1.0.0 for Resource Bundle my-bundle in us-central1, run: $ gcloud alpha container hub packages resource-bundles releases \ - update --version=v1.0.0 --resource-bundle=my-bundle \ - --source=manifest.yaml - - To update a Release with multiple variants in one directory, run: - - $ gcloud alpha container hub packages resource-bundles releases \ - update --version=v1.0.0 --resource-bundle=my-bundle \ - --source=/manifests/ --variants-pattern=manifest-*.yaml - - To update a Release with multiple variants across multiple directories, ex: - - $ gcloud alpha container hub packages resource-bundles releases \ - update --version=v1.0.0 --resource-bundle=my-bundle \ - --source=/manifests/ --variants-pattern=dir-*/ + update --version=v1.0.0 --resource-bundle=my-bundle \ + --lifecycle=PUBLISHED POSITIONAL ARGUMENTS RELEASE @@ -45,18 +32,6 @@ OPTIONAL FLAGS --location=LOCATION Google Cloud zone or region. - --source=SOURCE - Source file or directory to update the Release from. e.g. - --source=manifest.yaml, --source=/manifests-dir/ Can optionally be - paired with the --variants-pattern arg to create multiple variants of a - Release. - - --variants-pattern=VARIANTS_PATTERN - Glob pattern to Variants of the Release, to be paired with the --source - arg. ex: --source=/manifests-dir/ --variants-pattern=**, - --source=/manifests-dir/ --variants-pattern=us-*.yaml, - --source=/manifests/dir/ --variants-pattern=*/*.yaml - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -69,5 +44,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 container hub packages resource-bundles releases update diff --git a/gcloud/alpha/container/hub/packages/resource-bundles/update b/gcloud/alpha/container/hub/packages/resource-bundles/update index 9231dc529..af1876328 100644 --- a/gcloud/alpha/container/hub/packages/resource-bundles/update +++ b/gcloud/alpha/container/hub/packages/resource-bundles/update @@ -39,5 +39,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 container hub packages resource-bundles update diff --git a/gcloud/alpha/container/hub/packages/rollouts/abort b/gcloud/alpha/container/hub/packages/rollouts/abort index 083a54220..99b667c02 100644 --- a/gcloud/alpha/container/hub/packages/rollouts/abort +++ b/gcloud/alpha/container/hub/packages/rollouts/abort @@ -69,5 +69,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta container hub packages rollouts abort diff --git a/gcloud/alpha/container/hub/packages/rollouts/describe b/gcloud/alpha/container/hub/packages/rollouts/describe index 330758281..7717f32d2 100644 --- a/gcloud/alpha/container/hub/packages/rollouts/describe +++ b/gcloud/alpha/container/hub/packages/rollouts/describe @@ -43,5 +43,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 container hub packages rollouts describe diff --git a/gcloud/alpha/container/hub/packages/rollouts/help b/gcloud/alpha/container/hub/packages/rollouts/help index 325570921..3941da8ff 100644 --- a/gcloud/alpha/container/hub/packages/rollouts/help +++ b/gcloud/alpha/container/hub/packages/rollouts/help @@ -35,5 +35,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 container hub packages rollouts diff --git a/gcloud/alpha/container/hub/packages/rollouts/list b/gcloud/alpha/container/hub/packages/rollouts/list index 587688785..488f75f97 100644 --- a/gcloud/alpha/container/hub/packages/rollouts/list +++ b/gcloud/alpha/container/hub/packages/rollouts/list @@ -73,5 +73,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 container hub packages rollouts list diff --git a/gcloud/alpha/container/hub/packages/rollouts/resume b/gcloud/alpha/container/hub/packages/rollouts/resume index 6eec55d10..eb22b3cb3 100644 --- a/gcloud/alpha/container/hub/packages/rollouts/resume +++ b/gcloud/alpha/container/hub/packages/rollouts/resume @@ -70,5 +70,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 container hub packages rollouts resume diff --git a/gcloud/alpha/container/hub/packages/rollouts/suspend b/gcloud/alpha/container/hub/packages/rollouts/suspend index f5d57f70a..f9b2449f5 100644 --- a/gcloud/alpha/container/hub/packages/rollouts/suspend +++ b/gcloud/alpha/container/hub/packages/rollouts/suspend @@ -70,5 +70,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 container hub packages rollouts suspend diff --git a/gcloud/alpha/container/hub/packages/update b/gcloud/alpha/container/hub/packages/update index c302a8d33..781368168 100644 --- a/gcloud/alpha/container/hub/packages/update +++ b/gcloud/alpha/container/hub/packages/update @@ -64,5 +64,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 container hub packages update diff --git a/gcloud/alpha/container/hub/rbacrolebindingactuation/describe b/gcloud/alpha/container/hub/rbacrolebindingactuation/describe index eba528b3a..9dfc4f531 100644 --- a/gcloud/alpha/container/hub/rbacrolebindingactuation/describe +++ b/gcloud/alpha/container/hub/rbacrolebindingactuation/describe @@ -18,5 +18,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 container hub rbacrolebindingactuation describe + + $ gcloud beta container hub rbacrolebindingactuation describe diff --git a/gcloud/alpha/container/hub/rbacrolebindingactuation/help b/gcloud/alpha/container/hub/rbacrolebindingactuation/help index 85552a23a..cdc847da6 100644 --- a/gcloud/alpha/container/hub/rbacrolebindingactuation/help +++ b/gcloud/alpha/container/hub/rbacrolebindingactuation/help @@ -28,5 +28,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 container hub rbacrolebindingactuation + + $ gcloud beta container hub rbacrolebindingactuation diff --git a/gcloud/alpha/container/hub/rbacrolebindingactuation/update b/gcloud/alpha/container/hub/rbacrolebindingactuation/update index fe762ef21..6dd0be31e 100644 --- a/gcloud/alpha/container/hub/rbacrolebindingactuation/update +++ b/gcloud/alpha/container/hub/rbacrolebindingactuation/update @@ -17,8 +17,10 @@ EXAMPLES $ gcloud container fleet rbacrolebinding-actuation update \ --allowed-custom-roles=role1,role2 + $ gcloud container fleet rbacrolebinding-actuation update \ --add-allowed-custom-role=role1 + $ gcloud container fleet rbacrolebinding-actuation update \ --remove-allowed-custom-role=role2 @@ -47,5 +49,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 container hub rbacrolebindingactuation update + + $ gcloud beta container hub rbacrolebindingactuation update diff --git a/gcloud/alpha/container/hub/scopes/rbacrolebindings/create b/gcloud/alpha/container/hub/scopes/rbacrolebindings/create index f0c7fafaa..b9b50340f 100644 --- a/gcloud/alpha/container/hub/scopes/rbacrolebindings/create +++ b/gcloud/alpha/container/hub/scopes/rbacrolebindings/create @@ -26,6 +26,13 @@ EXAMPLES $ gcloud alpha container hub scopes rbacrolebindings create RBRB \ --scope=SCOPE --role=viewer --group=people@google.com + To create an RBAC RoleBinding with a custom role custom-role in scope SCOPE + for user person@google.com, run: + + $ gcloud alpha container hub scopes rbacrolebindings create RBRB \ + --scope=SCOPE --role=admin --user=person@google.com \ + --custom-role=custom-role + POSITIONAL ARGUMENTS Rbacrolebinding resource - The group of arguments defining an RBACRoleBinding. The arguments in this group can be used to specify the diff --git a/gcloud/alpha/container/hub/scopes/rbacrolebindings/update b/gcloud/alpha/container/hub/scopes/rbacrolebindings/update index 3c40b9e8b..3a6e175e2 100644 --- a/gcloud/alpha/container/hub/scopes/rbacrolebindings/update +++ b/gcloud/alpha/container/hub/scopes/rbacrolebindings/update @@ -22,6 +22,12 @@ EXAMPLES $ gcloud alpha container hub scopes rbacrolebindings update RBRB \ --scope=SCOPE --role=viewer + To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to + the custom role custom-role: + + $ gcloud alpha container hub scopes rbacrolebindings update RBRB \ + --scope=SCOPE --custom-role=custom-role + To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to the user someone@google.com: diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index d2b6595d3..28e8a4b3c 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -46,6 +46,7 @@ SYNOPSIS [--num-nodes=NUM_NODES] [--opportunistic-maintenance=[node-idle-time=NODE_IDLE_TIME, window=WINDOW,min-nodes=MIN_NODES,...]] + [--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT] [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] [--preemptible] [--resource-manager-tags=[KEY=VALUE,...]] [--sandbox=[type=TYPE]] @@ -607,6 +608,19 @@ FLAGS --opportunistic-maintenance=node-idle-time=600s,window=600s,\ min-nodes=2 + --performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT + Sets the Performance Monitoring Unit level. Valid values are + architectural, standard and enhanced. PERFORMANCE_MONITORING_UNIT must + be one of: + + architectural + Enables architectural PMU events tied to non last level cache (LLC) + events. + enhanced + Enables most documented core/L2 and LLC PMU events. + standard + Enables most documented core/L2 PMU events. + --placement-policy=PLACEMENT_POLICY Indicates the desired resource policy to use. diff --git a/gcloud/alpha/dataplex/datascans/create/data-discovery b/gcloud/alpha/dataplex/datascans/create/data-discovery index 4921c64b0..f46450062 100644 --- a/gcloud/alpha/dataplex/datascans/create/data-discovery +++ b/gcloud/alpha/dataplex/datascans/create/data-discovery @@ -207,5 +207,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 dataplex datascans create data-discovery diff --git a/gcloud/alpha/dataplex/datascans/update/data-discovery b/gcloud/alpha/dataplex/datascans/update/data-discovery index bd0b0107c..73a776e8d 100644 --- a/gcloud/alpha/dataplex/datascans/update/data-discovery +++ b/gcloud/alpha/dataplex/datascans/update/data-discovery @@ -190,5 +190,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 dataplex datascans update data-discovery diff --git a/gcloud/alpha/dataplex/entry-groups/add-iam-policy-binding b/gcloud/alpha/dataplex/entry-groups/add-iam-policy-binding index ad05c8715..007d61b4b 100644 --- a/gcloud/alpha/dataplex/entry-groups/add-iam-policy-binding +++ b/gcloud/alpha/dataplex/entry-groups/add-iam-policy-binding @@ -41,7 +41,7 @@ POSITIONAL ARGUMENTS ID of the entry group or fully qualified identifier for the entry group. - To set the entry_group attribute: + To set the entry-group attribute: ▸ provide the argument entry_group on the command line. This positional argument must be specified if any of the other diff --git a/gcloud/alpha/dataplex/entry-groups/create b/gcloud/alpha/dataplex/entry-groups/create index 8a2b5df12..0a1dcbea5 100644 --- a/gcloud/alpha/dataplex/entry-groups/create +++ b/gcloud/alpha/dataplex/entry-groups/create @@ -38,7 +38,7 @@ POSITIONAL ARGUMENTS ID of the entry group or fully qualified identifier for the entry group. - To set the entry_group attribute: + To set the entry-group attribute: ▸ provide the argument entry_group on the command line. This positional argument must be specified if any of the other diff --git a/gcloud/alpha/dataplex/entry-groups/remove-iam-policy-binding b/gcloud/alpha/dataplex/entry-groups/remove-iam-policy-binding index 258200795..effa0cd14 100644 --- a/gcloud/alpha/dataplex/entry-groups/remove-iam-policy-binding +++ b/gcloud/alpha/dataplex/entry-groups/remove-iam-policy-binding @@ -41,7 +41,7 @@ POSITIONAL ARGUMENTS ID of the entry group or fully qualified identifier for the entry group. - To set the entry_group attribute: + To set the entry-group attribute: ▸ provide the argument entry_group on the command line. This positional argument must be specified if any of the other diff --git a/gcloud/alpha/dataplex/entry-groups/set-iam-policy b/gcloud/alpha/dataplex/entry-groups/set-iam-policy index ebadf5f58..7114c38c1 100644 --- a/gcloud/alpha/dataplex/entry-groups/set-iam-policy +++ b/gcloud/alpha/dataplex/entry-groups/set-iam-policy @@ -39,7 +39,7 @@ POSITIONAL ARGUMENTS ID of the entry group or fully qualified identifier for the entry group. - To set the entry_group attribute: + To set the entry-group attribute: ▸ provide the argument entry_group on the command line. This positional argument must be specified if any of the other diff --git a/gcloud/alpha/dataplex/entry-groups/update b/gcloud/alpha/dataplex/entry-groups/update index f4a9b9c43..9085ed20a 100644 --- a/gcloud/alpha/dataplex/entry-groups/update +++ b/gcloud/alpha/dataplex/entry-groups/update @@ -38,7 +38,7 @@ POSITIONAL ARGUMENTS ID of the entry group or fully qualified identifier for the entry group. - To set the entry_group attribute: + To set the entry-group attribute: ▸ provide the argument entry_group on the command line. This positional argument must be specified if any of the other diff --git a/gcloud/alpha/dataplex/entry-links/create b/gcloud/alpha/dataplex/entry-links/create new file mode 100644 index 000000000..daccbc7cd --- /dev/null +++ b/gcloud/alpha/dataplex/entry-links/create @@ -0,0 +1,106 @@ +NAME + gcloud alpha dataplex entry-links create - create a Dataplex Entry Link + +SYNOPSIS + gcloud alpha dataplex entry-links create + (ENTRY_LINK : --entry-group=ENTRY_GROUP --location=LOCATION) + --entry-link-type=ENTRY_LINK_TYPE --entry-references=ENTRY_REFERENCES + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Dataplex Entry Link. + +EXAMPLES + To create a Dataplex Entry Link, you need to provide the entry link ID, the + entry group, the location, the project, the entry link type, and a path to + a YAML file containing the entry references. The entry references file + should contain a list of dictionaries, each representing an entry + reference. + + For example, to create an entry link of entry link type + 'projects/655216118709/locations/global/entryLinkTypes/synonym' named + 'my-entry-link' using entry references from 'entry_references.yaml', run: + + $ gcloud alpha dataplex entry-links create my-entry-link \ + --entry-group=my-entry-group --location=us-central1 \ + --project=test-project \ + --entry-link-type=projects/655216118709/locations/global/\ + entryLinkTypes/synonym \ + --entry-references=path/to/entry_references.yaml + + Example of entry_references.yaml file: - name: projects/test-project/locations/us-central1/entryGroups/my-entry-group/entries/my-entry-1 + type: SOURCE + path: my_path + - name: projects/test-project/locations/us-central1/entryGroups/my-entry-group/entries/my-entry-2 + type: TARGET + +POSITIONAL ARGUMENTS + Entry link resource - Arguments and flags that define the Dataplex entry + link you want to create. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument entry_link 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. + + ENTRY_LINK + ID of the entry link or fully qualified identifier for the entry + link. + + To set the entry-link attribute: + ▸ provide the argument entry_link on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + The name of entry link to use. + + To set the entry-group attribute: + ▸ provide the argument entry_link on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + The location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry_link on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + --entry-link-type=ENTRY_LINK_TYPE + Required. The type of the entry link. It is a resource name of the + EntryLinkType. Example: + projects/my-project/locations/global/entryLinkTypes/my-link-type + + --entry-references=ENTRY_REFERENCES + Required. Path to a YAML or JSON file containing the entry references. + The file should contain a list of dictionaries, each with "name", + "type", and optional "path" keys. Example: - name: + projects/test-project/locations/us-central1/entryGroups/my-entry-group/entries/my-entry-1 + type: SOURCE path: my_path - name: + projects/test-project/locations/us-central1/entryGroups/my-entry-group/entries/my-entry-2 + type: TARGET + +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/dataplex/entry-links/delete b/gcloud/alpha/dataplex/entry-links/delete new file mode 100644 index 000000000..b300d5359 --- /dev/null +++ b/gcloud/alpha/dataplex/entry-links/delete @@ -0,0 +1,77 @@ +NAME + gcloud alpha dataplex entry-links delete - delete a Dataplex entryLink + +SYNOPSIS + gcloud alpha dataplex entry-links delete + (ENTRY_LINK : --entry-group=ENTRY_GROUP --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Dataplex entryLink. + +EXAMPLES + To delete the entryLink 'entryLink1' in the entry group 'entry-group1' in + the project 'test-project' in the location 'us-central1', run: + + $ gcloud alpha dataplex entry-links delete entryLink1 \ + --entry_group=entry-group1 --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Entry link resource - EntryLink 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 entry_link 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. + + ENTRY_LINK + ID of the entry link or fully qualified identifier for the entry + link. + + To set the entry_link attribute: + ▸ provide the argument entry_link on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry_link on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry_link on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/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. + +API REFERENCE + This command uses the dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/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/dataplex/entry-links/describe b/gcloud/alpha/dataplex/entry-links/describe new file mode 100644 index 000000000..4bd18094e --- /dev/null +++ b/gcloud/alpha/dataplex/entry-links/describe @@ -0,0 +1,81 @@ +NAME + gcloud alpha dataplex entry-links describe - describe a Dataplex entry link + +SYNOPSIS + gcloud alpha dataplex entry-links describe + (ENTRY_LINK : --entry_group=ENTRY_GROUP --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Dataplex entry link. + + Displays the details of a Dataplex entry link resource given a valid entry + link ID. + +EXAMPLES + To describe a Dataplex entry entry-link1 within entry group entry-group1 in + location us-central1, run: + + $ gcloud alpha dataplex entry-links describe entry-link1 \ + --entry_group=entry-group1 --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Entry link resource - Arguments and flags that define the Dataplex Entry + Link you want to describe. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument entry_link 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. + + ENTRY_LINK + ID of the entry link or fully qualified identifier for the entry + link. + + To set the entry_link attribute: + ▸ provide the argument entry_link on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry_group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry_group attribute: + ▸ provide the argument entry_link on the command line with a fully + specified name; + ▸ provide the argument --entry_group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry_link on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/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. + +API REFERENCE + This command uses the dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/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/dataplex/entry-links/help b/gcloud/alpha/dataplex/entry-links/help new file mode 100644 index 000000000..5b17b8580 --- /dev/null +++ b/gcloud/alpha/dataplex/entry-links/help @@ -0,0 +1,33 @@ +NAME + gcloud alpha dataplex entry-links - manage Dataplex Catalog Entry Links + resources + +SYNOPSIS + gcloud alpha dataplex entry-links COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Dataplex Catalog Entry Links 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 + (ALPHA) Create a Dataplex Entry Link. + + delete + (ALPHA) Delete a Dataplex entryLink. + + describe + (ALPHA) Describe a Dataplex entry link. + +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/dataplex/help b/gcloud/alpha/dataplex/help index 257b0f033..92b1b9962 100644 --- a/gcloud/alpha/dataplex/help +++ b/gcloud/alpha/dataplex/help @@ -42,6 +42,9 @@ GROUPS entry-groups (ALPHA) Manage Dataplex Entry Groups. + entry-links + (ALPHA) Manage Dataplex Catalog Entry Links resources. + entry-types (ALPHA) Manage Dataplex Entry Types. diff --git a/gcloud/alpha/dataplex/metadata-jobs/cancel b/gcloud/alpha/dataplex/metadata-jobs/cancel index cea54c603..a7b80f9af 100644 --- a/gcloud/alpha/dataplex/metadata-jobs/cancel +++ b/gcloud/alpha/dataplex/metadata-jobs/cancel @@ -64,5 +64,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 dataplex metadata-jobs cancel diff --git a/gcloud/alpha/dataplex/metadata-jobs/create b/gcloud/alpha/dataplex/metadata-jobs/create index 880c98ac3..07fdd4e2c 100644 --- a/gcloud/alpha/dataplex/metadata-jobs/create +++ b/gcloud/alpha/dataplex/metadata-jobs/create @@ -15,8 +15,11 @@ SYNOPSIS --import-source-storage-uri=IMPORT_SOURCE_STORAGE_URI (--import-aspect-types=[IMPORT_ASPECT_TYPES,...] --import-entry-groups=[IMPORT_ENTRY_GROUPS,...] - --import-entry-types=[IMPORT_ENTRY_TYPES,...]) - : --import-log-level=IMPORT_LOG_LEVEL + --import-entry-link-types=[IMPORT_ENTRY_LINK_TYPES,...] + --import-entry-types=[IMPORT_ENTRY_TYPES,...] + --import-glossaries=[IMPORT_GLOSSARIES,...] + --import-referenced-entry-scopes=[IMPORT_REFERENCED_ENTRY_SCOPES, + ...]) : --import-log-level=IMPORT_LOG_LEVEL --import-source-create-time=IMPORT_SOURCE_CREATE_TIME]) [--async] [--labels=[KEY=VALUE,...]] [--validate-only] [GCLOUD_WIDE_FLAG ...] @@ -223,9 +226,18 @@ REQUIRED FLAGS --import-entry-groups=[IMPORT_ENTRY_GROUPS,...] The list of entry groups to import metadata jobs into. + --import-entry-link-types=[IMPORT_ENTRY_LINK_TYPES,...] + The list of entry link types to import metadata jobs into. + --import-entry-types=[IMPORT_ENTRY_TYPES,...] The list of entry types to import metadata jobs into. + --import-glossaries=[IMPORT_GLOSSARIES,...] + The list of glossaries to import metadata jobs into. + + --import-referenced-entry-scopes=[IMPORT_REFERENCED_ENTRY_SCOPES,...] + The list of referenced entry scopes to import metadata jobs into. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to @@ -254,5 +266,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 dataplex metadata-jobs create diff --git a/gcloud/alpha/dataplex/metadata-jobs/describe b/gcloud/alpha/dataplex/metadata-jobs/describe index 639d007a8..7a96b6cf1 100644 --- a/gcloud/alpha/dataplex/metadata-jobs/describe +++ b/gcloud/alpha/dataplex/metadata-jobs/describe @@ -65,5 +65,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 dataplex metadata-jobs describe diff --git a/gcloud/alpha/dataplex/metadata-jobs/help b/gcloud/alpha/dataplex/metadata-jobs/help index a238d1d75..7aee8cfd6 100644 --- a/gcloud/alpha/dataplex/metadata-jobs/help +++ b/gcloud/alpha/dataplex/metadata-jobs/help @@ -31,5 +31,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 dataplex metadata-jobs diff --git a/gcloud/alpha/dataplex/metadata-jobs/list b/gcloud/alpha/dataplex/metadata-jobs/list index 3a7d3a7e5..5247f996c 100644 --- a/gcloud/alpha/dataplex/metadata-jobs/list +++ b/gcloud/alpha/dataplex/metadata-jobs/list @@ -84,5 +84,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 dataplex metadata-jobs list diff --git a/gcloud/alpha/dataproc/clusters/create b/gcloud/alpha/dataproc/clusters/create index 2399f7546..a2886d44c 100644 --- a/gcloud/alpha/dataproc/clusters/create +++ b/gcloud/alpha/dataproc/clusters/create @@ -43,8 +43,7 @@ SYNOPSIS [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--secondary-worker-standard-capacity-percent-above-base=SECONDARY_WORKER_STANDARD_CAPACITY_PERCENT_ABOVE_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--stop-max-idle=STOP_MAX_IDLE] - [--temp-bucket=TEMP_BUCKET] + [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--tier=TIER] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -78,8 +77,6 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] - [--stop-expiration-time=STOP_EXPIRATION_TIME - | --stop-max-age=STOP_MAX_AGE] [--worker-machine-type=WORKER_MACHINE_TYPE | --worker-machine-types=type=MACHINE_TYPE[, type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] @@ -421,15 +418,13 @@ FLAGS security operations, such as remote attestation, encryption, and sealing of keys. - --stop-max-idle=STOP_MAX_IDLE - The duration after the last job completes to auto-stop the cluster, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - --temp-bucket=TEMP_BUCKET The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. + --tier=TIER + Cluster tier. TIER must be one of: premium, standard. + --worker-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the worker instance(s). @@ -950,18 +945,6 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. - At most one of these can be specified: - - --stop-expiration-time=STOP_EXPIRATION_TIME - The time when the cluster will be auto-stopped, such as - "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for - information on time formats. - - --stop-max-age=STOP_MAX_AGE - The lifespan of the cluster, with auto-stop upon completion, such as - "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - At most one of these can be specified: --worker-machine-type=WORKER_MACHINE_TYPE diff --git a/gcloud/alpha/dataproc/clusters/update b/gcloud/alpha/dataproc/clusters/update index 7f4d56dc6..392179dd9 100644 --- a/gcloud/alpha/dataproc/clusters/update +++ b/gcloud/alpha/dataproc/clusters/update @@ -17,11 +17,7 @@ SYNOPSIS | --expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE | --no-max-age] [--delete-max-idle=DELETE_MAX_IDLE | --no-delete-max-idle - | --max-idle=MAX_IDLE | --no-max-idle] - [--stop-expiration-time=STOP_EXPIRATION_TIME - | --stop-max-age=STOP_MAX_AGE | --no-stop-max-age] - [--stop-max-idle=STOP_MAX_IDLE | --no-stop-max-idle] - [GCLOUD_WIDE_FLAG ...] + | --max-idle=MAX_IDLE | --no-max-idle] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update the number of worker nodes and/or the labels in a cluster. @@ -225,33 +221,6 @@ FLAGS Cancels the cluster auto-deletion by cluster idle duration (configured by --max-idle flag) - At most one of these can be specified: - - --stop-expiration-time=STOP_EXPIRATION_TIME - The time when the cluster will be auto-stopped, such as - "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for - information on time formats. - - --stop-max-age=STOP_MAX_AGE - The lifespan of the cluster, with auto-stop upon completion, such as - "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - - --no-stop-max-age - Cancels the cluster auto-stop by maximum cluster age (configured by - --stop-max-age or --stop-expiration-time flags) - - At most one of these can be specified: - - --stop-max-idle=STOP_MAX_IDLE - The duration after the last job completes to auto-stop the cluster, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - - --no-stop-max-idle - Cancels the cluster auto-stop by cluster idle duration (configured by - --stop-max-idle flag) - 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/dataproc/workflow-templates/set-managed-cluster b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster index a41e79861..127339cc3 100644 --- a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster @@ -36,7 +36,7 @@ SYNOPSIS [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--secondary-worker-standard-capacity-percent-above-base=SECONDARY_WORKER_STANDARD_CAPACITY_PERCENT_ABOVE_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] + [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--tier=TIER] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -356,6 +356,9 @@ FLAGS The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. + --tier=TIER + Cluster tier. TIER must be one of: premium, standard. + --worker-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the worker instance(s). diff --git a/gcloud/alpha/developer-connect/account-connectors/update b/gcloud/alpha/developer-connect/account-connectors/update index 565762286..979fc7bbb 100644 --- a/gcloud/alpha/developer-connect/account-connectors/update +++ b/gcloud/alpha/developer-connect/account-connectors/update @@ -9,12 +9,12 @@ SYNOPSIS [--[no-]validate-only] [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations - | --remove-annotations=[__REMOVE_ANNOTATIONS,...]] + | --remove-annotations=REMOVE_ANNOTATIONS] [--clear-provider-oauth-config --provider-oauth-config-scopes=[PROVIDER_OAUTH_CONFIG_SCOPES,...]] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update an accountConnector @@ -147,8 +147,21 @@ FLAGS --clear-annotations Clear annotations value and set to empty map. - --remove-annotations=[__REMOVE_ANNOTATIONS,...] - Remove existing value from map annotations. + --remove-annotations=REMOVE_ANNOTATIONS + Remove existing value from map annotations. Sets remove_annotations + value. + + Shorthand Example: + + --remove-annotations=string,string + + JSON Example: + + --remove-annotations=["string"] + + File Example: + + --remove-annotations=path_to_file.(yaml|json) Arguments for the account connector config. @@ -217,8 +230,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/developer-connect/connections/update b/gcloud/alpha/developer-connect/connections/update index 0ab7d523d..6254df47c 100644 --- a/gcloud/alpha/developer-connect/connections/update +++ b/gcloud/alpha/developer-connect/connections/update @@ -9,7 +9,7 @@ SYNOPSIS [--secret=SECRET] [--[no-]validate-only] [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations - | --remove-annotations=[__REMOVE_ANNOTATIONS,...]] + | --remove-annotations=REMOVE_ANNOTATIONS] [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE --clear-bitbucket-cloud-config | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-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_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE --clear-bitbucket-data-center-config | --clear-github-config --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --clear-github-enterprise-config --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --clear-gitlab-config --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --clear-gitlab-enterprise-config --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] [--clear-crypto-key-config [--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE @@ -17,7 +17,7 @@ SYNOPSIS [--clear-git-proxy-config --[no-]git-proxy-config-enabled] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a connection. @@ -167,8 +167,21 @@ FLAGS --clear-annotations Clear annotations value and set to empty map. - --remove-annotations=[__REMOVE_ANNOTATIONS,...] - Remove existing value from map annotations. + --remove-annotations=REMOVE_ANNOTATIONS + Remove existing value from map annotations. Sets remove_annotations + value. + + Shorthand Example: + + --remove-annotations=string,string + + JSON Example: + + --remove-annotations=["string"] + + File Example: + + --remove-annotations=path_to_file.(yaml|json) Arguments for the connection config. @@ -809,8 +822,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/developer-connect/help b/gcloud/alpha/developer-connect/help index 8562d335e..bcbdbcddd 100644 --- a/gcloud/alpha/developer-connect/help +++ b/gcloud/alpha/developer-connect/help @@ -21,6 +21,9 @@ GROUPS connections (ALPHA) Manage connection resources. + insights-configs + (ALPHA) Manage Insights Config resources. + operations (ALPHA) Manage Operation resources. diff --git a/gcloud/alpha/developer-connect/insights-configs/create b/gcloud/alpha/developer-connect/insights-configs/create new file mode 100644 index 000000000..f4945abec --- /dev/null +++ b/gcloud/alpha/developer-connect/insights-configs/create @@ -0,0 +1,91 @@ +NAME + gcloud alpha developer-connect insights-configs create - create an insight + config + +SYNOPSIS + gcloud alpha developer-connect insights-configs create + (INSIGHTS_CONFIG : --location=LOCATION) + --app-hub-application=APP_HUB_APPLICATION + [--artifact-config=ARTIFACT_CONFIG_ITEM] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create an insights config. + +EXAMPLES + To create an insights config, run: + + $ gcloud alpha developer-connect insights-configs create \ + insights-config-name \ + --app-hub-application=projects/my-project/locations/\ + us-central1/applications/my-app-hub-application + +POSITIONAL ARGUMENTS + Insights config resource - The insights config to create. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument insights_config 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. + + INSIGHTS_CONFIG + ID of the insights_config or fully qualified identifier for the + insights_config. + + To set the insightsConfigs attribute: + ▸ provide the argument insights_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The region of the insight config. + + To set the location attribute: + ▸ provide the argument insights_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --app-hub-application=APP_HUB_APPLICATION + The App Hub application to which the insight config is associated. + +OPTIONAL FLAGS + --artifact-config=ARTIFACT_CONFIG_ITEM + Specifies a single artifact configuration. This flag can be repeated + for multiple configurations. + + Each configuration can be provided in a key-value format. + + Format examples: + --artifact-config=uri={REGION}-docker.pkg.dev/my-project/my-repo/my-image,buildProject=my-project + --artifact-config=[uri={REGION}-docker.pkg.dev/my-project/my-repo/my-image,buildProject=my-project] + + Supported keys within a configuration: + ◆ buildProject: String, e.g., my-project + ◆ uri: String, e.g., + {REGION}-docker.pkg.dev/my-project/my-repo/my-image + +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 developer-connect insights-configs create + + $ gcloud beta developer-connect insights-configs create + diff --git a/gcloud/alpha/developer-connect/insights-configs/delete b/gcloud/alpha/developer-connect/insights-configs/delete new file mode 100644 index 000000000..0c4280de0 --- /dev/null +++ b/gcloud/alpha/developer-connect/insights-configs/delete @@ -0,0 +1,100 @@ +NAME + gcloud alpha developer-connect insights-configs delete - delete + insightsConfigs + +SYNOPSIS + gcloud alpha developer-connect insights-configs delete + (INSIGHTS_CONFIG : --location=LOCATION) [--async] [--etag=ETAG] + [--request-id=REQUEST_ID] [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an insightsConfig + +EXAMPLES + To delete the insightsConfig, run: + + $ gcloud alpha developer-connect insights-configs delete + +POSITIONAL ARGUMENTS + InsightsConfig resource - Value for parent. 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 insights_config 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. + + INSIGHTS_CONFIG + ID of the insightsConfig or fully qualified identifier for the + insightsConfig. + + To set the insights_config attribute: + ▸ provide the argument insights_config 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 insightsConfig resource. + + To set the location attribute: + ▸ provide the argument insights_config 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. + + --etag=ETAG + This checksum is computed by the server based on the value of other + fields, and may be sent on update and delete requests to ensure the + client has an up-to-date value before proceeding. + + --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, validate the request, but do not actually post it. + +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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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 developer-connect insights-configs delete + + $ gcloud beta developer-connect insights-configs delete + diff --git a/gcloud/alpha/developer-connect/insights-configs/describe b/gcloud/alpha/developer-connect/insights-configs/describe new file mode 100644 index 000000000..6439a8509 --- /dev/null +++ b/gcloud/alpha/developer-connect/insights-configs/describe @@ -0,0 +1,71 @@ +NAME + gcloud alpha developer-connect insights-configs describe - describe + insightsConfigs + +SYNOPSIS + gcloud alpha developer-connect insights-configs describe + (INSIGHTS_CONFIG : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe an insightsConfig + +EXAMPLES + To describe the insightsConfig, run: + + $ gcloud alpha developer-connect insights-configs describe + +POSITIONAL ARGUMENTS + InsightsConfig 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 insights_config 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. + + INSIGHTS_CONFIG + ID of the insightsConfig or fully qualified identifier for the + insightsConfig. + + To set the insights_config attribute: + ▸ provide the argument insights_config 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 insightsConfig resource. + + To set the location attribute: + ▸ provide the argument insights_config 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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +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 developer-connect insights-configs describe + + $ gcloud beta developer-connect insights-configs describe + diff --git a/gcloud/alpha/developer-connect/insights-configs/help b/gcloud/alpha/developer-connect/insights-configs/help new file mode 100644 index 000000000..e3b7466f6 --- /dev/null +++ b/gcloud/alpha/developer-connect/insights-configs/help @@ -0,0 +1,44 @@ +NAME + gcloud alpha developer-connect insights-configs - manage Insights Config + resources + +SYNOPSIS + gcloud alpha developer-connect insights-configs COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Insights Config 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 + (ALPHA) Create an insight config. + + delete + (ALPHA) Delete insightsConfigs. + + describe + (ALPHA) Describe insightsConfigs. + + list + (ALPHA) List insightsConfigs. + + update + (ALPHA) Update the configuration of an insight config. + +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 developer-connect insights-configs + + $ gcloud beta developer-connect insights-configs + diff --git a/gcloud/alpha/healthcare/annotation-stores/list b/gcloud/alpha/developer-connect/insights-configs/list similarity index 61% rename from gcloud/alpha/healthcare/annotation-stores/list rename to gcloud/alpha/developer-connect/insights-configs/list index 4108a5f7d..50fab7b4c 100644 --- a/gcloud/alpha/healthcare/annotation-stores/list +++ b/gcloud/alpha/developer-connect/insights-configs/list @@ -1,53 +1,37 @@ NAME - gcloud alpha healthcare annotation-stores list - list Cloud Healthcare API - annotation stores + gcloud alpha developer-connect insights-configs list - list insightsConfigs SYNOPSIS - gcloud alpha healthcare annotation-stores list - (--dataset=DATASET : --location=LOCATION) [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha developer-connect insights-configs list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Cloud Healthcare API annotation stores. + (ALPHA) List insightsConfigs EXAMPLES - To list the annotation stores in 'test-dataset', run: + To list all insightsConfigs, run: - $ gcloud alpha healthcare annotation-stores list \ - --dataset=test-dataset + $ gcloud alpha developer-connect insights-configs list REQUIRED FLAGS - Dataset resource - The dataset to list the annotation stores for. 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. + Location resource - Parent value for ListInsightsConfigsRequest. 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 --dataset on the command line with a fully + ◆ 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. - --dataset=DATASET - ID of the dataset or fully qualified identifier for the dataset. - - To set the dataset attribute: - ▸ provide the argument --dataset on the command line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - --location=LOCATION - Google Cloud location. + ID of the location or fully qualified identifier for the location. To set the location attribute: - ▸ provide the argument --dataset on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. + ▸ provide the argument --location on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -90,14 +74,17 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the healthcare/v1alpha2 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare + This command uses the developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview 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 beta healthcare annotation-stores list + $ gcloud developer-connect insights-configs list + + $ gcloud beta developer-connect insights-configs list diff --git a/gcloud/alpha/developer-connect/insights-configs/update b/gcloud/alpha/developer-connect/insights-configs/update new file mode 100644 index 000000000..153238503 --- /dev/null +++ b/gcloud/alpha/developer-connect/insights-configs/update @@ -0,0 +1,99 @@ +NAME + gcloud alpha developer-connect insights-configs update - update the + configuration of an insight config + +SYNOPSIS + gcloud alpha developer-connect insights-configs update + (INSIGHTS_CONFIG : --location=LOCATION) + (--run-discovery + --artifact-uri=ARTIFACT_URI --build-project=BUILD_PROJECT) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update the configuration of an insights config. + +EXAMPLES + To update the state of an insights config, run: + + $ gcloud alpha developer-connect insights-configs update \ + insights-config-name --run-discovery + + To update the Artifact Analysis project for an artifact in an insights + config, run: + + $ gcloud alpha developer-connect insights-configs update \ + insights-config-name \ + --artifact-uri=us-{location}-docker.pkg.dev/my-project/\ + my-artifact-repo/my-image --build-project={build_project} + +POSITIONAL ARGUMENTS + Insights config resource - The insights config 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 insights_config 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. + + INSIGHTS_CONFIG + ID of the insights_config or fully qualified identifier for the + insights_config. + + To set the insightsConfigs attribute: + ▸ provide the argument insights_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The region of the insight config. + + To set the location attribute: + ▸ provide the argument insights_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Update the insight config. + + At least one of these must be specified: + + --run-discovery + Sets the state of the insight config to PENDING and kicks off the + discovery flow. + + --artifact-uri=ARTIFACT_URI + Identifier for the specific artifact you want to update + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --build-project=BUILD_PROJECT + The project ID of the project to where the artifact is built. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +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 developer-connect insights-configs update + + $ gcloud beta developer-connect insights-configs update + diff --git a/gcloud/alpha/dns/policies/update b/gcloud/alpha/dns/policies/update index 120ad910b..3362145c9 100644 --- a/gcloud/alpha/dns/policies/update +++ b/gcloud/alpha/dns/policies/update @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha dns policies update POLICY [--alternative-name-servers=[NAME_SERVERS,...]] - [--description=DESCRIPTION] [--enable-dns64-all-queries] + [--description=DESCRIPTION] [--[no-]enable-dns64-all-queries] [--enable-inbound-forwarding] [--enable-logging] [--networks=[NETWORKS,...]] [--private-alternative-name-servers=[NAME_SERVERS,...]] @@ -46,9 +46,10 @@ FLAGS --description=DESCRIPTION A description of the policy. - --enable-dns64-all-queries + --[no-]enable-dns64-all-queries Specifies whether to allow networks bound to this policy to use DNS64 - for IPv6-only VM instances. + for IPv6-only VM instances. Use --enable-dns64-all-queries to enable + and --no-enable-dns64-all-queries to disable. --enable-inbound-forwarding Specifies whether to allow networks bound to this policy to receive DNS diff --git a/gcloud/alpha/edge-cloud/container/clusters/create b/gcloud/alpha/edge-cloud/container/clusters/create index a993c3512..8578352d7 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/create +++ b/gcloud/alpha/edge-cloud/container/clusters/create @@ -16,6 +16,7 @@ SYNOPSIS [--control-plane-shared-deployment-policy=CONTROL_PLANE_SHARED_DEPLOYMENT_POLICY] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--enable-cluster-isolation=ENABLE_CLUSTER_ISOLATION] + [--enable-google-group-authentication] [--external-lb-address-pools=EXTERNAL_LB_ADDRESS_POOLS] [--external-lb-ipv4-address-pools=[EXTERNAL_LB_IPV4_ADDRESS,...]] [--external-lb-ipv6-address-pools=[EXTERNAL_LB_IPV6_ADDRESS,...]] @@ -135,6 +136,10 @@ FLAGS --enable-cluster-isolation=ENABLE_CLUSTER_ISOLATION If set, the cluster will be created in a secure cluster isolation mode. + --enable-google-group-authentication + If set, the cluster will be configured to use Google Group + authentication. + --external-lb-address-pools=EXTERNAL_LB_ADDRESS_POOLS Path to a YAML/JSON file containing external load balancer pool configuration. External load balancer pools are used for data plane diff --git a/gcloud/alpha/firebase/test/android/run b/gcloud/alpha/firebase/test/android/run index 888f9f967..77e27b714 100644 --- a/gcloud/alpha/firebase/test/android/run +++ b/gcloud/alpha/firebase/test/android/run @@ -446,7 +446,7 @@ ANDROID INSTRUMENTATION TEST FLAGS test targets). Each target filter must be fully qualified with the package name, class name, or test annotation desired. Any test filter supported by am instrument -e ... is supported. See - https://developer.android.com/reference/android/support/test/runner/AndroidJUnitRunner + https://developer.android.com/reference/androidx/test/runner/AndroidJUnitRunner for more information. Examples: ◆ --test-targets "package com.my.package.name" diff --git a/gcloud/alpha/firestore/databases/create b/gcloud/alpha/firestore/databases/create index 00fa15e7c..ef33e2a8e 100644 --- a/gcloud/alpha/firestore/databases/create +++ b/gcloud/alpha/firestore/databases/create @@ -11,7 +11,7 @@ SYNOPSIS EXAMPLES To create a Firestore Enterprise database named foo in nam5 for use with - Ignite APIs. + MongoDB Compatibility. $ gcloud alpha firestore databases create --database=foo \ --edition=enterprise --location=nam5 diff --git a/gcloud/alpha/firestore/indexes/composite/create b/gcloud/alpha/firestore/indexes/composite/create index e94d5015c..dfa5eb113 100644 --- a/gcloud/alpha/firestore/indexes/composite/create +++ b/gcloud/alpha/firestore/indexes/composite/create @@ -59,7 +59,7 @@ REQUIRED FLAGS Shorthand Example: - --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat={}} --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat={}} + --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat} --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat} JSON Example: diff --git a/gcloud/alpha/healthcare/annotation-stores/add-iam-policy-binding b/gcloud/alpha/healthcare/annotation-stores/add-iam-policy-binding deleted file mode 100644 index 9300eaf02..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/add-iam-policy-binding +++ /dev/null @@ -1,147 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores add-iam-policy-binding - add an - IAM policy binding to a Cloud Healthcare API annotation store - -SYNOPSIS - gcloud alpha healthcare annotation-stores add-iam-policy-binding - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - --member=PRINCIPAL --role=ROLE - [--condition=[KEY=VALUE,...] | --condition-from-file=PATH_TO_FILE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Add an IAM policy binding to a Cloud Healthcare API annotation - store. - -EXAMPLES - To add an IAM policy binding for the role of 'roles/editor' for the user - 'test-user@gmail.com' on the annotation store 'test-annotation-store', run: - - $ gcloud alpha healthcare annotation-stores add-iam-policy-binding \ - test-annotation-store --dataset=test-dataset \ - --member='user:test-user@gmail.com' --role='roles/editor' - - See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and member types. - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store to add an - IAM policy binding to. The arguments in this group can be used to specify - the attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - -REQUIRED FLAGS - --member=PRINCIPAL - The principal to add the binding for. Should be of the form - user|group|serviceAccount:email or domain:domain. - - Examples: user:test-user@gmail.com, group:admins@example.com, - serviceAccount:test123@example.domain.com, or - domain:example.domain.com. - - Some resources also accept the following special values: - ◆ allUsers - Special identifier that represents anyone who is on the - internet, with or without a Google account. - ◆ allAuthenticatedUsers - Special identifier that represents anyone - who is authenticated with a Google account or a service account. - - --role=ROLE - Role name to assign to the principal. The role name is the complete - path of a predefined role, such as roles/logging.viewer, or the role ID - for a custom role, such as - organizations/{ORGANIZATION_ID}/roles/logging.viewer. - -OPTIONAL FLAGS - At most one of these can be specified: - - --condition=[KEY=VALUE,...] - A condition to include in the binding. When the condition is - explicitly specified as None (--condition=None), a binding without a - condition is added. When the condition is specified and is not None, - --role cannot be a basic role. Basic roles are roles/editor, - roles/owner, and roles/viewer. For more on conditions, refer to the - conditions overview guide: - https://cloud.google.com/iam/docs/conditions-overview - - When using the --condition flag, include the following key-value - pairs: - - expression - (Required) Condition expression that evaluates to True or False. - This uses a subset of Common Expression Language syntax. - - If the condition expression includes a comma, use a different - delimiter to separate the key-value pairs. Specify the delimiter - before listing the key-value pairs. For example, to specify a - colon (:) as the delimiter, do the following: - --condition=^:^title=TITLE:expression=EXPRESSION. For more - information, see - https://cloud.google.com/sdk/gcloud/reference/topic/escaping. - - title - (Required) A short string describing the purpose of the - expression. - - description - (Optional) Additional description for the expression. - - --condition-from-file=PATH_TO_FILE - Path to a local JSON or YAML file that defines the condition. To see - available fields, see the help for --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. - -API REFERENCE - This command uses the healthcare/v1alpha2 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -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 healthcare annotation-stores add-iam-policy-binding - diff --git a/gcloud/alpha/healthcare/annotation-stores/create b/gcloud/alpha/healthcare/annotation-stores/create deleted file mode 100644 index 3f7edef5e..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/create +++ /dev/null @@ -1,79 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores create - create a Cloud - Healthcare API annotation store - -SYNOPSIS - gcloud alpha healthcare annotation-stores create - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a Cloud Healthcare API annotation store. - -EXAMPLES - To create an annotation store called 'test-annotation-store', run: - - $ gcloud alpha healthcare annotation-stores create \ - test-annotation-store --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store to - create. The arguments in this group can be used to specify the attributes - of this resource. (NOTE) Some attributes are not given arguments in this - group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/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. - -API REFERENCE - This command uses the healthcare/v1alpha2 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -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 healthcare annotation-stores create - diff --git a/gcloud/alpha/healthcare/annotation-stores/delete b/gcloud/alpha/healthcare/annotation-stores/delete deleted file mode 100644 index 6720fd286..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/delete +++ /dev/null @@ -1,79 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores delete - delete a Cloud - Healthcare API annotation store - -SYNOPSIS - gcloud alpha healthcare annotation-stores delete - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Delete a Cloud Healthcare API annotation store. - -EXAMPLES - To delete the annotation-store 'test-annotation-store', run: - - $ gcloud alpha healthcare annotation-stores delete \ - test-annotation-store --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/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. - -API REFERENCE - This command uses the healthcare/v1alpha2 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -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 healthcare annotation-stores delete - diff --git a/gcloud/alpha/healthcare/annotation-stores/describe b/gcloud/alpha/healthcare/annotation-stores/describe deleted file mode 100644 index 7a7608a5d..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/describe +++ /dev/null @@ -1,79 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores describe - describe a Cloud - Healthcare API annotation store - -SYNOPSIS - gcloud alpha healthcare annotation-stores describe - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Describe a Cloud Healthcare API annotation store. - -EXAMPLES - To describe the annotation-store 'test-annotation-store', run: - - $ gcloud alpha healthcare annotation-stores describe \ - test-annotation-store --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/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. - -API REFERENCE - This command uses the healthcare/v1alpha2 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -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 healthcare annotation-stores describe - diff --git a/gcloud/alpha/healthcare/annotation-stores/evaluate/bq b/gcloud/alpha/healthcare/annotation-stores/evaluate/bq deleted file mode 100644 index 1204b07cd..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/evaluate/bq +++ /dev/null @@ -1,114 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores evaluate bq - evaluate a Cloud - Healthcare API Annotation store and report to BigQuery - -SYNOPSIS - gcloud alpha healthcare annotation-stores evaluate bq - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - --bq-table=BQ_TABLE --golden-store=GOLDEN_STORE [--async] - [--write-disposition=WRITE_DISPOSITION] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Evaluate Cloud Healthcare API Annotation store against a ground - truth store and report the results to BigQuery. - -EXAMPLES - To evaluate the annotation-store 'eval-annotation-store' against a ground - truth annotation-store - projects/my-project/locations/my-location/datasets/test-dataset/annotationStores/golden-annotation-store, - and report the metric to the BigQuery table bqtable in the BigQuery dataset - bqdataset, run: - - $ gcloud alpha healthcare annotation-stores evaluate bq \ - eval-annotation-store \ - --golden-store=projects/my-project/locations/my-location/\ - datasets/test-dataset/annotationStores/golden-annotation-store \ - --bq-table=bq://my-project.bqdataset.bqtable \ - --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API Annotation store to be - evaluated. 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - -REQUIRED FLAGS - --bq-table=BQ_TABLE - BigQuery table where evaluation results are written. - - --golden-store=GOLDEN_STORE - Ground truth AnnotationStore to compare against. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --write-disposition=WRITE_DISPOSITION - Determines whether existing table in the destination dataset are - overwritten or appended to. WRITE_DISPOSITION must be one of: - - write-append - Append data to the existing table. - - write-empty - Only export data if the destination table is empty. - - write-truncate - Erase all existing data in a table before writing the instances. - -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 healthcare/v1alpha2 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -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 healthcare annotation-stores evaluate bq - diff --git a/gcloud/alpha/healthcare/annotation-stores/evaluate/help b/gcloud/alpha/healthcare/annotation-stores/evaluate/help deleted file mode 100644 index 7b78ffe7d..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/evaluate/help +++ /dev/null @@ -1,31 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores evaluate - manage Cloud - Healthcare API Annotation store evaluates - -SYNOPSIS - gcloud alpha healthcare annotation-stores evaluate COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Cloud Healthcare API Annotation store evaluates. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - bq - (ALPHA) Evaluate a Cloud Healthcare API Annotation store and report to - BigQuery. - -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 healthcare annotation-stores evaluate - diff --git a/gcloud/alpha/healthcare/annotation-stores/export/bq b/gcloud/alpha/healthcare/annotation-stores/export/bq deleted file mode 100644 index d041d50c7..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/export/bq +++ /dev/null @@ -1,105 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores export bq - export Cloud - Healthcare API Annotation records to BigQuery - -SYNOPSIS - gcloud alpha healthcare annotation-stores export bq - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - --bq-table=BQ_TABLE [--async] [--write-disposition=WRITE_DISPOSITION] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Export Cloud Healthcare API Annotation records to BigQuery. - -EXAMPLES - To export the annotation-store 'test-annotation-store' to the BigQuery - table 'bqtable' in the BigQuery dataset bqdataset, run: - - $ gcloud alpha healthcare annotation-stores export bq \ - test-annotation-store \ - --bq-table=bq://my-project.bqdataset.bqtable \ - --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API Annotation store to export - annotations from. 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - -REQUIRED FLAGS - --bq-table=BQ_TABLE - BigQuery table that annotation records will be exported to. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --write-disposition=WRITE_DISPOSITION - Determines whether existing table in the destination dataset are - overwritten or appended to. WRITE_DISPOSITION must be one of: - - write-append - Append data to the existing table. - - write-empty - Only export data if the destination table is empty. - - write-truncate - Erase all existing data in a table before writing the instances. - -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 healthcare/v1alpha2 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -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 healthcare annotation-stores export bq - diff --git a/gcloud/alpha/healthcare/annotation-stores/export/gcs b/gcloud/alpha/healthcare/annotation-stores/export/gcs deleted file mode 100644 index d5e527570..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/export/gcs +++ /dev/null @@ -1,94 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores export gcs - export Cloud - Healthcare API Annotation records to Google Cloud Storage - -SYNOPSIS - gcloud alpha healthcare annotation-stores export gcs - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - --gcs-uri=GCS_URI [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Export Cloud Healthcare API Annotation records to Google Cloud - Storage. - -EXAMPLES - To export the annotation-store 'test-annotation-store' to the existing - bucket 'testGcsBucket' in the folder 'someFolder', run: - - $ gcloud alpha healthcare annotation-stores export gcs \ - test-annotation-store --gcs-uri=gs://testGcsBucket/someFolder \ - --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API Annotation store to export - annotations from. 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - -REQUIRED FLAGS - --gcs-uri=GCS_URI - The Cloud Storage destination location. Specify a path to a Cloud - Storage bucket or folder rather than a concrete object. The server - creates one object per annotation record. Each object contains a - JSON-formatted text file of an Annotation record. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the healthcare/v1alpha2 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -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 healthcare annotation-stores export gcs - diff --git a/gcloud/alpha/healthcare/annotation-stores/export/help b/gcloud/alpha/healthcare/annotation-stores/export/help deleted file mode 100644 index 48fb9adb0..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/export/help +++ /dev/null @@ -1,34 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores export - manage Cloud Healthcare - API Annotation store exports - -SYNOPSIS - gcloud alpha healthcare annotation-stores export COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Cloud Healthcare API Annotation store exports. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - bq - (ALPHA) Export Cloud Healthcare API Annotation records to BigQuery. - - gcs - (ALPHA) Export Cloud Healthcare API Annotation records to Google Cloud - Storage. - -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 healthcare annotation-stores export - diff --git a/gcloud/alpha/healthcare/annotation-stores/get-iam-policy b/gcloud/alpha/healthcare/annotation-stores/get-iam-policy deleted file mode 100644 index ea845f117..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/get-iam-policy +++ /dev/null @@ -1,108 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores get-iam-policy - retrieve the IAM - policy for a Cloud Healthcare API annotation store - -SYNOPSIS - gcloud alpha healthcare annotation-stores get-iam-policy - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Retrieve the IAM policy for a Cloud Healthcare API annotation - store. - -EXAMPLES - To print the IAM policy for the annotation store 'test-annotation-store', - run: - - $ gcloud alpha healthcare annotation-stores get-iam-policy \ - test-annotation-store --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store whose IAM - policy to fetch. 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - -LIST COMMAND FLAGS - --filter=EXPRESSION - Apply a Boolean filter EXPRESSION to each resource item to be listed. - If the expression evaluates True, then that item is listed. For more - details and examples of filter expressions, run $ gcloud topic filters. - This flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is - determined by the service if it supports paging, otherwise it is - unlimited (no paging). Paging may be applied before or after --filter - and --limit depending on the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - -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 healthcare/v1alpha2 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -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 healthcare annotation-stores get-iam-policy - diff --git a/gcloud/alpha/healthcare/annotation-stores/help b/gcloud/alpha/healthcare/annotation-stores/help deleted file mode 100644 index 5c8691470..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/help +++ /dev/null @@ -1,69 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores - manage Cloud Healthcare API - annotation stores - -SYNOPSIS - gcloud alpha healthcare annotation-stores GROUP | COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Cloud Healthcare API annotation stores. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - evaluate - (ALPHA) Manage Cloud Healthcare API Annotation store evaluates. - - export - (ALPHA) Manage Cloud Healthcare API Annotation store exports. - - import - (ALPHA) Manage Cloud Healthcare API Annotation store imports. - -COMMANDS - COMMAND is one of the following: - - add-iam-policy-binding - (ALPHA) Add an IAM policy binding to a Cloud Healthcare API annotation - store. - - create - (ALPHA) Create a Cloud Healthcare API annotation store. - - delete - (ALPHA) Delete a Cloud Healthcare API annotation store. - - describe - (ALPHA) Describe a Cloud Healthcare API annotation store. - - get-iam-policy - (ALPHA) Retrieve the IAM policy for a Cloud Healthcare API annotation - store. - - list - (ALPHA) List Cloud Healthcare API annotation stores. - - remove-iam-policy-binding - (ALPHA) Remove an IAM policy binding from a Cloud Healthcare API - annotation store. - - set-iam-policy - (ALPHA) Set the IAM policy for a Cloud Healthcare API annotation store. - - update - (ALPHA) Update a Cloud Healthcare API annotation store. - -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 healthcare annotation-stores - diff --git a/gcloud/alpha/healthcare/annotation-stores/import/gcs b/gcloud/alpha/healthcare/annotation-stores/import/gcs deleted file mode 100644 index b00329f08..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/import/gcs +++ /dev/null @@ -1,95 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores import gcs - import Annotation - records from Google Cloud Storage into a Cloud Healthcare API - Annotation store - -SYNOPSIS - gcloud alpha healthcare annotation-stores import gcs - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - --gcs-uri=GCS_URI [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Import Annotation records from Google Cloud Storage into a Cloud - Healthcare API Annotation store. - -EXAMPLES - To import the Annotation records from the existing bucket 'testGcsBucket' - in the folder 'someFolder' into the Annotation store - 'test-annotation-store', run: - - $ gcloud alpha healthcare annotation-stores import gcs \ - test-annotation-store --gcs-uri=gs://testGcsBucket/someFolder \ - --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API Annotation store into - which the data is imported. 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - -REQUIRED FLAGS - --gcs-uri=GCS_URI - Cloud Storage source data locations. Each Cloud Storage object is a - text file that contains exactly one JSON structure conforming to the - Annotation proto. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the healthcare/v1alpha2 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -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 healthcare annotation-stores import gcs - diff --git a/gcloud/alpha/healthcare/annotation-stores/import/help b/gcloud/alpha/healthcare/annotation-stores/import/help deleted file mode 100644 index de8756011..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/import/help +++ /dev/null @@ -1,31 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores import - manage Cloud Healthcare - API Annotation store imports - -SYNOPSIS - gcloud alpha healthcare annotation-stores import COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Cloud Healthcare API Annotation store imports. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - gcs - (ALPHA) Import Annotation records from Google Cloud Storage into a - Cloud Healthcare API Annotation store. - -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 healthcare annotation-stores import - diff --git a/gcloud/alpha/healthcare/annotation-stores/remove-iam-policy-binding b/gcloud/alpha/healthcare/annotation-stores/remove-iam-policy-binding deleted file mode 100644 index 8e000fbc2..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/remove-iam-policy-binding +++ /dev/null @@ -1,154 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores remove-iam-policy-binding - - remove an IAM policy binding from a Cloud Healthcare API annotation - store - -SYNOPSIS - gcloud alpha healthcare annotation-stores remove-iam-policy-binding - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - --member=PRINCIPAL --role=ROLE - [--all | --condition=[KEY=VALUE,...] - | --condition-from-file=PATH_TO_FILE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Remove an IAM policy binding from a Cloud Healthcare API annotation - store. - -EXAMPLES - To remove an IAM policy binding for the role of 'roles/editor' for the user - 'test-user@gmail.com' on the annotation store 'test-annotation-store', run: - - $ gcloud alpha healthcare annotation-stores \ - remove-iam-policy-binding test-annotation-store \ - --dataset=test-dataset --member='user:test-user@gmail.com' \ - --role='roles/editor' - - See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and member types. - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store to remove - an IAM policy binding from. 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - -REQUIRED FLAGS - --member=PRINCIPAL - The principal to remove the binding for. Should be of the form - user|group|serviceAccount:email or domain:domain. - - Examples: user:test-user@gmail.com, group:admins@example.com, - serviceAccount:test123@example.domain.com, or - domain:example.domain.com. - - Deleted principals have an additional deleted: prefix and a ?uid=UID - suffix, where UID is a unique identifier for the principal. Example: - deleted:user:test-user@gmail.com?uid=123456789012345678901. - - Some resources also accept the following special values: - ◆ allUsers - Special identifier that represents anyone who is on the - internet, with or without a Google account. - ◆ allAuthenticatedUsers - Special identifier that represents anyone - who is authenticated with a Google account or a service account. - - --role=ROLE - The role to remove the principal from. - -OPTIONAL FLAGS - At most one of these can be specified: - - --all - Remove all bindings with this role and principal, irrespective of any - conditions. - - --condition=[KEY=VALUE,...] - The condition of the binding that you want to remove. When the - condition is explicitly specified as None (--condition=None), a - binding without a condition is removed. Otherwise, only a binding - with a condition that exactly matches the specified condition - (including the optional description) is removed. For more on - conditions, refer to the conditions overview guide: - https://cloud.google.com/iam/docs/conditions-overview - - When using the --condition flag, include the following key-value - pairs: - - expression - (Required) Condition expression that evaluates to True or False. - This uses a subset of Common Expression Language syntax. - - If the condition expression includes a comma, use a different - delimiter to separate the key-value pairs. Specify the delimiter - before listing the key-value pairs. For example, to specify a - colon (:) as the delimiter, do the following: - --condition=^:^title=TITLE:expression=EXPRESSION. For more - information, see - https://cloud.google.com/sdk/gcloud/reference/topic/escaping. - - title - (Required) A short string describing the purpose of the - expression. - - description - (Optional) Additional description for the expression. - - --condition-from-file=PATH_TO_FILE - Path to a local JSON or YAML file that defines the condition. To see - available fields, see the help for --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. - -API REFERENCE - This command uses the healthcare/v1alpha2 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -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 healthcare annotation-stores remove-iam-policy-binding - diff --git a/gcloud/alpha/healthcare/annotation-stores/set-iam-policy b/gcloud/alpha/healthcare/annotation-stores/set-iam-policy deleted file mode 100644 index c8530f104..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/set-iam-policy +++ /dev/null @@ -1,90 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores set-iam-policy - set the IAM - policy for a Cloud Healthcare API annotation store - -SYNOPSIS - gcloud alpha healthcare annotation-stores set-iam-policy - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) POLICY_FILE - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Set the IAM policy for a Cloud Healthcare API annotation store. - -EXAMPLES - The following command will read am IAM policy defined in a JSON file - 'policy.json' and set it for the annotation store 'test-annotation-store': - - $ gcloud alpha healthcare annotation-stores set-iam-policy \ - test-annotation-store policy.json --dataset=test-dataset - - See https://cloud.google.com/iam/docs/managing-policies for details of the - policy file format and contents. - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store whose IAM - policy to set. 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - - 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 healthcare/v1alpha2 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -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 healthcare annotation-stores set-iam-policy - diff --git a/gcloud/alpha/healthcare/annotation-stores/update b/gcloud/alpha/healthcare/annotation-stores/update deleted file mode 100644 index 08d463fab..000000000 --- a/gcloud/alpha/healthcare/annotation-stores/update +++ /dev/null @@ -1,79 +0,0 @@ -NAME - gcloud alpha healthcare annotation-stores update - update a Cloud - Healthcare API annotation store - -SYNOPSIS - gcloud alpha healthcare annotation-stores update - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Update a Cloud Healthcare API annotation store. - -EXAMPLES - To update the annotation store 'test-annotation-store', run: - - $ gcloud alpha healthcare annotation-stores update \ - test-annotation-store --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/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. - -API REFERENCE - This command uses the healthcare/v1alpha2 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -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 healthcare annotation-stores update - diff --git a/gcloud/alpha/healthcare/datasets/deidentify b/gcloud/alpha/healthcare/datasets/deidentify index e1a50056f..59ad93d0f 100644 --- a/gcloud/alpha/healthcare/datasets/deidentify +++ b/gcloud/alpha/healthcare/datasets/deidentify @@ -4,9 +4,8 @@ NAME SYNOPSIS gcloud alpha healthcare datasets deidentify (DATASET : --location=LOCATION) - --destination-dataset=DESTINATION_DATASET - [--annotation-store=ANNOTATION_STORE] [--async] [--default-fhir-config] - [--dicom-filter-tags=[DICOM_FILTER_TAGS,...]] + --destination-dataset=DESTINATION_DATASET [--async] + [--default-fhir-config] [--dicom-filter-tags=[DICOM_FILTER_TAGS,...]] [--text-redaction-mode=TEXT_REDACTION_MODE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -64,16 +63,6 @@ REQUIRED FLAGS new dataset must not exist, or the request will fail. OPTIONAL FLAGS - --annotation-store=ANNOTATION_STORE - The name of the annotation store to output the location of sensitive - data (e.g., - projects/{projectId}/locations/{locationId}/datasets/{datasetId}/annotationStores/{annotationStoreId}). - The annotation store, if not in the destination dataset, must already - exist. The generated annotations will contain the original values of - the de-identified data in the 'quote' field. See - https://cloud.google.com/healthcare/docs/how-tos/annotations-deidentify - for more details. - --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/alpha/healthcare/dicom-stores/deidentify b/gcloud/alpha/healthcare/dicom-stores/deidentify index eac0a86f4..9a4cb6a59 100644 --- a/gcloud/alpha/healthcare/dicom-stores/deidentify +++ b/gcloud/alpha/healthcare/dicom-stores/deidentify @@ -5,8 +5,7 @@ NAME SYNOPSIS gcloud alpha healthcare dicom-stores deidentify (DICOM_STORE : --dataset=DATASET --location=LOCATION) - --destination-store=DESTINATION_STORE - [--annotation-store=ANNOTATION_STORE] [--async] + --destination-store=DESTINATION_STORE [--async] [--dicom-filter-tags=[DICOM_FILTER_TAGS,...]] [--text-redaction-mode=TEXT_REDACTION_MODE] [GCLOUD_WIDE_FLAG ...] @@ -74,16 +73,6 @@ REQUIRED FLAGS fail. OPTIONAL FLAGS - --annotation-store=ANNOTATION_STORE - The name of the annotation store to output the location of sensitive - data (e.g., - projects/{projectId}/locations/{locationId}/datasets/{datasetId}/annotationStores/{annotationStoreId}). - The annotation store must already exist. The generated annotations will - contain the original values of the de-identified data in the 'quote' - field. See - https://cloud.google.com/healthcare/docs/how-tos/annotations-deidentify - for more details. - --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/alpha/healthcare/fhir-stores/deidentify b/gcloud/alpha/healthcare/fhir-stores/deidentify index 3a1a170b5..e08386293 100644 --- a/gcloud/alpha/healthcare/fhir-stores/deidentify +++ b/gcloud/alpha/healthcare/fhir-stores/deidentify @@ -5,8 +5,7 @@ NAME SYNOPSIS gcloud alpha healthcare fhir-stores deidentify (FHIR_STORE : --dataset=DATASET --location=LOCATION) - --destination-store=DESTINATION_STORE - [--annotation-store=ANNOTATION_STORE] [--async] [GCLOUD_WIDE_FLAG ...] + --destination-store=DESTINATION_STORE [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) De-identify data from the source store and write it to the @@ -69,16 +68,6 @@ REQUIRED FLAGS fail. OPTIONAL FLAGS - --annotation-store=ANNOTATION_STORE - The name of the annotation store to output the location of sensitive - data (e.g., - projects/{projectId}/locations/{locationId}/datasets/{datasetId}/annotationStores/{annotationStoreId}). - The annotation store must already exist. The generated annotations will - contain the original values of the de-identified data in the 'quote' - field. See - https://cloud.google.com/healthcare/docs/how-tos/annotations-deidentify - for more details. - --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/alpha/healthcare/help b/gcloud/alpha/healthcare/help index 194f641e6..5679c0f23 100644 --- a/gcloud/alpha/healthcare/help +++ b/gcloud/alpha/healthcare/help @@ -15,9 +15,6 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: - annotation-stores - (ALPHA) Manage Cloud Healthcare API annotation stores. - consent-stores (ALPHA) Manage Cloud Healthcare API consent stores. diff --git a/gcloud/alpha/iam/workforce-pools/providers/create-oidc b/gcloud/alpha/iam/workforce-pools/providers/create-oidc index bdb774dff..2076cdbc7 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/create-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/create-oidc @@ -12,7 +12,7 @@ SYNOPSIS : --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]) [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--client-secret-value=CLIENT_SECRET_VALUE] [--description=DESCRIPTION] - [--disabled] [--display-name=DISPLAY_NAME] + [--detailed-audit-logging] [--disabled] [--display-name=DISPLAY_NAME] [--jwk-json-path=PATH_TO_FILE] [--extra-attributes-client-id=EXTRA_ATTRIBUTES_CLIENT_ID --extra-attributes-client-secret-value=EXTRA_ATTRIBUTES_CLIENT_SECRET_VALUE --extra-attributes-issuer-uri=EXTRA_ATTRIBUTES_ISSUER_URI --extra-attributes-type=EXTRA_ATTRIBUTES_TYPE : --extra-attributes-filter=EXTRA_ATTRIBUTES_FILTER] @@ -240,6 +240,11 @@ OPTIONAL FLAGS A description for the workforce pool provider. Cannot exceed 256 characters in length. + --detailed-audit-logging + Enables detailed audit logging for this provider, which populates + additional debug information in STS Cloud Audit Logs. Specify + --no-detailed-audit-logging to disable it. + --disabled Disables the workforce pool provider. You cannot use a disabled provider to perform new token exchanges or sign-ins. However, existing diff --git a/gcloud/alpha/iam/workforce-pools/providers/update-oidc b/gcloud/alpha/iam/workforce-pools/providers/update-oidc index aca7216f4..af7e709ce 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/update-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/update-oidc @@ -7,8 +7,9 @@ SYNOPSIS (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL) [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--attribute-mapping=[KEY=VALUE,...]] [--client-id=CLIENT_ID] - [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] - [--issuer-uri=ISSUER_URI] [--jwk-json-path=PATH_TO_FILE] + [--description=DESCRIPTION] [--detailed-audit-logging] [--disabled] + [--display-name=DISPLAY_NAME] [--issuer-uri=ISSUER_URI] + [--jwk-json-path=PATH_TO_FILE] [--web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]] [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] @@ -187,6 +188,11 @@ FLAGS A description for the workforce pool provider. Cannot exceed 256 characters in length. + --detailed-audit-logging + Enables detailed audit logging for this provider, which populates + additional debug information in STS Cloud Audit Logs. Specify + --no-detailed-audit-logging to disable it. + --disabled Disables the workforce pool provider. You cannot use a disabled provider to perform new token exchanges or sign-ins. However, existing diff --git a/gcloud/alpha/iap/settings/get b/gcloud/alpha/iap/settings/get index 61ef4f23f..6ec1a6d2c 100644 --- a/gcloud/alpha/iap/settings/get +++ b/gcloud/alpha/iap/settings/get @@ -80,6 +80,18 @@ EXAMPLES --resource-type=forwarding-rule --service=SERVICE_ID \ --region=REGION_ID + To get the IAP setting for all Cloud Run services within a region of a + project, run: + + $ gcloud alpha iap settings get --project=PROJECT_ID \ + --resource-type=cloud-run --region=REGION_ID + + To get the IAP setting for a Cloud Run service within a project, run: + + $ gcloud alpha iap settings get --project=PROJECT_ID \ + --resource-type=cloud-run --region=REGION_ID \ + --service=SERVICE_ID + FLAGS --folder=FOLDER Folder ID. diff --git a/gcloud/alpha/iap/settings/set b/gcloud/alpha/iap/settings/set index 42760fc8a..75a7b2e11 100644 --- a/gcloud/alpha/iap/settings/set +++ b/gcloud/alpha/iap/settings/set @@ -15,73 +15,85 @@ EXAMPLES To set the IAP setting for the resources within an organization, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --organization=ORGANIZATION_ID + --organization=ORGANIZATION_ID - To set the IAP setting for the resources within a folder, run: + To set the IAP setting for the resources within a folder, run: $ gcloud alpha iap settings set iap_settings.yaml --folder=FOLDER_ID - To set the IAP setting for the resources within a project, run: + To set the IAP setting for the resources within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID + --project=PROJECT_ID - To set the IAP setting for web type resources within a project, run: + To set the IAP setting for web type resources within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=iap_web + --project=PROJECT_ID --resource-type=iap_web - To set the IAP setting for all app engine services within a project, run: + To set the IAP setting for all app engine services within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=app-engine + --project=PROJECT_ID --resource-type=app-engine - To set the IAP setting for an app engine service within a project, run: + To set the IAP setting for an app engine service within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=app-engine \ - --service=SERVICE_ID + --project=PROJECT_ID --resource-type=app-engine \ + --service=SERVICE_ID - To set the IAP setting for an app engine service version within a project, - run: + To set the IAP setting for an app engine service version within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=app-engine \ - --service=SERVICE_ID --version=VERSION_ID + --project=PROJECT_ID --resource-type=app-engine \ + --service=SERVICE_ID --version=VERSION_ID - To set the IAP setting for all backend services within a project, run: + To set the IAP setting for all backend services within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=backend-services + --project=PROJECT_ID --resource-type=backend-services - To set the IAP setting for a backend service within a project, run: + To set the IAP setting for a backend service within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=backend-services \ - --service=SERVICE_ID + --project=PROJECT_ID --resource-type=backend-services \ + --service=SERVICE_ID - To set the IAP setting for a region backend service within a project, run: + To set the IAP setting for a region backend service within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=backend-services \ - --service=SERVICE_ID --region=REGION_ID + --project=PROJECT_ID --resource-type=backend-services \ + --service=SERVICE_ID --region=REGION_ID - To set the IAP setting for all forwarding rule within a project, run: + To set the IAP setting for all forwarding rule within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=forwarding-rule + --project=PROJECT_ID --resource-type=forwarding-rule - To set the IAP setting for a forwarding rule within a project, run: + To set the IAP setting for a forwarding rule within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=forwarding-rule \ - --service=SERVICE_ID + --project=PROJECT_ID --resource-type=forwarding-rule \ + --service=SERVICE_ID - To set the IAP setting for a region forwarding rule within a project, run: + To set the IAP setting for a region forwarding rule within a project, run: $ gcloud alpha iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=forwarding-rule \ - --service=SERVICE_ID --region=REGION_ID + --project=PROJECT_ID --resource-type=forwarding-rule \ + --service=SERVICE_ID --region=REGION_ID + + To set the IAP setting for the all cloud run services within a region of a + project, run: + + $ gcloud alpha iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=cloud-run \ + --region=REGION_ID + + To set the IAP setting for a cloud run service within a project, run: + + $ gcloud alpha iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=cloud-run \ + --region=REGION_ID --service=SERVICE_ID POSITIONAL ARGUMENTS SETTING_FILE diff --git a/gcloud/alpha/kms/keys/create b/gcloud/alpha/kms/keys/create index db69a3d9c..0ddd88145 100644 --- a/gcloud/alpha/kms/keys/create +++ b/gcloud/alpha/kms/keys/create @@ -204,7 +204,8 @@ OPTIONAL FLAGS aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, ec-sign-p384-sha384, ec-sign-secp256k1-sha256, external-symmetric-encryption, google-symmetric-encryption, hmac-sha1, - hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, pq-sign-ml-dsa-65, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + pq-sign-hash-slh-dsa-sha2-128s-sha256, pq-sign-ml-dsa-65, pq-sign-slh-dsa-sha2-128s, rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, diff --git a/gcloud/alpha/kms/keys/update b/gcloud/alpha/kms/keys/update index 9572df059..341259cff 100644 --- a/gcloud/alpha/kms/keys/update +++ b/gcloud/alpha/kms/keys/update @@ -175,7 +175,8 @@ FLAGS aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, ec-sign-p384-sha384, ec-sign-secp256k1-sha256, external-symmetric-encryption, google-symmetric-encryption, hmac-sha1, - hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, pq-sign-ml-dsa-65, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + pq-sign-hash-slh-dsa-sha2-128s-sha256, pq-sign-ml-dsa-65, pq-sign-slh-dsa-sha2-128s, rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, diff --git a/gcloud/alpha/kms/keys/versions/import b/gcloud/alpha/kms/keys/versions/import index 9957e364a..73ca2ec9f 100644 --- a/gcloud/alpha/kms/keys/versions/import +++ b/gcloud/alpha/kms/keys/versions/import @@ -34,7 +34,8 @@ REQUIRED FLAGS aes-128-cbc, aes-128-ctr, aes-128-gcm, aes-256-cbc, aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, ec-sign-p384-sha384, ec-sign-secp256k1-sha256, google-symmetric-encryption, hmac-sha1, - hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, pq-sign-ml-dsa-65, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + pq-sign-hash-slh-dsa-sha2-128s-sha256, pq-sign-ml-dsa-65, pq-sign-slh-dsa-sha2-128s, rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, diff --git a/gcloud/alpha/logging/logs/delete b/gcloud/alpha/logging/logs/delete index 0273b48c5..391f82f6b 100644 --- a/gcloud/alpha/logging/logs/delete +++ b/gcloud/alpha/logging/logs/delete @@ -1,17 +1,17 @@ NAME gcloud alpha logging logs delete - delete all entries from a log in the - _Default log bucket + global _Default log bucket SYNOPSIS gcloud alpha logging logs delete LOG_NAME [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete all entries from a log in the _Default log bucket. With no - entries, the log will not appear in the list of your project's logs. - However, you can write new entries to the log. + (ALPHA) Delete all entries from a log in the global _Default log bucket. + With no entries, the log will not appear in the list of your project's + logs. However, you can write new entries to the log. EXAMPLES - To delete all entries from log 'my-log' in the _Default log bucket: + To delete all entries from log 'my-log' in the global _Default log bucket: $ gcloud alpha logging logs delete my-log diff --git a/gcloud/alpha/logging/logs/help b/gcloud/alpha/logging/logs/help index 682afc2fa..f66aa53f3 100644 --- a/gcloud/alpha/logging/logs/help +++ b/gcloud/alpha/logging/logs/help @@ -16,7 +16,8 @@ COMMANDS COMMAND is one of the following: delete - (ALPHA) Delete all entries from a log in the _Default log bucket. + (ALPHA) Delete all entries from a log in the global _Default log + bucket. list (ALPHA) List your project's logs. diff --git a/gcloud/alpha/logging/operations/list b/gcloud/alpha/logging/operations/list index c19e77c8c..ee9f78b6b 100644 --- a/gcloud/alpha/logging/operations/list +++ b/gcloud/alpha/logging/operations/list @@ -10,15 +10,37 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Return a list of long running operation details in given LOCATION. - The operations were scheduled by other gcloud commands. For example: a - copy_log_entries operation scheduled by command: gcloud alpha logging - operations copy BUCKET_ID DESTINATION --location=LOCATION. Note: while - listing the operations, the request_type must be specified in filter. - Example: --operation-filter=request_type=CopyLogEntries, Supported - operation types are: CopyLogEntries, CreateBucket and UpdateBucket. Other - supported filter expression are: operation_start_time, - operation_finish_time and operation_state. + (ALPHA) Return a list of long running operations in the given LOCATION. The + operations were scheduled by other gcloud commands. + + For example, a CopyLogEntries operation may be scheduled by the command: + gcloud logging copy BUCKET_ID DESTINATION --location=LOCATION. + + The --operation-filter flag is required and must specify the request_type. + Supported request types include but are not limited to: CopyLogEntries, + CreateBucket and UpdateBucket. + + Additional supported filter expressions include: operation_start_time, + operation_finish_time and operation_state. These can be combined with the + case-sensitive keyword AND between them. + + For operation_start_time and operation_end_time, the operators >=, >, <=, + and < are supported. + + Timestamps must be in either RFC3339 or ISO8601 formats. If the timestamp + contains a time value, then it must be quoted. For examples: + "YYYY-MM-DDTHH:MM:SSZ", "YYYY-MM-DDTHH:MM:SS.mmmZ", "YY-MM-DD", + "YYYY-MM-DDTHH:MM:SS-0000", "YYYY-MM-DDTHH:MM+0000", "YYYY-MM-DD", + YYYY-MM-DD, YY-MM-DD, etc. + + The operation_state filter expression can be used to filter for operations + that are in a specific state. The value can be one of the following: + SCHEDULED, WAITING_FOR_PRECONDITIONS, RUNNING, SUCCESS, FAILURE, CANCELLED, + PENDING. + + For operation_state, the operators = and != are supported. + + Other filter options are not supported. EXAMPLES To list CopyLogEntries operations, run: @@ -39,17 +61,17 @@ EXAMPLES --operation-filter='request_type=CopyLogEntries AND operation_finish_time<="2023-11-20T00:00:00Z"' - To list CopyLogEntries operations that have a specified state, run: + To list CopyLogEntries operations that completed successfully, run: $ gcloud alpha logging operations list --location=LOCATION \ --operation-filter='request_type=CopyLogEntries AND - operation_state=STATE' + operation_state=SUCCESS' - To list CopyLogEntries operations that don't have a specified state, run: + To list CopyLogEntries operations that have not failed, run: $ gcloud alpha logging operations list --location=LOCATION \ --operation-filter='request_type=CopyLogEntries AND - operation_state!=STATE' + operation_state!=FAILURE' REQUIRED FLAGS --location=LOCATION diff --git a/gcloud/alpha/lustre/instances/create b/gcloud/alpha/lustre/instances/create index 31d7b5b15..ca01619b8 100644 --- a/gcloud/alpha/lustre/instances/create +++ b/gcloud/alpha/lustre/instances/create @@ -4,22 +4,22 @@ NAME SYNOPSIS gcloud alpha lustre instances create (INSTANCE : --location=LOCATION) --capacity-gib=CAPACITY_GIB --filesystem=FILESYSTEM --network=NETWORK - [--async] [--description=DESCRIPTION] [--gke-support-enabled] - [--labels=[LABELS,...]] - [--per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT] - [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + --per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT [--async] + [--description=DESCRIPTION] [--gke-support-enabled] + [--labels=[LABELS,...]] [--request-id=REQUEST_ID] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates a Managed Lustre instance. EXAMPLES - To create an instance my-instance in location us-central1-a with 2048 Gib + To create an instance my-instance in location us-central1-a with 18000 Gib capacity run: $ gcloud alpha lustre instances create my-instance \ - --capacity-gib=2048 --location=us-central1-a \ + --capacity-gib=18000 --location=us-central1-a \ --network=projects/my-project/global/networks/default \ - --filesystem=lustrefs + --filesystem=lustrefs --per-unit-storage-throughput=1000 POSITIONAL ARGUMENTS Instance resource - Identifier. The name of the instance. The arguments in @@ -55,7 +55,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --capacity-gib=CAPACITY_GIB The storage capacity of the instance in gibibytes (GiB). Allowed values - are from 18000 to 936000, in increments of 9000. + are from 18000 to 954000, in increments of 9000. --filesystem=FILESYSTEM The filesystem name for this instance. This name is used by client-side @@ -82,6 +82,10 @@ REQUIRED FLAGS To set the network attribute: ▸ 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. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to @@ -117,10 +121,6 @@ OPTIONAL FLAGS --labels=path_to_file.(yaml|json) - --per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT - The throughput of the instance in MB/s/TiB. Valid values are 250, 500, - 1000. Default value is 1000. - --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 diff --git a/gcloud/alpha/lustre/instances/export-data b/gcloud/alpha/lustre/instances/export-data index f534daf7c..878616081 100644 --- a/gcloud/alpha/lustre/instances/export-data +++ b/gcloud/alpha/lustre/instances/export-data @@ -19,10 +19,11 @@ EXAMPLES --lustre-path='/path/to/lustre/dir' POSITIONAL ARGUMENTS - Instance resource - The name of the Managed Lustre instance. 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. + Instance resource - The name of the Managed Lustre instance in the format + projects/{project}/locations/{location}/instances/{instance}. 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 diff --git a/gcloud/alpha/lustre/instances/import-data b/gcloud/alpha/lustre/instances/import-data index 4b2cafa94..35e55f48f 100644 --- a/gcloud/alpha/lustre/instances/import-data +++ b/gcloud/alpha/lustre/instances/import-data @@ -19,9 +19,11 @@ EXAMPLES --lustre-path='/path/to/lustre/dir' POSITIONAL ARGUMENTS - Instance 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. + Instance resource - The name of the Managed Lustre instance in the format + projects/{project}/locations/{location}/instances/{instance}. 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 diff --git a/gcloud/alpha/lustre/instances/update b/gcloud/alpha/lustre/instances/update index ac77ad562..71fbdf26f 100644 --- a/gcloud/alpha/lustre/instances/update +++ b/gcloud/alpha/lustre/instances/update @@ -10,7 +10,7 @@ SYNOPSIS [--request-id=REQUEST_ID] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Updates the parameters of a single Managed Lustre instance. @@ -60,7 +60,7 @@ FLAGS --capacity-gib=CAPACITY_GIB The storage capacity of the instance in gibibytes (GiB). Allowed values - are from 18000 to 936000, in increments of 9000. + are from 18000 to 954000, in increments of 9000. --description=DESCRIPTION A user-readable description of the instance. @@ -71,8 +71,8 @@ FLAGS enable and --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 250, 500, - 1000. Default value is 1000. + The throughput of the instance in MB/s/TiB. Valid values are 125, 250, + 500, 1000. --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request @@ -144,8 +144,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/managed-kafka/clusters/create b/gcloud/alpha/managed-kafka/clusters/create index 2d5f3376b..90f7138f0 100644 --- a/gcloud/alpha/managed-kafka/clusters/create +++ b/gcloud/alpha/managed-kafka/clusters/create @@ -5,8 +5,9 @@ NAME SYNOPSIS gcloud alpha managed-kafka clusters create (CLUSTER : --location=LOCATION) --cpu=CPU --memory=MEMORY --subnets=[SUBNETS,...] [--async] - [--no-auto-rebalance] [--ca-pools=[CA_POOLS,...]] - [--encryption-key=ENCRYPTION_KEY] [--labels=[KEY=VALUE,...]] + [--no-auto-rebalance] [--encryption-key=ENCRYPTION_KEY] + [--labels=[KEY=VALUE,...]] [--mtls-ca-pools=[MTLS_CA_POOLS,...]] + [--ssl-principal-mapping-rules=SSL_PRINCIPAL_MAPPING_RULES] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -84,14 +85,6 @@ OPTIONAL FLAGS by default. Use --no-auto-rebalance to disable this flag. Enabled by default, use --no-auto-rebalance to disable. - --ca-pools=[CA_POOLS,...] - A comma-separated list of CA pools from the Google Cloud Certificate - Authority Service. The root certificates of these CA pools will be - installed in the truststore of each broker in the cluster for use with - mTLS. A maximum of 10 CA pools can be specified. CA pools can be in a - different project and region than the cluster. Each CA pool must be in - the format projects/PROJECT_ID/locations/LOCATION/caPools/CA_POOL. - --encryption-key=ENCRYPTION_KEY The relative resource path of the Cloud KMS key to use for encryption in the form: @@ -105,6 +98,24 @@ OPTIONAL FLAGS characters, and numbers. Values must contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --mtls-ca-pools=[MTLS_CA_POOLS,...] + A comma-separated list of CA pools from the Google Cloud Certificate + Authority Service. The root certificates of these CA pools will be + installed in the truststore of each broker in the cluster for use with + mTLS. A maximum of 10 CA pools can be specified. CA pools can be in a + different project and region than the cluster. Each CA pool must be in + the format projects/PROJECT_ID/locations/LOCATION/caPools/CA_POOL. + + --ssl-principal-mapping-rules=SSL_PRINCIPAL_MAPPING_RULES + The rules for mapping mTLS certificate Distinguished Names (DNs) to + shortened principal names for Kafka ACLs. This flag corresponds exactly + to the ssl.principal.mapping.rules broker config and matches the format + and syntax defined in the Apache Kafka documentation. Setting or + modifying this field will trigger a rolling restart of the Kafka + brokers to apply the change. An empty string means that the default + Kafka behavior is used. Example: + "RULE:^CN=(.?),OU=ServiceUsers.$/$1@example.com/,DEFAULT" + 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/managed-kafka/clusters/update b/gcloud/alpha/managed-kafka/clusters/update index 2259a841f..23122b7bf 100644 --- a/gcloud/alpha/managed-kafka/clusters/update +++ b/gcloud/alpha/managed-kafka/clusters/update @@ -4,9 +4,10 @@ NAME SYNOPSIS gcloud alpha managed-kafka clusters update (CLUSTER : --location=LOCATION) - (--auto-rebalance --ca-pools=[CA_POOLS,...] --cpu=CPU - --labels=[KEY=VALUE,...] --memory=MEMORY --subnets=[SUBNETS,...]) - [--async] [GCLOUD_WIDE_FLAG ...] + (--auto-rebalance --cpu=CPU --labels=[KEY=VALUE,...] --memory=MEMORY + --mtls-ca-pools=[MTLS_CA_POOLS,...] + --ssl-principal-mapping-rules=SSL_PRINCIPAL_MAPPING_RULES + --subnets=[SUBNETS,...]) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a Managed Service for Apache Kafka cluster. @@ -61,15 +62,6 @@ REQUIRED FLAGS when the number of CPUs in the cluster changes. Automatic rebalancing is enabled by default. Use --no-auto-rebalance to disable this flag. - --ca-pools=[CA_POOLS,...] - A comma-separated list of CA pools from the Google Cloud Certificate - Authority Service. The root certificates of these CA pools will be - installed in the truststore of each broker in the cluster for use - with mTLS. A maximum of 10 CA pools can be specified. CA pools can be - in a different project and region than the cluster. Each CA pool must - be in the format - projects/PROJECT_ID/locations/LOCATION/caPools/CA_POOL. - --cpu=CPU The number of vCPUs to provision for the cluster. The minimum is 3. @@ -83,6 +75,25 @@ REQUIRED FLAGS The memory to provision for the cluster in bytes. The value must be between 1 GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi. + --mtls-ca-pools=[MTLS_CA_POOLS,...] + A comma-separated list of CA pools from the Google Cloud Certificate + Authority Service. The root certificates of these CA pools will be + installed in the truststore of each broker in the cluster for use + with mTLS. A maximum of 10 CA pools can be specified. CA pools can be + in a different project and region than the cluster. Each CA pool must + be in the format + projects/PROJECT_ID/locations/LOCATION/caPools/CA_POOL. + + --ssl-principal-mapping-rules=SSL_PRINCIPAL_MAPPING_RULES + The rules for mapping mTLS certificate Distinguished Names (DNs) to + shortened principal names for Kafka ACLs. This flag corresponds + exactly to the ssl.principal.mapping.rules broker config and matches + the format and syntax defined in the Apache Kafka documentation. + Setting or modifying this field will trigger a rolling restart of the + Kafka brokers to apply the change. An empty string means that the + default Kafka behavior is used. Example: + "RULE:^CN=(.?),OU=ServiceUsers.$/$1@example.com/,DEFAULT" + --subnets=[SUBNETS,...] A comma-separated list of VPC subnets from which the cluster is accessible. Both broker and bootstrap server IP addresses and DNS diff --git a/gcloud/alpha/managed-kafka/schema-registries/create b/gcloud/alpha/managed-kafka/schema-registries/create index 2b47ca779..4df35685f 100644 --- a/gcloud/alpha/managed-kafka/schema-registries/create +++ b/gcloud/alpha/managed-kafka/schema-registries/create @@ -67,5 +67,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 managed-kafka schema-registries create diff --git a/gcloud/alpha/managed-kafka/schema-registries/delete b/gcloud/alpha/managed-kafka/schema-registries/delete index 92017d4cc..f3a886360 100644 --- a/gcloud/alpha/managed-kafka/schema-registries/delete +++ b/gcloud/alpha/managed-kafka/schema-registries/delete @@ -68,5 +68,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 managed-kafka schema-registries delete diff --git a/gcloud/alpha/managed-kafka/schema-registries/describe b/gcloud/alpha/managed-kafka/schema-registries/describe index 8f95eaa1f..ef2fb26f2 100644 --- a/gcloud/alpha/managed-kafka/schema-registries/describe +++ b/gcloud/alpha/managed-kafka/schema-registries/describe @@ -1,26 +1,23 @@ NAME - gcloud alpha managed-kafka schema-registries describe - describe a Managed - Service for Apache Kafka schema registry + gcloud alpha managed-kafka schema-registries describe - describe a schema + registry with all of its fields SYNOPSIS gcloud alpha managed-kafka schema-registries describe (SCHEMA_REGISTRY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] -DESCRIPTION - (ALPHA) Describe a Managed Service for Apache Kafka schema registry. - EXAMPLES - To describe a schema registry named myschemaregistry located in - us-central1, run the following: + Describe the schema registry with all of its fields: $ gcloud alpha managed-kafka schema-registries describe \ - myschemaregistry --location=us-central1 + --project=PROJECT_ID --location=LOCATION_ID \ + --schema_registry=SCHEMA_REGISTRY_ID POSITIONAL ARGUMENTS - Schema registry resource - Identifies the schema registry for details to - be displayed. 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. + Schema registry resource - The schema registry to create. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. To set the project attribute: ◆ provide the argument schema_registry on the command line with a fully @@ -59,14 +56,11 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the managedkafka/v1 API. The full documentation for this - API can be found at: - https://cloud.google.com/managed-service-for-apache-kafka/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. + access allowlist. This variant is also available: + + $ gcloud beta managed-kafka schema-registries describe diff --git a/gcloud/alpha/managed-kafka/schema-registries/help b/gcloud/alpha/managed-kafka/schema-registries/help index 675564e91..bd0797d6a 100644 --- a/gcloud/alpha/managed-kafka/schema-registries/help +++ b/gcloud/alpha/managed-kafka/schema-registries/help @@ -3,7 +3,8 @@ NAME for Apache Kafka schema-registries SYNOPSIS - gcloud alpha managed-kafka schema-registries COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha managed-kafka schema-registries GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Administer Managed Service for Apache Kafka schema-registries. @@ -13,6 +14,12 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + subject + (ALPHA) Administer Managed Service for Apache Kafka schema-registries. + COMMANDS COMMAND is one of the following: @@ -23,15 +30,20 @@ COMMANDS (ALPHA) Delete a Managed Service for Apache Kafka schema registry. describe - (ALPHA) Describe a Managed Service for Apache Kafka schema registry. + (ALPHA) Describe a schema registry with all of its fields. list (ALPHA) List all Managed Service for Apache Kafka schema registries in a given location. + update + (ALPHA) Update the mode and compatibility of a schema registry. + 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 managed-kafka schema-registries diff --git a/gcloud/alpha/managed-kafka/schema-registries/list b/gcloud/alpha/managed-kafka/schema-registries/list index cff539694..a1c7abede 100644 --- a/gcloud/alpha/managed-kafka/schema-registries/list +++ b/gcloud/alpha/managed-kafka/schema-registries/list @@ -82,5 +82,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 managed-kafka schema-registries list diff --git a/gcloud/alpha/managed-kafka/schema-registries/subject/describe b/gcloud/alpha/managed-kafka/schema-registries/subject/describe new file mode 100644 index 000000000..71bcbacbc --- /dev/null +++ b/gcloud/alpha/managed-kafka/schema-registries/subject/describe @@ -0,0 +1,80 @@ +NAME + gcloud alpha managed-kafka schema-registries subject describe - describe a + subject in a schema registry with all of its fields + +SYNOPSIS + gcloud alpha managed-kafka schema-registries subject describe + (SUBJECT : --location=LOCATION --schema-registry=SCHEMA_REGISTRY) + --schema_registry=SCHEMA_REGISTRY [--context=CONTEXT] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + Describe the subject in a schema registry with all of its fields: + + $ gcloud alpha managed-kafka schema-registries subject describe \ + --project=PROJECT_ID --location=LOCATION_ID \ + --schema_registry=SCHEMA_REGISTRY_ID + +POSITIONAL ARGUMENTS + Subject resource - The subject to create. The arguments in this group can + be used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument subject 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. + + SUBJECT + ID of the subject or fully qualified identifier for the subject. + + To set the subject attribute: + ▸ provide the argument subject on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument subject on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --schema-registry=SCHEMA_REGISTRY + The schema registry name. + + To set the schema-registry attribute: + ▸ provide the argument subject on the command line with a fully + specified name; + ▸ provide the argument --schema-registry on the command line. + +REQUIRED FLAGS + --schema_registry=SCHEMA_REGISTRY + The schema registry of the subject. + +OPTIONAL FLAGS + --context=CONTEXT + The context of the subject. + +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/managed-kafka/schema-registries/subject/help b/gcloud/alpha/managed-kafka/schema-registries/subject/help new file mode 100644 index 000000000..ef8f3d54d --- /dev/null +++ b/gcloud/alpha/managed-kafka/schema-registries/subject/help @@ -0,0 +1,31 @@ +NAME + gcloud alpha managed-kafka schema-registries subject - administer Managed + Service for Apache Kafka schema-registries + +SYNOPSIS + gcloud alpha managed-kafka schema-registries subject COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Administer Managed Service for Apache Kafka schema-registries. + +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 subject in a schema registry with all of its fields. + + update + (ALPHA) Update the mode and compatibility of a subject. + +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/managed-kafka/schema-registries/subject/update b/gcloud/alpha/managed-kafka/schema-registries/subject/update new file mode 100644 index 000000000..9cf1740d2 --- /dev/null +++ b/gcloud/alpha/managed-kafka/schema-registries/subject/update @@ -0,0 +1,93 @@ +NAME + gcloud alpha managed-kafka schema-registries subject update - update the + mode and compatibility of a subject + +SYNOPSIS + gcloud alpha managed-kafka schema-registries subject update + (SUBJECT : --location=LOCATION --schema-registry=SCHEMA_REGISTRY) + --schema_registry=SCHEMA_REGISTRY + (--compatibility=COMPATIBILITY | --mode=MODE) [--context=CONTEXT] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + Modify the mode of the subject to READONLY: + + $ gcloud alpha managed-kafka schema-registries subject update \ + --mode=READONLY + + Modify the compatibility of the subject to BACKWARDS: + + $ gcloud alpha managed-kafka schema-registries subject update \ + --compatibility=BACKWARDS + +POSITIONAL ARGUMENTS + Subject resource - The subject to create. The arguments in this group can + be used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument subject 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. + + SUBJECT + ID of the subject or fully qualified identifier for the subject. + + To set the subject attribute: + ▸ provide the argument subject on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument subject on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --schema-registry=SCHEMA_REGISTRY + The schema registry name. + + To set the schema-registry attribute: + ▸ provide the argument subject on the command line with a fully + specified name; + ▸ provide the argument --schema-registry on the command line. + +REQUIRED FLAGS + --schema_registry=SCHEMA_REGISTRY + The schema registry of the subject. + + Exactly one of these must be specified: + + --compatibility=COMPATIBILITY + The mode and compatibility of the schema registry. + + --mode=MODE + The mode and compatibility of the schema registry. + +OPTIONAL FLAGS + --context=CONTEXT + The context of the subject. + +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/managed-kafka/schema-registries/update b/gcloud/alpha/managed-kafka/schema-registries/update new file mode 100644 index 000000000..3622be8ba --- /dev/null +++ b/gcloud/alpha/managed-kafka/schema-registries/update @@ -0,0 +1,77 @@ +NAME + gcloud alpha managed-kafka schema-registries update - update the mode and + compatibility of a schema registry + +SYNOPSIS + gcloud alpha managed-kafka schema-registries update + (SCHEMA_REGISTRY : --location=LOCATION) + (--compatibility=COMPATIBILITY | --mode=MODE) [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + Modify the mode of the schema registry to READONLY: + + $ gcloud alpha managed-kafka schema-registries update --mode=READONLY + + Modify the compatibility of the schema registry to BACKWARDS: + + $ gcloud alpha managed-kafka schema-registries update \ + --compatibility=BACKWARDS + +POSITIONAL ARGUMENTS + Schema registry resource - The schema registry to create. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument schema_registry 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. + + SCHEMA_REGISTRY + ID of the schema_registry or fully qualified identifier for the + schema_registry. + + To set the schema_registry attribute: + ▸ provide the argument schema_registry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument schema_registry on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --compatibility=COMPATIBILITY + The mode and compatibility of the schema registry. + + --mode=MODE + The mode and compatibility of the schema registry. + +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/memorystore/instances/update b/gcloud/alpha/memorystore/instances/update index 2b5f9cdca..c1389f4e7 100644 --- a/gcloud/alpha/memorystore/instances/update +++ b/gcloud/alpha/memorystore/instances/update @@ -32,10 +32,10 @@ SYNOPSIS [--engine-configs=[ENGINE_CONFIGS,...] | --update-engine-configs=[UPDATE_ENGINE_CONFIGS,...] --clear-engine-configs - | --remove-engine-configs=[__REMOVE_ENGINE_CONFIGS,...]] + | --remove-engine-configs=REMOVE_ENGINE_CONFIGS] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update the configuration of a Memorystore instance. @@ -754,8 +754,21 @@ FLAGS --clear-engine-configs Clear engine_configs value and set to empty map. - --remove-engine-configs=[__REMOVE_ENGINE_CONFIGS,...] - Remove existing value from map engine_configs. + --remove-engine-configs=REMOVE_ENGINE_CONFIGS + Remove existing value from map engine_configs. Sets + remove_engine_configs value. + + Shorthand Example: + + --remove-engine-configs=string,string + + JSON Example: + + --remove-engine-configs=["string"] + + File Example: + + --remove-engine-configs=path_to_file.(yaml|json) Update labels. @@ -813,8 +826,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/model-armor/floorsettings/update b/gcloud/alpha/model-armor/floorsettings/update index 0ed5e393e..3b5380c53 100644 --- a/gcloud/alpha/model-armor/floorsettings/update +++ b/gcloud/alpha/model-armor/floorsettings/update @@ -41,7 +41,7 @@ OPTIONAL FLAGS Shorthand Example: - --add-rai-settings-filters=string --add-rai-settings-filters=string + --add-rai-settings-filters=string,string JSON Example: @@ -60,7 +60,7 @@ OPTIONAL FLAGS Shorthand Example: - --rai-settings-filters=string --rai-settings-filters=string + --rai-settings-filters=string,string JSON Example: @@ -75,7 +75,7 @@ OPTIONAL FLAGS Shorthand Example: - --remove-rai-settings-filters=string --remove-rai-settings-filters=string + --remove-rai-settings-filters=string,string JSON Example: diff --git a/gcloud/alpha/model-armor/templates/update b/gcloud/alpha/model-armor/templates/update index 90ab9b659..0612df8b7 100644 --- a/gcloud/alpha/model-armor/templates/update +++ b/gcloud/alpha/model-armor/templates/update @@ -15,7 +15,7 @@ SYNOPSIS --template-metadata-custom-llm-response-safety-error-code=TEMPLATE_METADATA_CUSTOM_LLM_RESPONSE_SAFETY_ERROR_CODE --template-metadata-custom-llm-response-safety-error-message=TEMPLATE_METADATA_CUSTOM_LLM_RESPONSE_SAFETY_ERROR_MESSAGE --template-metadata-custom-prompt-safety-error-code=TEMPLATE_METADATA_CUSTOM_PROMPT_SAFETY_ERROR_CODE --template-metadata-custom-prompt-safety-error-message=TEMPLATE_METADATA_CUSTOM_PROMPT_SAFETY_ERROR_MESSAGE --[no-]template-metadata-ignore-partial-invocation-failures --[no-]template-metadata-log-operations --[no-]template-metadata-log-sanitize-operations] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Updates a Template. @@ -347,8 +347,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/netapp/storage-pools/create b/gcloud/alpha/netapp/storage-pools/create index c7ed22749..a6381b7b2 100644 --- a/gcloud/alpha/netapp/storage-pools/create +++ b/gcloud/alpha/netapp/storage-pools/create @@ -9,7 +9,9 @@ SYNOPSIS --service-level=SERVICE_LEVEL [--active-directory=ACTIVE_DIRECTORY] [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] [--custom-performance-enabled=CUSTOM_PERFORMANCE_ENABLED] - [--description=DESCRIPTION] [--enable-ldap=ENABLE_LDAP] + [--description=DESCRIPTION] + [--enable-hot-tier-auto-resize=ENABLE_HOT_TIER_AUTO_RESIZE] + [--enable-ldap=ENABLE_LDAP] [--hot-tier-size=HOT_TIER_SIZE] [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] [--replica-zone=REPLICA_ZONE] [--total-iops=TOTAL_IOPS] [--total-throughput=TOTAL_THROUGHPUT] [--zone=ZONE] @@ -155,10 +157,18 @@ OPTIONAL FLAGS --description=DESCRIPTION A description of the Cloud NetApp Storage Pool + --enable-hot-tier-auto-resize=ENABLE_HOT_TIER_AUTO_RESIZE + Boolean flag indicating whether Storage Pool is allowed to use hot tier + auto resize + --enable-ldap=ENABLE_LDAP Boolean flag indicating whether Storage Pool is a NFS LDAP Storage Pool or not + --hot-tier-size=HOT_TIER_SIZE + The hot tier size of the Storage Pool in GiB/s units. If no throughput + unit is specified, GiB/s is assumed. + Kms config resource - The KMS config to attach to the Storage Pool. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. diff --git a/gcloud/alpha/netapp/storage-pools/update b/gcloud/alpha/netapp/storage-pools/update index 356daa107..cc56ea208 100644 --- a/gcloud/alpha/netapp/storage-pools/update +++ b/gcloud/alpha/netapp/storage-pools/update @@ -8,10 +8,11 @@ SYNOPSIS [--active-directory=ACTIVE_DIRECTORY] [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] [--capacity=CAPACITY] [--description=DESCRIPTION] - [--replica-zone=REPLICA_ZONE] [--total-iops=TOTAL_IOPS] - [--total-throughput=TOTAL_THROUGHPUT] [--update-labels=[KEY=VALUE,...]] - [--zone=ZONE] [--clear-labels | --remove-labels=[KEY,...]] - [GCLOUD_WIDE_FLAG ...] + [--enable-hot-tier-auto-resize=ENABLE_HOT_TIER_AUTO_RESIZE] + [--hot-tier-size=HOT_TIER_SIZE] [--replica-zone=REPLICA_ZONE] + [--total-iops=TOTAL_IOPS] [--total-throughput=TOTAL_THROUGHPUT] + [--update-labels=[KEY=VALUE,...]] [--zone=ZONE] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Updates a Storage Pool with given arguments @@ -96,6 +97,14 @@ FLAGS --description=DESCRIPTION A description of the Cloud NetApp Storage Pool + --enable-hot-tier-auto-resize=ENABLE_HOT_TIER_AUTO_RESIZE + Boolean flag indicating whether Storage Pool is allowed to use hot tier + auto resize + + --hot-tier-size=HOT_TIER_SIZE + The hot tier size of the Storage Pool in GiB/s units. If no throughput + unit is specified, GiB/s is assumed. + --replica-zone=REPLICA_ZONE String indicating replica zone for the Storage Pool diff --git a/gcloud/alpha/network-services/operations/cancel b/gcloud/alpha/network-services/operations/cancel index 7137b15ef..159b4e55e 100644 --- a/gcloud/alpha/network-services/operations/cancel +++ b/gcloud/alpha/network-services/operations/cancel @@ -62,5 +62,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 network-services operations cancel + + $ gcloud beta network-services operations cancel diff --git a/gcloud/alpha/network-services/operations/describe b/gcloud/alpha/network-services/operations/describe index 111a68acc..3d4a0ceca 100644 --- a/gcloud/alpha/network-services/operations/describe +++ b/gcloud/alpha/network-services/operations/describe @@ -62,5 +62,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 network-services operations describe + + $ gcloud beta network-services operations describe diff --git a/gcloud/alpha/network-services/operations/help b/gcloud/alpha/network-services/operations/help index 3218d7f76..1c55a0cb2 100644 --- a/gcloud/alpha/network-services/operations/help +++ b/gcloud/alpha/network-services/operations/help @@ -32,5 +32,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 network-services operations + + $ gcloud beta network-services operations diff --git a/gcloud/alpha/network-services/operations/list b/gcloud/alpha/network-services/operations/list index 5a3cbb8fc..d8a083628 100644 --- a/gcloud/alpha/network-services/operations/list +++ b/gcloud/alpha/network-services/operations/list @@ -83,5 +83,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 network-services operations list + + $ gcloud beta network-services operations list diff --git a/gcloud/alpha/network-services/operations/wait b/gcloud/alpha/network-services/operations/wait index 990d6bc92..35a6913ce 100644 --- a/gcloud/alpha/network-services/operations/wait +++ b/gcloud/alpha/network-services/operations/wait @@ -61,5 +61,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 network-services operations wait + + $ gcloud beta network-services operations wait diff --git a/gcloud/alpha/resource-manager/tags/keys/create b/gcloud/alpha/resource-manager/tags/keys/create index 5db344a89..390908496 100644 --- a/gcloud/alpha/resource-manager/tags/keys/create +++ b/gcloud/alpha/resource-manager/tags/keys/create @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha resource-manager tags keys create (SHORT_NAME --parent=PARENT) - [--async] [--description=DESCRIPTION] [--purpose=PURPOSE] + [--allowed-values-regex=ALLOWED_VALUES_REGEX] [--async] + [--description=DESCRIPTION] [--purpose=PURPOSE] [--purpose-data=[network=NETWORK],[organization=ORGANIZATION]] [GCLOUD_WIDE_FLAG ...] @@ -36,6 +37,9 @@ POSITIONAL ARGUMENTS this group are specified. FLAGS + --allowed-values-regex=ALLOWED_VALUES_REGEX + User-assigned regex of allowed short names of TagValues under a TagKey. + --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/alpha/resource-manager/tags/keys/update b/gcloud/alpha/resource-manager/tags/keys/update index 7b6b8f91b..d568784df 100644 --- a/gcloud/alpha/resource-manager/tags/keys/update +++ b/gcloud/alpha/resource-manager/tags/keys/update @@ -3,7 +3,8 @@ NAME TagKey resource's description SYNOPSIS - gcloud alpha resource-manager tags keys update RESOURCE_NAME [--async] + gcloud alpha resource-manager tags keys update RESOURCE_NAME + [--allowed-values-regex=ALLOWED_VALUES_REGEX] [--async] [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -14,12 +15,12 @@ EXAMPLES To update a TagKey with id 123, run: $ gcloud alpha resource-manager tags keys update tagKeys/123 \ - --description=foobar + --description=foobar --allowed-values-regex=.* To update a TagKey named env under organization 456, run: $ gcloud alpha resource-manager tags keys update 456/env \ - --description=foobar + --description=foobar --allowed-values-regex=.* POSITIONAL ARGUMENTS RESOURCE_NAME @@ -30,6 +31,9 @@ POSITIONAL ARGUMENTS dashes (-), underscores ( _ ), dots (.), and alphanumerics between. FLAGS + --allowed-values-regex=ALLOWED_VALUES_REGEX + User-assigned regex of allowed short names of TagValues under a TagKey. + --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/alpha/run/worker-pools/help b/gcloud/alpha/run/worker-pools/help index 0b80bdbd4..429d29f14 100644 --- a/gcloud/alpha/run/worker-pools/help +++ b/gcloud/alpha/run/worker-pools/help @@ -42,6 +42,10 @@ COMMANDS list (ALPHA) List available worker-pools. + replace + (ALPHA) Create or replace a worker-pool from a YAML worker-pool + specification. + update (ALPHA) Update Cloud Run environment variables and other configuration settings. diff --git a/gcloud/alpha/run/worker-pools/replace b/gcloud/alpha/run/worker-pools/replace new file mode 100644 index 000000000..8b7ed0c74 --- /dev/null +++ b/gcloud/alpha/run/worker-pools/replace @@ -0,0 +1,46 @@ +NAME + gcloud alpha run worker-pools replace - create or replace a worker-pool + from a YAML worker-pool specification + +SYNOPSIS + gcloud alpha run worker-pools replace FILE [--async] [--dry-run] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Creates or replaces a worker-pool from a YAML worker-pool + specification. + +EXAMPLES + To replace the specification for a worker-pool defined in + my-worker-pool.yaml + + $ gcloud alpha run worker-pools replace my-worker-pool.yaml + +POSITIONAL ARGUMENTS + FILE + The absolute path to the YAML file with a Cloud Run worker-pool + definition for the worker-pool to update or create. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --dry-run + If set to true, only validates the configuration. The configuration + will not be applied. + +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/scc/iac-validation-reports/list b/gcloud/alpha/scc/iac-validation-reports/list index e95d9f5ff..51d2e1fa9 100644 --- a/gcloud/alpha/scc/iac-validation-reports/list +++ b/gcloud/alpha/scc/iac-validation-reports/list @@ -3,9 +3,10 @@ NAME Command Center IaC validation reports for an organization SYNOPSIS - gcloud alpha scc iac-validation-reports list PARENT [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha scc iac-validation-reports list + ([PARENT] --location=LOCATION --organization=ORGANIZATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Lists all the Cloud Security Command Center (SCC) IaC validation @@ -18,10 +19,32 @@ EXAMPLES $ gcloud alpha scc iac-validation-reports list \ organizations/123/locations/global/reports + Or using flags: + + $ gcloud alpha scc iac-validation-reports list --organization=123 \ + --location=global + POSITIONAL ARGUMENTS - PARENT - Parent of IaC validation reports. Formatted as - organizations//locations//reports. + Exactly one of these must be specified: + + [PARENT] + Parent of the IaC validation reports or fully qualified identifier + for the IaC validation reports. + + Specify organization and location using flags. + + --location=LOCATION + When data residency controls are enabled, this attribute specifies + the location in which the resource is located and applicable. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --organization=ORGANIZATION + The organization ID (e.g., 123) that contains the resource. + + This flag argument must be specified if any of the other arguments + in this group are specified. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/scc/manage/services/describe b/gcloud/alpha/scc/manage/services/describe index 976a232b1..4f4f2ea93 100644 --- a/gcloud/alpha/scc/manage/services/describe +++ b/gcloud/alpha/scc/manage/services/describe @@ -64,6 +64,16 @@ POSITIONAL ARGUMENTS ◆ cloud-run-threat-detection (can be abbreviated as crtd) + ◆ vm-manager (can be abbreviated as vmm) + + ◆ ec2-vulnerability-assessment (can be abbreviated as ec2-va) + + ◆ gce-vulnerability-assessment (can be abbreviated as gce-va) + + ◆ azure-vulnerability-assessment (can be abbreviated as azure-va) + + ◆ notebook-security-scanner (can be abbreviated as nss) + REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/alpha/scc/manage/services/update b/gcloud/alpha/scc/manage/services/update index d26d366a2..6764755cc 100644 --- a/gcloud/alpha/scc/manage/services/update +++ b/gcloud/alpha/scc/manage/services/update @@ -56,6 +56,16 @@ POSITIONAL ARGUMENTS ◆ cloud-run-threat-detection (can be abbreviated as crtd) + ◆ vm-manager (can be abbreviated as vmm) + + ◆ ec2-vulnerability-assessment (can be abbreviated as ec2-va) + + ◆ gce-vulnerability-assessment (can be abbreviated as gce-va) + + ◆ azure-vulnerability-assessment (can be abbreviated as azure-va) + + ◆ notebook-security-scanner (can be abbreviated as nss) + REQUIRED FLAGS At least one of these must be specified: diff --git a/gcloud/alpha/scc/posture-deployments/list b/gcloud/alpha/scc/posture-deployments/list index 29f4b81e9..558bceca9 100644 --- a/gcloud/alpha/scc/posture-deployments/list +++ b/gcloud/alpha/scc/posture-deployments/list @@ -3,9 +3,10 @@ NAME Security Command Center posture deployments SYNOPSIS - gcloud alpha scc posture-deployments list PARENT [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha scc posture-deployments list + ([PARENT] --location=LOCATION --organization=ORGANIZATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) List the details of the Cloud Security Command Center (SCC) posture @@ -18,11 +19,30 @@ EXAMPLES $ gcloud alpha scc posture-deployments list \ organizations/123/locations/global + $ gcloud alpha scc posture-deployments list --organization=123 \ + --location=global + POSITIONAL ARGUMENTS - PARENT - Organization for listing the Cloud Security Command Center posture - deployments available at the organization level. Formatted as - organizations//locations/. + Exactly one of these must be specified: + + [PARENT] + Parent of Cloud Security Command Center posture deployments. + Formatted as organizations//locations/. + + Specify organization and location using flags. + + --location=LOCATION + When data residency controls are enabled, this attribute specifies + the location in which the resource is located and applicable. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --organization=ORGANIZATION + The organization ID (e.g., 123) that contains the resource. + + This flag argument must be specified if any of the other arguments + in this group are specified. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/scc/posture-templates/list b/gcloud/alpha/scc/posture-templates/list index 74f02a65a..dd1e108fc 100644 --- a/gcloud/alpha/scc/posture-templates/list +++ b/gcloud/alpha/scc/posture-templates/list @@ -13,16 +13,15 @@ DESCRIPTION EXAMPLES To list Cloud Security Command Center posture templates for organization - 123, run: + 123 and in the global location, run: $ gcloud alpha scc posture-templates list \ organizations/123/locations/global POSITIONAL ARGUMENTS PARENT - Organization for listing the Cloud Security Command Center posture - templates available at the organization level. Formatted as - organizations//locations/. + Parent of Cloud Security Command Center posture templates. Formatted as + organizations//locations/ LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/scheduler/jobs/create/app-engine b/gcloud/alpha/scheduler/jobs/create/app-engine index 66df28a39..c478fbb05 100644 --- a/gcloud/alpha/scheduler/jobs/create/app-engine +++ b/gcloud/alpha/scheduler/jobs/create/app-engine @@ -7,8 +7,8 @@ SYNOPSIS --schedule=SCHEDULE [--attempt-deadline=ATTEMPT_DEADLINE] [--description=DESCRIPTION] [--headers=[KEY=VALUE,...]] [--http-method=HTTP_METHOD; default="post"] - [--max-backoff=MAX_BACKOFF; default="1h"] - [--max-doublings=MAX_DOUBLINGS; default=16] + [--max-backoff=MAX_BACKOFF; default="3600s"] + [--max-doublings=MAX_DOUBLINGS; default=5] [--max-retry-attempts=MAX_RETRY_ATTEMPTS] [--max-retry-duration=MAX_RETRY_DURATION] [--min-backoff=MIN_BACKOFF; default="5s"] @@ -70,16 +70,16 @@ REQUIRED FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). OPTIONAL FLAGS --attempt-deadline=ATTEMPT_DEADLINE @@ -99,11 +99,11 @@ OPTIONAL FLAGS HTTP method to use for the request. HTTP_METHOD must be one of: delete, get, head, post, put. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -112,13 +112,14 @@ OPTIONAL FLAGS in range 0-5 inclusive. Default is 0. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task was + Time limit for retrying a failed job, measured from when the job was first run. If specified with --max-retry-attempts greater than 0, the - task will be retried until both limits are reached. Default is 0 (which - means unlimited). + job will be retried until both limits are reached. Default is 0 seconds + (which means unlimited); however, if --max-retry-attempts is also 0, a + job attempt won't be retried if it fails. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. --relative-url=RELATIVE_URL; default="/" diff --git a/gcloud/alpha/scheduler/jobs/create/http b/gcloud/alpha/scheduler/jobs/create/http index 100219df4..e161e4c63 100644 --- a/gcloud/alpha/scheduler/jobs/create/http +++ b/gcloud/alpha/scheduler/jobs/create/http @@ -7,8 +7,8 @@ SYNOPSIS --schedule=SCHEDULE --uri=URI [--attempt-deadline=ATTEMPT_DEADLINE] [--description=DESCRIPTION] [--headers=[KEY=VALUE,...]] [--http-method=HTTP_METHOD; default="post"] - [--max-backoff=MAX_BACKOFF; default="1h"] - [--max-doublings=MAX_DOUBLINGS; default=16] + [--max-backoff=MAX_BACKOFF; default="3600s"] + [--max-doublings=MAX_DOUBLINGS; default=5] [--max-retry-attempts=MAX_RETRY_ATTEMPTS] [--max-retry-duration=MAX_RETRY_DURATION] [--min-backoff=MIN_BACKOFF; default="5s"] @@ -73,16 +73,16 @@ REQUIRED FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --uri=URI The full URI path that the request will be sent to. This string must @@ -109,11 +109,11 @@ OPTIONAL FLAGS HTTP method to use for the request. HTTP_METHOD must be one of: delete, get, head, post, put. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -122,13 +122,14 @@ OPTIONAL FLAGS in range 0-5 inclusive. Default is 0. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task was + Time limit for retrying a failed job, measured from when the job was first run. If specified with --max-retry-attempts greater than 0, the - task will be retried until both limits are reached. Default is 0 (which - means unlimited). + job will be retried until both limits are reached. Default is 0 seconds + (which means unlimited); however, if --max-retry-attempts is also 0, a + job attempt won't be retried if it fails. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. --time-zone=TIME_ZONE; default="Etc/UTC" diff --git a/gcloud/alpha/scheduler/jobs/create/pubsub b/gcloud/alpha/scheduler/jobs/create/pubsub index c34cec8ac..b7255e2d3 100644 --- a/gcloud/alpha/scheduler/jobs/create/pubsub +++ b/gcloud/alpha/scheduler/jobs/create/pubsub @@ -7,8 +7,8 @@ SYNOPSIS --schedule=SCHEDULE --topic=TOPIC (--attributes=ATTRIBUTES --message-body=MESSAGE_BODY | --message-body-from-file=PATH_TO_FILE) [--description=DESCRIPTION] - [--max-backoff=MAX_BACKOFF; default="1h"] - [--max-doublings=MAX_DOUBLINGS; default=16] + [--max-backoff=MAX_BACKOFF; default="3600s"] + [--max-doublings=MAX_DOUBLINGS; default=5] [--max-retry-attempts=MAX_RETRY_ATTEMPTS] [--max-retry-duration=MAX_RETRY_DURATION] [--min-backoff=MIN_BACKOFF; default="5s"] @@ -68,16 +68,16 @@ REQUIRED FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --topic=TOPIC Name of the Google Cloud Pub/Sub topic to publish to when the job runs. @@ -105,11 +105,11 @@ OPTIONAL FLAGS --description=DESCRIPTION Human-readable description of the job. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -118,13 +118,14 @@ OPTIONAL FLAGS in range 0-5 inclusive. Default is 0. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task was + Time limit for retrying a failed job, measured from when the job was first run. If specified with --max-retry-attempts greater than 0, the - task will be retried until both limits are reached. Default is 0 (which - means unlimited). + job will be retried until both limits are reached. Default is 0 seconds + (which means unlimited); however, if --max-retry-attempts is also 0, a + job attempt won't be retried if it fails. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. --time-zone=TIME_ZONE; default="Etc/UTC" diff --git a/gcloud/alpha/scheduler/jobs/update/app-engine b/gcloud/alpha/scheduler/jobs/update/app-engine index 948f58931..e478b40da 100644 --- a/gcloud/alpha/scheduler/jobs/update/app-engine +++ b/gcloud/alpha/scheduler/jobs/update/app-engine @@ -9,8 +9,8 @@ SYNOPSIS [--version=VERSION] [--clear-headers | --remove-headers=[REMOVE_HEADERS,...] --update-headers=[KEY=VALUE,...]] - [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"] - [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16] + [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="3600s"] + [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=5] [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS] [--clear-max-retry-duration | --max-retry-duration=MAX_RETRY_DURATION] [--clear-message-body | --message-body=MESSAGE_BODY @@ -85,16 +85,16 @@ FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --version=VERSION Version of the App Engine service to send the request to. @@ -118,16 +118,16 @@ FLAGS --clear-max-backoff Clear the field corresponding to --max-backoff. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). At most one of these can be specified: --clear-max-doublings Clear the field corresponding to --max-doublings. - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -146,10 +146,11 @@ FLAGS Clear the field corresponding to --max-retry-duration. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task - was first run. If specified with --max-retry-attempts greater than 0, - the task will be retried until both limits are reached. Default is 0 - (which means unlimited). + Time limit for retrying a failed job, measured from when the job was + first run. If specified with --max-retry-attempts greater than 0, the + job will be retried until both limits are reached. Default is 0 + seconds (which means unlimited); however, if --max-retry-attempts is + also 0, a job attempt won't be retried if it fails. At most one of these can be specified: @@ -173,7 +174,7 @@ FLAGS Clear the field corresponding to --min-backoff. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. At most one of these can be specified: diff --git a/gcloud/alpha/scheduler/jobs/update/http b/gcloud/alpha/scheduler/jobs/update/http index db71df719..9b157cb45 100644 --- a/gcloud/alpha/scheduler/jobs/update/http +++ b/gcloud/alpha/scheduler/jobs/update/http @@ -14,8 +14,8 @@ SYNOPSIS : --oidc-token-audience=OIDC_TOKEN_AUDIENCE]] [--clear-headers | --remove-headers=[REMOVE_HEADERS,...] --update-headers=[KEY=VALUE,...]] - [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"] - [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16] + [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="3600s"] + [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=5] [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS] [--clear-max-retry-duration | --max-retry-duration=MAX_RETRY_DURATION] [--clear-message-body | --message-body=MESSAGE_BODY @@ -88,16 +88,16 @@ FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --uri=URI The full URI path that the request will be sent to. This string must @@ -173,16 +173,16 @@ FLAGS --clear-max-backoff Clear the field corresponding to --max-backoff. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). At most one of these can be specified: --clear-max-doublings Clear the field corresponding to --max-doublings. - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -201,10 +201,11 @@ FLAGS Clear the field corresponding to --max-retry-duration. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task - was first run. If specified with --max-retry-attempts greater than 0, - the task will be retried until both limits are reached. Default is 0 - (which means unlimited). + Time limit for retrying a failed job, measured from when the job was + first run. If specified with --max-retry-attempts greater than 0, the + job will be retried until both limits are reached. Default is 0 + seconds (which means unlimited); however, if --max-retry-attempts is + also 0, a job attempt won't be retried if it fails. At most one of these can be specified: @@ -228,7 +229,7 @@ FLAGS Clear the field corresponding to --min-backoff. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. At most one of these can be specified: diff --git a/gcloud/alpha/scheduler/jobs/update/pubsub b/gcloud/alpha/scheduler/jobs/update/pubsub index 8e6a41685..d28f7b5ed 100644 --- a/gcloud/alpha/scheduler/jobs/update/pubsub +++ b/gcloud/alpha/scheduler/jobs/update/pubsub @@ -7,8 +7,8 @@ SYNOPSIS [--description=DESCRIPTION] [--schedule=SCHEDULE] [--topic=TOPIC] [--clear-attributes | --remove-attributes=[REMOVE_ATTRIBUTES,...] --update-attributes=[KEY=VALUE,...]] - [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"] - [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16] + [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="3600s"] + [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=5] [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS] [--clear-max-retry-duration | --max-retry-duration=MAX_RETRY_DURATION] [--clear-min-backoff | --min-backoff=MIN_BACKOFF; default="5s"] @@ -71,16 +71,16 @@ FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --topic=TOPIC Name of the Google Cloud Pub/Sub topic to publish to when the job runs. @@ -103,16 +103,16 @@ FLAGS --clear-max-backoff Clear the field corresponding to --max-backoff. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). At most one of these can be specified: --clear-max-doublings Clear the field corresponding to --max-doublings. - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -131,10 +131,11 @@ FLAGS Clear the field corresponding to --max-retry-duration. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task - was first run. If specified with --max-retry-attempts greater than 0, - the task will be retried until both limits are reached. Default is 0 - (which means unlimited). + Time limit for retrying a failed job, measured from when the job was + first run. If specified with --max-retry-attempts greater than 0, the + job will be retried until both limits are reached. Default is 0 + seconds (which means unlimited); however, if --max-retry-attempts is + also 0, a job attempt won't be retried if it fails. At most one of these can be specified: @@ -142,7 +143,7 @@ FLAGS Clear the field corresponding to --min-backoff. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. At most one of these can be specified: diff --git a/gcloud/alpha/spanner/databases/help b/gcloud/alpha/spanner/databases/help index 9e48cff79..81e002878 100644 --- a/gcloud/alpha/spanner/databases/help +++ b/gcloud/alpha/spanner/databases/help @@ -54,6 +54,9 @@ COMMANDS get-iam-policy (ALPHA) Get the IAM policy for a Cloud Spanner database. + import + (ALPHA) Import data from various source files to Cloud Spanner. + list (ALPHA) List the Cloud Spanner databases contained within the given instance. diff --git a/gcloud/alpha/spanner/databases/import b/gcloud/alpha/spanner/databases/import new file mode 100644 index 000000000..24afb6b34 --- /dev/null +++ b/gcloud/alpha/spanner/databases/import @@ -0,0 +1,72 @@ +NAME + gcloud alpha spanner databases import - import data from various source + files to Cloud Spanner + +SYNOPSIS + gcloud alpha spanner databases import --database=DATABASE + --instance=INSTANCE --source-format=SOURCE_FORMAT + --source-uri=SOURCE_URI [--csv-field-delimiter=CSV_FIELD_DELIMITER] + [--csv-line-delimiter=CSV_LINE_DELIMITER] + [--database-dialect=DATABASE_DIALECT] [--schema-uri=SCHEMA_URI] + [--table-name=TABLE_NAME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Import data from various source files to Cloud Spanner. + +EXAMPLES + To import data from a source file to Cloud Spanner: + + $ gcloud alpha spanner databases import --instance=instanceA \ + --database=databaseA --table-name=tableA \ + --source-uri=gs://bucket/data.csv --source-format=csv \ + --schema_uri=gs://bucket/schema.csv + + $ gcloud alpha spanner databases import --instance=instanceA \ + --database=databaseA --source-uri=gs://bucket/dump.sql \ + --source-format=mysqldump + +REQUIRED FLAGS + --database=DATABASE + Cloud Spanner database ID. + + --instance=INSTANCE + Cloud Spanner instance ID. + + --source-format=SOURCE_FORMAT + Format of the file with data to import.Supported formats: csv or + myssqldump or pgdump + + --source-uri=SOURCE_URI + URI of the file with data to import + +OPTIONAL FLAGS + --csv-field-delimiter=CSV_FIELD_DELIMITER + Field delimiter for CSV files. + + --csv-line-delimiter=CSV_LINE_DELIMITER + Line delimiter for CSV files. + + --database-dialect=DATABASE_DIALECT + Dialect for the spanner database. DATABASE_DIALECT must be one of: + POSTGRESQL, GOOGLE_STANDARD_SQL. + + --schema-uri=SCHEMA_URI + URI of the file with schema of the data to import + + --table-name=TABLE_NAME + Cloud Spanner table name + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/spanner/databases/update b/gcloud/alpha/spanner/databases/update index 94323ba19..1f72505a4 100644 --- a/gcloud/alpha/spanner/databases/update +++ b/gcloud/alpha/spanner/databases/update @@ -3,7 +3,9 @@ NAME SYNOPSIS gcloud alpha spanner databases update (DATABASE : --instance=INSTANCE) - [--async] [--[no-]enable-drop-protection] [GCLOUD_WIDE_FLAG ...] + [--async] + [--[no-]enable-drop-protection | --kms-keys=KMS_KEY,[KMS_KEY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a Cloud Spanner database. @@ -21,6 +23,12 @@ EXAMPLES $ gcloud alpha spanner databases update my-database \ --no-enable-drop-protection + To update KMS key references for a Cloud Spanner database 'my-database', + run: + + $ gcloud alpha spanner databases update my-database \ + --kms-keys="KEY1,KEY2" + POSITIONAL ARGUMENTS Database resource - The Cloud Spanner database to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -58,10 +66,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. - --[no-]enable-drop-protection - Enable database deletion protection on this database. Use - --enable-drop-protection to enable and --no-enable-drop-protection to - disable. + At most one of these can be specified: + + --[no-]enable-drop-protection + Enable database deletion protection on this database. Use + --enable-drop-protection to enable and --no-enable-drop-protection to + disable. + + --kms-keys=KMS_KEY,[KMS_KEY,...] + Update KMS key references for this database. Users should always + provide the full set of required KMS key references. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/spanner/operations/describe b/gcloud/alpha/spanner/operations/describe index cd722f448..14b308f95 100644 --- a/gcloud/alpha/spanner/operations/describe +++ b/gcloud/alpha/spanner/operations/describe @@ -27,7 +27,7 @@ EXAMPLES $ gcloud alpha spanner operations describe _auto_12345 \ --instance=my-instance-id --backup=my-backup-id - To describe a Cloud Spanner instance partition operation, run: + To describe an instance partition operation, run: $ gcloud alpha spanner operations describe _auto_12345 \ --instance=my-instance-id --instance-partition=my-partition-id @@ -55,7 +55,7 @@ OPTIONAL FLAGS executing on. --instance-partition=INSTANCE_PARTITION - For instance partition operations, the name of the instance partition + For an instance partition operation, the name of the instance partition the operation is executing on. GCLOUD WIDE FLAGS diff --git a/gcloud/alpha/sql/backups/restore b/gcloud/alpha/sql/backups/restore index 480b936e5..bd9f63613 100644 --- a/gcloud/alpha/sql/backups/restore +++ b/gcloud/alpha/sql/backups/restore @@ -161,7 +161,10 @@ OPTIONAL FLAGS --cpu=CPU Whole number value indicating how many cores are desired in the machine. Both --cpu and --memory must be specified if a custom machine - type is desired, and the --tier flag must be omitted. + type is desired, and the --tier flag must be omitted.--cpu and --memory + flags are not compatible with the Enterprise Plus edition. These flags + should not be used when creating an Enterprise Plus edition, as the + machine configuration is determined by the --tier flag instead. --database-version=DATABASE_VERSION The database engine type and versions. If left unspecified, no changes @@ -255,7 +258,10 @@ OPTIONAL FLAGS machine. A size unit should be provided (eg. 3072MiB or 9GiB) - if no units are specified, GiB is assumed. Both --cpu and --memory must be specified if a custom machine type is desired, and the --tier flag must - be omitted. + be omitted. --cpu and --memory flags are not compatible with the + Enterprise Plus edition. These flags should not be used when creating + an Enterprise Plus edition, as the machine configuration is determined + by the --tier flag instead. --network=NETWORK Network in the current project that the instance will be part of. To diff --git a/gcloud/alpha/sql/instances/clone b/gcloud/alpha/sql/instances/clone index 22cb3b361..86dc1478f 100644 --- a/gcloud/alpha/sql/instances/clone +++ b/gcloud/alpha/sql/instances/clone @@ -34,35 +34,30 @@ EXAMPLES To clone an instance from its current state (most recent binary log coordinates): - $ gcloud alpha sql instances clone instance-foo instance-bar + $ gcloud alpha sql instances clone my-source-instance \ + my-cloned-instance To clone a MySQL instance from an earlier point in time (past binary log coordinates): - $ gcloud alpha sql instances clone instance-foo instance-bar \ - --bin-log-file-name mysql-bin.000020 --bin-log-position 170 + $ gcloud alpha sql instances clone my-source-instance \ + my-cloned-instance --bin-log-file-name mysql-bin.000020 \ + --bin-log-position 170 To clone a MySQL source instance at a specific point in time: - $ gcloud alpha sql instances clone instance-foo instance-bar \ - --point-in-time '2012-11-15T16:19:00.094Z' + $ gcloud alpha sql instances clone my-source-instance \ + my-cloned-instance --point-in-time '2012-11-15T16:19:00.094Z' To clone a PostgreSQL source instance at a specific point in time: - $ gcloud alpha sql instances clone instance-foo instance-bar \ - --point-in-time '2012-11-15T16:19:00.094Z' + $ gcloud alpha sql instances clone my-source-instance \ + my-cloned-instance --point-in-time '2012-11-15T16:19:00.094Z' To clone a SQL Server source instance at a specific point in time: - $ gcloud alpha sql instances clone instance-foo instance-bar \ - --point-in-time '2012-11-15T16:19:00.094Z' - - To specify the allocated IP range for the private IP target Instance - (reserved for future use): - $ gcloud alpha sql instances clone my-source-instance \ - my-cloned-instance \ - --allocated-ip-range-name cloned-instance-ip-range + my-cloned-instance --point-in-time '2012-11-15T16:19:00.094Z' To clone a deleted instance, include the name and deletion time of the source instance: @@ -71,6 +66,13 @@ EXAMPLES my-cloned-instance \ --source-instance-deletion-time '2012-11-15T16:19:00.094Z' + To specify the allocated IP range for the private IP target Instance + (reserved for future use): + + $ gcloud alpha sql instances clone my-source-instance \ + my-cloned-instance \ + --allocated-ip-range-name cloned-instance-ip-range + POSITIONAL ARGUMENTS SOURCE Cloud SQL instance ID of the source. diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index f61af1767..d5debcd92 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -215,7 +215,10 @@ FLAGS --cpu=CPU Whole number value indicating how many cores are desired in the machine. Both --cpu and --memory must be specified if a custom machine - type is desired, and the --tier flag must be omitted. + type is desired, and the --tier flag must be omitted.--cpu and --memory + flags are not compatible with the Enterprise Plus edition. These flags + should not be used when creating an Enterprise Plus edition, as the + machine configuration is determined by the --tier flag instead. --custom-subject-alternative-names=DNS,[DNS,[DNS]] A comma-separated list of DNS names to add to the instance's SSL @@ -385,7 +388,10 @@ FLAGS machine. A size unit should be provided (eg. 3072MiB or 9GiB) - if no units are specified, GiB is assumed. Both --cpu and --memory must be specified if a custom machine type is desired, and the --tier flag must - be omitted. + be omitted. --cpu and --memory flags are not compatible with the + Enterprise Plus edition. These flags should not be used when creating + an Enterprise Plus edition, as the machine configuration is determined + by the --tier flag instead. --network=NETWORK Network in the current project that the instance will be part of. To diff --git a/gcloud/alpha/sql/instances/get-latest-recovery-time b/gcloud/alpha/sql/instances/get-latest-recovery-time index c9d908ad7..bebcb43fb 100644 --- a/gcloud/alpha/sql/instances/get-latest-recovery-time +++ b/gcloud/alpha/sql/instances/get-latest-recovery-time @@ -16,6 +16,11 @@ EXAMPLES $ gcloud alpha sql instances get-latest-recovery-time instance-foo + To retrieve the latest recovery time for an instance that has been deleted: + + $ gcloud alpha sql instances get-latest-recovery-time instance-foo \ + --source-instance-deletion-time '2012-11-15T16:19:00.094Z' + POSITIONAL ARGUMENTS INSTANCE Cloud SQL instance ID. diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index 18a50682f..bfb05296d 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -45,6 +45,7 @@ SYNOPSIS [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] [--pricing-plan=PRICING_PLAN, -p PRICING_PLAN] + [--reconcile-psa-networking] [--[no-]recreate-replicas-on-primary-crash] [--remove-deny-maintenance-period] [--replication=REPLICATION] [--replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE] @@ -164,7 +165,10 @@ FLAGS --cpu=CPU Whole number value indicating how many cores are desired in the machine. Both --cpu and --memory must be specified if a custom machine - type is desired, and the --tier flag must be omitted. + type is desired, and the --tier flag must be omitted.--cpu and --memory + flags are not compatible with the Enterprise Plus edition. These flags + should not be used when creating an Enterprise Plus edition, as the + machine configuration is determined by the --tier flag instead. --database-version=DATABASE_VERSION The database engine type and versions. If left unspecified, no changes @@ -342,7 +346,10 @@ FLAGS machine. A size unit should be provided (eg. 3072MiB or 9GiB) - if no units are specified, GiB is assumed. Both --cpu and --memory must be specified if a custom machine type is desired, and the --tier flag must - be omitted. + be omitted. --cpu and --memory flags are not compatible with the + Enterprise Plus edition. These flags should not be used when creating + an Enterprise Plus edition, as the machine configuration is determined + by the --tier flag instead. --network=NETWORK Network in the current project that the instance will be part of. To @@ -388,6 +395,12 @@ FLAGS First Generation instances only. The pricing plan for this instance. PRICING_PLAN must be one of: PER_USE, PACKAGE. + --reconcile-psa-networking + Reconciles the instance's PSA networking configuration. If the instance + is already on a PSA network, the DNS zone and records associated with + the PSA write endpoint are either added if missing or updated if + incorrect. + --[no-]recreate-replicas-on-primary-crash Allow/Disallow replica recreation when a primary MySQL instance operating in reduced durability mode crashes. Not recreating the diff --git a/gcloud/alpha/sql/users/create b/gcloud/alpha/sql/users/create index 68e83ef8a..c2b270a0d 100644 --- a/gcloud/alpha/sql/users/create +++ b/gcloud/alpha/sql/users/create @@ -41,24 +41,20 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. - This flag is available only for MySQL. --[no-]password-policy-enable-failed-attempts-check - Enables the failed login attempts check if set to true. This flag is - available only for MySQL. Use + Enables the failed login attempts check if set to true. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. --[no-]password-policy-enable-password-verification - The current password must be specified when altering the password. This - flag is available only for MySQL. Use + The current password must be specified when altering the password. Use --password-policy-enable-password-verification to enable and --no-password-policy-enable-password-verification to disable. --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION Expiration duration after a password is updated, for example, 2d for 2 days. See gcloud topic datetimes for information on duration formats. - This flag is available only for MySQL. --type=TYPE Cloud SQL user's type. It determines the method to authenticate the diff --git a/gcloud/alpha/sql/users/set-password-policy b/gcloud/alpha/sql/users/set-password-policy index 108b611f8..95b41b874 100644 --- a/gcloud/alpha/sql/users/set-password-policy +++ b/gcloud/alpha/sql/users/set-password-policy @@ -57,24 +57,20 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. - This flag is available only for MySQL. --[no-]password-policy-enable-failed-attempts-check - Enables the failed login attempts check if set to true. This flag is - available only for MySQL. Use + Enables the failed login attempts check if set to true. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. --[no-]password-policy-enable-password-verification - The current password must be specified when altering the password. This - flag is available only for MySQL. Use + The current password must be specified when altering the password. Use --password-policy-enable-password-verification to enable and --no-password-policy-enable-password-verification to disable. --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION Expiration duration after a password is updated, for example, 2d for 2 days. See gcloud topic datetimes for information on duration formats. - This flag is available only for MySQL. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/storage/rm b/gcloud/alpha/storage/rm index 42bbfc1da..2b745504d 100644 --- a/gcloud/alpha/storage/rm +++ b/gcloud/alpha/storage/rm @@ -80,10 +80,11 @@ FLAGS --recursive, -R, -r Recursively delete the contents of buckets or directories that match - the path expression. If the path is set to a bucket, like gs://bucket, - the bucket is also deleted. This option implies the --all-versions - option. If you want to delete only live object versions, use the ``**'' - wildcard instead. + the path expression. By default, this will delete managed folders as + well. If the path is set to a bucket, like gs://bucket, the bucket is + also deleted. This option implies the --all-versions option. If you + want to delete only live object versions, use the ``**'' wildcard + instead. PRECONDITION FLAGS --if-generation-match=GENERATION diff --git a/gcloud/alpha/workstations/configs/create b/gcloud/alpha/workstations/configs/create index 7bb336de7..a2f1e656b 100644 --- a/gcloud/alpha/workstations/configs/create +++ b/gcloud/alpha/workstations/configs/create @@ -23,10 +23,8 @@ SYNOPSIS [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] - [--network-tags=[NETWORK_TAGS,...]] - [--pd-disk-type=PD_DISK_TYPE; default="pd-standard"] - [--pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete"] - [--pool-size=POOL_SIZE] [--replica-zones=[REPLICA_ZONES,...]] + [--network-tags=[NETWORK_TAGS,...]] [--pool-size=POOL_SIZE] + [--replica-zones=[REPLICA_ZONES,...]] [--running-timeout=RUNNING_TIMEOUT; default=7200] [--service-account=SERVICE_ACCOUNT] [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] @@ -38,7 +36,9 @@ SYNOPSIS | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE; default="codeoss"] [--kms-key=KMS_KEY : --kms-key-service-account=KMS_KEY_SERVICE_ACCOUNT] - [--pd-disk-size=PD_DISK_SIZE; default=200 + [--no-persistent-storage | --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 ...] DESCRIPTION @@ -272,7 +272,37 @@ FLAGS the root VM. --ephemeral-directory=[PROPERTY=VALUE,...] - Ephemeral directory which won't persist across workstation sessions. + Ephemeral directory which won't persist across workstation sessions. An + ephemeral directory is backed by a Compute Engine persistent disk whose + mount-path, source-snapshot, source-image, and read-only are + configurable. + + mount-path + Location of this directory in the running workstation. + + source-snapshot + Name of the snapshot to use as the source for the disk. Must be + empty if [source_image][] is set. Must be empty if [read_only][] is + false. Updating [source_snapshot][] will update content in the + ephemeral directory after the workstation is restarted. + + source-image + Name of the disk image to use as the source for the disk. Must be + empty if [source_snapshot][] is set. Updating [source_image][] will + update content in the ephemeral directory after the workstation is + restarted. + + read-only + Whether the disk is read only. If true, the disk may be shared by + multiple VMs and [source_snapshot][] must be set. Set to false when + not specified and true when specified. + + Example: + + $ gcloud alpha workstations configs create \ + --ephemeral-directory="mount-path=/home2,disk-type=pd-balanced,s\ + ource-snapshot=projects/my-project/global/snapshots/snapshot,read-on\ + ly=true" --grant-workstation-admin-role-on-create Default value is false. If set, creator of a workstation will get @@ -313,20 +343,6 @@ FLAGS $ gcloud alpha workstations configs create --network-tags=tag_1,tag_2 - --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. - --pool-size=POOL_SIZE Number of instances to pool for faster Workstation startup. @@ -441,12 +457,34 @@ FLAGS 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. + --no-persistent-storage + If set, workstations under this configuration will not have a + persistent directory. - --pd-source-snapshot=PD_SOURCE_SNAPSHOT - Name of the snapshot to use as the source for the home disk. + 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-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/ai/endpoints/list b/gcloud/beta/ai/endpoints/list index f707f4762..44b9472b0 100644 --- a/gcloud/beta/ai/endpoints/list +++ b/gcloud/beta/ai/endpoints/list @@ -21,7 +21,7 @@ EXAMPLES FLAGS --list-model-garden-endpoints-only - Whether to only list endpoints created from Model Garden. + Whether to only list endpoints related to Model Garden. Region resource - Cloud region to list endpoints. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but diff --git a/gcloud/beta/ai/model-garden/help b/gcloud/beta/ai/model-garden/help index c815c5603..28ccca5b6 100644 --- a/gcloud/beta/ai/model-garden/help +++ b/gcloud/beta/ai/model-garden/help @@ -20,8 +20,10 @@ GROUPS (BETA) List and use Model Garden models. 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 ai model-garden $ gcloud alpha ai model-garden diff --git a/gcloud/beta/ai/model-garden/models/deploy b/gcloud/beta/ai/model-garden/models/deploy index a6657f7aa..23cfbf1c2 100644 --- a/gcloud/beta/ai/model-garden/models/deploy +++ b/gcloud/beta/ai/model-garden/models/deploy @@ -190,8 +190,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. 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 ai model-garden models deploy $ gcloud alpha ai model-garden models deploy diff --git a/gcloud/beta/ai/model-garden/models/help b/gcloud/beta/ai/model-garden/models/help index 20c232a9d..1127586f0 100644 --- a/gcloud/beta/ai/model-garden/models/help +++ b/gcloud/beta/ai/model-garden/models/help @@ -26,8 +26,10 @@ COMMANDS model in Model Garden. 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 ai model-garden models $ gcloud alpha ai model-garden models diff --git a/gcloud/beta/ai/model-garden/models/list b/gcloud/beta/ai/model-garden/models/list index dcb339587..e3b727e3f 100644 --- a/gcloud/beta/ai/model-garden/models/list +++ b/gcloud/beta/ai/model-garden/models/list @@ -64,8 +64,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. 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 ai model-garden models list $ gcloud alpha ai model-garden models list diff --git a/gcloud/beta/ai/model-garden/models/list-deployment-config b/gcloud/beta/ai/model-garden/models/list-deployment-config index a64d54b27..45d625a93 100644 --- a/gcloud/beta/ai/model-garden/models/list-deployment-config +++ b/gcloud/beta/ai/model-garden/models/list-deployment-config @@ -61,8 +61,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. 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 ai model-garden models list-deployment-config $ gcloud alpha ai model-garden models list-deployment-config diff --git a/gcloud/beta/alloydb/clusters/create b/gcloud/beta/alloydb/clusters/create index b30be902c..0c879c0e8 100644 --- a/gcloud/beta/alloydb/clusters/create +++ b/gcloud/beta/alloydb/clusters/create @@ -54,7 +54,7 @@ OPTIONAL FLAGS for this cluster will be created in the allocated range. The range name must comply with RFC 1035. Specifically, the name must be 1-63 characters long and match the regular expression - [a-z]([-a-z0-9][a-z0-9])?. + [a-z]([-a-z0-9]*[a-z0-9])?. --async Return immediately, without waiting for the operation in progress to @@ -62,7 +62,7 @@ OPTIONAL FLAGS --database-version=DATABASE_VERSION Database version of the cluster. DATABASE_VERSION must be one of: - POSTGRES_14, POSTGRES_15, POSTGRES_16. + POSTGRES_14, POSTGRES_15, POSTGRES_16, POSTGRES_17. --enable-private-service-connect Enable Private Service Connect (PSC) connectivity for the cluster. diff --git a/gcloud/beta/alloydb/clusters/create-secondary b/gcloud/beta/alloydb/clusters/create-secondary index 65b45a33a..cf3f00641 100644 --- a/gcloud/beta/alloydb/clusters/create-secondary +++ b/gcloud/beta/alloydb/clusters/create-secondary @@ -50,7 +50,7 @@ OPTIONAL FLAGS for this cluster will be created in the allocated range. The range name must comply with RFC 1035. Specifically, the name must be 1-63 characters long and match the regular expression - [a-z]([-a-z0-9][a-z0-9])?. + [a-z]([-a-z0-9]*[a-z0-9])?. --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/beta/alloydb/clusters/help b/gcloud/beta/alloydb/clusters/help index e63c4b60f..79a3f7f3a 100644 --- a/gcloud/beta/alloydb/clusters/help +++ b/gcloud/beta/alloydb/clusters/help @@ -39,8 +39,7 @@ COMMANDS (BETA) List AlloyDB clusters in a given project and region. migrate-cloud-sql - (BETA) Migrate Cloud SQL instance to an AlloyDB cluster using an - existing Cloud SQL backup. + (BETA) Migrate Cloud SQL instance to an AlloyDB cluster. promote (BETA) Promote an AlloyDB SECONDARY cluster in a given project and diff --git a/gcloud/beta/alloydb/clusters/migrate-cloud-sql b/gcloud/beta/alloydb/clusters/migrate-cloud-sql index 0c1011975..9fa020d22 100644 --- a/gcloud/beta/alloydb/clusters/migrate-cloud-sql +++ b/gcloud/beta/alloydb/clusters/migrate-cloud-sql @@ -1,6 +1,6 @@ NAME gcloud beta alloydb clusters migrate-cloud-sql - migrate Cloud SQL instance - to an AlloyDB cluster using an existing Cloud SQL backup + to an AlloyDB cluster SYNOPSIS gcloud beta alloydb clusters migrate-cloud-sql CLUSTER @@ -30,8 +30,8 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Migrate Cloud SQL instance to an AlloyDB cluster using an existing - Cloud SQL backup. + (BETA) This command migrates a Cloud SQL instance to an AlloyDB cluster + using an existing Cloud SQL backup. EXAMPLES To migrate a Cloud SQL instance to an AlloyDB cluster from a backup, run: @@ -80,7 +80,7 @@ OPTIONAL FLAGS for this cluster will be created in the allocated range. The range name must comply with RFC 1035. Specifically, the name must be 1-63 characters long and match the regular expression - [a-z]([-a-z0-9][a-z0-9])?. + [a-z]([-a-z0-9]*[a-z0-9])?. --async Return immediately, without waiting for the operation in progress to @@ -88,7 +88,7 @@ OPTIONAL FLAGS --database-version=DATABASE_VERSION Database version of the cluster. DATABASE_VERSION must be one of: - POSTGRES_14, POSTGRES_15, POSTGRES_16. + POSTGRES_14, POSTGRES_15, POSTGRES_16, POSTGRES_17. --enable-private-service-connect Enable Private Service Connect (PSC) connectivity for the cluster. @@ -343,8 +343,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. 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 alloydb clusters migrate-cloud-sql $ gcloud alpha alloydb clusters migrate-cloud-sql diff --git a/gcloud/beta/alloydb/clusters/restore b/gcloud/beta/alloydb/clusters/restore index 1be3f8efd..e334d3bb3 100644 --- a/gcloud/beta/alloydb/clusters/restore +++ b/gcloud/beta/alloydb/clusters/restore @@ -58,16 +58,17 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. - --source-cluster=SOURCE_CLUSTER - AlloyDB source cluster to restore from. This must either be the - full cluster name - (projects/myProject/locations/us-central1/backups/myCluster) or the - cluster ID (myCluster). In the second case, the project and - location are assumed to be the same as the restored cluster that is - being created. + Source for a point in time restore operation. - This flag argument must be specified if any of the other arguments - in this group are specified. + Exactly one of these must be specified: + + --source-cluster=SOURCE_CLUSTER + AlloyDB source cluster to restore from. This must either be the + full cluster name + (projects/myProject/locations/us-central1/backups/myCluster) or + the cluster ID (myCluster). In the second case, the project and + location are assumed to be the same as the restored cluster that + is being created. OPTIONAL FLAGS --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME @@ -76,7 +77,7 @@ OPTIONAL FLAGS for this cluster will be created in the allocated range. The range name must comply with RFC 1035. Specifically, the name must be 1-63 characters long and match the regular expression - [a-z]([-a-z0-9][a-z0-9])?. + [a-z]([-a-z0-9]*[a-z0-9])?. --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/beta/alloydb/instances/update b/gcloud/beta/alloydb/instances/update index 51e493534..da48f8fcd 100644 --- a/gcloud/beta/alloydb/instances/update +++ b/gcloud/beta/alloydb/instances/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta alloydb instances update INSTANCE --cluster=CLUSTER - --region=REGION [--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]] + --region=REGION [--activation-policy=ACTIVATION_POLICY] + [--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]] [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async] [--authorized-external-networks=[AUTHORIZED_NETWORK,...]] [--availability-type=AVAILABILITY_TYPE] @@ -52,6 +53,11 @@ REQUIRED FLAGS regions at https://cloud.google.com/sql/docs/instance-locations. OPTIONAL FLAGS + --activation-policy=ACTIVATION_POLICY + Activation Policy for the instance. Required to START or STOP an + instance. ALWAYS - The instance is up and running. NEVER - The instance + is stopped. ACTIVATION_POLICY must be one of: ALWAYS, NEVER. + --allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...] Comma-separated list of allowed consumer projects to create endpoints for Private Service Connect (PSC) connectivity for the instance. Only diff --git a/gcloud/beta/bigtable/instances/tables/create b/gcloud/beta/bigtable/instances/tables/create index 5b00ebf02..34556d5da 100644 --- a/gcloud/beta/bigtable/instances/tables/create +++ b/gcloud/beta/bigtable/instances/tables/create @@ -115,7 +115,7 @@ REQUIRED FLAGS --column-families=[COLUMN_FAMILIES,...] A double-quote (") wrapped list of family name and corresponding garbage collection rules concatenated by :, where the rules are - optional. For example: \ + optional. For example: "family_1,family_2:maxage=5d&&maxversions=2,family_3:maxage=10d||maxversions=5" OPTIONAL FLAGS diff --git a/gcloud/beta/bigtable/tables/create b/gcloud/beta/bigtable/tables/create index d5f8917dc..b4b81832c 100644 --- a/gcloud/beta/bigtable/tables/create +++ b/gcloud/beta/bigtable/tables/create @@ -114,7 +114,7 @@ REQUIRED FLAGS --column-families=[COLUMN_FAMILIES,...] A double-quote (") wrapped list of family name and corresponding garbage collection rules concatenated by :, where the rules are - optional. For example: \ + optional. For example: "family_1,family_2:maxage=5d&&maxversions=2,family_3:maxage=10d||maxversions=5" OPTIONAL FLAGS diff --git a/gcloud/beta/colab/runtime-templates/create b/gcloud/beta/colab/runtime-templates/create index 1012d9cbb..500c5a9c9 100644 --- a/gcloud/beta/colab/runtime-templates/create +++ b/gcloud/beta/colab/runtime-templates/create @@ -14,11 +14,7 @@ SYNOPSIS : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] --no-enable-internet-access --network=NETWORK [--subnetwork=SUBNETWORK - : --subnetwork-region=SUBNETWORK_REGION] - --post-startup-script=POST_STARTUP_SCRIPT - --post-startup-script-behavior=POST_STARTUP_SCRIPT_BEHAVIOR - --post-startup-script-url=POST_STARTUP_SCRIPT_URL - --set-env-vars=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + : --subnetwork-region=SUBNETWORK_REGION]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a Colab Enterprise runtime template, a VM configuration for @@ -216,25 +212,6 @@ OPTIONAL FLAGS fully specified name; ◇ provide the argument --subnetwork-region on the command line. - The software configuration of the runtime template. - - --post-startup-script=POST_STARTUP_SCRIPT - Post startup script in raw string to execute on the runtime. - - --post-startup-script-behavior=POST_STARTUP_SCRIPT_BEHAVIOR - The behavior of the post startup script. The default if passing a - post-startup-script-url is RUN_ONCE. POST_STARTUP_SCRIPT_BEHAVIOR - must be one of: POST_STARTUP_SCRIPT_BEHAVIOR_UNSPECIFIED, RUN_ONCE, - RUN_EVERY_START, DOWNLOAD_AND_RUN_EVERY_START. - - --post-startup-script-url=POST_STARTUP_SCRIPT_URL - Post startup script URL to execute on the runtime. This can be a - public or private Google Cloud Storage object. In the form of - gs://bucket/object or https://storage.googleapis.com/bucket/object. - - --set-env-vars=[KEY=VALUE,...] - Set environment variables used by the runtime. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/backend-services/create b/gcloud/beta/compute/backend-services/create index aeecaa426..924deb167 100644 --- a/gcloud/beta/compute/backend-services/create +++ b/gcloud/beta/compute/backend-services/create @@ -45,6 +45,8 @@ SYNOPSIS [--timeout=TIMEOUT; default="30s"] [--tls-settings=[authenticationConfig=AUTHENTICATIONCONFIG],[sni=SNI]] [--tracking-mode=TRACKING_MODE] + [--zonal-affinity-spillover=ZONAL_AFFINITY_SPILLOVER] + [--zonal-affinity-spillover-ratio=ZONAL_AFFINITY_SPILLOVER_RATIO] [--cache-key-query-string-blacklist=[QUERY_STRING,...] | --cache-key-query-string-whitelist=QUERY_STRING,[...]] [--custom-metrics=[CUSTOM_METRICS,...] @@ -541,12 +543,10 @@ FLAGS Load Balancer), the protocol must be one of: TCP, UDP, UNSPECIFIED. If the load-balancing-scheme is INTERNAL_SELF_MANAGED (Traffic - Director), the protocol must be one of: HTTP, HTTPS, HTTP2, GRPC, H2C - (beta only). + Director), the protocol must be one of: HTTP, HTTPS, HTTP2, GRPC, H2C. If the load-balancing-scheme is INTERNAL_MANAGED (Internal Application - Load Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C - (beta only). + Load Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C. If the load-balancing-scheme is INTERNAL_MANAGED (Internal proxy Network Load Balancer), the protocol must be only TCP. @@ -561,8 +561,7 @@ FLAGS If the load-balancing-scheme is EXTERNAL_MANAGED (Global external Application Load Balancer and regional external Application Load - Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C (beta - only). + Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C. If the load-balancing-scheme is EXTERNAL_MANAGED (Global external proxy Network Load Balancer), the protocol must be one of: TCP, SSL. @@ -757,6 +756,44 @@ FLAGS (https://cloud.google.com/load-balancing/docs/network/networklb-backend-service#tracking-mode). TRACKING_MODE must be one of: PER_CONNECTION, PER_SESSION. + --zonal-affinity-spillover=ZONAL_AFFINITY_SPILLOVER + Specifies whether zonal affinity is enabled or not. + + Can only be set if load balancing scheme is INTERNAL, + + The possible values are: + + ZONAL_AFFINITY_DISABLED + Zonal Affinity is disabled. The load balancer distributes new + connections to all healthy backend endpoints across all zones. + + ZONAL_AFFINITY_STAY_WITHIN_ZONE + Zonal Affinity is enabled. The load balancer distributes new + connections to all healthy backend endpoints in the local zone only. + If there are no healthy backend endpoints in the local zone, the load + balancer distributes new connections to all backend endpoints in the + local zone. + + ZONAL_AFFINITY_SPILL_CROSS_ZONE + Zonal Affinity is enabled. The load balancer distributes new + connections to all healthy backend endpoints in the local zone only. + If there aren't enough healthy backend endpoints in the local zone, + the load balancer distributes new connections to all healthy backend + endpoints across all zones. + + ZONAL_AFFINITY_SPILLOVER must be one of: ZONAL_AFFINITY_DISABLED, + ZONAL_AFFINITY_STAY_WITHIN_ZONE, ZONAL_AFFINITY_SPILL_CROSS_ZONE. + + --zonal-affinity-spillover-ratio=ZONAL_AFFINITY_SPILLOVER_RATIO + The value of the field must be in [0, 1]. When the ratio of the count + of healthy backend endpoints in a zone to the count of backend + endpoints in that same zone is equal to or above this threshold, the + load balancer distributes new connections to all healthy endpoints in + the local zone only. When the ratio of the count of healthy backend + endpoints in a zone to the count of backend endpoints in that same zone + is below this threshold, the load balancer distributes all new + connections to all healthy endpoints across all zones. + At most one of these can be specified: --cache-key-query-string-blacklist=[QUERY_STRING,...] diff --git a/gcloud/beta/compute/backend-services/update b/gcloud/beta/compute/backend-services/update index 6091ddba1..f437c4d43 100644 --- a/gcloud/beta/compute/backend-services/update +++ b/gcloud/beta/compute/backend-services/update @@ -37,6 +37,8 @@ SYNOPSIS [--subsetting-policy=SUBSETTING_POLICY; default="NONE"] [--subsetting-subset-size=SUBSETTING_SUBSET_SIZE] [--timeout=TIMEOUT] [--tracking-mode=TRACKING_MODE] + [--zonal-affinity-spillover=ZONAL_AFFINITY_SPILLOVER] + [--zonal-affinity-spillover-ratio=ZONAL_AFFINITY_SPILLOVER_RATIO] [--bypass-cache-on-request-headers=BYPASS_CACHE_ON_REQUEST_HEADERS | --no-bypass-cache-on-request-headers] [--cache-key-query-string-blacklist=[QUERY_STRING,...] @@ -380,12 +382,10 @@ FLAGS Load Balancer), the protocol must be one of: TCP, UDP, UNSPECIFIED. If the load-balancing-scheme is INTERNAL_SELF_MANAGED (Traffic - Director), the protocol must be one of: HTTP, HTTPS, HTTP2, GRPC, H2C - (beta only). + Director), the protocol must be one of: HTTP, HTTPS, HTTP2, GRPC, H2C. If the load-balancing-scheme is INTERNAL_MANAGED (Internal Application - Load Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C - (beta only). + Load Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C. If the load-balancing-scheme is INTERNAL_MANAGED (Internal proxy Network Load Balancer), the protocol must be only TCP. @@ -400,8 +400,7 @@ FLAGS If the load-balancing-scheme is EXTERNAL_MANAGED (Global external Application Load Balancer and regional external Application Load - Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C (beta - only). + Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C. If the load-balancing-scheme is EXTERNAL_MANAGED (Global external proxy Network Load Balancer), the protocol must be one of: TCP, SSL. @@ -562,6 +561,44 @@ FLAGS (https://cloud.google.com/load-balancing/docs/network/networklb-backend-service#tracking-mode). TRACKING_MODE must be one of: PER_CONNECTION, PER_SESSION. + --zonal-affinity-spillover=ZONAL_AFFINITY_SPILLOVER + Specifies whether zonal affinity is enabled or not. + + Can only be set if load balancing scheme is INTERNAL, + + The possible values are: + + ZONAL_AFFINITY_DISABLED + Zonal Affinity is disabled. The load balancer distributes new + connections to all healthy backend endpoints across all zones. + + ZONAL_AFFINITY_STAY_WITHIN_ZONE + Zonal Affinity is enabled. The load balancer distributes new + connections to all healthy backend endpoints in the local zone only. + If there are no healthy backend endpoints in the local zone, the load + balancer distributes new connections to all backend endpoints in the + local zone. + + ZONAL_AFFINITY_SPILL_CROSS_ZONE + Zonal Affinity is enabled. The load balancer distributes new + connections to all healthy backend endpoints in the local zone only. + If there aren't enough healthy backend endpoints in the local zone, + the load balancer distributes new connections to all healthy backend + endpoints across all zones. + + ZONAL_AFFINITY_SPILLOVER must be one of: ZONAL_AFFINITY_DISABLED, + ZONAL_AFFINITY_STAY_WITHIN_ZONE, ZONAL_AFFINITY_SPILL_CROSS_ZONE. + + --zonal-affinity-spillover-ratio=ZONAL_AFFINITY_SPILLOVER_RATIO + The value of the field must be in [0, 1]. When the ratio of the count + of healthy backend endpoints in a zone to the count of backend + endpoints in that same zone is equal to or above this threshold, the + load balancer distributes new connections to all healthy endpoints in + the local zone only. When the ratio of the count of healthy backend + endpoints in a zone to the count of backend endpoints in that same zone + is below this threshold, the load balancer distributes all new + connections to all healthy endpoints across all zones. + At most one of these can be specified: --bypass-cache-on-request-headers=BYPASS_CACHE_ON_REQUEST_HEADERS diff --git a/gcloud/beta/compute/commitments/create b/gcloud/beta/compute/commitments/create index 8c7023eda..4f345dd6c 100644 --- a/gcloud/beta/compute/commitments/create +++ b/gcloud/beta/compute/commitments/create @@ -114,7 +114,7 @@ OPTIONAL FLAGS general-purpose-c4d, general-purpose-e2, general-purpose-n2, general-purpose-n2d, general-purpose-n4, general-purpose-t2d, graphics-optimized, memory-optimized, memory-optimized-m3, - memory-optimized-m4, memory-optimized-x4-16tb, + memory-optimized-m4, memory-optimized-m4-6tb, memory-optimized-x4-16tb, memory-optimized-x4-24tb, memory-optimized-x4-32tb, storage-optimized-z3. diff --git a/gcloud/beta/compute/help b/gcloud/beta/compute/help index 90a2f37b1..cfdb04ecc 100644 --- a/gcloud/beta/compute/help +++ b/gcloud/beta/compute/help @@ -139,6 +139,9 @@ GROUPS packet-mirrorings (BETA) Manage Compute Engine packet mirroring resources. + preview-features + (BETA) Read and manipulate Compute Engine Preview Features. + project-info (BETA) Read and manipulate project-level data like quotas and metadata. diff --git a/gcloud/beta/compute/instance-groups/managed/create b/gcloud/beta/compute/instance-groups/managed/create index e672236e1..dad9f41be 100644 --- a/gcloud/beta/compute/instance-groups/managed/create +++ b/gcloud/beta/compute/instance-groups/managed/create @@ -24,7 +24,7 @@ SYNOPSIS [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] [--stopped-size=STOPPED_SIZE] [--suspended-size=SUSPENDED_SIZE] [--target-distribution-shape=SHAPE] [--target-pool=[TARGET_POOL,...]] - [--zones=ZONE,[ZONE,...]] + [--workload-policy=WORKLOAD_POLICY] [--zones=ZONE,[ZONE,...]] [--health-check=HEALTH_CHECK | --http-health-check=HTTP_HEALTH_CHECK | --https-health-check=HTTPS_HEALTH_CHECK] [--region=REGION | --zone=ZONE] @@ -326,6 +326,11 @@ OPTIONAL FLAGS Specifies any target pools you want the instances of this managed instance group to be part of. + --workload-policy=WORKLOAD_POLICY + Specifies the workload policy for the managed instance group. It can be + a full or partial URL to a resource policy containing the workload + policy. + --zones=ZONE,[ZONE,...] If this flag is specified a regional managed instance group will be created. The managed instance group will be in the same region as diff --git a/gcloud/beta/compute/instance-groups/managed/update b/gcloud/beta/compute/instance-groups/managed/update index 7abbf9bde..faeaedae6 100644 --- a/gcloud/beta/compute/instance-groups/managed/update +++ b/gcloud/beta/compute/instance-groups/managed/update @@ -31,6 +31,7 @@ SYNOPSIS | --http-health-check=HTTP_HEALTH_CHECK | --https-health-check=HTTPS_HEALTH_CHECK] [--region=REGION | --zone=ZONE] + [--remove-workload-policy | --workload-policy=WORKLOAD_POLICY] [--update-policy-max-surge=MAX_SURGE --update-policy-max-unavailable=MAX_UNAVAILABLE --update-policy-min-ready=MIN_READY @@ -386,6 +387,16 @@ FLAGS Overrides the default compute/zone property value for this command invocation. + At most one of these can be specified: + + --remove-workload-policy + Detaches the workload policy from the managed instance group. + + --workload-policy=WORKLOAD_POLICY + Specifies the workload policy for the managed instance group. It can + be a full or partial URL to a resource policy containing the workload + policy. + Parameters for setting update policy for this managed instance group. --update-policy-max-surge=MAX_SURGE diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index be3eca16d..99ad8db63 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -15,7 +15,8 @@ SYNOPSIS [--discard-local-ssds-at-termination-timestamp=DISCARD_LOCAL_SSDS_AT_TERMINATION_TIMESTAMP] [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], [interface=INTERFACE],[mode=MODE],[name=NAME]] - [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] + [--enable-display-device] [--[no-]enable-nested-virtualization] + [--[no-]enable-uefi-networking] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] [--graceful-shutdown] @@ -131,8 +132,7 @@ FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the @@ -419,6 +419,9 @@ FLAGS ▸ SCSI ▸ NVME + --enable-display-device + Enable a display device on VM instances. Disabled by default. + --[no-]enable-nested-virtualization If set to true, enables nested virtualization for the instance. Use --enable-nested-virtualization to enable and @@ -769,6 +772,10 @@ FLAGS Specifies the network attachment that this interface should connect to. Mutually exclusive with --network and --subnet flags. + vlan + VLAN tag of a dynamic network interface, must be an integer in the + range from 2 to 255 inclusively. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/beta/compute/instance-templates/create-with-container b/gcloud/beta/compute/instance-templates/create-with-container index f79843795..c25636c54 100644 --- a/gcloud/beta/compute/instance-templates/create-with-container +++ b/gcloud/beta/compute/instance-templates/create-with-container @@ -40,7 +40,8 @@ SYNOPSIS [--network-interface=[PROPERTY=VALUE,...]] [--network-tier=NETWORK_TIER] [--preemptible] [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] - [--private-network-ip=PRIVATE_NETWORK_IP] [--region=REGION] + [--private-network-ip=PRIVATE_NETWORK_IP] + [--provisioning-model=PROVISIONING_MODEL] [--region=REGION] [--resource-policies=[RESOURCE_POLICY,...]] [--no-restart-on-failure] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--stack-type=STACK_TYPE] [--subnet=SUBNET] @@ -120,8 +121,7 @@ FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the @@ -688,6 +688,27 @@ FLAGS Specifies the RFC1918 IP to assign to the instance. The IP should be in the subnet or legacy network IP range. + --provisioning-model=PROVISIONING_MODEL + Specifies the provisioning model for your VM instances. This choice + affects the price, availability, and how long your VM instances can + run. PROVISIONING_MODEL must be one of: + + FLEX_START + Instance is provisioned using the Flex Start provisioning model and + has a limited runtime. + RESERVATION_BOUND + The VM instances run for the entire duration of their associated + reservation. You can only specify this provisioning model if you + want your VM instances to consume a specific reservation with + either a calendar reservation mode or a dense deployment type. + SPOT + Compute Engine may stop a Spot VM instance whenever it needs + capacity. Because Spot VM instances don't have a guaranteed + runtime, they come at a discounted price. + STANDARD + The default option. The STANDARD provisioning model gives you full + control over your VM instances' runtime. + --region=REGION Region of the instance template to create. If not specified, you might be prompted to select a region (interactive mode only). diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index 0b9a3f681..e540f7a5d 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -173,8 +173,7 @@ OPTIONAL FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index 4e54c9d21..4d1d4b8bf 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -186,8 +186,7 @@ FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the @@ -841,6 +840,10 @@ FLAGS Specifies the network attachment that this interface should connect to. Mutually exclusive with --network and --subnet flags. + vlan + VLAN tag of a dynamic network interface, must be an integer in the + range from 2 to 255 inclusively. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index 1530fc8a7..08a674a99 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -137,8 +137,7 @@ FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the diff --git a/gcloud/beta/compute/instances/network-interfaces/add b/gcloud/beta/compute/instances/network-interfaces/add index 04208c3f5..acc744699 100644 --- a/gcloud/beta/compute/instances/network-interfaces/add +++ b/gcloud/beta/compute/instances/network-interfaces/add @@ -121,8 +121,8 @@ FLAGS Specifies the subnetwork this network interface belongs to. --vlan=VLAN - VLAN tag of a dynamic network interface, must be in range from 2 to - 4094 inclusively. + VLAN tag of a dynamic network interface, must be an integer in the + range from 2 to 255 inclusively. --zone=ZONE Zone of the instance to operate on. If not specified, you might be diff --git a/gcloud/beta/compute/interconnects/attachments/dedicated/create b/gcloud/beta/compute/interconnects/attachments/dedicated/create index ac60854b7..c9c413ea0 100644 --- a/gcloud/beta/compute/interconnects/attachments/dedicated/create +++ b/gcloud/beta/compute/interconnects/attachments/dedicated/create @@ -5,6 +5,10 @@ NAME SYNOPSIS gcloud beta 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/beta/compute/interconnects/attachments/dedicated/update b/gcloud/beta/compute/interconnects/attachments/dedicated/update index 506e605c7..bb005daac 100644 --- a/gcloud/beta/compute/interconnects/attachments/dedicated/update +++ b/gcloud/beta/compute/interconnects/attachments/dedicated/update @@ -4,7 +4,10 @@ NAME SYNOPSIS gcloud beta 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] @@ -53,6 +56,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/beta/compute/interconnects/attachments/groups/update b/gcloud/beta/compute/interconnects/attachments/groups/update index 706ab22f4..71c7db18e 100644 --- a/gcloud/beta/compute/interconnects/attachments/groups/update +++ b/gcloud/beta/compute/interconnects/attachments/groups/update @@ -7,7 +7,7 @@ SYNOPSIS [--attachments=[INTERCONNECT_ATTACHMENT,...]] [--description=DESCRIPTION] [--intended-availability-sla=INTENDED_AVAILABILITY_SLA] - [GCLOUD_WIDE_FLAG ...] + [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute interconnects attachments groups update is used @@ -35,7 +35,8 @@ EXAMPLES $ gcloud beta compute interconnects attachments groups update \ example-attachment-group \ - --attachments=region-1/attachment-1,region-2/attachment-2 + --attachments=region-1/attachment-1,region-2/attachment-2 \ + --update-mask=attachments Although you can add or remove member attachments using this command, it is recommended to add or remove member attachments using the add-members and @@ -56,6 +57,11 @@ FLAGS --intended-availability-sla=INTENDED_AVAILABILITY_SLA The availability SLA that the user intends this group to support. + --update-mask=UPDATE_MASK + Optional update mask to specify which fields to update. Use commas to + separate masks. If not specified, all fields present in the command + will be updated. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/interconnects/attachments/partner/create b/gcloud/beta/compute/interconnects/attachments/partner/create index d07e8f855..fd09a6207 100644 --- a/gcloud/beta/compute/interconnects/attachments/partner/create +++ b/gcloud/beta/compute/interconnects/attachments/partner/create @@ -5,6 +5,10 @@ NAME SYNOPSIS gcloud beta 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] [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...] @@ -45,6 +49,26 @@ REQUIRED FLAGS The 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/beta/compute/interconnects/attachments/partner/update b/gcloud/beta/compute/interconnects/attachments/partner/update index 20dbb0fb3..cd839e1ba 100644 --- a/gcloud/beta/compute/interconnects/attachments/partner/update +++ b/gcloud/beta/compute/interconnects/attachments/partner/update @@ -4,6 +4,8 @@ NAME SYNOPSIS gcloud beta 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] [--update-labels=[KEY=VALUE,...]] @@ -20,6 +22,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/beta/compute/interconnects/create b/gcloud/beta/compute/interconnects/create index cef9f3458..13d654cb5 100644 --- a/gcloud/beta/compute/interconnects/create +++ b/gcloud/beta/compute/interconnects/create @@ -107,6 +107,10 @@ OPTIONAL FLAGS If specified then the interconnect is created on Cross-Site Network capable hardware ports. This parameter can only be provided during interconnect INSERT and cannot be changed using interconnect PATCH. + L2_FORWARDING + If specified then the interconnect is created on L2 forwarding + capable hardware ports. This parameter can only be provided during + interconnect INSERT and cannot be changed using interconnect PATCH. MACSEC If specified then the interconnect is created on MACsec capable hardware ports. If not specified, the interconnect is created on diff --git a/gcloud/beta/compute/interconnects/groups/create-members b/gcloud/beta/compute/interconnects/groups/create-members index 1a4d72394..547335894 100644 --- a/gcloud/beta/compute/interconnects/groups/create-members +++ b/gcloud/beta/compute/interconnects/groups/create-members @@ -110,6 +110,10 @@ OPTIONAL FLAGS If specified then the interconnect is created on Cross-Site Network capable hardware ports. This parameter can only be provided during interconnect INSERT and cannot be changed using interconnect PATCH. + L2_FORWARDING + If specified then the interconnect is created on L2 forwarding + capable hardware ports. This parameter can only be provided during + interconnect INSERT and cannot be changed using interconnect PATCH. MACSEC If specified then the interconnect is created on MACsec capable hardware ports. If not specified, the interconnect is created on diff --git a/gcloud/beta/compute/interconnects/groups/update b/gcloud/beta/compute/interconnects/groups/update index 9f8c4a5e3..30b4e19da 100644 --- a/gcloud/beta/compute/interconnects/groups/update +++ b/gcloud/beta/compute/interconnects/groups/update @@ -6,7 +6,8 @@ SYNOPSIS gcloud beta compute interconnects groups update NAME [--description=DESCRIPTION] [--intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY] - [--interconnects=[INTERCONNECT,...]] [GCLOUD_WIDE_FLAG ...] + [--interconnects=[INTERCONNECT,...]] [--update-mask=UPDATE_MASK] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute interconnects groups update is used to update @@ -34,7 +35,8 @@ EXAMPLES $ gcloud beta compute interconnects groups update \ example-interconnect-group \ - --interconnects=interconnect-1,interconnect-2 + --interconnects=interconnect-1,interconnect-2 \ + --update-mask=interconnects Although you can add or remove member interconnects using this command, it is recommended to add or remove member interconnects using the add-members @@ -55,6 +57,11 @@ FLAGS --interconnects=[INTERCONNECT,...] Member interconnects to set the interconnect group to contain. + --update-mask=UPDATE_MASK + Optional update mask to specify which fields to update. Use commas to + separate masks. If not specified, all fields present in the command + will be updated. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/network-firewall-policies/create b/gcloud/beta/compute/network-firewall-policies/create index a0552a4ad..d4aea2e63 100644 --- a/gcloud/beta/compute/network-firewall-policies/create +++ b/gcloud/beta/compute/network-firewall-policies/create @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud beta compute network-firewall-policies create FIREWALL_POLICY - [--description=DESCRIPTION] [--global | --region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--policy-type=POLICY_TYPE] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute network-firewall-policies create is used to @@ -33,6 +33,10 @@ FLAGS --description=DESCRIPTION An optional, textual description for the network firewall policy. + --policy-type=POLICY_TYPE + Network firewall policy type. POLICY_TYPE must be one of: VPC_POLICY, + RDMA_ROCE_POLICY. + At most one of these can be specified: --global diff --git a/gcloud/beta/compute/org-security-policies/associations/create b/gcloud/beta/compute/org-security-policies/associations/create index 3f3911f64..beef1ec2b 100644 --- a/gcloud/beta/compute/org-security-policies/associations/create +++ b/gcloud/beta/compute/org-security-policies/associations/create @@ -18,6 +18,10 @@ DESCRIPTION security policy is a set of rules that controls access to various resources. + This command has billing implications. Projects in the hierarchy with + effective hierarchical security policies will be automatically enrolled + into Cloud Armor Enterprise if not already enrolled. + EXAMPLES To associate an organization security policy under folder with ID ``123456789" to folder ``987654321", run: diff --git a/gcloud/beta/compute/preview-features/describe b/gcloud/beta/compute/preview-features/describe new file mode 100644 index 000000000..fe5987bce --- /dev/null +++ b/gcloud/beta/compute/preview-features/describe @@ -0,0 +1,54 @@ +NAME + gcloud beta compute preview-features describe - describe a preview feature + +SYNOPSIS + gcloud beta compute preview-features describe PREVIEW_FEATURE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a preview feature. + +EXAMPLES + To retrieve a single preview feature and print its properties, run the + following command: + + $ gcloud beta compute preview-features describe my-preview-feature + +POSITIONAL ARGUMENTS + Preview feature resource - Name of the preview feature you want to + inspect. 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 preview_feature 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. + + PREVIEW_FEATURE + ID of the preview feature or fully qualified identifier for the + preview feature. + + To set the preview_feature attribute: + ▸ provide the argument preview_feature 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 compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute preview-features describe + diff --git a/gcloud/beta/compute/preview-features/help b/gcloud/beta/compute/preview-features/help new file mode 100644 index 000000000..3aa91bd6f --- /dev/null +++ b/gcloud/beta/compute/preview-features/help @@ -0,0 +1,33 @@ +NAME + gcloud beta compute preview-features - read and manipulate Compute Engine + Preview Features + +SYNOPSIS + gcloud beta compute preview-features COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Read and manipulate Compute Engine Preview Features. + +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) Describe a preview feature. + + list + (BETA) View preview features. + + update + (BETA) Update a preview feature's activation status. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute preview-features + diff --git a/gcloud/beta/compute/preview-features/list b/gcloud/beta/compute/preview-features/list new file mode 100644 index 000000000..3b470ac32 --- /dev/null +++ b/gcloud/beta/compute/preview-features/list @@ -0,0 +1,66 @@ +NAME + gcloud beta compute preview-features list - view preview features + +SYNOPSIS + gcloud beta compute preview-features list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) View preview features. + +EXAMPLES + To display all preview features, run the following command: + + $ gcloud beta compute preview-features list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute preview-features list + diff --git a/gcloud/beta/compute/preview-features/update b/gcloud/beta/compute/preview-features/update new file mode 100644 index 000000000..d746f7ae6 --- /dev/null +++ b/gcloud/beta/compute/preview-features/update @@ -0,0 +1,73 @@ +NAME + gcloud beta compute preview-features update - update a preview feature's + activation status + +SYNOPSIS + gcloud beta compute preview-features update PREVIEW_FEATURE + --activation-status=ACTIVATION_STATUS + (--custom-rollout-plan=CUSTOM_ROLLOUT_PLAN + | --rollout-plan=ROLLOUT_PLAN) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a preview feature's activation status. + +EXAMPLES + To enable/disable a preview feature's activation status, run the following + command: + + $ gcloud beta compute preview-features update + +POSITIONAL ARGUMENTS + Preview feature resource - Name of the preview feature you want to update. + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument preview_feature 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. + + PREVIEW_FEATURE + ID of the preview feature or fully qualified identifier for the + preview feature. + + To set the preview_feature attribute: + ▸ provide the argument preview_feature on the command line. + +REQUIRED FLAGS + --activation-status=ACTIVATION_STATUS + The activation status of the preview feature. ACTIVATION_STATUS must be + one of: disabled, enabled. + + The rollout plan of the preview feature. + + Exactly one of these must be specified: + + --custom-rollout-plan=CUSTOM_ROLLOUT_PLAN + Use a custom rollout plan by name. + + --rollout-plan=ROLLOUT_PLAN + Use a predefined rollout plan. ROLLOUT_PLAN must be one of: + fast-rollout, two-day-rollout. + +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 compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute preview-features update + diff --git a/gcloud/beta/compute/reservations/help b/gcloud/beta/compute/reservations/help index ee7acd2f4..a9d60cad6 100644 --- a/gcloud/beta/compute/reservations/help +++ b/gcloud/beta/compute/reservations/help @@ -24,6 +24,9 @@ GROUPS blocks (BETA) Manage Compute Engine reservation blocks. + sub-blocks + (BETA) Manage Compute Engine reservation sub blocks. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/beta/compute/reservations/sub-blocks/describe b/gcloud/beta/compute/reservations/sub-blocks/describe new file mode 100644 index 000000000..b82d2e3de --- /dev/null +++ b/gcloud/beta/compute/reservations/sub-blocks/describe @@ -0,0 +1,69 @@ +NAME + gcloud beta compute reservations sub-blocks describe - describe a Compute + Engine reservation sub block + +SYNOPSIS + gcloud beta compute reservations sub-blocks describe RESERVATION + --block-name=BLOCK_NAME --sub-block-name=SUB_BLOCK_NAME [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Compute Engine reservation sub block. + +EXAMPLES + To describe a reservation sub block in reservation exr1 in my-zone with + block name my-block and sub block name my-sub-block, run: + + $ gcloud beta compute reservations sub-blocks describe exr1 \ + --zone=my-zone --block-name=my-block \ + --sub-block-name=my-sub-block + +POSITIONAL ARGUMENTS + RESERVATION + Name of the reservation to describe. + +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. + +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 beta and might change without notice. These + variants are also available: + + $ gcloud compute reservations sub-blocks describe + + $ gcloud alpha compute reservations sub-blocks describe + diff --git a/gcloud/beta/compute/reservations/sub-blocks/help b/gcloud/beta/compute/reservations/sub-blocks/help new file mode 100644 index 000000000..cdfe21a1a --- /dev/null +++ b/gcloud/beta/compute/reservations/sub-blocks/help @@ -0,0 +1,32 @@ +NAME + gcloud beta compute reservations sub-blocks - manage Compute Engine + reservation sub blocks + +SYNOPSIS + gcloud beta compute reservations sub-blocks COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Compute Engine reservation sub blocks. + +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) Describe a Compute Engine reservation sub block. + + list + (BETA) List Compute Engine reservation sub blocks. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute reservations sub-blocks + + $ gcloud alpha compute reservations sub-blocks + diff --git a/gcloud/beta/compute/reservations/sub-blocks/list b/gcloud/beta/compute/reservations/sub-blocks/list new file mode 100644 index 000000000..168d5096f --- /dev/null +++ b/gcloud/beta/compute/reservations/sub-blocks/list @@ -0,0 +1,106 @@ +NAME + gcloud beta compute reservations sub-blocks list - list Compute Engine + reservation sub blocks + +SYNOPSIS + gcloud beta compute reservations sub-blocks list RESERVATION + --block-name=BLOCK_NAME [--zone=ZONE] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute reservations sub-blocks list displays all + Compute Engine reservation sub blocks in an extended reservation's block. + +EXAMPLES + To list all reservation sub blocks in an extended reservation's block + my-block in table form, run: + + $ gcloud beta compute reservations sub-blocks list \ + extended-reservation --block-name=my-block \ + --zone=us-central1-a --project=my-project + + To list the URIs of all reservation blocks in an extended reservation, run: + + $ gcloud beta compute reservations sub-blocks list \ + extended-reservation --block-name=my-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. + +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 beta and might change without notice. These + variants are also available: + + $ gcloud compute reservations sub-blocks list + + $ gcloud alpha compute reservations sub-blocks list + diff --git a/gcloud/beta/compute/resource-policies/create/workload-policy b/gcloud/beta/compute/resource-policies/create/workload-policy index 8d5e7dec7..8b1730ec9 100644 --- a/gcloud/beta/compute/resource-policies/create/workload-policy +++ b/gcloud/beta/compute/resource-policies/create/workload-policy @@ -12,6 +12,12 @@ SYNOPSIS DESCRIPTION (BETA) Create a Compute Engine workload resource policy. +EXAMPLES + To create a workload policy: + + $ gcloud beta compute resource-policies create workload-policy \ + NAME --type=TYPE + POSITIONAL ARGUMENTS NAME Name of the resource policy to operate on. @@ -86,8 +92,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. 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 compute resource-policies create workload-policy $ gcloud alpha compute resource-policies create workload-policy diff --git a/gcloud/beta/compute/routers/create b/gcloud/beta/compute/routers/create index 8b4ebf7e7..21890dfd2 100644 --- a/gcloud/beta/compute/routers/create +++ b/gcloud/beta/compute/routers/create @@ -2,7 +2,8 @@ NAME gcloud beta compute routers create - create a Compute Engine router SYNOPSIS - gcloud beta compute routers create NAME --network=NETWORK + gcloud beta compute routers create NAME + (--ncc-gateway=NCC_GATEWAY | --network=NETWORK) [--advertisement-mode=MODE] [--asn=ASN] [--async] [--bgp-identifier-range=BGP_IDENTIFIER_RANGE] [--description=DESCRIPTION] [--encrypted-interconnect-router] @@ -20,8 +21,13 @@ POSITIONAL ARGUMENTS Name of the router to create. REQUIRED FLAGS - --network=NETWORK - The network for this router + Exactly one of these must be specified: + + --ncc-gateway=NCC_GATEWAY + The NCC gateway for this router. + + --network=NETWORK + The network for this router OPTIONAL FLAGS --advertisement-mode=MODE diff --git a/gcloud/beta/compute/vpn-tunnels/create b/gcloud/beta/compute/vpn-tunnels/create index 67a9f51bd..4e3394743 100644 --- a/gcloud/beta/compute/vpn-tunnels/create +++ b/gcloud/beta/compute/vpn-tunnels/create @@ -14,9 +14,15 @@ SYNOPSIS [--description=DESCRIPTION] [--ike-version=IKE_VERSION] [--interface=INTERFACE] [--local-traffic-selector=CIDR,[CIDR,...]] [--peer-external-gateway-interface=PEER_EXTERNAL_GATEWAY_INTERFACE] - [--region=REGION] [--remote-traffic-selector=CIDR,[CIDR,...]] - [--router=ROUTER] [--router-region=ROUTER_REGION] - [GCLOUD_WIDE_FLAG ...] + [--phase1-dh=GROUPS,[GROUPS,...]] + [--phase1-encryption=ALGORITHMS,[ALGORITHMS,...]] + [--phase1-integrity=ALGORITHMS,[ALGORITHMS,...]] + [--phase1-prf=PSEUDORANDOM FUNCTIONS,[...]] + [--phase2-encryption=ALGORITHMS,[ALGORITHMS,...]] + [--phase2-integrity=ALGORITHMS,[ALGORITHMS,...]] + [--phase2-pfs=ALGORITHMS,[ALGORITHMS,...]] [--region=REGION] + [--remote-traffic-selector=CIDR,[CIDR,...]] [--router=ROUTER] + [--router-region=ROUTER_REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute vpn-tunnels create is used to create a Classic @@ -110,6 +116,27 @@ OPTIONAL FLAGS a Highly Available VPN gateway to an External Vpn Gateway. PEER_EXTERNAL_GATEWAY_INTERFACE must be one of: 0, 1, 2, 3. + --phase1-dh=GROUPS,[GROUPS,...] + Phase 1 Diffie-Hellman groups. + + --phase1-encryption=ALGORITHMS,[ALGORITHMS,...] + Phase 1 encryption algorithms. + + --phase1-integrity=ALGORITHMS,[ALGORITHMS,...] + Phase 1 integrity algorithms. + + --phase1-prf=PSEUDORANDOM FUNCTIONS,[...] + Phase 1 pseudorandom functions. + + --phase2-encryption=ALGORITHMS,[ALGORITHMS,...] + Phase 2 encryption algorithms. + + --phase2-integrity=ALGORITHMS,[ALGORITHMS,...] + Phase 2 integrity algorithms. + + --phase2-pfs=ALGORITHMS,[ALGORITHMS,...] + Phase 2 perfect forward secerecy algorithms. + --region=REGION Region of the VPN Tunnel to create. If not specified, you might be prompted to select a region (interactive mode only). diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index 7a471f8ec..2012a8439 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -486,13 +486,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -501,6 +502,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 238d1368d..954720450 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -518,13 +518,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -533,6 +534,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 78c5a5572..8c3dae4ad 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -530,13 +530,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -545,6 +546,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 5bf1c7c24..c9fd7740c 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -533,13 +533,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -548,6 +549,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 0b91a4cde..7e274c2b7 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -494,13 +494,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -509,6 +510,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/beta/container/backup-restore/backup-channels/create b/gcloud/beta/container/backup-restore/backup-channels/create index e775f5527..1b96ed08a 100644 --- a/gcloud/beta/container/backup-restore/backup-channels/create +++ b/gcloud/beta/container/backup-restore/backup-channels/create @@ -14,11 +14,11 @@ DESCRIPTION EXAMPLES To create a backup channel my-backup-channel in project my-project in - location us-central1 with destination project projects/1234567890, run: + location us-central1 with destination project projects/backup-project, run: $ gcloud beta container backup-restore backup-channels create \ my-backup-channel --project=my-project --location=us-central1 \ - --destination-project=projects/1234567890 + --destination-project=projects/backup-project POSITIONAL ARGUMENTS Backup channel resource - Name of the backup channel to create. Once the @@ -62,8 +62,8 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --destination-project=DESTINATION_PROJECT The project where Backups are allowed to be created. The format is - projects/{project}. Currently, {project} can only be the project - number. e.g. projects/1234567890. + projects/{project}. Project can be project number or project ID. E.g. + projects/1234567890 or projects/my-project. OPTIONAL FLAGS --async diff --git a/gcloud/beta/container/backup-restore/restore-channels/create b/gcloud/beta/container/backup-restore/restore-channels/create index 0f4432cc5..b2326b27e 100644 --- a/gcloud/beta/container/backup-restore/restore-channels/create +++ b/gcloud/beta/container/backup-restore/restore-channels/create @@ -14,11 +14,12 @@ DESCRIPTION EXAMPLES To create a restore channel my-restore-channel in project my-project in - location us-central1 with destination project projects/1234567890, run: + location us-central1 with destination project projects/restore-project, + run: $ gcloud beta container backup-restore restore-channels create \ my-restore-channel --project=my-project --location=us-central1 \ - --destination-project=projects/1234567890 + --destination-project=projects/restore-project POSITIONAL ARGUMENTS Restore channel resource - Name of the restore channel to create. Once the @@ -62,8 +63,8 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --destination-project=DESTINATION_PROJECT The project where Restores are allowed to be created. The format is - projects/{project}. Currently, {project} can only be the project - number. e.g. projects/1234567890. + projects/{project}. Project can be project number or project ID. E.g. + projects/1234567890 or projects/my-project. OPTIONAL FLAGS --async diff --git a/gcloud/beta/container/clusters/check-autopilot-compatibility b/gcloud/beta/container/clusters/check-autopilot-compatibility index 51591ef7a..33d917141 100644 --- a/gcloud/beta/container/clusters/check-autopilot-compatibility +++ b/gcloud/beta/container/clusters/check-autopilot-compatibility @@ -11,6 +11,13 @@ SYNOPSIS DESCRIPTION (BETA) Check autopilot compatibility of a running cluster. + For clusters with GKE version 1.31.6-gke.1027000 or later, you must enable + the control plane component that performs the check by running the gcloud + container clusters update command with the + `--enable-autopilot-compatiblity-auditing` + (https://cloud.google.com/sdk/gcloud/reference/container/clusters/update#--%5Bno-%5Denable-autopilot-compatibility-auditing) + flag. + EXAMPLES To check autopilot compatibility of an existing cluster, run: diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 576036863..7b8c017d5 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -10,6 +10,8 @@ SYNOPSIS gpu-sharing-strategy=GPU_SHARING_STRATEGY, max-shared-clients-per-gpu=MAX_SHARED_CLIENTS_PER_GPU],...]] [--addons=[ADDON[=ENABLED|DISABLED],...]] [--allow-route-overlap] + [--alpha-cluster-feature-gates=[FEATURE=true|false,...]] + [--anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG] [--async] [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] [--autoprovisioning-enable-insecure-kubelet-readonly-port] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] @@ -72,6 +74,7 @@ SYNOPSIS [--node-version=NODE_VERSION] [--notification-config=[pubsub=ENABLED|DISABLED, pubsub-topic=TOPIC,...]] [--num-nodes=NUM_NODES; default=3] + [--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT] [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] [--preemptible] [--private-endpoint-subnetwork=NAME] [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] @@ -232,6 +235,28 @@ FLAGS Must be used in conjunction with '--enable-ip-alias' or '--no-enable-ip-alias'. + --alpha-cluster-feature-gates=[FEATURE=true|false,...] + Selectively enable or disable Kubernetes alpha and beta + kubernetesfeature gates on alpha GKE cluster. Alpha clusters are not + covered by the Kubernetes Engine SLA and should not be used for + production workloads. + + --anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG + Enable or restrict anonymous access to the cluster. When enabled, + anonymous users will be authenticated as system:anonymous with the + group system:unauthenticated. Limiting access restricts anonymous + access to only the health check endpoints /readyz, /livez, and + /healthz. + + ANONYMOUS_AUTHENTICATION_CONFIG must be one of: + + ENABLED + 'ENABLED' enables anonymous calls. + LIMITED + 'LIMITED' restricts anonymous access to the cluster. Only calls to + the health check endpoints are allowed anonymously, all other calls + will be rejected. + --async Return immediately, without waiting for the operation in progress to complete. @@ -1077,6 +1102,19 @@ FLAGS --num-nodes=NUM_NODES; default=3 The number of nodes to be created in each of the cluster's zones. + --performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT + Sets the Performance Monitoring Unit level. Valid values are + architectural, standard and enhanced. PERFORMANCE_MONITORING_UNIT must + be one of: + + architectural + Enables architectural PMU events tied to non last level cache (LLC) + events. + enhanced + Enables most documented core/L2 and LLC PMU events. + standard + Enables most documented core/L2 PMU events. + --placement-policy=PLACEMENT_POLICY Indicates the desired resource policy to use. diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 1a3c50663..8c58b2e68 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -3,8 +3,9 @@ NAME for running containers SYNOPSIS - gcloud beta container clusters create-auto NAME [--async] - [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] + gcloud beta container clusters create-auto NAME + [--anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG] + [--async] [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] [--autoprovisioning-enable-insecure-kubelet-readonly-port] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] @@ -73,6 +74,22 @@ POSITIONAL ARGUMENTS 40 characters. FLAGS + --anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG + Enable or restrict anonymous access to the cluster. When enabled, + anonymous users will be authenticated as system:anonymous with the + group system:unauthenticated. Limiting access restricts anonymous + access to only the health check endpoints /readyz, /livez, and + /healthz. + + ANONYMOUS_AUTHENTICATION_CONFIG must be one of: + + ENABLED + 'ENABLED' enables anonymous calls. + LIMITED + 'LIMITED' restricts anonymous access to the cluster. Only calls to + the health check endpoints are allowed anonymously, all other calls + will be rejected. + --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index e390f37c8..f3cee105b 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta container clusters update NAME - (--autoprovisioning-cgroup-mode=AUTOPROVISIONING_CGROUP_MODE + (--anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG + | --autoprovisioning-cgroup-mode=AUTOPROVISIONING_CGROUP_MODE | --autoprovisioning-enable-insecure-kubelet-readonly-port | --autoprovisioning-network-tags=[TAGS,...] | --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] @@ -136,6 +137,22 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Exactly one of these must be specified: + --anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG + Enable or restrict anonymous access to the cluster. When enabled, + anonymous users will be authenticated as system:anonymous with the + group system:unauthenticated. Limiting access restricts anonymous + access to only the health check endpoints /readyz, /livez, and + /healthz. + + ANONYMOUS_AUTHENTICATION_CONFIG must be one of: + + ENABLED + 'ENABLED' enables anonymous calls. + LIMITED + 'LIMITED' restricts anonymous access to the cluster. Only calls + to the health check endpoints are allowed anonymously, all other + calls will be rejected. + --autoprovisioning-cgroup-mode=AUTOPROVISIONING_CGROUP_MODE Sets the cgroup mode for auto-provisioned nodes. @@ -310,10 +327,16 @@ REQUIRED FLAGS https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity --[no-]enable-autopilot-compatibility-auditing - Enables the Autopilot Compatibility Auditing Feature. See - https://cloud.google.com/sdk/gcloud/reference/container/clusters/check-autopilot-compatibility. - Only applicable to clusters with version >= 1.32. Use - --enable-autopilot-compatibility-auditing to enable and + Lets you run the gcloud container clusters + check-autopilot-compatibility + (https://cloud.google.com/sdk/gcloud/reference/container/clusters/check-autopilot-compatibility) + command to check whether your workloads are compatible with Autopilot + mode. This flag is only applicable to clusters that run version + 1.31.6-gke.1027000 or later. + + Note: This flag causes a control plane restart. + + Use --enable-autopilot-compatibility-auditing to enable and --no-enable-autopilot-compatibility-auditing to disable. --enable-autoscaling diff --git a/gcloud/beta/container/fleet/help b/gcloud/beta/container/fleet/help index feac29022..5e62f5efe 100644 --- a/gcloud/beta/container/fleet/help +++ b/gcloud/beta/container/fleet/help @@ -82,9 +82,15 @@ GROUPS operations (BETA) Manage Anthos fleet long-running operations. + packages + (BETA) Manage Fleet Packages resources. + policycontroller (BETA) Manage Policy Controller Feature. + rbacrolebindingactuation + (BETA) Manage RbacRoleBinding Actuation. + scopes (BETA) Manage scopes of all your GKE fleets. diff --git a/gcloud/beta/container/fleet/packages/create b/gcloud/beta/container/fleet/packages/create new file mode 100644 index 000000000..ffba482e8 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/create @@ -0,0 +1,43 @@ +NAME + gcloud beta container fleet packages create - create Package Rollouts Fleet + Package + +SYNOPSIS + gcloud beta container fleet packages create NAME --source=SOURCE + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create Package Rollouts Fleet Package. + +EXAMPLES + To create Fleet Package cert-manager-app, run: + + $ gcloud beta container fleet packages create cert-manager-app \ + --source=source.yaml + +POSITIONAL ARGUMENTS + NAME + Resource name. + +REQUIRED FLAGS + --source=SOURCE + Source file containing Fleet Package configuration. + +OPTIONAL FLAGS + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages create + diff --git a/gcloud/beta/container/fleet/packages/delete b/gcloud/beta/container/fleet/packages/delete new file mode 100644 index 000000000..8c0a69491 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/delete @@ -0,0 +1,68 @@ +NAME + gcloud beta container fleet packages delete - delete Package Rollouts Fleet + Package + +SYNOPSIS + gcloud beta container fleet packages delete + (FLEET_PACKAGE : --location=LOCATION) [--force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete Package Rollouts Fleet Package. + +EXAMPLES + To delete Fleet Package cert-manager-app in us-central1, run: + + $ gcloud beta container fleet packages delete cert-manager-app \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Fleet package resource - The Fleet Package to create. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument fleet_package on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + FLEET_PACKAGE + ID of the fleet-package or fully qualified identifier for the + fleet-package. + + To set the fleet-package attribute: + ▸ provide the argument fleet_package on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud zone or region for the fleet-package. + + To set the location attribute: + ▸ provide the argument fleet_package on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property config_delivery/location. + +FLAGS + --force + If true, force deletion of any child resources. Otherwise, attempting + to delete a Fleet Package with children will fail. + +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 fleet packages delete + diff --git a/gcloud/beta/container/fleet/packages/describe b/gcloud/beta/container/fleet/packages/describe new file mode 100644 index 000000000..e4ae00e7c --- /dev/null +++ b/gcloud/beta/container/fleet/packages/describe @@ -0,0 +1,68 @@ +NAME + gcloud beta container fleet packages describe - describe Package Rollouts + Fleet Package + +SYNOPSIS + gcloud beta container fleet packages describe + (FLEET_PACKAGE : --location=LOCATION) [--show-cluster-status] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe Package Rollouts Fleet Package. + +EXAMPLES + To view Fleet Package cert-manager-app in us-central1, run: + + $ gcloud beta container fleet packages describe cert-manager-app \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Fleet package resource - The Fleet Package 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 fleet_package on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + FLEET_PACKAGE + ID of the fleet-package or fully qualified identifier for the + fleet-package. + + To set the fleet-package attribute: + ▸ provide the argument fleet_package on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud zone or region for the fleet-package. + + To set the location attribute: + ▸ provide the argument fleet_package on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property config_delivery/location. + +FLAGS + --show-cluster-status + Show more information about the Fleet Package. + +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 fleet packages describe + diff --git a/gcloud/beta/container/fleet/packages/help b/gcloud/beta/container/fleet/packages/help new file mode 100644 index 000000000..08522bf96 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/help @@ -0,0 +1,47 @@ +NAME + gcloud beta container fleet packages - manage Fleet Packages resources + +SYNOPSIS + gcloud beta container fleet packages GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Fleet Packages resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + resource-bundles + (BETA) Commands for managing Package Rollouts Resource Bundles. + + rollouts + (BETA) Commands for managing Rollouts. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create Package Rollouts Fleet Package. + + delete + (BETA) Delete Package Rollouts Fleet Package. + + describe + (BETA) Describe Package Rollouts Fleet Package. + + list + (BETA) List Package Rollouts Fleet Packages. + + update + (BETA) Update Package Rollouts Fleet Package. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages + diff --git a/gcloud/beta/container/fleet/packages/list b/gcloud/beta/container/fleet/packages/list new file mode 100644 index 000000000..b9c9dbfa3 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/list @@ -0,0 +1,67 @@ +NAME + gcloud beta container fleet packages list - list Package Rollouts Fleet + Packages + +SYNOPSIS + gcloud beta container fleet packages list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Package Rollouts Fleet Packages. + +EXAMPLES + To list all Fleet Packages in us-central1, run: + + $ gcloud beta container fleet packages list --location=us-central1 + +FLAGS + --location=LOCATION + Google Cloud zone or region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages list + diff --git a/gcloud/beta/container/fleet/packages/resource-bundles/create b/gcloud/beta/container/fleet/packages/resource-bundles/create new file mode 100644 index 000000000..6cd5924ef --- /dev/null +++ b/gcloud/beta/container/fleet/packages/resource-bundles/create @@ -0,0 +1,43 @@ +NAME + gcloud beta container fleet packages resource-bundles create - create + Package Rollouts Resource Bundle + +SYNOPSIS + gcloud beta container fleet packages resource-bundles create NAME + [--description=DESCRIPTION] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create Package Rollouts Resource Bundle. + +EXAMPLES + To create Resource Bundle cert-manager in us-central1, run: + + $ gcloud beta container fleet packages resource-bundles create \ + cert-manager --location=us-central1 + +POSITIONAL ARGUMENTS + NAME + Resource name. + +FLAGS + --description=DESCRIPTION + Resource description. + + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages resource-bundles create + diff --git a/gcloud/beta/container/fleet/packages/resource-bundles/delete b/gcloud/beta/container/fleet/packages/resource-bundles/delete new file mode 100644 index 000000000..ec90e9621 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/resource-bundles/delete @@ -0,0 +1,43 @@ +NAME + gcloud beta container fleet packages resource-bundles delete - delete + Package Rollouts Resource Bundle + +SYNOPSIS + gcloud beta container fleet packages resource-bundles delete NAME [--force] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete Package Rollouts Resource Bundle. + +EXAMPLES + To delete Resource Bundle cert-manager in us-central1, run: + + $ gcloud beta container fleet packages resource-bundles delete \ + cert-manager --location=us-central1 + +POSITIONAL ARGUMENTS + NAME + Resource name. + +FLAGS + --force + If true, force deletion of any child resources. Otherwise, attempting + to delete a Resource Bundle with children will fail. + + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages resource-bundles delete + diff --git a/gcloud/beta/container/fleet/packages/resource-bundles/describe b/gcloud/beta/container/fleet/packages/resource-bundles/describe new file mode 100644 index 000000000..c85f743ed --- /dev/null +++ b/gcloud/beta/container/fleet/packages/resource-bundles/describe @@ -0,0 +1,39 @@ +NAME + gcloud beta container fleet packages resource-bundles describe - describe + Package Rollouts Resource Bundle + +SYNOPSIS + gcloud beta container fleet packages resource-bundles describe NAME + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe Package Rollouts Resource Bundle. + +EXAMPLES + To describe Resource Bundle cert-manager in us-central1, run: + + $ gcloud beta container fleet packages resource-bundles describe \ + cert-manager --location=us-central1 + +POSITIONAL ARGUMENTS + NAME + Resource name. + +FLAGS + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages resource-bundles describe + diff --git a/gcloud/beta/container/fleet/packages/resource-bundles/help b/gcloud/beta/container/fleet/packages/resource-bundles/help new file mode 100644 index 000000000..53c830b22 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/resource-bundles/help @@ -0,0 +1,47 @@ +NAME + gcloud beta container fleet packages resource-bundles - commands for + managing Package Rollouts Resource Bundles + +SYNOPSIS + gcloud beta container fleet packages resource-bundles GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) See gcloud beta container fleet packages resource-bundles --help for + help. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + releases + (BETA) Commands for managing Package Rollouts Releases. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create Package Rollouts Resource Bundle. + + delete + (BETA) Delete Package Rollouts Resource Bundle. + + describe + (BETA) Describe Package Rollouts Resource Bundle. + + list + (BETA) List Package Rollouts Resource Bundles. + + update + (BETA) Update Package Rollouts Resource Bundle. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages resource-bundles + diff --git a/gcloud/beta/container/fleet/packages/resource-bundles/list b/gcloud/beta/container/fleet/packages/resource-bundles/list new file mode 100644 index 000000000..dc74db411 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/resource-bundles/list @@ -0,0 +1,69 @@ +NAME + gcloud beta container fleet packages resource-bundles list - list Package + Rollouts Resource Bundles + +SYNOPSIS + gcloud beta container fleet packages resource-bundles list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Package Rollouts Resource Bundles. + +EXAMPLES + To list Resource Bundles in us-central1, run: + + $ gcloud beta container fleet packages resource-bundles list \ + --location=us-central1 + +FLAGS + --location=LOCATION + Google Cloud zone or region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages resource-bundles list + diff --git a/gcloud/beta/container/fleet/packages/resource-bundles/releases/create b/gcloud/beta/container/fleet/packages/resource-bundles/releases/create new file mode 100644 index 000000000..ee36e2bc6 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/resource-bundles/releases/create @@ -0,0 +1,73 @@ +NAME + gcloud beta container fleet packages resource-bundles releases create - + create Package Rollouts Release + +SYNOPSIS + gcloud beta container fleet packages resource-bundles releases create + --resource-bundle=RESOURCE_BUNDLE --source=SOURCE --version=VERSION + [--lifecycle=LIFECYCLE] [--location=LOCATION] + [--variants-pattern=VARIANTS_PATTERN] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create Package Rollouts Release. + +EXAMPLES + To create Release v1.0.0 for Resource Bundle my-bundle in us-central1, run: + + $ gcloud beta container fleet packages resource-bundles releases \ + create --version=v1.0.0 --resource-bundle=my-bundle \ + --source=manifest.yaml + + To create a Release with multiple variants in one directory, run: + + $ gcloud beta container fleet packages resource-bundles releases \ + create --version=v1.0.0 --resource-bundle=my-bundle \ + --source=/manifests/ --variants-pattern=manifest-*.yaml + + To create a Release with multiple variants across multiple directories, ex: + + $ gcloud beta container fleet packages resource-bundles releases \ + create --version=v1.0.0 --resource-bundle=my-bundle \ + --source=/manifests/ --variants-pattern=dir-*/ + +REQUIRED FLAGS + --resource-bundle=RESOURCE_BUNDLE + Resource Bundle name. + + --source=SOURCE + Source file or directory to create the Release from. e.g. + --source=manifest.yaml, --source=/manifests-dir/ Can optionally be + paired with the --variants-pattern arg to create multiple variants of a + Release. + + --version=VERSION + Version of the Release to create. + +OPTIONAL FLAGS + --lifecycle=LIFECYCLE + Lifecycle of the Release. + + --location=LOCATION + Google Cloud zone or region. + + --variants-pattern=VARIANTS_PATTERN + Glob pattern to Variants of the Release, to be paired with the --source + arg. ex: --source=/manifests-dir/ --variants-pattern=**, + --source=/manifests-dir/ --variants-pattern=us-*.yaml, + --source=/manifests/dir/ --variants-pattern=*/*.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. This + variant is also available: + + $ gcloud alpha container fleet packages resource-bundles releases \ + create + diff --git a/gcloud/beta/container/fleet/packages/resource-bundles/releases/delete b/gcloud/beta/container/fleet/packages/resource-bundles/releases/delete new file mode 100644 index 000000000..07f47e287 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/resource-bundles/releases/delete @@ -0,0 +1,50 @@ +NAME + gcloud beta container fleet packages resource-bundles releases delete - + delete Package Rollouts Release + +SYNOPSIS + gcloud beta container fleet packages resource-bundles releases delete + RELEASE --resource-bundle=RESOURCE_BUNDLE [--force] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete Package Rollouts Release. + +EXAMPLES + To delete Release v1.0.0 of cert-manager in us-central1, run: + + $ gcloud beta container fleet packages resource-bundles releases \ + delete v1.0.0 --location=us-central1 \ + --resource-bundle=cert-manager + +POSITIONAL ARGUMENTS + RELEASE + Release identifier, either a version or tag. + +REQUIRED FLAGS + --resource-bundle=RESOURCE_BUNDLE + Resource Bundle name. + +OPTIONAL FLAGS + --force + If true, force deletion of any child resources. Otherwise, attempting + to delete a Release with children will fail. + + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages resource-bundles releases \ + delete + diff --git a/gcloud/beta/container/fleet/packages/resource-bundles/releases/describe b/gcloud/beta/container/fleet/packages/resource-bundles/releases/describe new file mode 100644 index 000000000..8043df294 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/resource-bundles/releases/describe @@ -0,0 +1,46 @@ +NAME + gcloud beta container fleet packages resource-bundles releases describe - + describe Package Rollouts Release + +SYNOPSIS + gcloud beta container fleet packages resource-bundles releases describe + RELEASE --resource-bundle=RESOURCE_BUNDLE [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe Package Rollouts Release. + +EXAMPLES + To view release v1.0.0 of cert-manager in us-central1, run: + + $ gcloud beta container fleet packages resource-bundles releases \ + describe v1.0.0 --location=us-central1 \ + --resource-bundle=cert-manager + +POSITIONAL ARGUMENTS + RELEASE + Release identifier, either a version or tag. + +REQUIRED FLAGS + --resource-bundle=RESOURCE_BUNDLE + Resource Bundle name. + +OPTIONAL FLAGS + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages resource-bundles releases \ + describe + diff --git a/gcloud/beta/container/fleet/packages/resource-bundles/releases/help b/gcloud/beta/container/fleet/packages/resource-bundles/releases/help new file mode 100644 index 000000000..3336db362 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/resource-bundles/releases/help @@ -0,0 +1,41 @@ +NAME + gcloud beta container fleet packages resource-bundles releases - commands + for managing Package Rollouts Releases + +SYNOPSIS + gcloud beta container fleet packages resource-bundles releases COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) See gcloud beta container fleet packages resource-bundles releases + --help for help. + +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 Package Rollouts Release. + + delete + (BETA) Delete Package Rollouts Release. + + describe + (BETA) Describe Package Rollouts Release. + + list + (BETA) List Releases of a Resource Bundle. + + update + (BETA) Update Package Rollouts Release. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages resource-bundles releases + diff --git a/gcloud/beta/container/fleet/packages/resource-bundles/releases/list b/gcloud/beta/container/fleet/packages/resource-bundles/releases/list new file mode 100644 index 000000000..0decf5c13 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/resource-bundles/releases/list @@ -0,0 +1,74 @@ +NAME + gcloud beta container fleet packages resource-bundles releases list - list + Releases of a Resource Bundle + +SYNOPSIS + gcloud beta container fleet packages resource-bundles releases list + --resource-bundle=RESOURCE_BUNDLE [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Releases of a Resource Bundle. + +EXAMPLES + To list all Releases for bundle cert-manager in us-central1, run: + + $ gcloud beta container fleet packages resource-bundles releases \ + list --resource-bundle=cert-manager --location=us-central1 + +REQUIRED FLAGS + --resource-bundle=RESOURCE_BUNDLE + Resource Bundle name. + +FLAGS + --location=LOCATION + Google Cloud zone or region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages resource-bundles releases \ + list + diff --git a/gcloud/beta/container/fleet/packages/resource-bundles/releases/update b/gcloud/beta/container/fleet/packages/resource-bundles/releases/update new file mode 100644 index 000000000..1cdff7c20 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/resource-bundles/releases/update @@ -0,0 +1,49 @@ +NAME + gcloud beta container fleet packages resource-bundles releases update - + update Package Rollouts Release + +SYNOPSIS + gcloud beta container fleet packages resource-bundles releases update + RELEASE --resource-bundle=RESOURCE_BUNDLE [--lifecycle=LIFECYCLE] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update Package Rollouts Release. + +EXAMPLES + To update Release v1.0.0 for Resource Bundle my-bundle in us-central1, run: + + $ gcloud beta container fleet packages resource-bundles releases \ + update --version=v1.0.0 --resource-bundle=my-bundle \ + --lifecycle=PUBLISHED + +POSITIONAL ARGUMENTS + RELEASE + Release identifier, either a version or tag. + +REQUIRED FLAGS + --resource-bundle=RESOURCE_BUNDLE + Resource Bundle name. + +OPTIONAL FLAGS + --lifecycle=LIFECYCLE + Lifecycle of the Release. + + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages resource-bundles releases \ + update + diff --git a/gcloud/beta/container/fleet/packages/resource-bundles/update b/gcloud/beta/container/fleet/packages/resource-bundles/update new file mode 100644 index 000000000..75c7a66e7 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/resource-bundles/update @@ -0,0 +1,43 @@ +NAME + gcloud beta container fleet packages resource-bundles update - update + Package Rollouts Resource Bundle + +SYNOPSIS + gcloud beta container fleet packages resource-bundles update NAME + [--description=DESCRIPTION] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update Package Rollouts Resource Bundle. + +EXAMPLES + To update Resource Bundle cert-manager in us-central1, run: + + $ gcloud beta container fleet packages resource-bundles update \ + cert-manager --location=us-central1 ... + +POSITIONAL ARGUMENTS + NAME + Resource name. + +FLAGS + --description=DESCRIPTION + Resource description. + + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages resource-bundles update + diff --git a/gcloud/beta/container/fleet/packages/rollouts/abort b/gcloud/beta/container/fleet/packages/rollouts/abort new file mode 100644 index 000000000..b40c6c78c --- /dev/null +++ b/gcloud/beta/container/fleet/packages/rollouts/abort @@ -0,0 +1,74 @@ +NAME + gcloud beta container fleet packages rollouts abort - abort Rollout + resource + +SYNOPSIS + gcloud beta container fleet packages rollouts abort + (ROLLOUT : --fleet-package=FLEET_PACKAGE --location=LOCATION) + [--reason=REASON] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Abort Rollout resource. + +EXAMPLES + To abort Rollout 20240318 for cert-manager-app in us-central1, run: + + $ gcloud beta container fleet packages rollouts abort 20240318 \ + --fleet-package=cert-manager-app --location=us-central1 + +POSITIONAL ARGUMENTS + Rollout resource - The rollout to abort. 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 rollout on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + ROLLOUT + ID of the rollout or fully qualified identifier for the rollout. + + To set the rollout attribute: + ▸ provide the argument rollout on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --fleet-package=FLEET_PACKAGE + Fleet Package name. + + To set the fleet-package attribute: + ▸ provide the argument rollout on the command line with a fully + specified name; + ▸ provide the argument --fleet-package on the command line. + + --location=LOCATION + Google Cloud zone or region for the rollout. + + To set the location attribute: + ▸ provide the argument rollout on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property config_delivery/location. + +FLAGS + --reason=REASON + Reason for aborting rollout. + +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 fleet packages rollouts abort + diff --git a/gcloud/beta/container/fleet/packages/rollouts/describe b/gcloud/beta/container/fleet/packages/rollouts/describe new file mode 100644 index 000000000..19af2d308 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/rollouts/describe @@ -0,0 +1,47 @@ +NAME + gcloud beta container fleet packages rollouts describe - describe Rollout + resource + +SYNOPSIS + gcloud beta container fleet packages rollouts describe NAME + --fleet-package=FLEET_PACKAGE [--less] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe Rollout resource. + +EXAMPLES + To view Rollout 20240318 for cert-manager-app in us-central1, run: + + $ gcloud beta container fleet packages rollouts describe 20240318 \ + --fleet-package=cert-manager-app --location=us-central1 + +POSITIONAL ARGUMENTS + NAME + Resource name. + +REQUIRED FLAGS + --fleet-package=FLEET_PACKAGE + Parent Fleet Package of the Rollout. + +OPTIONAL FLAGS + --less + Show less verbose output. + + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages rollouts describe + diff --git a/gcloud/beta/container/fleet/packages/rollouts/help b/gcloud/beta/container/fleet/packages/rollouts/help new file mode 100644 index 000000000..79bf21eb8 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/rollouts/help @@ -0,0 +1,40 @@ +NAME + gcloud beta container fleet packages rollouts - commands for managing + Rollouts + +SYNOPSIS + gcloud beta container fleet packages rollouts COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) See gcloud beta container fleet packages rollouts --help for help. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + abort + (BETA) Abort Rollout resource. + + describe + (BETA) Describe Rollout resource. + + list + (BETA) List Rollouts of a Fleet Package. + + resume + (BETA) Resume suspended Rollout. + + suspend + (BETA) Suspend in-progress Rollout. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages rollouts + diff --git a/gcloud/beta/container/fleet/packages/rollouts/list b/gcloud/beta/container/fleet/packages/rollouts/list new file mode 100644 index 000000000..f4d1a985a --- /dev/null +++ b/gcloud/beta/container/fleet/packages/rollouts/list @@ -0,0 +1,77 @@ +NAME + gcloud beta container fleet packages rollouts list - list Rollouts of a + Fleet Package + +SYNOPSIS + gcloud beta container fleet packages rollouts list + --fleet-package=FLEET_PACKAGE [--less] [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Rollouts of a Fleet Package. + +EXAMPLES + To list all Rollouts for Fleet Package cert-manager-app in us-central1, + run: + + $ gcloud beta container fleet packages rollouts list \ + --fleet-package=cert-manager-app --location=us-central1 + +REQUIRED FLAGS + --fleet-package=FLEET_PACKAGE + Parent Fleet Package of the Rollout. + +FLAGS + --less + Show less verbose output. + + --location=LOCATION + Google Cloud zone or region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet packages rollouts list + diff --git a/gcloud/beta/container/fleet/packages/rollouts/resume b/gcloud/beta/container/fleet/packages/rollouts/resume new file mode 100644 index 000000000..23103647a --- /dev/null +++ b/gcloud/beta/container/fleet/packages/rollouts/resume @@ -0,0 +1,74 @@ +NAME + gcloud beta container fleet packages rollouts resume - resume suspended + Rollout + +SYNOPSIS + gcloud beta container fleet packages rollouts resume + (ROLLOUT : --fleet-package=FLEET_PACKAGE --location=LOCATION) + [--reason=REASON] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Resume suspended Rollout. + +EXAMPLES + To resume Rollout 20240318 for cert-manager-app in us-central1, run: + + $ gcloud beta container fleet packages rollouts resume 20240318 \ + --fleet-package=cert-manager-app --location=us-central1 + +POSITIONAL ARGUMENTS + Rollout resource - The rollout 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 rollout on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + ROLLOUT + ID of the rollout or fully qualified identifier for the rollout. + + To set the rollout attribute: + ▸ provide the argument rollout on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --fleet-package=FLEET_PACKAGE + Fleet Package name. + + To set the fleet-package attribute: + ▸ provide the argument rollout on the command line with a fully + specified name; + ▸ provide the argument --fleet-package on the command line. + + --location=LOCATION + Google Cloud zone or region for the rollout. + + To set the location attribute: + ▸ provide the argument rollout on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property config_delivery/location. + +FLAGS + --reason=REASON + Reason for resuming rollout. + +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 fleet packages rollouts resume + diff --git a/gcloud/beta/container/fleet/packages/rollouts/suspend b/gcloud/beta/container/fleet/packages/rollouts/suspend new file mode 100644 index 000000000..b871f2693 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/rollouts/suspend @@ -0,0 +1,74 @@ +NAME + gcloud beta container fleet packages rollouts suspend - suspend in-progress + Rollout + +SYNOPSIS + gcloud beta container fleet packages rollouts suspend + (ROLLOUT : --fleet-package=FLEET_PACKAGE --location=LOCATION) + [--reason=REASON] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Suspend in-progress Rollout. + +EXAMPLES + To suspend Rollout 20240318 for cert-manager-app in us-central1, run: + + $ gcloud beta container fleet packages rollouts suspend 20240318 \ + --fleet-package=cert-manager-app --location=us-central1 + +POSITIONAL ARGUMENTS + Rollout resource - The rollout to suspend. 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 rollout on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + ROLLOUT + ID of the rollout or fully qualified identifier for the rollout. + + To set the rollout attribute: + ▸ provide the argument rollout on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --fleet-package=FLEET_PACKAGE + Fleet Package name. + + To set the fleet-package attribute: + ▸ provide the argument rollout on the command line with a fully + specified name; + ▸ provide the argument --fleet-package on the command line. + + --location=LOCATION + Google Cloud zone or region for the rollout. + + To set the location attribute: + ▸ provide the argument rollout on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property config_delivery/location. + +FLAGS + --reason=REASON + Reason for suspending rollout. + +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 fleet packages rollouts suspend + diff --git a/gcloud/beta/container/fleet/packages/update b/gcloud/beta/container/fleet/packages/update new file mode 100644 index 000000000..d7ea3c8f5 --- /dev/null +++ b/gcloud/beta/container/fleet/packages/update @@ -0,0 +1,68 @@ +NAME + gcloud beta container fleet packages update - update Package Rollouts Fleet + Package + +SYNOPSIS + gcloud beta container fleet packages update + (FLEET_PACKAGE : --location=LOCATION) --source=SOURCE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update Package Rollouts Fleet Package. + +EXAMPLES + To update Fleet Package cert-manager-app, run: + + $ gcloud beta container fleet packages update cert-manager-app \ + --source=my_source.yaml + +POSITIONAL ARGUMENTS + Fleet package resource - The Fleet Package to create. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument fleet_package on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + FLEET_PACKAGE + ID of the fleet-package or fully qualified identifier for the + fleet-package. + + To set the fleet-package attribute: + ▸ provide the argument fleet_package on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud zone or region for the fleet-package. + + To set the location attribute: + ▸ provide the argument fleet_package on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property config_delivery/location. + +REQUIRED FLAGS + --source=SOURCE + Source file containing Fleet Package configuration. + +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 fleet packages update + diff --git a/gcloud/beta/container/fleet/rbacrolebindingactuation/describe b/gcloud/beta/container/fleet/rbacrolebindingactuation/describe new file mode 100644 index 000000000..b576bb59f --- /dev/null +++ b/gcloud/beta/container/fleet/rbacrolebindingactuation/describe @@ -0,0 +1,24 @@ +NAME + gcloud beta container fleet rbacrolebindingactuation describe - describe + the status of the RbacRoleBinding Actuation Feature in a fleet + +SYNOPSIS + gcloud beta container fleet rbacrolebindingactuation describe + [GCLOUD_WIDE_FLAG ...] + +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 container fleet rbacrolebindingactuation describe + + $ gcloud alpha container fleet rbacrolebindingactuation describe + diff --git a/gcloud/beta/container/fleet/rbacrolebindingactuation/help b/gcloud/beta/container/fleet/rbacrolebindingactuation/help new file mode 100644 index 000000000..d936ee348 --- /dev/null +++ b/gcloud/beta/container/fleet/rbacrolebindingactuation/help @@ -0,0 +1,34 @@ +NAME + gcloud beta container fleet rbacrolebindingactuation - manage + RbacRoleBinding Actuation + +SYNOPSIS + gcloud beta container fleet rbacrolebindingactuation COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage RbacRoleBinding Actuation. + +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) Describe the status of the RbacRoleBinding Actuation Feature in + a fleet. + + update + (BETA) Update RbacRoleBinding Actuation Feature. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet rbacrolebindingactuation + + $ gcloud alpha container fleet rbacrolebindingactuation + diff --git a/gcloud/beta/container/fleet/rbacrolebindingactuation/update b/gcloud/beta/container/fleet/rbacrolebindingactuation/update new file mode 100644 index 000000000..57708f26f --- /dev/null +++ b/gcloud/beta/container/fleet/rbacrolebindingactuation/update @@ -0,0 +1,55 @@ +NAME + gcloud beta container fleet rbacrolebindingactuation update - update + RbacRoleBinding Actuation Feature + +SYNOPSIS + gcloud beta container fleet rbacrolebindingactuation update + (--add-allowed-custom-role=ADD_ALLOWED_CUSTOM_ROLE + | --allowed-custom-roles=[ROLES,...] + | --remove-allowed-custom-role=REMOVE_ALLOWED_CUSTOM_ROLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command updates RbacRoleBinding Actuation Feature in a fleet. + +EXAMPLES + To update the RbacRoleBinding Actuation Feature, run: + + $ gcloud container fleet rbacrolebinding-actuation update \ + --allowed-custom-roles=role1,role2 + + $ gcloud container fleet rbacrolebinding-actuation update \ + --add-allowed-custom-role=role1 + + $ gcloud container fleet rbacrolebinding-actuation update \ + --remove-allowed-custom-role=role2 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --add-allowed-custom-role=ADD_ALLOWED_CUSTOM_ROLE + Add a single custom role to the allowed custom roles list. + + --allowed-custom-roles=[ROLES,...] + The list of allowed custom roles that can be used in scope + RBACRoleBindings. + + --remove-allowed-custom-role=REMOVE_ALLOWED_CUSTOM_ROLE + Remove a single custom role from the allowed custom roles list. + +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 container fleet rbacrolebindingactuation update + + $ gcloud alpha container fleet rbacrolebindingactuation update + diff --git a/gcloud/beta/container/fleet/scopes/rbacrolebindings/create b/gcloud/beta/container/fleet/scopes/rbacrolebindings/create index e3dfdb190..8fec6f6ec 100644 --- a/gcloud/beta/container/fleet/scopes/rbacrolebindings/create +++ b/gcloud/beta/container/fleet/scopes/rbacrolebindings/create @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud beta container fleet scopes rbacrolebindings create - (NAME : --location=LOCATION --scope=SCOPE) --role=ROLE - (--group=GROUP | --user=USER) [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + (NAME : --location=LOCATION --scope=SCOPE) + (--custom-role=CUSTOM_ROLE | --role=ROLE) (--group=GROUP | --user=USER) + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -26,6 +26,13 @@ EXAMPLES $ gcloud beta container fleet scopes rbacrolebindings create RBRB \ --scope=SCOPE --role=viewer --group=people@google.com + To create an RBAC RoleBinding with a custom role custom-role in scope SCOPE + for user person@google.com, run: + + $ gcloud beta container fleet scopes rbacrolebindings create RBRB \ + --scope=SCOPE --role=admin --user=person@google.com \ + --custom-role=custom-role + POSITIONAL ARGUMENTS Rbacrolebinding resource - The group of arguments defining an RBACRoleBinding. The arguments in this group can be used to specify the @@ -68,9 +75,14 @@ POSITIONAL ARGUMENTS ▸ provide the argument --scope on the command line. REQUIRED FLAGS - --role=ROLE - Predefined role to assign to principal (admin, edit, view). ROLE must - be one of: admin, edit, view. + Exactly one of these must be specified: + + --custom-role=CUSTOM_ROLE + Custom role to assign to principal. + + --role=ROLE + Predefined role to assign to principal (admin, edit, view). ROLE must + be one of: admin, edit, view. Exactly one of these must be specified: diff --git a/gcloud/beta/container/fleet/scopes/rbacrolebindings/update b/gcloud/beta/container/fleet/scopes/rbacrolebindings/update index 077abbfb8..504d18992 100644 --- a/gcloud/beta/container/fleet/scopes/rbacrolebindings/update +++ b/gcloud/beta/container/fleet/scopes/rbacrolebindings/update @@ -4,10 +4,11 @@ NAME SYNOPSIS gcloud beta container fleet scopes rbacrolebindings update - (NAME : --location=LOCATION --scope=SCOPE) [--role=ROLE] + (NAME : --location=LOCATION --scope=SCOPE) [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] - [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...] + [--custom-role=CUSTOM_ROLE | --role=ROLE] [--group=GROUP | --user=USER] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -21,6 +22,12 @@ EXAMPLES $ gcloud beta container fleet scopes rbacrolebindings update RBRB \ --scope=SCOPE --role=viewer + To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to + the custom role custom-role: + + $ gcloud beta container fleet scopes rbacrolebindings update RBRB \ + --scope=SCOPE --custom-role=custom-role + To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to the user someone@google.com: @@ -69,10 +76,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --scope on the command line. FLAGS - --role=ROLE - Predefined role to assign to principal (admin, edit, view). ROLE must - be one of: admin, edit, view. - --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. @@ -103,6 +106,15 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + At most one of these can be specified: + + --custom-role=CUSTOM_ROLE + Custom role to assign to principal. + + --role=ROLE + Predefined role to assign to principal (admin, edit, view). ROLE must + be one of: admin, edit, view. + At most one of these can be specified: --group=GROUP diff --git a/gcloud/beta/container/hub/help b/gcloud/beta/container/hub/help index e44de14a5..7819c029e 100644 --- a/gcloud/beta/container/hub/help +++ b/gcloud/beta/container/hub/help @@ -82,9 +82,15 @@ GROUPS operations (BETA) Manage Anthos fleet long-running operations. + packages + (BETA) Manage Fleet Packages resources. + policycontroller (BETA) Manage Policy Controller Feature. + rbacrolebindingactuation + (BETA) Manage RbacRoleBinding Actuation. + scopes (BETA) Manage scopes of all your GKE fleets. diff --git a/gcloud/beta/container/hub/packages/create b/gcloud/beta/container/hub/packages/create new file mode 100644 index 000000000..44574c0e5 --- /dev/null +++ b/gcloud/beta/container/hub/packages/create @@ -0,0 +1,43 @@ +NAME + gcloud beta container hub packages create - create Package Rollouts Fleet + Package + +SYNOPSIS + gcloud beta container hub packages create NAME --source=SOURCE + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create Package Rollouts Fleet Package. + +EXAMPLES + To create Fleet Package cert-manager-app, run: + + $ gcloud beta container hub packages create cert-manager-app \ + --source=source.yaml + +POSITIONAL ARGUMENTS + NAME + Resource name. + +REQUIRED FLAGS + --source=SOURCE + Source file containing Fleet Package configuration. + +OPTIONAL FLAGS + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages create + diff --git a/gcloud/beta/container/hub/packages/delete b/gcloud/beta/container/hub/packages/delete new file mode 100644 index 000000000..df4c6fb24 --- /dev/null +++ b/gcloud/beta/container/hub/packages/delete @@ -0,0 +1,68 @@ +NAME + gcloud beta container hub packages delete - delete Package Rollouts Fleet + Package + +SYNOPSIS + gcloud beta container hub packages delete + (FLEET_PACKAGE : --location=LOCATION) [--force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete Package Rollouts Fleet Package. + +EXAMPLES + To delete Fleet Package cert-manager-app in us-central1, run: + + $ gcloud beta container hub packages delete cert-manager-app \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Fleet package resource - The Fleet Package to create. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument fleet_package on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + FLEET_PACKAGE + ID of the fleet-package or fully qualified identifier for the + fleet-package. + + To set the fleet-package attribute: + ▸ provide the argument fleet_package on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud zone or region for the fleet-package. + + To set the location attribute: + ▸ provide the argument fleet_package on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property config_delivery/location. + +FLAGS + --force + If true, force deletion of any child resources. Otherwise, attempting + to delete a Fleet Package with children will fail. + +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 hub packages delete + diff --git a/gcloud/beta/container/hub/packages/describe b/gcloud/beta/container/hub/packages/describe new file mode 100644 index 000000000..e0e16718b --- /dev/null +++ b/gcloud/beta/container/hub/packages/describe @@ -0,0 +1,68 @@ +NAME + gcloud beta container hub packages describe - describe Package Rollouts + Fleet Package + +SYNOPSIS + gcloud beta container hub packages describe + (FLEET_PACKAGE : --location=LOCATION) [--show-cluster-status] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe Package Rollouts Fleet Package. + +EXAMPLES + To view Fleet Package cert-manager-app in us-central1, run: + + $ gcloud beta container hub packages describe cert-manager-app \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Fleet package resource - The Fleet Package 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 fleet_package on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + FLEET_PACKAGE + ID of the fleet-package or fully qualified identifier for the + fleet-package. + + To set the fleet-package attribute: + ▸ provide the argument fleet_package on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud zone or region for the fleet-package. + + To set the location attribute: + ▸ provide the argument fleet_package on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property config_delivery/location. + +FLAGS + --show-cluster-status + Show more information about the Fleet Package. + +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 hub packages describe + diff --git a/gcloud/beta/container/hub/packages/help b/gcloud/beta/container/hub/packages/help new file mode 100644 index 000000000..7aed3f994 --- /dev/null +++ b/gcloud/beta/container/hub/packages/help @@ -0,0 +1,47 @@ +NAME + gcloud beta container hub packages - manage Fleet Packages resources + +SYNOPSIS + gcloud beta container hub packages GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Fleet Packages resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + resource-bundles + (BETA) Commands for managing Package Rollouts Resource Bundles. + + rollouts + (BETA) Commands for managing Rollouts. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create Package Rollouts Fleet Package. + + delete + (BETA) Delete Package Rollouts Fleet Package. + + describe + (BETA) Describe Package Rollouts Fleet Package. + + list + (BETA) List Package Rollouts Fleet Packages. + + update + (BETA) Update Package Rollouts Fleet Package. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages + diff --git a/gcloud/beta/container/hub/packages/list b/gcloud/beta/container/hub/packages/list new file mode 100644 index 000000000..79a83f766 --- /dev/null +++ b/gcloud/beta/container/hub/packages/list @@ -0,0 +1,67 @@ +NAME + gcloud beta container hub packages list - list Package Rollouts Fleet + Packages + +SYNOPSIS + gcloud beta container hub packages list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Package Rollouts Fleet Packages. + +EXAMPLES + To list all Fleet Packages in us-central1, run: + + $ gcloud beta container hub packages list --location=us-central1 + +FLAGS + --location=LOCATION + Google Cloud zone or region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages list + diff --git a/gcloud/beta/container/hub/packages/resource-bundles/create b/gcloud/beta/container/hub/packages/resource-bundles/create new file mode 100644 index 000000000..c1f8f548e --- /dev/null +++ b/gcloud/beta/container/hub/packages/resource-bundles/create @@ -0,0 +1,43 @@ +NAME + gcloud beta container hub packages resource-bundles create - create Package + Rollouts Resource Bundle + +SYNOPSIS + gcloud beta container hub packages resource-bundles create NAME + [--description=DESCRIPTION] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create Package Rollouts Resource Bundle. + +EXAMPLES + To create Resource Bundle cert-manager in us-central1, run: + + $ gcloud beta container hub packages resource-bundles create \ + cert-manager --location=us-central1 + +POSITIONAL ARGUMENTS + NAME + Resource name. + +FLAGS + --description=DESCRIPTION + Resource description. + + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages resource-bundles create + diff --git a/gcloud/beta/container/hub/packages/resource-bundles/delete b/gcloud/beta/container/hub/packages/resource-bundles/delete new file mode 100644 index 000000000..101fa7579 --- /dev/null +++ b/gcloud/beta/container/hub/packages/resource-bundles/delete @@ -0,0 +1,43 @@ +NAME + gcloud beta container hub packages resource-bundles delete - delete Package + Rollouts Resource Bundle + +SYNOPSIS + gcloud beta container hub packages resource-bundles delete NAME [--force] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete Package Rollouts Resource Bundle. + +EXAMPLES + To delete Resource Bundle cert-manager in us-central1, run: + + $ gcloud beta container hub packages resource-bundles delete \ + cert-manager --location=us-central1 + +POSITIONAL ARGUMENTS + NAME + Resource name. + +FLAGS + --force + If true, force deletion of any child resources. Otherwise, attempting + to delete a Resource Bundle with children will fail. + + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages resource-bundles delete + diff --git a/gcloud/beta/container/hub/packages/resource-bundles/describe b/gcloud/beta/container/hub/packages/resource-bundles/describe new file mode 100644 index 000000000..9bab268c7 --- /dev/null +++ b/gcloud/beta/container/hub/packages/resource-bundles/describe @@ -0,0 +1,39 @@ +NAME + gcloud beta container hub packages resource-bundles describe - describe + Package Rollouts Resource Bundle + +SYNOPSIS + gcloud beta container hub packages resource-bundles describe NAME + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe Package Rollouts Resource Bundle. + +EXAMPLES + To describe Resource Bundle cert-manager in us-central1, run: + + $ gcloud beta container hub packages resource-bundles describe \ + cert-manager --location=us-central1 + +POSITIONAL ARGUMENTS + NAME + Resource name. + +FLAGS + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages resource-bundles describe + diff --git a/gcloud/beta/container/hub/packages/resource-bundles/help b/gcloud/beta/container/hub/packages/resource-bundles/help new file mode 100644 index 000000000..060d18d62 --- /dev/null +++ b/gcloud/beta/container/hub/packages/resource-bundles/help @@ -0,0 +1,47 @@ +NAME + gcloud beta container hub packages resource-bundles - commands for managing + Package Rollouts Resource Bundles + +SYNOPSIS + gcloud beta container hub packages resource-bundles GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) See gcloud beta container fleet packages resource-bundles --help for + help. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + releases + (BETA) Commands for managing Package Rollouts Releases. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create Package Rollouts Resource Bundle. + + delete + (BETA) Delete Package Rollouts Resource Bundle. + + describe + (BETA) Describe Package Rollouts Resource Bundle. + + list + (BETA) List Package Rollouts Resource Bundles. + + update + (BETA) Update Package Rollouts Resource Bundle. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages resource-bundles + diff --git a/gcloud/beta/container/hub/packages/resource-bundles/list b/gcloud/beta/container/hub/packages/resource-bundles/list new file mode 100644 index 000000000..a4e76df99 --- /dev/null +++ b/gcloud/beta/container/hub/packages/resource-bundles/list @@ -0,0 +1,69 @@ +NAME + gcloud beta container hub packages resource-bundles list - list Package + Rollouts Resource Bundles + +SYNOPSIS + gcloud beta container hub packages resource-bundles list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Package Rollouts Resource Bundles. + +EXAMPLES + To list Resource Bundles in us-central1, run: + + $ gcloud beta container hub packages resource-bundles list \ + --location=us-central1 + +FLAGS + --location=LOCATION + Google Cloud zone or region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages resource-bundles list + diff --git a/gcloud/beta/container/hub/packages/resource-bundles/releases/create b/gcloud/beta/container/hub/packages/resource-bundles/releases/create new file mode 100644 index 000000000..ca571df84 --- /dev/null +++ b/gcloud/beta/container/hub/packages/resource-bundles/releases/create @@ -0,0 +1,73 @@ +NAME + gcloud beta container hub packages resource-bundles releases create - + create Package Rollouts Release + +SYNOPSIS + gcloud beta container hub packages resource-bundles releases create + --resource-bundle=RESOURCE_BUNDLE --source=SOURCE --version=VERSION + [--lifecycle=LIFECYCLE] [--location=LOCATION] + [--variants-pattern=VARIANTS_PATTERN] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create Package Rollouts Release. + +EXAMPLES + To create Release v1.0.0 for Resource Bundle my-bundle in us-central1, run: + + $ gcloud beta container hub packages resource-bundles releases \ + create --version=v1.0.0 --resource-bundle=my-bundle \ + --source=manifest.yaml + + To create a Release with multiple variants in one directory, run: + + $ gcloud beta container hub packages resource-bundles releases \ + create --version=v1.0.0 --resource-bundle=my-bundle \ + --source=/manifests/ --variants-pattern=manifest-*.yaml + + To create a Release with multiple variants across multiple directories, ex: + + $ gcloud beta container hub packages resource-bundles releases \ + create --version=v1.0.0 --resource-bundle=my-bundle \ + --source=/manifests/ --variants-pattern=dir-*/ + +REQUIRED FLAGS + --resource-bundle=RESOURCE_BUNDLE + Resource Bundle name. + + --source=SOURCE + Source file or directory to create the Release from. e.g. + --source=manifest.yaml, --source=/manifests-dir/ Can optionally be + paired with the --variants-pattern arg to create multiple variants of a + Release. + + --version=VERSION + Version of the Release to create. + +OPTIONAL FLAGS + --lifecycle=LIFECYCLE + Lifecycle of the Release. + + --location=LOCATION + Google Cloud zone or region. + + --variants-pattern=VARIANTS_PATTERN + Glob pattern to Variants of the Release, to be paired with the --source + arg. ex: --source=/manifests-dir/ --variants-pattern=**, + --source=/manifests-dir/ --variants-pattern=us-*.yaml, + --source=/manifests/dir/ --variants-pattern=*/*.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. This + variant is also available: + + $ gcloud alpha container hub packages resource-bundles releases \ + create + diff --git a/gcloud/beta/container/hub/packages/resource-bundles/releases/delete b/gcloud/beta/container/hub/packages/resource-bundles/releases/delete new file mode 100644 index 000000000..1522210de --- /dev/null +++ b/gcloud/beta/container/hub/packages/resource-bundles/releases/delete @@ -0,0 +1,50 @@ +NAME + gcloud beta container hub packages resource-bundles releases delete - + delete Package Rollouts Release + +SYNOPSIS + gcloud beta container hub packages resource-bundles releases delete RELEASE + --resource-bundle=RESOURCE_BUNDLE [--force] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete Package Rollouts Release. + +EXAMPLES + To delete Release v1.0.0 of cert-manager in us-central1, run: + + $ gcloud beta container hub packages resource-bundles releases \ + delete v1.0.0 --location=us-central1 \ + --resource-bundle=cert-manager + +POSITIONAL ARGUMENTS + RELEASE + Release identifier, either a version or tag. + +REQUIRED FLAGS + --resource-bundle=RESOURCE_BUNDLE + Resource Bundle name. + +OPTIONAL FLAGS + --force + If true, force deletion of any child resources. Otherwise, attempting + to delete a Release with children will fail. + + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages resource-bundles releases \ + delete + diff --git a/gcloud/beta/container/hub/packages/resource-bundles/releases/describe b/gcloud/beta/container/hub/packages/resource-bundles/releases/describe new file mode 100644 index 000000000..30746f97d --- /dev/null +++ b/gcloud/beta/container/hub/packages/resource-bundles/releases/describe @@ -0,0 +1,46 @@ +NAME + gcloud beta container hub packages resource-bundles releases describe - + describe Package Rollouts Release + +SYNOPSIS + gcloud beta container hub packages resource-bundles releases describe + RELEASE --resource-bundle=RESOURCE_BUNDLE [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe Package Rollouts Release. + +EXAMPLES + To view release v1.0.0 of cert-manager in us-central1, run: + + $ gcloud beta container hub packages resource-bundles releases \ + describe v1.0.0 --location=us-central1 \ + --resource-bundle=cert-manager + +POSITIONAL ARGUMENTS + RELEASE + Release identifier, either a version or tag. + +REQUIRED FLAGS + --resource-bundle=RESOURCE_BUNDLE + Resource Bundle name. + +OPTIONAL FLAGS + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages resource-bundles releases \ + describe + diff --git a/gcloud/beta/container/hub/packages/resource-bundles/releases/help b/gcloud/beta/container/hub/packages/resource-bundles/releases/help new file mode 100644 index 000000000..b570aa6ea --- /dev/null +++ b/gcloud/beta/container/hub/packages/resource-bundles/releases/help @@ -0,0 +1,41 @@ +NAME + gcloud beta container hub packages resource-bundles releases - commands for + managing Package Rollouts Releases + +SYNOPSIS + gcloud beta container hub packages resource-bundles releases COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) See gcloud beta container fleet packages resource-bundles releases + --help for help. + +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 Package Rollouts Release. + + delete + (BETA) Delete Package Rollouts Release. + + describe + (BETA) Describe Package Rollouts Release. + + list + (BETA) List Releases of a Resource Bundle. + + update + (BETA) Update Package Rollouts Release. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages resource-bundles releases + diff --git a/gcloud/beta/container/hub/packages/resource-bundles/releases/list b/gcloud/beta/container/hub/packages/resource-bundles/releases/list new file mode 100644 index 000000000..80164d494 --- /dev/null +++ b/gcloud/beta/container/hub/packages/resource-bundles/releases/list @@ -0,0 +1,73 @@ +NAME + gcloud beta container hub packages resource-bundles releases list - list + Releases of a Resource Bundle + +SYNOPSIS + gcloud beta container hub packages resource-bundles releases list + --resource-bundle=RESOURCE_BUNDLE [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Releases of a Resource Bundle. + +EXAMPLES + To list all Releases for bundle cert-manager in us-central1, run: + + $ gcloud beta container hub packages resource-bundles releases \ + list --resource-bundle=cert-manager --location=us-central1 + +REQUIRED FLAGS + --resource-bundle=RESOURCE_BUNDLE + Resource Bundle name. + +FLAGS + --location=LOCATION + Google Cloud zone or region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages resource-bundles releases list + diff --git a/gcloud/beta/container/hub/packages/resource-bundles/releases/update b/gcloud/beta/container/hub/packages/resource-bundles/releases/update new file mode 100644 index 000000000..a617642af --- /dev/null +++ b/gcloud/beta/container/hub/packages/resource-bundles/releases/update @@ -0,0 +1,49 @@ +NAME + gcloud beta container hub packages resource-bundles releases update - + update Package Rollouts Release + +SYNOPSIS + gcloud beta container hub packages resource-bundles releases update RELEASE + --resource-bundle=RESOURCE_BUNDLE [--lifecycle=LIFECYCLE] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update Package Rollouts Release. + +EXAMPLES + To update Release v1.0.0 for Resource Bundle my-bundle in us-central1, run: + + $ gcloud beta container hub packages resource-bundles releases \ + update --version=v1.0.0 --resource-bundle=my-bundle \ + --lifecycle=PUBLISHED + +POSITIONAL ARGUMENTS + RELEASE + Release identifier, either a version or tag. + +REQUIRED FLAGS + --resource-bundle=RESOURCE_BUNDLE + Resource Bundle name. + +OPTIONAL FLAGS + --lifecycle=LIFECYCLE + Lifecycle of the Release. + + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages resource-bundles releases \ + update + diff --git a/gcloud/beta/container/hub/packages/resource-bundles/update b/gcloud/beta/container/hub/packages/resource-bundles/update new file mode 100644 index 000000000..e9aed9c43 --- /dev/null +++ b/gcloud/beta/container/hub/packages/resource-bundles/update @@ -0,0 +1,43 @@ +NAME + gcloud beta container hub packages resource-bundles update - update Package + Rollouts Resource Bundle + +SYNOPSIS + gcloud beta container hub packages resource-bundles update NAME + [--description=DESCRIPTION] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update Package Rollouts Resource Bundle. + +EXAMPLES + To update Resource Bundle cert-manager in us-central1, run: + + $ gcloud beta container hub packages resource-bundles update \ + cert-manager --location=us-central1 ... + +POSITIONAL ARGUMENTS + NAME + Resource name. + +FLAGS + --description=DESCRIPTION + Resource description. + + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages resource-bundles update + diff --git a/gcloud/beta/container/hub/packages/rollouts/abort b/gcloud/beta/container/hub/packages/rollouts/abort new file mode 100644 index 000000000..39cd9926e --- /dev/null +++ b/gcloud/beta/container/hub/packages/rollouts/abort @@ -0,0 +1,73 @@ +NAME + gcloud beta container hub packages rollouts abort - abort Rollout resource + +SYNOPSIS + gcloud beta container hub packages rollouts abort + (ROLLOUT : --fleet-package=FLEET_PACKAGE --location=LOCATION) + [--reason=REASON] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Abort Rollout resource. + +EXAMPLES + To abort Rollout 20240318 for cert-manager-app in us-central1, run: + + $ gcloud beta container hub packages rollouts abort 20240318 \ + --fleet-package=cert-manager-app --location=us-central1 + +POSITIONAL ARGUMENTS + Rollout resource - The rollout to abort. 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 rollout on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + ROLLOUT + ID of the rollout or fully qualified identifier for the rollout. + + To set the rollout attribute: + ▸ provide the argument rollout on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --fleet-package=FLEET_PACKAGE + Fleet Package name. + + To set the fleet-package attribute: + ▸ provide the argument rollout on the command line with a fully + specified name; + ▸ provide the argument --fleet-package on the command line. + + --location=LOCATION + Google Cloud zone or region for the rollout. + + To set the location attribute: + ▸ provide the argument rollout on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property config_delivery/location. + +FLAGS + --reason=REASON + Reason for aborting rollout. + +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 hub packages rollouts abort + diff --git a/gcloud/beta/container/hub/packages/rollouts/describe b/gcloud/beta/container/hub/packages/rollouts/describe new file mode 100644 index 000000000..b8726af2c --- /dev/null +++ b/gcloud/beta/container/hub/packages/rollouts/describe @@ -0,0 +1,47 @@ +NAME + gcloud beta container hub packages rollouts describe - describe Rollout + resource + +SYNOPSIS + gcloud beta container hub packages rollouts describe NAME + --fleet-package=FLEET_PACKAGE [--less] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe Rollout resource. + +EXAMPLES + To view Rollout 20240318 for cert-manager-app in us-central1, run: + + $ gcloud beta container hub packages rollouts describe 20240318 \ + --fleet-package=cert-manager-app --location=us-central1 + +POSITIONAL ARGUMENTS + NAME + Resource name. + +REQUIRED FLAGS + --fleet-package=FLEET_PACKAGE + Parent Fleet Package of the Rollout. + +OPTIONAL FLAGS + --less + Show less verbose output. + + --location=LOCATION + Google Cloud zone or region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages rollouts describe + diff --git a/gcloud/beta/container/hub/packages/rollouts/help b/gcloud/beta/container/hub/packages/rollouts/help new file mode 100644 index 000000000..276d51f63 --- /dev/null +++ b/gcloud/beta/container/hub/packages/rollouts/help @@ -0,0 +1,39 @@ +NAME + gcloud beta container hub packages rollouts - commands for managing + Rollouts + +SYNOPSIS + gcloud beta container hub packages rollouts COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) See gcloud beta container fleet packages rollouts --help for help. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + abort + (BETA) Abort Rollout resource. + + describe + (BETA) Describe Rollout resource. + + list + (BETA) List Rollouts of a Fleet Package. + + resume + (BETA) Resume suspended Rollout. + + suspend + (BETA) Suspend in-progress Rollout. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages rollouts + diff --git a/gcloud/beta/container/hub/packages/rollouts/list b/gcloud/beta/container/hub/packages/rollouts/list new file mode 100644 index 000000000..79d6d5f64 --- /dev/null +++ b/gcloud/beta/container/hub/packages/rollouts/list @@ -0,0 +1,77 @@ +NAME + gcloud beta container hub packages rollouts list - list Rollouts of a Fleet + Package + +SYNOPSIS + gcloud beta container hub packages rollouts list + --fleet-package=FLEET_PACKAGE [--less] [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Rollouts of a Fleet Package. + +EXAMPLES + To list all Rollouts for Fleet Package cert-manager-app in us-central1, + run: + + $ gcloud beta container hub packages rollouts list \ + --fleet-package=cert-manager-app --location=us-central1 + +REQUIRED FLAGS + --fleet-package=FLEET_PACKAGE + Parent Fleet Package of the Rollout. + +FLAGS + --less + Show less verbose output. + + --location=LOCATION + Google Cloud zone or region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub packages rollouts list + diff --git a/gcloud/beta/container/hub/packages/rollouts/resume b/gcloud/beta/container/hub/packages/rollouts/resume new file mode 100644 index 000000000..82e0358dc --- /dev/null +++ b/gcloud/beta/container/hub/packages/rollouts/resume @@ -0,0 +1,74 @@ +NAME + gcloud beta container hub packages rollouts resume - resume suspended + Rollout + +SYNOPSIS + gcloud beta container hub packages rollouts resume + (ROLLOUT : --fleet-package=FLEET_PACKAGE --location=LOCATION) + [--reason=REASON] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Resume suspended Rollout. + +EXAMPLES + To resume Rollout 20240318 for cert-manager-app in us-central1, run: + + $ gcloud beta container hub packages rollouts resume 20240318 \ + --fleet-package=cert-manager-app --location=us-central1 + +POSITIONAL ARGUMENTS + Rollout resource - The rollout 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 rollout on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + ROLLOUT + ID of the rollout or fully qualified identifier for the rollout. + + To set the rollout attribute: + ▸ provide the argument rollout on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --fleet-package=FLEET_PACKAGE + Fleet Package name. + + To set the fleet-package attribute: + ▸ provide the argument rollout on the command line with a fully + specified name; + ▸ provide the argument --fleet-package on the command line. + + --location=LOCATION + Google Cloud zone or region for the rollout. + + To set the location attribute: + ▸ provide the argument rollout on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property config_delivery/location. + +FLAGS + --reason=REASON + Reason for resuming rollout. + +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 hub packages rollouts resume + diff --git a/gcloud/beta/container/hub/packages/rollouts/suspend b/gcloud/beta/container/hub/packages/rollouts/suspend new file mode 100644 index 000000000..06027a8ab --- /dev/null +++ b/gcloud/beta/container/hub/packages/rollouts/suspend @@ -0,0 +1,74 @@ +NAME + gcloud beta container hub packages rollouts suspend - suspend in-progress + Rollout + +SYNOPSIS + gcloud beta container hub packages rollouts suspend + (ROLLOUT : --fleet-package=FLEET_PACKAGE --location=LOCATION) + [--reason=REASON] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Suspend in-progress Rollout. + +EXAMPLES + To suspend Rollout 20240318 for cert-manager-app in us-central1, run: + + $ gcloud beta container hub packages rollouts suspend 20240318 \ + --fleet-package=cert-manager-app --location=us-central1 + +POSITIONAL ARGUMENTS + Rollout resource - The rollout to suspend. 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 rollout on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + ROLLOUT + ID of the rollout or fully qualified identifier for the rollout. + + To set the rollout attribute: + ▸ provide the argument rollout on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --fleet-package=FLEET_PACKAGE + Fleet Package name. + + To set the fleet-package attribute: + ▸ provide the argument rollout on the command line with a fully + specified name; + ▸ provide the argument --fleet-package on the command line. + + --location=LOCATION + Google Cloud zone or region for the rollout. + + To set the location attribute: + ▸ provide the argument rollout on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property config_delivery/location. + +FLAGS + --reason=REASON + Reason for suspending rollout. + +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 hub packages rollouts suspend + diff --git a/gcloud/beta/container/hub/packages/update b/gcloud/beta/container/hub/packages/update new file mode 100644 index 000000000..d1b93ce2a --- /dev/null +++ b/gcloud/beta/container/hub/packages/update @@ -0,0 +1,68 @@ +NAME + gcloud beta container hub packages update - update Package Rollouts Fleet + Package + +SYNOPSIS + gcloud beta container hub packages update + (FLEET_PACKAGE : --location=LOCATION) --source=SOURCE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update Package Rollouts Fleet Package. + +EXAMPLES + To update Fleet Package cert-manager-app, run: + + $ gcloud beta container hub packages update cert-manager-app \ + --source=my_source.yaml + +POSITIONAL ARGUMENTS + Fleet package resource - The Fleet Package to create. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument fleet_package on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + FLEET_PACKAGE + ID of the fleet-package or fully qualified identifier for the + fleet-package. + + To set the fleet-package attribute: + ▸ provide the argument fleet_package on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud zone or region for the fleet-package. + + To set the location attribute: + ▸ provide the argument fleet_package on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property config_delivery/location. + +REQUIRED FLAGS + --source=SOURCE + Source file containing Fleet Package configuration. + +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 hub packages update + diff --git a/gcloud/beta/container/hub/rbacrolebindingactuation/describe b/gcloud/beta/container/hub/rbacrolebindingactuation/describe new file mode 100644 index 000000000..0b03285c7 --- /dev/null +++ b/gcloud/beta/container/hub/rbacrolebindingactuation/describe @@ -0,0 +1,24 @@ +NAME + gcloud beta container hub rbacrolebindingactuation describe - describe the + status of the RbacRoleBinding Actuation Feature in a fleet + +SYNOPSIS + gcloud beta container hub rbacrolebindingactuation describe + [GCLOUD_WIDE_FLAG ...] + +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 container hub rbacrolebindingactuation describe + + $ gcloud alpha container hub rbacrolebindingactuation describe + diff --git a/gcloud/beta/container/hub/rbacrolebindingactuation/help b/gcloud/beta/container/hub/rbacrolebindingactuation/help new file mode 100644 index 000000000..332e90e6b --- /dev/null +++ b/gcloud/beta/container/hub/rbacrolebindingactuation/help @@ -0,0 +1,34 @@ +NAME + gcloud beta container hub rbacrolebindingactuation - manage RbacRoleBinding + Actuation + +SYNOPSIS + gcloud beta container hub rbacrolebindingactuation COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage RbacRoleBinding Actuation. + +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) Describe the status of the RbacRoleBinding Actuation Feature in + a fleet. + + update + (BETA) Update RbacRoleBinding Actuation Feature. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub rbacrolebindingactuation + + $ gcloud alpha container hub rbacrolebindingactuation + diff --git a/gcloud/beta/container/hub/rbacrolebindingactuation/update b/gcloud/beta/container/hub/rbacrolebindingactuation/update new file mode 100644 index 000000000..ae7957b7a --- /dev/null +++ b/gcloud/beta/container/hub/rbacrolebindingactuation/update @@ -0,0 +1,55 @@ +NAME + gcloud beta container hub rbacrolebindingactuation update - update + RbacRoleBinding Actuation Feature + +SYNOPSIS + gcloud beta container hub rbacrolebindingactuation update + (--add-allowed-custom-role=ADD_ALLOWED_CUSTOM_ROLE + | --allowed-custom-roles=[ROLES,...] + | --remove-allowed-custom-role=REMOVE_ALLOWED_CUSTOM_ROLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command updates RbacRoleBinding Actuation Feature in a fleet. + +EXAMPLES + To update the RbacRoleBinding Actuation Feature, run: + + $ gcloud container fleet rbacrolebinding-actuation update \ + --allowed-custom-roles=role1,role2 + + $ gcloud container fleet rbacrolebinding-actuation update \ + --add-allowed-custom-role=role1 + + $ gcloud container fleet rbacrolebinding-actuation update \ + --remove-allowed-custom-role=role2 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --add-allowed-custom-role=ADD_ALLOWED_CUSTOM_ROLE + Add a single custom role to the allowed custom roles list. + + --allowed-custom-roles=[ROLES,...] + The list of allowed custom roles that can be used in scope + RBACRoleBindings. + + --remove-allowed-custom-role=REMOVE_ALLOWED_CUSTOM_ROLE + Remove a single custom role from the allowed custom roles list. + +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 container hub rbacrolebindingactuation update + + $ gcloud alpha container hub rbacrolebindingactuation update + diff --git a/gcloud/beta/container/hub/scopes/rbacrolebindings/create b/gcloud/beta/container/hub/scopes/rbacrolebindings/create index 00889f8f1..d255caf91 100644 --- a/gcloud/beta/container/hub/scopes/rbacrolebindings/create +++ b/gcloud/beta/container/hub/scopes/rbacrolebindings/create @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud beta container hub scopes rbacrolebindings create - (NAME : --location=LOCATION --scope=SCOPE) --role=ROLE - (--group=GROUP | --user=USER) [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + (NAME : --location=LOCATION --scope=SCOPE) + (--custom-role=CUSTOM_ROLE | --role=ROLE) (--group=GROUP | --user=USER) + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -26,6 +26,13 @@ EXAMPLES $ gcloud beta container hub scopes rbacrolebindings create RBRB \ --scope=SCOPE --role=viewer --group=people@google.com + To create an RBAC RoleBinding with a custom role custom-role in scope SCOPE + for user person@google.com, run: + + $ gcloud beta container hub scopes rbacrolebindings create RBRB \ + --scope=SCOPE --role=admin --user=person@google.com \ + --custom-role=custom-role + POSITIONAL ARGUMENTS Rbacrolebinding resource - The group of arguments defining an RBACRoleBinding. The arguments in this group can be used to specify the @@ -68,9 +75,14 @@ POSITIONAL ARGUMENTS ▸ provide the argument --scope on the command line. REQUIRED FLAGS - --role=ROLE - Predefined role to assign to principal (admin, edit, view). ROLE must - be one of: admin, edit, view. + Exactly one of these must be specified: + + --custom-role=CUSTOM_ROLE + Custom role to assign to principal. + + --role=ROLE + Predefined role to assign to principal (admin, edit, view). ROLE must + be one of: admin, edit, view. Exactly one of these must be specified: diff --git a/gcloud/beta/container/hub/scopes/rbacrolebindings/update b/gcloud/beta/container/hub/scopes/rbacrolebindings/update index 85b13e038..fc1863b5f 100644 --- a/gcloud/beta/container/hub/scopes/rbacrolebindings/update +++ b/gcloud/beta/container/hub/scopes/rbacrolebindings/update @@ -4,10 +4,11 @@ NAME SYNOPSIS gcloud beta container hub scopes rbacrolebindings update - (NAME : --location=LOCATION --scope=SCOPE) [--role=ROLE] + (NAME : --location=LOCATION --scope=SCOPE) [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] - [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...] + [--custom-role=CUSTOM_ROLE | --role=ROLE] [--group=GROUP | --user=USER] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -21,6 +22,12 @@ EXAMPLES $ gcloud beta container hub scopes rbacrolebindings update RBRB \ --scope=SCOPE --role=viewer + To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to + the custom role custom-role: + + $ gcloud beta container hub scopes rbacrolebindings update RBRB \ + --scope=SCOPE --custom-role=custom-role + To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to the user someone@google.com: @@ -69,10 +76,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --scope on the command line. FLAGS - --role=ROLE - Predefined role to assign to principal (admin, edit, view). ROLE must - be one of: admin, edit, view. - --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. @@ -103,6 +106,15 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + At most one of these can be specified: + + --custom-role=CUSTOM_ROLE + Custom role to assign to principal. + + --role=ROLE + Predefined role to assign to principal (admin, edit, view). ROLE must + be one of: admin, edit, view. + At most one of these can be specified: --group=GROUP diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 2570a79a5..3c1820911 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -45,6 +45,7 @@ SYNOPSIS [--num-nodes=NUM_NODES] [--opportunistic-maintenance=[node-idle-time=NODE_IDLE_TIME, window=WINDOW,min-nodes=MIN_NODES,...]] + [--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT] [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] [--preemptible] [--resource-manager-tags=[KEY=VALUE,...]] [--sandbox=[type=TYPE]] @@ -591,6 +592,19 @@ FLAGS --opportunistic-maintenance=node-idle-time=600s,window=600s,\ min-nodes=2 + --performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT + Sets the Performance Monitoring Unit level. Valid values are + architectural, standard and enhanced. PERFORMANCE_MONITORING_UNIT must + be one of: + + architectural + Enables architectural PMU events tied to non last level cache (LLC) + events. + enhanced + Enables most documented core/L2 and LLC PMU events. + standard + Enables most documented core/L2 PMU events. + --placement-policy=PLACEMENT_POLICY Indicates the desired resource policy to use. diff --git a/gcloud/beta/dataproc/clusters/create b/gcloud/beta/dataproc/clusters/create index b161ecaad..b6147fd7b 100644 --- a/gcloud/beta/dataproc/clusters/create +++ b/gcloud/beta/dataproc/clusters/create @@ -43,8 +43,7 @@ SYNOPSIS [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--secondary-worker-standard-capacity-percent-above-base=SECONDARY_WORKER_STANDARD_CAPACITY_PERCENT_ABOVE_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--stop-max-idle=STOP_MAX_IDLE] - [--temp-bucket=TEMP_BUCKET] + [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--tier=TIER] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -78,8 +77,6 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] - [--stop-expiration-time=STOP_EXPIRATION_TIME - | --stop-max-age=STOP_MAX_AGE] [--worker-machine-type=WORKER_MACHINE_TYPE | --worker-machine-types=type=MACHINE_TYPE[, type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] @@ -421,15 +418,13 @@ FLAGS security operations, such as remote attestation, encryption, and sealing of keys. - --stop-max-idle=STOP_MAX_IDLE - The duration after the last job completes to auto-stop the cluster, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - --temp-bucket=TEMP_BUCKET The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. + --tier=TIER + Cluster tier. TIER must be one of: premium, standard. + --worker-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the worker instance(s). @@ -950,18 +945,6 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. - At most one of these can be specified: - - --stop-expiration-time=STOP_EXPIRATION_TIME - The time when the cluster will be auto-stopped, such as - "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for - information on time formats. - - --stop-max-age=STOP_MAX_AGE - The lifespan of the cluster, with auto-stop upon completion, such as - "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - At most one of these can be specified: --worker-machine-type=WORKER_MACHINE_TYPE diff --git a/gcloud/beta/dataproc/clusters/update b/gcloud/beta/dataproc/clusters/update index e7d4b5048..5e032cc9e 100644 --- a/gcloud/beta/dataproc/clusters/update +++ b/gcloud/beta/dataproc/clusters/update @@ -15,11 +15,7 @@ SYNOPSIS | --expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE | --no-max-age] [--delete-max-idle=DELETE_MAX_IDLE | --no-delete-max-idle - | --max-idle=MAX_IDLE | --no-max-idle] - [--stop-expiration-time=STOP_EXPIRATION_TIME - | --stop-max-age=STOP_MAX_AGE | --no-stop-max-age] - [--stop-max-idle=STOP_MAX_IDLE | --no-stop-max-idle] - [GCLOUD_WIDE_FLAG ...] + | --max-idle=MAX_IDLE | --no-max-idle] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update the number of worker nodes and/or the labels in a cluster. @@ -220,33 +216,6 @@ FLAGS Cancels the cluster auto-deletion by cluster idle duration (configured by --max-idle flag) - At most one of these can be specified: - - --stop-expiration-time=STOP_EXPIRATION_TIME - The time when the cluster will be auto-stopped, such as - "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for - information on time formats. - - --stop-max-age=STOP_MAX_AGE - The lifespan of the cluster, with auto-stop upon completion, such as - "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - - --no-stop-max-age - Cancels the cluster auto-stop by maximum cluster age (configured by - --stop-max-age or --stop-expiration-time flags) - - At most one of these can be specified: - - --stop-max-idle=STOP_MAX_IDLE - The duration after the last job completes to auto-stop the cluster, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - - --no-stop-max-idle - Cancels the cluster auto-stop by cluster idle duration (configured by - --stop-max-idle flag) - 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/dataproc/workflow-templates/set-managed-cluster b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster index 544b5090d..5b63d16c0 100644 --- a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster @@ -36,7 +36,7 @@ SYNOPSIS [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--secondary-worker-standard-capacity-percent-above-base=SECONDARY_WORKER_STANDARD_CAPACITY_PERCENT_ABOVE_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] + [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--tier=TIER] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -356,6 +356,9 @@ FLAGS The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. + --tier=TIER + Cluster tier. TIER must be one of: premium, standard. + --worker-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the worker instance(s). diff --git a/gcloud/beta/datastream/connection-profiles/create b/gcloud/beta/datastream/connection-profiles/create index 53171ffdf..192588a4d 100644 --- a/gcloud/beta/datastream/connection-profiles/create +++ b/gcloud/beta/datastream/connection-profiles/create @@ -14,7 +14,7 @@ SYNOPSIS | --oracle-secret-manager-stored-password=ORACLE_SECRET_MANAGER_STORED_PASSWORD) | [--mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT, [...] --mongodb-username=MONGODB_USERNAME (--mongodb-password=MONGODB_PASSWORD | --mongodb-prompt-for-password - | --mongodb-secret-manager-stored-password=MONGODB_SECRET_MANAGER_STORED_PASSWORD) (--mongodb-srv-connection-format | --mongodb-standard-connection-format) : --mongodb-replica-set=MONGODB_REPLICA_SET] | [--mysql-hostname=MYSQL_HOSTNAME --mysql-port=MYSQL_PORT --mysql-username=MYSQL_USERNAME (--mysql-password=MYSQL_PASSWORD | --mysql-prompt-for-password | --mysql-secret-manager-stored-password=MYSQL_SECRET_MANAGER_STORED_PASSWORD) : --ca-certificate=CA_CERTIFICATE --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY] | [--postgresql-database=POSTGRESQL_DATABASE --postgresql-hostname=POSTGRESQL_HOSTNAME --postgresql-port=POSTGRESQL_PORT --postgresql-username=POSTGRESQL_USERNAME (--postgresql-password=POSTGRESQL_PASSWORD | --postgresql-prompt-for-password | --postgresql-secret-manager-stored-password=POSTGRESQL_SECRET_MANAGER_STORED_PASSWORD) : [--postgresql-ca-certificate=POSTGRESQL_CA_CERTIFICATE : --postgresql-client-certificate=POSTGRESQL_CLIENT_CERTIFICATE --postgresql-client-key=POSTGRESQL_CLIENT_KEY]] | --salesforce-domain=SALESFORCE_DOMAIN (--salesforce-oauth2-client-id=SALESFORCE_OAUTH2_CLIENT_ID (--salesforce-oauth2-client-secret=SALESFORCE_OAUTH2_CLIENT_SECRET | --salesforce-prompt-for-oauth2-client-secret | --salesforce-secret-manager-stored-oauth2-client-secret=SALESFORCE_SECRET_MANAGER_STORED_OAUTH2_CLIENT_SECRET) | --salesforce-username=SALESFORCE_USERNAME (--salesforce-password=SALESFORCE_PASSWORD | --salesforce-prompt-for-password | --salesforce-secret-manager-stored-password=SALESFORCE_SECRET_MANAGER_STORED_PASSWORD) (--salesforce-prompt-for-security-token | --salesforce-secret-manager-stored-security-token=SALESFORCE_SECRET_MANAGER_STORED_SECURITY_TOKEN | --salesforce-security-token=SALESFORCE_SECURITY_TOKEN)) | --sqlserver-database=SQLSERVER_DATABASE --sqlserver-hostname=SQLSERVER_HOSTNAME --sqlserver-port=SQLSERVER_PORT --sqlserver-username=SQLSERVER_USERNAME (--sqlserver-password=SQLSERVER_PASSWORD | --sqlserver-prompt-for-password | --sqlserver-secret-manager-stored-password=SQLSERVER_SECRET_MANAGER_STORED_PASSWORD)] + | --mongodb-secret-manager-stored-password=MONGODB_SECRET_MANAGER_STORED_PASSWORD) (--mongodb-srv-connection-format | --mongodb-standard-connection-format) : --mongodb-direct-connection --mongodb-replica-set=MONGODB_REPLICA_SET --mongodb-tls] | [--mysql-hostname=MYSQL_HOSTNAME --mysql-port=MYSQL_PORT --mysql-username=MYSQL_USERNAME (--mysql-password=MYSQL_PASSWORD | --mysql-prompt-for-password | --mysql-secret-manager-stored-password=MYSQL_SECRET_MANAGER_STORED_PASSWORD) : --ca-certificate=CA_CERTIFICATE --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY] | [--postgresql-database=POSTGRESQL_DATABASE --postgresql-hostname=POSTGRESQL_HOSTNAME --postgresql-port=POSTGRESQL_PORT --postgresql-username=POSTGRESQL_USERNAME (--postgresql-password=POSTGRESQL_PASSWORD | --postgresql-prompt-for-password | --postgresql-secret-manager-stored-password=POSTGRESQL_SECRET_MANAGER_STORED_PASSWORD) : [--postgresql-ca-certificate=POSTGRESQL_CA_CERTIFICATE : --postgresql-client-certificate=POSTGRESQL_CLIENT_CERTIFICATE --postgresql-client-key=POSTGRESQL_CLIENT_KEY]] | --salesforce-domain=SALESFORCE_DOMAIN (--salesforce-oauth2-client-id=SALESFORCE_OAUTH2_CLIENT_ID (--salesforce-oauth2-client-secret=SALESFORCE_OAUTH2_CLIENT_SECRET | --salesforce-prompt-for-oauth2-client-secret | --salesforce-secret-manager-stored-oauth2-client-secret=SALESFORCE_SECRET_MANAGER_STORED_OAUTH2_CLIENT_SECRET) | --salesforce-username=SALESFORCE_USERNAME (--salesforce-password=SALESFORCE_PASSWORD | --salesforce-prompt-for-password | --salesforce-secret-manager-stored-password=SALESFORCE_SECRET_MANAGER_STORED_PASSWORD) (--salesforce-prompt-for-security-token | --salesforce-secret-manager-stored-security-token=SALESFORCE_SECRET_MANAGER_STORED_SECURITY_TOKEN | --salesforce-security-token=SALESFORCE_SECURITY_TOKEN)) | --sqlserver-database=SQLSERVER_DATABASE --sqlserver-hostname=SQLSERVER_HOSTNAME --sqlserver-port=SQLSERVER_PORT --sqlserver-username=SQLSERVER_USERNAME (--sqlserver-password=SQLSERVER_PASSWORD | --sqlserver-prompt-for-password | --sqlserver-secret-manager-stored-password=SQLSERVER_SECRET_MANAGER_STORED_PASSWORD)] [--no-connectivity | --private-connection-name=PRIVATE_CONNECTION_NAME | --static-ip-connectivity | [--forward-ssh-hostname=FORWARD_SSH_HOSTNAME @@ -166,9 +166,16 @@ OPTIONAL FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --mongodb-direct-connection + Connect to the mongodb hosts directly and do not try to resolve any + of the replicas from the replica set. + --mongodb-replica-set=MONGODB_REPLICA_SET Replica set of the MongoDB source database. + --mongodb-tls + Enable Transport Layer Security for the monogodb connection. + Exactly one of these must be specified: --mongodb-password=MONGODB_PASSWORD diff --git a/gcloud/beta/datastream/connection-profiles/update b/gcloud/beta/datastream/connection-profiles/update index 42d4d4fb9..b14be55cd 100644 --- a/gcloud/beta/datastream/connection-profiles/update +++ b/gcloud/beta/datastream/connection-profiles/update @@ -11,8 +11,8 @@ SYNOPSIS --oracle-hostname=ORACLE_HOSTNAME --oracle-port=ORACLE_PORT --oracle-username=ORACLE_USERNAME --oracle-password=ORACLE_PASSWORD | --oracle-prompt-for-password - | --oracle-secret-manager-stored-password=ORACLE_SECRET_MANAGER_STORED_PASSWORD | --mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT, - [...] --mongodb-replica-set=MONGODB_REPLICA_SET + | --oracle-secret-manager-stored-password=ORACLE_SECRET_MANAGER_STORED_PASSWORD | --mongodb-direct-connection --mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT, + [...] --mongodb-replica-set=MONGODB_REPLICA_SET --mongodb-tls --mongodb-username=MONGODB_USERNAME --mongodb-password=MONGODB_PASSWORD | --mongodb-prompt-for-password | --mongodb-secret-manager-stored-password=MONGODB_SECRET_MANAGER_STORED_PASSWORD --mongodb-srv-connection-format | --mongodb-standard-connection-format | --mysql-hostname=MYSQL_HOSTNAME --mysql-port=MYSQL_PORT --mysql-username=MYSQL_USERNAME --ca-certificate=CA_CERTIFICATE --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY --mysql-password=MYSQL_PASSWORD | --mysql-prompt-for-password | --mysql-secret-manager-stored-password=MYSQL_SECRET_MANAGER_STORED_PASSWORD | --postgresql-database=POSTGRESQL_DATABASE --postgresql-hostname=POSTGRESQL_HOSTNAME --postgresql-port=POSTGRESQL_PORT --postgresql-username=POSTGRESQL_USERNAME --postgresql-ca-certificate=POSTGRESQL_CA_CERTIFICATE --postgresql-client-certificate=POSTGRESQL_CLIENT_CERTIFICATE --postgresql-client-key=POSTGRESQL_CLIENT_KEY --postgresql-password=POSTGRESQL_PASSWORD | --postgresql-prompt-for-password | --postgresql-secret-manager-stored-password=POSTGRESQL_SECRET_MANAGER_STORED_PASSWORD | --salesforce-domain=SALESFORCE_DOMAIN --salesforce-oauth2-client-id=SALESFORCE_OAUTH2_CLIENT_ID --salesforce-oauth2-client-secret=SALESFORCE_OAUTH2_CLIENT_SECRET | --salesforce-prompt-for-oauth2-client-secret | --salesforce-secret-manager-stored-oauth2-client-secret=SALESFORCE_SECRET_MANAGER_STORED_OAUTH2_CLIENT_SECRET | --salesforce-username=SALESFORCE_USERNAME --salesforce-password=SALESFORCE_PASSWORD | --salesforce-prompt-for-password | --salesforce-secret-manager-stored-password=SALESFORCE_SECRET_MANAGER_STORED_PASSWORD --salesforce-prompt-for-security-token | --salesforce-secret-manager-stored-security-token=SALESFORCE_SECRET_MANAGER_STORED_SECURITY_TOKEN | --salesforce-security-token=SALESFORCE_SECURITY_TOKEN | --sqlserver-database=SQLSERVER_DATABASE --sqlserver-hostname=SQLSERVER_HOSTNAME --sqlserver-port=SQLSERVER_PORT --sqlserver-username=SQLSERVER_USERNAME --sqlserver-password=SQLSERVER_PASSWORD | --sqlserver-prompt-for-password | --sqlserver-secret-manager-stored-password=SQLSERVER_SECRET_MANAGER_STORED_PASSWORD] @@ -142,12 +142,19 @@ OPTIONAL FLAGS Path to secret manager, storing the password for the user used to connect to the database. + --mongodb-direct-connection + Connect to the mongodb hosts directly and do not try to resolve any + of the replicas from the replica set. + --mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT,[...] IP or hostname and port of the MongoDB source database. --mongodb-replica-set=MONGODB_REPLICA_SET Replica set of the MongoDB source database. + --mongodb-tls + Enable Transport Layer Security for the monogodb connection. + --mongodb-username=MONGODB_USERNAME Username Datastream will use to connect to the database. diff --git a/gcloud/beta/developer-connect/connections/update b/gcloud/beta/developer-connect/connections/update index 2352af744..d55d7996d 100644 --- a/gcloud/beta/developer-connect/connections/update +++ b/gcloud/beta/developer-connect/connections/update @@ -9,7 +9,7 @@ SYNOPSIS [--secret=SECRET] [--[no-]validate-only] [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations - | --remove-annotations=[__REMOVE_ANNOTATIONS,...]] + | --remove-annotations=REMOVE_ANNOTATIONS] [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE --clear-bitbucket-cloud-config | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-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_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE --clear-bitbucket-data-center-config | --clear-github-config --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --clear-github-enterprise-config --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --clear-gitlab-config --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --clear-gitlab-enterprise-config --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] [--clear-crypto-key-config [--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE @@ -17,7 +17,7 @@ SYNOPSIS [--clear-git-proxy-config --[no-]git-proxy-config-enabled] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update a connection. @@ -167,8 +167,21 @@ FLAGS --clear-annotations Clear annotations value and set to empty map. - --remove-annotations=[__REMOVE_ANNOTATIONS,...] - Remove existing value from map annotations. + --remove-annotations=REMOVE_ANNOTATIONS + Remove existing value from map annotations. Sets remove_annotations + value. + + Shorthand Example: + + --remove-annotations=string,string + + JSON Example: + + --remove-annotations=["string"] + + File Example: + + --remove-annotations=path_to_file.(yaml|json) Arguments for the connection config. @@ -809,8 +822,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/developer-connect/help b/gcloud/beta/developer-connect/help index 5a9067191..7bf3bcdde 100644 --- a/gcloud/beta/developer-connect/help +++ b/gcloud/beta/developer-connect/help @@ -18,6 +18,9 @@ GROUPS connections (BETA) Manage connection resources. + insights-configs + (BETA) Manage Insights Config resources. + operations (BETA) Manage Operation resources. diff --git a/gcloud/beta/developer-connect/insights-configs/create b/gcloud/beta/developer-connect/insights-configs/create new file mode 100644 index 000000000..9fd03407f --- /dev/null +++ b/gcloud/beta/developer-connect/insights-configs/create @@ -0,0 +1,89 @@ +NAME + gcloud beta developer-connect insights-configs create - create an insight + config + +SYNOPSIS + gcloud beta developer-connect insights-configs create + (INSIGHTS_CONFIG : --location=LOCATION) + --app-hub-application=APP_HUB_APPLICATION + [--artifact-config=ARTIFACT_CONFIG_ITEM] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create an insights config. + +EXAMPLES + To create an insights config, run: + + $ gcloud beta developer-connect insights-configs create \ + insights-config-name \ + --app-hub-application=projects/my-project/locations/\ + us-central1/applications/my-app-hub-application + +POSITIONAL ARGUMENTS + Insights config resource - The insights config to create. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument insights_config 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. + + INSIGHTS_CONFIG + ID of the insights_config or fully qualified identifier for the + insights_config. + + To set the insightsConfigs attribute: + ▸ provide the argument insights_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The region of the insight config. + + To set the location attribute: + ▸ provide the argument insights_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --app-hub-application=APP_HUB_APPLICATION + The App Hub application to which the insight config is associated. + +OPTIONAL FLAGS + --artifact-config=ARTIFACT_CONFIG_ITEM + Specifies a single artifact configuration. This flag can be repeated + for multiple configurations. + + Each configuration can be provided in a key-value format. + + Format examples: + --artifact-config=uri={REGION}-docker.pkg.dev/my-project/my-repo/my-image,buildProject=my-project + --artifact-config=[uri={REGION}-docker.pkg.dev/my-project/my-repo/my-image,buildProject=my-project] + + Supported keys within a configuration: + ◆ buildProject: String, e.g., my-project + ◆ uri: String, e.g., + {REGION}-docker.pkg.dev/my-project/my-repo/my-image + +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 developer-connect insights-configs create + + $ gcloud alpha developer-connect insights-configs create + diff --git a/gcloud/beta/developer-connect/insights-configs/delete b/gcloud/beta/developer-connect/insights-configs/delete new file mode 100644 index 000000000..2c9f01e63 --- /dev/null +++ b/gcloud/beta/developer-connect/insights-configs/delete @@ -0,0 +1,98 @@ +NAME + gcloud beta developer-connect insights-configs delete - delete + insightsConfigs + +SYNOPSIS + gcloud beta developer-connect insights-configs delete + (INSIGHTS_CONFIG : --location=LOCATION) [--async] [--etag=ETAG] + [--request-id=REQUEST_ID] [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete an insightsConfig + +EXAMPLES + To delete the insightsConfig, run: + + $ gcloud beta developer-connect insights-configs delete + +POSITIONAL ARGUMENTS + InsightsConfig resource - Value for parent. 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 insights_config 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. + + INSIGHTS_CONFIG + ID of the insightsConfig or fully qualified identifier for the + insightsConfig. + + To set the insights_config attribute: + ▸ provide the argument insights_config 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 insightsConfig resource. + + To set the location attribute: + ▸ provide the argument insights_config 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. + + --etag=ETAG + This checksum is computed by the server based on the value of other + fields, and may be sent on update and delete requests to ensure the + client has an up-to-date value before proceeding. + + --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, validate the request, but do not actually post it. + +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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud developer-connect insights-configs delete + + $ gcloud alpha developer-connect insights-configs delete + diff --git a/gcloud/beta/developer-connect/insights-configs/describe b/gcloud/beta/developer-connect/insights-configs/describe new file mode 100644 index 000000000..842b1071f --- /dev/null +++ b/gcloud/beta/developer-connect/insights-configs/describe @@ -0,0 +1,69 @@ +NAME + gcloud beta developer-connect insights-configs describe - describe + insightsConfigs + +SYNOPSIS + gcloud beta developer-connect insights-configs describe + (INSIGHTS_CONFIG : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an insightsConfig + +EXAMPLES + To describe the insightsConfig, run: + + $ gcloud beta developer-connect insights-configs describe + +POSITIONAL ARGUMENTS + InsightsConfig 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 insights_config 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. + + INSIGHTS_CONFIG + ID of the insightsConfig or fully qualified identifier for the + insightsConfig. + + To set the insights_config attribute: + ▸ provide the argument insights_config 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 insightsConfig resource. + + To set the location attribute: + ▸ provide the argument insights_config 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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud developer-connect insights-configs describe + + $ gcloud alpha developer-connect insights-configs describe + diff --git a/gcloud/beta/developer-connect/insights-configs/help b/gcloud/beta/developer-connect/insights-configs/help new file mode 100644 index 000000000..1189cfca2 --- /dev/null +++ b/gcloud/beta/developer-connect/insights-configs/help @@ -0,0 +1,42 @@ +NAME + gcloud beta developer-connect insights-configs - manage Insights Config + resources + +SYNOPSIS + gcloud beta developer-connect insights-configs COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Insights Config 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 + (BETA) Create an insight config. + + delete + (BETA) Delete insightsConfigs. + + describe + (BETA) Describe insightsConfigs. + + list + (BETA) List insightsConfigs. + + update + (BETA) Update the configuration of an insight config. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud developer-connect insights-configs + + $ gcloud alpha developer-connect insights-configs + diff --git a/gcloud/beta/developer-connect/insights-configs/list b/gcloud/beta/developer-connect/insights-configs/list new file mode 100644 index 000000000..a7c9d4467 --- /dev/null +++ b/gcloud/beta/developer-connect/insights-configs/list @@ -0,0 +1,88 @@ +NAME + gcloud beta developer-connect insights-configs list - list insightsConfigs + +SYNOPSIS + gcloud beta developer-connect insights-configs list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List insightsConfigs + +EXAMPLES + To list all insightsConfigs, run: + + $ gcloud beta developer-connect insights-configs list + +REQUIRED FLAGS + Location resource - Parent value for ListInsightsConfigsRequest. 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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud developer-connect insights-configs list + + $ gcloud alpha developer-connect insights-configs list + diff --git a/gcloud/beta/developer-connect/insights-configs/update b/gcloud/beta/developer-connect/insights-configs/update new file mode 100644 index 000000000..25e7c6ea4 --- /dev/null +++ b/gcloud/beta/developer-connect/insights-configs/update @@ -0,0 +1,97 @@ +NAME + gcloud beta developer-connect insights-configs update - update the + configuration of an insight config + +SYNOPSIS + gcloud beta developer-connect insights-configs update + (INSIGHTS_CONFIG : --location=LOCATION) + (--run-discovery + --artifact-uri=ARTIFACT_URI --build-project=BUILD_PROJECT) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the configuration of an insights config. + +EXAMPLES + To update the state of an insights config, run: + + $ gcloud beta developer-connect insights-configs update \ + insights-config-name --run-discovery + + To update the Artifact Analysis project for an artifact in an insights + config, run: + + $ gcloud beta developer-connect insights-configs update \ + insights-config-name \ + --artifact-uri=us-{location}-docker.pkg.dev/my-project/\ + my-artifact-repo/my-image --build-project={build_project} + +POSITIONAL ARGUMENTS + Insights config resource - The insights config 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 insights_config 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. + + INSIGHTS_CONFIG + ID of the insights_config or fully qualified identifier for the + insights_config. + + To set the insightsConfigs attribute: + ▸ provide the argument insights_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The region of the insight config. + + To set the location attribute: + ▸ provide the argument insights_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Update the insight config. + + At least one of these must be specified: + + --run-discovery + Sets the state of the insight config to PENDING and kicks off the + discovery flow. + + --artifact-uri=ARTIFACT_URI + Identifier for the specific artifact you want to update + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --build-project=BUILD_PROJECT + The project ID of the project to where the artifact is built. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +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 developer-connect insights-configs update + + $ gcloud alpha developer-connect insights-configs update + diff --git a/gcloud/beta/dns/policies/update b/gcloud/beta/dns/policies/update index 983ff1f35..ee5bd31ff 100644 --- a/gcloud/beta/dns/policies/update +++ b/gcloud/beta/dns/policies/update @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta dns policies update POLICY [--alternative-name-servers=[NAME_SERVERS,...]] - [--description=DESCRIPTION] [--enable-dns64-all-queries] + [--description=DESCRIPTION] [--[no-]enable-dns64-all-queries] [--enable-inbound-forwarding] [--enable-logging] [--networks=[NETWORKS,...]] [--private-alternative-name-servers=[NAME_SERVERS,...]] @@ -46,9 +46,10 @@ FLAGS --description=DESCRIPTION A description of the policy. - --enable-dns64-all-queries + --[no-]enable-dns64-all-queries Specifies whether to allow networks bound to this policy to use DNS64 - for IPv6-only VM instances. + for IPv6-only VM instances. Use --enable-dns64-all-queries to enable + and --no-enable-dns64-all-queries to disable. --enable-inbound-forwarding Specifies whether to allow networks bound to this policy to receive DNS diff --git a/gcloud/beta/eventarc/pipelines/create b/gcloud/beta/eventarc/pipelines/create index b2f5bbda4..d2ff05728 100644 --- a/gcloud/beta/eventarc/pipelines/create +++ b/gcloud/beta/eventarc/pipelines/create @@ -390,30 +390,26 @@ REQUIRED FLAGS The destination Workflow ID. For example: $ gcloud eventarc pipelines create example-pipeline \ - --destinations=workflow=my-workflow,\ - network_attachment=example-network-attachment + --destinations=workflow=my-workflow message_bus The destination Message Bus ID. For example: $ gcloud eventarc pipelines create example-pipeline \ - --destinations=message_bus=my-message-bus,\ - network_attachment=example-network-attachment + --destinations=message_bus=my-message-bus pubsub_topic The destination Pub/Sub topic ID. For example: $ gcloud eventarc pipelines create example-pipeline \ - --destinations=pubsub_topic=my-topic,\ - network_attachment=example-network-attachment + --destinations=pubsub_topic=my-topic project The project ID of the destination resource. If project is not set, then the project ID of the pipeline is used. For example: $ gcloud eventarc pipelines create example-pipeline \ - --destinations=project=example-project,workflow=my-workflow,\ - network_attachment=example-network-attachment + --destinations=project=example-project,workflow=my-workflow Note: When http_endpoint_uri is set, project can't be set. @@ -435,7 +431,8 @@ REQUIRED FLAGS --destinations=network_attachment=my-network-attachment,\ http_endpoint_uri='https://example.com' - Note: A network attachment must be specified for a pipeline. + Note: A network attachment must be specified for a pipeline when + http_endpoint_uri is set. google_oidc_authentication_service_account The service account email used to generate the OIDC token. The diff --git a/gcloud/beta/eventarc/pipelines/update b/gcloud/beta/eventarc/pipelines/update index ae0628ac2..2ffd04c6e 100644 --- a/gcloud/beta/eventarc/pipelines/update +++ b/gcloud/beta/eventarc/pipelines/update @@ -221,30 +221,26 @@ FLAGS The destination Workflow ID. For example: $ gcloud eventarc pipelines create example-pipeline \ - --destinations=workflow=my-workflow,\ - network_attachment=example-network-attachment + --destinations=workflow=my-workflow message_bus The destination Message Bus ID. For example: $ gcloud eventarc pipelines create example-pipeline \ - --destinations=message_bus=my-message-bus,\ - network_attachment=example-network-attachment + --destinations=message_bus=my-message-bus pubsub_topic The destination Pub/Sub topic ID. For example: $ gcloud eventarc pipelines create example-pipeline \ - --destinations=pubsub_topic=my-topic,\ - network_attachment=example-network-attachment + --destinations=pubsub_topic=my-topic project The project ID of the destination resource. If project is not set, then the project ID of the pipeline is used. For example: $ gcloud eventarc pipelines create example-pipeline \ - --destinations=project=example-project,workflow=my-workflow,\ - network_attachment=example-network-attachment + --destinations=project=example-project,workflow=my-workflow Note: When http_endpoint_uri is set, project can't be set. @@ -266,7 +262,8 @@ FLAGS --destinations=network_attachment=my-network-attachment,\ http_endpoint_uri='https://example.com' - Note: A network attachment must be specified for a pipeline. + Note: A network attachment must be specified for a pipeline when + http_endpoint_uri is set. google_oidc_authentication_service_account The service account email used to generate the OIDC token. The diff --git a/gcloud/beta/firebase/test/android/run b/gcloud/beta/firebase/test/android/run index 9d1d79b85..377503b79 100644 --- a/gcloud/beta/firebase/test/android/run +++ b/gcloud/beta/firebase/test/android/run @@ -446,7 +446,7 @@ ANDROID INSTRUMENTATION TEST FLAGS test targets). Each target filter must be fully qualified with the package name, class name, or test annotation desired. Any test filter supported by am instrument -e ... is supported. See - https://developer.android.com/reference/android/support/test/runner/AndroidJUnitRunner + https://developer.android.com/reference/androidx/test/runner/AndroidJUnitRunner for more information. Examples: ◆ --test-targets "package com.my.package.name" diff --git a/gcloud/beta/firestore/databases/create b/gcloud/beta/firestore/databases/create index 5178de29e..483687861 100644 --- a/gcloud/beta/firestore/databases/create +++ b/gcloud/beta/firestore/databases/create @@ -11,7 +11,7 @@ SYNOPSIS EXAMPLES To create a Firestore Enterprise database named foo in nam5 for use with - Ignite APIs. + MongoDB Compatibility. $ gcloud beta firestore databases create --database=foo \ --edition=enterprise --location=nam5 diff --git a/gcloud/beta/firestore/indexes/composite/create b/gcloud/beta/firestore/indexes/composite/create index c18421ad7..7c0bd1edf 100644 --- a/gcloud/beta/firestore/indexes/composite/create +++ b/gcloud/beta/firestore/indexes/composite/create @@ -59,7 +59,7 @@ REQUIRED FLAGS Shorthand Example: - --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat={}} --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat={}} + --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat} --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat} JSON Example: diff --git a/gcloud/beta/healthcare/annotation-stores/add-iam-policy-binding b/gcloud/beta/healthcare/annotation-stores/add-iam-policy-binding deleted file mode 100644 index 1abd02118..000000000 --- a/gcloud/beta/healthcare/annotation-stores/add-iam-policy-binding +++ /dev/null @@ -1,145 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores add-iam-policy-binding - add an - IAM policy binding to a Cloud Healthcare API annotation store - -SYNOPSIS - gcloud beta healthcare annotation-stores add-iam-policy-binding - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - --member=PRINCIPAL --role=ROLE - [--condition=[KEY=VALUE,...] | --condition-from-file=PATH_TO_FILE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Add an IAM policy binding to a Cloud Healthcare API annotation - store. - -EXAMPLES - To add an IAM policy binding for the role of 'roles/editor' for the user - 'test-user@gmail.com' on the annotation store 'test-annotation-store', run: - - $ gcloud beta healthcare annotation-stores add-iam-policy-binding \ - test-annotation-store --dataset=test-dataset \ - --member='user:test-user@gmail.com' --role='roles/editor' - - See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and member types. - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store to add an - IAM policy binding to. The arguments in this group can be used to specify - the attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - -REQUIRED FLAGS - --member=PRINCIPAL - The principal to add the binding for. Should be of the form - user|group|serviceAccount:email or domain:domain. - - Examples: user:test-user@gmail.com, group:admins@example.com, - serviceAccount:test123@example.domain.com, or - domain:example.domain.com. - - Some resources also accept the following special values: - ◆ allUsers - Special identifier that represents anyone who is on the - internet, with or without a Google account. - ◆ allAuthenticatedUsers - Special identifier that represents anyone - who is authenticated with a Google account or a service account. - - --role=ROLE - Role name to assign to the principal. The role name is the complete - path of a predefined role, such as roles/logging.viewer, or the role ID - for a custom role, such as - organizations/{ORGANIZATION_ID}/roles/logging.viewer. - -OPTIONAL FLAGS - At most one of these can be specified: - - --condition=[KEY=VALUE,...] - A condition to include in the binding. When the condition is - explicitly specified as None (--condition=None), a binding without a - condition is added. When the condition is specified and is not None, - --role cannot be a basic role. Basic roles are roles/editor, - roles/owner, and roles/viewer. For more on conditions, refer to the - conditions overview guide: - https://cloud.google.com/iam/docs/conditions-overview - - When using the --condition flag, include the following key-value - pairs: - - expression - (Required) Condition expression that evaluates to True or False. - This uses a subset of Common Expression Language syntax. - - If the condition expression includes a comma, use a different - delimiter to separate the key-value pairs. Specify the delimiter - before listing the key-value pairs. For example, to specify a - colon (:) as the delimiter, do the following: - --condition=^:^title=TITLE:expression=EXPRESSION. For more - information, see - https://cloud.google.com/sdk/gcloud/reference/topic/escaping. - - title - (Required) A short string describing the purpose of the - expression. - - description - (Optional) Additional description for the expression. - - --condition-from-file=PATH_TO_FILE - Path to a local JSON or YAML file that defines the condition. To see - available fields, see the help for --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. - -API REFERENCE - This command uses the healthcare/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores add-iam-policy-binding - diff --git a/gcloud/beta/healthcare/annotation-stores/create b/gcloud/beta/healthcare/annotation-stores/create deleted file mode 100644 index 73e1ea11d..000000000 --- a/gcloud/beta/healthcare/annotation-stores/create +++ /dev/null @@ -1,77 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores create - create a Cloud Healthcare - API annotation store - -SYNOPSIS - gcloud beta healthcare annotation-stores create - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Create a Cloud Healthcare API annotation store. - -EXAMPLES - To create an annotation store called 'test-annotation-store', run: - - $ gcloud beta healthcare annotation-stores create \ - test-annotation-store --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store to - create. The arguments in this group can be used to specify the attributes - of this resource. (NOTE) Some attributes are not given arguments in this - group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/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. - -API REFERENCE - This command uses the healthcare/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores create - diff --git a/gcloud/beta/healthcare/annotation-stores/delete b/gcloud/beta/healthcare/annotation-stores/delete deleted file mode 100644 index 419596bd2..000000000 --- a/gcloud/beta/healthcare/annotation-stores/delete +++ /dev/null @@ -1,77 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores delete - delete a Cloud Healthcare - API annotation store - -SYNOPSIS - gcloud beta healthcare annotation-stores delete - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Delete a Cloud Healthcare API annotation store. - -EXAMPLES - To delete the annotation-store 'test-annotation-store', run: - - $ gcloud beta healthcare annotation-stores delete \ - test-annotation-store --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/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. - -API REFERENCE - This command uses the healthcare/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores delete - diff --git a/gcloud/beta/healthcare/annotation-stores/describe b/gcloud/beta/healthcare/annotation-stores/describe deleted file mode 100644 index 1b21f27dc..000000000 --- a/gcloud/beta/healthcare/annotation-stores/describe +++ /dev/null @@ -1,77 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores describe - describe a Cloud - Healthcare API annotation store - -SYNOPSIS - gcloud beta healthcare annotation-stores describe - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Describe a Cloud Healthcare API annotation store. - -EXAMPLES - To describe the annotation-store 'test-annotation-store', run: - - $ gcloud beta healthcare annotation-stores describe \ - test-annotation-store --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/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. - -API REFERENCE - This command uses the healthcare/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores describe - diff --git a/gcloud/beta/healthcare/annotation-stores/evaluate/bq b/gcloud/beta/healthcare/annotation-stores/evaluate/bq deleted file mode 100644 index f0ce2bfc5..000000000 --- a/gcloud/beta/healthcare/annotation-stores/evaluate/bq +++ /dev/null @@ -1,112 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores evaluate bq - evaluate a Cloud - Healthcare API Annotation store and report to BigQuery - -SYNOPSIS - gcloud beta healthcare annotation-stores evaluate bq - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - --bq-table=BQ_TABLE --golden-store=GOLDEN_STORE [--async] - [--write-disposition=WRITE_DISPOSITION] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Evaluate Cloud Healthcare API Annotation store against a ground - truth store and report the results to BigQuery. - -EXAMPLES - To evaluate the annotation-store 'eval-annotation-store' against a ground - truth annotation-store - projects/my-project/locations/my-location/datasets/test-dataset/annotationStores/golden-annotation-store, - and report the metric to the BigQuery table bqtable in the BigQuery dataset - bqdataset, run: - - $ gcloud beta healthcare annotation-stores evaluate bq \ - eval-annotation-store \ - --golden-store=projects/my-project/locations/my-location/\ - datasets/test-dataset/annotationStores/golden-annotation-store \ - --bq-table=bq://my-project.bqdataset.bqtable \ - --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API Annotation store to be - evaluated. 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - -REQUIRED FLAGS - --bq-table=BQ_TABLE - BigQuery table where evaluation results are written. - - --golden-store=GOLDEN_STORE - Ground truth AnnotationStore to compare against. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --write-disposition=WRITE_DISPOSITION - Determines whether existing table in the destination dataset are - overwritten or appended to. WRITE_DISPOSITION must be one of: - - write-append - Append data to the existing table. - - write-empty - Only export data if the destination table is empty. - - write-truncate - Erase all existing data in a table before writing the instances. - -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 healthcare/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores evaluate bq - diff --git a/gcloud/beta/healthcare/annotation-stores/evaluate/help b/gcloud/beta/healthcare/annotation-stores/evaluate/help deleted file mode 100644 index db8ffadd6..000000000 --- a/gcloud/beta/healthcare/annotation-stores/evaluate/help +++ /dev/null @@ -1,29 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores evaluate - manage Cloud Healthcare - API Annotation store evaluates - -SYNOPSIS - gcloud beta healthcare annotation-stores evaluate COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Manage Cloud Healthcare API Annotation store evaluates. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - bq - (BETA) Evaluate a Cloud Healthcare API Annotation store and report to - BigQuery. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores evaluate - diff --git a/gcloud/beta/healthcare/annotation-stores/export/bq b/gcloud/beta/healthcare/annotation-stores/export/bq deleted file mode 100644 index 012fbb54a..000000000 --- a/gcloud/beta/healthcare/annotation-stores/export/bq +++ /dev/null @@ -1,103 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores export bq - export Cloud - Healthcare API Annotation records to BigQuery - -SYNOPSIS - gcloud beta healthcare annotation-stores export bq - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - --bq-table=BQ_TABLE [--async] [--write-disposition=WRITE_DISPOSITION] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Export Cloud Healthcare API Annotation records to BigQuery. - -EXAMPLES - To export the annotation-store 'test-annotation-store' to the BigQuery - table 'bqtable' in the BigQuery dataset bqdataset, run: - - $ gcloud beta healthcare annotation-stores export bq \ - test-annotation-store \ - --bq-table=bq://my-project.bqdataset.bqtable \ - --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API Annotation store to export - annotations from. 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - -REQUIRED FLAGS - --bq-table=BQ_TABLE - BigQuery table that annotation records will be exported to. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --write-disposition=WRITE_DISPOSITION - Determines whether existing table in the destination dataset are - overwritten or appended to. WRITE_DISPOSITION must be one of: - - write-append - Append data to the existing table. - - write-empty - Only export data if the destination table is empty. - - write-truncate - Erase all existing data in a table before writing the instances. - -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 healthcare/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores export bq - diff --git a/gcloud/beta/healthcare/annotation-stores/export/gcs b/gcloud/beta/healthcare/annotation-stores/export/gcs deleted file mode 100644 index 534dec2f6..000000000 --- a/gcloud/beta/healthcare/annotation-stores/export/gcs +++ /dev/null @@ -1,92 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores export gcs - export Cloud - Healthcare API Annotation records to Google Cloud Storage - -SYNOPSIS - gcloud beta healthcare annotation-stores export gcs - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - --gcs-uri=GCS_URI [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Export Cloud Healthcare API Annotation records to Google Cloud - Storage. - -EXAMPLES - To export the annotation-store 'test-annotation-store' to the existing - bucket 'testGcsBucket' in the folder 'someFolder', run: - - $ gcloud beta healthcare annotation-stores export gcs \ - test-annotation-store --gcs-uri=gs://testGcsBucket/someFolder \ - --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API Annotation store to export - annotations from. 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - -REQUIRED FLAGS - --gcs-uri=GCS_URI - The Cloud Storage destination location. Specify a path to a Cloud - Storage bucket or folder rather than a concrete object. The server - creates one object per annotation record. Each object contains a - JSON-formatted text file of an Annotation record. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the healthcare/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores export gcs - diff --git a/gcloud/beta/healthcare/annotation-stores/export/help b/gcloud/beta/healthcare/annotation-stores/export/help deleted file mode 100644 index 5b6013c1a..000000000 --- a/gcloud/beta/healthcare/annotation-stores/export/help +++ /dev/null @@ -1,32 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores export - manage Cloud Healthcare - API Annotation store exports - -SYNOPSIS - gcloud beta healthcare annotation-stores export COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Manage Cloud Healthcare API Annotation store exports. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - bq - (BETA) Export Cloud Healthcare API Annotation records to BigQuery. - - gcs - (BETA) Export Cloud Healthcare API Annotation records to Google Cloud - Storage. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores export - diff --git a/gcloud/beta/healthcare/annotation-stores/help b/gcloud/beta/healthcare/annotation-stores/help deleted file mode 100644 index 471e5864c..000000000 --- a/gcloud/beta/healthcare/annotation-stores/help +++ /dev/null @@ -1,67 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores - manage Cloud Healthcare API - annotation stores - -SYNOPSIS - gcloud beta healthcare annotation-stores GROUP | COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Manage Cloud Healthcare API annotation stores. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - evaluate - (BETA) Manage Cloud Healthcare API Annotation store evaluates. - - export - (BETA) Manage Cloud Healthcare API Annotation store exports. - - import - (BETA) Manage Cloud Healthcare API Annotation store imports. - -COMMANDS - COMMAND is one of the following: - - add-iam-policy-binding - (BETA) Add an IAM policy binding to a Cloud Healthcare API annotation - store. - - create - (BETA) Create a Cloud Healthcare API annotation store. - - delete - (BETA) Delete a Cloud Healthcare API annotation store. - - describe - (BETA) Describe a Cloud Healthcare API annotation store. - - get-iam-policy - (BETA) Retrieve the IAM policy for a Cloud Healthcare API annotation - store. - - list - (BETA) List Cloud Healthcare API annotation stores. - - remove-iam-policy-binding - (BETA) Remove an IAM policy binding from a Cloud Healthcare API - annotation store. - - set-iam-policy - (BETA) Set the IAM policy for a Cloud Healthcare API annotation store. - - update - (BETA) Update a Cloud Healthcare API annotation store. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores - diff --git a/gcloud/beta/healthcare/annotation-stores/import/gcs b/gcloud/beta/healthcare/annotation-stores/import/gcs deleted file mode 100644 index ae631195f..000000000 --- a/gcloud/beta/healthcare/annotation-stores/import/gcs +++ /dev/null @@ -1,93 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores import gcs - import Annotation - records from Google Cloud Storage into a Cloud Healthcare API - Annotation store - -SYNOPSIS - gcloud beta healthcare annotation-stores import gcs - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - --gcs-uri=GCS_URI [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Import Annotation records from Google Cloud Storage into a Cloud - Healthcare API Annotation store. - -EXAMPLES - To import the Annotation records from the existing bucket 'testGcsBucket' - in the folder 'someFolder' into the Annotation store - 'test-annotation-store', run: - - $ gcloud beta healthcare annotation-stores import gcs \ - test-annotation-store --gcs-uri=gs://testGcsBucket/someFolder \ - --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API Annotation store into - which the data is imported. 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - -REQUIRED FLAGS - --gcs-uri=GCS_URI - Cloud Storage source data locations. Each Cloud Storage object is a - text file that contains exactly one JSON structure conforming to the - Annotation proto. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the healthcare/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores import gcs - diff --git a/gcloud/beta/healthcare/annotation-stores/import/help b/gcloud/beta/healthcare/annotation-stores/import/help deleted file mode 100644 index d4ce071b5..000000000 --- a/gcloud/beta/healthcare/annotation-stores/import/help +++ /dev/null @@ -1,29 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores import - manage Cloud Healthcare - API Annotation store imports - -SYNOPSIS - gcloud beta healthcare annotation-stores import COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Manage Cloud Healthcare API Annotation store imports. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - gcs - (BETA) Import Annotation records from Google Cloud Storage into a Cloud - Healthcare API Annotation store. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores import - diff --git a/gcloud/beta/healthcare/annotation-stores/remove-iam-policy-binding b/gcloud/beta/healthcare/annotation-stores/remove-iam-policy-binding deleted file mode 100644 index f1f2dd4a5..000000000 --- a/gcloud/beta/healthcare/annotation-stores/remove-iam-policy-binding +++ /dev/null @@ -1,151 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores remove-iam-policy-binding - remove - an IAM policy binding from a Cloud Healthcare API annotation store - -SYNOPSIS - gcloud beta healthcare annotation-stores remove-iam-policy-binding - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - --member=PRINCIPAL --role=ROLE - [--all | --condition=[KEY=VALUE,...] - | --condition-from-file=PATH_TO_FILE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Remove an IAM policy binding from a Cloud Healthcare API annotation - store. - -EXAMPLES - To remove an IAM policy binding for the role of 'roles/editor' for the user - 'test-user@gmail.com' on the annotation store 'test-annotation-store', run: - - $ gcloud beta healthcare annotation-stores \ - remove-iam-policy-binding test-annotation-store \ - --dataset=test-dataset --member='user:test-user@gmail.com' \ - --role='roles/editor' - - See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and member types. - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store to remove - an IAM policy binding from. 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - -REQUIRED FLAGS - --member=PRINCIPAL - The principal to remove the binding for. Should be of the form - user|group|serviceAccount:email or domain:domain. - - Examples: user:test-user@gmail.com, group:admins@example.com, - serviceAccount:test123@example.domain.com, or - domain:example.domain.com. - - Deleted principals have an additional deleted: prefix and a ?uid=UID - suffix, where UID is a unique identifier for the principal. Example: - deleted:user:test-user@gmail.com?uid=123456789012345678901. - - Some resources also accept the following special values: - ◆ allUsers - Special identifier that represents anyone who is on the - internet, with or without a Google account. - ◆ allAuthenticatedUsers - Special identifier that represents anyone - who is authenticated with a Google account or a service account. - - --role=ROLE - The role to remove the principal from. - -OPTIONAL FLAGS - At most one of these can be specified: - - --all - Remove all bindings with this role and principal, irrespective of any - conditions. - - --condition=[KEY=VALUE,...] - The condition of the binding that you want to remove. When the - condition is explicitly specified as None (--condition=None), a - binding without a condition is removed. Otherwise, only a binding - with a condition that exactly matches the specified condition - (including the optional description) is removed. For more on - conditions, refer to the conditions overview guide: - https://cloud.google.com/iam/docs/conditions-overview - - When using the --condition flag, include the following key-value - pairs: - - expression - (Required) Condition expression that evaluates to True or False. - This uses a subset of Common Expression Language syntax. - - If the condition expression includes a comma, use a different - delimiter to separate the key-value pairs. Specify the delimiter - before listing the key-value pairs. For example, to specify a - colon (:) as the delimiter, do the following: - --condition=^:^title=TITLE:expression=EXPRESSION. For more - information, see - https://cloud.google.com/sdk/gcloud/reference/topic/escaping. - - title - (Required) A short string describing the purpose of the - expression. - - description - (Optional) Additional description for the expression. - - --condition-from-file=PATH_TO_FILE - Path to a local JSON or YAML file that defines the condition. To see - available fields, see the help for --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. - -API REFERENCE - This command uses the healthcare/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores remove-iam-policy-binding - diff --git a/gcloud/beta/healthcare/annotation-stores/set-iam-policy b/gcloud/beta/healthcare/annotation-stores/set-iam-policy deleted file mode 100644 index d1f545f1c..000000000 --- a/gcloud/beta/healthcare/annotation-stores/set-iam-policy +++ /dev/null @@ -1,88 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores set-iam-policy - set the IAM - policy for a Cloud Healthcare API annotation store - -SYNOPSIS - gcloud beta healthcare annotation-stores set-iam-policy - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) POLICY_FILE - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Set the IAM policy for a Cloud Healthcare API annotation store. - -EXAMPLES - The following command will read am IAM policy defined in a JSON file - 'policy.json' and set it for the annotation store 'test-annotation-store': - - $ gcloud beta healthcare annotation-stores set-iam-policy \ - test-annotation-store policy.json --dataset=test-dataset - - See https://cloud.google.com/iam/docs/managing-policies for details of the - policy file format and contents. - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store whose IAM - policy to set. 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. - - 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 healthcare/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores set-iam-policy - diff --git a/gcloud/beta/healthcare/annotation-stores/update b/gcloud/beta/healthcare/annotation-stores/update deleted file mode 100644 index 54cd5f139..000000000 --- a/gcloud/beta/healthcare/annotation-stores/update +++ /dev/null @@ -1,77 +0,0 @@ -NAME - gcloud beta healthcare annotation-stores update - update a Cloud Healthcare - API annotation store - -SYNOPSIS - gcloud beta healthcare annotation-stores update - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Update a Cloud Healthcare API annotation store. - -EXAMPLES - To update the annotation store 'test-annotation-store', run: - - $ gcloud beta healthcare annotation-stores update \ - test-annotation-store --dataset=test-dataset - -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store 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 annotation_store 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. - - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - - --location=LOCATION - Google Cloud location. - - To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/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. - -API REFERENCE - This command uses the healthcare/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha healthcare annotation-stores update - diff --git a/gcloud/beta/healthcare/datasets/deidentify b/gcloud/beta/healthcare/datasets/deidentify index 17f1e73c8..6b71598a3 100644 --- a/gcloud/beta/healthcare/datasets/deidentify +++ b/gcloud/beta/healthcare/datasets/deidentify @@ -4,9 +4,8 @@ NAME SYNOPSIS gcloud beta healthcare datasets deidentify (DATASET : --location=LOCATION) - --destination-dataset=DESTINATION_DATASET - [--annotation-store=ANNOTATION_STORE] [--async] [--default-fhir-config] - [--dicom-filter-tags=[DICOM_FILTER_TAGS,...]] + --destination-dataset=DESTINATION_DATASET [--async] + [--default-fhir-config] [--dicom-filter-tags=[DICOM_FILTER_TAGS,...]] [--text-redaction-mode=TEXT_REDACTION_MODE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -64,16 +63,6 @@ REQUIRED FLAGS new dataset must not exist, or the request will fail. OPTIONAL FLAGS - --annotation-store=ANNOTATION_STORE - The name of the annotation store to output the location of sensitive - data (e.g., - projects/{projectId}/locations/{locationId}/datasets/{datasetId}/annotationStores/{annotationStoreId}). - The annotation store, if not in the destination dataset, must already - exist. The generated annotations will contain the original values of - the de-identified data in the 'quote' field. See - https://cloud.google.com/healthcare/docs/how-tos/annotations-deidentify - for more details. - --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/beta/healthcare/dicom-stores/deidentify b/gcloud/beta/healthcare/dicom-stores/deidentify index 954791448..f8e37e2b2 100644 --- a/gcloud/beta/healthcare/dicom-stores/deidentify +++ b/gcloud/beta/healthcare/dicom-stores/deidentify @@ -5,8 +5,7 @@ NAME SYNOPSIS gcloud beta healthcare dicom-stores deidentify (DICOM_STORE : --dataset=DATASET --location=LOCATION) - --destination-store=DESTINATION_STORE - [--annotation-store=ANNOTATION_STORE] [--async] + --destination-store=DESTINATION_STORE [--async] [--dicom-filter-tags=[DICOM_FILTER_TAGS,...]] [--text-redaction-mode=TEXT_REDACTION_MODE] [GCLOUD_WIDE_FLAG ...] @@ -74,16 +73,6 @@ REQUIRED FLAGS fail. OPTIONAL FLAGS - --annotation-store=ANNOTATION_STORE - The name of the annotation store to output the location of sensitive - data (e.g., - projects/{projectId}/locations/{locationId}/datasets/{datasetId}/annotationStores/{annotationStoreId}). - The annotation store must already exist. The generated annotations will - contain the original values of the de-identified data in the 'quote' - field. See - https://cloud.google.com/healthcare/docs/how-tos/annotations-deidentify - for more details. - --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/beta/healthcare/fhir-stores/deidentify b/gcloud/beta/healthcare/fhir-stores/deidentify index 0f5306196..26b1109a7 100644 --- a/gcloud/beta/healthcare/fhir-stores/deidentify +++ b/gcloud/beta/healthcare/fhir-stores/deidentify @@ -5,8 +5,7 @@ NAME SYNOPSIS gcloud beta healthcare fhir-stores deidentify (FHIR_STORE : --dataset=DATASET --location=LOCATION) - --destination-store=DESTINATION_STORE - [--annotation-store=ANNOTATION_STORE] [--async] [GCLOUD_WIDE_FLAG ...] + --destination-store=DESTINATION_STORE [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) De-identify data from the source store and write it to the @@ -69,16 +68,6 @@ REQUIRED FLAGS fail. OPTIONAL FLAGS - --annotation-store=ANNOTATION_STORE - The name of the annotation store to output the location of sensitive - data (e.g., - projects/{projectId}/locations/{locationId}/datasets/{datasetId}/annotationStores/{annotationStoreId}). - The annotation store must already exist. The generated annotations will - contain the original values of the de-identified data in the 'quote' - field. See - https://cloud.google.com/healthcare/docs/how-tos/annotations-deidentify - for more details. - --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/beta/healthcare/help b/gcloud/beta/healthcare/help index 6c91beeb2..bca1eeaec 100644 --- a/gcloud/beta/healthcare/help +++ b/gcloud/beta/healthcare/help @@ -15,9 +15,6 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: - annotation-stores - (BETA) Manage Cloud Healthcare API annotation stores. - consent-stores (BETA) Manage Cloud Healthcare API consent stores. diff --git a/gcloud/beta/iam/policy-bindings/create b/gcloud/beta/iam/policy-bindings/create index 31c3cdd69..3a121b4e2 100644 --- a/gcloud/beta/iam/policy-bindings/create +++ b/gcloud/beta/iam/policy-bindings/create @@ -5,7 +5,9 @@ SYNOPSIS gcloud beta iam policy-bindings create (POLICY_BINDING : --folder=FOLDER --location=LOCATION --organization=ORGANIZATION) - --policy=POLICY --target-principal-set=TARGET_PRINCIPAL_SET + --policy=POLICY + (--target-principal-set=TARGET_PRINCIPAL_SET + | --target-resource=TARGET_RESOURCE) [--annotations=[ANNOTATIONS,...]] [--async] [--display-name=DISPLAY_NAME] [--etag=ETAG] [--policy-kind=POLICY_KIND] [--condition-description=CONDITION_DESCRIPTION @@ -31,8 +33,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,7 +98,7 @@ 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. @@ -105,26 +107,46 @@ REQUIRED FLAGS Arguments for the target. + At most one of these can be specified: + --target-principal-set=TARGET_PRINCIPAL_SET Full Resource Name used for principal access boundary policy - bindings Examples: + 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/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 binding's 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 binding's parented by a folder: + ◇ Folder: + //cloudresourcemanager.googleapis.com/folders/FOLDER_ID + ▫ For binding's 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 + + --target-resource=TARGET_RESOURCE + Full Resource Name used for access policy bindings Examples: + + ▹ 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 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 @@ -164,8 +186,11 @@ OPTIONAL FLAGS ◆ Left empty (will be automatically set to the policy kind) ◆ The input policy kind. - POLICY_KIND must be (only one value is supported): + POLICY_KIND must be one of: + access + Access policy kind. Keep behind visibility label until Access + Policy launch. principal-access-boundary Principal access boundary policy kind diff --git a/gcloud/beta/iam/policy-bindings/update b/gcloud/beta/iam/policy-bindings/update index 081b5fb55..f1788f01e 100644 --- a/gcloud/beta/iam/policy-bindings/update +++ b/gcloud/beta/iam/policy-bindings/update @@ -8,8 +8,8 @@ SYNOPSIS [--async] [--display-name=DISPLAY_NAME] [--etag=ETAG] [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations - | --remove-annotations=[__REMOVE_ANNOTATIONS,...]] - [--condition-description=CONDITION_DESCRIPTION + | --remove-annotations=REMOVE_ANNOTATIONS] + [--clear-condition --condition-description=CONDITION_DESCRIPTION --condition-expression=CONDITION_EXPRESSION --condition-location=CONDITION_LOCATION --condition-title=CONDITION_TITLE] [GCLOUD_WIDE_FLAG ...] @@ -28,8 +28,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: @@ -108,7 +108,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. @@ -131,7 +131,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. @@ -158,8 +158,21 @@ FLAGS --clear-annotations Clear annotations value and set to empty map. - --remove-annotations=[__REMOVE_ANNOTATIONS,...] - Remove existing value from map annotations. + --remove-annotations=REMOVE_ANNOTATIONS + Remove existing value from map annotations. Sets remove_annotations + value. + + Shorthand Example: + + --remove-annotations=string,string + + JSON Example: + + --remove-annotations=["string"] + + File Example: + + --remove-annotations=path_to_file.(yaml|json) Represents a textual expression in the Common Expression Language (CEL) syntax. CEL is a C-like expression language. The syntax and semantics of @@ -193,6 +206,9 @@ FLAGS expression are determined by the service that evaluates it. See the service documentation for additional information. + --clear-condition + Set googleIamV3betaPolicyBinding.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/beta/iam/principal-access-boundary-policies/create b/gcloud/beta/iam/principal-access-boundary-policies/create index 478df54e9..1373f269a 100644 --- a/gcloud/beta/iam/principal-access-boundary-policies/create +++ b/gcloud/beta/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/beta/iam/principal-access-boundary-policies/delete b/gcloud/beta/iam/principal-access-boundary-policies/delete index 8a2b23a71..ecf596ddf 100644 --- a/gcloud/beta/iam/principal-access-boundary-policies/delete +++ b/gcloud/beta/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/beta/iam/principal-access-boundary-policies/update b/gcloud/beta/iam/principal-access-boundary-policies/update index 89567898d..9bb1a5986 100644 --- a/gcloud/beta/iam/principal-access-boundary-policies/update +++ b/gcloud/beta/iam/principal-access-boundary-policies/update @@ -9,8 +9,9 @@ SYNOPSIS [--display-name=DISPLAY_NAME] [--etag=ETAG] [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations - | --remove-annotations=[__REMOVE_ANNOTATIONS,...]] - [--details-enforcement-version=DETAILS_ENFORCEMENT_VERSION + | --remove-annotations=REMOVE_ANNOTATIONS] + [--clear-details + --details-enforcement-version=DETAILS_ENFORCEMENT_VERSION --details-rules=[description=DESCRIPTION], [effect=EFFECT],[resources=RESOURCES] | --add-details-rules=[description=DESCRIPTION], @@ -134,16 +135,33 @@ FLAGS --clear-annotations Clear annotations value and set to empty map. - --remove-annotations=[__REMOVE_ANNOTATIONS,...] - Remove existing value from map annotations. + --remove-annotations=REMOVE_ANNOTATIONS + Remove existing value from map annotations. Sets remove_annotations + value. + + Shorthand Example: + + --remove-annotations=string,string + + JSON Example: + + --remove-annotations=["string"] + + File Example: + + --remove-annotations=path_to_file.(yaml|json) Principal access boundary policy details + --clear-details + Set googleIamV3betaPrincipalAccessBoundaryPolicy.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. @@ -162,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: @@ -202,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: @@ -247,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/beta/iam/workforce-pools/providers/create-oidc b/gcloud/beta/iam/workforce-pools/providers/create-oidc index e01d8cc61..ca39e2d7a 100644 --- a/gcloud/beta/iam/workforce-pools/providers/create-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/create-oidc @@ -12,7 +12,7 @@ SYNOPSIS : --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]) [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--client-secret-value=CLIENT_SECRET_VALUE] [--description=DESCRIPTION] - [--disabled] [--display-name=DISPLAY_NAME] + [--detailed-audit-logging] [--disabled] [--display-name=DISPLAY_NAME] [--jwk-json-path=PATH_TO_FILE] [--extra-attributes-client-id=EXTRA_ATTRIBUTES_CLIENT_ID --extra-attributes-client-secret-value=EXTRA_ATTRIBUTES_CLIENT_SECRET_VALUE --extra-attributes-issuer-uri=EXTRA_ATTRIBUTES_ISSUER_URI --extra-attributes-type=EXTRA_ATTRIBUTES_TYPE : --extra-attributes-filter=EXTRA_ATTRIBUTES_FILTER] @@ -240,6 +240,11 @@ OPTIONAL FLAGS A description for the workforce pool provider. Cannot exceed 256 characters in length. + --detailed-audit-logging + Enables detailed audit logging for this provider, which populates + additional debug information in STS Cloud Audit Logs. Specify + --no-detailed-audit-logging to disable it. + --disabled Disables the workforce pool provider. You cannot use a disabled provider to perform new token exchanges or sign-ins. However, existing diff --git a/gcloud/beta/iam/workforce-pools/providers/update-oidc b/gcloud/beta/iam/workforce-pools/providers/update-oidc index a28e25ecc..78264c09b 100644 --- a/gcloud/beta/iam/workforce-pools/providers/update-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/update-oidc @@ -7,8 +7,9 @@ SYNOPSIS (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL) [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--attribute-mapping=[KEY=VALUE,...]] [--client-id=CLIENT_ID] - [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] - [--issuer-uri=ISSUER_URI] [--jwk-json-path=PATH_TO_FILE] + [--description=DESCRIPTION] [--detailed-audit-logging] [--disabled] + [--display-name=DISPLAY_NAME] [--issuer-uri=ISSUER_URI] + [--jwk-json-path=PATH_TO_FILE] [--web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]] [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] @@ -187,6 +188,11 @@ FLAGS A description for the workforce pool provider. Cannot exceed 256 characters in length. + --detailed-audit-logging + Enables detailed audit logging for this provider, which populates + additional debug information in STS Cloud Audit Logs. Specify + --no-detailed-audit-logging to disable it. + --disabled Disables the workforce pool provider. You cannot use a disabled provider to perform new token exchanges or sign-ins. However, existing diff --git a/gcloud/beta/iap/settings/get b/gcloud/beta/iap/settings/get index e8249fed3..39a6c69de 100644 --- a/gcloud/beta/iap/settings/get +++ b/gcloud/beta/iap/settings/get @@ -80,6 +80,18 @@ EXAMPLES --resource-type=forwarding-rule --service=SERVICE_ID \ --region=REGION_ID + To get the IAP setting for all Cloud Run services within a region of a + project, run: + + $ gcloud beta iap settings get --project=PROJECT_ID \ + --resource-type=cloud-run --region=REGION_ID + + To get the IAP setting for a Cloud Run service within a project, run: + + $ gcloud beta iap settings get --project=PROJECT_ID \ + --resource-type=cloud-run --region=REGION_ID \ + --service=SERVICE_ID + FLAGS --folder=FOLDER Folder ID. diff --git a/gcloud/beta/iap/settings/set b/gcloud/beta/iap/settings/set index c149b0a4f..3cdf9a15c 100644 --- a/gcloud/beta/iap/settings/set +++ b/gcloud/beta/iap/settings/set @@ -15,72 +15,84 @@ EXAMPLES To set the IAP setting for the resources within an organization, run: $ gcloud beta iap settings set iap_settings.yaml \ - --organization=ORGANIZATION_ID + --organization=ORGANIZATION_ID - To set the IAP setting for the resources within a folder, run: + To set the IAP setting for the resources within a folder, run: $ gcloud beta iap settings set iap_settings.yaml --folder=FOLDER_ID - To set the IAP setting for the resources within a project, run: + To set the IAP setting for the resources within a project, run: $ gcloud beta iap settings set iap_settings.yaml --project=PROJECT_ID - To set the IAP setting for web type resources within a project, run: + To set the IAP setting for web type resources within a project, run: $ gcloud beta iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=iap_web + --project=PROJECT_ID --resource-type=iap_web - To set the IAP setting for all app engine services within a project, run: + To set the IAP setting for all app engine services within a project, run: $ gcloud beta iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=app-engine + --project=PROJECT_ID --resource-type=app-engine - To set the IAP setting for an app engine service within a project, run: + To set the IAP setting for an app engine service within a project, run: $ gcloud beta iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=app-engine \ - --service=SERVICE_ID + --project=PROJECT_ID --resource-type=app-engine \ + --service=SERVICE_ID - To set the IAP setting for an app engine service version within a project, - run: + To set the IAP setting for an app engine service version within a project, run: $ gcloud beta iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=app-engine \ - --service=SERVICE_ID --version=VERSION_ID + --project=PROJECT_ID --resource-type=app-engine \ + --service=SERVICE_ID --version=VERSION_ID - To set the IAP setting for all backend services within a project, run: + To set the IAP setting for all backend services within a project, run: $ gcloud beta iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=backend-services + --project=PROJECT_ID --resource-type=backend-services - To set the IAP setting for a backend service within a project, run: + To set the IAP setting for a backend service within a project, run: $ gcloud beta iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=backend-services \ - --service=SERVICE_ID + --project=PROJECT_ID --resource-type=backend-services \ + --service=SERVICE_ID - To set the IAP setting for a region backend service within a project, run: + To set the IAP setting for a region backend service within a project, run: $ gcloud beta iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=backend-services \ - --service=SERVICE_ID --region=REGION_ID + --project=PROJECT_ID --resource-type=backend-services \ + --service=SERVICE_ID --region=REGION_ID - To set the IAP setting for all forwarding rule within a project, run: + To set the IAP setting for all forwarding rule within a project, run: $ gcloud beta iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=forwarding-rule + --project=PROJECT_ID --resource-type=forwarding-rule - To set the IAP setting for a forwarding rule within a project, run: + To set the IAP setting for a forwarding rule within a project, run: $ gcloud beta iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=forwarding-rule \ - --service=SERVICE_ID + --project=PROJECT_ID --resource-type=forwarding-rule \ + --service=SERVICE_ID - To set the IAP setting for a region forwarding rule within a project, run: + To set the IAP setting for a region forwarding rule within a project, run: $ gcloud beta iap settings set iap_settings.yaml \ - --project=PROJECT_ID --resource-type=forwarding-rule \ - --service=SERVICE_ID --region=REGION_ID + --project=PROJECT_ID --resource-type=forwarding-rule \ + --service=SERVICE_ID --region=REGION_ID + + To set the IAP setting for the all cloud run services within a region of a + project, run: + + $ gcloud beta iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=cloud-run \ + --region=REGION_ID + + To set the IAP setting for a cloud run service within a project, run: + + $ gcloud beta iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=cloud-run \ + --region=REGION_ID --service=SERVICE_ID POSITIONAL ARGUMENTS SETTING_FILE diff --git a/gcloud/beta/kms/keys/create b/gcloud/beta/kms/keys/create index 3a09f2075..924ebb7f6 100644 --- a/gcloud/beta/kms/keys/create +++ b/gcloud/beta/kms/keys/create @@ -204,7 +204,8 @@ OPTIONAL FLAGS aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, ec-sign-p384-sha384, ec-sign-secp256k1-sha256, external-symmetric-encryption, google-symmetric-encryption, hmac-sha1, - hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, pq-sign-ml-dsa-65, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + pq-sign-hash-slh-dsa-sha2-128s-sha256, pq-sign-ml-dsa-65, pq-sign-slh-dsa-sha2-128s, rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, diff --git a/gcloud/beta/kms/keys/update b/gcloud/beta/kms/keys/update index 41087a343..33936e115 100644 --- a/gcloud/beta/kms/keys/update +++ b/gcloud/beta/kms/keys/update @@ -175,7 +175,8 @@ FLAGS aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, ec-sign-p384-sha384, ec-sign-secp256k1-sha256, external-symmetric-encryption, google-symmetric-encryption, hmac-sha1, - hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, pq-sign-ml-dsa-65, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + pq-sign-hash-slh-dsa-sha2-128s-sha256, pq-sign-ml-dsa-65, pq-sign-slh-dsa-sha2-128s, rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, diff --git a/gcloud/beta/kms/keys/versions/import b/gcloud/beta/kms/keys/versions/import index 5d8ec9ecb..1637db9f0 100644 --- a/gcloud/beta/kms/keys/versions/import +++ b/gcloud/beta/kms/keys/versions/import @@ -34,7 +34,8 @@ REQUIRED FLAGS aes-128-cbc, aes-128-ctr, aes-128-gcm, aes-256-cbc, aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, ec-sign-p384-sha384, ec-sign-secp256k1-sha256, google-symmetric-encryption, hmac-sha1, - hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, pq-sign-ml-dsa-65, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + pq-sign-hash-slh-dsa-sha2-128s-sha256, pq-sign-ml-dsa-65, pq-sign-slh-dsa-sha2-128s, rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, diff --git a/gcloud/beta/logging/logs/delete b/gcloud/beta/logging/logs/delete index 433abb3d9..a28d6e5cc 100644 --- a/gcloud/beta/logging/logs/delete +++ b/gcloud/beta/logging/logs/delete @@ -1,17 +1,17 @@ NAME gcloud beta logging logs delete - delete all entries from a log in the - _Default log bucket + global _Default log bucket SYNOPSIS gcloud beta logging logs delete LOG_NAME [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete all entries from a log in the _Default log bucket. With no - entries, the log will not appear in the list of your project's logs. - However, you can write new entries to the log. + (BETA) Delete all entries from a log in the global _Default log bucket. + With no entries, the log will not appear in the list of your project's + logs. However, you can write new entries to the log. EXAMPLES - To delete all entries from log 'my-log' in the _Default log bucket: + To delete all entries from log 'my-log' in the global _Default log bucket: $ gcloud beta logging logs delete my-log diff --git a/gcloud/beta/logging/logs/help b/gcloud/beta/logging/logs/help index 5f5cb434e..174b8bf31 100644 --- a/gcloud/beta/logging/logs/help +++ b/gcloud/beta/logging/logs/help @@ -16,7 +16,7 @@ COMMANDS COMMAND is one of the following: delete - (BETA) Delete all entries from a log in the _Default log bucket. + (BETA) Delete all entries from a log in the global _Default log bucket. list (BETA) List your project's logs. diff --git a/gcloud/beta/logging/operations/list b/gcloud/beta/logging/operations/list index 3755ff9f6..12f953d63 100644 --- a/gcloud/beta/logging/operations/list +++ b/gcloud/beta/logging/operations/list @@ -10,15 +10,37 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Return a list of long running operation details in given LOCATION. - The operations were scheduled by other gcloud commands. For example: a - copy_log_entries operation scheduled by command: gcloud alpha logging - operations copy BUCKET_ID DESTINATION --location=LOCATION. Note: while - listing the operations, the request_type must be specified in filter. - Example: --operation-filter=request_type=CopyLogEntries, Supported - operation types are: CopyLogEntries, CreateBucket and UpdateBucket. Other - supported filter expression are: operation_start_time, - operation_finish_time and operation_state. + (BETA) Return a list of long running operations in the given LOCATION. The + operations were scheduled by other gcloud commands. + + For example, a CopyLogEntries operation may be scheduled by the command: + gcloud logging copy BUCKET_ID DESTINATION --location=LOCATION. + + The --operation-filter flag is required and must specify the request_type. + Supported request types include but are not limited to: CopyLogEntries, + CreateBucket and UpdateBucket. + + Additional supported filter expressions include: operation_start_time, + operation_finish_time and operation_state. These can be combined with the + case-sensitive keyword AND between them. + + For operation_start_time and operation_end_time, the operators >=, >, <=, + and < are supported. + + Timestamps must be in either RFC3339 or ISO8601 formats. If the timestamp + contains a time value, then it must be quoted. For examples: + "YYYY-MM-DDTHH:MM:SSZ", "YYYY-MM-DDTHH:MM:SS.mmmZ", "YY-MM-DD", + "YYYY-MM-DDTHH:MM:SS-0000", "YYYY-MM-DDTHH:MM+0000", "YYYY-MM-DD", + YYYY-MM-DD, YY-MM-DD, etc. + + The operation_state filter expression can be used to filter for operations + that are in a specific state. The value can be one of the following: + SCHEDULED, WAITING_FOR_PRECONDITIONS, RUNNING, SUCCESS, FAILURE, CANCELLED, + PENDING. + + For operation_state, the operators = and != are supported. + + Other filter options are not supported. EXAMPLES To list CopyLogEntries operations, run: @@ -39,17 +61,17 @@ EXAMPLES --operation-filter='request_type=CopyLogEntries AND operation_finish_time<="2023-11-20T00:00:00Z"' - To list CopyLogEntries operations that have a specified state, run: + To list CopyLogEntries operations that completed successfully, run: $ gcloud beta logging operations list --location=LOCATION \ --operation-filter='request_type=CopyLogEntries AND - operation_state=STATE' + operation_state=SUCCESS' - To list CopyLogEntries operations that don't have a specified state, run: + To list CopyLogEntries operations that have not failed, run: $ gcloud beta logging operations list --location=LOCATION \ --operation-filter='request_type=CopyLogEntries AND - operation_state!=STATE' + operation_state!=FAILURE' REQUIRED FLAGS --location=LOCATION diff --git a/gcloud/beta/managed-kafka/help b/gcloud/beta/managed-kafka/help index ebc7dde99..2f3d1357f 100644 --- a/gcloud/beta/managed-kafka/help +++ b/gcloud/beta/managed-kafka/help @@ -29,6 +29,9 @@ GROUPS operations (BETA) View Managed Service for Apache Kafka operations. + schema-registries + (BETA) Administer Managed Service for Apache Kafka schema-registries. + topics (BETA) Administer Managed Service for Apache Kafka topics. diff --git a/gcloud/beta/managed-kafka/schema-registries/create b/gcloud/beta/managed-kafka/schema-registries/create new file mode 100644 index 000000000..286578276 --- /dev/null +++ b/gcloud/beta/managed-kafka/schema-registries/create @@ -0,0 +1,71 @@ +NAME + gcloud beta managed-kafka schema-registries create - create a Managed + Service for Apache Kafka schema registry + +SYNOPSIS + gcloud beta managed-kafka schema-registries create + (SCHEMA_REGISTRY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Managed Service for Apache Kafka schema registry. + +EXAMPLES + To create a schema registry, run the following: + + $ gcloud beta managed-kafka schema-registries create \ + myschemaregistry --location=us-central1 + +POSITIONAL ARGUMENTS + Schema registry resource - Identifies the schema registry for which the + command runs. 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 schema_registry 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. + + SCHEMA_REGISTRY + ID of the schema_registry or fully qualified identifier for the + schema_registry. + + To set the schema_registry attribute: + ▸ provide the argument schema_registry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument schema_registry 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 managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha managed-kafka schema-registries create + diff --git a/gcloud/beta/managed-kafka/schema-registries/delete b/gcloud/beta/managed-kafka/schema-registries/delete new file mode 100644 index 000000000..9c335c3a9 --- /dev/null +++ b/gcloud/beta/managed-kafka/schema-registries/delete @@ -0,0 +1,72 @@ +NAME + gcloud beta managed-kafka schema-registries delete - delete a Managed + Service for Apache Kafka schema registry + +SYNOPSIS + gcloud beta managed-kafka schema-registries delete + (SCHEMA_REGISTRY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Managed Service for Apache Kafka schema registry. + +EXAMPLES + To delete a schema registry named myschemaregistry located in us-central1, + run the following: + + $ gcloud beta managed-kafka schema-registries delete \ + myschemaregistry --location=us-central1 + +POSITIONAL ARGUMENTS + Schema registry resource - Identifies the schema registry for deletion. + 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 schema_registry 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. + + SCHEMA_REGISTRY + ID of the schema_registry or fully qualified identifier for the + schema_registry. + + To set the schema_registry attribute: + ▸ provide the argument schema_registry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument schema_registry 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 managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha managed-kafka schema-registries delete + diff --git a/gcloud/beta/managed-kafka/schema-registries/describe b/gcloud/beta/managed-kafka/schema-registries/describe new file mode 100644 index 000000000..d6ecb1886 --- /dev/null +++ b/gcloud/beta/managed-kafka/schema-registries/describe @@ -0,0 +1,64 @@ +NAME + gcloud beta managed-kafka schema-registries describe - describe a schema + registry with all of its fields + +SYNOPSIS + gcloud beta managed-kafka schema-registries describe + (SCHEMA_REGISTRY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + Describe the schema registry with all of its fields: + + $ gcloud beta managed-kafka schema-registries describe \ + --project=PROJECT_ID --location=LOCATION_ID \ + --schema_registry=SCHEMA_REGISTRY_ID + +POSITIONAL ARGUMENTS + Schema registry resource - The schema registry to create. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument schema_registry 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. + + SCHEMA_REGISTRY + ID of the schema_registry or fully qualified identifier for the + schema_registry. + + To set the schema_registry attribute: + ▸ provide the argument schema_registry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument schema_registry 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. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha managed-kafka schema-registries describe + diff --git a/gcloud/beta/managed-kafka/schema-registries/help b/gcloud/beta/managed-kafka/schema-registries/help new file mode 100644 index 000000000..5221269ca --- /dev/null +++ b/gcloud/beta/managed-kafka/schema-registries/help @@ -0,0 +1,37 @@ +NAME + gcloud beta managed-kafka schema-registries - administer Managed Service + for Apache Kafka schema-registries + +SYNOPSIS + gcloud beta managed-kafka schema-registries COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Administer Managed Service for Apache Kafka schema-registries. + +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 Managed Service for Apache Kafka schema registry. + + delete + (BETA) Delete a Managed Service for Apache Kafka schema registry. + + describe + (BETA) Describe a schema registry with all of its fields. + + list + (BETA) List all Managed Service for Apache Kafka schema registries in a + given location. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha managed-kafka schema-registries + diff --git a/gcloud/beta/healthcare/annotation-stores/get-iam-policy b/gcloud/beta/managed-kafka/schema-registries/list similarity index 52% rename from gcloud/beta/healthcare/annotation-stores/get-iam-policy rename to gcloud/beta/managed-kafka/schema-registries/list index 633cc9409..cffbf15ed 100644 --- a/gcloud/beta/healthcare/annotation-stores/get-iam-policy +++ b/gcloud/beta/managed-kafka/schema-registries/list @@ -1,63 +1,43 @@ NAME - gcloud beta healthcare annotation-stores get-iam-policy - retrieve the IAM - policy for a Cloud Healthcare API annotation store + gcloud beta managed-kafka schema-registries list - list all Managed Service + for Apache Kafka schema registries in a given location SYNOPSIS - gcloud beta healthcare annotation-stores get-iam-policy - (ANNOTATION_STORE : --dataset=DATASET --location=LOCATION) + gcloud beta managed-kafka schema-registries list --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Retrieve the IAM policy for a Cloud Healthcare API annotation store. + (BETA) List all Managed Service for Apache Kafka schema registries in a + given location. To specify the maximum number of clusters to list, use the + --limit flag. EXAMPLES - To print the IAM policy for the annotation store 'test-annotation-store', - run: + To list all schema registries in a given location, such as us-central1, run + the following: - $ gcloud beta healthcare annotation-stores get-iam-policy \ - test-annotation-store --dataset=test-dataset + $ gcloud beta managed-kafka schema-registries list \ + --location=us-central1 -POSITIONAL ARGUMENTS - AnnotationStore resource - Cloud Healthcare API annotation store whose IAM - policy to fetch. 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. +REQUIRED FLAGS + Location resource - Identifies the region which contains all the schema + registries to be listed. 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 annotation_store on the command line with a - fully specified name; + ◆ 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. - ANNOTATION_STORE - ID of the annotationStore or fully qualified identifier for the - annotationStore. - - To set the annotation_store attribute: - ▸ provide the argument annotation_store on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --dataset=DATASET - Cloud Healthcare dataset. - - To set the dataset attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --dataset on the command line. - --location=LOCATION - Google Cloud location. + ID of the location or fully qualified identifier for the location. To set the location attribute: - ▸ provide the argument annotation_store on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. + ▸ provide the argument --location on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -94,12 +74,13 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the healthcare/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs NOTES This command is currently in beta and might change without notice. This variant is also available: - $ gcloud alpha healthcare annotation-stores get-iam-policy + $ gcloud alpha managed-kafka schema-registries list diff --git a/gcloud/beta/memorystore/instances/update b/gcloud/beta/memorystore/instances/update index ffd171433..77b4782b6 100644 --- a/gcloud/beta/memorystore/instances/update +++ b/gcloud/beta/memorystore/instances/update @@ -32,10 +32,10 @@ SYNOPSIS [--engine-configs=[ENGINE_CONFIGS,...] | --update-engine-configs=[UPDATE_ENGINE_CONFIGS,...] --clear-engine-configs - | --remove-engine-configs=[__REMOVE_ENGINE_CONFIGS,...]] + | --remove-engine-configs=REMOVE_ENGINE_CONFIGS] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update the configuration of a Memorystore instance. @@ -754,8 +754,21 @@ FLAGS --clear-engine-configs Clear engine_configs value and set to empty map. - --remove-engine-configs=[__REMOVE_ENGINE_CONFIGS,...] - Remove existing value from map engine_configs. + --remove-engine-configs=REMOVE_ENGINE_CONFIGS + Remove existing value from map engine_configs. Sets + remove_engine_configs value. + + Shorthand Example: + + --remove-engine-configs=string,string + + JSON Example: + + --remove-engine-configs=["string"] + + File Example: + + --remove-engine-configs=path_to_file.(yaml|json) Update labels. @@ -813,8 +826,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/netapp/backup-vaults/create b/gcloud/beta/netapp/backup-vaults/create index 46c308a7e..db14b131b 100644 --- a/gcloud/beta/netapp/backup-vaults/create +++ b/gcloud/beta/netapp/backup-vaults/create @@ -5,9 +5,14 @@ NAME SYNOPSIS gcloud beta netapp backup-vaults create (BACKUP_VAULT : --location=LOCATION) [--async] - [--backup-region=BACKUP_REGION] [--backup-vault-type=BACKUP_VAULT_TYPE] - [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + [--backup-region=BACKUP_REGION] + [--backup-retention-policy=[backup-minimum-enforced-retention-days=BACKUP-MINIMUM-ENFORCED-RETENTION-DAYS], + [daily-backup-immutable=DAILY-BACKUP-IMMUTABLE], + [manual-backup-immutable=MANUAL-BACKUP-IMMUTABLE], + [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 ...] DESCRIPTION (BETA) Create a Cloud NetApp Backup Vault. @@ -60,6 +65,14 @@ FLAGS --backup-region=BACKUP_REGION String indicating backup location for the Backup Vault + --backup-retention-policy=[backup-minimum-enforced-retention-days=BACKUP-MINIMUM-ENFORCED-RETENTION-DAYS],[daily-backup-immutable=DAILY-BACKUP-IMMUTABLE],[manual-backup-immutable=MANUAL-BACKUP-IMMUTABLE],[monthly-backup-immutable=MONTHLY-BACKUP-IMMUTABLE],[weekly-backup-immutable=WEEKLY-BACKUP-IMMUTABLE] + Backup Retention Policy of the Backup Vault. + + Backup Retention Policy allows you to configure the retention policy + for backups created within this vault. It consists of several fields + that govern how long backups are kept and what type of backups are + immutable. + --backup-vault-type=BACKUP_VAULT_TYPE String indicating the type of backup vault. The supported values are: 'IN_REGION','CROSS_REGION' diff --git a/gcloud/beta/netapp/backup-vaults/update b/gcloud/beta/netapp/backup-vaults/update index 6a4668c27..c52624aa6 100644 --- a/gcloud/beta/netapp/backup-vaults/update +++ b/gcloud/beta/netapp/backup-vaults/update @@ -5,6 +5,11 @@ NAME SYNOPSIS gcloud beta netapp backup-vaults update (BACKUP_VAULT : --location=LOCATION) [--async] + [--backup-retention-policy=[backup-minimum-enforced-retention-days=BACKUP-MINIMUM-ENFORCED-RETENTION-DAYS], + [daily-backup-immutable=DAILY-BACKUP-IMMUTABLE], + [manual-backup-immutable=MANUAL-BACKUP-IMMUTABLE], + [monthly-backup-immutable=MONTHLY-BACKUP-IMMUTABLE], + [weekly-backup-immutable=WEEKLY-BACKUP-IMMUTABLE]] [--description=DESCRIPTION] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -63,6 +68,14 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --backup-retention-policy=[backup-minimum-enforced-retention-days=BACKUP-MINIMUM-ENFORCED-RETENTION-DAYS],[daily-backup-immutable=DAILY-BACKUP-IMMUTABLE],[manual-backup-immutable=MANUAL-BACKUP-IMMUTABLE],[monthly-backup-immutable=MONTHLY-BACKUP-IMMUTABLE],[weekly-backup-immutable=WEEKLY-BACKUP-IMMUTABLE] + Backup Retention Policy of the Backup Vault. + + Backup Retention Policy allows you to configure the retention policy + for backups created within this vault. It consists of several fields + that govern how long backups are kept and what type of backups are + immutable. + --description=DESCRIPTION A description of the Cloud NetApp Backup Vault diff --git a/gcloud/beta/netapp/storage-pools/create b/gcloud/beta/netapp/storage-pools/create index 473969db2..ff379ac78 100644 --- a/gcloud/beta/netapp/storage-pools/create +++ b/gcloud/beta/netapp/storage-pools/create @@ -9,7 +9,9 @@ SYNOPSIS --service-level=SERVICE_LEVEL [--active-directory=ACTIVE_DIRECTORY] [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] [--custom-performance-enabled=CUSTOM_PERFORMANCE_ENABLED] - [--description=DESCRIPTION] [--enable-ldap=ENABLE_LDAP] + [--description=DESCRIPTION] + [--enable-hot-tier-auto-resize=ENABLE_HOT_TIER_AUTO_RESIZE] + [--enable-ldap=ENABLE_LDAP] [--hot-tier-size=HOT_TIER_SIZE] [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] [--replica-zone=REPLICA_ZONE] [--total-iops=TOTAL_IOPS] [--total-throughput=TOTAL_THROUGHPUT] [--zone=ZONE] @@ -155,10 +157,18 @@ OPTIONAL FLAGS --description=DESCRIPTION A description of the Cloud NetApp Storage Pool + --enable-hot-tier-auto-resize=ENABLE_HOT_TIER_AUTO_RESIZE + Boolean flag indicating whether Storage Pool is allowed to use hot tier + auto resize + --enable-ldap=ENABLE_LDAP Boolean flag indicating whether Storage Pool is a NFS LDAP Storage Pool or not + --hot-tier-size=HOT_TIER_SIZE + The hot tier size of the Storage Pool in GiB/s units. If no throughput + unit is specified, GiB/s is assumed. + Kms config resource - The KMS config to attach to the Storage Pool. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. diff --git a/gcloud/beta/netapp/storage-pools/update b/gcloud/beta/netapp/storage-pools/update index 9498ddeee..b77e30118 100644 --- a/gcloud/beta/netapp/storage-pools/update +++ b/gcloud/beta/netapp/storage-pools/update @@ -8,10 +8,11 @@ SYNOPSIS [--active-directory=ACTIVE_DIRECTORY] [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] [--capacity=CAPACITY] [--description=DESCRIPTION] - [--replica-zone=REPLICA_ZONE] [--total-iops=TOTAL_IOPS] - [--total-throughput=TOTAL_THROUGHPUT] [--update-labels=[KEY=VALUE,...]] - [--zone=ZONE] [--clear-labels | --remove-labels=[KEY,...]] - [GCLOUD_WIDE_FLAG ...] + [--enable-hot-tier-auto-resize=ENABLE_HOT_TIER_AUTO_RESIZE] + [--hot-tier-size=HOT_TIER_SIZE] [--replica-zone=REPLICA_ZONE] + [--total-iops=TOTAL_IOPS] [--total-throughput=TOTAL_THROUGHPUT] + [--update-labels=[KEY=VALUE,...]] [--zone=ZONE] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Updates a Storage Pool with given arguments @@ -96,6 +97,14 @@ FLAGS --description=DESCRIPTION A description of the Cloud NetApp Storage Pool + --enable-hot-tier-auto-resize=ENABLE_HOT_TIER_AUTO_RESIZE + Boolean flag indicating whether Storage Pool is allowed to use hot tier + auto resize + + --hot-tier-size=HOT_TIER_SIZE + The hot tier size of the Storage Pool in GiB/s units. If no throughput + unit is specified, GiB/s is assumed. + --replica-zone=REPLICA_ZONE String indicating replica zone for the Storage Pool diff --git a/gcloud/beta/network-connectivity/help b/gcloud/beta/network-connectivity/help index 3a75f706e..4f0dd6fae 100644 --- a/gcloud/beta/network-connectivity/help +++ b/gcloud/beta/network-connectivity/help @@ -1,12 +1,11 @@ NAME - gcloud beta network-connectivity - manage Network Connectivity Center - resources + gcloud beta network-connectivity - manage Network Connectivity resources SYNOPSIS gcloud beta network-connectivity GROUP [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Manage Network Connectivity Center resources. + (BETA) Manage Network Connectivity resources. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/create b/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/create new file mode 100644 index 000000000..bd0d8ba8a --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/create @@ -0,0 +1,100 @@ +NAME + gcloud beta network-connectivity spokes gateways advertised-routes create - + create a new gateway advertised route + +SYNOPSIS + gcloud beta network-connectivity spokes gateways advertised-routes create + (GATEWAY_ADVERTISED_ROUTE : --region=REGION --spoke=SPOKE) + --advertise-to-hub --ip-range=IP_RANGE [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--priority=PRIORITY] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new gateway advertised route with the given name. + +EXAMPLES + Create an advertised route with name my-route for gateway spoke my-gateway + in region us-central1: + + $ gcloud beta network-connectivity spokes gateways \ + advertised-routes create my-route --spoke=my-gateway \ + --region=us-central1 --ip-range=10.0.1.0/24 + +POSITIONAL ARGUMENTS + GatewayAdvertisedRoute resource - Name of the gateway advertised route to + be created. 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 gateway_advertised_route 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. + + GATEWAY_ADVERTISED_ROUTE + ID of the gatewayAdvertisedRoute or fully qualified identifier for + the gatewayAdvertisedRoute. + + To set the gateway_advertised_route attribute: + ▸ provide the argument gateway_advertised_route on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The location Id. + + To set the region attribute: + ▸ provide the argument gateway_advertised_route on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + + --spoke=SPOKE + Id of the spoke. + + To set the spoke attribute: + ▸ provide the argument gateway_advertised_route on the command line + with a fully specified name; + ▸ provide the argument --spoke on the command line. + +REQUIRED FLAGS + --advertise-to-hub + The gateway should advertise this route toward the hub. + + --ip-range=IP_RANGE + Advertise this IP range. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description of the advertised route to be created. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + --priority=PRIORITY + This route's priority. Must be between 0 and 65335. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1beta API. The full + documentation for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/delete b/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/delete new file mode 100644 index 000000000..0b64946fc --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/delete @@ -0,0 +1,82 @@ +NAME + gcloud beta network-connectivity spokes gateways advertised-routes delete - + delete a gateway advertised route + +SYNOPSIS + gcloud beta network-connectivity spokes gateways advertised-routes delete + (GATEWAY_ADVERTISED_ROUTE : --region=REGION --spoke=SPOKE) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete the specified advertised route for a gateway spoke. + +EXAMPLES + To delete an advertised route with name my-route for spoke my-spoke in + region us-central1, run: + + $ gcloud beta network-connectivity spokes gateways \ + advertised-routes delete my-route --region=us-central1 \ + --spoke=my-spoke + +POSITIONAL ARGUMENTS + GatewayAdvertisedRoute resource - Name of the advertised route to be + deleted. The arguments in this group can be used to specify the attributes + of this resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument gateway_advertised_route 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. + + GATEWAY_ADVERTISED_ROUTE + ID of the gatewayAdvertisedRoute or fully qualified identifier for + the gatewayAdvertisedRoute. + + To set the gateway_advertised_route attribute: + ▸ provide the argument gateway_advertised_route on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The location Id. + + To set the region attribute: + ▸ provide the argument gateway_advertised_route on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + + --spoke=SPOKE + Id of the spoke. + + To set the spoke attribute: + ▸ provide the argument gateway_advertised_route on the command line + with a fully specified name; + ▸ provide the argument --spoke on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1beta API. The full + documentation for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/describe b/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/describe new file mode 100644 index 000000000..49216464c --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/describe @@ -0,0 +1,76 @@ +NAME + gcloud beta network-connectivity spokes gateways advertised-routes describe + - describe a gateway advertised route + +SYNOPSIS + gcloud beta network-connectivity spokes gateways advertised-routes describe + (GATEWAY_ADVERTISED_ROUTE : --region=REGION --spoke=SPOKE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Retrieve and display details about a gateway advertised route. + +EXAMPLES + To display details about a gateway advertised route named my-route, run: + + $ gcloud beta network-connectivity spokes gateways \ + advertised-routes describe my-route --region=us-central1 \ + --spoke=my-gateway + +POSITIONAL ARGUMENTS + GatewayAdvertisedRoute resource - Name of the gateway advertised route to + be described. 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 gateway_advertised_route 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. + + GATEWAY_ADVERTISED_ROUTE + ID of the gatewayAdvertisedRoute or fully qualified identifier for + the gatewayAdvertisedRoute. + + To set the gateway_advertised_route attribute: + ▸ provide the argument gateway_advertised_route on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The location Id. + + To set the region attribute: + ▸ provide the argument gateway_advertised_route on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + + --spoke=SPOKE + Id of the spoke. + + To set the spoke attribute: + ▸ provide the argument gateway_advertised_route on the command line + with a fully specified name; + ▸ provide the argument --spoke 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 networkconnectivity/v1beta API. The full + documentation for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/help b/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/help new file mode 100644 index 000000000..1d9c7f919 --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/help @@ -0,0 +1,34 @@ +NAME + gcloud beta network-connectivity spokes gateways advertised-routes - manage + gateway advertised routes + +SYNOPSIS + gcloud beta network-connectivity spokes gateways advertised-routes COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage gateway advertised routes. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a new gateway advertised route. + + delete + (BETA) Delete a gateway advertised route. + + describe + (BETA) Describe a gateway advertised route. + + list + (BETA) List gateway advertised routes. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/list b/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/list new file mode 100644 index 000000000..5797ccb82 --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/gateways/advertised-routes/list @@ -0,0 +1,105 @@ +NAME + gcloud beta network-connectivity spokes gateways advertised-routes list - + list gateway advertised routes + +SYNOPSIS + gcloud beta network-connectivity spokes gateways advertised-routes list + [--region=REGION --spoke=SPOKE] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Retrieve and display a list of advertised routes for the specified + gateway spoke. + +EXAMPLES + To list all advertised routes across all gateway spokes, run: + + $ gcloud beta network-connectivity spokes gateways \ + advertised-routes list --region=- --spoke=- + + To list advertised routes for all gateway spokes in region us-central1, + run: + + $ gcloud beta network-connectivity spokes gateways \ + advertised-routes list --region=us-central1 + + To list all advertised routes for spoke my-gateway, run: + + $ gcloud beta network-connectivity spokes gateways \ + advertised-routes list --region=us-central1 --spoke=my-gateway + +FLAGS + Spoke resource - A gateway spoke. Use this flag to filter the list of + advertised routes to a specific spoke. Use ``-`` to specify all spokes. + 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 --spoke on the command line with a fully + specified name; + ◆ if spoke is empty, will use the wildcard '-' to list all spokes with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + The location ID. + + To set the region attribute: + ▸ provide the argument --spoke on the command line with a fully + specified name; + ▸ if spoke is empty, will use the wildcard '-' to list all spokes + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ use default wildcard location . + + --spoke=SPOKE + ID of the spoke or fully qualified identifier for the spoke. + + To set the spoke attribute: + ▸ provide the argument --spoke on the command line; + ▸ if spoke is empty, will use the wildcard '-' to list all spokes. + +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 networkconnectivity/v1beta API. The full + documentation for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-connectivity/spokes/gateways/create b/gcloud/beta/network-connectivity/spokes/gateways/create new file mode 100644 index 000000000..0187cd9cd --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/gateways/create @@ -0,0 +1,115 @@ +NAME + gcloud beta network-connectivity spokes gateways create - create a new + Gateway spoke + +SYNOPSIS + gcloud beta network-connectivity spokes gateways create SPOKE + --capacity=CAPACITY --group=GROUP --hub=HUB + --ip-range-reservations=[CIDR_RANGE,...] --region=REGION [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--landing-network=LANDING_NETWORK] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new Gateway spoke. + +EXAMPLES + To create a Gateway spoke named myspoke in us-central1, with a capacity of + 10 Gbps and IP range reservations of 10.1.1.0/24 + + $ gcloud beta network-connectivity spokes gateways create myspoke \ + --hub=my-hub --region us-central1 --group gateways \ + --capacity 10g --ip-range-reservations 10.1.1.0/24 + + To create a Gateway spoke named myspoke in us-central1, with a capacity of + 10 Gbps, IP range reservations of 10.1.1.0/24 and 10.1.2.0/24, and a + landing network of my-vpc, run: + + $ gcloud beta network-connectivity spokes gateways create myspoke \ + --hub=my-hub --region us-central1 --group gateways \ + --capacity 10g --ip-range-reservations 10.1.1.0/24,10.1.2.0/24 \ + --landing-network my-vpc + +POSITIONAL ARGUMENTS + Spoke resource - Name of the spoke to create. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --region on the command line. + + This must be specified. + + SPOKE + ID of the spoke or fully qualified identifier for the spoke. + + To set the spoke attribute: + ▸ provide the argument spoke on the command line. + +REQUIRED FLAGS + --capacity=CAPACITY + Set the capacity of the gateway in Gbps. CAPACITY must be one of: + + 100g + Gateway will have capacity of 100 Gbps + 10g + Gateway will have capacity of 10 Gbps + 1g + Gateway will have capacity of 1 Gbps + + --group=GROUP + Group that the spoke will be part of. The group must already exist. + + --hub=HUB + Hub that the spoke will attach to. The hub must already exist. + + --ip-range-reservations=[CIDR_RANGE,...] + The IP range reservation for the spoke. + + --region=REGION + A Google Cloud region. To see the names of regions, see Viewing a list + of available regions + (https://cloud.google.com/compute/docs/regions-zones/viewing-regions-zones#viewing_a_list_of_available_regions). + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description of the spoke to create. + + --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. + + --landing-network=LANDING_NETWORK + The landing network for the spoke. The network must already exist. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-connectivity/spokes/gateways/help b/gcloud/beta/network-connectivity/spokes/gateways/help new file mode 100644 index 000000000..d251f182c --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/gateways/help @@ -0,0 +1,33 @@ +NAME + gcloud beta network-connectivity spokes gateways - manage Gateway spokes + +SYNOPSIS + gcloud beta network-connectivity spokes gateways GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Gateway spokes. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + advertised-routes + (BETA) Manage gateway advertised routes. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a new Gateway spoke. + + update + (BETA) Update a Gateway spoke. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-connectivity/spokes/gateways/update b/gcloud/beta/network-connectivity/spokes/gateways/update new file mode 100644 index 000000000..1cc7e7d4d --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/gateways/update @@ -0,0 +1,108 @@ +NAME + gcloud beta network-connectivity spokes gateways update - update a Gateway + spoke + +SYNOPSIS + gcloud beta network-connectivity spokes gateways update + (SPOKE : --region=REGION) [--async] [--capacity=CAPACITY] + [--description=DESCRIPTION] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the details of a Gateway spoke. + +EXAMPLES + To update the description of a Gateway spoke named my-spoke, run: + + $ gcloud beta network-connectivity spokes gateways update my-spoke \ + --region=us-central1 --description="new spoke description" + +POSITIONAL ARGUMENTS + Spoke resource - Name of the spoke 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 spoke 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. + + SPOKE + ID of the spoke or fully qualified identifier for the spoke. + + To set the spoke attribute: + ▸ provide the argument spoke on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The location Id. + + To set the region attribute: + ▸ provide the argument spoke on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --capacity=CAPACITY + New gateway capacity of the spoke. CAPACITY must be one of: 100g, 10g, + 1g. + + --description=DESCRIPTION + New description of the spoke. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta network-connectivity spokes gateways update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta network-connectivity spokes gateways update \ + --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1beta API. The full + documentation for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-connectivity/spokes/help b/gcloud/beta/network-connectivity/spokes/help index 76689176b..24b080869 100644 --- a/gcloud/beta/network-connectivity/spokes/help +++ b/gcloud/beta/network-connectivity/spokes/help @@ -17,6 +17,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + gateways + (BETA) Manage Gateway spokes. + linked-interconnect-attachments (BETA) Manage VLAN attachment spokes. diff --git a/gcloud/beta/network-management/vpc-flow-logs-configs/create b/gcloud/beta/network-management/vpc-flow-logs-configs/create index c0724d94b..b029ca03f 100644 --- a/gcloud/beta/network-management/vpc-flow-logs-configs/create +++ b/gcloud/beta/network-management/vpc-flow-logs-configs/create @@ -1,42 +1,36 @@ NAME gcloud beta network-management vpc-flow-logs-configs create - creates a new - VPC Flow Logs configuration in the specified project + VPC Flow Logs configuration in the specified organization SYNOPSIS gcloud beta network-management vpc-flow-logs-configs create - (VPC_FLOW_LOGS_CONFIG : --location=LOCATION) + (VPC_FLOW_LOGS_CONFIG + : --location=LOCATION --organization=ORGANIZATION) [--aggregation-interval=AGGREGATION_INTERVAL] [--async] + [--cross-project-metadata=CROSS_PROJECT_METADATA] [--description=DESCRIPTION] [--filter-expr=FILTER_EXPR] [--flow-sampling=FLOW_SAMPLING] [--labels=[LABELS,...]] [--metadata=METADATA] [--metadata-fields=[METADATA_FIELDS,...]] [--state=STATE] - [--interconnect-attachment=INTERCONNECT_ATTACHMENT - | --vpn-tunnel=VPN_TUNNEL] [GCLOUD_WIDE_FLAG ...] + [--interconnect-attachment=INTERCONNECT_ATTACHMENT | --network=NETWORK + | --subnet=SUBNET | --vpn-tunnel=VPN_TUNNEL] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Creates a new VPC Flow Logs configuration in the specified project. + (BETA) Creates a new VPC Flow Logs configuration in the specified + organization. EXAMPLES - To create a new VPC Flow Logs configuration my-config in project my-project - for a VLAN attachment for Cloud Interconnect, run: + To create a new VPC Flow Logs configuration my-config in organization + my-org-number, run: $ gcloud beta network-management vpc-flow-logs-configs create \ - my-config --location=global \ - --interconnect-attachment="projects/{project_id}/regions/{region\ - }/interconnectAttachments/{interconnect_attachment_id}" - - To create a new VPC Flow Logs configuration my-config in project my-project - for a Cloud VPN tunnel, run: - - $ gcloud beta network-management vpc-flow-logs-configs create \ - my-config --location=global \ - --vpn-tunnel="projects/{project_id}/regions/{region}/vpnTunnels/\ - {vpn_tunnel_id}" + my-config --location=global --organization= POSITIONAL ARGUMENTS VpcFlowLogsConfig resource - Identifier. Unique name of the configuration - using the form: + using one of the forms: projects/{project_id}/locations/global/vpcFlowLogsConfigs/{vpc_flow_logs_config_id} + organizations/{organization_id}/locations/global/vpcFlowLogsConfigs/{vpc_flow_logs_config_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. @@ -45,7 +39,10 @@ POSITIONAL ARGUMENTS ◆ provide the argument vpc_flow_logs_config on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: + [networkmanagement.organizations.locations.vpcFlowLogsConfigs, + networkmanagement.projects.locations.vpcFlowLogsConfigs]. This must be specified. @@ -67,6 +64,16 @@ POSITIONAL ARGUMENTS with a fully specified name; ▸ provide the argument --location on the command line. + --organization=ORGANIZATION + The organization id of the vpcFlowLogsConfig resource. + + To set the organization attribute: + ▸ provide the argument vpc_flow_logs_config on the command line + with a fully specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networkmanagement.organizations.locations.vpcFlowLogsConfigs]. + FLAGS Arguments for the aggregation interval. @@ -91,6 +98,22 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + Arguments for the cross project metadata. + + --cross-project-metadata=CROSS_PROJECT_METADATA + Determines whether to include cross project annotations in the logs. + This field is available only for organization configurations. If not + specified in org configs will be set to + CROSS_PROJECT_METADATA_ENABLED. CROSS_PROJECT_METADATA must be one + of: + + cross-project-metadata-disabled + When CROSS_PROJECT_METADATA_DISABLED, metadata from other + projects will not be included in the logs. + cross-project-metadata-enabled + When CROSS_PROJECT_METADATA_ENABLED, metadata from other projects + will be included in the logs. + Arguments for the description. --description=DESCRIPTION @@ -155,8 +178,9 @@ FLAGS --state=STATE The state of the VPC Flow Log configuration. Default value is - ENABLED. When creating a new configuration, it must be enabled. STATE - must be one of: + ENABLED. When creating a new configuration, it must be enabled. + Setting state=DISABLED will pause the log generation for this config. + STATE must be one of: disabled When DISABLED, this configuration will not generate logs. @@ -171,6 +195,15 @@ FLAGS Traffic will be logged from the Interconnect Attachment. Format: projects/{project_id}/regions/{region}/interconnectAttachments/{name} + --network=NETWORK + Traffic will be logged from VMs, VPN tunnels and Interconnect + Attachments within the network. Format: + projects/{project_id}/global/networks/{name} + + --subnet=SUBNET + Traffic will be logged from VMs within the subnetwork. Format: + projects/{project_id}/regions/{region}/subnetworks/{name} + --vpn-tunnel=VPN_TUNNEL Traffic will be logged from the VPN Tunnel. Format: projects/{project_id}/regions/{region}/vpnTunnels/{name} diff --git a/gcloud/beta/network-management/vpc-flow-logs-configs/delete b/gcloud/beta/network-management/vpc-flow-logs-configs/delete index 6804e93ce..a53ef75cb 100644 --- a/gcloud/beta/network-management/vpc-flow-logs-configs/delete +++ b/gcloud/beta/network-management/vpc-flow-logs-configs/delete @@ -4,22 +4,25 @@ NAME SYNOPSIS gcloud beta network-management vpc-flow-logs-configs delete - (VPC_FLOW_LOGS_CONFIG : --location=LOCATION) [--async] + (VPC_FLOW_LOGS_CONFIG + : --location=LOCATION --organization=ORGANIZATION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Deletes the specified VPC Flow Logs configuration. EXAMPLES - To delete a VPC Flow Logs configuration my-config, run: + To delete a VPC Flow Logs configuration my-config within the organization + my-org-number, run: $ gcloud beta network-management vpc-flow-logs-configs delete \ - my-config --location=global + my-config --location=global --organization= POSITIONAL ARGUMENTS - VpcFlowLogsConfig resource - VpcFlowLogsConfig resource name using the - form: + VpcFlowLogsConfig resource - VpcFlowLogsConfig resource name using one of + the form: projects/{project_id}/locations/global/vpcFlowLogsConfigs/{vpc_flow_logs_config} + organizations/{organization_id}/locations/global/vpcFlowLogsConfigs/{vpc_flow_logs_config} 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. @@ -28,7 +31,10 @@ POSITIONAL ARGUMENTS ◆ provide the argument vpc_flow_logs_config on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: + [networkmanagement.organizations.locations.vpcFlowLogsConfigs, + networkmanagement.projects.locations.vpcFlowLogsConfigs]. This must be specified. @@ -50,6 +56,16 @@ POSITIONAL ARGUMENTS with a fully specified name; ▸ provide the argument --location on the command line. + --organization=ORGANIZATION + The organization id of the vpcFlowLogsConfig resource. + + To set the organization attribute: + ▸ provide the argument vpc_flow_logs_config on the command line + with a fully specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networkmanagement.organizations.locations.vpcFlowLogsConfigs]. + FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/beta/network-management/vpc-flow-logs-configs/describe b/gcloud/beta/network-management/vpc-flow-logs-configs/describe index 5b7db24d5..6f63a7ff8 100644 --- a/gcloud/beta/network-management/vpc-flow-logs-configs/describe +++ b/gcloud/beta/network-management/vpc-flow-logs-configs/describe @@ -1,24 +1,29 @@ NAME gcloud beta network-management vpc-flow-logs-configs describe - describe - the details of a specific VPC Flow Logs configuration + the details of a specific VPC Flow Logs configuration for organization SYNOPSIS gcloud beta network-management vpc-flow-logs-configs describe - (VPC_FLOW_LOGS_CONFIG : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + (VPC_FLOW_LOGS_CONFIG + : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describes the details of a specific VPC Flow Logs configuration. + (BETA) Describes the details of a specific VPC Flow Logs configuration for + organization. EXAMPLES - To get the details of a VPC Flow Logs configuration my-config, run: + To get the details of a VPC Flow Logs configuration my-config, within the + organization my-org-number, run: $ gcloud beta network-management vpc-flow-logs-configs describe \ - my-config --location=global + my-config --location=global --organization= POSITIONAL ARGUMENTS VpcFlowLogsConfig resource - VpcFlowLogsConfig resource name using the form: projects/{project_id}/locations/global/vpcFlowLogsConfigs/{vpc_flow_logs_config} + organizations/{organization_id}/locations/global/vpcFlowLogsConfigs/{vpc_flow_logs_config} 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. @@ -27,7 +32,10 @@ POSITIONAL ARGUMENTS ◆ provide the argument vpc_flow_logs_config on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: + [networkmanagement.organizations.locations.vpcFlowLogsConfigs, + networkmanagement.projects.locations.vpcFlowLogsConfigs]. This must be specified. @@ -49,6 +57,16 @@ POSITIONAL ARGUMENTS with a fully specified name; ▸ provide the argument --location on the command line. + --organization=ORGANIZATION + The organization id of the vpcFlowLogsConfig resource. + + To set the organization attribute: + ▸ provide the argument vpc_flow_logs_config on the command line + with a fully specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networkmanagement.organizations.locations.vpcFlowLogsConfigs]. + 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/network-management/vpc-flow-logs-configs/help b/gcloud/beta/network-management/vpc-flow-logs-configs/help index 94e05896d..5bc3d3aee 100644 --- a/gcloud/beta/network-management/vpc-flow-logs-configs/help +++ b/gcloud/beta/network-management/vpc-flow-logs-configs/help @@ -19,16 +19,21 @@ COMMANDS create (BETA) Creates a new VPC Flow Logs configuration in the specified - project. + organization. delete (BETA) Deletes the specified VPC Flow Logs configuration. describe - (BETA) Describe the details of a specific VPC Flow Logs configuration. + (BETA) Describe the details of a specific VPC Flow Logs configuration + for organization. list - (BETA) List all VPC Flow Logs configurations in the project. + (BETA) List all VPC Flow Logs configurations in the organization. + + query-org-vpc-flow-logs-configs + (BETA) Fetch all organization-level VPC Flow Logs configurations + associated with the project. update (BETA) Updates one or more fields in an existing VPC Flow Logs diff --git a/gcloud/beta/network-management/vpc-flow-logs-configs/list b/gcloud/beta/network-management/vpc-flow-logs-configs/list index 865424249..638032438 100644 --- a/gcloud/beta/network-management/vpc-flow-logs-configs/list +++ b/gcloud/beta/network-management/vpc-flow-logs-configs/list @@ -1,39 +1,44 @@ NAME gcloud beta network-management vpc-flow-logs-configs list - list all VPC - Flow Logs configurations in the project + Flow Logs configurations in the organization SYNOPSIS gcloud beta network-management vpc-flow-logs-configs list - --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + (--location=LOCATION : --organization=ORGANIZATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Lists all VPC Flow Logs configurations in the project. + (BETA) Lists all VPC Flow Logs configurations in the organization. EXAMPLES - To list all the VPC Flow Logs configurations within the project, run: + To list all the VPC Flow Logs configurations within the organization, run: $ gcloud beta network-management vpc-flow-logs-configs list \ - --location=global + --location=global --organization= - To list all the VPC Flow Logs configurations within the project with state - 'ENABLED', run: + To list all the VPC Flow Logs configurations within the organization with + state 'ENABLED', run: $ gcloud beta network-management vpc-flow-logs-configs list \ - --location=global --filter="state:ENABLED" + --location=global --organization= \ + --filter="state:ENABLED" REQUIRED FLAGS Location resource - The parent resource of the VpcFlowLogsConfig: - projects/{project_id}/locations/global This represents a Cloud resource. - (NOTE) Some attributes are not given arguments in this group but can be - set in other ways. + projects/{project_id}/locations/global + organizations/{organization_id}/locations/global 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 --location on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: [networkmanagement.organizations.locations, + networkmanagement.projects.locations]. This must be specified. @@ -43,6 +48,19 @@ REQUIRED FLAGS To set the location attribute: ▸ provide the argument --location on the command line. + This flag argument must be specified if any of the other arguments in + this group are specified. + + --organization=ORGANIZATION + The organization id of the location resource. + + To set the organization attribute: + ▸ provide the argument --location on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networkmanagement.organizations.locations]. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/network-management/vpc-flow-logs-configs/query-org-vpc-flow-logs-configs b/gcloud/beta/network-management/vpc-flow-logs-configs/query-org-vpc-flow-logs-configs new file mode 100644 index 000000000..8a207c139 --- /dev/null +++ b/gcloud/beta/network-management/vpc-flow-logs-configs/query-org-vpc-flow-logs-configs @@ -0,0 +1,83 @@ +NAME + gcloud beta network-management vpc-flow-logs-configs + query-org-vpc-flow-logs-configs - fetch all organization-level VPC Flow + Logs configurations associated with the project + +SYNOPSIS + gcloud beta network-management vpc-flow-logs-configs + query-org-vpc-flow-logs-configs --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Fetch all organization-level VPC Flow Logs configurations that the + project is associated with. This method allows you to retrieve which + organization-level configurations are applied to the current project. + +EXAMPLES + To fetch all the organization-level VPC Flow Logs configurations associated + with the project, run: + + $ gcloud beta network-management vpc-flow-logs-configs \ query-org-vpc-flow-logs-configs --location=global + +REQUIRED FLAGS + Location resource - The parent resource of the VpcFlowLogsConfig: + projects/{project_id}/locations/global 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. + +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 networkmanagement/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-management/vpc-flow-logs-configs/update b/gcloud/beta/network-management/vpc-flow-logs-configs/update index 86347906f..cdc1ab279 100644 --- a/gcloud/beta/network-management/vpc-flow-logs-configs/update +++ b/gcloud/beta/network-management/vpc-flow-logs-configs/update @@ -4,15 +4,17 @@ NAME SYNOPSIS gcloud beta network-management vpc-flow-logs-configs update - (VPC_FLOW_LOGS_CONFIG : --location=LOCATION) + (VPC_FLOW_LOGS_CONFIG + : --location=LOCATION --organization=ORGANIZATION) [--aggregation-interval=AGGREGATION_INTERVAL] [--async] + [--cross-project-metadata=CROSS_PROJECT_METADATA] [--description=DESCRIPTION] [--filter-expr=FILTER_EXPR] [--flow-sampling=FLOW_SAMPLING] [--metadata=METADATA] [--state=STATE] - [--interconnect-attachment=INTERCONNECT_ATTACHMENT - | --vpn-tunnel=VPN_TUNNEL] + [--interconnect-attachment=INTERCONNECT_ATTACHMENT | --network=NETWORK + | --subnet=SUBNET | --vpn-tunnel=VPN_TUNNEL] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] + | --remove-labels=REMOVE_LABELS] [--metadata-fields=[METADATA_FIELDS,...] | --add-metadata-fields=[ADD_METADATA_FIELDS,...] --clear-metadata-fields @@ -28,12 +30,14 @@ EXAMPLES configuration my-config, run: $ gcloud beta network-management vpc-flow-logs-configs update \ - my-config --location=global --state=DISABLED + my-config --location=global --organization= \ + --state=DISABLED POSITIONAL ARGUMENTS VpcFlowLogsConfig resource - Identifier. Unique name of the configuration - using the form: + using one of the forms: projects/{project_id}/locations/global/vpcFlowLogsConfigs/{vpc_flow_logs_config_id} + organizations/{organization_id}/locations/global/vpcFlowLogsConfigs/{vpc_flow_logs_config_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. @@ -42,7 +46,10 @@ POSITIONAL ARGUMENTS ◆ provide the argument vpc_flow_logs_config on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: + [networkmanagement.organizations.locations.vpcFlowLogsConfigs, + networkmanagement.projects.locations.vpcFlowLogsConfigs]. This must be specified. @@ -64,6 +71,16 @@ POSITIONAL ARGUMENTS with a fully specified name; ▸ provide the argument --location on the command line. + --organization=ORGANIZATION + The organization id of the vpcFlowLogsConfig resource. + + To set the organization attribute: + ▸ provide the argument vpc_flow_logs_config on the command line + with a fully specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networkmanagement.organizations.locations.vpcFlowLogsConfigs]. + FLAGS Arguments for the aggregation interval. @@ -88,6 +105,22 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + Arguments for the cross project metadata. + + --cross-project-metadata=CROSS_PROJECT_METADATA + Determines whether to include cross project annotations in the logs. + This field is available only for organization configurations. If not + specified in org configs will be set to + CROSS_PROJECT_METADATA_ENABLED. CROSS_PROJECT_METADATA must be one + of: + + cross-project-metadata-disabled + When CROSS_PROJECT_METADATA_DISABLED, metadata from other + projects will not be included in the logs. + cross-project-metadata-enabled + When CROSS_PROJECT_METADATA_ENABLED, metadata from other projects + will be included in the logs. + Arguments for the description. --description=DESCRIPTION @@ -125,8 +158,9 @@ FLAGS --state=STATE The state of the VPC Flow Log configuration. Default value is - ENABLED. When creating a new configuration, it must be enabled. STATE - must be one of: + ENABLED. When creating a new configuration, it must be enabled. + Setting state=DISABLED will pause the log generation for this config. + STATE must be one of: disabled When DISABLED, this configuration will not generate logs. @@ -141,6 +175,15 @@ FLAGS Traffic will be logged from the Interconnect Attachment. Format: projects/{project_id}/regions/{region}/interconnectAttachments/{name} + --network=NETWORK + Traffic will be logged from VMs, VPN tunnels and Interconnect + Attachments within the network. Format: + projects/{project_id}/global/networks/{name} + + --subnet=SUBNET + Traffic will be logged from VMs within the subnetwork. Format: + projects/{project_id}/regions/{region}/subnetworks/{name} + --vpn-tunnel=VPN_TUNNEL Traffic will be logged from the VPN Tunnel. Format: projects/{project_id}/regions/{region}/vpnTunnels/{name} @@ -202,8 +245,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) Update metadata_fields. diff --git a/gcloud/beta/network-security/help b/gcloud/beta/network-security/help index c42aa8b7d..cb7bbc624 100644 --- a/gcloud/beta/network-security/help +++ b/gcloud/beta/network-security/help @@ -66,6 +66,9 @@ GROUPS org-address-groups (BETA) Manage Network Security AddressGroups. + secure-access-connect + (BETA) Manage Secure Access Connect resources. + security-profile-groups (BETA) Manage Network Security - Security Profile Groups. diff --git a/gcloud/beta/network-security/secure-access-connect/attachments/create b/gcloud/beta/network-security/secure-access-connect/attachments/create new file mode 100644 index 000000000..4e466481c --- /dev/null +++ b/gcloud/beta/network-security/secure-access-connect/attachments/create @@ -0,0 +1,102 @@ +NAME + gcloud beta network-security secure-access-connect attachments create - + create a SAC attachment + +SYNOPSIS + gcloud beta network-security secure-access-connect attachments create + (SAC_ATTACHMENT : --location=LOCATION) --gateway=GATEWAY --realm=REALM + [--async] [--country=COUNTRY] + [--symantec-location-name=SYMANTEC_LOCATION_NAME] + [--symantec-site=SYMANTEC_SITE] [--time-zone=TIME_ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new attachment linked to an existing SAC realm and NCC + gateway. + +EXAMPLES + The following command creates a new attachment named my-attachment in the + location us-central1. + + $ gcloud beta network-security secure-access-connect attachments \ + create my-attachment --location=us-central1 --realm=my-realm \ + --gateway=my-gateway + + The attachment adds security inspection from my-realm to traffic within + my-gateway. + +POSITIONAL ARGUMENTS + SAC attachment resource - Attachment to be created. 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 sac_attachment 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. + + SAC_ATTACHMENT + ID of the SAC attachment or fully qualified identifier for the SAC + attachment. + + To set the sac_attachment attribute: + ▸ provide the argument sac_attachment 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. + + To set the location attribute: + ▸ provide the argument sac_attachment on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --gateway=GATEWAY + NCC gateway whose traffic will be inspected by this attachment. + + --realm=REALM + SAC realm to which this attachment belongs. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --country=COUNTRY + ISO 3166 alpha-2 country code associated with this attachment for + localization. Does not need to match the region where this attachment + is created. + + --symantec-location-name=SYMANTEC_LOCATION_NAME + Name of the Symantec Location that should be created along with this + attachment. + + --symantec-site=SYMANTEC_SITE + Identifier of the Symantec site to which this attachment connects. + + --time-zone=TIME_ZONE + tzinfo time zone associated with this attachment for localization. Does + not need to match the region where this attachment is created. + +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 networksecurity/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-security/secure-access-connect/attachments/delete b/gcloud/beta/network-security/secure-access-connect/attachments/delete new file mode 100644 index 000000000..4459dbe49 --- /dev/null +++ b/gcloud/beta/network-security/secure-access-connect/attachments/delete @@ -0,0 +1,70 @@ +NAME + gcloud beta network-security secure-access-connect attachments delete - + delete a SAC attachment + +SYNOPSIS + gcloud beta network-security secure-access-connect attachments delete + (SAC_ATTACHMENT : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete the specified SAC attachment. + +EXAMPLES + To delete an attachment named my-attachment in the location us-central1, + run: + + $ gcloud beta network-security secure-access-connect attachments \ + delete my-attachment --location=us-central1 + +POSITIONAL ARGUMENTS + SAC attachment resource - Attachment to be deleted. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument sac_attachment 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. + + SAC_ATTACHMENT + ID of the SAC attachment or fully qualified identifier for the SAC + attachment. + + To set the sac_attachment attribute: + ▸ provide the argument sac_attachment 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. + + To set the location attribute: + ▸ provide the argument sac_attachment 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. + +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 networksecurity/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-security/secure-access-connect/attachments/describe b/gcloud/beta/network-security/secure-access-connect/attachments/describe new file mode 100644 index 000000000..5176c8398 --- /dev/null +++ b/gcloud/beta/network-security/secure-access-connect/attachments/describe @@ -0,0 +1,65 @@ +NAME + gcloud beta network-security secure-access-connect attachments describe - + describe a SAC attachment + +SYNOPSIS + gcloud beta network-security secure-access-connect attachments describe + (SAC_ATTACHMENT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show details for the specified SAC attachment. + +EXAMPLES + To describe an attachment named my-attachment in the location us-central1, + run: + + $ gcloud beta network-security secure-access-connect attachments \ + describe my-attachment --location=us-central1 + +POSITIONAL ARGUMENTS + SAC attachment resource - Attachment to be described. 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 sac_attachment 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. + + SAC_ATTACHMENT + ID of the SAC attachment or fully qualified identifier for the SAC + attachment. + + To set the sac_attachment attribute: + ▸ provide the argument sac_attachment 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. + + To set the location attribute: + ▸ provide the argument sac_attachment 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 networksecurity/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-security/secure-access-connect/attachments/help b/gcloud/beta/network-security/secure-access-connect/attachments/help new file mode 100644 index 000000000..5f4f5da8f --- /dev/null +++ b/gcloud/beta/network-security/secure-access-connect/attachments/help @@ -0,0 +1,34 @@ +NAME + gcloud beta network-security secure-access-connect attachments - manage + Secure Access Connect attachments + +SYNOPSIS + gcloud beta network-security secure-access-connect attachments COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Secure Access Connect attachments. + +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 SAC attachment. + + delete + (BETA) Delete a SAC attachment. + + describe + (BETA) Describe a SAC attachment. + + list + (BETA) List SAC attachments. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-security/secure-access-connect/attachments/list b/gcloud/beta/network-security/secure-access-connect/attachments/list new file mode 100644 index 000000000..704fabcde --- /dev/null +++ b/gcloud/beta/network-security/secure-access-connect/attachments/list @@ -0,0 +1,78 @@ +NAME + gcloud beta network-security secure-access-connect attachments list - list + SAC attachments + +SYNOPSIS + gcloud beta network-security secure-access-connect attachments list + --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all SAC attachments within a given location. + +EXAMPLES + To list all attachments in the location us-central1, run: + + $ gcloud beta network-security secure-access-connect attachments \ + list --location=us-central1 + +REQUIRED FLAGS + Location resource - Region of the attachments to display. 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. + +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 networksecurity/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-security/secure-access-connect/help b/gcloud/beta/network-security/secure-access-connect/help new file mode 100644 index 000000000..2d8dafa43 --- /dev/null +++ b/gcloud/beta/network-security/secure-access-connect/help @@ -0,0 +1,28 @@ +NAME + gcloud beta network-security secure-access-connect - manage Secure Access + Connect resources + +SYNOPSIS + gcloud beta network-security secure-access-connect GROUP + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Secure Access Connect resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + attachments + (BETA) Manage Secure Access Connect attachments. + + realms + (BETA) Manage Secure Access Connect realms. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-security/secure-access-connect/realms/create b/gcloud/beta/network-security/secure-access-connect/realms/create new file mode 100644 index 000000000..13d1697c5 --- /dev/null +++ b/gcloud/beta/network-security/secure-access-connect/realms/create @@ -0,0 +1,77 @@ +NAME + gcloud beta network-security secure-access-connect realms create - create a + SAC realm + +SYNOPSIS + gcloud beta network-security secure-access-connect realms create + (SAC_REALM : --location=LOCATION) --security-service=SECURITY_SERVICE + [--async] [--symantec-secret=SYMANTEC_SECRET] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new realm supported by the specified security service. + +EXAMPLES + To create a realm named my-realm using Prisma Access, run: + + $ gcloud beta network-security secure-access-connect realms create \ + my-realm --security-service=prisma-access + +POSITIONAL ARGUMENTS + SAC realm resource - Realm to be created. 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 sac_realm 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. + + SAC_REALM + ID of the SAC realm or fully qualified identifier for the SAC realm. + + To set the sac_realm attribute: + ▸ provide the argument sac_realm 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. + + To set the location attribute: + ▸ provide the argument sac_realm on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ location is global by default. + +REQUIRED FLAGS + --security-service=SECURITY_SERVICE + Security service supporting this realm. SECURITY_SERVICE must be one + of: prisma-access, symantec-cloud-swg. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --symantec-secret=SYMANTEC_SECRET + ID of the Secret in Secret Manager containing the Symantec credentials. + +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 networksecurity/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-security/secure-access-connect/realms/delete b/gcloud/beta/network-security/secure-access-connect/realms/delete new file mode 100644 index 000000000..54dc8a339 --- /dev/null +++ b/gcloud/beta/network-security/secure-access-connect/realms/delete @@ -0,0 +1,68 @@ +NAME + gcloud beta network-security secure-access-connect realms delete - delete a + SAC realm + +SYNOPSIS + gcloud beta network-security secure-access-connect realms delete + (SAC_REALM : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete the specified SAC realm. + +EXAMPLES + To delete a realm named my-realm, run: + + $ gcloud beta network-security secure-access-connect realms delete \ + my-realm + +POSITIONAL ARGUMENTS + SAC realm resource - Realm to be deleted. The arguments in this group can + be used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument sac_realm 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. + + SAC_REALM + ID of the SAC realm or fully qualified identifier for the SAC realm. + + To set the sac_realm attribute: + ▸ provide the argument sac_realm 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. + + To set the location attribute: + ▸ provide the argument sac_realm on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ location is global by default. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networksecurity/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-security/secure-access-connect/realms/describe b/gcloud/beta/network-security/secure-access-connect/realms/describe new file mode 100644 index 000000000..388ccc55a --- /dev/null +++ b/gcloud/beta/network-security/secure-access-connect/realms/describe @@ -0,0 +1,64 @@ +NAME + gcloud beta network-security secure-access-connect realms describe - + describe a SAC realm + +SYNOPSIS + gcloud beta network-security secure-access-connect realms describe + (SAC_REALM : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show details for the specified SAC realm. + +EXAMPLES + To describe a realm named my-realm, run: + + $ gcloud beta network-security secure-access-connect realms \ + describe my-realm + +POSITIONAL ARGUMENTS + SAC realm resource - Realm to be described. 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 sac_realm 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. + + SAC_REALM + ID of the SAC realm or fully qualified identifier for the SAC realm. + + To set the sac_realm attribute: + ▸ provide the argument sac_realm 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. + + To set the location attribute: + ▸ provide the argument sac_realm on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ location is global by default. + +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 networksecurity/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-security/secure-access-connect/realms/help b/gcloud/beta/network-security/secure-access-connect/realms/help new file mode 100644 index 000000000..02959772b --- /dev/null +++ b/gcloud/beta/network-security/secure-access-connect/realms/help @@ -0,0 +1,34 @@ +NAME + gcloud beta network-security secure-access-connect realms - manage Secure + Access Connect realms + +SYNOPSIS + gcloud beta network-security secure-access-connect realms COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Secure Access Connect realms. + +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 SAC realm. + + delete + (BETA) Delete a SAC realm. + + describe + (BETA) Describe a SAC realm. + + list + (BETA) List SAC realms. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-security/secure-access-connect/realms/list b/gcloud/beta/network-security/secure-access-connect/realms/list new file mode 100644 index 000000000..cf3dbe5b3 --- /dev/null +++ b/gcloud/beta/network-security/secure-access-connect/realms/list @@ -0,0 +1,78 @@ +NAME + gcloud beta network-security secure-access-connect realms list - list SAC + realms + +SYNOPSIS + gcloud beta network-security secure-access-connect realms list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all SAC realms within a given project. + +EXAMPLES + To list all realms in the current project, run: + + $ gcloud beta network-security secure-access-connect realms list + +FLAGS + Location resource - Project of the realms to display. The location is + global by default and should not be set. 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; + ◆ location is global by default 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; + ▸ location is global by default. + +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 networksecurity/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/network-services/help b/gcloud/beta/network-services/help index 99866b872..ff3206ed7 100644 --- a/gcloud/beta/network-services/help +++ b/gcloud/beta/network-services/help @@ -45,6 +45,9 @@ GROUPS multicast-producer-associations (BETA) Manage Network Services MulticastProducerAssociations. + operations + (BETA) Manage Network Services Operations. + service-bindings (BETA) Manage Network Services Bindings. diff --git a/gcloud/beta/network-services/operations/cancel b/gcloud/beta/network-services/operations/cancel new file mode 100644 index 000000000..a22b446db --- /dev/null +++ b/gcloud/beta/network-services/operations/cancel @@ -0,0 +1,68 @@ +NAME + gcloud beta network-services operations cancel - cancel a Network Services + long running operation + +SYNOPSIS + gcloud beta network-services operations cancel + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Cancel a Network Services long running operation. + +EXAMPLES + The following command cancels an operation with the full name + OPERATION_NAME: + + $ gcloud beta network-services operations cancel OPERATION_NAME + +POSITIONAL ARGUMENTS + Operation resource - Name of the operation to cancel. 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. + + 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 networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud network-services operations cancel + + $ gcloud alpha network-services operations cancel + diff --git a/gcloud/beta/network-services/operations/describe b/gcloud/beta/network-services/operations/describe new file mode 100644 index 000000000..dc23602f5 --- /dev/null +++ b/gcloud/beta/network-services/operations/describe @@ -0,0 +1,68 @@ +NAME + gcloud beta network-services operations describe - show details of a + Network Services long running operation + +SYNOPSIS + gcloud beta network-services operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show details of a Network Services long running operation. + +EXAMPLES + The following command describes an operation with the full name + OPERATION_NAME: + + $ gcloud beta network-services operations describe OPERATION_NAME + +POSITIONAL ARGUMENTS + Operation resource - Name of the operation 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 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. + + 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 networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud network-services operations describe + + $ gcloud alpha network-services operations describe + diff --git a/gcloud/beta/network-services/operations/help b/gcloud/beta/network-services/operations/help new file mode 100644 index 000000000..16bde633f --- /dev/null +++ b/gcloud/beta/network-services/operations/help @@ -0,0 +1,38 @@ +NAME + gcloud beta network-services operations - manage Network Services + Operations + +SYNOPSIS + gcloud beta network-services operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Network Services Operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (BETA) Cancel a Network Services long running operation. + + describe + (BETA) Show details of a Network Services long running operation. + + list + (BETA) List all Network Services long running operations. + + wait + (BETA) Poll a Network Services long running operation. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud network-services operations + + $ gcloud alpha network-services operations + diff --git a/gcloud/beta/healthcare/annotation-stores/list b/gcloud/beta/network-services/operations/list similarity index 62% rename from gcloud/beta/healthcare/annotation-stores/list rename to gcloud/beta/network-services/operations/list index 563d66b34..50cb8d119 100644 --- a/gcloud/beta/healthcare/annotation-stores/list +++ b/gcloud/beta/network-services/operations/list @@ -1,53 +1,39 @@ NAME - gcloud beta healthcare annotation-stores list - list Cloud Healthcare API - annotation stores + gcloud beta network-services operations list - list all Network Services + long running operations SYNOPSIS - gcloud beta healthcare annotation-stores list - (--dataset=DATASET : --location=LOCATION) [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud beta network-services operations list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Cloud Healthcare API annotation stores. + (BETA) List all Network Services long running operations. EXAMPLES - To list the annotation stores in 'test-dataset', run: + The following command lists all operations in the current project and in + location global: - $ gcloud beta healthcare annotation-stores list \ - --dataset=test-dataset + $ gcloud beta network-services operations list --location=global REQUIRED FLAGS - Dataset resource - The dataset to list the annotation stores for. The - arguments in this group can be used to specify the attributes of this + Location resource - Location of the operations. 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 --dataset on the command line with a fully + ◆ 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. - --dataset=DATASET - ID of the dataset or fully qualified identifier for the dataset. - - To set the dataset attribute: - ▸ provide the argument --dataset on the command line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - --location=LOCATION - Google Cloud location. + ID of the location or fully qualified identifier for the location. To set the location attribute: - ▸ provide the argument --dataset on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property healthcare/location. + ▸ provide the argument --location on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -90,12 +76,14 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the healthcare/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/healthcare + This command uses the networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking 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 alpha healthcare annotation-stores list + $ gcloud network-services operations list + + $ gcloud alpha network-services operations list diff --git a/gcloud/beta/network-services/operations/wait b/gcloud/beta/network-services/operations/wait new file mode 100644 index 000000000..854bae441 --- /dev/null +++ b/gcloud/beta/network-services/operations/wait @@ -0,0 +1,67 @@ +NAME + gcloud beta network-services operations wait - poll a Network Services long + running operation + +SYNOPSIS + gcloud beta network-services operations wait + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Poll a Network Services long running operation. + +EXAMPLES + The following command polls an operation with the full name OPERATION_NAME: + + $ gcloud beta network-services operations wait OPERATION_NAME + +POSITIONAL ARGUMENTS + Operation resource - Name of the operation to poll. 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. + + 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 networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud network-services operations wait + + $ gcloud alpha network-services operations wait + diff --git a/gcloud/beta/resource-manager/tags/keys/create b/gcloud/beta/resource-manager/tags/keys/create index fc1633d75..2b5ba698a 100644 --- a/gcloud/beta/resource-manager/tags/keys/create +++ b/gcloud/beta/resource-manager/tags/keys/create @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta resource-manager tags keys create (SHORT_NAME --parent=PARENT) - [--async] [--description=DESCRIPTION] [--purpose=PURPOSE] + [--allowed-values-regex=ALLOWED_VALUES_REGEX] [--async] + [--description=DESCRIPTION] [--purpose=PURPOSE] [--purpose-data=[network=NETWORK],[organization=ORGANIZATION]] [GCLOUD_WIDE_FLAG ...] @@ -36,6 +37,9 @@ POSITIONAL ARGUMENTS this group are specified. FLAGS + --allowed-values-regex=ALLOWED_VALUES_REGEX + User-assigned regex of allowed short names of TagValues under a TagKey. + --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/beta/resource-manager/tags/keys/update b/gcloud/beta/resource-manager/tags/keys/update index da9524171..b80d5f348 100644 --- a/gcloud/beta/resource-manager/tags/keys/update +++ b/gcloud/beta/resource-manager/tags/keys/update @@ -3,7 +3,8 @@ NAME TagKey resource's description SYNOPSIS - gcloud beta resource-manager tags keys update RESOURCE_NAME [--async] + gcloud beta resource-manager tags keys update RESOURCE_NAME + [--allowed-values-regex=ALLOWED_VALUES_REGEX] [--async] [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -14,12 +15,12 @@ EXAMPLES To update a TagKey with id 123, run: $ gcloud beta resource-manager tags keys update tagKeys/123 \ - --description=foobar + --description=foobar --allowed-values-regex=.* To update a TagKey named env under organization 456, run: $ gcloud beta resource-manager tags keys update 456/env \ - --description=foobar + --description=foobar --allowed-values-regex=.* POSITIONAL ARGUMENTS RESOURCE_NAME @@ -30,6 +31,9 @@ POSITIONAL ARGUMENTS dashes (-), underscores ( _ ), dots (.), and alphanumerics between. FLAGS + --allowed-values-regex=ALLOWED_VALUES_REGEX + User-assigned regex of allowed short names of TagValues under a TagKey. + --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/beta/saas-runtime/releases/update b/gcloud/beta/saas-runtime/releases/update index 0eb06035e..e71094f66 100644 --- a/gcloud/beta/saas-runtime/releases/update +++ b/gcloud/beta/saas-runtime/releases/update @@ -11,7 +11,7 @@ SYNOPSIS [value=VALUE],[variable=VARIABLE]] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] + | --remove-labels=REMOVE_LABELS] [--upgradeable-from-releases=[UPGRADEABLE_FROM_RELEASES,...] | --add-upgradeable-from-releases=[ADD_UPGRADEABLE_FROM_RELEASES,...] --clear-upgradeable-from-releases @@ -203,8 +203,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) Update upgradeable_from_releases. diff --git a/gcloud/beta/saas-runtime/rollout-kinds/update b/gcloud/beta/saas-runtime/rollout-kinds/update index 7501b8167..9b27735a8 100644 --- a/gcloud/beta/saas-runtime/rollout-kinds/update +++ b/gcloud/beta/saas-runtime/rollout-kinds/update @@ -12,7 +12,7 @@ SYNOPSIS --error-budget-allowed-percentage=ERROR_BUDGET_ALLOWED_PERCENTAGE] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update a Rollout Type @@ -149,8 +149,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/saas-runtime/rollouts/update b/gcloud/beta/saas-runtime/rollouts/update index bcb5d62d5..3b7594a67 100644 --- a/gcloud/beta/saas-runtime/rollouts/update +++ b/gcloud/beta/saas-runtime/rollouts/update @@ -9,7 +9,7 @@ SYNOPSIS --control-action=CONTROL_ACTION --[no-]retry-failed-operations] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update a Rollout @@ -155,8 +155,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/saas-runtime/saas/update b/gcloud/beta/saas-runtime/saas/update index 8371260ab..2ed5e7857 100644 --- a/gcloud/beta/saas-runtime/saas/update +++ b/gcloud/beta/saas-runtime/saas/update @@ -5,7 +5,7 @@ SYNOPSIS gcloud beta saas-runtime saas update (SAAS : --location=LOCATION) [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] + | --remove-labels=REMOVE_LABELS] [--locations=[name=NAME] | --add-locations=[name=NAME] --clear-locations | --remove-locations=[name=NAME]] [GCLOUD_WIDE_FLAG ...] @@ -108,8 +108,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) Update locations. diff --git a/gcloud/beta/saas-runtime/tenants/update b/gcloud/beta/saas-runtime/tenants/update index 2811f4068..9dba817ff 100644 --- a/gcloud/beta/saas-runtime/tenants/update +++ b/gcloud/beta/saas-runtime/tenants/update @@ -5,7 +5,7 @@ SYNOPSIS gcloud beta saas-runtime tenants update (TENANT : --location=LOCATION) [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update a tenant @@ -105,8 +105,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/saas-runtime/unit-kinds/update b/gcloud/beta/saas-runtime/unit-kinds/update index 8b6389bde..44e106f0d 100644 --- a/gcloud/beta/saas-runtime/unit-kinds/update +++ b/gcloud/beta/saas-runtime/unit-kinds/update @@ -16,7 +16,7 @@ SYNOPSIS [to=TO],[variable=VARIABLE]] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] + | --remove-labels=REMOVE_LABELS] [--output-variable-mappings=[from=FROM],[to=TO],[variable=VARIABLE] | --add-output-variable-mappings=[from=FROM], [to=TO],[variable=VARIABLE] --clear-output-variable-mappings @@ -398,8 +398,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) Update output_variable_mappings. diff --git a/gcloud/beta/saas-runtime/unit-operations/update b/gcloud/beta/saas-runtime/unit-operations/update index b483c0e12..cbaeb9e34 100644 --- a/gcloud/beta/saas-runtime/unit-operations/update +++ b/gcloud/beta/saas-runtime/unit-operations/update @@ -24,7 +24,7 @@ SYNOPSIS [value=VALUE],[variable=VARIABLE]] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update a Unit Operation @@ -466,8 +466,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/saas-runtime/units/update b/gcloud/beta/saas-runtime/units/update index a9c4e2651..ce6db1ffa 100644 --- a/gcloud/beta/saas-runtime/units/update +++ b/gcloud/beta/saas-runtime/units/update @@ -8,7 +8,7 @@ SYNOPSIS [--clear-unit-kind | --unit-kind=UNIT_KIND] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update a Unit @@ -180,8 +180,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/scheduler/jobs/create/app-engine b/gcloud/beta/scheduler/jobs/create/app-engine index 8243fa86f..5e8d56329 100644 --- a/gcloud/beta/scheduler/jobs/create/app-engine +++ b/gcloud/beta/scheduler/jobs/create/app-engine @@ -7,8 +7,8 @@ SYNOPSIS --schedule=SCHEDULE [--attempt-deadline=ATTEMPT_DEADLINE] [--description=DESCRIPTION] [--headers=[KEY=VALUE,...]] [--http-method=HTTP_METHOD; default="post"] - [--max-backoff=MAX_BACKOFF; default="1h"] - [--max-doublings=MAX_DOUBLINGS; default=16] + [--max-backoff=MAX_BACKOFF; default="3600s"] + [--max-doublings=MAX_DOUBLINGS; default=5] [--max-retry-attempts=MAX_RETRY_ATTEMPTS] [--max-retry-duration=MAX_RETRY_DURATION] [--min-backoff=MIN_BACKOFF; default="5s"] @@ -70,16 +70,16 @@ REQUIRED FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). OPTIONAL FLAGS --attempt-deadline=ATTEMPT_DEADLINE @@ -99,11 +99,11 @@ OPTIONAL FLAGS HTTP method to use for the request. HTTP_METHOD must be one of: delete, get, head, post, put. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -112,13 +112,14 @@ OPTIONAL FLAGS in range 0-5 inclusive. Default is 0. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task was + Time limit for retrying a failed job, measured from when the job was first run. If specified with --max-retry-attempts greater than 0, the - task will be retried until both limits are reached. Default is 0 (which - means unlimited). + job will be retried until both limits are reached. Default is 0 seconds + (which means unlimited); however, if --max-retry-attempts is also 0, a + job attempt won't be retried if it fails. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. --relative-url=RELATIVE_URL; default="/" diff --git a/gcloud/beta/scheduler/jobs/create/http b/gcloud/beta/scheduler/jobs/create/http index 7c6bb872e..9129d3491 100644 --- a/gcloud/beta/scheduler/jobs/create/http +++ b/gcloud/beta/scheduler/jobs/create/http @@ -7,8 +7,8 @@ SYNOPSIS --schedule=SCHEDULE --uri=URI [--attempt-deadline=ATTEMPT_DEADLINE] [--description=DESCRIPTION] [--headers=[KEY=VALUE,...]] [--http-method=HTTP_METHOD; default="post"] - [--max-backoff=MAX_BACKOFF; default="1h"] - [--max-doublings=MAX_DOUBLINGS; default=16] + [--max-backoff=MAX_BACKOFF; default="3600s"] + [--max-doublings=MAX_DOUBLINGS; default=5] [--max-retry-attempts=MAX_RETRY_ATTEMPTS] [--max-retry-duration=MAX_RETRY_DURATION] [--min-backoff=MIN_BACKOFF; default="5s"] @@ -73,16 +73,16 @@ REQUIRED FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --uri=URI The full URI path that the request will be sent to. This string must @@ -109,11 +109,11 @@ OPTIONAL FLAGS HTTP method to use for the request. HTTP_METHOD must be one of: delete, get, head, post, put. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -122,13 +122,14 @@ OPTIONAL FLAGS in range 0-5 inclusive. Default is 0. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task was + Time limit for retrying a failed job, measured from when the job was first run. If specified with --max-retry-attempts greater than 0, the - task will be retried until both limits are reached. Default is 0 (which - means unlimited). + job will be retried until both limits are reached. Default is 0 seconds + (which means unlimited); however, if --max-retry-attempts is also 0, a + job attempt won't be retried if it fails. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. --time-zone=TIME_ZONE; default="Etc/UTC" diff --git a/gcloud/beta/scheduler/jobs/create/pubsub b/gcloud/beta/scheduler/jobs/create/pubsub index d75489b2a..01f8c8db7 100644 --- a/gcloud/beta/scheduler/jobs/create/pubsub +++ b/gcloud/beta/scheduler/jobs/create/pubsub @@ -7,8 +7,8 @@ SYNOPSIS --schedule=SCHEDULE --topic=TOPIC (--attributes=ATTRIBUTES --message-body=MESSAGE_BODY | --message-body-from-file=PATH_TO_FILE) [--description=DESCRIPTION] - [--max-backoff=MAX_BACKOFF; default="1h"] - [--max-doublings=MAX_DOUBLINGS; default=16] + [--max-backoff=MAX_BACKOFF; default="3600s"] + [--max-doublings=MAX_DOUBLINGS; default=5] [--max-retry-attempts=MAX_RETRY_ATTEMPTS] [--max-retry-duration=MAX_RETRY_DURATION] [--min-backoff=MIN_BACKOFF; default="5s"] @@ -68,16 +68,16 @@ REQUIRED FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --topic=TOPIC Name of the Google Cloud Pub/Sub topic to publish to when the job runs. @@ -105,11 +105,11 @@ OPTIONAL FLAGS --description=DESCRIPTION Human-readable description of the job. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -118,13 +118,14 @@ OPTIONAL FLAGS in range 0-5 inclusive. Default is 0. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task was + Time limit for retrying a failed job, measured from when the job was first run. If specified with --max-retry-attempts greater than 0, the - task will be retried until both limits are reached. Default is 0 (which - means unlimited). + job will be retried until both limits are reached. Default is 0 seconds + (which means unlimited); however, if --max-retry-attempts is also 0, a + job attempt won't be retried if it fails. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. --time-zone=TIME_ZONE; default="Etc/UTC" diff --git a/gcloud/beta/scheduler/jobs/update/app-engine b/gcloud/beta/scheduler/jobs/update/app-engine index e11d9eef5..fe7835286 100644 --- a/gcloud/beta/scheduler/jobs/update/app-engine +++ b/gcloud/beta/scheduler/jobs/update/app-engine @@ -9,8 +9,8 @@ SYNOPSIS [--version=VERSION] [--clear-headers | --remove-headers=[REMOVE_HEADERS,...] --update-headers=[KEY=VALUE,...]] - [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"] - [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16] + [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="3600s"] + [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=5] [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS] [--clear-max-retry-duration | --max-retry-duration=MAX_RETRY_DURATION] [--clear-message-body | --message-body=MESSAGE_BODY @@ -85,16 +85,16 @@ FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --version=VERSION Version of the App Engine service to send the request to. @@ -118,16 +118,16 @@ FLAGS --clear-max-backoff Clear the field corresponding to --max-backoff. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). At most one of these can be specified: --clear-max-doublings Clear the field corresponding to --max-doublings. - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -146,10 +146,11 @@ FLAGS Clear the field corresponding to --max-retry-duration. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task - was first run. If specified with --max-retry-attempts greater than 0, - the task will be retried until both limits are reached. Default is 0 - (which means unlimited). + Time limit for retrying a failed job, measured from when the job was + first run. If specified with --max-retry-attempts greater than 0, the + job will be retried until both limits are reached. Default is 0 + seconds (which means unlimited); however, if --max-retry-attempts is + also 0, a job attempt won't be retried if it fails. At most one of these can be specified: @@ -173,7 +174,7 @@ FLAGS Clear the field corresponding to --min-backoff. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. At most one of these can be specified: diff --git a/gcloud/beta/scheduler/jobs/update/http b/gcloud/beta/scheduler/jobs/update/http index 5feb29ca6..9add6c30c 100644 --- a/gcloud/beta/scheduler/jobs/update/http +++ b/gcloud/beta/scheduler/jobs/update/http @@ -14,8 +14,8 @@ SYNOPSIS : --oidc-token-audience=OIDC_TOKEN_AUDIENCE]] [--clear-headers | --remove-headers=[REMOVE_HEADERS,...] --update-headers=[KEY=VALUE,...]] - [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"] - [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16] + [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="3600s"] + [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=5] [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS] [--clear-max-retry-duration | --max-retry-duration=MAX_RETRY_DURATION] [--clear-message-body | --message-body=MESSAGE_BODY @@ -88,16 +88,16 @@ FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --uri=URI The full URI path that the request will be sent to. This string must @@ -173,16 +173,16 @@ FLAGS --clear-max-backoff Clear the field corresponding to --max-backoff. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). At most one of these can be specified: --clear-max-doublings Clear the field corresponding to --max-doublings. - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -201,10 +201,11 @@ FLAGS Clear the field corresponding to --max-retry-duration. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task - was first run. If specified with --max-retry-attempts greater than 0, - the task will be retried until both limits are reached. Default is 0 - (which means unlimited). + Time limit for retrying a failed job, measured from when the job was + first run. If specified with --max-retry-attempts greater than 0, the + job will be retried until both limits are reached. Default is 0 + seconds (which means unlimited); however, if --max-retry-attempts is + also 0, a job attempt won't be retried if it fails. At most one of these can be specified: @@ -228,7 +229,7 @@ FLAGS Clear the field corresponding to --min-backoff. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. At most one of these can be specified: diff --git a/gcloud/beta/scheduler/jobs/update/pubsub b/gcloud/beta/scheduler/jobs/update/pubsub index 44e0109f2..f3d64a2f2 100644 --- a/gcloud/beta/scheduler/jobs/update/pubsub +++ b/gcloud/beta/scheduler/jobs/update/pubsub @@ -7,8 +7,8 @@ SYNOPSIS [--description=DESCRIPTION] [--schedule=SCHEDULE] [--topic=TOPIC] [--clear-attributes | --remove-attributes=[REMOVE_ATTRIBUTES,...] --update-attributes=[KEY=VALUE,...]] - [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"] - [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16] + [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="3600s"] + [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=5] [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS] [--clear-max-retry-duration | --max-retry-duration=MAX_RETRY_DURATION] [--clear-min-backoff | --min-backoff=MIN_BACKOFF; default="5s"] @@ -71,16 +71,16 @@ FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --topic=TOPIC Name of the Google Cloud Pub/Sub topic to publish to when the job runs. @@ -103,16 +103,16 @@ FLAGS --clear-max-backoff Clear the field corresponding to --max-backoff. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). At most one of these can be specified: --clear-max-doublings Clear the field corresponding to --max-doublings. - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -131,10 +131,11 @@ FLAGS Clear the field corresponding to --max-retry-duration. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task - was first run. If specified with --max-retry-attempts greater than 0, - the task will be retried until both limits are reached. Default is 0 - (which means unlimited). + Time limit for retrying a failed job, measured from when the job was + first run. If specified with --max-retry-attempts greater than 0, the + job will be retried until both limits are reached. Default is 0 + seconds (which means unlimited); however, if --max-retry-attempts is + also 0, a job attempt won't be retried if it fails. At most one of these can be specified: @@ -142,7 +143,7 @@ FLAGS Clear the field corresponding to --min-backoff. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. At most one of these can be specified: diff --git a/gcloud/beta/service-extensions/help b/gcloud/beta/service-extensions/help index b63d1b226..a67b8b045 100644 --- a/gcloud/beta/service-extensions/help +++ b/gcloud/beta/service-extensions/help @@ -18,6 +18,9 @@ GROUPS authz-extensions (BETA) Manage Service Extensions AuthzExtension resources. + lb-edge-extensions + (BETA) Manage Service Extensions LbEdgeExtension resources. + lb-route-extensions (BETA) Manage Service Extensions LbRouteExtension resources. diff --git a/gcloud/beta/service-extensions/lb-edge-extensions/delete b/gcloud/beta/service-extensions/lb-edge-extensions/delete new file mode 100644 index 000000000..70db4a122 --- /dev/null +++ b/gcloud/beta/service-extensions/lb-edge-extensions/delete @@ -0,0 +1,70 @@ +NAME + gcloud beta service-extensions lb-edge-extensions delete - delete an + LbEdgeExtension resource + +SYNOPSIS + gcloud beta service-extensions lb-edge-extensions delete + (LB_EDGE_EXTENSION : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete the specified LbEdgeExtension resource. + +EXAMPLES + To delete a global LbEdgeExtension resource named my-edge-extension, run: + + $ gcloud beta service-extensions lb-edge-extensions delete \ + my-edge-extension --location=global + +POSITIONAL ARGUMENTS + LbEdgeExtension resource - The ID of the deleted LbEdgeExtension 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 lb_edge_extension 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. + + LB_EDGE_EXTENSION + ID of the LbEdgeExtension or fully qualified identifier for the + LbEdgeExtension. + + To set the lb_edge_extension attribute: + ▸ provide the argument lb_edge_extension on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Cloud region in which the resource is located. + + To set the location attribute: + ▸ provide the argument lb_edge_extension 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. + +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 networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/service-extensions/lb-edge-extensions/describe b/gcloud/beta/service-extensions/lb-edge-extensions/describe new file mode 100644 index 000000000..b2e949630 --- /dev/null +++ b/gcloud/beta/service-extensions/lb-edge-extensions/describe @@ -0,0 +1,65 @@ +NAME + gcloud beta service-extensions lb-edge-extensions describe - describe an + LbEdgeExtension resource + +SYNOPSIS + gcloud beta service-extensions lb-edge-extensions describe + (LB_EDGE_EXTENSION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show details about an LbEdgeExtension resource. + +EXAMPLES + To show details about the global LbEdgeExtension resource named + my-edge-extension. + + $ gcloud beta service-extensions lb-edge-extensions describe \ + my-edge-extension --location=global + +POSITIONAL ARGUMENTS + LbEdgeExtension resource - The ID of the LbEdgeExtension 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 lb_edge_extension 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. + + LB_EDGE_EXTENSION + ID of the LbEdgeExtension or fully qualified identifier for the + LbEdgeExtension. + + To set the lb_edge_extension attribute: + ▸ provide the argument lb_edge_extension on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Cloud region in which the resource is located. + + To set the location attribute: + ▸ provide the argument lb_edge_extension 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 networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/service-extensions/lb-edge-extensions/help b/gcloud/beta/service-extensions/lb-edge-extensions/help new file mode 100644 index 000000000..a891a7662 --- /dev/null +++ b/gcloud/beta/service-extensions/lb-edge-extensions/help @@ -0,0 +1,34 @@ +NAME + gcloud beta service-extensions lb-edge-extensions - manage Service + Extensions LbEdgeExtension resources + +SYNOPSIS + gcloud beta service-extensions lb-edge-extensions COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Service Extensions LbEdgeExtension resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (BETA) Delete an LbEdgeExtension resource. + + describe + (BETA) Describe an LbEdgeExtension resource. + + import + (BETA) Import an LbEdgeExtension resource. + + list + (BETA) List LbEdgeExtension resources. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/service-extensions/lb-edge-extensions/import b/gcloud/beta/service-extensions/lb-edge-extensions/import new file mode 100644 index 000000000..ebaf5f3de --- /dev/null +++ b/gcloud/beta/service-extensions/lb-edge-extensions/import @@ -0,0 +1,82 @@ +NAME + gcloud beta service-extensions lb-edge-extensions import - import an + LbEdgeExtension resource + +SYNOPSIS + gcloud beta service-extensions lb-edge-extensions import + (LB_EDGE_EXTENSION : --location=LOCATION) [--async] [--source=SOURCE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Import an LbEdgeExtension resource defined in a YAML file. + +EXAMPLES + To import a global LbEdgeExtension resource named my-edge-extension from a + YAML file, run: + + $ gcloud beta service-extensions lb-edge-extensions import \ + my-edge-extension --source=my-edge-extension.yaml \ + --location=global + +POSITIONAL ARGUMENTS + LbEdgeExtension resource - The ID of the new or updated LbEdgeExtension + 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 lb_edge_extension 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. + + LB_EDGE_EXTENSION + ID of the LbEdgeExtension or fully qualified identifier for the + LbEdgeExtension. + + To set the lb_edge_extension attribute: + ▸ provide the argument lb_edge_extension on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Cloud region in which the resource is located. + + To set the location attribute: + ▸ provide the argument lb_edge_extension 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. + + --source=SOURCE + Path to a YAML file containing the configuration export data. The YAML + file must not contain any output-only fields. Alternatively, you may + omit this flag to read from standard input. For a schema describing the + export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + + $CLOUDSDKROOT is can be obtained with the following command: + + $ gcloud info --format='value(installation.sdk_root)' + +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 networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/service-extensions/lb-edge-extensions/list b/gcloud/beta/service-extensions/lb-edge-extensions/list new file mode 100644 index 000000000..5e8f6b17f --- /dev/null +++ b/gcloud/beta/service-extensions/lb-edge-extensions/list @@ -0,0 +1,85 @@ +NAME + gcloud beta service-extensions lb-edge-extensions list - list + LbEdgeExtension resources + +SYNOPSIS + gcloud beta service-extensions lb-edge-extensions list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all LbEdgeExtension resources in the specified location of the + current project. + +EXAMPLES + To list all global LbEdgeExtension resources in the current project, run: + + $ gcloud beta service-extensions lb-edge-extensions list \ + --location=global + +REQUIRED FLAGS + Location resource - The parent location. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ 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 networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/spanner/databases/update b/gcloud/beta/spanner/databases/update index 44ad035d6..c37b4aa97 100644 --- a/gcloud/beta/spanner/databases/update +++ b/gcloud/beta/spanner/databases/update @@ -3,7 +3,9 @@ NAME SYNOPSIS gcloud beta spanner databases update (DATABASE : --instance=INSTANCE) - [--async] [--[no-]enable-drop-protection] [GCLOUD_WIDE_FLAG ...] + [--async] + [--[no-]enable-drop-protection | --kms-keys=KMS_KEY,[KMS_KEY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update a Cloud Spanner database. @@ -21,6 +23,12 @@ EXAMPLES $ gcloud beta spanner databases update my-database \ --no-enable-drop-protection + To update KMS key references for a Cloud Spanner database 'my-database', + run: + + $ gcloud beta spanner databases update my-database \ + --kms-keys="KEY1,KEY2" + POSITIONAL ARGUMENTS Database resource - The Cloud Spanner database to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -58,10 +66,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. - --[no-]enable-drop-protection - Enable database deletion protection on this database. Use - --enable-drop-protection to enable and --no-enable-drop-protection to - disable. + At most one of these can be specified: + + --[no-]enable-drop-protection + Enable database deletion protection on this database. Use + --enable-drop-protection to enable and --no-enable-drop-protection to + disable. + + --kms-keys=KMS_KEY,[KMS_KEY,...] + Update KMS key references for this database. Users should always + provide the full set of required KMS key references. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/spanner/operations/describe b/gcloud/beta/spanner/operations/describe index 4c5168f4d..0dd742f34 100644 --- a/gcloud/beta/spanner/operations/describe +++ b/gcloud/beta/spanner/operations/describe @@ -27,7 +27,7 @@ EXAMPLES $ gcloud beta spanner operations describe _auto_12345 \ --instance=my-instance-id --backup=my-backup-id - To describe a Cloud Spanner instance partition operation, run: + To describe an instance partition operation, run: $ gcloud beta spanner operations describe _auto_12345 \ --instance=my-instance-id --instance-partition=my-partition-id @@ -55,7 +55,7 @@ OPTIONAL FLAGS executing on. --instance-partition=INSTANCE_PARTITION - For instance partition operations, the name of the instance partition + For an instance partition operation, the name of the instance partition the operation is executing on. GCLOUD WIDE FLAGS diff --git a/gcloud/beta/sql/backups/restore b/gcloud/beta/sql/backups/restore index 23b48c154..827f7fc26 100644 --- a/gcloud/beta/sql/backups/restore +++ b/gcloud/beta/sql/backups/restore @@ -160,7 +160,10 @@ OPTIONAL FLAGS --cpu=CPU Whole number value indicating how many cores are desired in the machine. Both --cpu and --memory must be specified if a custom machine - type is desired, and the --tier flag must be omitted. + type is desired, and the --tier flag must be omitted.--cpu and --memory + flags are not compatible with the Enterprise Plus edition. These flags + should not be used when creating an Enterprise Plus edition, as the + machine configuration is determined by the --tier flag instead. --database-version=DATABASE_VERSION The database engine type and versions. If left unspecified, no changes @@ -254,7 +257,10 @@ OPTIONAL FLAGS machine. A size unit should be provided (eg. 3072MiB or 9GiB) - if no units are specified, GiB is assumed. Both --cpu and --memory must be specified if a custom machine type is desired, and the --tier flag must - be omitted. + be omitted. --cpu and --memory flags are not compatible with the + Enterprise Plus edition. These flags should not be used when creating + an Enterprise Plus edition, as the machine configuration is determined + by the --tier flag instead. --network=NETWORK Network in the current project that the instance will be part of. To diff --git a/gcloud/beta/sql/instances/clone b/gcloud/beta/sql/instances/clone index e7996b99c..f6b23c3a7 100644 --- a/gcloud/beta/sql/instances/clone +++ b/gcloud/beta/sql/instances/clone @@ -33,28 +33,37 @@ EXAMPLES To clone an instance from its current state (most recent binary log coordinates): - $ gcloud beta sql instances clone instance-foo instance-bar + $ gcloud beta sql instances clone my-source-instance \ + my-cloned-instance To clone a MySQL instance from an earlier point in time (past binary log coordinates): - $ gcloud beta sql instances clone instance-foo instance-bar \ - --bin-log-file-name mysql-bin.000020 --bin-log-position 170 + $ gcloud beta sql instances clone my-source-instance \ + my-cloned-instance --bin-log-file-name mysql-bin.000020 \ + --bin-log-position 170 To clone a MySQL source instance at a specific point in time: - $ gcloud beta sql instances clone instance-foo instance-bar \ - --point-in-time '2012-11-15T16:19:00.094Z' + $ gcloud beta sql instances clone my-source-instance \ + my-cloned-instance --point-in-time '2012-11-15T16:19:00.094Z' To clone a PostgreSQL source instance at a specific point in time: - $ gcloud beta sql instances clone instance-foo instance-bar \ - --point-in-time '2012-11-15T16:19:00.094Z' + $ gcloud beta sql instances clone my-source-instance \ + my-cloned-instance --point-in-time '2012-11-15T16:19:00.094Z' To clone a SQL Server source instance at a specific point in time: - $ gcloud beta sql instances clone instance-foo instance-bar \ - --point-in-time '2012-11-15T16:19:00.094Z' + $ gcloud beta sql instances clone my-source-instance \ + my-cloned-instance --point-in-time '2012-11-15T16:19:00.094Z' + + To clone a deleted instance, include the name and deletion time of the + source instance: + + $ gcloud beta sql instances clone my-source-instance \ + my-cloned-instance \ + --source-instance-deletion-time '2012-11-15T16:19:00.094Z' POSITIONAL ARGUMENTS SOURCE diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index a4d605041..d8548705f 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -215,7 +215,10 @@ FLAGS --cpu=CPU Whole number value indicating how many cores are desired in the machine. Both --cpu and --memory must be specified if a custom machine - type is desired, and the --tier flag must be omitted. + type is desired, and the --tier flag must be omitted.--cpu and --memory + flags are not compatible with the Enterprise Plus edition. These flags + should not be used when creating an Enterprise Plus edition, as the + machine configuration is determined by the --tier flag instead. --custom-subject-alternative-names=DNS,[DNS,[DNS]] A comma-separated list of DNS names to add to the instance's SSL @@ -385,7 +388,10 @@ FLAGS machine. A size unit should be provided (eg. 3072MiB or 9GiB) - if no units are specified, GiB is assumed. Both --cpu and --memory must be specified if a custom machine type is desired, and the --tier flag must - be omitted. + be omitted. --cpu and --memory flags are not compatible with the + Enterprise Plus edition. These flags should not be used when creating + an Enterprise Plus edition, as the machine configuration is determined + by the --tier flag instead. --network=NETWORK Network in the current project that the instance will be part of. To diff --git a/gcloud/beta/sql/instances/get-latest-recovery-time b/gcloud/beta/sql/instances/get-latest-recovery-time index 70ee5407d..206c4c3bd 100644 --- a/gcloud/beta/sql/instances/get-latest-recovery-time +++ b/gcloud/beta/sql/instances/get-latest-recovery-time @@ -16,6 +16,11 @@ EXAMPLES $ gcloud beta sql instances get-latest-recovery-time instance-foo + To retrieve the latest recovery time for an instance that has been deleted: + + $ gcloud beta sql instances get-latest-recovery-time instance-foo \ + --source-instance-deletion-time '2012-11-15T16:19:00.094Z' + POSITIONAL ARGUMENTS INSTANCE Cloud SQL instance ID. diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index 82e6083ac..a2ec7e569 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -45,6 +45,7 @@ SYNOPSIS [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] [--pricing-plan=PRICING_PLAN, -p PRICING_PLAN] + [--reconcile-psa-networking] [--[no-]recreate-replicas-on-primary-crash] [--remove-deny-maintenance-period] [--replication=REPLICATION] [--replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE] @@ -164,7 +165,10 @@ FLAGS --cpu=CPU Whole number value indicating how many cores are desired in the machine. Both --cpu and --memory must be specified if a custom machine - type is desired, and the --tier flag must be omitted. + type is desired, and the --tier flag must be omitted.--cpu and --memory + flags are not compatible with the Enterprise Plus edition. These flags + should not be used when creating an Enterprise Plus edition, as the + machine configuration is determined by the --tier flag instead. --database-version=DATABASE_VERSION The database engine type and versions. If left unspecified, no changes @@ -342,7 +346,10 @@ FLAGS machine. A size unit should be provided (eg. 3072MiB or 9GiB) - if no units are specified, GiB is assumed. Both --cpu and --memory must be specified if a custom machine type is desired, and the --tier flag must - be omitted. + be omitted. --cpu and --memory flags are not compatible with the + Enterprise Plus edition. These flags should not be used when creating + an Enterprise Plus edition, as the machine configuration is determined + by the --tier flag instead. --network=NETWORK Network in the current project that the instance will be part of. To @@ -388,6 +395,12 @@ FLAGS First Generation instances only. The pricing plan for this instance. PRICING_PLAN must be one of: PER_USE, PACKAGE. + --reconcile-psa-networking + Reconciles the instance's PSA networking configuration. If the instance + is already on a PSA network, the DNS zone and records associated with + the PSA write endpoint are either added if missing or updated if + incorrect. + --[no-]recreate-replicas-on-primary-crash Allow/Disallow replica recreation when a primary MySQL instance operating in reduced durability mode crashes. Not recreating the diff --git a/gcloud/beta/sql/users/create b/gcloud/beta/sql/users/create index 9e905a7b2..891754c11 100644 --- a/gcloud/beta/sql/users/create +++ b/gcloud/beta/sql/users/create @@ -41,24 +41,20 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. - This flag is available only for MySQL. --[no-]password-policy-enable-failed-attempts-check - Enables the failed login attempts check if set to true. This flag is - available only for MySQL. Use + Enables the failed login attempts check if set to true. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. --[no-]password-policy-enable-password-verification - The current password must be specified when altering the password. This - flag is available only for MySQL. Use + The current password must be specified when altering the password. Use --password-policy-enable-password-verification to enable and --no-password-policy-enable-password-verification to disable. --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION Expiration duration after a password is updated, for example, 2d for 2 days. See gcloud topic datetimes for information on duration formats. - This flag is available only for MySQL. --type=TYPE Cloud SQL user's type. It determines the method to authenticate the diff --git a/gcloud/beta/sql/users/set-password-policy b/gcloud/beta/sql/users/set-password-policy index aee6b6a1f..d11596360 100644 --- a/gcloud/beta/sql/users/set-password-policy +++ b/gcloud/beta/sql/users/set-password-policy @@ -57,24 +57,20 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. - This flag is available only for MySQL. --[no-]password-policy-enable-failed-attempts-check - Enables the failed login attempts check if set to true. This flag is - available only for MySQL. Use + Enables the failed login attempts check if set to true. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. --[no-]password-policy-enable-password-verification - The current password must be specified when altering the password. This - flag is available only for MySQL. Use + The current password must be specified when altering the password. Use --password-policy-enable-password-verification to enable and --no-password-policy-enable-password-verification to disable. --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION Expiration duration after a password is updated, for example, 2d for 2 days. See gcloud topic datetimes for information on duration formats. - This flag is available only for MySQL. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/workstations/configs/create b/gcloud/beta/workstations/configs/create index 65207156a..7f11b36d8 100644 --- a/gcloud/beta/workstations/configs/create +++ b/gcloud/beta/workstations/configs/create @@ -23,10 +23,8 @@ SYNOPSIS [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] - [--network-tags=[NETWORK_TAGS,...]] - [--pd-disk-type=PD_DISK_TYPE; default="pd-standard"] - [--pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete"] - [--pool-size=POOL_SIZE] [--replica-zones=[REPLICA_ZONES,...]] + [--network-tags=[NETWORK_TAGS,...]] [--pool-size=POOL_SIZE] + [--replica-zones=[REPLICA_ZONES,...]] [--running-timeout=RUNNING_TIMEOUT; default=7200] [--service-account=SERVICE_ACCOUNT] [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] @@ -38,7 +36,9 @@ SYNOPSIS | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE; default="codeoss"] [--kms-key=KMS_KEY : --kms-key-service-account=KMS_KEY_SERVICE_ACCOUNT] - [--pd-disk-size=PD_DISK_SIZE; default=200 + [--no-persistent-storage | --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 ...] DESCRIPTION @@ -272,7 +272,37 @@ FLAGS the root VM. --ephemeral-directory=[PROPERTY=VALUE,...] - Ephemeral directory which won't persist across workstation sessions. + Ephemeral directory which won't persist across workstation sessions. An + ephemeral directory is backed by a Compute Engine persistent disk whose + mount-path, source-snapshot, source-image, and read-only are + configurable. + + mount-path + Location of this directory in the running workstation. + + source-snapshot + Name of the snapshot to use as the source for the disk. Must be + empty if [source_image][] is set. Must be empty if [read_only][] is + false. Updating [source_snapshot][] will update content in the + ephemeral directory after the workstation is restarted. + + source-image + Name of the disk image to use as the source for the disk. Must be + empty if [source_snapshot][] is set. Updating [source_image][] will + update content in the ephemeral directory after the workstation is + restarted. + + read-only + Whether the disk is read only. If true, the disk may be shared by + multiple VMs and [source_snapshot][] must be set. Set to false when + not specified and true when specified. + + Example: + + $ gcloud beta workstations configs create \ + --ephemeral-directory="mount-path=/home2,disk-type=pd-balanced,s\ + ource-snapshot=projects/my-project/global/snapshots/snapshot,read-on\ + ly=true" --grant-workstation-admin-role-on-create Default value is false. If set, creator of a workstation will get @@ -313,20 +343,6 @@ FLAGS $ gcloud beta workstations configs create --network-tags=tag_1,tag_2 - --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. - --pool-size=POOL_SIZE Number of instances to pool for faster Workstation startup. @@ -441,12 +457,34 @@ FLAGS 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. + --no-persistent-storage + If set, workstations under this configuration will not have a + persistent directory. - --pd-source-snapshot=PD_SOURCE_SNAPSHOT - Name of the snapshot to use as the source for the home disk. + 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-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/bigtable/instances/tables/create b/gcloud/bigtable/instances/tables/create index b48d0c163..4caf810c5 100644 --- a/gcloud/bigtable/instances/tables/create +++ b/gcloud/bigtable/instances/tables/create @@ -113,7 +113,7 @@ REQUIRED FLAGS --column-families=[COLUMN_FAMILIES,...] A double-quote (") wrapped list of family name and corresponding garbage collection rules concatenated by :, where the rules are - optional. For example: \ + optional. For example: "family_1,family_2:maxage=5d&&maxversions=2,family_3:maxage=10d||maxversions=5" OPTIONAL FLAGS diff --git a/gcloud/bigtable/tables/create b/gcloud/bigtable/tables/create index 166da8d7d..db1092c4c 100644 --- a/gcloud/bigtable/tables/create +++ b/gcloud/bigtable/tables/create @@ -107,7 +107,7 @@ REQUIRED FLAGS --column-families=[COLUMN_FAMILIES,...] A double-quote (") wrapped list of family name and corresponding garbage collection rules concatenated by :, where the rules are - optional. For example: \ + optional. For example: "family_1,family_2:maxage=5d&&maxversions=2,family_3:maxage=10d||maxversions=5" OPTIONAL FLAGS diff --git a/gcloud/colab/runtime-templates/create b/gcloud/colab/runtime-templates/create index 68c973414..b01bfc12a 100644 --- a/gcloud/colab/runtime-templates/create +++ b/gcloud/colab/runtime-templates/create @@ -14,11 +14,7 @@ SYNOPSIS : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] --no-enable-internet-access --network=NETWORK [--subnetwork=SUBNETWORK - : --subnetwork-region=SUBNETWORK_REGION] - --post-startup-script=POST_STARTUP_SCRIPT - --post-startup-script-behavior=POST_STARTUP_SCRIPT_BEHAVIOR - --post-startup-script-url=POST_STARTUP_SCRIPT_URL - --set-env-vars=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + : --subnetwork-region=SUBNETWORK_REGION]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a Colab Enterprise runtime template, a VM configuration for your @@ -216,25 +212,6 @@ OPTIONAL FLAGS fully specified name; ◇ provide the argument --subnetwork-region on the command line. - The software configuration of the runtime template. - - --post-startup-script=POST_STARTUP_SCRIPT - Post startup script in raw string to execute on the runtime. - - --post-startup-script-behavior=POST_STARTUP_SCRIPT_BEHAVIOR - The behavior of the post startup script. The default if passing a - post-startup-script-url is RUN_ONCE. POST_STARTUP_SCRIPT_BEHAVIOR - must be one of: POST_STARTUP_SCRIPT_BEHAVIOR_UNSPECIFIED, RUN_ONCE, - RUN_EVERY_START, DOWNLOAD_AND_RUN_EVERY_START. - - --post-startup-script-url=POST_STARTUP_SCRIPT_URL - Post startup script URL to execute on the runtime. This can be a - public or private Google Cloud Storage object. In the form of - gs://bucket/object or https://storage.googleapis.com/bucket/object. - - --set-env-vars=[KEY=VALUE,...] - Set environment variables used by the runtime. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/compute/backend-buckets/create b/gcloud/compute/backend-buckets/create index 9cb5d7763..097e4bbff 100644 --- a/gcloud/compute/backend-buckets/create +++ b/gcloud/compute/backend-buckets/create @@ -11,7 +11,8 @@ SYNOPSIS [--compression-mode=COMPRESSION_MODE] [--custom-response-header=CUSTOM_RESPONSE_HEADER] [--default-ttl=DEFAULT_TTL] [--description=DESCRIPTION] - [--[no-]enable-cdn] [--max-ttl=MAX_TTL] [--[no-]negative-caching] + [--[no-]enable-cdn] [--load-balancing-scheme=LOAD_BALANCING_SCHEME] + [--max-ttl=MAX_TTL] [--[no-]negative-caching] [--negative-caching-policy=[[CODE=TTL],...]] [--[no-]request-coalescing] [--serve-while-stale=SERVE_WHILE_STALE] [--signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE] @@ -157,6 +158,12 @@ OPTIONAL FLAGS responses from a backend bucket at the edge of the network, close to users. Use --enable-cdn to enable and --no-enable-cdn to disable. + --load-balancing-scheme=LOAD_BALANCING_SCHEME + The load balancing scheme of the backend bucket. If left blank, the + backend bucket will be compatible with Global External Application Load + Balancer or Classic Application Load Balancer. LOAD_BALANCING_SCHEME + must be (only one value is supported): INTERNAL_MANAGED. + --max-ttl=MAX_TTL Specifies the maximum allowed TTL for cached content served by this origin. diff --git a/gcloud/compute/backend-services/create b/gcloud/compute/backend-services/create index 1eb430dc1..f1b2d76ec 100644 --- a/gcloud/compute/backend-services/create +++ b/gcloud/compute/backend-services/create @@ -531,12 +531,10 @@ FLAGS Load Balancer), the protocol must be one of: TCP, UDP, UNSPECIFIED. If the load-balancing-scheme is INTERNAL_SELF_MANAGED (Traffic - Director), the protocol must be one of: HTTP, HTTPS, HTTP2, GRPC, H2C - (beta only). + Director), the protocol must be one of: HTTP, HTTPS, HTTP2, GRPC, H2C. If the load-balancing-scheme is INTERNAL_MANAGED (Internal Application - Load Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C - (beta only). + Load Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C. If the load-balancing-scheme is INTERNAL_MANAGED (Internal proxy Network Load Balancer), the protocol must be only TCP. @@ -551,8 +549,7 @@ FLAGS If the load-balancing-scheme is EXTERNAL_MANAGED (Global external Application Load Balancer and regional external Application Load - Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C (beta - only). + Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C. If the load-balancing-scheme is EXTERNAL_MANAGED (Global external proxy Network Load Balancer), the protocol must be one of: TCP, SSL. diff --git a/gcloud/compute/backend-services/update b/gcloud/compute/backend-services/update index b2a6295b5..ea2f11d06 100644 --- a/gcloud/compute/backend-services/update +++ b/gcloud/compute/backend-services/update @@ -372,12 +372,10 @@ FLAGS Load Balancer), the protocol must be one of: TCP, UDP, UNSPECIFIED. If the load-balancing-scheme is INTERNAL_SELF_MANAGED (Traffic - Director), the protocol must be one of: HTTP, HTTPS, HTTP2, GRPC, H2C - (beta only). + Director), the protocol must be one of: HTTP, HTTPS, HTTP2, GRPC, H2C. If the load-balancing-scheme is INTERNAL_MANAGED (Internal Application - Load Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C - (beta only). + Load Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C. If the load-balancing-scheme is INTERNAL_MANAGED (Internal proxy Network Load Balancer), the protocol must be only TCP. @@ -392,8 +390,7 @@ FLAGS If the load-balancing-scheme is EXTERNAL_MANAGED (Global external Application Load Balancer and regional external Application Load - Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C (beta - only). + Balancer), the protocol must be one of: HTTP, HTTPS, HTTP2, H2C. If the load-balancing-scheme is EXTERNAL_MANAGED (Global external proxy Network Load Balancer), the protocol must be one of: TCP, SSL. diff --git a/gcloud/compute/commitments/create b/gcloud/compute/commitments/create index 48a2df4b8..d160d33d4 100644 --- a/gcloud/compute/commitments/create +++ b/gcloud/compute/commitments/create @@ -110,7 +110,7 @@ OPTIONAL FLAGS general-purpose-c4d, general-purpose-e2, general-purpose-n2, general-purpose-n2d, general-purpose-n4, general-purpose-t2d, graphics-optimized, memory-optimized, memory-optimized-m3, - memory-optimized-m4, memory-optimized-x4-16tb, + memory-optimized-m4, memory-optimized-m4-6tb, memory-optimized-x4-16tb, memory-optimized-x4-24tb, memory-optimized-x4-32tb, storage-optimized-z3. diff --git a/gcloud/compute/instance-groups/managed/create b/gcloud/compute/instance-groups/managed/create index 48e65362d..b097328f2 100644 --- a/gcloud/compute/instance-groups/managed/create +++ b/gcloud/compute/instance-groups/managed/create @@ -21,7 +21,7 @@ SYNOPSIS [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] [--stopped-size=STOPPED_SIZE] [--suspended-size=SUSPENDED_SIZE] [--target-distribution-shape=SHAPE] [--target-pool=[TARGET_POOL,...]] - [--zones=ZONE,[ZONE,...]] + [--workload-policy=WORKLOAD_POLICY] [--zones=ZONE,[ZONE,...]] [--health-check=HEALTH_CHECK | --http-health-check=HTTP_HEALTH_CHECK | --https-health-check=HTTPS_HEALTH_CHECK] [--region=REGION | --zone=ZONE] @@ -301,6 +301,11 @@ OPTIONAL FLAGS Specifies any target pools you want the instances of this managed instance group to be part of. + --workload-policy=WORKLOAD_POLICY + Specifies the workload policy for the managed instance group. It can be + a full or partial URL to a resource policy containing the workload + policy. + --zones=ZONE,[ZONE,...] If this flag is specified a regional managed instance group will be created. The managed instance group will be in the same region as diff --git a/gcloud/compute/instance-groups/managed/update b/gcloud/compute/instance-groups/managed/update index 2fcd57583..4c7a3daa0 100644 --- a/gcloud/compute/instance-groups/managed/update +++ b/gcloud/compute/instance-groups/managed/update @@ -30,6 +30,7 @@ SYNOPSIS | --http-health-check=HTTP_HEALTH_CHECK | --https-health-check=HTTPS_HEALTH_CHECK] [--region=REGION | --zone=ZONE] + [--remove-workload-policy | --workload-policy=WORKLOAD_POLICY] [--update-policy-max-surge=MAX_SURGE --update-policy-max-unavailable=MAX_UNAVAILABLE --update-policy-minimal-action=UPDATE_POLICY_MINIMAL_ACTION @@ -369,6 +370,16 @@ FLAGS Overrides the default compute/zone property value for this command invocation. + At most one of these can be specified: + + --remove-workload-policy + Detaches the workload policy from the managed instance group. + + --workload-policy=WORKLOAD_POLICY + Specifies the workload policy for the managed instance group. It can + be a full or partial URL to a resource policy containing the workload + policy. + Parameters for setting update policy for this managed instance group. --update-policy-max-surge=MAX_SURGE diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index 47004c56f..d348adda9 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -119,8 +119,7 @@ FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the diff --git a/gcloud/compute/instance-templates/create-with-container b/gcloud/compute/instance-templates/create-with-container index 62cdf40be..8f27c116c 100644 --- a/gcloud/compute/instance-templates/create-with-container +++ b/gcloud/compute/instance-templates/create-with-container @@ -38,7 +38,8 @@ SYNOPSIS [--network-interface=[PROPERTY=VALUE,...]] [--network-tier=NETWORK_TIER] [--preemptible] [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] - [--private-network-ip=PRIVATE_NETWORK_IP] [--region=REGION] + [--private-network-ip=PRIVATE_NETWORK_IP] + [--provisioning-model=PROVISIONING_MODEL] [--region=REGION] [--resource-policies=[RESOURCE_POLICY,...]] [--no-restart-on-failure] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--stack-type=STACK_TYPE] [--subnet=SUBNET] @@ -105,8 +106,7 @@ FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the @@ -641,6 +641,24 @@ FLAGS Specifies the RFC1918 IP to assign to the instance. The IP should be in the subnet or legacy network IP range. + --provisioning-model=PROVISIONING_MODEL + Specifies the provisioning model for your VM instances. This choice + affects the price, availability, and how long your VM instances can + run. PROVISIONING_MODEL must be one of: + + RESERVATION_BOUND + The VM instances run for the entire duration of their associated + reservation. You can only specify this provisioning model if you + want your VM instances to consume a specific reservation with + either a calendar reservation mode or a dense deployment type. + SPOT + Compute Engine may stop a Spot VM instance whenever it needs + capacity. Because Spot VM instances don't have a guaranteed + runtime, they come at a discounted price. + STANDARD + The default option. The STANDARD provisioning model gives you full + control over your VM instances' runtime. + --region=REGION Region of the instance template to create. If not specified, you might be prompted to select a region (interactive mode only). diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index d716f55f1..2769835db 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -169,8 +169,7 @@ OPTIONAL FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index ae1f47582..42ea2fbb6 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -182,8 +182,7 @@ FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index e26aee77c..f5ff7d28a 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -134,8 +134,7 @@ FLAGS --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number - of I/O operations per second that the disk can handle. Value must be - between 10,000 and 120,000. + of I/O operations per second that the disk can handle. --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT Indicates how much throughput to provision for the disk. This sets the diff --git a/gcloud/compute/interconnects/attachments/groups/update b/gcloud/compute/interconnects/attachments/groups/update index 4dfca801d..deb491736 100644 --- a/gcloud/compute/interconnects/attachments/groups/update +++ b/gcloud/compute/interconnects/attachments/groups/update @@ -7,7 +7,7 @@ SYNOPSIS [--attachments=[INTERCONNECT_ATTACHMENT,...]] [--description=DESCRIPTION] [--intended-availability-sla=INTENDED_AVAILABILITY_SLA] - [GCLOUD_WIDE_FLAG ...] + [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute interconnects attachments groups update is used to update @@ -35,7 +35,8 @@ EXAMPLES $ gcloud compute interconnects attachments groups update \ example-attachment-group \ - --attachments=region-1/attachment-1,region-2/attachment-2 + --attachments=region-1/attachment-1,region-2/attachment-2 \ + --update-mask=attachments Although you can add or remove member attachments using this command, it is recommended to add or remove member attachments using the add-members and @@ -56,6 +57,11 @@ FLAGS --intended-availability-sla=INTENDED_AVAILABILITY_SLA The availability SLA that the user intends this group to support. + --update-mask=UPDATE_MASK + Optional update mask to specify which fields to update. Use commas to + separate masks. If not specified, all fields present in the command + will be updated. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/compute/interconnects/create b/gcloud/compute/interconnects/create index 1934a7b42..392cc14bf 100644 --- a/gcloud/compute/interconnects/create +++ b/gcloud/compute/interconnects/create @@ -103,6 +103,10 @@ OPTIONAL FLAGS If specified then the interconnect is created on Cross-Site Network capable hardware ports. This parameter can only be provided during interconnect INSERT and cannot be changed using interconnect PATCH. + L2_FORWARDING + If specified then the interconnect is created on L2 forwarding + capable hardware ports. This parameter can only be provided during + interconnect INSERT and cannot be changed using interconnect PATCH. MACSEC If specified then the interconnect is created on MACsec capable hardware ports. If not specified, the interconnect is created on diff --git a/gcloud/compute/interconnects/groups/create-members b/gcloud/compute/interconnects/groups/create-members index 016017d26..8c6f96b1f 100644 --- a/gcloud/compute/interconnects/groups/create-members +++ b/gcloud/compute/interconnects/groups/create-members @@ -110,6 +110,10 @@ OPTIONAL FLAGS If specified then the interconnect is created on Cross-Site Network capable hardware ports. This parameter can only be provided during interconnect INSERT and cannot be changed using interconnect PATCH. + L2_FORWARDING + If specified then the interconnect is created on L2 forwarding + capable hardware ports. This parameter can only be provided during + interconnect INSERT and cannot be changed using interconnect PATCH. MACSEC If specified then the interconnect is created on MACsec capable hardware ports. If not specified, the interconnect is created on diff --git a/gcloud/compute/interconnects/groups/update b/gcloud/compute/interconnects/groups/update index 78e53f416..c1ab3a0a3 100644 --- a/gcloud/compute/interconnects/groups/update +++ b/gcloud/compute/interconnects/groups/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud compute interconnects groups update NAME [--description=DESCRIPTION] [--intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY] - [--interconnects=[INTERCONNECT,...]] [GCLOUD_WIDE_FLAG ...] + [--interconnects=[INTERCONNECT,...]] [--update-mask=UPDATE_MASK] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute interconnects groups update is used to update interconnect @@ -33,7 +34,8 @@ EXAMPLES $ gcloud compute interconnects groups update \ example-interconnect-group \ - --interconnects=interconnect-1,interconnect-2 + --interconnects=interconnect-1,interconnect-2 \ + --update-mask=interconnects Although you can add or remove member interconnects using this command, it is recommended to add or remove member interconnects using the add-members @@ -54,6 +56,11 @@ FLAGS --interconnects=[INTERCONNECT,...] Member interconnects to set the interconnect group to contain. + --update-mask=UPDATE_MASK + Optional update mask to specify which fields to update. Use commas to + separate masks. If not specified, all fields present in the command + will be updated. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/compute/reservations/help b/gcloud/compute/reservations/help index d358d0e04..2233963e1 100644 --- a/gcloud/compute/reservations/help +++ b/gcloud/compute/reservations/help @@ -24,6 +24,9 @@ GROUPS blocks Manage Compute Engine reservation blocks. + sub-blocks + Manage Compute Engine reservation sub blocks. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/compute/reservations/sub-blocks/describe b/gcloud/compute/reservations/sub-blocks/describe new file mode 100644 index 000000000..deefaf295 --- /dev/null +++ b/gcloud/compute/reservations/sub-blocks/describe @@ -0,0 +1,68 @@ +NAME + gcloud compute reservations sub-blocks describe - describe a Compute Engine + reservation sub block + +SYNOPSIS + gcloud compute reservations sub-blocks describe RESERVATION + --block-name=BLOCK_NAME --sub-block-name=SUB_BLOCK_NAME [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Compute Engine reservation sub block. + +EXAMPLES + To describe a reservation sub block in reservation exr1 in my-zone with + block name my-block and sub block name my-sub-block, run: + + $ gcloud compute reservations sub-blocks describe exr1 \ + --zone=my-zone --block-name=my-block \ + --sub-block-name=my-sub-block + +POSITIONAL ARGUMENTS + RESERVATION + Name of the reservation to describe. + +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. + +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 + These variants are also available: + + $ gcloud alpha compute reservations sub-blocks describe + + $ gcloud beta compute reservations sub-blocks describe + diff --git a/gcloud/compute/reservations/sub-blocks/help b/gcloud/compute/reservations/sub-blocks/help new file mode 100644 index 000000000..56878943c --- /dev/null +++ b/gcloud/compute/reservations/sub-blocks/help @@ -0,0 +1,31 @@ +NAME + gcloud compute reservations sub-blocks - manage Compute Engine reservation + sub blocks + +SYNOPSIS + gcloud compute reservations sub-blocks COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Compute Engine reservation sub blocks. + +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 a Compute Engine reservation sub block. + + list + List Compute Engine reservation sub blocks. + +NOTES + These variants are also available: + + $ gcloud alpha compute reservations sub-blocks + + $ gcloud beta compute reservations sub-blocks + diff --git a/gcloud/compute/reservations/sub-blocks/list b/gcloud/compute/reservations/sub-blocks/list new file mode 100644 index 000000000..cb553de9d --- /dev/null +++ b/gcloud/compute/reservations/sub-blocks/list @@ -0,0 +1,104 @@ +NAME + gcloud compute reservations sub-blocks list - list Compute Engine + reservation sub blocks + +SYNOPSIS + gcloud compute reservations sub-blocks list RESERVATION + --block-name=BLOCK_NAME [--zone=ZONE] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute reservations sub-blocks list displays all Compute Engine + reservation sub blocks in an extended reservation's block. + +EXAMPLES + To list all reservation sub blocks in an extended reservation's block + my-block in table form, run: + + $ gcloud compute reservations sub-blocks list extended-reservation \ + --block-name=my-block --zone=us-central1-a --project=my-project + + To list the URIs of all reservation blocks in an extended reservation, run: + + $ gcloud compute reservations sub-blocks list extended-reservation \ + --block-name=my-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. + +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 + These variants are also available: + + $ gcloud alpha compute reservations sub-blocks list + + $ gcloud beta compute reservations sub-blocks list + diff --git a/gcloud/compute/resource-policies/create/group-placement b/gcloud/compute/resource-policies/create/group-placement index 2fe859252..0afcfe374 100644 --- a/gcloud/compute/resource-policies/create/group-placement +++ b/gcloud/compute/resource-policies/create/group-placement @@ -6,7 +6,8 @@ SYNOPSIS gcloud compute resource-policies create group-placement NAME [--availability-domain-count=AVAILABILITY_DOMAIN_COUNT] [--collocation=COLLOCATION] [--description=DESCRIPTION] - [--region=REGION] [--vm-count=VM_COUNT] [GCLOUD_WIDE_FLAG ...] + [--gpu-topology=GPU_TOPOLOGY] [--region=REGION] [--vm-count=VM_COUNT] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a Compute Engine Group Placement Resource Policy. @@ -38,6 +39,10 @@ FLAGS --description=DESCRIPTION An optional, textual description for the backend. + --gpu-topology=GPU_TOPOLOGY + Specifies the shape of the GPU slice, in slice based GPU families eg. + A4X. + --region=REGION Region of the resource policy to operate on. If not specified, you might be prompted to select a region (interactive mode only). diff --git a/gcloud/compute/resource-policies/create/help b/gcloud/compute/resource-policies/create/help index 792742196..8d95c37ee 100644 --- a/gcloud/compute/resource-policies/create/help +++ b/gcloud/compute/resource-policies/create/help @@ -28,6 +28,9 @@ COMMANDS snapshot-schedule Create a Compute Engine Snapshot Schedule Resource Policy. + workload-policy + Create a Compute Engine workload resource policy. + NOTES These variants are also available: diff --git a/gcloud/compute/resource-policies/create/workload-policy b/gcloud/compute/resource-policies/create/workload-policy new file mode 100644 index 000000000..510b2b896 --- /dev/null +++ b/gcloud/compute/resource-policies/create/workload-policy @@ -0,0 +1,100 @@ +NAME + gcloud compute resource-policies create workload-policy - create a Compute + Engine workload resource policy + +SYNOPSIS + gcloud compute resource-policies create workload-policy NAME --type=TYPE + [--description=DESCRIPTION] [--region=REGION] + [--accelerator-topology=ACCELERATOR_TOPOLOGY + | --max-topology-distance=MAX_TOPOLOGY_DISTANCE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Compute Engine workload resource policy. + +EXAMPLES + To create a workload policy: + + $ gcloud compute resource-policies create workload-policy NAME \ + --type=TYPE + +POSITIONAL ARGUMENTS + NAME + Name of the resource policy to operate on. + +REQUIRED FLAGS + --type=TYPE + Type of the workload policy defining the high-level intent of the + cluster. TYPE must be one of: + + HIGH_AVAILABILITY + For workloads that aim to be highly available. Common examples are + web / ML serving, or distributed database clusters. Compute Engine + spreads VMs at best-effort to improve reliability of the + distributed infrastructure. + HIGH_THROUGHPUT + For high throughput distributed workloads eg. HPC or ML training. + Compute Engine collocates VMs at best-effort to reduce network + latency between VMs. + +OPTIONAL FLAGS + --description=DESCRIPTION + An optional, textual description for the backend. + + --region=REGION + Region of the resource policy to operate on. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + At most one of these can be specified: + + --accelerator-topology=ACCELERATOR_TOPOLOGY + Specifies the topology of placement and interconnection performance + required to create a slice of VMs with interconnected accelerators. + + --max-topology-distance=MAX_TOPOLOGY_DISTANCE + Specifies the topology of placement and interconnection network + performance of the group of VMs (MIG / Multi-MIGs). + MAX_TOPOLOGY_DISTANCE must be one of: + + BLOCK + VMs are placed within the same block of capacity with improved + latency compared to Cluster. + CLUSTER + VMs are placed within the same cluster of capacity with improved + latency between them. + SUBBLOCK + Tightest collocation of VMs that provides minimized network + latency. VMs are placed within the same rack of capacity with + improved latency compared to Block. + +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 compute resource-policies create workload-policy + + $ gcloud beta compute resource-policies create workload-policy + diff --git a/gcloud/config/get b/gcloud/config/get index a50dde015..74f557462 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -486,13 +486,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -501,6 +502,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/config/help b/gcloud/config/help index 86efc1a4f..60c9fc72d 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -518,13 +518,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -533,6 +534,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/config/list b/gcloud/config/list index 3f55d1662..446c28300 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -530,13 +530,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -545,6 +546,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/config/set b/gcloud/config/set index 5effaea23..4cd16fd8d 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -533,13 +533,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -548,6 +549,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/config/unset b/gcloud/config/unset index e68505a93..6f54e73f5 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -494,13 +494,14 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud notebooks command group. Defaults to https://notebooks.googleapis.com/ + observability + Overrides API endpoint for gcloud observability command group. + Defaults to https://observability.googleapis.com/ + orgpolicy Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ - pam - Overrides API endpoint for gcloud pam command group. - policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ @@ -509,6 +510,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud privateca command group. Defaults to https://privateca.googleapis.com/ + privilegedaccessmanager + Overrides API endpoint for gcloud pam command group. Defaults to + https://privilegedaccessmanager.googleapis.com/ + publicca Overrides API endpoint for gcloud publicca command group. Defaults to https://publicca.googleapis.com/ diff --git a/gcloud/container/clusters/check-autopilot-compatibility b/gcloud/container/clusters/check-autopilot-compatibility index 0eeef6097..ae153545a 100644 --- a/gcloud/container/clusters/check-autopilot-compatibility +++ b/gcloud/container/clusters/check-autopilot-compatibility @@ -11,6 +11,13 @@ SYNOPSIS DESCRIPTION Check autopilot compatibility of a running cluster. + For clusters with GKE version 1.31.6-gke.1027000 or later, you must enable + the control plane component that performs the check by running the gcloud + container clusters update command with the + `--enable-autopilot-compatiblity-auditing` + (https://cloud.google.com/sdk/gcloud/reference/container/clusters/update#--%5Bno-%5Denable-autopilot-compatibility-auditing) + flag. + EXAMPLES To check autopilot compatibility of an existing cluster, run: diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 5e1f4fb68..e413c3b6a 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -9,8 +9,10 @@ SYNOPSIS gpu-sharing-strategy=GPU_SHARING_STRATEGY, max-shared-clients-per-gpu=MAX_SHARED_CLIENTS_PER_GPU],...]] [--additional-zones=ZONE,[ZONE,...]] - [--addons=[ADDON[=ENABLED|DISABLED],...]] [--async] - [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] + [--addons=[ADDON[=ENABLED|DISABLED],...]] + [--alpha-cluster-feature-gates=[FEATURE=true|false,...]] + [--anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG] + [--async] [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] [--autoprovisioning-enable-insecure-kubelet-readonly-port] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] @@ -68,6 +70,7 @@ SYNOPSIS [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] [--notification-config=[pubsub=ENABLED|DISABLED, pubsub-topic=TOPIC,...]] [--num-nodes=NUM_NODES; default=3] + [--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT] [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] [--preemptible] [--private-endpoint-subnetwork=NAME] [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] @@ -230,6 +233,28 @@ FLAGS GcePersistentDiskCsiDriver, GcpFilestoreCsiDriver, BackupRestore, GcsFuseCsiDriver, ParallelstoreCsiDriver, RayOperator, CloudRun. + --alpha-cluster-feature-gates=[FEATURE=true|false,...] + Selectively enable or disable Kubernetes alpha and beta + kubernetesfeature gates on alpha GKE cluster. Alpha clusters are not + covered by the Kubernetes Engine SLA and should not be used for + production workloads. + + --anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG + Enable or restrict anonymous access to the cluster. When enabled, + anonymous users will be authenticated as system:anonymous with the + group system:unauthenticated. Limiting access restricts anonymous + access to only the health check endpoints /readyz, /livez, and + /healthz. + + ANONYMOUS_AUTHENTICATION_CONFIG must be one of: + + ENABLED + 'ENABLED' enables anonymous calls. + LIMITED + 'LIMITED' restricts anonymous access to the cluster. Only calls to + the health check endpoints are allowed anonymously, all other calls + will be rejected. + --async Return immediately, without waiting for the operation in progress to complete. @@ -1040,6 +1065,19 @@ FLAGS --num-nodes=NUM_NODES; default=3 The number of nodes to be created in each of the cluster's zones. + --performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT + Sets the Performance Monitoring Unit level. Valid values are + architectural, standard and enhanced. PERFORMANCE_MONITORING_UNIT must + be one of: + + architectural + Enables architectural PMU events tied to non last level cache (LLC) + events. + enhanced + Enables most documented core/L2 and LLC PMU events. + standard + Enables most documented core/L2 PMU events. + --placement-policy=PLACEMENT_POLICY Indicates the desired resource policy to use. diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 7d2cec798..e55cedf80 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -3,8 +3,9 @@ NAME running containers SYNOPSIS - gcloud container clusters create-auto NAME [--async] - [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] + gcloud container clusters create-auto NAME + [--anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG] + [--async] [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] [--autoprovisioning-enable-insecure-kubelet-readonly-port] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] @@ -71,6 +72,22 @@ POSITIONAL ARGUMENTS 40 characters. FLAGS + --anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG + Enable or restrict anonymous access to the cluster. When enabled, + anonymous users will be authenticated as system:anonymous with the + group system:unauthenticated. Limiting access restricts anonymous + access to only the health check endpoints /readyz, /livez, and + /healthz. + + ANONYMOUS_AUTHENTICATION_CONFIG must be one of: + + ENABLED + 'ENABLED' enables anonymous calls. + LIMITED + 'LIMITED' restricts anonymous access to the cluster. Only calls to + the health check endpoints are allowed anonymously, all other calls + will be rejected. + --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index d896f0729..b1e3a84bb 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud container clusters update NAME - (--autoprovisioning-cgroup-mode=AUTOPROVISIONING_CGROUP_MODE + (--anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG + | --autoprovisioning-cgroup-mode=AUTOPROVISIONING_CGROUP_MODE | --autoprovisioning-enable-insecure-kubelet-readonly-port | --autoprovisioning-network-tags=[TAGS,...] | --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] @@ -130,6 +131,22 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Exactly one of these must be specified: + --anonymous-authentication-config=ANONYMOUS_AUTHENTICATION_CONFIG + Enable or restrict anonymous access to the cluster. When enabled, + anonymous users will be authenticated as system:anonymous with the + group system:unauthenticated. Limiting access restricts anonymous + access to only the health check endpoints /readyz, /livez, and + /healthz. + + ANONYMOUS_AUTHENTICATION_CONFIG must be one of: + + ENABLED + 'ENABLED' enables anonymous calls. + LIMITED + 'LIMITED' restricts anonymous access to the cluster. Only calls + to the health check endpoints are allowed anonymously, all other + calls will be rejected. + --autoprovisioning-cgroup-mode=AUTOPROVISIONING_CGROUP_MODE Sets the cgroup mode for auto-provisioned nodes. @@ -304,10 +321,16 @@ REQUIRED FLAGS https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity --[no-]enable-autopilot-compatibility-auditing - Enables the Autopilot Compatibility Auditing Feature. See - https://cloud.google.com/sdk/gcloud/reference/container/clusters/check-autopilot-compatibility. - Only applicable to clusters with version >= 1.32. Use - --enable-autopilot-compatibility-auditing to enable and + Lets you run the gcloud container clusters + check-autopilot-compatibility + (https://cloud.google.com/sdk/gcloud/reference/container/clusters/check-autopilot-compatibility) + command to check whether your workloads are compatible with Autopilot + mode. This flag is only applicable to clusters that run version + 1.31.6-gke.1027000 or later. + + Note: This flag causes a control plane restart. + + Use --enable-autopilot-compatibility-auditing to enable and --no-enable-autopilot-compatibility-auditing to disable. --enable-autoscaling diff --git a/gcloud/container/fleet/help b/gcloud/container/fleet/help index 5d8320c60..9a3de19fe 100644 --- a/gcloud/container/fleet/help +++ b/gcloud/container/fleet/help @@ -82,6 +82,9 @@ GROUPS policycontroller Manage Policy Controller Feature. + rbacrolebindingactuation + Manage RbacRoleBinding Actuation. + scopes Manage scopes of all your GKE fleets. diff --git a/gcloud/container/fleet/rbacrolebindingactuation/describe b/gcloud/container/fleet/rbacrolebindingactuation/describe new file mode 100644 index 000000000..886528568 --- /dev/null +++ b/gcloud/container/fleet/rbacrolebindingactuation/describe @@ -0,0 +1,23 @@ +NAME + gcloud container fleet rbacrolebindingactuation describe - describe the + status of the RbacRoleBinding Actuation Feature in a fleet + +SYNOPSIS + gcloud container fleet rbacrolebindingactuation describe + [GCLOUD_WIDE_FLAG ...] + +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 container fleet rbacrolebindingactuation describe + + $ gcloud beta container fleet rbacrolebindingactuation describe + diff --git a/gcloud/container/fleet/rbacrolebindingactuation/help b/gcloud/container/fleet/rbacrolebindingactuation/help new file mode 100644 index 000000000..2051ae553 --- /dev/null +++ b/gcloud/container/fleet/rbacrolebindingactuation/help @@ -0,0 +1,33 @@ +NAME + gcloud container fleet rbacrolebindingactuation - manage RbacRoleBinding + Actuation + +SYNOPSIS + gcloud container fleet rbacrolebindingactuation COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage RbacRoleBinding Actuation. + +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 the status of the RbacRoleBinding Actuation Feature in a + fleet. + + update + Update RbacRoleBinding Actuation Feature. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet rbacrolebindingactuation + + $ gcloud beta container fleet rbacrolebindingactuation + diff --git a/gcloud/container/fleet/rbacrolebindingactuation/update b/gcloud/container/fleet/rbacrolebindingactuation/update new file mode 100644 index 000000000..0f5af52de --- /dev/null +++ b/gcloud/container/fleet/rbacrolebindingactuation/update @@ -0,0 +1,54 @@ +NAME + gcloud container fleet rbacrolebindingactuation update - update + RbacRoleBinding Actuation Feature + +SYNOPSIS + gcloud container fleet rbacrolebindingactuation update + (--add-allowed-custom-role=ADD_ALLOWED_CUSTOM_ROLE + | --allowed-custom-roles=[ROLES,...] + | --remove-allowed-custom-role=REMOVE_ALLOWED_CUSTOM_ROLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command updates RbacRoleBinding Actuation Feature in a fleet. + +EXAMPLES + To update the RbacRoleBinding Actuation Feature, run: + + $ gcloud container fleet rbacrolebinding-actuation update \ + --allowed-custom-roles=role1,role2 + + $ gcloud container fleet rbacrolebinding-actuation update \ + --add-allowed-custom-role=role1 + + $ gcloud container fleet rbacrolebinding-actuation update \ + --remove-allowed-custom-role=role2 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --add-allowed-custom-role=ADD_ALLOWED_CUSTOM_ROLE + Add a single custom role to the allowed custom roles list. + + --allowed-custom-roles=[ROLES,...] + The list of allowed custom roles that can be used in scope + RBACRoleBindings. + + --remove-allowed-custom-role=REMOVE_ALLOWED_CUSTOM_ROLE + Remove a single custom role from the allowed custom roles list. + +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 container fleet rbacrolebindingactuation update + + $ gcloud beta container fleet rbacrolebindingactuation update + diff --git a/gcloud/container/fleet/scopes/rbacrolebindings/create b/gcloud/container/fleet/scopes/rbacrolebindings/create index 47914123d..034ba8e3f 100644 --- a/gcloud/container/fleet/scopes/rbacrolebindings/create +++ b/gcloud/container/fleet/scopes/rbacrolebindings/create @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud container fleet scopes rbacrolebindings create - (NAME : --location=LOCATION --scope=SCOPE) --role=ROLE - (--group=GROUP | --user=USER) [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + (NAME : --location=LOCATION --scope=SCOPE) + (--custom-role=CUSTOM_ROLE | --role=ROLE) (--group=GROUP | --user=USER) + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command can fail for the following reasons: @@ -26,6 +26,13 @@ EXAMPLES $ gcloud container fleet scopes rbacrolebindings create RBRB \ --scope=SCOPE --role=viewer --group=people@google.com + To create an RBAC RoleBinding with a custom role custom-role in scope SCOPE + for user person@google.com, run: + + $ gcloud container fleet scopes rbacrolebindings create RBRB \ + --scope=SCOPE --role=admin --user=person@google.com \ + --custom-role=custom-role + POSITIONAL ARGUMENTS Rbacrolebinding resource - The group of arguments defining an RBACRoleBinding. The arguments in this group can be used to specify the @@ -68,9 +75,14 @@ POSITIONAL ARGUMENTS ▸ provide the argument --scope on the command line. REQUIRED FLAGS - --role=ROLE - Predefined role to assign to principal (admin, edit, view). ROLE must - be one of: admin, edit, view. + Exactly one of these must be specified: + + --custom-role=CUSTOM_ROLE + Custom role to assign to principal. + + --role=ROLE + Predefined role to assign to principal (admin, edit, view). ROLE must + be one of: admin, edit, view. Exactly one of these must be specified: diff --git a/gcloud/container/fleet/scopes/rbacrolebindings/update b/gcloud/container/fleet/scopes/rbacrolebindings/update index 152a66bd4..e62ff9a8e 100644 --- a/gcloud/container/fleet/scopes/rbacrolebindings/update +++ b/gcloud/container/fleet/scopes/rbacrolebindings/update @@ -4,10 +4,11 @@ NAME SYNOPSIS gcloud container fleet scopes rbacrolebindings update - (NAME : --location=LOCATION --scope=SCOPE) [--role=ROLE] + (NAME : --location=LOCATION --scope=SCOPE) [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] - [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...] + [--custom-role=CUSTOM_ROLE | --role=ROLE] [--group=GROUP | --user=USER] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command can fail for the following reasons: @@ -21,6 +22,12 @@ EXAMPLES $ gcloud container fleet scopes rbacrolebindings update RBRB \ --scope=SCOPE --role=viewer + To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to + the custom role custom-role: + + $ gcloud container fleet scopes rbacrolebindings update RBRB \ + --scope=SCOPE --custom-role=custom-role + To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to the user someone@google.com: @@ -69,10 +76,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --scope on the command line. FLAGS - --role=ROLE - Predefined role to assign to principal (admin, edit, view). ROLE must - be one of: admin, edit, view. - --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. @@ -103,6 +106,15 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + At most one of these can be specified: + + --custom-role=CUSTOM_ROLE + Custom role to assign to principal. + + --role=ROLE + Predefined role to assign to principal (admin, edit, view). ROLE must + be one of: admin, edit, view. + At most one of these can be specified: --group=GROUP diff --git a/gcloud/container/hub/help b/gcloud/container/hub/help index c78efff6e..6ebb8060f 100644 --- a/gcloud/container/hub/help +++ b/gcloud/container/hub/help @@ -82,6 +82,9 @@ GROUPS policycontroller Manage Policy Controller Feature. + rbacrolebindingactuation + Manage RbacRoleBinding Actuation. + scopes Manage scopes of all your GKE fleets. diff --git a/gcloud/container/hub/rbacrolebindingactuation/describe b/gcloud/container/hub/rbacrolebindingactuation/describe new file mode 100644 index 000000000..f8bfe0a43 --- /dev/null +++ b/gcloud/container/hub/rbacrolebindingactuation/describe @@ -0,0 +1,23 @@ +NAME + gcloud container hub rbacrolebindingactuation describe - describe the + status of the RbacRoleBinding Actuation Feature in a fleet + +SYNOPSIS + gcloud container hub rbacrolebindingactuation describe + [GCLOUD_WIDE_FLAG ...] + +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 container hub rbacrolebindingactuation describe + + $ gcloud beta container hub rbacrolebindingactuation describe + diff --git a/gcloud/container/hub/rbacrolebindingactuation/help b/gcloud/container/hub/rbacrolebindingactuation/help new file mode 100644 index 000000000..a19549d90 --- /dev/null +++ b/gcloud/container/hub/rbacrolebindingactuation/help @@ -0,0 +1,33 @@ +NAME + gcloud container hub rbacrolebindingactuation - manage RbacRoleBinding + Actuation + +SYNOPSIS + gcloud container hub rbacrolebindingactuation COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage RbacRoleBinding Actuation. + +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 the status of the RbacRoleBinding Actuation Feature in a + fleet. + + update + Update RbacRoleBinding Actuation Feature. + +NOTES + These variants are also available: + + $ gcloud alpha container hub rbacrolebindingactuation + + $ gcloud beta container hub rbacrolebindingactuation + diff --git a/gcloud/container/hub/rbacrolebindingactuation/update b/gcloud/container/hub/rbacrolebindingactuation/update new file mode 100644 index 000000000..745271d0c --- /dev/null +++ b/gcloud/container/hub/rbacrolebindingactuation/update @@ -0,0 +1,54 @@ +NAME + gcloud container hub rbacrolebindingactuation update - update + RbacRoleBinding Actuation Feature + +SYNOPSIS + gcloud container hub rbacrolebindingactuation update + (--add-allowed-custom-role=ADD_ALLOWED_CUSTOM_ROLE + | --allowed-custom-roles=[ROLES,...] + | --remove-allowed-custom-role=REMOVE_ALLOWED_CUSTOM_ROLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command updates RbacRoleBinding Actuation Feature in a fleet. + +EXAMPLES + To update the RbacRoleBinding Actuation Feature, run: + + $ gcloud container fleet rbacrolebinding-actuation update \ + --allowed-custom-roles=role1,role2 + + $ gcloud container fleet rbacrolebinding-actuation update \ + --add-allowed-custom-role=role1 + + $ gcloud container fleet rbacrolebinding-actuation update \ + --remove-allowed-custom-role=role2 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --add-allowed-custom-role=ADD_ALLOWED_CUSTOM_ROLE + Add a single custom role to the allowed custom roles list. + + --allowed-custom-roles=[ROLES,...] + The list of allowed custom roles that can be used in scope + RBACRoleBindings. + + --remove-allowed-custom-role=REMOVE_ALLOWED_CUSTOM_ROLE + Remove a single custom role from the allowed custom roles list. + +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 container hub rbacrolebindingactuation update + + $ gcloud beta container hub rbacrolebindingactuation update + diff --git a/gcloud/container/hub/scopes/rbacrolebindings/create b/gcloud/container/hub/scopes/rbacrolebindings/create index 45b386d7e..727c651ae 100644 --- a/gcloud/container/hub/scopes/rbacrolebindings/create +++ b/gcloud/container/hub/scopes/rbacrolebindings/create @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud container hub scopes rbacrolebindings create - (NAME : --location=LOCATION --scope=SCOPE) --role=ROLE - (--group=GROUP | --user=USER) [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + (NAME : --location=LOCATION --scope=SCOPE) + (--custom-role=CUSTOM_ROLE | --role=ROLE) (--group=GROUP | --user=USER) + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command can fail for the following reasons: @@ -26,6 +26,13 @@ EXAMPLES $ gcloud container hub scopes rbacrolebindings create RBRB \ --scope=SCOPE --role=viewer --group=people@google.com + To create an RBAC RoleBinding with a custom role custom-role in scope SCOPE + for user person@google.com, run: + + $ gcloud container hub scopes rbacrolebindings create RBRB \ + --scope=SCOPE --role=admin --user=person@google.com \ + --custom-role=custom-role + POSITIONAL ARGUMENTS Rbacrolebinding resource - The group of arguments defining an RBACRoleBinding. The arguments in this group can be used to specify the @@ -68,9 +75,14 @@ POSITIONAL ARGUMENTS ▸ provide the argument --scope on the command line. REQUIRED FLAGS - --role=ROLE - Predefined role to assign to principal (admin, edit, view). ROLE must - be one of: admin, edit, view. + Exactly one of these must be specified: + + --custom-role=CUSTOM_ROLE + Custom role to assign to principal. + + --role=ROLE + Predefined role to assign to principal (admin, edit, view). ROLE must + be one of: admin, edit, view. Exactly one of these must be specified: diff --git a/gcloud/container/hub/scopes/rbacrolebindings/update b/gcloud/container/hub/scopes/rbacrolebindings/update index 6bd78ef79..c652204d3 100644 --- a/gcloud/container/hub/scopes/rbacrolebindings/update +++ b/gcloud/container/hub/scopes/rbacrolebindings/update @@ -4,10 +4,11 @@ NAME SYNOPSIS gcloud container hub scopes rbacrolebindings update - (NAME : --location=LOCATION --scope=SCOPE) [--role=ROLE] + (NAME : --location=LOCATION --scope=SCOPE) [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] - [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...] + [--custom-role=CUSTOM_ROLE | --role=ROLE] [--group=GROUP | --user=USER] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command can fail for the following reasons: @@ -21,6 +22,12 @@ EXAMPLES $ gcloud container hub scopes rbacrolebindings update RBRB \ --scope=SCOPE --role=viewer + To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to + the custom role custom-role: + + $ gcloud container hub scopes rbacrolebindings update RBRB \ + --scope=SCOPE --custom-role=custom-role + To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to the user someone@google.com: @@ -69,10 +76,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --scope on the command line. FLAGS - --role=ROLE - Predefined role to assign to principal (admin, edit, view). ROLE must - be one of: admin, edit, view. - --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. @@ -102,6 +105,15 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + At most one of these can be specified: + + --custom-role=CUSTOM_ROLE + Custom role to assign to principal. + + --role=ROLE + Predefined role to assign to principal (admin, edit, view). ROLE must + be one of: admin, edit, view. + At most one of these can be specified: --group=GROUP diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index 025a6282e..f5994624e 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -43,6 +43,7 @@ SYNOPSIS [--num-nodes=NUM_NODES] [--opportunistic-maintenance=[node-idle-time=NODE_IDLE_TIME, window=WINDOW,min-nodes=MIN_NODES,...]] + [--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT] [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] [--preemptible] [--resource-manager-tags=[KEY=VALUE,...]] [--sandbox=[type=TYPE]] @@ -579,6 +580,19 @@ FLAGS --opportunistic-maintenance=node-idle-time=600s,window=600s,\ min-nodes=2 + --performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT + Sets the Performance Monitoring Unit level. Valid values are + architectural, standard and enhanced. PERFORMANCE_MONITORING_UNIT must + be one of: + + architectural + Enables architectural PMU events tied to non last level cache (LLC) + events. + enhanced + Enables most documented core/L2 and LLC PMU events. + standard + Enables most documented core/L2 PMU events. + --placement-policy=PLACEMENT_POLICY Indicates the desired resource policy to use. diff --git a/gcloud/database-migration/connection-profiles/create/alloydb b/gcloud/database-migration/connection-profiles/create/alloydb index 2fba8148d..013830873 100644 --- a/gcloud/database-migration/connection-profiles/create/alloydb +++ b/gcloud/database-migration/connection-profiles/create/alloydb @@ -94,7 +94,7 @@ OPTIONAL FLAGS --database-version=DATABASE_VERSION Database engine major version. DATABASE_VERSION must be one of: - POSTGRES_14, POSTGRES_15, POSTGRES_16. + POSTGRES_14, POSTGRES_15, POSTGRES_16, POSTGRES_17. --display-name=DISPLAY_NAME A user-friendly name for the connection profile. The display name can diff --git a/gcloud/database-migration/connection-profiles/create/sqlserver b/gcloud/database-migration/connection-profiles/create/sqlserver index 8a1c323d2..bee8f948b 100644 --- a/gcloud/database-migration/connection-profiles/create/sqlserver +++ b/gcloud/database-migration/connection-profiles/create/sqlserver @@ -6,7 +6,7 @@ SYNOPSIS gcloud database-migration connection-profiles create sqlserver (CONNECTION_PROFILE : --region=REGION) [--no-async] [--database=DATABASE] [--display-name=DISPLAY_NAME] - [--labels=[KEY=VALUE,...]] [--role=ROLE] + [--labels=[KEY=VALUE,...]] [--role=ROLE] [--ssl-flags=[FLAG=VALUE,...]] [--ca-certificate=CA_CERTIFICATE --ssl-type=SSL_TYPE] [[--gcs-bucket=GCS_BUCKET : --gcs-prefix=GCS_PREFIX --provider=PROVIDER] @@ -93,6 +93,12 @@ FLAGS The role of the connection profile. ROLE must be one of: SOURCE, DESTINATION. + --ssl-flags=[FLAG=VALUE,...] + Comma-separated list of SSL flags used for establishing SSL connection + to the database. Use an equals sign to separate the flag name and + value. Example: --ssl-flags + ssl_mode=enable,server_certificate_hostname=server.com. + --ca-certificate=CA_CERTIFICATE x509 PEM-encoded certificate of the CA that signed the database server's certificate. The value for this flag needs to be the content diff --git a/gcloud/database-migration/conversion-workspaces/create b/gcloud/database-migration/conversion-workspaces/create index 6ec50b7ec..a2c924d4b 100644 --- a/gcloud/database-migration/conversion-workspaces/create +++ b/gcloud/database-migration/conversion-workspaces/create @@ -7,9 +7,13 @@ SYNOPSIS (CONVERSION_WORKSPACE : --region=REGION) --destination-database-engine=DESTINATION_DATABASE_ENGINE --source-database-engine=SOURCE_DATABASE_ENGINE [--no-async] + [--destination-database-provider=DESTINATION_DATABASE_PROVIDER; + default="CLOUDSQL"] [--destination-database-version=DESTINATION_DATABASE_VERSION; default="unspecified"] [--display-name=DISPLAY_NAME] [--global-settings=[KEY=VALUE,...]] + [--source-database-provider=SOURCE_DATABASE_PROVIDER; + default="UNSPECIFIED"] [--source-database-version=SOURCE_DATABASE_VERSION; default="unspecified"] [GCLOUD_WIDE_FLAG ...] @@ -24,7 +28,7 @@ EXAMPLES --display-name=cw1 --source-database-engine=ORACLE \ --source-database-version=11 \ --destination-database-engine=POSTGRESQL \ - --destination-database-version=8 + --destination-database-version=15 POSITIONAL ARGUMENTS Conversion workspace resource - The conversion workspace to create. The @@ -64,13 +68,17 @@ REQUIRED FLAGS (only one value is supported): POSTGRESQL. --source-database-engine=SOURCE_DATABASE_ENGINE - Source database engine type. SOURCE_DATABASE_ENGINE must be (only one - value is supported): ORACLE. + Source database engine type. SOURCE_DATABASE_ENGINE must be one of: + ORACLE, SQL_SERVER. OPTIONAL FLAGS --no-async Waits for the operation in progress to complete before returning. + --destination-database-provider=DESTINATION_DATABASE_PROVIDER; default="CLOUDSQL" + Destination database provider. DESTINATION_DATABASE_PROVIDER must be + one of: ALLOYDB, CLOUDSQL. + --destination-database-version=DESTINATION_DATABASE_VERSION; default="unspecified" Version number for the database engine. The version number must contain numbers and letters only. Example for PostgreSQL 17.0, version number @@ -87,6 +95,11 @@ OPTIONAL FLAGS engine or turn on or off specific features. An object containing a list of "key": "value" pairs. + --source-database-provider=SOURCE_DATABASE_PROVIDER; default="UNSPECIFIED" + Source database provider. SOURCE_DATABASE_PROVIDER must be one of: + AMAZON_RDS, AZURE_MANAGED_INSTANCE, AZURE_SQL_DATABASE, CLOUDSQL, + UNSPECIFIED. + --source-database-version=SOURCE_DATABASE_VERSION; default="unspecified" Version number for the database engine. The version number must contain numbers and letters only. Example for Oracle 21c, version number will diff --git a/gcloud/database-migration/conversion-workspaces/update b/gcloud/database-migration/conversion-workspaces/update index 6671e89ea..3a396145b 100644 --- a/gcloud/database-migration/conversion-workspaces/update +++ b/gcloud/database-migration/conversion-workspaces/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud database-migration conversion-workspaces update (CONVERSION_WORKSPACE : --region=REGION) [--no-async] - [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + [--display-name=DISPLAY_NAME] [--global-filter=GLOBAL_FILTER] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a Database Migration Service conversion workspace. @@ -58,6 +59,12 @@ FLAGS include letters, numbers, spaces, and hyphens, and must start with a letter. The maximum length allowed is 60 characters. + --global-filter=GLOBAL_FILTER + Filter the source entities based on AIP-160 + (https://google.aip.dev/160) standard. This filter will be applied to + all subsequent operations on the source entities, such as convert and + describe-entities. + 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/database-migration/migration-jobs/restart b/gcloud/database-migration/migration-jobs/restart index bc981bb10..1c9a8c567 100644 --- a/gcloud/database-migration/migration-jobs/restart +++ b/gcloud/database-migration/migration-jobs/restart @@ -58,6 +58,8 @@ POSITIONAL ARGUMENTS FLAGS The migration job objects config. + At most one of these can be specified: + --databases-filter=databaseName,[...] A list of databases to be migrated to the destination instance. Provide databases as a comma separated list. This flag is used only diff --git a/gcloud/dataplex/datascans/create/data-discovery b/gcloud/dataplex/datascans/create/data-discovery new file mode 100644 index 000000000..2fbf658f9 --- /dev/null +++ b/gcloud/dataplex/datascans/create/data-discovery @@ -0,0 +1,210 @@ +NAME + gcloud dataplex datascans create data-discovery - create a Dataplex data + discovery scan job + +SYNOPSIS + gcloud dataplex datascans create data-discovery + (DATASCAN : --location=LOCATION) + --data-source-resource=DATA_SOURCE_RESOURCE [--description=DESCRIPTION] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [--async | --validate-only] + [--bigquery-publishing-connection=BIGQUERY_PUBLISHING_CONNECTION + --bigquery-publishing-dataset-location=BIGQUERY_PUBLISHING_DATASET_LOCATION --bigquery-publishing-table-type=BIGQUERY_PUBLISHING_TABLE_TYPE --storage-exclude-patterns=[PATTERN, + ...] --storage-include-patterns=[PATTERN,...] + --csv-delimiter=CSV_DELIMITER + --csv-disable-type-inference=CSV_DISABLE_TYPE_INFERENCE + --csv-encoding=CSV_ENCODING + --csv-header-row-count=CSV_HEADER_ROW_COUNT + --csv-quote-character=CSV_QUOTE_CHARACTER + --json-disable-type-inference=JSON_DISABLE_TYPE_INFERENCE + --json-encoding=JSON_ENCODING] + [--on-demand=ON_DEMAND | --schedule=SCHEDULE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Allows users to auto discover BigQuery External and BigLake tables from + underlying Cloud Storage buckets. + +EXAMPLES + To create a data discovery scan data-discovery-datascan in project + test-project located in us-central1 on Cloud Storage bucket test-bucket, + run: + + $ gcloud dataplex datascans create data-discovery \ + data-discovery-datascan --project=test-project \ + --location=us-central1 \ + --data-source-resource="//storage.googleapis.com/projects/test-p\ + roject/buckets/test-bucket" + +POSITIONAL ARGUMENTS + Datascan resource - Arguments and flags that define the Dataplex datascan + you want to create a data discovery scan for. 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 datascan 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. + + DATASCAN + ID of the datascan or fully qualified identifier for the datascan. + + To set the dataScans attribute: + ▸ provide the argument datascan 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 of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument datascan on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + --data-source-resource=DATA_SOURCE_RESOURCE + Fully-qualified service resource name of the cloud resource bucket that + contains the data for the data discovery scan, of the form: + //storage.googleapis.com/projects/{project_id_or_number}/buckets/{bucket_id}. + +OPTIONAL FLAGS + --description=DESCRIPTION + Description of the data discovery scan. + + --display-name=DISPLAY_NAME + Display name of the data discovery scan. + + --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. + + At most one of --async | --validate-only can be specified. + + At most one of these can be specified: + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --validate-only + Validate the create action, but don't actually perform it. + + Data spec for the data discovery scan. + + BigQuery publishing config arguments for the data discovery scan. + + --bigquery-publishing-connection=BIGQUERY_PUBLISHING_CONNECTION + BigQuery connection to use for auto discovering cloud resource + bucket to BigLake tables in format + projects/{project_id}/locations/{location_id}/connections/{connection_id}. + Connection is required for BIGLAKE BigQuery publishing table type. + + --bigquery-publishing-dataset-location=BIGQUERY_PUBLISHING_DATASET_LOCATION + The location of the BigQuery dataset to publish BigLake external or + non-BigLake external tables to. If not specified, the dataset + location will be set to the location of the data source resource. + Refer to + https://cloud.google.com/bigquery/docs/locations#supportedLocations + for supported locations. + + --bigquery-publishing-table-type=BIGQUERY_PUBLISHING_TABLE_TYPE + BigQuery table type to discover the cloud resource bucket. Can be + either EXTERNAL or BIGLAKE. If not specified, the table type will + be set to EXTERNAL. BIGQUERY_PUBLISHING_TABLE_TYPE must be one of: + + BIGLAKE + Cloud Storage bucket is discovered to BigQuery BigLake tables. + EXTERNAL + Default value. Cloud Storage bucket is discovered to BigQuery + External tables. + + Storage config arguments for the data discovery scan. + + --storage-exclude-patterns=[PATTERN,...] + List of patterns that identify the data to exclude during + discovery. These patterns are interpreted as glob patterns used to + match object names in the Cloud Storage bucket. Exclude patterns + will be applied before include patterns. + + --storage-include-patterns=[PATTERN,...] + List of patterns that identify the data to include during discovery + when only a subset of the data should be considered. These patterns + are interpreted as glob patterns used to match object names in the + Cloud Storage bucket. + + CSV options arguments for the data discovery scan. + + --csv-delimiter=CSV_DELIMITER + Delimiter used to separate values in the CSV file. If not + specified, the delimiter will be set to comma (","). + + --csv-disable-type-inference=CSV_DISABLE_TYPE_INFERENCE + Whether to disable the inference of data types for CSV data. If + true, all columns are registered as strings. + + --csv-encoding=CSV_ENCODING + Character encoding of the CSV file. If not specified, the + encoding will be set to UTF-8. + + --csv-header-row-count=CSV_HEADER_ROW_COUNT + The number of rows to interpret as header rows that should be + skipped when reading data rows. The default value is 1. + + --csv-quote-character=CSV_QUOTE_CHARACTER + The character used to quote column values. Accepts " (double + quotation mark) or ' (single quotation mark). If unspecified, + defaults to " (double quotation mark). + + JSON options arguments for the data discovery scan. + + --json-disable-type-inference=JSON_DISABLE_TYPE_INFERENCE + Whether to disable the inference of data types for JSON data. If + true, all columns are registered as strings. + + --json-encoding=JSON_ENCODING + Character encoding of the JSON file. If not specified, the + encoding will be set to UTF-8. + + Data discovery scan execution settings. + + Data discovery scan scheduling and trigger settings. + + At most one of these can be specified: + + --on-demand=ON_DEMAND + If set, the scan runs one-time shortly after data discovery scan + creation. + + --schedule=SCHEDULE + Cron schedule (https://en.wikipedia.org/wiki/Cron) for running + scans periodically. To explicitly set a timezone to the cron tab, + apply a prefix in the cron tab: "CRON_TZ=${IANA_TIME_ZONE}" or + "TZ=${IANA_TIME_ZONE}". The ${IANA_TIME_ZONE} may only be a valid + string from IANA time zone database. For example, + CRON_TZ=America/New_York 1 * * * * or TZ=America/New_York 1 * * * + *. This field is required for RECURRING scans. + +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 dataplex datascans create data-discovery + diff --git a/gcloud/dataplex/datascans/create/help b/gcloud/dataplex/datascans/create/help index d7d70820b..1bcab32d7 100644 --- a/gcloud/dataplex/datascans/create/help +++ b/gcloud/dataplex/datascans/create/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + data-discovery + Create a Dataplex data discovery scan job. + data-profile Create a Dataplex data profile scan job. diff --git a/gcloud/dataplex/datascans/update/data-discovery b/gcloud/dataplex/datascans/update/data-discovery new file mode 100644 index 000000000..f515c37a7 --- /dev/null +++ b/gcloud/dataplex/datascans/update/data-discovery @@ -0,0 +1,193 @@ +NAME + gcloud dataplex datascans update data-discovery - update a Dataplex data + discovery scan job + +SYNOPSIS + gcloud dataplex datascans update data-discovery + (DATASCAN : --location=LOCATION) [--description=DESCRIPTION] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [--async | --validate-only] + [--bigquery-publishing-connection=BIGQUERY_PUBLISHING_CONNECTION + --bigquery-publishing-dataset-location=BIGQUERY_PUBLISHING_DATASET_LOCATION --bigquery-publishing-table-type=BIGQUERY_PUBLISHING_TABLE_TYPE --storage-exclude-patterns=[PATTERN, + ...] --storage-include-patterns=[PATTERN,...] + --csv-delimiter=CSV_DELIMITER + --csv-disable-type-inference=CSV_DISABLE_TYPE_INFERENCE + --csv-encoding=CSV_ENCODING + --csv-header-row-count=CSV_HEADER_ROW_COUNT + --csv-quote-character=CSV_QUOTE_CHARACTER + --json-disable-type-inference=JSON_DISABLE_TYPE_INFERENCE + --json-encoding=JSON_ENCODING] + [--on-demand=ON_DEMAND | --schedule=SCHEDULE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Allows users to auto discover BigQuery External and BigLake tables from + underlying Cloud Storage buckets. + +EXAMPLES + To update description of a data discovery scan data-discovery-datascan in + project test-project located in us-central1, run: + + $ gcloud dataplex datascans update data-discovery \ + data-discovery-datascan --project=test-project \ + --location=us-central1 --description="Description is updated." + +POSITIONAL ARGUMENTS + Datascan resource - Arguments and flags that define the Dataplex datascan + you want to update a data discovery scan for. 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 datascan 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. + + DATASCAN + ID of the datascan or fully qualified identifier for the datascan. + + To set the dataScans attribute: + ▸ provide the argument datascan 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 of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument datascan on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +FLAGS + --description=DESCRIPTION + Description of the data discovery scan + + --display-name=DISPLAY_NAME + Display name of the data discovery scan + + --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. + + At most one of --async | --validate-only can be specified. + + At most one of these can be specified: + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --validate-only + Validate the update action, but don't actually perform it. + + Data spec for the data discovery scan. + + BigQuery publishing config arguments for the data discovery scan. + + --bigquery-publishing-connection=BIGQUERY_PUBLISHING_CONNECTION + BigQuery connection to use for auto discovering cloud resource + bucket to BigLake tables. Connection is required for + BIGLAKE`BigQuery publishing table type. + + --bigquery-publishing-dataset-location=BIGQUERY_PUBLISHING_DATASET_LOCATION + The location of the BigQuery dataset to publish BigLake external or + non-BigLake external tables to. If not specified, the dataset + location will be set to the location of the data source resource. + Refer to + https://cloud.google.com/bigquery/docs/locations#supportedLocations + for supported locations. + + --bigquery-publishing-table-type=BIGQUERY_PUBLISHING_TABLE_TYPE + BigQuery table type to discover the cloud resource bucket. Can be + either EXTERNAL or BIGLAKE. If not specified, the table type will + be set to EXTERNAL. + + Storage config arguments for the data discovery scan. + + --storage-exclude-patterns=[PATTERN,...] + List of patterns that identify the data to exclude during + discovery. These patterns are interpreted as glob patterns used to + match object names in the Cloud Storage bucket. Exclude patterns + will be applied before include patterns. + + --storage-include-patterns=[PATTERN,...] + List of patterns that identify the data to include during discovery + when only a subset of the data should be considered. These patterns + are interpreted as glob patterns used to match object names in the + Cloud Storage bucket. + + CSV options arguments for the data discovery scan. + + --csv-delimiter=CSV_DELIMITER + Delimiter used to separate values in the CSV file. If not + specified, the delimiter will be set to comma (","). + + --csv-disable-type-inference=CSV_DISABLE_TYPE_INFERENCE + Whether to disable the inference of data types for CSV data. If + true, all columns are registered as strings. + + --csv-encoding=CSV_ENCODING + Character encoding of the CSV file. If not specified, the + encoding will be set to UTF-8. + + --csv-header-row-count=CSV_HEADER_ROW_COUNT + The number of rows to interpret as header rows that should be + skipped when reading data rows. The default value is 1. + + --csv-quote-character=CSV_QUOTE_CHARACTER + The character used to quote column values. Accepts " (double + quotation mark) or ' (single quotation mark). If unspecified, + defaults to " (double quotation mark). + + JSON options arguments for the data discovery scan. + + --json-disable-type-inference=JSON_DISABLE_TYPE_INFERENCE + Whether to disable the inference of data types for JSON data. If + true, all columns are registered as strings. + + --json-encoding=JSON_ENCODING + Character encoding of the JSON file. If not specified, the + encoding will be set to UTF-8. + + Data discovery scan execution settings. + + Data discovery scan scheduling and trigger settings + + At most one of these can be specified: + + --on-demand=ON_DEMAND + If set, the scan runs one-time shortly after data discovery scan + updation. + + --schedule=SCHEDULE + Cron schedule (https://en.wikipedia.org/wiki/Cron) for running + scans periodically. To explicitly set a timezone to the cron tab, + apply a prefix in the cron tab: "CRON_TZ=${IANA_TIME_ZONE}" or + "TZ=${IANA_TIME_ZONE}". The ${IANA_TIME_ZONE} may only be a valid + string from IANA time zone database. For example, + CRON_TZ=America/New_York 1 * * * * or TZ=America/New_York 1 * * * + *. This field is required for RECURRING scans. + +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 dataplex datascans update data-discovery + diff --git a/gcloud/dataplex/datascans/update/help b/gcloud/dataplex/datascans/update/help index 50a6a45f9..bc37b6e7b 100644 --- a/gcloud/dataplex/datascans/update/help +++ b/gcloud/dataplex/datascans/update/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + data-discovery + Update a Dataplex data discovery scan job. + data-profile Update a Dataplex data profile scan job. diff --git a/gcloud/dataplex/entry-groups/add-iam-policy-binding b/gcloud/dataplex/entry-groups/add-iam-policy-binding index 6da7806a8..21923433d 100644 --- a/gcloud/dataplex/entry-groups/add-iam-policy-binding +++ b/gcloud/dataplex/entry-groups/add-iam-policy-binding @@ -41,7 +41,7 @@ POSITIONAL ARGUMENTS ID of the entry group or fully qualified identifier for the entry group. - To set the entry_group attribute: + To set the entry-group attribute: ▸ provide the argument entry_group on the command line. This positional argument must be specified if any of the other diff --git a/gcloud/dataplex/entry-groups/create b/gcloud/dataplex/entry-groups/create index a8bae2b46..dee7f2985 100644 --- a/gcloud/dataplex/entry-groups/create +++ b/gcloud/dataplex/entry-groups/create @@ -38,7 +38,7 @@ POSITIONAL ARGUMENTS ID of the entry group or fully qualified identifier for the entry group. - To set the entry_group attribute: + To set the entry-group attribute: ▸ provide the argument entry_group on the command line. This positional argument must be specified if any of the other diff --git a/gcloud/dataplex/entry-groups/remove-iam-policy-binding b/gcloud/dataplex/entry-groups/remove-iam-policy-binding index 65864bf6f..0ae38c35d 100644 --- a/gcloud/dataplex/entry-groups/remove-iam-policy-binding +++ b/gcloud/dataplex/entry-groups/remove-iam-policy-binding @@ -41,7 +41,7 @@ POSITIONAL ARGUMENTS ID of the entry group or fully qualified identifier for the entry group. - To set the entry_group attribute: + To set the entry-group attribute: ▸ provide the argument entry_group on the command line. This positional argument must be specified if any of the other diff --git a/gcloud/dataplex/entry-groups/set-iam-policy b/gcloud/dataplex/entry-groups/set-iam-policy index bbeab6974..1498a42e6 100644 --- a/gcloud/dataplex/entry-groups/set-iam-policy +++ b/gcloud/dataplex/entry-groups/set-iam-policy @@ -38,7 +38,7 @@ POSITIONAL ARGUMENTS ID of the entry group or fully qualified identifier for the entry group. - To set the entry_group attribute: + To set the entry-group attribute: ▸ provide the argument entry_group on the command line. This positional argument must be specified if any of the other diff --git a/gcloud/dataplex/entry-groups/update b/gcloud/dataplex/entry-groups/update index 4aa24f0d9..742718c23 100644 --- a/gcloud/dataplex/entry-groups/update +++ b/gcloud/dataplex/entry-groups/update @@ -38,7 +38,7 @@ POSITIONAL ARGUMENTS ID of the entry group or fully qualified identifier for the entry group. - To set the entry_group attribute: + To set the entry-group attribute: ▸ provide the argument entry_group on the command line. This positional argument must be specified if any of the other diff --git a/gcloud/dataplex/help b/gcloud/dataplex/help index 002a9a641..8829a7a33 100644 --- a/gcloud/dataplex/help +++ b/gcloud/dataplex/help @@ -48,6 +48,9 @@ GROUPS lakes Manage Dataplex Lake resources. + metadata-jobs + Manage Dataplex metadata jobs. + tasks Manage Dataplex Task services. diff --git a/gcloud/dataplex/metadata-jobs/cancel b/gcloud/dataplex/metadata-jobs/cancel new file mode 100644 index 000000000..cc78bda21 --- /dev/null +++ b/gcloud/dataplex/metadata-jobs/cancel @@ -0,0 +1,67 @@ +NAME + gcloud dataplex metadata-jobs cancel - cancel a Metadata Job run + +SYNOPSIS + gcloud dataplex metadata-jobs cancel (METADATA_JOB : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Cancels an existing Metadata Job run. + +EXAMPLES + To cancel a Dataplex Metadata Job run test-metadata-job within location + us-central1 and in project test-project + + $ gcloud dataplex metadata-jobs cancel test-metadata-job \ + --location=us-central1 --project=test-project + +POSITIONAL ARGUMENTS + Metadata job resource - Arguments and flags that define the Dataplex + metadata job you want to cancel. 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 metadata_job 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. + + METADATA_JOB + ID of the metadata job or fully qualified identifier for the metadata + job. + + To set the metadata_job attribute: + ▸ provide the argument metadata_job on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument metadata_job on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/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. + +API REFERENCE + This command uses the dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/docs + +NOTES + This variant is also available: + + $ gcloud alpha dataplex metadata-jobs cancel + diff --git a/gcloud/dataplex/metadata-jobs/create b/gcloud/dataplex/metadata-jobs/create new file mode 100644 index 000000000..56d5b49b3 --- /dev/null +++ b/gcloud/dataplex/metadata-jobs/create @@ -0,0 +1,269 @@ +NAME + gcloud dataplex metadata-jobs create - create a Dataplex Metadata Job + +SYNOPSIS + gcloud dataplex metadata-jobs create [[METADATA_JOB] --location=LOCATION] + --type=TYPE + (--export-output-path=EXPORT_OUTPUT_PATH + ((--export-entry-groups=[EXPORT_ENTRY_GROUPS,...] + | --export-organization-level=EXPORT_ORGANIZATION_LEVEL + | --export-projects=[EXPORT_PROJECTS,...]) + : --export-aspect-types=[EXPORT_ASPECT_TYPES,...] + --export-entry-types=[EXPORT_ENTRY_TYPES,...]) + | [--import-aspect-sync-mode=IMPORT_ASPECT_SYNC_MODE + --import-entry-sync-mode=IMPORT_ENTRY_SYNC_MODE + --import-source-storage-uri=IMPORT_SOURCE_STORAGE_URI + (--import-aspect-types=[IMPORT_ASPECT_TYPES,...] + --import-entry-groups=[IMPORT_ENTRY_GROUPS,...] + --import-entry-link-types=[IMPORT_ENTRY_LINK_TYPES,...] + --import-entry-types=[IMPORT_ENTRY_TYPES,...] + --import-glossaries=[IMPORT_GLOSSARIES,...] + --import-referenced-entry-scopes=[IMPORT_REFERENCED_ENTRY_SCOPES, + ...]) : --import-log-level=IMPORT_LOG_LEVEL + --import-source-create-time=IMPORT_SOURCE_CREATE_TIME]) [--async] + [--labels=[KEY=VALUE,...]] [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + A metadata job represents a long running job on Dataplex Catalog metadata + entries. Some operations include importing and exporting metadata into + entry groups through the usage of entry types and aspect types. + + The Metadata Job ID will be used to identify each configuration run. The + Metadata Job id must follow these rules: + ▪ Must contain only lowercase letters, numbers, and hyphens. + ▪ Must start with a letter. + ▪ Must end with a number or a letter. + ▪ Must be between 1-63 characters. + ▪ Must be unique within the customer project / location. + +EXAMPLES + To create a Dataplex Metadata Job with type IMPORT and name my-metadata-job + in location us-central1 with additional parameters, run: + + $ gcloud dataplex metadata-jobs create my-metadata-job \ + --location=us-central --project=test-project --type=import \ + --import-source-storage-uri=gs://test-storage/ \ + --import-source-create-time="2019-01-23T12:34:56.123456789Z" \ + --import-entry-sync-mode=FULL \ + --import-aspect-sync-mode=INCREMENTAL \ + --import-log-level="debug" \ + --import-entry-groups=projects/test-project/locations/\ + us-central1/entryGroups/eg1 \ + --import-entry-types="projects/test-project/locations/us-central\ + 1/entryTypes/et1", \ + "projects/test-project/locations/us-central1/entryTypes/et2" \ + --import-aspect-types="projects/test-project/locations/us-centra\ + l1/aspectTypes/at1", \ + "projects/test-project/locations/us-central1/aspectTypes/at2" + + To create a Dataplex Metadata Job with type EXPORT and name my-metadata-job + in location us-central1 with additional parameters, run: + + $ gcloud dataplex metadata-jobs create my-metadata-job \ + --location=us-central --project=test-project --type=export \ + --export-output-path=gs://test-storage/ \ + --export-entry-groups=projects/test-project/locations/\ + us-central1/entryGroups/eg1 \ + --export-entry-types="projects/test-project/locations/us-central\ + 1/entryTypes/et1", \ + "projects/test-project/locations/us-central1/entryTypes/et2" \ + --export-aspect-types="projects/test-project/locations/us-centra\ + l1/aspectTypes/at1", \ + "projects/test-project/locations/us-central1/aspectTypes/at2" + +POSITIONAL ARGUMENTS + Metadata job resource - Arguments and flags that define the Dataplex + metdata job you want to create. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument metadata_job on the command line with a fully + specified name; + ◆ job ID is optional and will be generated if not specified with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + [METADATA_JOB] + ID of the metadata job or fully qualified identifier for the metadata + job. + + To set the metadata_job attribute: + ▸ provide the argument metadata_job on the command line; + ▸ job ID is optional and will be generated if not specified. + + --location=LOCATION + The location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument metadata_job on the command line with a + fully specified name; + ▸ job ID is optional and will be generated if not specified with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + --type=TYPE + Type. TYPE must be one of: + + EXPORT + A Metadata Export Job will export entries and aspects from the + declared Dataplex scope to the specified Cloud Storage location. + IMPORT + A Metadata Import Job will ingest, update, or delete entries and + aspects into the declared Dataplex entry group. + + Settings for metadata job operation. + + Exactly one of these must be specified: + + Settings for metadata export job operation. + + --export-output-path=EXPORT_OUTPUT_PATH + The Cloud Storage location to export metadata to. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + A boundary on the scope of impact that the metadata export job can + have. + + At least one of these must be specified: + + --export-aspect-types=[EXPORT_ASPECT_TYPES,...] + The list of aspect types to export metadata from. + + --export-entry-types=[EXPORT_ENTRY_TYPES,...] + The list of entry types to export metadata from. + + The scope of resources to export metadata from. + + Exactly one of these must be specified: + + --export-entry-groups=[EXPORT_ENTRY_GROUPS,...] + The list of entry groups to export metadata from. + + --export-organization-level=EXPORT_ORGANIZATION_LEVEL + Whether to export metadata at the organization level. + + --export-projects=[EXPORT_PROJECTS,...] + The list of projects to export metadata from. + + Settings for metadata import job operation. + + --import-aspect-sync-mode=IMPORT_ASPECT_SYNC_MODE + Type. IMPORT_ASPECT_SYNC_MODE must be one of: + + FULL + All resources in the job's scope are modified. If a resource + exists in Dataplex but isn't included in the metadata import + file, the resource is deleted when you run the metadata job. + Use this mode to perform a full sync of the set of entries in + the job scope. + INCREMENTAL + Only the entries and aspects that are explicitly included in + the metadata import file are modified. Use this mode to modify + a subset of resources while leaving unreferenced resources + unchanged. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --import-entry-sync-mode=IMPORT_ENTRY_SYNC_MODE + Type. IMPORT_ENTRY_SYNC_MODE must be one of: + + FULL + All resources in the job's scope are modified. If a resource + exists in Dataplex but isn't included in the metadata import + file, the resource is deleted when you run the metadata job. + Use this mode to perform a full sync of the set of entries in + the job scope. + INCREMENTAL + Only the entries and aspects that are explicitly included in + the metadata import file are modified. Use this mode to modify + a subset of resources while leaving unreferenced resources + unchanged. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --import-source-storage-uri=IMPORT_SOURCE_STORAGE_URI + The Dataplex source storage URI to import metadata from. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --import-log-level=IMPORT_LOG_LEVEL + Type. IMPORT_LOG_LEVEL must be one of: + + DEBUG + Debug-level logging. Captures detailed logs for each import + item. Use debug-level logging to troubleshoot issues with + specific import items. For example, use debug-level logging to + identify resources that are missing from the job scope, entries + or aspects that don't conform to the associated entry type or + aspect type, or other misconfigurations with the metadata + import file.. + INFO + Info-level logging. Captures logs at the overall job level. + Includes aggregate logs about import items, but doesn't specify + which import item has an error.. + + --import-source-create-time=IMPORT_SOURCE_CREATE_TIME + Time at which the event took place. See $ gcloud topic datetimes + for information on supported time formats. + + A boundary on the scope of impact that the metadata import job can + have. + + At least one of these must be specified: + + --import-aspect-types=[IMPORT_ASPECT_TYPES,...] + The list of aspect types to import metadata jobs into. + + --import-entry-groups=[IMPORT_ENTRY_GROUPS,...] + The list of entry groups to import metadata jobs into. + + --import-entry-link-types=[IMPORT_ENTRY_LINK_TYPES,...] + The list of entry link types to import metadata jobs into. + + --import-entry-types=[IMPORT_ENTRY_TYPES,...] + The list of entry types to import metadata jobs into. + + --import-glossaries=[IMPORT_GLOSSARIES,...] + The list of glossaries to import metadata jobs into. + + --import-referenced-entry-scopes=[IMPORT_REFERENCED_ENTRY_SCOPES,...] + The list of referenced entry scopes to import metadata jobs into. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --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. + + --validate-only + Validate the create action, but don't actually perform it. + +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 dataplex metadata-jobs create + diff --git a/gcloud/dataplex/metadata-jobs/describe b/gcloud/dataplex/metadata-jobs/describe new file mode 100644 index 000000000..85a2b27ed --- /dev/null +++ b/gcloud/dataplex/metadata-jobs/describe @@ -0,0 +1,68 @@ +NAME + gcloud dataplex metadata-jobs describe - describe a Metadata Job + +SYNOPSIS + gcloud dataplex metadata-jobs describe (METADATA_JOB : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Displays all details of a Dataplex Metadata Job given a valid Metadata Job + ID. + +EXAMPLES + To describe a Dataplex Metadata Job test-metadata-job within location + us-central1 and in project test-project + + $ gcloud dataplex metadata-jobs describe test-metadata-job \ + --location=us-central1 --project=test-project + +POSITIONAL ARGUMENTS + Metadata job resource - Arguments and flags that define the Dataplex + metadata job you want to retrieve. 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 metadata_job 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. + + METADATA_JOB + ID of the metadata job or fully qualified identifier for the metadata + job. + + To set the metadata_job attribute: + ▸ provide the argument metadata_job on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument metadata_job on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/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. + +API REFERENCE + This command uses the dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/docs + +NOTES + This variant is also available: + + $ gcloud alpha dataplex metadata-jobs describe + diff --git a/gcloud/dataplex/metadata-jobs/help b/gcloud/dataplex/metadata-jobs/help new file mode 100644 index 000000000..82a9eb4d8 --- /dev/null +++ b/gcloud/dataplex/metadata-jobs/help @@ -0,0 +1,34 @@ +NAME + gcloud dataplex metadata-jobs - manage Dataplex metadata jobs + +SYNOPSIS + gcloud dataplex metadata-jobs COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Dataplex metadata jobs. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + Cancel a Metadata Job run. + + create + Create a Dataplex Metadata Job. + + describe + Describe a Metadata Job. + + list + List Metadata Job resources under a project. + +NOTES + This variant is also available: + + $ gcloud alpha dataplex metadata-jobs + diff --git a/gcloud/dataplex/metadata-jobs/list b/gcloud/dataplex/metadata-jobs/list new file mode 100644 index 000000000..80af43c98 --- /dev/null +++ b/gcloud/dataplex/metadata-jobs/list @@ -0,0 +1,86 @@ +NAME + gcloud dataplex metadata-jobs list - list Metadata Job resources under a + project + +SYNOPSIS + gcloud dataplex metadata-jobs list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all Metadata Job resource under a specific project and location. + +EXAMPLES + To List Metadata Jobs in project test-dataplex at location us-central1 + + $ gcloud dataplex metadata-jobs list --location=us-central1 \ + --project=test-dataplex + +FLAGS + Location resource - Location in which to list Metadata Jobs. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property dataplex/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; + ▸ set the property dataplex/location. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/docs + +NOTES + This variant is also available: + + $ gcloud alpha dataplex metadata-jobs list + diff --git a/gcloud/dataproc/clusters/create b/gcloud/dataproc/clusters/create index 81955493b..98e0fd2b4 100644 --- a/gcloud/dataproc/clusters/create +++ b/gcloud/dataproc/clusters/create @@ -45,8 +45,7 @@ SYNOPSIS [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--secondary-worker-standard-capacity-percent-above-base=SECONDARY_WORKER_STANDARD_CAPACITY_PERCENT_ABOVE_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--stop-max-idle=STOP_MAX_IDLE] - [--temp-bucket=TEMP_BUCKET] + [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--tier=TIER] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -83,8 +82,6 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] - [--stop-expiration-time=STOP_EXPIRATION_TIME - | --stop-max-age=STOP_MAX_AGE] [--worker-machine-type=WORKER_MACHINE_TYPE | --worker-machine-types=type=MACHINE_TYPE[, type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] @@ -449,15 +446,13 @@ FLAGS security operations, such as remote attestation, encryption, and sealing of keys. - --stop-max-idle=STOP_MAX_IDLE - The duration after the last job completes to auto-stop the cluster, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - --temp-bucket=TEMP_BUCKET The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. + --tier=TIER + Cluster tier. TIER must be one of: premium, standard. + --worker-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the worker instance(s). @@ -1018,18 +1013,6 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. - At most one of these can be specified: - - --stop-expiration-time=STOP_EXPIRATION_TIME - The time when the cluster will be auto-stopped, such as - "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for - information on time formats. - - --stop-max-age=STOP_MAX_AGE - The lifespan of the cluster, with auto-stop upon completion, such as - "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - At most one of these can be specified: --worker-machine-type=WORKER_MACHINE_TYPE diff --git a/gcloud/dataproc/clusters/update b/gcloud/dataproc/clusters/update index f8443da4f..24c5880cf 100644 --- a/gcloud/dataproc/clusters/update +++ b/gcloud/dataproc/clusters/update @@ -15,11 +15,7 @@ SYNOPSIS | --expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE | --no-max-age] [--delete-max-idle=DELETE_MAX_IDLE | --no-delete-max-idle - | --max-idle=MAX_IDLE | --no-max-idle] - [--stop-expiration-time=STOP_EXPIRATION_TIME - | --stop-max-age=STOP_MAX_AGE | --no-stop-max-age] - [--stop-max-idle=STOP_MAX_IDLE | --no-stop-max-idle] - [GCLOUD_WIDE_FLAG ...] + | --max-idle=MAX_IDLE | --no-max-idle] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update the number of worker nodes and/or the labels in a cluster. @@ -220,33 +216,6 @@ FLAGS Cancels the cluster auto-deletion by cluster idle duration (configured by --max-idle flag) - At most one of these can be specified: - - --stop-expiration-time=STOP_EXPIRATION_TIME - The time when the cluster will be auto-stopped, such as - "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for - information on time formats. - - --stop-max-age=STOP_MAX_AGE - The lifespan of the cluster, with auto-stop upon completion, such as - "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - - --no-stop-max-age - Cancels the cluster auto-stop by maximum cluster age (configured by - --stop-max-age or --stop-expiration-time flags) - - At most one of these can be specified: - - --stop-max-idle=STOP_MAX_IDLE - The duration after the last job completes to auto-stop the cluster, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - - --no-stop-max-idle - Cancels the cluster auto-stop by cluster idle duration (configured by - --stop-max-idle flag) - 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/dataproc/workflow-templates/set-managed-cluster b/gcloud/dataproc/workflow-templates/set-managed-cluster index 6ac213c6c..aa2a84e67 100644 --- a/gcloud/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/dataproc/workflow-templates/set-managed-cluster @@ -37,7 +37,7 @@ SYNOPSIS [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--secondary-worker-standard-capacity-percent-above-base=SECONDARY_WORKER_STANDARD_CAPACITY_PERCENT_ABOVE_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] + [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--tier=TIER] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -373,6 +373,9 @@ FLAGS The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. + --tier=TIER + Cluster tier. TIER must be one of: premium, standard. + --worker-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the worker instance(s). diff --git a/gcloud/datastream/connection-profiles/create b/gcloud/datastream/connection-profiles/create index abe4bf4d1..588eada7f 100644 --- a/gcloud/datastream/connection-profiles/create +++ b/gcloud/datastream/connection-profiles/create @@ -14,7 +14,7 @@ SYNOPSIS | --oracle-secret-manager-stored-password=ORACLE_SECRET_MANAGER_STORED_PASSWORD) | [--mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT, [...] --mongodb-username=MONGODB_USERNAME (--mongodb-password=MONGODB_PASSWORD | --mongodb-prompt-for-password - | --mongodb-secret-manager-stored-password=MONGODB_SECRET_MANAGER_STORED_PASSWORD) (--mongodb-srv-connection-format | --mongodb-standard-connection-format) : --mongodb-replica-set=MONGODB_REPLICA_SET] | [--mysql-hostname=MYSQL_HOSTNAME --mysql-port=MYSQL_PORT --mysql-username=MYSQL_USERNAME (--mysql-password=MYSQL_PASSWORD | --mysql-prompt-for-password | --mysql-secret-manager-stored-password=MYSQL_SECRET_MANAGER_STORED_PASSWORD) : --ca-certificate=CA_CERTIFICATE --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY] | [--postgresql-database=POSTGRESQL_DATABASE --postgresql-hostname=POSTGRESQL_HOSTNAME --postgresql-port=POSTGRESQL_PORT --postgresql-username=POSTGRESQL_USERNAME (--postgresql-password=POSTGRESQL_PASSWORD | --postgresql-prompt-for-password | --postgresql-secret-manager-stored-password=POSTGRESQL_SECRET_MANAGER_STORED_PASSWORD) : [--postgresql-ca-certificate=POSTGRESQL_CA_CERTIFICATE : --postgresql-client-certificate=POSTGRESQL_CLIENT_CERTIFICATE --postgresql-client-key=POSTGRESQL_CLIENT_KEY]] | --salesforce-domain=SALESFORCE_DOMAIN (--salesforce-oauth2-client-id=SALESFORCE_OAUTH2_CLIENT_ID (--salesforce-oauth2-client-secret=SALESFORCE_OAUTH2_CLIENT_SECRET | --salesforce-prompt-for-oauth2-client-secret | --salesforce-secret-manager-stored-oauth2-client-secret=SALESFORCE_SECRET_MANAGER_STORED_OAUTH2_CLIENT_SECRET) | --salesforce-username=SALESFORCE_USERNAME (--salesforce-password=SALESFORCE_PASSWORD | --salesforce-prompt-for-password | --salesforce-secret-manager-stored-password=SALESFORCE_SECRET_MANAGER_STORED_PASSWORD) (--salesforce-prompt-for-security-token | --salesforce-secret-manager-stored-security-token=SALESFORCE_SECRET_MANAGER_STORED_SECURITY_TOKEN | --salesforce-security-token=SALESFORCE_SECURITY_TOKEN)) | --sqlserver-database=SQLSERVER_DATABASE --sqlserver-hostname=SQLSERVER_HOSTNAME --sqlserver-port=SQLSERVER_PORT --sqlserver-username=SQLSERVER_USERNAME (--sqlserver-password=SQLSERVER_PASSWORD | --sqlserver-prompt-for-password | --sqlserver-secret-manager-stored-password=SQLSERVER_SECRET_MANAGER_STORED_PASSWORD)] + | --mongodb-secret-manager-stored-password=MONGODB_SECRET_MANAGER_STORED_PASSWORD) (--mongodb-srv-connection-format | --mongodb-standard-connection-format) : --mongodb-direct-connection --mongodb-replica-set=MONGODB_REPLICA_SET --mongodb-tls] | [--mysql-hostname=MYSQL_HOSTNAME --mysql-port=MYSQL_PORT --mysql-username=MYSQL_USERNAME (--mysql-password=MYSQL_PASSWORD | --mysql-prompt-for-password | --mysql-secret-manager-stored-password=MYSQL_SECRET_MANAGER_STORED_PASSWORD) : --ca-certificate=CA_CERTIFICATE --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY] | [--postgresql-database=POSTGRESQL_DATABASE --postgresql-hostname=POSTGRESQL_HOSTNAME --postgresql-port=POSTGRESQL_PORT --postgresql-username=POSTGRESQL_USERNAME (--postgresql-password=POSTGRESQL_PASSWORD | --postgresql-prompt-for-password | --postgresql-secret-manager-stored-password=POSTGRESQL_SECRET_MANAGER_STORED_PASSWORD) : [--postgresql-ca-certificate=POSTGRESQL_CA_CERTIFICATE : --postgresql-client-certificate=POSTGRESQL_CLIENT_CERTIFICATE --postgresql-client-key=POSTGRESQL_CLIENT_KEY]] | --salesforce-domain=SALESFORCE_DOMAIN (--salesforce-oauth2-client-id=SALESFORCE_OAUTH2_CLIENT_ID (--salesforce-oauth2-client-secret=SALESFORCE_OAUTH2_CLIENT_SECRET | --salesforce-prompt-for-oauth2-client-secret | --salesforce-secret-manager-stored-oauth2-client-secret=SALESFORCE_SECRET_MANAGER_STORED_OAUTH2_CLIENT_SECRET) | --salesforce-username=SALESFORCE_USERNAME (--salesforce-password=SALESFORCE_PASSWORD | --salesforce-prompt-for-password | --salesforce-secret-manager-stored-password=SALESFORCE_SECRET_MANAGER_STORED_PASSWORD) (--salesforce-prompt-for-security-token | --salesforce-secret-manager-stored-security-token=SALESFORCE_SECRET_MANAGER_STORED_SECURITY_TOKEN | --salesforce-security-token=SALESFORCE_SECURITY_TOKEN)) | --sqlserver-database=SQLSERVER_DATABASE --sqlserver-hostname=SQLSERVER_HOSTNAME --sqlserver-port=SQLSERVER_PORT --sqlserver-username=SQLSERVER_USERNAME (--sqlserver-password=SQLSERVER_PASSWORD | --sqlserver-prompt-for-password | --sqlserver-secret-manager-stored-password=SQLSERVER_SECRET_MANAGER_STORED_PASSWORD)] [--private-connection=PRIVATE_CONNECTION | --static-ip-connectivity | [--forward-ssh-hostname=FORWARD_SSH_HOSTNAME --forward-ssh-username=FORWARD_SSH_USERNAME @@ -217,9 +217,16 @@ OPTIONAL FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --mongodb-direct-connection + Connect to the mongodb hosts directly and do not try to resolve any + of the replicas from the replica set. + --mongodb-replica-set=MONGODB_REPLICA_SET Replica set of the MongoDB source database. + --mongodb-tls + Enable Transport Layer Security for the monogodb connection. + Exactly one of these must be specified: --mongodb-password=MONGODB_PASSWORD diff --git a/gcloud/datastream/connection-profiles/update b/gcloud/datastream/connection-profiles/update index 729cfe289..b7a50c723 100644 --- a/gcloud/datastream/connection-profiles/update +++ b/gcloud/datastream/connection-profiles/update @@ -12,8 +12,8 @@ SYNOPSIS --oracle-hostname=ORACLE_HOSTNAME --oracle-port=ORACLE_PORT --oracle-username=ORACLE_USERNAME --oracle-password=ORACLE_PASSWORD | --oracle-prompt-for-password - | --oracle-secret-manager-stored-password=ORACLE_SECRET_MANAGER_STORED_PASSWORD | --mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT, - [...] --mongodb-replica-set=MONGODB_REPLICA_SET + | --oracle-secret-manager-stored-password=ORACLE_SECRET_MANAGER_STORED_PASSWORD | --mongodb-direct-connection --mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT, + [...] --mongodb-replica-set=MONGODB_REPLICA_SET --mongodb-tls --mongodb-username=MONGODB_USERNAME --mongodb-password=MONGODB_PASSWORD | --mongodb-prompt-for-password | --mongodb-secret-manager-stored-password=MONGODB_SECRET_MANAGER_STORED_PASSWORD --mongodb-srv-connection-format | --mongodb-standard-connection-format | --mysql-hostname=MYSQL_HOSTNAME --mysql-port=MYSQL_PORT --mysql-username=MYSQL_USERNAME --ca-certificate=CA_CERTIFICATE --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY --mysql-password=MYSQL_PASSWORD | --mysql-prompt-for-password | --mysql-secret-manager-stored-password=MYSQL_SECRET_MANAGER_STORED_PASSWORD | --postgresql-database=POSTGRESQL_DATABASE --postgresql-hostname=POSTGRESQL_HOSTNAME --postgresql-port=POSTGRESQL_PORT --postgresql-username=POSTGRESQL_USERNAME --postgresql-ca-certificate=POSTGRESQL_CA_CERTIFICATE --postgresql-client-certificate=POSTGRESQL_CLIENT_CERTIFICATE --postgresql-client-key=POSTGRESQL_CLIENT_KEY --postgresql-password=POSTGRESQL_PASSWORD | --postgresql-prompt-for-password | --postgresql-secret-manager-stored-password=POSTGRESQL_SECRET_MANAGER_STORED_PASSWORD | --salesforce-domain=SALESFORCE_DOMAIN --salesforce-oauth2-client-id=SALESFORCE_OAUTH2_CLIENT_ID --salesforce-oauth2-client-secret=SALESFORCE_OAUTH2_CLIENT_SECRET | --salesforce-prompt-for-oauth2-client-secret | --salesforce-secret-manager-stored-oauth2-client-secret=SALESFORCE_SECRET_MANAGER_STORED_OAUTH2_CLIENT_SECRET | --salesforce-username=SALESFORCE_USERNAME --salesforce-password=SALESFORCE_PASSWORD | --salesforce-prompt-for-password | --salesforce-secret-manager-stored-password=SALESFORCE_SECRET_MANAGER_STORED_PASSWORD --salesforce-prompt-for-security-token | --salesforce-secret-manager-stored-security-token=SALESFORCE_SECRET_MANAGER_STORED_SECURITY_TOKEN | --salesforce-security-token=SALESFORCE_SECURITY_TOKEN | --sqlserver-database=SQLSERVER_DATABASE --sqlserver-hostname=SQLSERVER_HOSTNAME --sqlserver-port=SQLSERVER_PORT --sqlserver-username=SQLSERVER_USERNAME --sqlserver-password=SQLSERVER_PASSWORD | --sqlserver-prompt-for-password | --sqlserver-secret-manager-stored-password=SQLSERVER_SECRET_MANAGER_STORED_PASSWORD] @@ -182,12 +182,19 @@ OPTIONAL FLAGS Path to secret manager, storing the password for the user used to connect to the database. + --mongodb-direct-connection + Connect to the mongodb hosts directly and do not try to resolve any + of the replicas from the replica set. + --mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT,[...] IP or hostname and port of the MongoDB source database. --mongodb-replica-set=MONGODB_REPLICA_SET Replica set of the MongoDB source database. + --mongodb-tls + Enable Transport Layer Security for the monogodb connection. + --mongodb-username=MONGODB_USERNAME Username Datastream will use to connect to the database. diff --git a/gcloud/developer-connect/connections/update b/gcloud/developer-connect/connections/update index 489166db9..43cf1e6c6 100644 --- a/gcloud/developer-connect/connections/update +++ b/gcloud/developer-connect/connections/update @@ -9,7 +9,7 @@ SYNOPSIS [--secret=SECRET] [--[no-]validate-only] [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations - | --remove-annotations=[__REMOVE_ANNOTATIONS,...]] + | --remove-annotations=REMOVE_ANNOTATIONS] [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE --clear-bitbucket-cloud-config | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-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_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE --clear-bitbucket-data-center-config | --clear-github-config --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --clear-github-enterprise-config --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --clear-gitlab-config --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --clear-gitlab-enterprise-config --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] [--clear-crypto-key-config [--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE @@ -17,7 +17,7 @@ SYNOPSIS [--clear-git-proxy-config --[no-]git-proxy-config-enabled] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a connection. @@ -167,8 +167,21 @@ FLAGS --clear-annotations Clear annotations value and set to empty map. - --remove-annotations=[__REMOVE_ANNOTATIONS,...] - Remove existing value from map annotations. + --remove-annotations=REMOVE_ANNOTATIONS + Remove existing value from map annotations. Sets remove_annotations + value. + + Shorthand Example: + + --remove-annotations=string,string + + JSON Example: + + --remove-annotations=["string"] + + File Example: + + --remove-annotations=path_to_file.(yaml|json) Arguments for the connection config. @@ -809,8 +822,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/developer-connect/help b/gcloud/developer-connect/help index c62f546d4..ce309df9a 100644 --- a/gcloud/developer-connect/help +++ b/gcloud/developer-connect/help @@ -18,6 +18,9 @@ GROUPS connections Manage connection resources. + insights-configs + Manage Insights Config resources. + operations Manage Operation resources. diff --git a/gcloud/developer-connect/insights-configs/create b/gcloud/developer-connect/insights-configs/create new file mode 100644 index 000000000..00391688a --- /dev/null +++ b/gcloud/developer-connect/insights-configs/create @@ -0,0 +1,87 @@ +NAME + gcloud developer-connect insights-configs create - create an insight config + +SYNOPSIS + gcloud developer-connect insights-configs create + (INSIGHTS_CONFIG : --location=LOCATION) + --app-hub-application=APP_HUB_APPLICATION + [--artifact-config=ARTIFACT_CONFIG_ITEM] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create an insights config. + +EXAMPLES + To create an insights config, run: + + $ gcloud developer-connect insights-configs create \ + insights-config-name \ + --app-hub-application=projects/my-project/locations/\ + us-central1/applications/my-app-hub-application + +POSITIONAL ARGUMENTS + Insights config resource - The insights config to create. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument insights_config 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. + + INSIGHTS_CONFIG + ID of the insights_config or fully qualified identifier for the + insights_config. + + To set the insightsConfigs attribute: + ▸ provide the argument insights_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The region of the insight config. + + To set the location attribute: + ▸ provide the argument insights_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --app-hub-application=APP_HUB_APPLICATION + The App Hub application to which the insight config is associated. + +OPTIONAL FLAGS + --artifact-config=ARTIFACT_CONFIG_ITEM + Specifies a single artifact configuration. This flag can be repeated + for multiple configurations. + + Each configuration can be provided in a key-value format. + + Format examples: + --artifact-config=uri={REGION}-docker.pkg.dev/my-project/my-repo/my-image,buildProject=my-project + --artifact-config=[uri={REGION}-docker.pkg.dev/my-project/my-repo/my-image,buildProject=my-project] + + Supported keys within a configuration: + ◆ buildProject: String, e.g., my-project + ◆ uri: String, e.g., + {REGION}-docker.pkg.dev/my-project/my-repo/my-image + +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 developer-connect insights-configs create + + $ gcloud beta developer-connect insights-configs create + diff --git a/gcloud/developer-connect/insights-configs/delete b/gcloud/developer-connect/insights-configs/delete new file mode 100644 index 000000000..cf30ff271 --- /dev/null +++ b/gcloud/developer-connect/insights-configs/delete @@ -0,0 +1,96 @@ +NAME + gcloud developer-connect insights-configs delete - delete insightsConfigs + +SYNOPSIS + gcloud developer-connect insights-configs delete + (INSIGHTS_CONFIG : --location=LOCATION) [--async] [--etag=ETAG] + [--request-id=REQUEST_ID] [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an insightsConfig + +EXAMPLES + To delete the insightsConfig, run: + + $ gcloud developer-connect insights-configs delete + +POSITIONAL ARGUMENTS + InsightsConfig resource - Value for parent. 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 insights_config 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. + + INSIGHTS_CONFIG + ID of the insightsConfig or fully qualified identifier for the + insightsConfig. + + To set the insights_config attribute: + ▸ provide the argument insights_config 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 insightsConfig resource. + + To set the location attribute: + ▸ provide the argument insights_config 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. + + --etag=ETAG + This checksum is computed by the server based on the value of other + fields, and may be sent on update and delete requests to ensure the + client has an up-to-date value before proceeding. + + --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, validate the request, but do not actually post it. + +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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +NOTES + These variants are also available: + + $ gcloud alpha developer-connect insights-configs delete + + $ gcloud beta developer-connect insights-configs delete + diff --git a/gcloud/developer-connect/insights-configs/describe b/gcloud/developer-connect/insights-configs/describe new file mode 100644 index 000000000..f12107885 --- /dev/null +++ b/gcloud/developer-connect/insights-configs/describe @@ -0,0 +1,68 @@ +NAME + gcloud developer-connect insights-configs describe - describe + insightsConfigs + +SYNOPSIS + gcloud developer-connect insights-configs describe + (INSIGHTS_CONFIG : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an insightsConfig + +EXAMPLES + To describe the insightsConfig, run: + + $ gcloud developer-connect insights-configs describe + +POSITIONAL ARGUMENTS + InsightsConfig 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 insights_config 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. + + INSIGHTS_CONFIG + ID of the insightsConfig or fully qualified identifier for the + insightsConfig. + + To set the insights_config attribute: + ▸ provide the argument insights_config 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 insightsConfig resource. + + To set the location attribute: + ▸ provide the argument insights_config 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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +NOTES + These variants are also available: + + $ gcloud alpha developer-connect insights-configs describe + + $ gcloud beta developer-connect insights-configs describe + diff --git a/gcloud/developer-connect/insights-configs/help b/gcloud/developer-connect/insights-configs/help new file mode 100644 index 000000000..5703978c2 --- /dev/null +++ b/gcloud/developer-connect/insights-configs/help @@ -0,0 +1,40 @@ +NAME + gcloud developer-connect insights-configs - manage Insights Config + resources + +SYNOPSIS + gcloud developer-connect insights-configs COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Insights Config 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 an insight config. + + delete + Delete insightsConfigs. + + describe + Describe insightsConfigs. + + list + List insightsConfigs. + + update + Update the configuration of an insight config. + +NOTES + These variants are also available: + + $ gcloud alpha developer-connect insights-configs + + $ gcloud beta developer-connect insights-configs + diff --git a/gcloud/developer-connect/insights-configs/list b/gcloud/developer-connect/insights-configs/list new file mode 100644 index 000000000..1153e3905 --- /dev/null +++ b/gcloud/developer-connect/insights-configs/list @@ -0,0 +1,87 @@ +NAME + gcloud developer-connect insights-configs list - list insightsConfigs + +SYNOPSIS + gcloud developer-connect insights-configs list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List insightsConfigs + +EXAMPLES + To list all insightsConfigs, run: + + $ gcloud developer-connect insights-configs list + +REQUIRED FLAGS + Location resource - Parent value for ListInsightsConfigsRequest. 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 developerconnect/v1 API. The full documentation for + this API can be found at: + http://cloud.google.com/developer-connect/docs/overview + +NOTES + These variants are also available: + + $ gcloud alpha developer-connect insights-configs list + + $ gcloud beta developer-connect insights-configs list + diff --git a/gcloud/developer-connect/insights-configs/update b/gcloud/developer-connect/insights-configs/update new file mode 100644 index 000000000..741570b68 --- /dev/null +++ b/gcloud/developer-connect/insights-configs/update @@ -0,0 +1,96 @@ +NAME + gcloud developer-connect insights-configs update - update the configuration + of an insight config + +SYNOPSIS + gcloud developer-connect insights-configs update + (INSIGHTS_CONFIG : --location=LOCATION) + (--run-discovery + --artifact-uri=ARTIFACT_URI --build-project=BUILD_PROJECT) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update the configuration of an insights config. + +EXAMPLES + To update the state of an insights config, run: + + $ gcloud developer-connect insights-configs update \ + insights-config-name --run-discovery + + To update the Artifact Analysis project for an artifact in an insights + config, run: + + $ gcloud developer-connect insights-configs update \ + insights-config-name \ + --artifact-uri=us-{location}-docker.pkg.dev/my-project/\ + my-artifact-repo/my-image --build-project={build_project} + +POSITIONAL ARGUMENTS + Insights config resource - The insights config 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 insights_config 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. + + INSIGHTS_CONFIG + ID of the insights_config or fully qualified identifier for the + insights_config. + + To set the insightsConfigs attribute: + ▸ provide the argument insights_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The region of the insight config. + + To set the location attribute: + ▸ provide the argument insights_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Update the insight config. + + At least one of these must be specified: + + --run-discovery + Sets the state of the insight config to PENDING and kicks off the + discovery flow. + + --artifact-uri=ARTIFACT_URI + Identifier for the specific artifact you want to update + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --build-project=BUILD_PROJECT + The project ID of the project to where the artifact is built. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +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 developer-connect insights-configs update + + $ gcloud beta developer-connect insights-configs update + diff --git a/gcloud/dns/policies/create b/gcloud/dns/policies/create index a9f6ff668..fc9ae2f75 100644 --- a/gcloud/dns/policies/create +++ b/gcloud/dns/policies/create @@ -5,7 +5,8 @@ SYNOPSIS gcloud dns policies create POLICY --description=DESCRIPTION --networks=[NETWORKS,...] [--alternative-name-servers=[NAME_SERVERS,...]] - [--enable-inbound-forwarding] [--enable-logging] + [--enable-dns64-all-queries] [--enable-inbound-forwarding] + [--enable-logging] [--private-alternative-name-servers=[NAME_SERVERS,...]] [GCLOUD_WIDE_FLAG ...] @@ -24,7 +25,8 @@ EXAMPLES --description='My new policy test policy 5' \ --networks=network1,network2 \ --alternative-name-servers=192.168.1.1,192.168.1.2 \ - --enable-inbound-forwarding --enable-logging + --enable-inbound-forwarding --enable-logging \ + --enable-dns64-all-queries POSITIONAL ARGUMENTS Policy resource - The policy to create. This represents a Cloud resource. @@ -57,6 +59,10 @@ OPTIONAL FLAGS will forward to the target through the Internet.RFC1918 addresses will forward through the VPC. + --enable-dns64-all-queries + Specifies whether to allow networks bound to this policy to use DNS64 + for IPv6-only VM instances. + --enable-inbound-forwarding Specifies whether to allow networks bound to this policy to receive DNS queries sent by VMs or applications over VPN connections. Defaults to diff --git a/gcloud/dns/policies/update b/gcloud/dns/policies/update index 792018ef5..0fae04acd 100644 --- a/gcloud/dns/policies/update +++ b/gcloud/dns/policies/update @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud dns policies update POLICY [--alternative-name-servers=[NAME_SERVERS,...]] - [--description=DESCRIPTION] [--enable-inbound-forwarding] - [--enable-logging] [--networks=[NETWORKS,...]] + [--description=DESCRIPTION] [--[no-]enable-dns64-all-queries] + [--enable-inbound-forwarding] [--enable-logging] + [--networks=[NETWORKS,...]] [--private-alternative-name-servers=[NAME_SERVERS,...]] [GCLOUD_WIDE_FLAG ...] @@ -44,6 +45,11 @@ FLAGS --description=DESCRIPTION A description of the policy. + --[no-]enable-dns64-all-queries + Specifies whether to allow networks bound to this policy to use DNS64 + for IPv6-only VM instances. Use --enable-dns64-all-queries to enable + and --no-enable-dns64-all-queries to disable. + --enable-inbound-forwarding Specifies whether to allow networks bound to this policy to receive DNS queries sent by VMs or applications over VPN connections. Defaults to diff --git a/gcloud/filestore/instances/create b/gcloud/filestore/instances/create index 95e30805d..569c325cf 100644 --- a/gcloud/filestore/instances/create +++ b/gcloud/filestore/instances/create @@ -11,8 +11,9 @@ SYNOPSIS [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--location=LOCATION] [--performance=[max-iops=MAX-IOPS],[max-iops-per-tb=MAX-IOPS-PER-TB]] - [--region=REGION] [--source-instance=SOURCE_INSTANCE] - [--tags=[KEY=VALUE,...]] [--tier=TIER; default="BASIC_HDD"] + [--protocol=PROTOCOL; default="NFS_V3"] [--region=REGION] + [--source-instance=SOURCE_INSTANCE] [--tags=[KEY=VALUE,...]] + [--tier=TIER; default="BASIC_HDD"] [--deletion-protection : --deletion-protection-reason=DELETION_PROTECTION_REASON] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING @@ -27,7 +28,8 @@ EXAMPLES volume. $ gcloud filestore instances create NAME --description=DESCRIPTION \ - --tier=TIER --file-share=name=VOLUME_NAME,capacity=CAPACITY \ + --tier=TIER --protocol=PROTOCOL \ + --file-share=name=VOLUME_NAME,capacity=CAPACITY \ --network=name=NETWORK_NAME,\ reserved-ip-range=RESERVED_IP_RANGE,connect-mode=CONNECT_MODE \ --zone=ZONE --performance=max-iops-per-tb=MAX-IOPS-PER-TB \ @@ -248,6 +250,15 @@ OPTIONAL FLAGS $ gcloud filestore instances create example-cluster \ --performance=max-iops-per-tb=17000 + --protocol=PROTOCOL; default="NFS_V3" + The service protocol for the Cloud Filestore instance. PROTOCOL must be + one of: + + nfs-v3 + NFSv3 protocol. + nfs-v4-1 + NFSv4.1 protocol. + --region=REGION Region of the Cloud Filestore instance. diff --git a/gcloud/firebase/test/android/run b/gcloud/firebase/test/android/run index 4bbb50c12..74db6cd83 100644 --- a/gcloud/firebase/test/android/run +++ b/gcloud/firebase/test/android/run @@ -386,7 +386,7 @@ ANDROID INSTRUMENTATION TEST FLAGS test targets). Each target filter must be fully qualified with the package name, class name, or test annotation desired. Any test filter supported by am instrument -e ... is supported. See - https://developer.android.com/reference/android/support/test/runner/AndroidJUnitRunner + https://developer.android.com/reference/androidx/test/runner/AndroidJUnitRunner for more information. Examples: ◆ --test-targets "package com.my.package.name" diff --git a/gcloud/firestore/databases/create b/gcloud/firestore/databases/create index 44403ce2c..75ed5ba7b 100644 --- a/gcloud/firestore/databases/create +++ b/gcloud/firestore/databases/create @@ -11,7 +11,7 @@ SYNOPSIS EXAMPLES To create a Firestore Enterprise database named foo in nam5 for use with - Ignite APIs. + MongoDB Compatibility. $ gcloud firestore databases create --database=foo \ --edition=enterprise --location=nam5 diff --git a/gcloud/firestore/indexes/composite/create b/gcloud/firestore/indexes/composite/create index 3ee040d31..385013a5a 100644 --- a/gcloud/firestore/indexes/composite/create +++ b/gcloud/firestore/indexes/composite/create @@ -58,7 +58,7 @@ REQUIRED FLAGS Shorthand Example: - --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat={}} --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat={}} + --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat} --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat} JSON Example: diff --git a/gcloud/gemini/code-repository-indexes/repository-groups/update b/gcloud/gemini/code-repository-indexes/repository-groups/update index 25f05197b..a716bed55 100644 --- a/gcloud/gemini/code-repository-indexes/repository-groups/update +++ b/gcloud/gemini/code-repository-indexes/repository-groups/update @@ -9,7 +9,7 @@ SYNOPSIS [--async] [--request-id=REQUEST_ID] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] + | --remove-labels=REMOVE_LABELS] [--repositories=[branchPattern=BRANCHPATTERN],[resource=RESOURCE] | --add-repositories=[branchPattern=BRANCHPATTERN], [resource=RESOURCE] --clear-repositories @@ -141,8 +141,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) Update repositories. diff --git a/gcloud/gemini/code-repository-indexes/update b/gcloud/gemini/code-repository-indexes/update index 678b5b2aa..8282255df 100644 --- a/gcloud/gemini/code-repository-indexes/update +++ b/gcloud/gemini/code-repository-indexes/update @@ -8,7 +8,7 @@ SYNOPSIS [--request-id=REQUEST_ID] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update the configuration of a code repository index instance. @@ -122,8 +122,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/gemini/code-tools-settings/setting-bindings/update b/gcloud/gemini/code-tools-settings/setting-bindings/update index ba6e78b7b..83ad58ab8 100644 --- a/gcloud/gemini/code-tools-settings/setting-bindings/update +++ b/gcloud/gemini/code-tools-settings/setting-bindings/update @@ -10,7 +10,7 @@ SYNOPSIS [--target=TARGET] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a settingBinding @@ -149,8 +149,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/gemini/code-tools-settings/update b/gcloud/gemini/code-tools-settings/update index 693f26af6..30ba6d080 100644 --- a/gcloud/gemini/code-tools-settings/update +++ b/gcloud/gemini/code-tools-settings/update @@ -14,7 +14,7 @@ SYNOPSIS [handle=HANDLE],[tool=TOOL],[uriOverride=URIOVERRIDE]] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a codeToolsSetting @@ -254,8 +254,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, 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 0f9f4b6db..de2afda58 100644 --- a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/update +++ b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/update @@ -10,7 +10,7 @@ SYNOPSIS [--request-id=REQUEST_ID] [--target=TARGET] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a settingBinding @@ -150,8 +150,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/gemini/data-sharing-with-google-settings/update b/gcloud/gemini/data-sharing-with-google-settings/update index 379dff593..5db72df00 100644 --- a/gcloud/gemini/data-sharing-with-google-settings/update +++ b/gcloud/gemini/data-sharing-with-google-settings/update @@ -8,7 +8,7 @@ SYNOPSIS [--[no-]enable-preview-data-sharing] [--request-id=REQUEST_ID] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a dataSharingWithGoogleSetting @@ -128,8 +128,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/create b/gcloud/gemini/gemini-gcp-enablement-settings/create index a9ef7c4be..550575aa6 100644 --- a/gcloud/gemini/gemini-gcp-enablement-settings/create +++ b/gcloud/gemini/gemini-gcp-enablement-settings/create @@ -5,8 +5,9 @@ NAME SYNOPSIS gcloud gemini gemini-gcp-enablement-settings create (GEMINI_GCP_ENABLEMENT_SETTING : --location=LOCATION) - [--enable-customer-data-sharing] [--labels=[LABELS,...]] - [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + [--disable-web-grounding] [--enable-customer-data-sharing] + [--labels=[LABELS,...]] [--request-id=REQUEST_ID] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a geminiGcpEnablementSetting @@ -51,6 +52,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line. FLAGS + --disable-web-grounding + Whether web grounding should be disabled. + --enable-customer-data-sharing Whether customer data sharing should be enabled. diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/update b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/update index d28df4640..f412d6e49 100644 --- a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/update +++ b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/update @@ -10,7 +10,7 @@ SYNOPSIS [--request-id=REQUEST_ID] [--target=TARGET] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a settingBinding @@ -150,8 +150,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/update b/gcloud/gemini/gemini-gcp-enablement-settings/update index 1ade400d4..cce388a00 100644 --- a/gcloud/gemini/gemini-gcp-enablement-settings/update +++ b/gcloud/gemini/gemini-gcp-enablement-settings/update @@ -5,10 +5,11 @@ NAME SYNOPSIS gcloud gemini gemini-gcp-enablement-settings update (GEMINI_GCP_ENABLEMENT_SETTING : --location=LOCATION) - [--[no-]enable-customer-data-sharing] [--request-id=REQUEST_ID] + [--[no-]disable-web-grounding] [--[no-]enable-customer-data-sharing] + [--request-id=REQUEST_ID] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a geminiGcpEnablementSetting @@ -53,6 +54,10 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line. FLAGS + --[no-]disable-web-grounding + Whether web grounding should be disabled. 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 @@ -128,8 +133,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/gemini/logging-settings/setting-bindings/update b/gcloud/gemini/logging-settings/setting-bindings/update index 76f826ebb..53dfc35e4 100644 --- a/gcloud/gemini/logging-settings/setting-bindings/update +++ b/gcloud/gemini/logging-settings/setting-bindings/update @@ -9,7 +9,7 @@ SYNOPSIS [--product=PRODUCT] [--request-id=REQUEST_ID] [--target=TARGET] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a settingBinding @@ -148,8 +148,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/gemini/logging-settings/update b/gcloud/gemini/logging-settings/update index 92ec52034..eb4425969 100644 --- a/gcloud/gemini/logging-settings/update +++ b/gcloud/gemini/logging-settings/update @@ -7,7 +7,7 @@ SYNOPSIS [--[no-]log-prompts-and-responses] [--request-id=REQUEST_ID] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a loggingSetting @@ -129,8 +129,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/gemini/release-channel-settings/setting-bindings/update b/gcloud/gemini/release-channel-settings/setting-bindings/update index e1dac35e9..901f18ae1 100644 --- a/gcloud/gemini/release-channel-settings/setting-bindings/update +++ b/gcloud/gemini/release-channel-settings/setting-bindings/update @@ -9,7 +9,7 @@ SYNOPSIS [--product=PRODUCT] [--request-id=REQUEST_ID] [--target=TARGET] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a settingBinding @@ -149,8 +149,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/gemini/release-channel-settings/update b/gcloud/gemini/release-channel-settings/update index b59993be8..4101ef7a0 100644 --- a/gcloud/gemini/release-channel-settings/update +++ b/gcloud/gemini/release-channel-settings/update @@ -8,7 +8,7 @@ SYNOPSIS [--release-channel=RELEASE_CHANNEL] [--request-id=REQUEST_ID] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a releaseChannelSetting @@ -130,8 +130,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/iam/policy-bindings/update b/gcloud/iam/policy-bindings/update index b4386189d..5cb4b8c54 100644 --- a/gcloud/iam/policy-bindings/update +++ b/gcloud/iam/policy-bindings/update @@ -8,7 +8,7 @@ SYNOPSIS [--async] [--display-name=DISPLAY_NAME] [--etag=ETAG] [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations - | --remove-annotations=[__REMOVE_ANNOTATIONS,...]] + | --remove-annotations=REMOVE_ANNOTATIONS] [--condition-description=CONDITION_DESCRIPTION --condition-expression=CONDITION_EXPRESSION --condition-location=CONDITION_LOCATION @@ -157,8 +157,21 @@ FLAGS --clear-annotations Clear annotations value and set to empty map. - --remove-annotations=[__REMOVE_ANNOTATIONS,...] - Remove existing value from map annotations. + --remove-annotations=REMOVE_ANNOTATIONS + Remove existing value from map annotations. Sets remove_annotations + value. + + Shorthand Example: + + --remove-annotations=string,string + + JSON Example: + + --remove-annotations=["string"] + + File Example: + + --remove-annotations=path_to_file.(yaml|json) Represents a textual expression in the Common Expression Language (CEL) syntax. CEL is a C-like expression language. The syntax and semantics of diff --git a/gcloud/iam/principal-access-boundary-policies/update b/gcloud/iam/principal-access-boundary-policies/update index ef7076415..987a5041b 100644 --- a/gcloud/iam/principal-access-boundary-policies/update +++ b/gcloud/iam/principal-access-boundary-policies/update @@ -9,7 +9,7 @@ SYNOPSIS [--display-name=DISPLAY_NAME] [--etag=ETAG] [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations - | --remove-annotations=[__REMOVE_ANNOTATIONS,...]] + | --remove-annotations=REMOVE_ANNOTATIONS] [--details-enforcement-version=DETAILS_ENFORCEMENT_VERSION --details-rules=[description=DESCRIPTION], [effect=EFFECT],[resources=RESOURCES] @@ -134,8 +134,21 @@ FLAGS --clear-annotations Clear annotations value and set to empty map. - --remove-annotations=[__REMOVE_ANNOTATIONS,...] - Remove existing value from map annotations. + --remove-annotations=REMOVE_ANNOTATIONS + Remove existing value from map annotations. Sets remove_annotations + value. + + Shorthand Example: + + --remove-annotations=string,string + + JSON Example: + + --remove-annotations=["string"] + + File Example: + + --remove-annotations=path_to_file.(yaml|json) Principal access boundary policy details diff --git a/gcloud/iam/workforce-pools/providers/create-oidc b/gcloud/iam/workforce-pools/providers/create-oidc index 749c45cd1..ad563152b 100644 --- a/gcloud/iam/workforce-pools/providers/create-oidc +++ b/gcloud/iam/workforce-pools/providers/create-oidc @@ -12,7 +12,7 @@ SYNOPSIS : --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]) [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--client-secret-value=CLIENT_SECRET_VALUE] [--description=DESCRIPTION] - [--disabled] [--display-name=DISPLAY_NAME] + [--detailed-audit-logging] [--disabled] [--display-name=DISPLAY_NAME] [--jwk-json-path=PATH_TO_FILE] [--extra-attributes-client-id=EXTRA_ATTRIBUTES_CLIENT_ID --extra-attributes-client-secret-value=EXTRA_ATTRIBUTES_CLIENT_SECRET_VALUE --extra-attributes-issuer-uri=EXTRA_ATTRIBUTES_ISSUER_URI --extra-attributes-type=EXTRA_ATTRIBUTES_TYPE : --extra-attributes-filter=EXTRA_ATTRIBUTES_FILTER] @@ -240,6 +240,11 @@ OPTIONAL FLAGS A description for the workforce pool provider. Cannot exceed 256 characters in length. + --detailed-audit-logging + Enables detailed audit logging for this provider, which populates + additional debug information in STS Cloud Audit Logs. Specify + --no-detailed-audit-logging to disable it. + --disabled Disables the workforce pool provider. You cannot use a disabled provider to perform new token exchanges or sign-ins. However, existing diff --git a/gcloud/iam/workforce-pools/providers/create-saml b/gcloud/iam/workforce-pools/providers/create-saml index 0e612663e..137c7ee38 100644 --- a/gcloud/iam/workforce-pools/providers/create-saml +++ b/gcloud/iam/workforce-pools/providers/create-saml @@ -7,7 +7,8 @@ SYNOPSIS (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL) --attribute-mapping=[KEY=VALUE,...] --idp-metadata-path=PATH_TO_FILE [--async] [--attribute-condition=ATTRIBUTE_CONDITION] - [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] + [--description=DESCRIPTION] [--detailed-audit-logging] [--disabled] + [--display-name=DISPLAY_NAME] [--extra-attributes-client-id=EXTRA_ATTRIBUTES_CLIENT_ID --extra-attributes-client-secret-value=EXTRA_ATTRIBUTES_CLIENT_SECRET_VALUE --extra-attributes-issuer-uri=EXTRA_ATTRIBUTES_ISSUER_URI --extra-attributes-type=EXTRA_ATTRIBUTES_TYPE : --extra-attributes-filter=EXTRA_ATTRIBUTES_FILTER] [GCLOUD_WIDE_FLAG ...] @@ -180,6 +181,11 @@ OPTIONAL FLAGS A description for the workforce pool provider. Cannot exceed 256 characters in length. + --detailed-audit-logging + Enables detailed audit logging for this provider, which populates + additional debug information in STS Cloud Audit Logs. Specify + --no-detailed-audit-logging to disable it. + --disabled Disables the workforce pool provider. You cannot use a disabled provider to perform new token exchanges or sign-ins. However, existing diff --git a/gcloud/iam/workforce-pools/providers/update-oidc b/gcloud/iam/workforce-pools/providers/update-oidc index 2b455b0f0..f3bd0fbed 100644 --- a/gcloud/iam/workforce-pools/providers/update-oidc +++ b/gcloud/iam/workforce-pools/providers/update-oidc @@ -7,8 +7,9 @@ SYNOPSIS (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL) [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--attribute-mapping=[KEY=VALUE,...]] [--client-id=CLIENT_ID] - [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] - [--issuer-uri=ISSUER_URI] [--jwk-json-path=PATH_TO_FILE] + [--description=DESCRIPTION] [--detailed-audit-logging] [--disabled] + [--display-name=DISPLAY_NAME] [--issuer-uri=ISSUER_URI] + [--jwk-json-path=PATH_TO_FILE] [--web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]] [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] @@ -187,6 +188,11 @@ FLAGS A description for the workforce pool provider. Cannot exceed 256 characters in length. + --detailed-audit-logging + Enables detailed audit logging for this provider, which populates + additional debug information in STS Cloud Audit Logs. Specify + --no-detailed-audit-logging to disable it. + --disabled Disables the workforce pool provider. You cannot use a disabled provider to perform new token exchanges or sign-ins. However, existing diff --git a/gcloud/iam/workforce-pools/providers/update-saml b/gcloud/iam/workforce-pools/providers/update-saml index 5c426dd3f..b75d3c68c 100644 --- a/gcloud/iam/workforce-pools/providers/update-saml +++ b/gcloud/iam/workforce-pools/providers/update-saml @@ -7,7 +7,7 @@ SYNOPSIS (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL) [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION] - [--disabled] [--display-name=DISPLAY_NAME] + [--detailed-audit-logging] [--disabled] [--display-name=DISPLAY_NAME] [--idp-metadata-path=PATH_TO_FILE] [--clear-extra-attributes-config | --extra-attributes-client-id=EXTRA_ATTRIBUTES_CLIENT_ID @@ -174,6 +174,11 @@ FLAGS A description for the workforce pool provider. Cannot exceed 256 characters in length. + --detailed-audit-logging + Enables detailed audit logging for this provider, which populates + additional debug information in STS Cloud Audit Logs. Specify + --no-detailed-audit-logging to disable it. + --disabled Disables the workforce pool provider. You cannot use a disabled provider to perform new token exchanges or sign-ins. However, existing diff --git a/gcloud/iam/workload-identity-pools/create b/gcloud/iam/workload-identity-pools/create index b04fcdc72..e0861452b 100644 --- a/gcloud/iam/workload-identity-pools/create +++ b/gcloud/iam/workload-identity-pools/create @@ -73,8 +73,8 @@ FLAGS caPools: us-east1: projects/1234/locations/us-east1/caPools/capoolname us-west1: projects/1234/locations/us-west1/caPools/capoolname - keyAlgorithm: RSA_4096 - lifetime: 7200s + keyAlgorithm: ECDSA_P256 + lifetime: 86400s rotationWindowPercentage: 50 --inline-trust-config-file=INLINE_TRUST_CONFIG_FILE diff --git a/gcloud/iam/workload-identity-pools/update b/gcloud/iam/workload-identity-pools/update index e5d0ff59f..a4e68cd6b 100644 --- a/gcloud/iam/workload-identity-pools/update +++ b/gcloud/iam/workload-identity-pools/update @@ -94,8 +94,8 @@ FLAGS caPools: us-east1: projects/1234/locations/us-east1/caPools/capoolname us-west1: projects/1234/locations/us-west1/caPools/capoolname - keyAlgorithm: RSA_4096 - lifetime: 7200s + keyAlgorithm: ECDSA_P256 + lifetime: 86400s rotationWindowPercentage: 50 --certificate-lifetime=CERTIFICATE_LIFETIME diff --git a/gcloud/kms/keys/create b/gcloud/kms/keys/create index 99f4f1e99..05804e7bf 100644 --- a/gcloud/kms/keys/create +++ b/gcloud/kms/keys/create @@ -204,7 +204,8 @@ OPTIONAL FLAGS aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, ec-sign-p384-sha384, ec-sign-secp256k1-sha256, external-symmetric-encryption, google-symmetric-encryption, hmac-sha1, - hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, pq-sign-ml-dsa-65, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + pq-sign-hash-slh-dsa-sha2-128s-sha256, pq-sign-ml-dsa-65, pq-sign-slh-dsa-sha2-128s, rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, diff --git a/gcloud/kms/keys/update b/gcloud/kms/keys/update index 3b5f3f144..832a02bee 100644 --- a/gcloud/kms/keys/update +++ b/gcloud/kms/keys/update @@ -175,7 +175,8 @@ FLAGS aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, ec-sign-p384-sha384, ec-sign-secp256k1-sha256, external-symmetric-encryption, google-symmetric-encryption, hmac-sha1, - hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, pq-sign-ml-dsa-65, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + pq-sign-hash-slh-dsa-sha2-128s-sha256, pq-sign-ml-dsa-65, pq-sign-slh-dsa-sha2-128s, rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, diff --git a/gcloud/kms/keys/versions/import b/gcloud/kms/keys/versions/import index 7d97173bd..1dbdf6ff4 100644 --- a/gcloud/kms/keys/versions/import +++ b/gcloud/kms/keys/versions/import @@ -34,7 +34,8 @@ REQUIRED FLAGS aes-128-cbc, aes-128-ctr, aes-128-gcm, aes-256-cbc, aes-256-ctr, aes-256-gcm, ec-sign-ed25519, ec-sign-p256-sha256, ec-sign-p384-sha384, ec-sign-secp256k1-sha256, google-symmetric-encryption, hmac-sha1, - hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, pq-sign-ml-dsa-65, + hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512, + pq-sign-hash-slh-dsa-sha2-128s-sha256, pq-sign-ml-dsa-65, pq-sign-slh-dsa-sha2-128s, rsa-decrypt-oaep-2048-sha1, rsa-decrypt-oaep-2048-sha256, rsa-decrypt-oaep-3072-sha1, rsa-decrypt-oaep-3072-sha256, rsa-decrypt-oaep-4096-sha1, diff --git a/gcloud/logging/logs/delete b/gcloud/logging/logs/delete index 7c41efbe9..8c80b2d2d 100644 --- a/gcloud/logging/logs/delete +++ b/gcloud/logging/logs/delete @@ -1,17 +1,17 @@ NAME - gcloud logging logs delete - delete all entries from a log in the _Default - log bucket + gcloud logging logs delete - delete all entries from a log in the global + _Default log bucket SYNOPSIS gcloud logging logs delete LOG_NAME [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Delete all entries from a log in the _Default log bucket. With no entries, - the log will not appear in the list of your project's logs. However, you - can write new entries to the log. + Delete all entries from a log in the global _Default log bucket. With no + entries, the log will not appear in the list of your project's logs. + However, you can write new entries to the log. EXAMPLES - To delete all entries from log 'my-log' in the _Default log bucket: + To delete all entries from log 'my-log' in the global _Default log bucket: $ gcloud logging logs delete my-log diff --git a/gcloud/logging/logs/help b/gcloud/logging/logs/help index 883185c40..0141844db 100644 --- a/gcloud/logging/logs/help +++ b/gcloud/logging/logs/help @@ -16,7 +16,7 @@ COMMANDS COMMAND is one of the following: delete - Delete all entries from a log in the _Default log bucket. + Delete all entries from a log in the global _Default log bucket. list List your project's logs. diff --git a/gcloud/logging/operations/list b/gcloud/logging/operations/list index 44009576d..d7128964f 100644 --- a/gcloud/logging/operations/list +++ b/gcloud/logging/operations/list @@ -10,15 +10,37 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Return a list of long running operation details in given LOCATION. The - operations were scheduled by other gcloud commands. For example: a - copy_log_entries operation scheduled by command: gcloud alpha logging - operations copy BUCKET_ID DESTINATION --location=LOCATION. Note: while - listing the operations, the request_type must be specified in filter. - Example: --operation-filter=request_type=CopyLogEntries, Supported - operation types are: CopyLogEntries, CreateBucket and UpdateBucket. Other - supported filter expression are: operation_start_time, - operation_finish_time and operation_state. + Return a list of long running operations in the given LOCATION. The + operations were scheduled by other gcloud commands. + + For example, a CopyLogEntries operation may be scheduled by the command: + gcloud logging copy BUCKET_ID DESTINATION --location=LOCATION. + + The --operation-filter flag is required and must specify the request_type. + Supported request types include but are not limited to: CopyLogEntries, + CreateBucket and UpdateBucket. + + Additional supported filter expressions include: operation_start_time, + operation_finish_time and operation_state. These can be combined with the + case-sensitive keyword AND between them. + + For operation_start_time and operation_end_time, the operators >=, >, <=, + and < are supported. + + Timestamps must be in either RFC3339 or ISO8601 formats. If the timestamp + contains a time value, then it must be quoted. For examples: + "YYYY-MM-DDTHH:MM:SSZ", "YYYY-MM-DDTHH:MM:SS.mmmZ", "YY-MM-DD", + "YYYY-MM-DDTHH:MM:SS-0000", "YYYY-MM-DDTHH:MM+0000", "YYYY-MM-DD", + YYYY-MM-DD, YY-MM-DD, etc. + + The operation_state filter expression can be used to filter for operations + that are in a specific state. The value can be one of the following: + SCHEDULED, WAITING_FOR_PRECONDITIONS, RUNNING, SUCCESS, FAILURE, CANCELLED, + PENDING. + + For operation_state, the operators = and != are supported. + + Other filter options are not supported. EXAMPLES To list CopyLogEntries operations, run: @@ -39,17 +61,17 @@ EXAMPLES --operation-filter='request_type=CopyLogEntries AND operation_finish_time<="2023-11-20T00:00:00Z"' - To list CopyLogEntries operations that have a specified state, run: + To list CopyLogEntries operations that completed successfully, run: $ gcloud logging operations list --location=LOCATION \ --operation-filter='request_type=CopyLogEntries AND - operation_state=STATE' + operation_state=SUCCESS' - To list CopyLogEntries operations that don't have a specified state, run: + To list CopyLogEntries operations that have not failed, run: $ gcloud logging operations list --location=LOCATION \ --operation-filter='request_type=CopyLogEntries AND - operation_state!=STATE' + operation_state!=FAILURE' REQUIRED FLAGS --location=LOCATION diff --git a/gcloud/lustre/instances/update b/gcloud/lustre/instances/update index d98134858..05042d49f 100644 --- a/gcloud/lustre/instances/update +++ b/gcloud/lustre/instances/update @@ -10,7 +10,7 @@ SYNOPSIS [--request-id=REQUEST_ID] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Updates the parameters of a single Managed Lustre instance. @@ -144,8 +144,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/memorystore/instances/update b/gcloud/memorystore/instances/update index eeba14b06..699d3daba 100644 --- a/gcloud/memorystore/instances/update +++ b/gcloud/memorystore/instances/update @@ -32,10 +32,10 @@ SYNOPSIS [--engine-configs=[ENGINE_CONFIGS,...] | --update-engine-configs=[UPDATE_ENGINE_CONFIGS,...] --clear-engine-configs - | --remove-engine-configs=[__REMOVE_ENGINE_CONFIGS,...]] + | --remove-engine-configs=REMOVE_ENGINE_CONFIGS] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update the configuration of a Memorystore instance. @@ -754,8 +754,21 @@ FLAGS --clear-engine-configs Clear engine_configs value and set to empty map. - --remove-engine-configs=[__REMOVE_ENGINE_CONFIGS,...] - Remove existing value from map engine_configs. + --remove-engine-configs=REMOVE_ENGINE_CONFIGS + Remove existing value from map engine_configs. Sets + remove_engine_configs value. + + Shorthand Example: + + --remove-engine-configs=string,string + + JSON Example: + + --remove-engine-configs=["string"] + + File Example: + + --remove-engine-configs=path_to_file.(yaml|json) Update labels. @@ -813,8 +826,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/model-armor/floorsettings/update b/gcloud/model-armor/floorsettings/update index 93d9879a5..f296294dc 100644 --- a/gcloud/model-armor/floorsettings/update +++ b/gcloud/model-armor/floorsettings/update @@ -40,7 +40,7 @@ OPTIONAL FLAGS Shorthand Example: - --add-rai-settings-filters=string --add-rai-settings-filters=string + --add-rai-settings-filters=string,string JSON Example: @@ -59,7 +59,7 @@ OPTIONAL FLAGS Shorthand Example: - --rai-settings-filters=string --rai-settings-filters=string + --rai-settings-filters=string,string JSON Example: @@ -74,7 +74,7 @@ OPTIONAL FLAGS Shorthand Example: - --remove-rai-settings-filters=string --remove-rai-settings-filters=string + --remove-rai-settings-filters=string,string JSON Example: diff --git a/gcloud/model-armor/templates/update b/gcloud/model-armor/templates/update index 932d6e459..d742fa7a4 100644 --- a/gcloud/model-armor/templates/update +++ b/gcloud/model-armor/templates/update @@ -15,7 +15,7 @@ SYNOPSIS --template-metadata-custom-llm-response-safety-error-code=TEMPLATE_METADATA_CUSTOM_LLM_RESPONSE_SAFETY_ERROR_CODE --template-metadata-custom-llm-response-safety-error-message=TEMPLATE_METADATA_CUSTOM_LLM_RESPONSE_SAFETY_ERROR_MESSAGE --template-metadata-custom-prompt-safety-error-code=TEMPLATE_METADATA_CUSTOM_PROMPT_SAFETY_ERROR_CODE --template-metadata-custom-prompt-safety-error-message=TEMPLATE_METADATA_CUSTOM_PROMPT_SAFETY_ERROR_MESSAGE --[no-]template-metadata-ignore-partial-invocation-failures --[no-]template-metadata-log-operations --[no-]template-metadata-log-sanitize-operations] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Updates a Template. @@ -347,8 +347,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/netapp/backup-vaults/create b/gcloud/netapp/backup-vaults/create index ff98b48c8..184953f38 100644 --- a/gcloud/netapp/backup-vaults/create +++ b/gcloud/netapp/backup-vaults/create @@ -3,7 +3,13 @@ NAME SYNOPSIS gcloud netapp backup-vaults create (BACKUP_VAULT : --location=LOCATION) - [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--async] + [--backup-retention-policy=[backup-minimum-enforced-retention-days=BACKUP-MINIMUM-ENFORCED-RETENTION-DAYS], + [daily-backup-immutable=DAILY-BACKUP-IMMUTABLE], + [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 @@ -54,6 +60,14 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --backup-retention-policy=[backup-minimum-enforced-retention-days=BACKUP-MINIMUM-ENFORCED-RETENTION-DAYS],[daily-backup-immutable=DAILY-BACKUP-IMMUTABLE],[manual-backup-immutable=MANUAL-BACKUP-IMMUTABLE],[monthly-backup-immutable=MONTHLY-BACKUP-IMMUTABLE],[weekly-backup-immutable=WEEKLY-BACKUP-IMMUTABLE] + Backup Retention Policy of the Backup Vault. + + Backup Retention Policy allows you to configure the retention policy + for backups created within this vault. It consists of several fields + that govern how long backups are kept and what type of backups are + immutable. + --description=DESCRIPTION A description of the Cloud NetApp Backup Vault diff --git a/gcloud/netapp/backup-vaults/update b/gcloud/netapp/backup-vaults/update index 3782b8dc9..0b94b1e48 100644 --- a/gcloud/netapp/backup-vaults/update +++ b/gcloud/netapp/backup-vaults/update @@ -4,7 +4,13 @@ NAME SYNOPSIS gcloud netapp backup-vaults update (BACKUP_VAULT : --location=LOCATION) - [--async] [--description=DESCRIPTION] [--update-labels=[KEY=VALUE,...]] + [--async] + [--backup-retention-policy=[backup-minimum-enforced-retention-days=BACKUP-MINIMUM-ENFORCED-RETENTION-DAYS], + [daily-backup-immutable=DAILY-BACKUP-IMMUTABLE], + [manual-backup-immutable=MANUAL-BACKUP-IMMUTABLE], + [monthly-backup-immutable=MONTHLY-BACKUP-IMMUTABLE], + [weekly-backup-immutable=WEEKLY-BACKUP-IMMUTABLE]] + [--description=DESCRIPTION] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -62,6 +68,14 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --backup-retention-policy=[backup-minimum-enforced-retention-days=BACKUP-MINIMUM-ENFORCED-RETENTION-DAYS],[daily-backup-immutable=DAILY-BACKUP-IMMUTABLE],[manual-backup-immutable=MANUAL-BACKUP-IMMUTABLE],[monthly-backup-immutable=MONTHLY-BACKUP-IMMUTABLE],[weekly-backup-immutable=WEEKLY-BACKUP-IMMUTABLE] + Backup Retention Policy of the Backup Vault. + + Backup Retention Policy allows you to configure the retention policy + for backups created within this vault. It consists of several fields + that govern how long backups are kept and what type of backups are + immutable. + --description=DESCRIPTION A description of the Cloud NetApp Backup Vault diff --git a/gcloud/netapp/storage-pools/create b/gcloud/netapp/storage-pools/create index 2bc0fa25b..9e1a03afe 100644 --- a/gcloud/netapp/storage-pools/create +++ b/gcloud/netapp/storage-pools/create @@ -6,9 +6,12 @@ SYNOPSIS --capacity=CAPACITY --network=[name=NAME],[psa-range=PSA-RANGE] --service-level=SERVICE_LEVEL [--active-directory=ACTIVE_DIRECTORY] [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] + [--custom-performance-enabled=CUSTOM_PERFORMANCE_ENABLED] [--description=DESCRIPTION] [--enable-ldap=ENABLE_LDAP] [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] - [--replica-zone=REPLICA_ZONE] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--replica-zone=REPLICA_ZONE] [--total-iops=TOTAL_IOPS] + [--total-throughput=TOTAL_THROUGHPUT] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Creates a Storage Pool to contain Volumes with a specified Service Level @@ -142,6 +145,10 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --custom-performance-enabled=CUSTOM_PERFORMANCE_ENABLED + Boolean flag indicating whether Storage Pool is a custom performance + Storage Pool or not + --description=DESCRIPTION A description of the Cloud NetApp Storage Pool @@ -183,6 +190,13 @@ OPTIONAL FLAGS --replica-zone=REPLICA_ZONE String indicating replica zone for the Storage Pool + --total-iops=TOTAL_IOPS + Integer indicating total IOPS of the Storage Pool + + --total-throughput=TOTAL_THROUGHPUT + The total throughput of the Storage Pool in MiB/s or GiB/s units. If no + throughput unit is specified, MiB/s is assumed. + --zone=ZONE String indicating active zone of the Storage Pool diff --git a/gcloud/netapp/storage-pools/update b/gcloud/netapp/storage-pools/update index fedfa6118..a6cec7859 100644 --- a/gcloud/netapp/storage-pools/update +++ b/gcloud/netapp/storage-pools/update @@ -6,7 +6,8 @@ SYNOPSIS [--active-directory=ACTIVE_DIRECTORY] [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] [--capacity=CAPACITY] [--description=DESCRIPTION] - [--replica-zone=REPLICA_ZONE] [--update-labels=[KEY=VALUE,...]] + [--replica-zone=REPLICA_ZONE] [--total-iops=TOTAL_IOPS] + [--total-throughput=TOTAL_THROUGHPUT] [--update-labels=[KEY=VALUE,...]] [--zone=ZONE] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -96,6 +97,13 @@ FLAGS --replica-zone=REPLICA_ZONE String indicating replica zone for the Storage Pool + --total-iops=TOTAL_IOPS + Integer indicating total IOPS of the Storage Pool + + --total-throughput=TOTAL_THROUGHPUT + The total throughput of the Storage Pool in MiB/s or GiB/s units. If no + throughput unit is specified, MiB/s is assumed. + --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. diff --git a/gcloud/network-connectivity/internal-ranges/create b/gcloud/network-connectivity/internal-ranges/create index 00b980eb3..a65121b11 100644 --- a/gcloud/network-connectivity/internal-ranges/create +++ b/gcloud/network-connectivity/internal-ranges/create @@ -6,10 +6,12 @@ SYNOPSIS gcloud network-connectivity internal-ranges create (INTERNAL_RANGE : --region=REGION) --network=NETWORK (--ip-cidr-range=IP_CIDR_RANGE | [--prefix-length=PREFIX_LENGTH - : --exclude-cidr-ranges=[EXCLUDE_CIDR_RANGES,...] - --target-cidr-range=[TARGET_CIDR_RANGE,...]]) [--async] - [--description=DESCRIPTION] [--immutable] [--labels=[KEY=VALUE,...]] - [--overlaps=[OVERLAPS,...]] [--peering=PEERING; default="for-self"] + : --allocation_strategy=ALLOCATION_STRATEGY + --exclude-cidr-ranges=[EXCLUDE_CIDR_RANGES,...] + --first_available_ranges_lookup_size=FIRST_AVAILABLE_RANGES_LOOKUP_SIZE --target-cidr-range=[TARGET_CIDR_RANGE, + ...]]) [--async] [--description=DESCRIPTION] [--immutable] + [--labels=[KEY=VALUE,...]] [--overlaps=[OVERLAPS,...]] + [--peering=PEERING; default="for-self"] [--usage=USAGE; default="for-vpc"] [--migration-source=MIGRATION_SOURCE --migration-target=MIGRATION_TARGET] [GCLOUD_WIDE_FLAG ...] @@ -92,11 +94,44 @@ REQUIRED FLAGS Additional options for the internal range's address auto-allocation (allowed only when prefix-length is set): + --allocation_strategy=ALLOCATION_STRATEGY + Allocation strategy to be used when searching for a free range. + ALLOCATION_STRATEGY must be one of: + + first-available + Pick the first available address range. This strategy is + deterministic and the result is easy to predict. + + first-smallest-fitting + Pick the smallest but fitting available range. This + deterministic strategy minimizes fragmentation of the address + space. + + random + Random strategy, the legacy algorithm, used for backwards + compatibility. This allocation strategy remains efficient in + the case of concurrent allocation requests in the same peered + network space and doesn't require providing the level of + concurrency in an explicit parameter, but it is prone to + fragmenting available address space. + + random-first-n-available + Pick an arbitrary range out of the first N available ones. The + N will be set in the first_available_ranges_lookup_size flag. + This strategy should be used when concurrent allocation + requests are made in the same space of peered networks while + the fragmentation of the addrress space is reduced. + --exclude-cidr-ranges=[EXCLUDE_CIDR_RANGES,...] A list of CIDR ranges to exclude from the search for a free range. This can be used to exclude specific ranges that are already intended to have some other use. + --first_available_ranges_lookup_size=FIRST_AVAILABLE_RANGES_LOOKUP_SIZE + The number of ranges to be considered when using the + RANDOM_FIRST_N_AVAILABLE allocation strategy. This is only allowed + when allocation_strategy is set to RANDOM_FIRST_N_AVAILABLE. + --target-cidr-range=[TARGET_CIDR_RANGE,...] Can be set to narrow down or pick a different address space while searching for a free range. If not set, defaults to the diff --git a/gcloud/network-connectivity/policy-based-routes/create b/gcloud/network-connectivity/policy-based-routes/create index 63004ed2c..657cbe3aa 100644 --- a/gcloud/network-connectivity/policy-based-routes/create +++ b/gcloud/network-connectivity/policy-based-routes/create @@ -88,7 +88,7 @@ OPTIONAL FLAGS --protocol-version=PROTOCOL_VERSION; default="IPV4" Internet protocol versions that this policy-based route applies to. For this version, only IPV4 is supported. PROTOCOL_VERSION must be one of: - ipv4, protocol-version-unspecified. + ipv4, ipv6, protocol-version-unspecified. --source-range=SOURCE_RANGE Source IP range of outgoing packets that this policy-based route diff --git a/gcloud/network-management/vpc-flow-logs-configs/update b/gcloud/network-management/vpc-flow-logs-configs/update index 381ae5df3..4f26d40fb 100644 --- a/gcloud/network-management/vpc-flow-logs-configs/update +++ b/gcloud/network-management/vpc-flow-logs-configs/update @@ -12,7 +12,7 @@ SYNOPSIS | --vpn-tunnel=VPN_TUNNEL] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] + | --remove-labels=REMOVE_LABELS] [--metadata-fields=[METADATA_FIELDS,...] | --add-metadata-fields=[ADD_METADATA_FIELDS,...] --clear-metadata-fields @@ -201,8 +201,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) Update metadata_fields. diff --git a/gcloud/network-services/help b/gcloud/network-services/help index 9e8b36a3f..dee0a25dd 100644 --- a/gcloud/network-services/help +++ b/gcloud/network-services/help @@ -30,6 +30,9 @@ GROUPS meshes Manage Network Services Meshes. + operations + Manage Network Services Operations. + route-views View Network Services Route Views. diff --git a/gcloud/network-services/operations/cancel b/gcloud/network-services/operations/cancel new file mode 100644 index 000000000..32e883889 --- /dev/null +++ b/gcloud/network-services/operations/cancel @@ -0,0 +1,67 @@ +NAME + gcloud network-services operations cancel - cancel a Network Services long + running operation + +SYNOPSIS + gcloud network-services operations cancel (OPERATION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Cancel a Network Services long running operation. + +EXAMPLES + The following command cancels an operation with the full name + OPERATION_NAME: + + $ gcloud network-services operations cancel OPERATION_NAME + +POSITIONAL ARGUMENTS + Operation resource - Name of the operation to cancel. 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. + + 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 networkservices/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + These variants are also available: + + $ gcloud alpha network-services operations cancel + + $ gcloud beta network-services operations cancel + diff --git a/gcloud/network-services/operations/describe b/gcloud/network-services/operations/describe new file mode 100644 index 000000000..6d3c0c4b5 --- /dev/null +++ b/gcloud/network-services/operations/describe @@ -0,0 +1,67 @@ +NAME + gcloud network-services operations describe - show details of a Network + Services long running operation + +SYNOPSIS + gcloud network-services operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details of a Network Services long running operation. + +EXAMPLES + The following command describes an operation with the full name + OPERATION_NAME: + + $ gcloud network-services operations describe OPERATION_NAME + +POSITIONAL ARGUMENTS + Operation resource - Name of the operation 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 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. + + 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 networkservices/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + These variants are also available: + + $ gcloud alpha network-services operations describe + + $ gcloud beta network-services operations describe + diff --git a/gcloud/network-services/operations/help b/gcloud/network-services/operations/help new file mode 100644 index 000000000..130e026e6 --- /dev/null +++ b/gcloud/network-services/operations/help @@ -0,0 +1,36 @@ +NAME + gcloud network-services operations - manage Network Services Operations + +SYNOPSIS + gcloud network-services operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Network Services Operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + Cancel a Network Services long running operation. + + describe + Show details of a Network Services long running operation. + + list + List all Network Services long running operations. + + wait + Poll a Network Services long running operation. + +NOTES + These variants are also available: + + $ gcloud alpha network-services operations + + $ gcloud beta network-services operations + diff --git a/gcloud/network-services/operations/list b/gcloud/network-services/operations/list new file mode 100644 index 000000000..cbc3dadd5 --- /dev/null +++ b/gcloud/network-services/operations/list @@ -0,0 +1,88 @@ +NAME + gcloud network-services operations list - list all Network Services long + running operations + +SYNOPSIS + gcloud network-services operations list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all Network Services long running operations. + +EXAMPLES + The following command lists all operations in the current project and in + location global: + + $ gcloud network-services operations list --location=global + +REQUIRED FLAGS + Location resource - Location of the operations. 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 networkservices/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + These variants are also available: + + $ gcloud alpha network-services operations list + + $ gcloud beta network-services operations list + diff --git a/gcloud/network-services/operations/wait b/gcloud/network-services/operations/wait new file mode 100644 index 000000000..8aae6b717 --- /dev/null +++ b/gcloud/network-services/operations/wait @@ -0,0 +1,66 @@ +NAME + gcloud network-services operations wait - poll a Network Services long + running operation + +SYNOPSIS + gcloud network-services operations wait (OPERATION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Poll a Network Services long running operation. + +EXAMPLES + The following command polls an operation with the full name OPERATION_NAME: + + $ gcloud network-services operations wait OPERATION_NAME + +POSITIONAL ARGUMENTS + Operation resource - Name of the operation to poll. 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. + + 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 networkservices/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + These variants are also available: + + $ gcloud alpha network-services operations wait + + $ gcloud beta network-services operations wait + diff --git a/gcloud/observability/help b/gcloud/observability/help new file mode 100644 index 000000000..b6b9d7b33 --- /dev/null +++ b/gcloud/observability/help @@ -0,0 +1,19 @@ +NAME + gcloud observability - manage Observability resources + +SYNOPSIS + gcloud observability GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Observability resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + scopes + Manage Scope resources. diff --git a/gcloud/observability/scopes/describe b/gcloud/observability/scopes/describe new file mode 100644 index 000000000..3cf68c265 --- /dev/null +++ b/gcloud/observability/scopes/describe @@ -0,0 +1,61 @@ +NAME + gcloud observability scopes describe - describe scopes + +SYNOPSIS + gcloud observability scopes describe (SCOPE : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a scope + +EXAMPLES + To describe the scope, run: + + $ gcloud observability scopes describe + +POSITIONAL ARGUMENTS + Scope resource - Name of the resource. The format is: + + projects/{project}/locations/{location}/scopes/{scope} + + The {location} field must be set to global. The {scope} field must be set + to Default. 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 scope 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. + + SCOPE + ID of the scope or fully qualified identifier for the scope. + + To set the scope attribute: + ▸ provide the argument scope 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 scope resource. + + To set the location attribute: + ▸ provide the argument scope 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 observability/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/stackdriver/docs/ diff --git a/gcloud/observability/scopes/help b/gcloud/observability/scopes/help new file mode 100644 index 000000000..e999eeb67 --- /dev/null +++ b/gcloud/observability/scopes/help @@ -0,0 +1,22 @@ +NAME + gcloud observability scopes - manage Scope resources + +SYNOPSIS + gcloud observability scopes COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Scope 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 scopes. + + update + Update scopes. diff --git a/gcloud/observability/scopes/update b/gcloud/observability/scopes/update new file mode 100644 index 000000000..e4910b173 --- /dev/null +++ b/gcloud/observability/scopes/update @@ -0,0 +1,67 @@ +NAME + gcloud observability scopes update - update scopes + +SYNOPSIS + gcloud observability scopes update (SCOPE : --location=LOCATION) + [--log-scope=LOG_SCOPE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a scope + +EXAMPLES + To update the scope, run: + + $ gcloud observability scopes update + +POSITIONAL ARGUMENTS + Scope resource - Identifier. Name of the resource. The format is: + + projects/{project}/locations/{location}/scopes/{scope} + + The {location} field must be set to global. The {scope} field must be set + to Default. 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 scope 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. + + SCOPE + ID of the scope or fully qualified identifier for the scope. + + To set the scope attribute: + ▸ provide the argument scope 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 scope resource. + + To set the location attribute: + ▸ provide the argument scope on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --log-scope=LOG_SCOPE + The full resource name of the LogScope. For example: + + //logging.googleapis.com/projects/myproject/locations/global/logScopes/my-log-scope + +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 observability/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/stackdriver/docs/ diff --git a/gcloud/parametermanager/parameters/update b/gcloud/parametermanager/parameters/update index 10773f45b..c97c2f3ff 100644 --- a/gcloud/parametermanager/parameters/update +++ b/gcloud/parametermanager/parameters/update @@ -8,7 +8,7 @@ SYNOPSIS [--request-id=REQUEST_ID] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels - | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update the metadata of a parameter (e.g. labels). This command will return @@ -142,8 +142,20 @@ FLAGS --clear-labels Clear labels value and set to empty map. - --remove-labels=[__REMOVE_LABELS,...] - Remove existing value from map labels. + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/privateca/certificates/create b/gcloud/privateca/certificates/create index 6b0e136d1..1eab1ca2d 100644 --- a/gcloud/privateca/certificates/create +++ b/gcloud/privateca/certificates/create @@ -37,7 +37,7 @@ EXAMPLES --issuer-pool=my-pool --issuer-location=us-west1 \ --csr=./csr.pem --cert-output-file=./cert.pem --validity=P30D - To create a certificate using a client-generated key: + To create a certificate using a client-generated key: $ gcloud privateca certificates create frontend-server-tls \ --issuer-pool=my-pool --issuer-location=us-west1 \ diff --git a/gcloud/resource-manager/tags/keys/update b/gcloud/resource-manager/tags/keys/update index 94ac2d4ec..c3f2bf508 100644 --- a/gcloud/resource-manager/tags/keys/update +++ b/gcloud/resource-manager/tags/keys/update @@ -14,12 +14,12 @@ EXAMPLES To update a TagKey with id 123, run: $ gcloud resource-manager tags keys update tagKeys/123 \ - --description=foobar + --description=foobar --allowed-values-regex=.* To update a TagKey named env under organization 456, run: $ gcloud resource-manager tags keys update 456/env \ - --description=foobar + --description=foobar --allowed-values-regex=.* POSITIONAL ARGUMENTS RESOURCE_NAME diff --git a/gcloud/run/services/add-iam-policy-binding b/gcloud/run/services/add-iam-policy-binding index c777fdfcd..57b468bbe 100644 --- a/gcloud/run/services/add-iam-policy-binding +++ b/gcloud/run/services/add-iam-policy-binding @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud run services add-iam-policy-binding SERVICE --member=PRINCIPAL - --role=ROLE [--region=REGION] [GCLOUD_WIDE_FLAG ...] + --role=ROLE [--region=REGION] + [--condition=[KEY=VALUE,...] | --condition-from-file=PATH_TO_FILE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Add an IAM policy binding to the IAM policy of a Cloud Run service. One @@ -74,6 +76,44 @@ OPTIONAL FLAGS Region in which the resource can be found. Alternatively, set the property [run/region]. + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=PATH_TO_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --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, diff --git a/gcloud/run/services/remove-iam-policy-binding b/gcloud/run/services/remove-iam-policy-binding index 957cec440..766285753 100644 --- a/gcloud/run/services/remove-iam-policy-binding +++ b/gcloud/run/services/remove-iam-policy-binding @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud run services remove-iam-policy-binding SERVICE --member=PRINCIPAL - --role=ROLE [--region=REGION] [GCLOUD_WIDE_FLAG ...] + --role=ROLE [--region=REGION] + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=PATH_TO_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Remove an IAM policy binding from the IAM policy of a service. One binding @@ -75,6 +77,48 @@ OPTIONAL FLAGS Region in which the resource can be found. Alternatively, set the property [run/region]. + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=PATH_TO_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --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, diff --git a/gcloud/scc/iac-validation-reports/list b/gcloud/scc/iac-validation-reports/list index dd75bc283..bef3c3cd2 100644 --- a/gcloud/scc/iac-validation-reports/list +++ b/gcloud/scc/iac-validation-reports/list @@ -3,9 +3,10 @@ NAME Command Center IaC validation reports for an organization SYNOPSIS - gcloud scc iac-validation-reports list PARENT [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + gcloud scc iac-validation-reports list + ([PARENT] --location=LOCATION --organization=ORGANIZATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Lists all the Cloud Security Command Center (SCC) IaC validation reports @@ -18,10 +19,32 @@ EXAMPLES $ gcloud scc iac-validation-reports list \ organizations/123/locations/global/reports + Or using flags: + + $ gcloud scc iac-validation-reports list --organization=123 \ + --location=global + POSITIONAL ARGUMENTS - PARENT - Parent of IaC validation reports. Formatted as - organizations//locations//reports. + Exactly one of these must be specified: + + [PARENT] + Parent of the IaC validation reports or fully qualified identifier + for the IaC validation reports. + + Specify organization and location using flags. + + --location=LOCATION + When data residency controls are enabled, this attribute specifies + the location in which the resource is located and applicable. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --organization=ORGANIZATION + The organization ID (e.g., 123) that contains the resource. + + This flag argument must be specified if any of the other arguments + in this group are specified. LIST COMMAND FLAGS --filter=EXPRESSION @@ -58,8 +81,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securityposture/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the securityposture/v1 API. For more information, see + Security Command Center API. + (https://cloud.google.com/security-command-center) NOTES This variant is also available: diff --git a/gcloud/scc/manage/services/describe b/gcloud/scc/manage/services/describe index 8f93da4a7..c0774a3fa 100644 --- a/gcloud/scc/manage/services/describe +++ b/gcloud/scc/manage/services/describe @@ -62,6 +62,16 @@ POSITIONAL ARGUMENTS ◆ cloud-run-threat-detection (can be abbreviated as crtd) + ◆ vm-manager (can be abbreviated as vmm) + + ◆ ec2-vulnerability-assessment (can be abbreviated as ec2-va) + + ◆ gce-vulnerability-assessment (can be abbreviated as gce-va) + + ◆ azure-vulnerability-assessment (can be abbreviated as azure-va) + + ◆ notebook-security-scanner (can be abbreviated as nss) + REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/scc/manage/services/update b/gcloud/scc/manage/services/update index f33ea6fb0..f3372bf56 100644 --- a/gcloud/scc/manage/services/update +++ b/gcloud/scc/manage/services/update @@ -56,6 +56,16 @@ POSITIONAL ARGUMENTS ◆ cloud-run-threat-detection (can be abbreviated as crtd) + ◆ vm-manager (can be abbreviated as vmm) + + ◆ ec2-vulnerability-assessment (can be abbreviated as ec2-va) + + ◆ gce-vulnerability-assessment (can be abbreviated as gce-va) + + ◆ azure-vulnerability-assessment (can be abbreviated as azure-va) + + ◆ notebook-security-scanner (can be abbreviated as nss) + REQUIRED FLAGS At least one of these must be specified: diff --git a/gcloud/scc/posture-deployments/list b/gcloud/scc/posture-deployments/list index 4b4a0e593..7a61164b5 100644 --- a/gcloud/scc/posture-deployments/list +++ b/gcloud/scc/posture-deployments/list @@ -3,9 +3,10 @@ NAME Security Command Center posture deployments SYNOPSIS - gcloud scc posture-deployments list PARENT [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + gcloud scc posture-deployments list + ([PARENT] --location=LOCATION --organization=ORGANIZATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION List the details of the Cloud Security Command Center (SCC) posture @@ -18,11 +19,30 @@ EXAMPLES $ gcloud scc posture-deployments list \ organizations/123/locations/global + $ gcloud scc posture-deployments list --organization=123 \ + --location=global + POSITIONAL ARGUMENTS - PARENT - Organization for listing the Cloud Security Command Center posture - deployments available at the organization level. Formatted as - organizations//locations/. + Exactly one of these must be specified: + + [PARENT] + Parent of Cloud Security Command Center posture deployments. + Formatted as organizations//locations/. + + Specify organization and location using flags. + + --location=LOCATION + When data residency controls are enabled, this attribute specifies + the location in which the resource is located and applicable. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --organization=ORGANIZATION + The organization ID (e.g., 123) that contains the resource. + + This flag argument must be specified if any of the other arguments + in this group are specified. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/scc/posture-templates/list b/gcloud/scc/posture-templates/list index 57d5f34e1..8454bd8a6 100644 --- a/gcloud/scc/posture-templates/list +++ b/gcloud/scc/posture-templates/list @@ -13,16 +13,15 @@ DESCRIPTION EXAMPLES To list Cloud Security Command Center posture templates for organization - 123, run: + 123 and in the global location, run: $ gcloud scc posture-templates list \ organizations/123/locations/global POSITIONAL ARGUMENTS PARENT - Organization for listing the Cloud Security Command Center posture - templates available at the organization level. Formatted as - organizations//locations/. + Parent of Cloud Security Command Center posture templates. Formatted as + organizations//locations/ LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/scheduler/jobs/create/app-engine b/gcloud/scheduler/jobs/create/app-engine index 9f6f2a740..e764d1ab4 100644 --- a/gcloud/scheduler/jobs/create/app-engine +++ b/gcloud/scheduler/jobs/create/app-engine @@ -7,8 +7,8 @@ SYNOPSIS --schedule=SCHEDULE [--attempt-deadline=ATTEMPT_DEADLINE] [--description=DESCRIPTION] [--headers=[KEY=VALUE,...]] [--http-method=HTTP_METHOD; default="post"] - [--max-backoff=MAX_BACKOFF; default="1h"] - [--max-doublings=MAX_DOUBLINGS; default=16] + [--max-backoff=MAX_BACKOFF; default="3600s"] + [--max-doublings=MAX_DOUBLINGS; default=5] [--max-retry-attempts=MAX_RETRY_ATTEMPTS] [--max-retry-duration=MAX_RETRY_DURATION] [--min-backoff=MIN_BACKOFF; default="5s"] @@ -70,16 +70,16 @@ REQUIRED FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). OPTIONAL FLAGS --attempt-deadline=ATTEMPT_DEADLINE @@ -99,11 +99,11 @@ OPTIONAL FLAGS HTTP method to use for the request. HTTP_METHOD must be one of: delete, get, head, post, put. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -112,13 +112,14 @@ OPTIONAL FLAGS in range 0-5 inclusive. Default is 0. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task was + Time limit for retrying a failed job, measured from when the job was first run. If specified with --max-retry-attempts greater than 0, the - task will be retried until both limits are reached. Default is 0 (which - means unlimited). + job will be retried until both limits are reached. Default is 0 seconds + (which means unlimited); however, if --max-retry-attempts is also 0, a + job attempt won't be retried if it fails. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. --relative-url=RELATIVE_URL; default="/" diff --git a/gcloud/scheduler/jobs/create/http b/gcloud/scheduler/jobs/create/http index f46896b54..3f25299cd 100644 --- a/gcloud/scheduler/jobs/create/http +++ b/gcloud/scheduler/jobs/create/http @@ -7,8 +7,8 @@ SYNOPSIS --schedule=SCHEDULE --uri=URI [--attempt-deadline=ATTEMPT_DEADLINE] [--description=DESCRIPTION] [--headers=[KEY=VALUE,...]] [--http-method=HTTP_METHOD; default="post"] - [--max-backoff=MAX_BACKOFF; default="1h"] - [--max-doublings=MAX_DOUBLINGS; default=16] + [--max-backoff=MAX_BACKOFF; default="3600s"] + [--max-doublings=MAX_DOUBLINGS; default=5] [--max-retry-attempts=MAX_RETRY_ATTEMPTS] [--max-retry-duration=MAX_RETRY_DURATION] [--min-backoff=MIN_BACKOFF; default="5s"] @@ -73,16 +73,16 @@ REQUIRED FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --uri=URI The full URI path that the request will be sent to. This string must @@ -109,11 +109,11 @@ OPTIONAL FLAGS HTTP method to use for the request. HTTP_METHOD must be one of: delete, get, head, post, put. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -122,13 +122,14 @@ OPTIONAL FLAGS in range 0-5 inclusive. Default is 0. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task was + Time limit for retrying a failed job, measured from when the job was first run. If specified with --max-retry-attempts greater than 0, the - task will be retried until both limits are reached. Default is 0 (which - means unlimited). + job will be retried until both limits are reached. Default is 0 seconds + (which means unlimited); however, if --max-retry-attempts is also 0, a + job attempt won't be retried if it fails. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. --time-zone=TIME_ZONE; default="Etc/UTC" diff --git a/gcloud/scheduler/jobs/create/pubsub b/gcloud/scheduler/jobs/create/pubsub index e9340e7b7..c6da86e86 100644 --- a/gcloud/scheduler/jobs/create/pubsub +++ b/gcloud/scheduler/jobs/create/pubsub @@ -7,8 +7,8 @@ SYNOPSIS --schedule=SCHEDULE --topic=TOPIC (--attributes=ATTRIBUTES --message-body=MESSAGE_BODY | --message-body-from-file=PATH_TO_FILE) [--description=DESCRIPTION] - [--max-backoff=MAX_BACKOFF; default="1h"] - [--max-doublings=MAX_DOUBLINGS; default=16] + [--max-backoff=MAX_BACKOFF; default="3600s"] + [--max-doublings=MAX_DOUBLINGS; default=5] [--max-retry-attempts=MAX_RETRY_ATTEMPTS] [--max-retry-duration=MAX_RETRY_DURATION] [--min-backoff=MIN_BACKOFF; default="5s"] @@ -68,16 +68,16 @@ REQUIRED FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --topic=TOPIC Name of the Google Cloud Pub/Sub topic to publish to when the job runs. @@ -105,11 +105,11 @@ OPTIONAL FLAGS --description=DESCRIPTION Human-readable description of the job. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -118,13 +118,14 @@ OPTIONAL FLAGS in range 0-5 inclusive. Default is 0. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task was + Time limit for retrying a failed job, measured from when the job was first run. If specified with --max-retry-attempts greater than 0, the - task will be retried until both limits are reached. Default is 0 (which - means unlimited). + job will be retried until both limits are reached. Default is 0 seconds + (which means unlimited); however, if --max-retry-attempts is also 0, a + job attempt won't be retried if it fails. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. --time-zone=TIME_ZONE; default="Etc/UTC" diff --git a/gcloud/scheduler/jobs/update/app-engine b/gcloud/scheduler/jobs/update/app-engine index ae2e82823..e6bbe874b 100644 --- a/gcloud/scheduler/jobs/update/app-engine +++ b/gcloud/scheduler/jobs/update/app-engine @@ -9,8 +9,8 @@ SYNOPSIS [--version=VERSION] [--clear-headers | --remove-headers=[REMOVE_HEADERS,...] --update-headers=[KEY=VALUE,...]] - [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"] - [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16] + [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="3600s"] + [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=5] [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS] [--clear-max-retry-duration | --max-retry-duration=MAX_RETRY_DURATION] [--clear-message-body | --message-body=MESSAGE_BODY @@ -85,16 +85,16 @@ FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --version=VERSION Version of the App Engine service to send the request to. @@ -118,16 +118,16 @@ FLAGS --clear-max-backoff Clear the field corresponding to --max-backoff. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). At most one of these can be specified: --clear-max-doublings Clear the field corresponding to --max-doublings. - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -146,10 +146,11 @@ FLAGS Clear the field corresponding to --max-retry-duration. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task - was first run. If specified with --max-retry-attempts greater than 0, - the task will be retried until both limits are reached. Default is 0 - (which means unlimited). + Time limit for retrying a failed job, measured from when the job was + first run. If specified with --max-retry-attempts greater than 0, the + job will be retried until both limits are reached. Default is 0 + seconds (which means unlimited); however, if --max-retry-attempts is + also 0, a job attempt won't be retried if it fails. At most one of these can be specified: @@ -173,7 +174,7 @@ FLAGS Clear the field corresponding to --min-backoff. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. At most one of these can be specified: diff --git a/gcloud/scheduler/jobs/update/http b/gcloud/scheduler/jobs/update/http index 4349d325c..978329f1e 100644 --- a/gcloud/scheduler/jobs/update/http +++ b/gcloud/scheduler/jobs/update/http @@ -14,8 +14,8 @@ SYNOPSIS : --oidc-token-audience=OIDC_TOKEN_AUDIENCE]] [--clear-headers | --remove-headers=[REMOVE_HEADERS,...] --update-headers=[KEY=VALUE,...]] - [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"] - [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16] + [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="3600s"] + [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=5] [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS] [--clear-max-retry-duration | --max-retry-duration=MAX_RETRY_DURATION] [--clear-message-body | --message-body=MESSAGE_BODY @@ -87,16 +87,16 @@ FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --uri=URI The full URI path that the request will be sent to. This string must @@ -172,16 +172,16 @@ FLAGS --clear-max-backoff Clear the field corresponding to --max-backoff. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). At most one of these can be specified: --clear-max-doublings Clear the field corresponding to --max-doublings. - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -200,10 +200,11 @@ FLAGS Clear the field corresponding to --max-retry-duration. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task - was first run. If specified with --max-retry-attempts greater than 0, - the task will be retried until both limits are reached. Default is 0 - (which means unlimited). + Time limit for retrying a failed job, measured from when the job was + first run. If specified with --max-retry-attempts greater than 0, the + job will be retried until both limits are reached. Default is 0 + seconds (which means unlimited); however, if --max-retry-attempts is + also 0, a job attempt won't be retried if it fails. At most one of these can be specified: @@ -227,7 +228,7 @@ FLAGS Clear the field corresponding to --min-backoff. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. At most one of these can be specified: diff --git a/gcloud/scheduler/jobs/update/pubsub b/gcloud/scheduler/jobs/update/pubsub index 41617ddb5..9456f8a8c 100644 --- a/gcloud/scheduler/jobs/update/pubsub +++ b/gcloud/scheduler/jobs/update/pubsub @@ -7,8 +7,8 @@ SYNOPSIS [--description=DESCRIPTION] [--schedule=SCHEDULE] [--topic=TOPIC] [--clear-attributes | --remove-attributes=[REMOVE_ATTRIBUTES,...] --update-attributes=[KEY=VALUE,...]] - [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="1h"] - [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=16] + [--clear-max-backoff | --max-backoff=MAX_BACKOFF; default="3600s"] + [--clear-max-doublings | --max-doublings=MAX_DOUBLINGS; default=5] [--clear-max-retry-attempts | --max-retry-attempts=MAX_RETRY_ATTEMPTS] [--clear-max-retry-duration | --max-retry-duration=MAX_RETRY_DURATION] [--clear-min-backoff | --min-backoff=MIN_BACKOFF; default="5s"] @@ -70,16 +70,16 @@ FLAGS if the n+1 execution is scheduled to run at 16:00 but the n execution takes until 16:15, the n+1 execution will not start until 16:15. A scheduled start time will be delayed if the previous execution has not - ended when its scheduled time occurs. + ended when its scheduled time occurs. Learn more about the cron job + format + (https://cloud.google.com/scheduler/docs/configuring/cron-job-schedules). If --retry-count > 0 and a job attempt fails, the job will be tried a - total of --retry-count times, with exponential backoff, until the next - scheduled start time. - - The schedule can be either of the following types: - ◆ Crontab: http://en.wikipedia.org/wiki/Cron#Overview - ◆ English-like schedule: - https://cloud.google.com/scheduler/docs/quickstart#defining_the_job_schedule + total of --retry-count times, with exponential backoff, until the job + succeeds or the number of retries is exhausted. Note that the next + scheduled execution time might be skipped if the retries continue + through that time. For more information, see Retry jobs + (https://cloud.google.com/scheduler/docs/configuring/retry-jobs). --topic=TOPIC Name of the Google Cloud Pub/Sub topic to publish to when the job runs. @@ -102,16 +102,16 @@ FLAGS --clear-max-backoff Clear the field corresponding to --max-backoff. - --max-backoff=MAX_BACKOFF; default="1h" - Maximum amount of time to wait before retrying a task after it fails. - For example, 10m. Default is 1h. + --max-backoff=MAX_BACKOFF; default="3600s" + Maximum amount of time to wait before retrying a job after it fails. + For example, 60s. Default is 3600s (1 hour). At most one of these can be specified: --clear-max-doublings Clear the field corresponding to --max-doublings. - --max-doublings=MAX_DOUBLINGS; default=16 + --max-doublings=MAX_DOUBLINGS; default=5 Maximum number of times that the interval between failed job retries will be doubled before the increase becomes constant. @@ -130,10 +130,11 @@ FLAGS Clear the field corresponding to --max-retry-duration. --max-retry-duration=MAX_RETRY_DURATION - Time limit for retrying a failed task, measured from when the task - was first run. If specified with --max-retry-attempts greater than 0, - the task will be retried until both limits are reached. Default is 0 - (which means unlimited). + Time limit for retrying a failed job, measured from when the job was + first run. If specified with --max-retry-attempts greater than 0, the + job will be retried until both limits are reached. Default is 0 + seconds (which means unlimited); however, if --max-retry-attempts is + also 0, a job attempt won't be retried if it fails. At most one of these can be specified: @@ -141,7 +142,7 @@ FLAGS Clear the field corresponding to --min-backoff. --min-backoff=MIN_BACKOFF; default="5s" - Minimum amount of time to wait before retrying a task after it fails. + Minimum amount of time to wait before retrying a job after it fails. For example, 10s. Default is 5s. At most one of these can be specified: diff --git a/gcloud/spanner/databases/update b/gcloud/spanner/databases/update index c2e767046..98a67e3f6 100644 --- a/gcloud/spanner/databases/update +++ b/gcloud/spanner/databases/update @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud spanner databases update (DATABASE : --instance=INSTANCE) [--async] - [--[no-]enable-drop-protection] [GCLOUD_WIDE_FLAG ...] + [--[no-]enable-drop-protection | --kms-keys=KMS_KEY,[KMS_KEY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a Cloud Spanner database. @@ -21,6 +22,11 @@ EXAMPLES $ gcloud spanner databases update my-database \ --no-enable-drop-protection + To update KMS key references for a Cloud Spanner database 'my-database', + run: + + $ gcloud spanner databases update my-database --kms-keys="KEY1,KEY2" + POSITIONAL ARGUMENTS Database resource - The Cloud Spanner database to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -58,10 +64,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. - --[no-]enable-drop-protection - Enable database deletion protection on this database. Use - --enable-drop-protection to enable and --no-enable-drop-protection to - disable. + At most one of these can be specified: + + --[no-]enable-drop-protection + Enable database deletion protection on this database. Use + --enable-drop-protection to enable and --no-enable-drop-protection to + disable. + + --kms-keys=KMS_KEY,[KMS_KEY,...] + Update KMS key references for this database. Users should always + provide the full set of required KMS key references. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/spanner/operations/describe b/gcloud/spanner/operations/describe index 2ac9ee7a5..55eb2e490 100644 --- a/gcloud/spanner/operations/describe +++ b/gcloud/spanner/operations/describe @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud spanner operations describe OPERATION-ID (--instance=INSTANCE | --instance-config=INSTANCE_CONFIG) - [--backup=BACKUP] [--database=DATABASE] [GCLOUD_WIDE_FLAG ...] + [--backup=BACKUP] [--database=DATABASE] + [--instance-partition=INSTANCE_PARTITION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Describe a Cloud Spanner operation. @@ -25,6 +26,11 @@ EXAMPLES $ gcloud spanner operations describe _auto_12345 \ --instance=my-instance-id --backup=my-backup-id + To describe an instance partition operation, run: + + $ gcloud spanner operations describe _auto_12345 \ + --instance=my-instance-id --instance-partition=my-partition-id + POSITIONAL ARGUMENTS OPERATION-ID ID of the operation @@ -47,6 +53,10 @@ OPTIONAL FLAGS For a database operation, the name of the database the operation is executing on. + --instance-partition=INSTANCE_PARTITION + For an instance partition operation, the name of the instance partition + the operation is executing on. + 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/sql/backups/restore b/gcloud/sql/backups/restore index 6911a3cc4..9917831bb 100644 --- a/gcloud/sql/backups/restore +++ b/gcloud/sql/backups/restore @@ -160,7 +160,10 @@ OPTIONAL FLAGS --cpu=CPU Whole number value indicating how many cores are desired in the machine. Both --cpu and --memory must be specified if a custom machine - type is desired, and the --tier flag must be omitted. + type is desired, and the --tier flag must be omitted.--cpu and --memory + flags are not compatible with the Enterprise Plus edition. These flags + should not be used when creating an Enterprise Plus edition, as the + machine configuration is determined by the --tier flag instead. --database-version=DATABASE_VERSION The database engine type and versions. If left unspecified, no changes @@ -254,7 +257,10 @@ OPTIONAL FLAGS machine. A size unit should be provided (eg. 3072MiB or 9GiB) - if no units are specified, GiB is assumed. Both --cpu and --memory must be specified if a custom machine type is desired, and the --tier flag must - be omitted. + be omitted. --cpu and --memory flags are not compatible with the + Enterprise Plus edition. These flags should not be used when creating + an Enterprise Plus edition, as the machine configuration is determined + by the --tier flag instead. --network=NETWORK Network in the current project that the instance will be part of. To diff --git a/gcloud/sql/instances/clone b/gcloud/sql/instances/clone index 8211b1293..48041c70e 100644 --- a/gcloud/sql/instances/clone +++ b/gcloud/sql/instances/clone @@ -33,29 +33,35 @@ EXAMPLES To clone an instance from its current state (most recent binary log coordinates): - $ gcloud sql instances clone instance-foo instance-bar + $ gcloud sql instances clone my-source-instance my-cloned-instance To clone a MySQL instance from an earlier point in time (past binary log coordinates): - $ gcloud sql instances clone instance-foo instance-bar \ + $ gcloud sql instances clone my-source-instance my-cloned-instance \ --bin-log-file-name mysql-bin.000020 --bin-log-position 170 To clone a MySQL source instance at a specific point in time: - $ gcloud sql instances clone instance-foo instance-bar \ + $ gcloud sql instances clone my-source-instance my-cloned-instance \ --point-in-time '2012-11-15T16:19:00.094Z' To clone a PostgreSQL source instance at a specific point in time: - $ gcloud sql instances clone instance-foo instance-bar \ + $ gcloud sql instances clone my-source-instance my-cloned-instance \ --point-in-time '2012-11-15T16:19:00.094Z' To clone a SQL Server source instance at a specific point in time: - $ gcloud sql instances clone instance-foo instance-bar \ + $ gcloud sql instances clone my-source-instance my-cloned-instance \ --point-in-time '2012-11-15T16:19:00.094Z' + To clone a deleted instance, include the name and deletion time of the + source instance: + + $ gcloud sql instances clone my-source-instance my-cloned-instance \ + --source-instance-deletion-time '2012-11-15T16:19:00.094Z' + POSITIONAL ARGUMENTS SOURCE Cloud SQL instance ID of the source. diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index 3027a9b99..6a78dd16e 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -188,7 +188,10 @@ FLAGS --cpu=CPU Whole number value indicating how many cores are desired in the machine. Both --cpu and --memory must be specified if a custom machine - type is desired, and the --tier flag must be omitted. + type is desired, and the --tier flag must be omitted.--cpu and --memory + flags are not compatible with the Enterprise Plus edition. These flags + should not be used when creating an Enterprise Plus edition, as the + machine configuration is determined by the --tier flag instead. --custom-subject-alternative-names=DNS,[DNS,[DNS]] A comma-separated list of DNS names to add to the instance's SSL @@ -344,7 +347,10 @@ FLAGS machine. A size unit should be provided (eg. 3072MiB or 9GiB) - if no units are specified, GiB is assumed. Both --cpu and --memory must be specified if a custom machine type is desired, and the --tier flag must - be omitted. + be omitted. --cpu and --memory flags are not compatible with the + Enterprise Plus edition. These flags should not be used when creating + an Enterprise Plus edition, as the machine configuration is determined + by the --tier flag instead. --network=NETWORK Network in the current project that the instance will be part of. To diff --git a/gcloud/sql/instances/get-latest-recovery-time b/gcloud/sql/instances/get-latest-recovery-time index f825c7779..bfdfdd8b0 100644 --- a/gcloud/sql/instances/get-latest-recovery-time +++ b/gcloud/sql/instances/get-latest-recovery-time @@ -16,6 +16,11 @@ EXAMPLES $ gcloud sql instances get-latest-recovery-time instance-foo + To retrieve the latest recovery time for an instance that has been deleted: + + $ gcloud sql instances get-latest-recovery-time instance-foo \ + --source-instance-deletion-time '2012-11-15T16:19:00.094Z' + POSITIONAL ARGUMENTS INSTANCE Cloud SQL instance ID. diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index 09a90b98a..89e13e894 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -145,7 +145,10 @@ FLAGS --cpu=CPU Whole number value indicating how many cores are desired in the machine. Both --cpu and --memory must be specified if a custom machine - type is desired, and the --tier flag must be omitted. + type is desired, and the --tier flag must be omitted.--cpu and --memory + flags are not compatible with the Enterprise Plus edition. These flags + should not be used when creating an Enterprise Plus edition, as the + machine configuration is determined by the --tier flag instead. --database-version=DATABASE_VERSION The database engine type and versions. If left unspecified, no changes @@ -317,7 +320,10 @@ FLAGS machine. A size unit should be provided (eg. 3072MiB or 9GiB) - if no units are specified, GiB is assumed. Both --cpu and --memory must be specified if a custom machine type is desired, and the --tier flag must - be omitted. + be omitted. --cpu and --memory flags are not compatible with the + Enterprise Plus edition. These flags should not be used when creating + an Enterprise Plus edition, as the machine configuration is determined + by the --tier flag instead. --network=NETWORK Network in the current project that the instance will be part of. To diff --git a/gcloud/sql/users/create b/gcloud/sql/users/create index 0056c357a..6013fbaf1 100644 --- a/gcloud/sql/users/create +++ b/gcloud/sql/users/create @@ -41,24 +41,20 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. - This flag is available only for MySQL. --[no-]password-policy-enable-failed-attempts-check - Enables the failed login attempts check if set to true. This flag is - available only for MySQL. Use + Enables the failed login attempts check if set to true. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. --[no-]password-policy-enable-password-verification - The current password must be specified when altering the password. This - flag is available only for MySQL. Use + The current password must be specified when altering the password. Use --password-policy-enable-password-verification to enable and --no-password-policy-enable-password-verification to disable. --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION Expiration duration after a password is updated, for example, 2d for 2 days. See gcloud topic datetimes for information on duration formats. - This flag is available only for MySQL. --type=TYPE Cloud SQL user's type. It determines the method to authenticate the diff --git a/gcloud/sql/users/set-password-policy b/gcloud/sql/users/set-password-policy index 3c341215e..33019d794 100644 --- a/gcloud/sql/users/set-password-policy +++ b/gcloud/sql/users/set-password-policy @@ -57,24 +57,20 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. - This flag is available only for MySQL. --[no-]password-policy-enable-failed-attempts-check - Enables the failed login attempts check if set to true. This flag is - available only for MySQL. Use + Enables the failed login attempts check if set to true. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. --[no-]password-policy-enable-password-verification - The current password must be specified when altering the password. This - flag is available only for MySQL. Use + The current password must be specified when altering the password. Use --password-policy-enable-password-verification to enable and --no-password-policy-enable-password-verification to disable. --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION Expiration duration after a password is updated, for example, 2d for 2 days. See gcloud topic datetimes for information on duration formats. - This flag is available only for MySQL. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/storage/rm b/gcloud/storage/rm index 0533232df..55ddc4f03 100644 --- a/gcloud/storage/rm +++ b/gcloud/storage/rm @@ -80,10 +80,11 @@ FLAGS --recursive, -R, -r Recursively delete the contents of buckets or directories that match - the path expression. If the path is set to a bucket, like gs://bucket, - the bucket is also deleted. This option implies the --all-versions - option. If you want to delete only live object versions, use the ``**'' - wildcard instead. + the path expression. By default, this will delete managed folders as + well. If the path is set to a bucket, like gs://bucket, the bucket is + also deleted. This option implies the --all-versions option. If you + want to delete only live object versions, use the ``**'' wildcard + instead. PRECONDITION FLAGS --if-generation-match=GENERATION diff --git a/gcloud/workstations/configs/create b/gcloud/workstations/configs/create index 7cff4e4ff..5e607bfa9 100644 --- a/gcloud/workstations/configs/create +++ b/gcloud/workstations/configs/create @@ -19,10 +19,8 @@ SYNOPSIS [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] - [--network-tags=[NETWORK_TAGS,...]] - [--pd-disk-type=PD_DISK_TYPE; default="pd-standard"] - [--pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete"] - [--pool-size=POOL_SIZE] [--replica-zones=[REPLICA_ZONES,...]] + [--network-tags=[NETWORK_TAGS,...]] [--pool-size=POOL_SIZE] + [--replica-zones=[REPLICA_ZONES,...]] [--running-timeout=RUNNING_TIMEOUT; default=7200] [--service-account=SERVICE_ACCOUNT] [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] @@ -34,7 +32,9 @@ SYNOPSIS | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE; default="codeoss"] [--kms-key=KMS_KEY : --kms-key-service-account=KMS_KEY_SERVICE_ACCOUNT] - [--pd-disk-size=PD_DISK_SIZE; default=200 + [--no-persistent-storage | --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 ...] DESCRIPTION @@ -203,7 +203,37 @@ FLAGS the root VM. --ephemeral-directory=[PROPERTY=VALUE,...] - Ephemeral directory which won't persist across workstation sessions. + Ephemeral directory which won't persist across workstation sessions. An + ephemeral directory is backed by a Compute Engine persistent disk whose + mount-path, source-snapshot, source-image, and read-only are + configurable. + + mount-path + Location of this directory in the running workstation. + + source-snapshot + Name of the snapshot to use as the source for the disk. Must be + empty if [source_image][] is set. Must be empty if [read_only][] is + false. Updating [source_snapshot][] will update content in the + ephemeral directory after the workstation is restarted. + + source-image + Name of the disk image to use as the source for the disk. Must be + empty if [source_snapshot][] is set. Updating [source_image][] will + update content in the ephemeral directory after the workstation is + restarted. + + read-only + Whether the disk is read only. If true, the disk may be shared by + multiple VMs and [source_snapshot][] must be set. Set to false when + not specified and true when specified. + + Example: + + $ gcloud workstations configs create \ + --ephemeral-directory="mount-path=/home2,disk-type=pd-balanced,s\ + ource-snapshot=projects/my-project/global/snapshots/snapshot,read-on\ + ly=true" --grant-workstation-admin-role-on-create Default value is false. If set, creator of a workstation will get @@ -244,20 +274,6 @@ FLAGS $ gcloud workstations configs create --network-tags=tag_1,tag_2 - --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. - --pool-size=POOL_SIZE Number of instances to pool for faster Workstation startup. @@ -372,12 +388,34 @@ FLAGS 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. + --no-persistent-storage + If set, workstations under this configuration will not have a + persistent directory. - --pd-source-snapshot=PD_SOURCE_SNAPSHOT - Name of the snapshot to use as the source for the home disk. + 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-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,