From 82f3a6666403a882995179eb7198632d7a11b931 Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 14 May 2025 10:45:02 +0000 Subject: [PATCH] gcloud: Wed May 14 10:45:02 UTC 2025 --- gcloud/_version | 8 +- gcloud/alloydb/instances/create | 32 +- gcloud/alloydb/instances/create-secondary | 4 +- gcloud/alloydb/instances/update | 4 +- gcloud/alpha/ai/endpoints/deploy-model | 8 +- gcloud/alpha/alloydb/instances/create | 32 +- .../alpha/alloydb/instances/create-secondary | 4 +- gcloud/alpha/alloydb/instances/update | 4 +- gcloud/alpha/artifacts/repositories/list | 38 +-- gcloud/alpha/backup-dr/backups/update | 9 - gcloud/alpha/bigtable/instances/tables/create | 7 + gcloud/alpha/bigtable/instances/tables/update | 13 + gcloud/alpha/bigtable/tables/create | 7 + gcloud/alpha/bigtable/tables/update | 13 + .../composer/environments/storage/dags/delete | 2 +- .../composer/environments/storage/dags/list | 2 +- .../composer/environments/storage/data/delete | 2 +- .../composer/environments/storage/data/list | 2 +- .../environments/storage/plugins/delete | 2 +- .../environments/storage/plugins/list | 2 +- .../compute/backend-services/add-backend | 4 +- gcloud/alpha/compute/backend-services/create | 4 +- gcloud/alpha/compute/backend-services/update | 12 +- .../compute/backend-services/update-backend | 4 +- .../firewall-policies/mirroring-rules/create | 2 +- .../firewall-policies/mirroring-rules/update | 2 +- .../compute/firewall-policies/rules/create | 2 +- .../compute/firewall-policies/rules/update | 2 +- gcloud/alpha/compute/firewall-rules/create | 5 + gcloud/alpha/compute/forwarding-rules/update | 8 +- gcloud/alpha/compute/help | 6 + .../compute/instant-snapshot-groups/create | 80 +++++ .../compute/instant-snapshot-groups/describe | 74 +++++ .../compute/instant-snapshot-groups/help | 30 ++ .../interconnects/application-awareness/help | 4 + .../application-awareness/update | 50 ++++ gcloud/alpha/compute/networks/create | 6 +- gcloud/alpha/compute/networks/subnets/create | 7 +- .../alpha/compute/preview-features/describe | 54 ++++ gcloud/alpha/compute/preview-features/help | 33 +++ gcloud/alpha/compute/preview-features/list | 66 +++++ gcloud/alpha/compute/preview-features/update | 73 +++++ gcloud/alpha/compute/routes/create | 6 +- .../backup-restore/backup-channels/create | 2 +- .../backup-restore/restore-channels/create | 2 +- .../packages/resource-bundles/releases/create | 6 +- .../packages/resource-bundles/releases/create | 6 +- .../dataplex/datascans/create/data-discovery | 9 +- .../dataplex/datascans/update/data-discovery | 65 +++- .../alpha/dataplex/encryption-config/create | 73 +++++ .../alpha/dataplex/encryption-config/describe | 71 +++++ gcloud/alpha/dataplex/encryption-config/help | 32 ++ .../glossaries/add-iam-policy-binding | 90 ++++++ .../dataplex/glossaries/categories/create | 104 +++++++ .../dataplex/glossaries/categories/delete | 79 +++++ .../dataplex/glossaries/categories/describe | 79 +++++ .../alpha/dataplex/glossaries/categories/help | 42 +++ .../alpha/dataplex/glossaries/categories/list | 104 +++++++ .../dataplex/glossaries/categories/update | 108 +++++++ gcloud/alpha/dataplex/glossaries/create | 94 ++++++ gcloud/alpha/dataplex/glossaries/delete | 75 +++++ gcloud/alpha/dataplex/glossaries/describe | 70 +++++ .../alpha/dataplex/glossaries/get-iam-policy | 99 +++++++ gcloud/alpha/dataplex/glossaries/help | 62 ++++ gcloud/alpha/dataplex/glossaries/list | 88 ++++++ .../glossaries/remove-iam-policy-binding | 91 ++++++ .../alpha/dataplex/glossaries/set-iam-policy | 74 +++++ gcloud/alpha/dataplex/glossaries/terms/create | 104 +++++++ gcloud/alpha/dataplex/glossaries/terms/delete | 80 +++++ .../alpha/dataplex/glossaries/terms/describe | 80 +++++ gcloud/alpha/dataplex/glossaries/terms/help | 42 +++ gcloud/alpha/dataplex/glossaries/terms/list | 104 +++++++ gcloud/alpha/dataplex/glossaries/terms/update | 107 +++++++ gcloud/alpha/dataplex/glossaries/update | 94 ++++++ gcloud/alpha/dataplex/help | 9 + gcloud/alpha/dataplex/metadata-jobs/cancel | 68 +++++ gcloud/alpha/dataplex/metadata-jobs/create | 258 ++++++++++++++++ gcloud/alpha/dataplex/metadata-jobs/describe | 69 +++++ gcloud/alpha/dataplex/metadata-jobs/help | 35 +++ gcloud/alpha/dataplex/metadata-jobs/list | 88 ++++++ gcloud/alpha/dataproc/clusters/create | 22 +- gcloud/alpha/dataproc/clusters/update | 33 ++- gcloud/alpha/deploy/job-runs/terminate | 6 +- gcloud/alpha/deploy/releases/create | 4 + gcloud/alpha/deploy/releases/promote | 8 +- gcloud/alpha/deploy/rollouts/advance | 6 +- gcloud/alpha/deploy/rollouts/approve | 7 +- gcloud/alpha/deploy/rollouts/cancel | 7 +- gcloud/alpha/deploy/rollouts/ignore-job | 7 +- gcloud/alpha/deploy/rollouts/reject | 7 +- gcloud/alpha/deploy/rollouts/retry-job | 7 +- gcloud/alpha/deploy/targets/redeploy | 7 +- gcloud/alpha/deploy/targets/rollback | 9 +- .../iam/workforce-pools/providers/create-oidc | 24 +- .../iam/workforce-pools/providers/update-oidc | 26 +- gcloud/alpha/managed-kafka/acls/add-acl-entry | 4 +- .../alpha/managed-kafka/acls/remove-acl-entry | 4 +- gcloud/alpha/managed-kafka/clusters/create | 27 +- gcloud/alpha/managed-kafka/clusters/update | 27 +- .../managed-kafka/consumer-groups/update | 2 +- gcloud/alpha/managed-kafka/help | 3 + .../managed-kafka/schema-registries/create | 71 +++++ .../managed-kafka/schema-registries/delete | 72 +++++ .../managed-kafka/schema-registries/describe | 72 +++++ .../managed-kafka/schema-registries/help | 37 +++ .../managed-kafka/schema-registries/list | 86 ++++++ gcloud/alpha/monitoring/snoozes/create | 21 +- .../alpha/netapp/volumes/replications/create | 4 +- .../intercept-deployment-groups/create | 4 +- .../intercept-deployment-groups/delete | 4 +- .../intercept-deployment-groups/describe | 4 +- .../intercept-deployment-groups/help | 4 +- .../intercept-deployment-groups/list | 4 +- .../intercept-deployment-groups/update | 4 +- .../intercept-deployments/create | 4 +- .../intercept-deployments/delete | 4 +- .../intercept-deployments/describe | 4 +- .../intercept-deployments/help | 4 +- .../intercept-deployments/list | 4 +- .../intercept-deployments/update | 4 +- .../create | 5 +- .../delete | 5 +- .../describe | 5 +- .../help | 4 +- .../list | 4 +- .../update | 5 +- .../intercept-endpoint-groups/create | 4 +- .../intercept-endpoint-groups/delete | 4 +- .../intercept-endpoint-groups/describe | 4 +- .../intercept-endpoint-groups/help | 4 +- .../intercept-endpoint-groups/list | 4 +- .../intercept-endpoint-groups/update | 4 +- .../security-profile-groups/create | 24 +- .../security-profile-groups/update | 12 +- .../security-profiles/custom-intercept/create | 4 +- .../security-profiles/custom-intercept/delete | 4 +- .../custom-intercept/describe | 4 +- .../security-profiles/custom-intercept/help | 4 +- .../security-profiles/custom-intercept/list | 4 +- .../security-profiles/custom-intercept/update | 4 +- gcloud/alpha/run/worker-pools/describe | 25 +- gcloud/alpha/scc/findings/bulk-mute | 13 +- gcloud/alpha/scc/findings/create | 13 +- gcloud/alpha/scc/findings/group | 13 +- gcloud/alpha/scc/findings/list | 13 +- gcloud/alpha/scc/findings/list-marks | 13 +- gcloud/alpha/scc/findings/set-mute | 13 +- gcloud/alpha/scc/findings/update | 13 +- gcloud/alpha/scc/findings/update-marks | 13 +- gcloud/alpha/scc/muteconfigs/create | 13 +- gcloud/alpha/scc/muteconfigs/delete | 13 +- gcloud/alpha/scc/muteconfigs/get | 13 +- gcloud/alpha/scc/muteconfigs/list | 13 +- gcloud/alpha/scc/muteconfigs/update | 13 +- .../alpha/spanner/instance-partitions/delete | 6 +- .../spanner/instance-partitions/describe | 12 +- gcloud/alpha/spanner/instance-partitions/help | 12 +- gcloud/alpha/spanner/instance-partitions/list | 14 +- .../alpha/spanner/instance-partitions/update | 16 +- gcloud/alpha/spanner/instances/move | 2 +- gcloud/alpha/spanner/operations/cancel | 5 +- gcloud/alpha/spanner/operations/list | 6 +- gcloud/alpha/sql/instances/create | 2 +- gcloud/alpha/sql/instances/patch | 2 +- gcloud/alpha/workstations/clusters/create | 7 +- gcloud/alpha/workstations/configs/create | 6 +- gcloud/alpha/workstations/configs/update | 6 +- gcloud/artifacts/repositories/list | 34 ++- gcloud/backup-dr/backups/update | 9 - gcloud/beta/ai/endpoints/deploy-model | 8 +- gcloud/beta/alloydb/instances/create | 32 +- .../beta/alloydb/instances/create-secondary | 4 +- gcloud/beta/alloydb/instances/update | 4 +- gcloud/beta/artifacts/repositories/list | 38 +-- gcloud/beta/bigtable/instances/tables/create | 7 + gcloud/beta/bigtable/instances/tables/update | 13 + gcloud/beta/bigtable/tables/create | 7 + gcloud/beta/bigtable/tables/update | 13 + .../composer/environments/storage/dags/delete | 2 +- .../composer/environments/storage/dags/list | 2 +- .../composer/environments/storage/data/delete | 2 +- .../composer/environments/storage/data/list | 2 +- .../environments/storage/plugins/delete | 2 +- .../environments/storage/plugins/list | 2 +- .../beta/compute/backend-services/add-backend | 4 +- gcloud/beta/compute/backend-services/create | 4 +- gcloud/beta/compute/backend-services/update | 12 +- .../compute/backend-services/update-backend | 4 +- .../firewall-policies/mirroring-rules/create | 2 +- .../firewall-policies/mirroring-rules/update | 2 +- .../compute/firewall-policies/rules/create | 2 +- .../compute/firewall-policies/rules/update | 2 +- gcloud/beta/compute/firewall-rules/create | 5 + gcloud/beta/compute/forwarding-rules/update | 8 +- .../beta/compute/future-reservations/update | 7 + gcloud/beta/compute/instance-templates/create | 3 + gcloud/beta/compute/networks/create | 6 +- gcloud/beta/compute/networks/subnets/create | 7 +- gcloud/beta/compute/reservations/update | 7 + gcloud/beta/compute/routes/create | 6 +- gcloud/beta/compute/security-policies/create | 2 +- .../compute/security-policies/rules/create | 4 + .../compute/security-policies/rules/update | 4 + .../backup-restore/backup-channels/create | 2 +- .../backup-restore/restore-channels/create | 2 +- gcloud/beta/dataproc/batches/submit/help | 5 + gcloud/beta/dataproc/batches/submit/pyspark | 11 +- gcloud/beta/dataproc/batches/submit/spark | 5 + gcloud/beta/dataproc/batches/submit/spark-r | 5 + gcloud/beta/dataproc/batches/submit/spark-sql | 5 + gcloud/beta/dataproc/clusters/create | 22 +- gcloud/beta/dataproc/clusters/update | 33 ++- gcloud/beta/dataproc/sessions/create/help | 10 +- gcloud/beta/dataproc/sessions/create/spark | 10 +- gcloud/beta/deploy/job-runs/terminate | 6 +- gcloud/beta/deploy/releases/create | 4 + gcloud/beta/deploy/releases/promote | 8 +- gcloud/beta/deploy/rollouts/advance | 6 +- gcloud/beta/deploy/rollouts/approve | 7 +- gcloud/beta/deploy/rollouts/cancel | 7 +- gcloud/beta/deploy/rollouts/ignore-job | 7 +- gcloud/beta/deploy/rollouts/reject | 7 +- gcloud/beta/deploy/rollouts/retry-job | 7 +- gcloud/beta/deploy/targets/redeploy | 7 +- gcloud/beta/deploy/targets/rollback | 8 +- .../iam/workforce-pools/providers/create-oidc | 24 +- .../iam/workforce-pools/providers/update-oidc | 26 +- gcloud/beta/managed-kafka/acls/add-acl-entry | 4 +- .../beta/managed-kafka/acls/remove-acl-entry | 4 +- gcloud/beta/managed-kafka/clusters/create | 14 +- gcloud/beta/managed-kafka/clusters/update | 16 +- .../beta/managed-kafka/consumer-groups/update | 2 +- gcloud/beta/monitoring/snoozes/create | 21 +- .../beta/netapp/volumes/replications/create | 4 +- gcloud/beta/network-connectivity/hubs/update | 7 +- .../intercept-deployment-groups/create | 6 +- .../intercept-deployment-groups/delete | 6 +- .../intercept-deployment-groups/describe | 6 +- .../intercept-deployment-groups/help | 6 +- .../intercept-deployment-groups/list | 6 +- .../intercept-deployment-groups/update | 6 +- .../intercept-deployments/create | 6 +- .../intercept-deployments/delete | 6 +- .../intercept-deployments/describe | 6 +- .../intercept-deployments/help | 6 +- .../intercept-deployments/list | 6 +- .../intercept-deployments/update | 6 +- .../create | 7 +- .../delete | 7 +- .../describe | 7 +- .../help | 6 +- .../list | 6 +- .../update | 7 +- .../intercept-endpoint-groups/create | 6 +- .../intercept-endpoint-groups/delete | 6 +- .../intercept-endpoint-groups/describe | 6 +- .../intercept-endpoint-groups/help | 6 +- .../intercept-endpoint-groups/list | 6 +- .../intercept-endpoint-groups/update | 6 +- .../security-profile-groups/create | 277 +++++++++--------- .../security-profile-groups/update | 6 +- .../security-profiles/custom-intercept/create | 6 +- .../security-profiles/custom-intercept/delete | 6 +- .../custom-intercept/describe | 6 +- .../security-profiles/custom-intercept/help | 6 +- .../security-profiles/custom-intercept/list | 6 +- .../security-profiles/custom-intercept/update | 6 +- .../service-lb-policies/create | 28 ++ .../service-lb-policies/update | 28 ++ gcloud/beta/scc/findings/create | 13 +- gcloud/beta/scc/findings/group | 13 +- gcloud/beta/scc/findings/list | 13 +- gcloud/beta/scc/findings/list-marks | 13 +- gcloud/beta/scc/findings/update | 13 +- gcloud/beta/scc/findings/update-marks | 13 +- .../beta/spanner/instance-partitions/delete | 6 +- .../beta/spanner/instance-partitions/describe | 12 +- gcloud/beta/spanner/instance-partitions/help | 12 +- gcloud/beta/spanner/instance-partitions/list | 16 +- .../beta/spanner/instance-partitions/update | 18 +- gcloud/beta/spanner/instances/move | 2 +- gcloud/beta/spanner/operations/cancel | 5 +- gcloud/beta/spanner/operations/list | 6 +- gcloud/beta/sql/instances/create | 2 +- gcloud/beta/sql/instances/patch | 2 +- gcloud/beta/workstations/clusters/create | 7 +- gcloud/beta/workstations/configs/create | 6 +- gcloud/beta/workstations/configs/update | 6 +- .../composer/environments/storage/dags/delete | 2 +- .../composer/environments/storage/dags/list | 2 +- .../composer/environments/storage/data/delete | 2 +- .../composer/environments/storage/data/list | 2 +- .../environments/storage/plugins/delete | 2 +- .../environments/storage/plugins/list | 2 +- gcloud/compute/backend-services/add-backend | 4 +- gcloud/compute/backend-services/create | 4 +- gcloud/compute/backend-services/update | 40 ++- .../compute/backend-services/update-backend | 4 +- gcloud/compute/firewall-policies/rules/create | 2 +- gcloud/compute/firewall-policies/rules/update | 2 +- gcloud/compute/forwarding-rules/update | 40 ++- gcloud/dataplex/encryption-config/create | 69 +++++ gcloud/dataplex/encryption-config/describe | 67 +++++ gcloud/dataplex/encryption-config/help | 28 ++ .../glossaries/add-iam-policy-binding | 87 ++++++ gcloud/dataplex/glossaries/categories/create | 100 +++++++ gcloud/dataplex/glossaries/categories/delete | 75 +++++ .../dataplex/glossaries/categories/describe | 76 +++++ gcloud/dataplex/glossaries/categories/help | 38 +++ gcloud/dataplex/glossaries/categories/list | 101 +++++++ gcloud/dataplex/glossaries/categories/update | 104 +++++++ gcloud/dataplex/glossaries/create | 90 ++++++ gcloud/dataplex/glossaries/delete | 72 +++++ gcloud/dataplex/glossaries/describe | 67 +++++ gcloud/dataplex/glossaries/get-iam-policy | 95 ++++++ gcloud/dataplex/glossaries/help | 59 ++++ gcloud/dataplex/glossaries/list | 85 ++++++ .../glossaries/remove-iam-policy-binding | 88 ++++++ gcloud/dataplex/glossaries/set-iam-policy | 71 +++++ gcloud/dataplex/glossaries/terms/create | 101 +++++++ gcloud/dataplex/glossaries/terms/delete | 77 +++++ gcloud/dataplex/glossaries/terms/describe | 77 +++++ gcloud/dataplex/glossaries/terms/help | 39 +++ gcloud/dataplex/glossaries/terms/list | 100 +++++++ gcloud/dataplex/glossaries/terms/update | 104 +++++++ gcloud/dataplex/glossaries/update | 91 ++++++ gcloud/dataplex/help | 6 + gcloud/dataproc/batches/submit/help | 5 + gcloud/dataproc/batches/submit/pyspark | 11 +- gcloud/dataproc/batches/submit/spark | 5 + gcloud/dataproc/batches/submit/spark-r | 5 + gcloud/dataproc/batches/submit/spark-sql | 5 + gcloud/dataproc/clusters/create | 22 +- gcloud/dataproc/clusters/update | 33 ++- gcloud/deploy/job-runs/terminate | 6 +- gcloud/deploy/releases/create | 4 + gcloud/deploy/releases/promote | 8 +- gcloud/deploy/rollouts/advance | 6 +- gcloud/deploy/rollouts/approve | 7 +- gcloud/deploy/rollouts/cancel | 7 +- gcloud/deploy/rollouts/ignore-job | 7 +- gcloud/deploy/rollouts/reject | 7 +- gcloud/deploy/rollouts/retry-job | 7 +- gcloud/deploy/targets/redeploy | 7 +- gcloud/deploy/targets/rollback | 8 +- .../iam/workforce-pools/providers/create-oidc | 24 +- .../iam/workforce-pools/providers/create-saml | 40 ++- .../iam/workforce-pools/providers/update-oidc | 26 +- .../iam/workforce-pools/providers/update-saml | 42 +-- .../providers/create-x509 | 213 ++++++++++++++ .../workload-identity-pools/providers/help | 6 + .../providers/update-x509 | 212 ++++++++++++++ gcloud/managed-kafka/acls/add-acl-entry | 4 +- gcloud/managed-kafka/acls/remove-acl-entry | 4 +- gcloud/managed-kafka/clusters/create | 14 +- gcloud/managed-kafka/clusters/update | 16 +- gcloud/managed-kafka/consumer-groups/update | 2 +- gcloud/monitoring/snoozes/create | 21 +- gcloud/netapp/volumes/replications/create | 4 +- gcloud/network-security/help | 12 + .../intercept-deployment-groups/create | 135 +++++++++ .../intercept-deployment-groups/delete | 89 ++++++ .../intercept-deployment-groups/describe | 75 +++++ .../intercept-deployment-groups/help | 44 +++ .../intercept-deployment-groups/list | 93 ++++++ .../intercept-deployment-groups/update | 136 +++++++++ .../intercept-deployments/create | 200 +++++++++++++ .../intercept-deployments/delete | 81 +++++ .../intercept-deployments/describe | 73 +++++ .../intercept-deployments/help | 42 +++ .../intercept-deployments/list | 93 ++++++ .../intercept-deployments/update | 133 +++++++++ .../create | 170 +++++++++++ .../delete | 90 ++++++ .../describe | 76 +++++ .../help | 42 +++ .../list | 99 +++++++ .../update | 125 ++++++++ .../intercept-endpoint-groups/create | 157 ++++++++++ .../intercept-endpoint-groups/delete | 86 ++++++ .../intercept-endpoint-groups/describe | 72 +++++ .../intercept-endpoint-groups/help | 42 +++ .../intercept-endpoint-groups/list | 101 +++++++ .../intercept-endpoint-groups/update | 135 +++++++++ .../security-profile-groups/create | 233 +++++++++------ .../security-profile-groups/update | 6 +- .../security-profiles/custom-intercept/create | 127 ++++++++ .../security-profiles/custom-intercept/delete | 78 +++++ .../custom-intercept/describe | 73 +++++ .../security-profiles/custom-intercept/help | 42 +++ .../security-profiles/custom-intercept/list | 91 ++++++ .../security-profiles/custom-intercept/update | 119 ++++++++ .../network-security/security-profiles/help | 3 + gcloud/scc/bqexports/create | 13 +- gcloud/scc/bqexports/delete | 13 +- gcloud/scc/bqexports/get | 13 +- gcloud/scc/bqexports/list | 13 +- gcloud/scc/bqexports/update | 13 +- gcloud/scc/findings/bulk-mute | 13 +- gcloud/scc/findings/create | 13 +- gcloud/scc/findings/group | 13 +- gcloud/scc/findings/list | 13 +- gcloud/scc/findings/list-marks | 13 +- gcloud/scc/findings/set-mute | 13 +- gcloud/scc/findings/update | 13 +- gcloud/scc/findings/update-marks | 13 +- gcloud/scc/muteconfigs/create | 13 +- gcloud/scc/muteconfigs/delete | 13 +- gcloud/scc/muteconfigs/get | 13 +- gcloud/scc/muteconfigs/list | 13 +- gcloud/scc/muteconfigs/update | 13 +- gcloud/spanner/instance-partitions/delete | 6 +- gcloud/spanner/instance-partitions/describe | 65 ++++ gcloud/spanner/instance-partitions/help | 14 +- gcloud/spanner/instance-partitions/list | 76 +++++ gcloud/spanner/instance-partitions/update | 92 ++++++ gcloud/spanner/instances/move | 2 +- gcloud/spanner/operations/cancel | 12 +- gcloud/spanner/operations/list | 24 +- gcloud/sql/instances/create | 2 +- gcloud/workstations/clusters/create | 7 +- gcloud/workstations/configs/create | 4 +- gcloud/workstations/configs/update | 4 +- 423 files changed, 11160 insertions(+), 1149 deletions(-) create mode 100644 gcloud/alpha/compute/instant-snapshot-groups/create create mode 100644 gcloud/alpha/compute/instant-snapshot-groups/describe create mode 100644 gcloud/alpha/compute/instant-snapshot-groups/help create mode 100644 gcloud/alpha/compute/interconnects/application-awareness/update create mode 100644 gcloud/alpha/compute/preview-features/describe create mode 100644 gcloud/alpha/compute/preview-features/help create mode 100644 gcloud/alpha/compute/preview-features/list create mode 100644 gcloud/alpha/compute/preview-features/update create mode 100644 gcloud/alpha/dataplex/encryption-config/create create mode 100644 gcloud/alpha/dataplex/encryption-config/describe create mode 100644 gcloud/alpha/dataplex/encryption-config/help create mode 100644 gcloud/alpha/dataplex/glossaries/add-iam-policy-binding create mode 100644 gcloud/alpha/dataplex/glossaries/categories/create create mode 100644 gcloud/alpha/dataplex/glossaries/categories/delete create mode 100644 gcloud/alpha/dataplex/glossaries/categories/describe create mode 100644 gcloud/alpha/dataplex/glossaries/categories/help create mode 100644 gcloud/alpha/dataplex/glossaries/categories/list create mode 100644 gcloud/alpha/dataplex/glossaries/categories/update create mode 100644 gcloud/alpha/dataplex/glossaries/create create mode 100644 gcloud/alpha/dataplex/glossaries/delete create mode 100644 gcloud/alpha/dataplex/glossaries/describe create mode 100644 gcloud/alpha/dataplex/glossaries/get-iam-policy create mode 100644 gcloud/alpha/dataplex/glossaries/help create mode 100644 gcloud/alpha/dataplex/glossaries/list create mode 100644 gcloud/alpha/dataplex/glossaries/remove-iam-policy-binding create mode 100644 gcloud/alpha/dataplex/glossaries/set-iam-policy create mode 100644 gcloud/alpha/dataplex/glossaries/terms/create create mode 100644 gcloud/alpha/dataplex/glossaries/terms/delete create mode 100644 gcloud/alpha/dataplex/glossaries/terms/describe create mode 100644 gcloud/alpha/dataplex/glossaries/terms/help create mode 100644 gcloud/alpha/dataplex/glossaries/terms/list create mode 100644 gcloud/alpha/dataplex/glossaries/terms/update create mode 100644 gcloud/alpha/dataplex/glossaries/update create mode 100644 gcloud/alpha/dataplex/metadata-jobs/cancel create mode 100644 gcloud/alpha/dataplex/metadata-jobs/create create mode 100644 gcloud/alpha/dataplex/metadata-jobs/describe create mode 100644 gcloud/alpha/dataplex/metadata-jobs/help create mode 100644 gcloud/alpha/dataplex/metadata-jobs/list create mode 100644 gcloud/alpha/managed-kafka/schema-registries/create create mode 100644 gcloud/alpha/managed-kafka/schema-registries/delete create mode 100644 gcloud/alpha/managed-kafka/schema-registries/describe create mode 100644 gcloud/alpha/managed-kafka/schema-registries/help create mode 100644 gcloud/alpha/managed-kafka/schema-registries/list create mode 100644 gcloud/dataplex/encryption-config/create create mode 100644 gcloud/dataplex/encryption-config/describe create mode 100644 gcloud/dataplex/encryption-config/help create mode 100644 gcloud/dataplex/glossaries/add-iam-policy-binding create mode 100644 gcloud/dataplex/glossaries/categories/create create mode 100644 gcloud/dataplex/glossaries/categories/delete create mode 100644 gcloud/dataplex/glossaries/categories/describe create mode 100644 gcloud/dataplex/glossaries/categories/help create mode 100644 gcloud/dataplex/glossaries/categories/list create mode 100644 gcloud/dataplex/glossaries/categories/update create mode 100644 gcloud/dataplex/glossaries/create create mode 100644 gcloud/dataplex/glossaries/delete create mode 100644 gcloud/dataplex/glossaries/describe create mode 100644 gcloud/dataplex/glossaries/get-iam-policy create mode 100644 gcloud/dataplex/glossaries/help create mode 100644 gcloud/dataplex/glossaries/list create mode 100644 gcloud/dataplex/glossaries/remove-iam-policy-binding create mode 100644 gcloud/dataplex/glossaries/set-iam-policy create mode 100644 gcloud/dataplex/glossaries/terms/create create mode 100644 gcloud/dataplex/glossaries/terms/delete create mode 100644 gcloud/dataplex/glossaries/terms/describe create mode 100644 gcloud/dataplex/glossaries/terms/help create mode 100644 gcloud/dataplex/glossaries/terms/list create mode 100644 gcloud/dataplex/glossaries/terms/update create mode 100644 gcloud/dataplex/glossaries/update create mode 100644 gcloud/iam/workload-identity-pools/providers/create-x509 create mode 100644 gcloud/iam/workload-identity-pools/providers/update-x509 create mode 100644 gcloud/network-security/intercept-deployment-groups/create create mode 100644 gcloud/network-security/intercept-deployment-groups/delete create mode 100644 gcloud/network-security/intercept-deployment-groups/describe create mode 100644 gcloud/network-security/intercept-deployment-groups/help create mode 100644 gcloud/network-security/intercept-deployment-groups/list create mode 100644 gcloud/network-security/intercept-deployment-groups/update create mode 100644 gcloud/network-security/intercept-deployments/create create mode 100644 gcloud/network-security/intercept-deployments/delete create mode 100644 gcloud/network-security/intercept-deployments/describe create mode 100644 gcloud/network-security/intercept-deployments/help create mode 100644 gcloud/network-security/intercept-deployments/list create mode 100644 gcloud/network-security/intercept-deployments/update create mode 100644 gcloud/network-security/intercept-endpoint-group-associations/create create mode 100644 gcloud/network-security/intercept-endpoint-group-associations/delete create mode 100644 gcloud/network-security/intercept-endpoint-group-associations/describe create mode 100644 gcloud/network-security/intercept-endpoint-group-associations/help create mode 100644 gcloud/network-security/intercept-endpoint-group-associations/list create mode 100644 gcloud/network-security/intercept-endpoint-group-associations/update create mode 100644 gcloud/network-security/intercept-endpoint-groups/create create mode 100644 gcloud/network-security/intercept-endpoint-groups/delete create mode 100644 gcloud/network-security/intercept-endpoint-groups/describe create mode 100644 gcloud/network-security/intercept-endpoint-groups/help create mode 100644 gcloud/network-security/intercept-endpoint-groups/list create mode 100644 gcloud/network-security/intercept-endpoint-groups/update create mode 100644 gcloud/network-security/security-profiles/custom-intercept/create create mode 100644 gcloud/network-security/security-profiles/custom-intercept/delete create mode 100644 gcloud/network-security/security-profiles/custom-intercept/describe create mode 100644 gcloud/network-security/security-profiles/custom-intercept/help create mode 100644 gcloud/network-security/security-profiles/custom-intercept/list create mode 100644 gcloud/network-security/security-profiles/custom-intercept/update create mode 100644 gcloud/spanner/instance-partitions/describe create mode 100644 gcloud/spanner/instance-partitions/list create mode 100644 gcloud/spanner/instance-partitions/update diff --git a/gcloud/_version b/gcloud/_version index d0feca977..e3399c7f4 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 521.0.0 -alpha 2025.05.02 -beta 2025.05.02 +Google Cloud SDK 522.0.0 +alpha 2025.05.09 +beta 2025.05.09 bq 2.1.16 bundled-python3-unix 3.12.9 -core 2025.05.02 +core 2025.05.09 gcloud-crc32c 1.0.0 gsutil 5.34 diff --git a/gcloud/alloydb/instances/create b/gcloud/alloydb/instances/create index 27c437e8e..0a49b2a37 100644 --- a/gcloud/alloydb/instances/create +++ b/gcloud/alloydb/instances/create @@ -4,11 +4,11 @@ NAME SYNOPSIS gcloud alloydb instances create INSTANCE --cluster=CLUSTER - --cpu-count=CPU_COUNT --instance-type=INSTANCE_TYPE --region=REGION + --instance-type=INSTANCE_TYPE --region=REGION [--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]] [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async] [--authorized-external-networks=[AUTHORIZED_NETWORK,...]] - [--availability-type=AVAILABILITY_TYPE] + [--availability-type=AVAILABILITY_TYPE] [--cpu-count=CPU_COUNT] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] @@ -44,18 +44,6 @@ REQUIRED FLAGS --cluster=CLUSTER AlloyDB cluster ID - --cpu-count=CPU_COUNT - Whole number value indicating how many vCPUs the machine should - contain. If the instance does not have a machine-type, the vCPU count - will be used to determine the machine type where each vCPU corresponds - to an N2 high-mem machine: - (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machine_types). - where CPU_COUNT can be one of: 2, 4, 8, 16, 32, 64, 96, 128. If the - instance has a machine-type, cpu-count must have the same value as the - vCPU count in the machine-type. Eg: if machine-type is - c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, - 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. - --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: @@ -111,6 +99,18 @@ OPTIONAL FLAGS production instances; instance does not automatically fail over to another zone. + --cpu-count=CPU_COUNT + Whole number value indicating how many vCPUs the machine should + contain. If the instance does not have a machine-type, the vCPU count + will be used to determine the machine type where each vCPU corresponds + to an N2 high-mem machine: + (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machine_types). + where CPU_COUNT can be one of: 2, 4, 8, 16, 32, 64, 96, 128. If the + instance has a machine-type, cpu-count must have the same value as the + vCPU count in the machine-type. Eg: if machine-type is + c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, + 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. + --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an equals sign to separate flag name and value. Flags without values, like @@ -162,10 +162,10 @@ OPTIONAL FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project - Required, Sets project value. + Required, sets project value. Shorthand Example: diff --git a/gcloud/alloydb/instances/create-secondary b/gcloud/alloydb/instances/create-secondary index cf96b05ea..00bd0b76a 100644 --- a/gcloud/alloydb/instances/create-secondary +++ b/gcloud/alloydb/instances/create-secondary @@ -97,10 +97,10 @@ OPTIONAL FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project - Required, Sets project value. + Required, sets project value. Shorthand Example: diff --git a/gcloud/alloydb/instances/update b/gcloud/alloydb/instances/update index e2a99efed..4983ac589 100644 --- a/gcloud/alloydb/instances/update +++ b/gcloud/alloydb/instances/update @@ -181,10 +181,10 @@ OPTIONAL FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project - Required, Sets project value. + Required, sets project value. Shorthand Example: diff --git a/gcloud/alpha/ai/endpoints/deploy-model b/gcloud/alpha/ai/endpoints/deploy-model index 695fbcfa8..f463ee120 100644 --- a/gcloud/alpha/ai/endpoints/deploy-model +++ b/gcloud/alpha/ai/endpoints/deploy-model @@ -77,10 +77,10 @@ OPTIONAL FLAGS type The type of the accelerator. Choices are 'nvidia-a100-80gb', - 'nvidia-h100-80gb', 'nvidia-h100-mega-80gb', 'nvidia-h200-141gb', - 'nvidia-l4', 'nvidia-tesla-a100', 'nvidia-tesla-k80', - 'nvidia-tesla-p100', 'nvidia-tesla-p4', 'nvidia-tesla-t4', - 'nvidia-tesla-v100'. + 'nvidia-b200', 'nvidia-h100-80gb', 'nvidia-h100-mega-80gb', + 'nvidia-h200-141gb', 'nvidia-l4', 'nvidia-tesla-a100', + 'nvidia-tesla-k80', 'nvidia-tesla-p100', 'nvidia-tesla-p4', + 'nvidia-tesla-t4', 'nvidia-tesla-v100'. count The number of accelerators to attach to each machine running the diff --git a/gcloud/alpha/alloydb/instances/create b/gcloud/alpha/alloydb/instances/create index cff9bbbf4..f675e7628 100644 --- a/gcloud/alpha/alloydb/instances/create +++ b/gcloud/alpha/alloydb/instances/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha alloydb instances create INSTANCE --cluster=CLUSTER - --cpu-count=CPU_COUNT --instance-type=INSTANCE_TYPE --region=REGION + --instance-type=INSTANCE_TYPE --region=REGION [--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]] [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async] [--authorized-external-networks=[AUTHORIZED_NETWORK,...]] @@ -18,7 +18,7 @@ SYNOPSIS [--connection-pooling-query-wait-timeout=CONNECTION_POOLING_QUERY_WAIT_TIMEOUT] [--connection-pooling-server-idle-timeout=CONNECTION_POOLING_SERVER_IDLE_TIMEOUT] [--connection-pooling-stats-users=[STATS_USERS,...]] - [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] + [--cpu-count=CPU_COUNT] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--[no-]enable-connection-pooling] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] @@ -61,18 +61,6 @@ REQUIRED FLAGS --cluster=CLUSTER AlloyDB cluster ID - --cpu-count=CPU_COUNT - Whole number value indicating how many vCPUs the machine should - contain. If the instance does not have a machine-type, the vCPU count - will be used to determine the machine type where each vCPU corresponds - to an N2 high-mem machine: - (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machine_types). - where CPU_COUNT can be one of: 2, 4, 8, 16, 32, 64, 96, 128. If the - instance has a machine-type, cpu-count must have the same value as the - vCPU count in the machine-type. Eg: if machine-type is - c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, - 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. - --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: @@ -160,6 +148,18 @@ OPTIONAL FLAGS Comma-separated list of database users to access connection pooling stats. + --cpu-count=CPU_COUNT + Whole number value indicating how many vCPUs the machine should + contain. If the instance does not have a machine-type, the vCPU count + will be used to determine the machine type where each vCPU corresponds + to an N2 high-mem machine: + (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machine_types). + where CPU_COUNT can be one of: 2, 4, 8, 16, 32, 64, 96, 128. If the + instance has a machine-type, cpu-count must have the same value as the + vCPU count in the machine-type. Eg: if machine-type is + c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, + 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. + --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an equals sign to separate flag name and value. Flags without values, like @@ -251,10 +251,10 @@ OPTIONAL FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project - Required, Sets project value. + Required, sets project value. Shorthand Example: diff --git a/gcloud/alpha/alloydb/instances/create-secondary b/gcloud/alpha/alloydb/instances/create-secondary index 4ac454017..9e3edf6ab 100644 --- a/gcloud/alpha/alloydb/instances/create-secondary +++ b/gcloud/alpha/alloydb/instances/create-secondary @@ -97,10 +97,10 @@ OPTIONAL FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project - Required, Sets project value. + Required, sets project value. Shorthand Example: diff --git a/gcloud/alpha/alloydb/instances/update b/gcloud/alpha/alloydb/instances/update index 1608643c4..76ea3b957 100644 --- a/gcloud/alpha/alloydb/instances/update +++ b/gcloud/alpha/alloydb/instances/update @@ -285,10 +285,10 @@ OPTIONAL FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project - Required, Sets project value. + Required, sets project value. Shorthand Example: diff --git a/gcloud/alpha/artifacts/repositories/list b/gcloud/alpha/artifacts/repositories/list index aa72e2aeb..cf613c293 100644 --- a/gcloud/alpha/artifacts/repositories/list +++ b/gcloud/alpha/artifacts/repositories/list @@ -18,54 +18,58 @@ EXAMPLES $ gcloud alpha artifacts repositories list --limit=5 - To list repositories with name as `my_repo`: + To list repositories with name as my_repo: $ gcloud alpha artifacts repositories list \ - --filter='name="projects/my-project/locations/us/repositories/my\ + --filter='name="projects/my-project/locations/us/repositories/my\ _repo"' - To list repositories with a given partial name, use `*` to match any character in name: + To list repositories with a given partial name, use * to match any + character in name: $ gcloud alpha artifacts repositories list \ - --filter='name="projects/my-project/locations/us/repositories/*r\ + --filter='name="projects/my-project/locations/us/repositories/*r\ epo"' $ gcloud alpha artifacts repositories list \ - --filter='name="projects/my-project/locations/us/repositories/my\ + --filter='name="projects/my-project/locations/us/repositories/my\ _*"' - To list files that have annotations: + To list files that have annotations: $ gcloud alpha artifacts repositories list --filter=annotations:* - To list repositories with annotations pair as [annotation_key: annotation_value] + To list repositories with annotations pair as [annotation_key: + annotation_value] $ gcloud alpha artifacts repositories list \ - --filter='annotations.annotation_key:annotation_value' + --filter='annotations.annotation_key:annotation_value' - To list repositories with annotations containing key as `my_key`: + To list repositories with annotations containing key as my_key: $ gcloud alpha artifacts repositories list \ - --filter='annotations.my_key' + --filter='annotations.my_key' - If the key or value contains special characters, such as `my.key` or `my.value`, backtick("`") is required: + If the key or value contains special characters, such as my.key or + my.value, backtick("") is required: $ gcloud alpha artifacts repositories list \ - --filter='annotations.`my.key`' + --filter='annotations.`my.key`' $ gcloud alpha artifacts repositories list \ - --filter='annotations.`my.key`:`my.value`' + --filter='annotations.`my.key`:`my.value`' - To list repositories with given partial annotation key or value, use `*` to match any character: + To list repositories with given partial annotation key or value, use * to + match any character: $ gcloud alpha artifacts repositories list \ - --filter='annotations.*key:`*.value`' + --filter='annotations.*key:`*.value`' - To list repositories ordered by create_time: + To list repositories ordered by create_time: $ gcloud alpha artifacts repositories list --sort-by=create_time - To list repositories ordered by update_time reversely: + To list repositories ordered by update_time reversely: $ gcloud alpha artifacts repositories list--sort-by=~update_time diff --git a/gcloud/alpha/backup-dr/backups/update b/gcloud/alpha/backup-dr/backups/update index 505579bba..907155597 100644 --- a/gcloud/alpha/backup-dr/backups/update +++ b/gcloud/alpha/backup-dr/backups/update @@ -21,15 +21,6 @@ EXAMPLES --project=sample-project --location=us-central1 \ --enforced-retention-end-time="2025-02-14T01:10:20Z" - To update the expire time of a backup sample-backup in backup vault - sample-vault, data source sample-ds, project sample-project and location - us-central1, run: - - $ gcloud alpha backup-dr backups update sample-backup \ - --backup-vault=sample-vault --data-source=sample-ds \ - --project=sample-project --location=us-central1 \ - --expire-time="2025-02-14T01:10:20Z" - POSITIONAL ARGUMENTS Backup resource - Name of the backup to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some diff --git a/gcloud/alpha/bigtable/instances/tables/create b/gcloud/alpha/bigtable/instances/tables/create index b7e818be6..c4f1614f2 100644 --- a/gcloud/alpha/bigtable/instances/tables/create +++ b/gcloud/alpha/bigtable/instances/tables/create @@ -9,6 +9,7 @@ SYNOPSIS [--deletion-protection] [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] + [--tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] @@ -159,6 +160,12 @@ OPTIONAL FLAGS Row keys where the table should initially be split. For example: car,key + --tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN + The age at which data should be moved to infrequent access storage. + + See $ gcloud topic datetimes for information on absolute duration + formats. + At most one of these can be specified: --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD diff --git a/gcloud/alpha/bigtable/instances/tables/update b/gcloud/alpha/bigtable/instances/tables/update index 618ce97e8..d13e8b17a 100644 --- a/gcloud/alpha/bigtable/instances/tables/update +++ b/gcloud/alpha/bigtable/instances/tables/update @@ -11,6 +11,8 @@ SYNOPSIS | --clear-change-stream-retention-period] [--clear-row-key-schema | --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [--clear-tiered-storage-config + | --tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -162,6 +164,17 @@ FLAGS encoding: raw: {} + At most one of these can be specified: + + --clear-tiered-storage-config + Disables the tiered storage config. + + --tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN + The age at which data should be moved to infrequent access storage. + + See $ gcloud topic datetimes for information on absolute duration + formats. + 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/bigtable/tables/create b/gcloud/alpha/bigtable/tables/create index 689627864..a8403b9f9 100644 --- a/gcloud/alpha/bigtable/tables/create +++ b/gcloud/alpha/bigtable/tables/create @@ -8,6 +8,7 @@ SYNOPSIS [--deletion-protection] [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] + [--tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] @@ -158,6 +159,12 @@ OPTIONAL FLAGS Row keys where the table should initially be split. For example: car,key + --tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN + The age at which data should be moved to infrequent access storage. + + See $ gcloud topic datetimes for information on absolute duration + formats. + At most one of these can be specified: --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD diff --git a/gcloud/alpha/bigtable/tables/update b/gcloud/alpha/bigtable/tables/update index 0243c7e2b..22e3a408d 100644 --- a/gcloud/alpha/bigtable/tables/update +++ b/gcloud/alpha/bigtable/tables/update @@ -11,6 +11,8 @@ SYNOPSIS | --clear-change-stream-retention-period] [--clear-row-key-schema | --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [--clear-tiered-storage-config + | --tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -162,6 +164,17 @@ FLAGS encoding: raw: {} + At most one of these can be specified: + + --clear-tiered-storage-config + Disables the tiered storage config. + + --tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN + The age at which data should be moved to infrequent access storage. + + See $ gcloud topic datetimes for information on absolute duration + formats. + 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/composer/environments/storage/dags/delete b/gcloud/alpha/composer/environments/storage/dags/delete index a58dd14da..ae705f8c9 100644 --- a/gcloud/alpha/composer/environments/storage/dags/delete +++ b/gcloud/alpha/composer/environments/storage/dags/delete @@ -13,7 +13,7 @@ DESCRIPTION EXAMPLES To delete the dags in the path path/to/dags, for the environment named - environmnet-1 in the location us-east1, run: + environment-1 in the location us-east1, run: $ gcloud alpha composer environments storage dags delete \ path/to/dags --environment=environment-1 --location=us-east1 diff --git a/gcloud/alpha/composer/environments/storage/dags/list b/gcloud/alpha/composer/environments/storage/dags/list index 011227f1b..6e5717b86 100644 --- a/gcloud/alpha/composer/environments/storage/dags/list +++ b/gcloud/alpha/composer/environments/storage/dags/list @@ -11,7 +11,7 @@ DESCRIPTION (ALPHA) List the DAG files for a Cloud Composer environment. EXAMPLES - To list the dags for the Cloud Composer environment environmnet-1 and + To list the dags for the Cloud Composer environment environment-1 and location us-central1, run: $ gcloud alpha composer environments storage dags list \ diff --git a/gcloud/alpha/composer/environments/storage/data/delete b/gcloud/alpha/composer/environments/storage/data/delete index fbda54771..f6934375c 100644 --- a/gcloud/alpha/composer/environments/storage/data/delete +++ b/gcloud/alpha/composer/environments/storage/data/delete @@ -13,7 +13,7 @@ DESCRIPTION EXAMPLES To delete the data from the path path/to/data, for the environment named - environmnet-1 in the location us-east1, run: + environment-1 in the location us-east1, run: $ gcloud alpha composer environments storage data delete \ path/to/data --environment=environment-1 --location=us-east1 diff --git a/gcloud/alpha/composer/environments/storage/data/list b/gcloud/alpha/composer/environments/storage/data/list index 3f6f90fae..d25849308 100644 --- a/gcloud/alpha/composer/environments/storage/data/list +++ b/gcloud/alpha/composer/environments/storage/data/list @@ -11,7 +11,7 @@ DESCRIPTION (ALPHA) List the data for a Cloud Composer environment. EXAMPLES - To list the data from the Cloud Composer environment environmnet-1 and + To list the data from the Cloud Composer environment environment-1 and location us-central1, run: $ gcloud alpha composer environments storage data list \ diff --git a/gcloud/alpha/composer/environments/storage/plugins/delete b/gcloud/alpha/composer/environments/storage/plugins/delete index 8a299096d..4cf272ea2 100644 --- a/gcloud/alpha/composer/environments/storage/plugins/delete +++ b/gcloud/alpha/composer/environments/storage/plugins/delete @@ -13,7 +13,7 @@ DESCRIPTION EXAMPLES To delete the plugins in the path path/to/plugins, for the environment - named environmnet-1 in the location us-east1, run: + named environment-1 in the location us-east1, run: $ gcloud alpha composer environments storage plugins delete \ path/to/plugins --environment=environment-1 --location=us-east1 diff --git a/gcloud/alpha/composer/environments/storage/plugins/list b/gcloud/alpha/composer/environments/storage/plugins/list index d1111eb34..e971dd55e 100644 --- a/gcloud/alpha/composer/environments/storage/plugins/list +++ b/gcloud/alpha/composer/environments/storage/plugins/list @@ -11,7 +11,7 @@ DESCRIPTION (ALPHA) List the plugins for a Cloud Composer environment. EXAMPLES - To list the plugins for the Cloud Composer environment environmnet-1 and + To list the plugins for the Cloud Composer environment environment-1 and location us-central1, run: $ gcloud alpha composer environments storage plugins list \ diff --git a/gcloud/alpha/compute/backend-services/add-backend b/gcloud/alpha/compute/backend-services/add-backend index c29416f87..dfea4026a 100644 --- a/gcloud/alpha/compute/backend-services/add-backend +++ b/gcloud/alpha/compute/backend-services/add-backend @@ -283,7 +283,7 @@ OPTIONAL FLAGS Sets maxUtilization value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -316,7 +316,7 @@ OPTIONAL FLAGS Sets maxUtilization value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: diff --git a/gcloud/alpha/compute/backend-services/create b/gcloud/alpha/compute/backend-services/create index 85ee07b75..c1f151782 100644 --- a/gcloud/alpha/compute/backend-services/create +++ b/gcloud/alpha/compute/backend-services/create @@ -838,7 +838,7 @@ FLAGS Sets dryRun value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -867,7 +867,7 @@ FLAGS Sets dryRun value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: diff --git a/gcloud/alpha/compute/backend-services/update b/gcloud/alpha/compute/backend-services/update index 68f3d489e..6c8449b64 100644 --- a/gcloud/alpha/compute/backend-services/update +++ b/gcloud/alpha/compute/backend-services/update @@ -315,7 +315,7 @@ FLAGS Enables Dynamic Forwarding in IpPort selection mode. --load-balancing-scheme=LOAD_BALANCING_SCHEME - Only for the Global external ALB migration. + Only for the Global external Application Load Balancer migration. The value of this field must be EXTERNAL or EXTERNAL_MANAGED. @@ -674,7 +674,7 @@ FLAGS Sets dryRun value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -703,7 +703,7 @@ FLAGS Sets dryRun value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -723,15 +723,15 @@ FLAGS Clears current state of external managed migration. --external-managed-migration-state=EXTERNAL_MANAGED_MIGRATION_STATE - Specifies the canary migration state. Possible values are PREPARE, + Specifies the migration state. Possible values are PREPARE, TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state must be changed to PREPARE. The state must be changed to TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be - used to migrate traffic by percentage using - externalManagedMigrationTestingPercentage. + used to migrate traffic by percentage using the + --external-managed-migration-testing-percentage flag. EXTERNAL_MANAGED_MIGRATION_STATE must be one of: PREPARE, TEST_BY_PERCENTAGE, TEST_ALL_TRAFFIC. diff --git a/gcloud/alpha/compute/backend-services/update-backend b/gcloud/alpha/compute/backend-services/update-backend index 396a88d30..136d59b30 100644 --- a/gcloud/alpha/compute/backend-services/update-backend +++ b/gcloud/alpha/compute/backend-services/update-backend @@ -255,7 +255,7 @@ OPTIONAL FLAGS Sets maxUtilization value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -288,7 +288,7 @@ OPTIONAL FLAGS Sets maxUtilization value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: diff --git a/gcloud/alpha/compute/firewall-policies/mirroring-rules/create b/gcloud/alpha/compute/firewall-policies/mirroring-rules/create index 642ab2a11..3b03de404 100644 --- a/gcloud/alpha/compute/firewall-policies/mirroring-rules/create +++ b/gcloud/alpha/compute/firewall-policies/mirroring-rules/create @@ -68,7 +68,7 @@ OPTIONAL FLAGS http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ - c) . In case "c" gCloud CLI will create a reference matching + c) . In case "c" gcloud CLI will create a reference matching format "a", but to make it work CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSECURITY property must be set. In order to set this property, please run the command gcloud config set diff --git a/gcloud/alpha/compute/firewall-policies/mirroring-rules/update b/gcloud/alpha/compute/firewall-policies/mirroring-rules/update index 81336103b..0bcbd840f 100644 --- a/gcloud/alpha/compute/firewall-policies/mirroring-rules/update +++ b/gcloud/alpha/compute/firewall-policies/mirroring-rules/update @@ -71,7 +71,7 @@ OPTIONAL FLAGS http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ - c) . In case "c" gCloud CLI will create a reference matching + c) . In case "c" gcloud CLI will create a reference matching format "a", but to make it work CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSECURITY property must be set. In order to set this property, please run the command gcloud config set diff --git a/gcloud/alpha/compute/firewall-policies/rules/create b/gcloud/alpha/compute/firewall-policies/rules/create index b45b385c2..e6a49d351 100644 --- a/gcloud/alpha/compute/firewall-policies/rules/create +++ b/gcloud/alpha/compute/firewall-policies/rules/create @@ -110,7 +110,7 @@ OPTIONAL FLAGS http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ - c) . In case "c" gCloud CLI will create a reference matching + c) . In case "c" gcloud CLI will create a reference matching format "a", but to make it work CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSECURITY property must be set. In order to set this property, please run the command gcloud config set diff --git a/gcloud/alpha/compute/firewall-policies/rules/update b/gcloud/alpha/compute/firewall-policies/rules/update index 32d05f0e9..18febb42c 100644 --- a/gcloud/alpha/compute/firewall-policies/rules/update +++ b/gcloud/alpha/compute/firewall-policies/rules/update @@ -115,7 +115,7 @@ OPTIONAL FLAGS http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ - c) . In case "c" gCloud CLI will create a reference matching + c) . In case "c" gcloud CLI will create a reference matching format "a", but to make it work CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSECURITY property must be set. In order to set this property, please run the command gcloud config set diff --git a/gcloud/alpha/compute/firewall-rules/create b/gcloud/alpha/compute/firewall-rules/create index 68461b515..6f8d35ec1 100644 --- a/gcloud/alpha/compute/firewall-rules/create +++ b/gcloud/alpha/compute/firewall-rules/create @@ -10,6 +10,7 @@ SYNOPSIS [--direction=DIRECTION] [--disabled] [--[no-]enable-logging] [--logging-metadata=LOGGING_METADATA] [--network=NETWORK; default="default"] [--priority=PRIORITY] + [--resource-manager-tags=[KEY=VALUE,...]] [--rules=PROTOCOL[:PORT[-PORT]],[...]] [--source-ranges=CIDR_RANGE,[CIDR_RANGE,...]] [--source-service-accounts=EMAIL,[EMAIL,...]] @@ -150,6 +151,10 @@ OPTIONAL FLAGS precedence. DENY rules take precedence over ALLOW rules having equal priority. + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the + firewall. + --rules=PROTOCOL[:PORT[-PORT]],[...] A list of protocols and ports to which the firewall rule will apply. diff --git a/gcloud/alpha/compute/forwarding-rules/update b/gcloud/alpha/compute/forwarding-rules/update index f176995b8..7f4b53390 100644 --- a/gcloud/alpha/compute/forwarding-rules/update +++ b/gcloud/alpha/compute/forwarding-rules/update @@ -65,7 +65,7 @@ FLAGS The value of this field must be in the range [0, 100]. --load-balancing-scheme=LOAD_BALANCING_SCHEME - Only for the Global external ALB migration. + Only for the Global external Application Load Balancer migration. The value of this field must be EXTERNAL or EXTERNAL_MANAGED. @@ -95,7 +95,7 @@ FLAGS Clears current state of external managed migration. --external-managed-backend-bucket-migration-state=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_STATE - Specifies the canary migration state. Possible values are PREPARE, + Specifies the migration state. Possible values are PREPARE, TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state @@ -103,8 +103,8 @@ FLAGS TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate traffic to backend buckets attached to this - forwarding rule by percentage using - externalManagedBackendBucketMigrationTestingPercentage. + forwarding rule by percentage using the + --external-managed-backend-bucket-migration-testing-percentage flag. EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_STATE must be one of: PREPARE, TEST_BY_PERCENTAGE, TEST_ALL_TRAFFIC. diff --git a/gcloud/alpha/compute/help b/gcloud/alpha/compute/help index e196e5afe..2afbca548 100644 --- a/gcloud/alpha/compute/help +++ b/gcloud/alpha/compute/help @@ -94,6 +94,9 @@ GROUPS instances (ALPHA) Read and manipulate Compute Engine virtual machine instances. + instant-snapshot-groups + (ALPHA) Create, list and delete Compute Engine instant snapshot groups. + instant-snapshots (ALPHA) Create, list and delete Compute Engine instant snapshots. @@ -139,6 +142,9 @@ GROUPS packet-mirrorings (ALPHA) Manage Compute Engine packet mirroring resources. + preview-features + (ALPHA) Read and manipulate Compute Engine Preview Features. + project-info (ALPHA) Read and manipulate project-level data like quotas and metadata. diff --git a/gcloud/alpha/compute/instant-snapshot-groups/create b/gcloud/alpha/compute/instant-snapshot-groups/create new file mode 100644 index 000000000..932d46a85 --- /dev/null +++ b/gcloud/alpha/compute/instant-snapshot-groups/create @@ -0,0 +1,80 @@ +NAME + gcloud alpha compute instant-snapshot-groups create - create a Compute + Engine instant snapshot group + +SYNOPSIS + gcloud alpha compute instant-snapshot-groups create + INSTANT_SNAPSHOT_GROUP_NAME + --source-consistency-group=SOURCE_CONSISTENCY_GROUP + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Compute Engine instant snapshot group. + +POSITIONAL ARGUMENTS + INSTANT_SNAPSHOT_GROUP_NAME + Name of the instant snapshot group to create. + +REQUIRED FLAGS + --source-consistency-group=SOURCE_CONSISTENCY_GROUP + URL of the source consistency group resource policy. The resource + policy is always in the same region as the source disks. + +OPTIONAL FLAGS + At most one of these can be specified: + + --region=REGION + Region of the instant snapshot group 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. + + --zone=ZONE + Zone of the instant snapshot group to create. 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/describe b/gcloud/alpha/compute/instant-snapshot-groups/describe new file mode 100644 index 000000000..9e855d87a --- /dev/null +++ b/gcloud/alpha/compute/instant-snapshot-groups/describe @@ -0,0 +1,74 @@ +NAME + gcloud alpha compute instant-snapshot-groups describe - describe a Compute + Engine instant snapshot group + +SYNOPSIS + gcloud alpha compute instant-snapshot-groups describe + INSTANT_SNAPSHOT_GROUP_NAME [--region=REGION | --zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Compute Engine instant snapshot group. + +POSITIONAL ARGUMENTS + INSTANT_SNAPSHOT_GROUP_NAME + Name of the instant snapshot group to describe. + +FLAGS + At most one of these can be specified: + + --region=REGION + Region of the instant snapshot group 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. + + --zone=ZONE + Zone of the instant snapshot group to describe. If not specified and + the compute/zone property isn't set, you might be prompted to select + a zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/instant-snapshot-groups/help b/gcloud/alpha/compute/instant-snapshot-groups/help new file mode 100644 index 000000000..176e91d19 --- /dev/null +++ b/gcloud/alpha/compute/instant-snapshot-groups/help @@ -0,0 +1,30 @@ +NAME + gcloud alpha compute instant-snapshot-groups - create, list and delete + Compute Engine instant snapshot groups + +SYNOPSIS + gcloud alpha compute instant-snapshot-groups COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create, list and delete Compute Engine instant 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 instant snapshot group. + + describe + (ALPHA) Describe a Compute Engine instant snapshot group. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/application-awareness/help b/gcloud/alpha/compute/interconnects/application-awareness/help index 9c2774bb4..c544d4407 100644 --- a/gcloud/alpha/compute/interconnects/application-awareness/help +++ b/gcloud/alpha/compute/interconnects/application-awareness/help @@ -23,6 +23,10 @@ COMMANDS (ALPHA) Get application awareness configuration of a Compute Engine interconnect. + update + (ALPHA) Updates application awareness configuration of a Compute Engine + interconnect. + 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/interconnects/application-awareness/update b/gcloud/alpha/compute/interconnects/application-awareness/update new file mode 100644 index 000000000..eb7f1864b --- /dev/null +++ b/gcloud/alpha/compute/interconnects/application-awareness/update @@ -0,0 +1,50 @@ +NAME + gcloud alpha compute interconnects application-awareness update - updates + application awareness configuration of a Compute Engine interconnect + +SYNOPSIS + gcloud alpha compute interconnects application-awareness update NAME + [--enabled] [--profile-description=PROFILE_DESCRIPTION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects application-awareness update + allows the user to enable or disable application awareness on Interconnect, + as well as add/update the description of the application awareness on + Interconnect profile. For an example, refer to the EXAMPLES section below. + +EXAMPLES + To update the application awareness config on Compute Engine interconnect + in a project, run: + + $ gcloud alpha compute interconnects application-awareness update \ + example-interconnect application-awareness update --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/networks/create b/gcloud/alpha/compute/networks/create index a27d97199..cb80c0d25 100644 --- a/gcloud/alpha/compute/networks/create +++ b/gcloud/alpha/compute/networks/create @@ -8,7 +8,7 @@ SYNOPSIS [--internal-ipv6-range=INTERNAL_IPV6_RANGE] [--mtu=MTU] [--network-firewall-policy-enforcement-order=NETWORK_FIREWALL_POLICY_ENFORCEMENT_ORDER] [--network-profile=NETWORK_PROFILE] [--range=RANGE] - [--subnet-mode=MODE] + [--resource-manager-tags=[KEY=VALUE,...]] [--subnet-mode=MODE] [--bgp-best-path-selection-mode=BGP_BEST_PATH_SELECTION_MODE --[no-]bgp-bps-always-compare-med --bgp-bps-inter-region-cost=BGP_BPS_INTER_REGION_COST] @@ -91,6 +91,10 @@ FLAGS Cloud Platform features are not supported on legacy networks. Please be advised that legacy networks may not be supported in the future. + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the + network. + --subnet-mode=MODE The subnet mode of the network. If not specified, defaults to AUTO. diff --git a/gcloud/alpha/compute/networks/subnets/create b/gcloud/alpha/compute/networks/subnets/create index ea153fafb..2e2a99df9 100644 --- a/gcloud/alpha/compute/networks/subnets/create +++ b/gcloud/alpha/compute/networks/subnets/create @@ -18,7 +18,8 @@ SYNOPSIS [--logging-metadata-fields=[METADATA_FIELD,...]] [--metadata=METADATA] [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] [--purpose=PURPOSE] [--range=RANGE] [--region=REGION] - [--reserved-internal-range=RESERVED_INTERNAL_RANGE] [--role=ROLE] + [--reserved-internal-range=RESERVED_INTERNAL_RANGE] + [--resource-manager-tags=[KEY=VALUE,...]] [--role=ROLE] [--secondary-range=PROPERTY=VALUE,[...]] [--secondary-range-with-reserved-internal-range=RANGE_NAME=INTERNAL_RANGE_URL, [...]] [--stack-type=STACK_TYPE] [--enable-l2 : --vlan=VLAN] @@ -204,6 +205,10 @@ OPTIONAL FLAGS --reserved-internal-range //networkconnectivity.googleapis.com/projects/PROJECT/locations/global/internalRanges/RANGE + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the + subnetwork. + --role=ROLE The role of subnetwork. This field is required when the purpose is set to GLOBAL_MANAGED_PROXY, REGIONAL_MANAGED_PROXY or diff --git a/gcloud/alpha/compute/preview-features/describe b/gcloud/alpha/compute/preview-features/describe new file mode 100644 index 000000000..5acd45a60 --- /dev/null +++ b/gcloud/alpha/compute/preview-features/describe @@ -0,0 +1,54 @@ +NAME + gcloud alpha compute preview-features describe - describe a preview feature + +SYNOPSIS + gcloud alpha compute preview-features describe PREVIEW_FEATURE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a preview feature. + +EXAMPLES + To retrieve a single preview feature and print its properties, run the + following command: + + $ gcloud alpha 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/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +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/preview-features/help b/gcloud/alpha/compute/preview-features/help new file mode 100644 index 000000000..603fc690c --- /dev/null +++ b/gcloud/alpha/compute/preview-features/help @@ -0,0 +1,33 @@ +NAME + gcloud alpha compute preview-features - read and manipulate Compute Engine + Preview Features + +SYNOPSIS + gcloud alpha compute preview-features COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) 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 + (ALPHA) Describe a preview feature. + + list + (ALPHA) View preview features. + + update + (ALPHA) Update a preview feature's activation status. + +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/preview-features/list b/gcloud/alpha/compute/preview-features/list new file mode 100644 index 000000000..3e4cd1662 --- /dev/null +++ b/gcloud/alpha/compute/preview-features/list @@ -0,0 +1,66 @@ +NAME + gcloud alpha compute preview-features list - view preview features + +SYNOPSIS + gcloud alpha compute preview-features list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) View preview features. + +EXAMPLES + To display all preview features, run the following command: + + $ gcloud alpha 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/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +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/preview-features/update b/gcloud/alpha/compute/preview-features/update new file mode 100644 index 000000000..3e659c737 --- /dev/null +++ b/gcloud/alpha/compute/preview-features/update @@ -0,0 +1,73 @@ +NAME + gcloud alpha compute preview-features update - update a preview feature's + activation status + +SYNOPSIS + gcloud alpha compute preview-features update PREVIEW_FEATURE + --activation-status=ACTIVATION_STATUS + (--custom-rollout-plan=CUSTOM_ROLLOUT_PLAN + | --rollout-plan=ROLLOUT_PLAN) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a preview feature's activation status. + +EXAMPLES + To enable/disable a preview feature's activation status, run the following + command: + + $ gcloud alpha 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: + rollout-plan-fast-rollout, rollout-plan-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/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +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/routes/create b/gcloud/alpha/compute/routes/create index 7bd137a27..3c5e75c4a 100644 --- a/gcloud/alpha/compute/routes/create +++ b/gcloud/alpha/compute/routes/create @@ -12,7 +12,8 @@ SYNOPSIS [--next-hop-ilb-region=NEXT_HOP_ILB_REGION] [--next-hop-instance-zone=NEXT_HOP_INSTANCE_ZONE] [--next-hop-vpn-tunnel-region=NEXT_HOP_VPN_TUNNEL_REGION] - [--priority=PRIORITY; default=1000] [--tags=TAG,[TAG,...]] + [--priority=PRIORITY; default=1000] + [--resource-manager-tags=[KEY=VALUE,...]] [--tags=TAG,[TAG,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -159,6 +160,9 @@ OPTIONAL FLAGS Specifies the priority of this route relative to other routes with the same specificity. The lower the value, the higher the priority. + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the route. + --tags=TAG,[TAG,...] Identifies the set of instances that this route will apply to. If no tags are provided, the route will apply to all instances in the diff --git a/gcloud/alpha/container/backup-restore/backup-channels/create b/gcloud/alpha/container/backup-restore/backup-channels/create index 46f5ff766..bfe5b9fef 100644 --- a/gcloud/alpha/container/backup-restore/backup-channels/create +++ b/gcloud/alpha/container/backup-restore/backup-channels/create @@ -18,7 +18,7 @@ EXAMPLES $ gcloud alpha container backup-restore backup-channels create \ my-backup-channel --project=my-project --location=us-central1 \ - --destination_project=projects/1234567890 + --destination-project=projects/1234567890 POSITIONAL ARGUMENTS Backup channel resource - Name of the backup channel to create. Once the diff --git a/gcloud/alpha/container/backup-restore/restore-channels/create b/gcloud/alpha/container/backup-restore/restore-channels/create index e5340fe02..4c2b95e41 100644 --- a/gcloud/alpha/container/backup-restore/restore-channels/create +++ b/gcloud/alpha/container/backup-restore/restore-channels/create @@ -18,7 +18,7 @@ EXAMPLES $ gcloud alpha container backup-restore restore-channels create \ my-restore-channel --project=my-project --location=us-central1 \ - --destination_project=projects/1234567890 + --destination-project=projects/1234567890 POSITIONAL ARGUMENTS Restore channel resource - Name of the restore channel to create. Once the diff --git a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/create b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/create index a46fa58dc..3b07548de 100644 --- a/gcloud/alpha/container/fleet/packages/resource-bundles/releases/create +++ b/gcloud/alpha/container/fleet/packages/resource-bundles/releases/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha container fleet packages resource-bundles releases create --resource-bundle=RESOURCE_BUNDLE --source=SOURCE --version=VERSION - [--lifecycle=LIFECYCLE] [--location=LOCATION] [--use-nested-variants] + [--lifecycle=LIFECYCLE] [--location=LOCATION] [--variants-pattern=VARIANTS_PATTERN] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -50,10 +50,6 @@ OPTIONAL FLAGS --location=LOCATION Google Cloud zone or region. - --use-nested-variants - Whether to use nested variants. If true, the Release will create - variants as nested resources. - --variants-pattern=VARIANTS_PATTERN Glob pattern to Variants of the Release, to be paired with the --source arg. ex: --source=/manifests-dir/ --variants-pattern=**, diff --git a/gcloud/alpha/container/hub/packages/resource-bundles/releases/create b/gcloud/alpha/container/hub/packages/resource-bundles/releases/create index 56a6950b0..5633e2fc6 100644 --- a/gcloud/alpha/container/hub/packages/resource-bundles/releases/create +++ b/gcloud/alpha/container/hub/packages/resource-bundles/releases/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha container hub packages resource-bundles releases create --resource-bundle=RESOURCE_BUNDLE --source=SOURCE --version=VERSION - [--lifecycle=LIFECYCLE] [--location=LOCATION] [--use-nested-variants] + [--lifecycle=LIFECYCLE] [--location=LOCATION] [--variants-pattern=VARIANTS_PATTERN] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -50,10 +50,6 @@ OPTIONAL FLAGS --location=LOCATION Google Cloud zone or region. - --use-nested-variants - Whether to use nested variants. If true, the Release will create - variants as nested resources. - --variants-pattern=VARIANTS_PATTERN Glob pattern to Variants of the Release, to be paired with the --source arg. ex: --source=/manifests-dir/ --variants-pattern=**, diff --git a/gcloud/alpha/dataplex/datascans/create/data-discovery b/gcloud/alpha/dataplex/datascans/create/data-discovery index 333cd42de..4921c64b0 100644 --- a/gcloud/alpha/dataplex/datascans/create/data-discovery +++ b/gcloud/alpha/dataplex/datascans/create/data-discovery @@ -133,12 +133,15 @@ OPTIONAL FLAGS --storage-exclude-patterns=[PATTERN,...] List of patterns that identify the data to exclude during - discovery. When both include and exclude patterns exist at the same - time, exclude patterns are applied first. + 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. + 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. diff --git a/gcloud/alpha/dataplex/datascans/update/data-discovery b/gcloud/alpha/dataplex/datascans/update/data-discovery index 8506edbc2..bd0b0107c 100644 --- a/gcloud/alpha/dataplex/datascans/update/data-discovery +++ b/gcloud/alpha/dataplex/datascans/update/data-discovery @@ -8,7 +8,15 @@ SYNOPSIS [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--async | --validate-only] [--bigquery-publishing-connection=BIGQUERY_PUBLISHING_CONNECTION - --bigquery-publishing-table-type=BIGQUERY_PUBLISHING_TABLE_TYPE] + --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 @@ -91,11 +99,66 @@ FLAGS 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 diff --git a/gcloud/alpha/dataplex/encryption-config/create b/gcloud/alpha/dataplex/encryption-config/create new file mode 100644 index 000000000..4923c8bb8 --- /dev/null +++ b/gcloud/alpha/dataplex/encryption-config/create @@ -0,0 +1,73 @@ +NAME + gcloud alpha dataplex encryption-config create - create a Dataplex + encryption config resource + +SYNOPSIS + gcloud alpha dataplex encryption-config create + (ENCRYPTION_CONFIG : --location=LOCATION --organization=ORGANIZATION) + [--key=KEY] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) An EncryptionConfig is created only for CMEK opted in + organizations. + +EXAMPLES + To create an EncryptionConfig default in organization test-org-id at + location us-central1 with key test-key, run: $ gcloud alpha dataplex encryption-config create default \ + --location=us-central1 --organization=test-org-id \ + --key='test-key' + +POSITIONAL ARGUMENTS + Encryption config resource - Arguments and flags that define the Dataplex + EncryptionConfig you want to create. The arguments in this group can be + used to specify the attributes of this resource. + + This must be specified. + + ENCRYPTION_CONFIG + ID of the encryption config or fully qualified identifier for the + encryption config. + + To set the encryption_config attribute: + ▸ provide the argument encryption_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 of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument encryption_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + + --organization=ORGANIZATION + The name of encryption config to use. + + To set the organization attribute: + ▸ provide the argument encryption_config on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. + +FLAGS + --key=KEY + The KMS key to use for encryption. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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 dataplex encryption-config create + diff --git a/gcloud/alpha/dataplex/encryption-config/describe b/gcloud/alpha/dataplex/encryption-config/describe new file mode 100644 index 000000000..e07647947 --- /dev/null +++ b/gcloud/alpha/dataplex/encryption-config/describe @@ -0,0 +1,71 @@ +NAME + gcloud alpha dataplex encryption-config describe - describe an + EncryptionConfig + +SYNOPSIS + gcloud alpha dataplex encryption-config describe + (ENCRYPTION_CONFIG : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe an EncryptionConfig. Displays all the details of an + EncryptionConfig used for CMEK with valid organization and location. + +EXAMPLES + To describe an EncryptionConfig: $ gcloud alpha dataplex encryption-config describe default \ + --location=us-central1 --organization=test-org + +POSITIONAL ARGUMENTS + Encryption config resource - encryption_config you want to Describe The + arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + ENCRYPTION_CONFIG + ID of the encryption config or fully qualified identifier for the + encryption config. + + To set the encryption_config attribute: + ▸ provide the argument encryption_config 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 encryption_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + + --organization=ORGANIZATION + Name of the Cloud organization to use. + + To set the organization attribute: + ▸ provide the argument encryption_config on the command line with a + fully specified name; + ▸ provide the argument --organization 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 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. This variant is also available: + + $ gcloud dataplex encryption-config describe + diff --git a/gcloud/alpha/dataplex/encryption-config/help b/gcloud/alpha/dataplex/encryption-config/help new file mode 100644 index 000000000..40161a61a --- /dev/null +++ b/gcloud/alpha/dataplex/encryption-config/help @@ -0,0 +1,32 @@ +NAME + gcloud alpha dataplex encryption-config - manage Dataplex encryption + configs + +SYNOPSIS + gcloud alpha dataplex encryption-config COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Dataplex encryption configs. + +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 encryption config resource. + + describe + (ALPHA) Describe an EncryptionConfig. + +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 dataplex encryption-config + diff --git a/gcloud/alpha/dataplex/glossaries/add-iam-policy-binding b/gcloud/alpha/dataplex/glossaries/add-iam-policy-binding new file mode 100644 index 000000000..0dffca921 --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/add-iam-policy-binding @@ -0,0 +1,90 @@ +NAME + gcloud alpha dataplex glossaries add-iam-policy-binding - add IAM policy + binding to a Dataplex Glossary + +SYNOPSIS + gcloud alpha dataplex glossaries add-iam-policy-binding + (GLOSSARY : --location=LOCATION) --member=PRINCIPAL --role=ROLE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Add IAM policy binding to a Dataplex Glossary. + +EXAMPLES + To add an IAM policy binding for the role of roles/dataplex.viewer for the + user test-user@gmail.com to Glossary test-glossary in location us-central, + run: $ gcloud alpha dataplex glossaries add-iam-policy-binding \ + test-glossary --project=test-project --location=us-central1 \ + --role=roles/dataplex.viewer --member=user:test-user@gmail.com \ + See https://cloud.google.com/dataplex/docs/iam-roles for \ + details of policy role and member types. + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + you want to add 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud dataplex glossaries add-iam-policy-binding + diff --git a/gcloud/alpha/dataplex/glossaries/categories/create b/gcloud/alpha/dataplex/glossaries/categories/create new file mode 100644 index 000000000..16431fa7f --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/categories/create @@ -0,0 +1,104 @@ +NAME + gcloud alpha dataplex glossaries categories create - creates a glossary + category + +SYNOPSIS + gcloud alpha dataplex glossaries categories create + (GLOSSARY_CATEGORY : --glossary=GLOSSARY --location=LOCATION) + --parent=PARENT [--description=DESCRIPTION] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) A glossary category represents a collection of glossary categories + and glossary terms within a glossary that are related to each other. + +EXAMPLES + To create a glossary category test-category in glossary test-glossary in + project test-project in location us-central1, with description test + description, displayName displayName and parent + projects/test-project/locations/us-central1/glossaries/test-glossary , run: + + $ gcloud alpha dataplex glossaries categories create test-category \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project \ + --parent='projects/test-project/locations/us-central1/glossaries\ + /test-glossary' --description='test description' \ + --display-name='displayName' + +POSITIONAL ARGUMENTS + Glossary category resource - Arguments and flags that define the Dataplex + Glossary Category 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 glossary_category 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. + + GLOSSARY_CATEGORY + ID of the glossary category or fully qualified identifier for the + glossary category. + + To set the glossary_category attribute: + ▸ provide the argument glossary_category on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + The name of glossary category to use. + + To set the glossary attribute: + ▸ provide the argument glossary_category on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + The location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_category on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + --parent=PARENT + Immediate parent of the created glossary category. + +OPTIONAL FLAGS + --description=DESCRIPTION + Description of the glossary category. + + --display-name=DISPLAY_NAME + Display name of the glossary category. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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 dataplex glossaries categories create + diff --git a/gcloud/alpha/dataplex/glossaries/categories/delete b/gcloud/alpha/dataplex/glossaries/categories/delete new file mode 100644 index 000000000..b2bda4fbe --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/categories/delete @@ -0,0 +1,79 @@ +NAME + gcloud alpha dataplex glossaries categories delete - deletes a glossary + category + +SYNOPSIS + gcloud alpha dataplex glossaries categories delete + (GLOSSARY_CATEGORY : --glossary=GLOSSARY --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes a glossary category. + +EXAMPLES + To delete glossary category test-category in glossary test-glossary in + project test-project in location us-central1, run: $ gcloud alpha dataplex glossaries categories delete test-category \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Glossary category resource - Arguments and flags that define the glossary + category you want 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 glossary_category 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. + + GLOSSARY_CATEGORY + ID of the glossary category or fully qualified identifier for the + glossary category. + + To set the glossary_category attribute: + ▸ provide the argument glossary_category on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + Identifier of the Dataplex Glossary resource. + + To set the glossary attribute: + ▸ provide the argument glossary_category on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_category 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. This variant is also available: + + $ gcloud dataplex glossaries categories delete + diff --git a/gcloud/alpha/dataplex/glossaries/categories/describe b/gcloud/alpha/dataplex/glossaries/categories/describe new file mode 100644 index 000000000..a49bfa5cc --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/categories/describe @@ -0,0 +1,79 @@ +NAME + gcloud alpha dataplex glossaries categories describe - describes a glossary + category + +SYNOPSIS + gcloud alpha dataplex glossaries categories describe + (GLOSSARY_CATEGORY : --glossary=GLOSSARY --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describes a glossary category. + +EXAMPLES + To describe a glossary category test-category in glossary test-glossary in + project test-project in loaction us-central1, run: $ gcloud alpha dataplex glossaries categories describe \ + test-category --glossary=test-glossary --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Glossary category resource - Arguments and flags that define the glossary + category 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 glossary_category 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. + + GLOSSARY_CATEGORY + ID of the glossary category or fully qualified identifier for the + glossary category. + + To set the glossary_category attribute: + ▸ provide the argument glossary_category on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + Identifier of the Dataplex Glossary resource. + + To set the glossary attribute: + ▸ provide the argument glossary_category on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_category 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. This variant is also available: + + $ gcloud dataplex glossaries categories describe + diff --git a/gcloud/alpha/dataplex/glossaries/categories/help b/gcloud/alpha/dataplex/glossaries/categories/help new file mode 100644 index 000000000..bae4928db --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/categories/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha dataplex glossaries categories - manage Dataplex glossary + categories + +SYNOPSIS + gcloud alpha dataplex glossaries categories COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) A glossary category represents a collection of glossary categories + and glossary terms within a glossary that are related to each other. + +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) Creates a glossary category. + + delete + (ALPHA) Deletes a glossary category. + + describe + (ALPHA) Describes a glossary category. + + list + (ALPHA) List glossary categories. + + update + (ALPHA) Updates a glossary category. + +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 dataplex glossaries categories + diff --git a/gcloud/alpha/dataplex/glossaries/categories/list b/gcloud/alpha/dataplex/glossaries/categories/list new file mode 100644 index 000000000..0505b47cf --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/categories/list @@ -0,0 +1,104 @@ +NAME + gcloud alpha dataplex glossaries categories list - list glossary categories + +SYNOPSIS + gcloud alpha dataplex glossaries categories list + (--glossary=GLOSSARY : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List glossary categories. + +EXAMPLES + To list glossary categories in glossary test-glossary in location + us-central1 in project test-project, run : + + $ gcloud alpha dataplex glossaries categories list \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project + +REQUIRED FLAGS + Glossary resource - Arguments and flags that define the glossary in which + to list glossary categories. 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 --glossary 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. + + --glossary=GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument --glossary on the command line. + + This flag 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 --glossary on the command line with a fully + specified name; + ▸ 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 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 dataplex glossaries categories list + diff --git a/gcloud/alpha/dataplex/glossaries/categories/update b/gcloud/alpha/dataplex/glossaries/categories/update new file mode 100644 index 000000000..a24cf15da --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/categories/update @@ -0,0 +1,108 @@ +NAME + gcloud alpha dataplex glossaries categories update - updates a glossary + category + +SYNOPSIS + gcloud alpha dataplex glossaries categories update + (GLOSSARY_CATEGORY : --glossary=GLOSSARY --location=LOCATION) + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [--parent=PARENT] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates a glossary category. + +EXAMPLES + To update display name, desciption and labels of glossary category + test-category in glossary test-glossary in project test-project in location + us-central1, run: + + $ gcloud alpha dataplex glossaries categories update test-category \ + --location=us-central1 --project=test-project \ + --glossary=test-glossary --description='updated description' \ + --display-name='updated displayName' \ + --labels=key1=value1,key2=value2 + + To update parent of glossary category test-category in glossary + test-glossary in project test-project in location us-central1, run: + + $ gcloud alpha dataplex glossaries categories update test-category \ + --location=us-central1 --project=test-project \ + --glossary=test-glossary \ + --parent='projects/test-project/locations/us-central1/glossaries\ + /updated-glossary' + +POSITIONAL ARGUMENTS + Glossary category resource - Arguments and flags that define the Dataplex + Glossary Category you want to update. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument glossary_category 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. + + GLOSSARY_CATEGORY + ID of the glossary category or fully qualified identifier for the + glossary category. + + To set the glossary_category attribute: + ▸ provide the argument glossary_category on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + The name of glossary category to use. + + To set the glossary attribute: + ▸ provide the argument glossary_category on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + The location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_category 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 glossary category. + + --display-name=DISPLAY_NAME + Display Name of the glossary category. + + --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. + + --parent=PARENT + Immediate parent of the created glossary category. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud dataplex glossaries categories update + diff --git a/gcloud/alpha/dataplex/glossaries/create b/gcloud/alpha/dataplex/glossaries/create new file mode 100644 index 000000000..005c65be5 --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/create @@ -0,0 +1,94 @@ +NAME + gcloud alpha dataplex glossaries create - create a Dataplex Glossary + resource + +SYNOPSIS + gcloud alpha dataplex glossaries create (GLOSSARY : --location=LOCATION) + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [--async | --validate-only] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) A Glossary represents a collection of Categories and Terms. + +EXAMPLES + To create a Glossary test-glossary in project test-dataplex at location + us-central1, with description test description and displayName displayName + , run: + + $ gcloud alpha dataplex glossaries create test-glossary \ + --location=us-central1 --project=test-dataplex \ + --description='test description' --display-name='displayName' + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary 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 Glossary. + + --display-name=DISPLAY_NAME + Display Name of the Glossary. + + --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 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud dataplex glossaries create + diff --git a/gcloud/alpha/dataplex/glossaries/delete b/gcloud/alpha/dataplex/glossaries/delete new file mode 100644 index 000000000..73a5a978d --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/delete @@ -0,0 +1,75 @@ +NAME + gcloud alpha dataplex glossaries delete - delete a Dataplex Glossary + +SYNOPSIS + gcloud alpha dataplex glossaries delete (GLOSSARY : --location=LOCATION) + [--async] [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Dataplex Glossary. + +EXAMPLES + To Delete Glossary test-glossary in project test-dataplex at location + us-central1, run: $ gcloud alpha dataplex glossaries delete test-glossary \ + --location=us-central1 --project=test-dataplex + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + you want 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --etag=ETAG + etag value for particular Glossary. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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. This variant is also available: + + $ gcloud dataplex glossaries delete + diff --git a/gcloud/alpha/dataplex/glossaries/describe b/gcloud/alpha/dataplex/glossaries/describe new file mode 100644 index 000000000..3859d9945 --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/describe @@ -0,0 +1,70 @@ +NAME + gcloud alpha dataplex glossaries describe - describe a Glossary + +SYNOPSIS + gcloud alpha dataplex glossaries describe (GLOSSARY : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Glossary. Displays all details of a Glossary given a + valid Glossary ID. + +EXAMPLES + To describe a Dataplex Glossary test-glossary within location us-central1 + and in project test-project + + $ gcloud alpha dataplex glossaries describe test-glossary \ + --location=us-central1 --project=test-project + +POSITIONAL ARGUMENTS + Glossary resource - Glossary 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary 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. This variant is also available: + + $ gcloud dataplex glossaries describe + diff --git a/gcloud/alpha/dataplex/glossaries/get-iam-policy b/gcloud/alpha/dataplex/glossaries/get-iam-policy new file mode 100644 index 000000000..8128b3ee0 --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/get-iam-policy @@ -0,0 +1,99 @@ +NAME + gcloud alpha dataplex glossaries get-iam-policy - retrieve a Dataplex + Glossary IAM policy + +SYNOPSIS + gcloud alpha dataplex glossaries get-iam-policy + (GLOSSARY : --location=LOCATION) [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Displays the IAM policy associated with a Dataplex Glossary + resource. If formatted as JSON, the output can be edited and used as a + policy file for set-iam-policy. The output includes an "etag" field + identifying the version emitted and allowing detection of concurrent policy + updates. + +EXAMPLES + To get the IAM policy of a Dataplex Glossary test-glossary in project + test-project under location us-central1 $ gcloud alpha dataplex glossaries get-iam-policy test-glossary \ + --project=test-project --location=us-central1 + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + IAM policy 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary on the command line with a fully + specified name; + ▸ 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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. This variant is also available: + + $ gcloud dataplex glossaries get-iam-policy + diff --git a/gcloud/alpha/dataplex/glossaries/help b/gcloud/alpha/dataplex/glossaries/help new file mode 100644 index 000000000..eda73d95b --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/help @@ -0,0 +1,62 @@ +NAME + gcloud alpha dataplex glossaries - manage Dataplex glossaries + +SYNOPSIS + gcloud alpha dataplex glossaries GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) A Glossary represents a collection of Categories and Terms. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + categories + (ALPHA) Manage Dataplex glossary categories. + + terms + (ALPHA) Manage Dataplex glossary terms. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + (ALPHA) Add IAM policy binding to a Dataplex Glossary. + + create + (ALPHA) Create a Dataplex Glossary resource. + + delete + (ALPHA) Delete a Dataplex Glossary. + + describe + (ALPHA) Describe a Glossary. + + get-iam-policy + (ALPHA) Retrieve a Dataplex Glossary IAM policy. + + list + (ALPHA) List Glossaries. + + remove-iam-policy-binding + (ALPHA) Removes IAM policy binding from a Dataplex Glossary. + + set-iam-policy + (ALPHA) Set an IAM policy binding for a Dataplex Glossary as defined in + a JSON or YAML file. + + update + (ALPHA) Updates a Dataplex Glossary. + +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 dataplex glossaries + diff --git a/gcloud/alpha/dataplex/glossaries/list b/gcloud/alpha/dataplex/glossaries/list new file mode 100644 index 000000000..35b3acc2a --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/list @@ -0,0 +1,88 @@ +NAME + gcloud alpha dataplex glossaries list - list Glossaries + +SYNOPSIS + gcloud alpha dataplex glossaries list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Glossaries. + +EXAMPLES + To List Glossaries in project test-dataplex at location us-central1 + + $ gcloud alpha dataplex glossaries list --location=us-central1 \ + --project=test-dataplex + +FLAGS + Location resource - Location in which to list Glossaries. 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 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 dataplex glossaries list + diff --git a/gcloud/alpha/dataplex/glossaries/remove-iam-policy-binding b/gcloud/alpha/dataplex/glossaries/remove-iam-policy-binding new file mode 100644 index 000000000..8c5027517 --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/remove-iam-policy-binding @@ -0,0 +1,91 @@ +NAME + gcloud alpha dataplex glossaries remove-iam-policy-binding - removes IAM + policy binding from a Dataplex Glossary + +SYNOPSIS + gcloud alpha dataplex glossaries remove-iam-policy-binding + (GLOSSARY : --location=LOCATION) --member=PRINCIPAL --role=ROLE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Removes IAM policy binding from a Dataplex Glossary. + +EXAMPLES + To remove an IAM policy binding for the role roles/dataplex.viewer for the + user test-user@gmail.com from a glossary test-glossary within projet + test-project in location us-central1, run: $ gcloud alpha dataplex glossaries remove-iam-policy-binding \ + test-glossary --project=test-project --location=us-central1 \ + --role=roles/dataplex.viewer --member=user:test-user@gmail.com \ + See https://cloud.google.com/dataplex/docs/iam-roles for \ + details of policy role and member types. + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + you want to remove 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud dataplex glossaries remove-iam-policy-binding + diff --git a/gcloud/alpha/dataplex/glossaries/set-iam-policy b/gcloud/alpha/dataplex/glossaries/set-iam-policy new file mode 100644 index 000000000..3d49c9986 --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/set-iam-policy @@ -0,0 +1,74 @@ +NAME + gcloud alpha dataplex glossaries set-iam-policy - set an IAM policy binding + for a Dataplex Glossary as defined in a JSON or YAML file + +SYNOPSIS + gcloud alpha dataplex glossaries set-iam-policy + (GLOSSARY : --location=LOCATION) POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) See https://cloud.google.com/iam/docs/managing-policies for details + of the policy file format and contents. + +EXAMPLES + The following command will read an IAM policy defined in a JSON file + policy.json and set it for the Dataplex Glossary test-glossary within + project test-project in location us-central1: $ gcloud alpha dataplex glossaries set-iam-policy test-glossary \ + --project=test-project --location=us-central1 policy.json \ + where policy.json is the relative path to the json file. + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + you want to set IAM policy 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/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. + +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 dataplex glossaries set-iam-policy + diff --git a/gcloud/alpha/dataplex/glossaries/terms/create b/gcloud/alpha/dataplex/glossaries/terms/create new file mode 100644 index 000000000..421ccfe2e --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/terms/create @@ -0,0 +1,104 @@ +NAME + gcloud alpha dataplex glossaries terms create - creates a glossary term + +SYNOPSIS + gcloud alpha dataplex glossaries terms create + (GLOSSARY_TERM : --glossary=GLOSSARY --location=LOCATION) + --parent=PARENT [--description=DESCRIPTION] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) A glossary term holds a rich text description that can be attached + to entries or specific columns to enrich them. + +EXAMPLES + To create a glossary term test-term in glossary test-glossary in project + test-project in location us-central1, with description test description, + displayName displayName and parent + projects/test-project/locations/us-central1/glossaries/test-glossary/categories/test-category + , run: + + $ gcloud alpha dataplex glossaries terms create test-term \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project \ + --parent='projects/test-project/locations/us-central1/glossaries\ + /test-glossary/categories/test-category' \ + --description='test description' --display-name='displayName' + +POSITIONAL ARGUMENTS + Glossary term resource - Arguments and flags that define the Dataplex + Glossary Term 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 glossary_term 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. + + GLOSSARY_TERM + ID of the glossary term or fully qualified identifier for the + glossary term. + + To set the glossary_term attribute: + ▸ provide the argument glossary_term on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + The name of glossary term to use. + + To set the glossary attribute: + ▸ provide the argument glossary_term on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + The location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_term on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + --parent=PARENT + Immediate parent of the created glossary term. + +OPTIONAL FLAGS + --description=DESCRIPTION + Description of the glossary term. + + --display-name=DISPLAY_NAME + Display name of the glossary term. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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 dataplex glossaries terms create + diff --git a/gcloud/alpha/dataplex/glossaries/terms/delete b/gcloud/alpha/dataplex/glossaries/terms/delete new file mode 100644 index 000000000..da51c2390 --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/terms/delete @@ -0,0 +1,80 @@ +NAME + gcloud alpha dataplex glossaries terms delete - deletes a glossary term + +SYNOPSIS + gcloud alpha dataplex glossaries terms delete + (GLOSSARY_TERM : --glossary=GLOSSARY --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes a glossary term. + +EXAMPLES + To delete the glossary term test-term in glossary test-glossary in project + test-project in location us-central1, run: + + $ gcloud alpha dataplex glossaries terms delete test-term \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Glossary term resource - Arguments and flags that define the glossary term + you want 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 glossary_term 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. + + GLOSSARY_TERM + ID of the glossary term or fully qualified identifier for the + glossary term. + + To set the glossary_term attribute: + ▸ provide the argument glossary_term on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + Identifier of the Dataplex Glossary resource. + + To set the glossary attribute: + ▸ provide the argument glossary_term on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_term 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. This variant is also available: + + $ gcloud dataplex glossaries terms delete + diff --git a/gcloud/alpha/dataplex/glossaries/terms/describe b/gcloud/alpha/dataplex/glossaries/terms/describe new file mode 100644 index 000000000..4215e998f --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/terms/describe @@ -0,0 +1,80 @@ +NAME + gcloud alpha dataplex glossaries terms describe - describes a glossary term + +SYNOPSIS + gcloud alpha dataplex glossaries terms describe + (GLOSSARY_TERM : --glossary=GLOSSARY --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describes a glossary term. + +EXAMPLES + To describe the glossary term test-term in glossary test-glossary in + project test-project in loaction us-central1, run: + + $ gcloud alpha dataplex glossaries terms describe test-term \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Glossary term resource - Arguments and flags that define the glossary term + 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 glossary_term 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. + + GLOSSARY_TERM + ID of the glossary term or fully qualified identifier for the + glossary term. + + To set the glossary_term attribute: + ▸ provide the argument glossary_term on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + Identifier of the Dataplex Glossary resource. + + To set the glossary attribute: + ▸ provide the argument glossary_term on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_term 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. This variant is also available: + + $ gcloud dataplex glossaries terms describe + diff --git a/gcloud/alpha/dataplex/glossaries/terms/help b/gcloud/alpha/dataplex/glossaries/terms/help new file mode 100644 index 000000000..7d715338c --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/terms/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha dataplex glossaries terms - manage Dataplex glossary terms + +SYNOPSIS + gcloud alpha dataplex glossaries terms COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Glossary terms are the core of a Dataplex glossary. A glossary term + holds a rich text description that can be attached to entries or specific + columns to enrich them. + +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) Creates a glossary term. + + delete + (ALPHA) Deletes a glossary term. + + describe + (ALPHA) Describes a glossary term. + + list + (ALPHA) List glossary terms. + + update + (ALPHA) Updates a glossary term. + +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 dataplex glossaries terms + diff --git a/gcloud/alpha/dataplex/glossaries/terms/list b/gcloud/alpha/dataplex/glossaries/terms/list new file mode 100644 index 000000000..a46069247 --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/terms/list @@ -0,0 +1,104 @@ +NAME + gcloud alpha dataplex glossaries terms list - list glossary terms + +SYNOPSIS + gcloud alpha dataplex glossaries terms list + (--glossary=GLOSSARY : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List glossary terms. + +EXAMPLES + To list glossary terms in glossary test-glossary in project test-project in + location us-central1, run : + + $ gcloud alpha dataplex glossaries terms list \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project + +REQUIRED FLAGS + Glossary resource - Arguments and flags that define the glossary in which + to list glossary terms. 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 --glossary 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. + + --glossary=GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument --glossary on the command line. + + This flag 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 --glossary on the command line with a fully + specified name; + ▸ 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 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 dataplex glossaries terms list + diff --git a/gcloud/alpha/dataplex/glossaries/terms/update b/gcloud/alpha/dataplex/glossaries/terms/update new file mode 100644 index 000000000..ce856b6dd --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/terms/update @@ -0,0 +1,107 @@ +NAME + gcloud alpha dataplex glossaries terms update - updates a glossary term + +SYNOPSIS + gcloud alpha dataplex glossaries terms update + (GLOSSARY_TERM : --glossary=GLOSSARY --location=LOCATION) + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [--parent=PARENT] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates a glossary term. + +EXAMPLES + To update display name, desciption and labels of glossary term test-term in + glossary test-glossary in project test-project in location us-central1, + run: + + $ gcloud alpha dataplex glossaries terms update test-term \ + --location=us-central1 --project=test-project \ + --glossary=test-glossary --description='updated description' \ + --display-name='updated displayName' \ + --labels=key1=value1,key2=value2 + + To update parent of glossary term test-term in glossary test-glossary in + project test-project in location us-central1, run: + + $ gcloud alpha dataplex glossaries terms update test-term \ + --location=us-central1 --project=test-project \ + --glossary=test-glossary \ + --parent='projects/test-project/locations/us-central1/glossaries\ + /updated-glossary' + +POSITIONAL ARGUMENTS + Glossary term resource - Arguments and flags that define the Dataplex + Glossary Term you want to update. The arguments in this group can be used + to specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument glossary_term 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. + + GLOSSARY_TERM + ID of the glossary term or fully qualified identifier for the + glossary term. + + To set the glossary_term attribute: + ▸ provide the argument glossary_term on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + The name of glossary term to use. + + To set the glossary attribute: + ▸ provide the argument glossary_term on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + The location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_term 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 glossary term. + + --display-name=DISPLAY_NAME + Display name of the glossary term. + + --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. + + --parent=PARENT + Immediate parent of the created glossary term. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud dataplex glossaries terms update + diff --git a/gcloud/alpha/dataplex/glossaries/update b/gcloud/alpha/dataplex/glossaries/update new file mode 100644 index 000000000..2f8c358b2 --- /dev/null +++ b/gcloud/alpha/dataplex/glossaries/update @@ -0,0 +1,94 @@ +NAME + gcloud alpha dataplex glossaries update - updates a Dataplex Glossary + +SYNOPSIS + gcloud alpha dataplex glossaries update (GLOSSARY : --location=LOCATION) + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--etag=ETAG] + [--labels=[KEY=VALUE,...]] [--async | --validate-only] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates a Dataplex Glossary. + +EXAMPLES + To update Glossary test-glossary in project test-dataplex at location + us-central1, with description updated description and displayName + displayName $ gcloud alpha dataplex glossaries update test-glossary \ + --location=us-central1 --project test-dataplex \ + --description='updated description' + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + you want to update. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary 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 Glossary. + + --display-name=DISPLAY_NAME + Display Name of the Glossary. + + --etag=ETAG + etag value for particular Glossary. + + --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 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud dataplex glossaries update + diff --git a/gcloud/alpha/dataplex/help b/gcloud/alpha/dataplex/help index e648897d3..257b0f033 100644 --- a/gcloud/alpha/dataplex/help +++ b/gcloud/alpha/dataplex/help @@ -33,6 +33,9 @@ GROUPS datascans (ALPHA) Manage Dataplex Datascan. + encryption-config + (ALPHA) Manage Dataplex encryption configs. + entries (ALPHA) Manage Dataplex Catalog Entries resources. @@ -45,9 +48,15 @@ GROUPS environments (ALPHA) Manage Dataplex Environments. + glossaries + (ALPHA) Manage Dataplex glossaries. + lakes (ALPHA) Manage Dataplex Lake resources. + metadata-jobs + (ALPHA) Manage Dataplex metadata jobs. + tasks (ALPHA) Manage Dataplex Task services. diff --git a/gcloud/alpha/dataplex/metadata-jobs/cancel b/gcloud/alpha/dataplex/metadata-jobs/cancel new file mode 100644 index 000000000..cea54c603 --- /dev/null +++ b/gcloud/alpha/dataplex/metadata-jobs/cancel @@ -0,0 +1,68 @@ +NAME + gcloud alpha dataplex metadata-jobs cancel - cancel a Metadata Job run + +SYNOPSIS + gcloud alpha dataplex metadata-jobs cancel + (METADATA_JOB : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) 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 alpha 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 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/metadata-jobs/create b/gcloud/alpha/dataplex/metadata-jobs/create new file mode 100644 index 000000000..880c98ac3 --- /dev/null +++ b/gcloud/alpha/dataplex/metadata-jobs/create @@ -0,0 +1,258 @@ +NAME + gcloud alpha dataplex metadata-jobs create - create a Dataplex Metadata Job + +SYNOPSIS + gcloud alpha 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-types=[IMPORT_ENTRY_TYPES,...]) + : --import-log-level=IMPORT_LOG_LEVEL + --import-source-create-time=IMPORT_SOURCE_CREATE_TIME]) [--async] + [--labels=[KEY=VALUE,...]] [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) 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 alpha 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 alpha 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-types=[IMPORT_ENTRY_TYPES,...] + The list of entry types 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 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/metadata-jobs/describe b/gcloud/alpha/dataplex/metadata-jobs/describe new file mode 100644 index 000000000..639d007a8 --- /dev/null +++ b/gcloud/alpha/dataplex/metadata-jobs/describe @@ -0,0 +1,69 @@ +NAME + gcloud alpha dataplex metadata-jobs describe - describe a Metadata Job + +SYNOPSIS + gcloud alpha dataplex metadata-jobs describe + (METADATA_JOB : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) 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 alpha 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 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/metadata-jobs/help b/gcloud/alpha/dataplex/metadata-jobs/help new file mode 100644 index 000000000..a238d1d75 --- /dev/null +++ b/gcloud/alpha/dataplex/metadata-jobs/help @@ -0,0 +1,35 @@ +NAME + gcloud alpha dataplex metadata-jobs - manage Dataplex metadata jobs + +SYNOPSIS + gcloud alpha dataplex metadata-jobs COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) 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 + (ALPHA) Cancel a Metadata Job run. + + create + (ALPHA) Create a Dataplex Metadata Job. + + describe + (ALPHA) Describe a Metadata Job. + + list + (ALPHA) List Metadata Job resources under a project. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/dataplex/metadata-jobs/list b/gcloud/alpha/dataplex/metadata-jobs/list new file mode 100644 index 000000000..3a7d3a7e5 --- /dev/null +++ b/gcloud/alpha/dataplex/metadata-jobs/list @@ -0,0 +1,88 @@ +NAME + gcloud alpha dataplex metadata-jobs list - list Metadata Job resources + under a project + +SYNOPSIS + gcloud alpha dataplex metadata-jobs list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) 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 alpha 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 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/dataproc/clusters/create b/gcloud/alpha/dataproc/clusters/create index cd91785be..2399f7546 100644 --- a/gcloud/alpha/dataproc/clusters/create +++ b/gcloud/alpha/dataproc/clusters/create @@ -43,7 +43,8 @@ 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] [--stop-max-idle=STOP_MAX_IDLE] + [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -77,6 +78,8 @@ 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 ...] @@ -418,6 +421,11 @@ 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. @@ -942,6 +950,18 @@ 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 392179dd9..7f4d56dc6 100644 --- a/gcloud/alpha/dataproc/clusters/update +++ b/gcloud/alpha/dataproc/clusters/update @@ -17,7 +17,11 @@ 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] [GCLOUD_WIDE_FLAG ...] + | --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 ...] DESCRIPTION (ALPHA) Update the number of worker nodes and/or the labels in a cluster. @@ -221,6 +225,33 @@ 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/deploy/job-runs/terminate b/gcloud/alpha/deploy/job-runs/terminate index cb7b61f03..00cd6a4bb 100644 --- a/gcloud/alpha/deploy/job-runs/terminate +++ b/gcloud/alpha/deploy/job-runs/terminate @@ -5,7 +5,7 @@ SYNOPSIS gcloud alpha deploy job-runs terminate (JOB_RUN : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION --release=RELEASE --rollout=ROLLOUT) - [GCLOUD_WIDE_FLAG ...] + [--override-deploy-policies=[POLICY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Terminates a Cloud Deploy job run. @@ -78,6 +78,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --rollout on the command line. +FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/releases/create b/gcloud/alpha/deploy/releases/create index 3b6c638a2..048e6c7b5 100644 --- a/gcloud/alpha/deploy/releases/create +++ b/gcloud/alpha/deploy/releases/create @@ -9,6 +9,7 @@ SYNOPSIS [--description=DESCRIPTION] [--gcs-source-staging-dir=GCS_SOURCE_STAGING_DIR] [--ignore-file=IGNORE_FILE] [--labels=[KEY=VALUE,...]] + [--override-deploy-policies=[POLICY,...]] [--skaffold-version=SKAFFOLD_VERSION] [--to-target=TO_TARGET] [--build-artifacts=BUILD_ARTIFACTS | --images=[NAME=TAG,...]] [--disable-initial-rollout | --enable-initial-rollout @@ -148,6 +149,9 @@ FLAGS $ gcloud alpha deploy releases create \ --labels="commit=abc123,author=foo" + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --skaffold-version=SKAFFOLD_VERSION Version of the Skaffold binary. diff --git a/gcloud/alpha/deploy/releases/promote b/gcloud/alpha/deploy/releases/promote index 931abe449..ad1496e84 100644 --- a/gcloud/alpha/deploy/releases/promote +++ b/gcloud/alpha/deploy/releases/promote @@ -7,8 +7,9 @@ SYNOPSIS (--release=RELEASE : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) [--annotations=[KEY=VALUE,...]] [--labels=[KEY=VALUE,...]] - [--rollout-id=ROLLOUT_ID] [--starting-phase-id=STARTING_PHASE_ID] - [--to-target=TO_TARGET] [GCLOUD_WIDE_FLAG ...] + [--override-deploy-policies=[POLICY,...]] [--rollout-id=ROLLOUT_ID] + [--starting-phase-id=STARTING_PHASE_ID] [--to-target=TO_TARGET] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) If to-target is not specified the command promotes the release from @@ -89,6 +90,9 @@ OPTIONAL FLAGS $ gcloud alpha deploy releases promote \ --labels="commit=abc123,author=foo" + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --rollout-id=ROLLOUT_ID ID to assign to the generated rollout for promotion. diff --git a/gcloud/alpha/deploy/rollouts/advance b/gcloud/alpha/deploy/rollouts/advance index 0cc0f4d5a..1a5344553 100644 --- a/gcloud/alpha/deploy/rollouts/advance +++ b/gcloud/alpha/deploy/rollouts/advance @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha deploy rollouts advance (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE - --region=REGION --release=RELEASE) [--phase-id=PHASE_ID] + --region=REGION --release=RELEASE) + [--override-deploy-policies=[POLICY,...]] [--phase-id=PHASE_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -70,6 +71,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --release on the command line. FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --phase-id=PHASE_ID Phase ID on a rollout resource diff --git a/gcloud/alpha/deploy/rollouts/approve b/gcloud/alpha/deploy/rollouts/approve index f13616b8f..8d64a41d3 100644 --- a/gcloud/alpha/deploy/rollouts/approve +++ b/gcloud/alpha/deploy/rollouts/approve @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha deploy rollouts approve (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE - --region=REGION --release=RELEASE) [GCLOUD_WIDE_FLAG ...] + --region=REGION --release=RELEASE) + [--override-deploy-policies=[POLICY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Approves a rollout having an Approval state of "Required". @@ -69,6 +70,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --release on the command line. +FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/rollouts/cancel b/gcloud/alpha/deploy/rollouts/cancel index 9d5df72a9..d10e7493e 100644 --- a/gcloud/alpha/deploy/rollouts/cancel +++ b/gcloud/alpha/deploy/rollouts/cancel @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha deploy rollouts cancel (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE - --region=REGION --release=RELEASE) [GCLOUD_WIDE_FLAG ...] + --region=REGION --release=RELEASE) + [--override-deploy-policies=[POLICY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Cancel a Rollout. @@ -68,6 +69,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --release on the command line. +FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/rollouts/ignore-job b/gcloud/alpha/deploy/rollouts/ignore-job index 0e4440f07..d00dc34f6 100644 --- a/gcloud/alpha/deploy/rollouts/ignore-job +++ b/gcloud/alpha/deploy/rollouts/ignore-job @@ -6,7 +6,8 @@ SYNOPSIS gcloud alpha deploy rollouts ignore-job (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION --release=RELEASE) --job-id=JOB_ID - --phase-id=PHASE_ID [GCLOUD_WIDE_FLAG ...] + --phase-id=PHASE_ID [--override-deploy-policies=[POLICY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Ignores a specified job and phase combination on a rollout. @@ -79,6 +80,10 @@ REQUIRED FLAGS --phase-id=PHASE_ID Phase ID on a rollout resource +OPTIONAL FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/rollouts/reject b/gcloud/alpha/deploy/rollouts/reject index e6c65f795..eef7731bb 100644 --- a/gcloud/alpha/deploy/rollouts/reject +++ b/gcloud/alpha/deploy/rollouts/reject @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha deploy rollouts reject (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE - --region=REGION --release=RELEASE) [GCLOUD_WIDE_FLAG ...] + --region=REGION --release=RELEASE) + [--override-deploy-policies=[POLICY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Rejects a rollout having an Approval state of "Required". @@ -69,6 +70,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --release on the command line. +FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/rollouts/retry-job b/gcloud/alpha/deploy/rollouts/retry-job index 96e32c038..18826cd91 100644 --- a/gcloud/alpha/deploy/rollouts/retry-job +++ b/gcloud/alpha/deploy/rollouts/retry-job @@ -6,7 +6,8 @@ SYNOPSIS gcloud alpha deploy rollouts retry-job (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION --release=RELEASE) --job-id=JOB_ID - --phase-id=PHASE_ID [GCLOUD_WIDE_FLAG ...] + --phase-id=PHASE_ID [--override-deploy-policies=[POLICY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Retries a specified job, phase combination on a rollout. @@ -79,6 +80,10 @@ REQUIRED FLAGS --phase-id=PHASE_ID Phase ID on a rollout resource +OPTIONAL FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/targets/redeploy b/gcloud/alpha/deploy/targets/redeploy index 3de6a9243..5bf5548c8 100644 --- a/gcloud/alpha/deploy/targets/redeploy +++ b/gcloud/alpha/deploy/targets/redeploy @@ -6,8 +6,8 @@ SYNOPSIS gcloud alpha deploy targets redeploy (TARGET : --region=REGION) --delivery-pipeline=DELIVERY_PIPELINE [--annotations=[KEY=VALUE,...]] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--rollout-id=ROLLOUT_ID] [--starting-phase-id=STARTING_PHASE_ID] - [GCLOUD_WIDE_FLAG ...] + [--override-deploy-policies=[POLICY,...]] [--rollout-id=ROLLOUT_ID] + [--starting-phase-id=STARTING_PHASE_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Redeploy the last rollout that has a state of SUCCESSFUL or FAILED @@ -83,6 +83,9 @@ OPTIONAL FLAGS $ gcloud alpha deploy targets redeploy \ --labels="commit=abc123,author=foo" + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --rollout-id=ROLLOUT_ID ID to assign to the generated rollout for promotion. diff --git a/gcloud/alpha/deploy/targets/rollback b/gcloud/alpha/deploy/targets/rollback index 914eea888..e9b6556a2 100644 --- a/gcloud/alpha/deploy/targets/rollback +++ b/gcloud/alpha/deploy/targets/rollback @@ -6,9 +6,9 @@ SYNOPSIS gcloud alpha deploy targets rollback (TARGET : --region=REGION) --delivery-pipeline=DELIVERY_PIPELINE [--annotations=[KEY=VALUE,...]] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--release=RELEASE] [--rollback-of-rollout=ROLLBACK_OF_ROLLOUT] - [--rollout-id=ROLLOUT_ID] [--starting-phase-id=STARTING_PHASE_ID] - [GCLOUD_WIDE_FLAG ...] + [--override-deploy-policies=[POLICY,...]] [--release=RELEASE] + [--rollback-of-rollout=ROLLBACK_OF_ROLLOUT] [--rollout-id=ROLLOUT_ID] + [--starting-phase-id=STARTING_PHASE_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) If release is not specified, the command rollbacks the target with @@ -84,6 +84,9 @@ OPTIONAL FLAGS $ gcloud alpha deploy targets rollback \ --labels="commit=abc123,author=foo" + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --release=RELEASE Name of the release to rollback to. diff --git a/gcloud/alpha/iam/workforce-pools/providers/create-oidc b/gcloud/alpha/iam/workforce-pools/providers/create-oidc index 966c5c961..bdb774dff 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/create-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/create-oidc @@ -273,32 +273,28 @@ OPTIONAL FLAGS *--extra-attributes-client-id*=_EXTRA_ATTRIBUTES_CLIENT_ID_:: - The OAuth 2.0 client ID for retrieving extra attributes from the identity provider. Required - to get the Access Token using client credentials grant flow. + The OAuth 2.0 client ID for retrieving extra attributes from the identity provider. Required to get the access token using client credentials grant flow. *--extra-attributes-client-secret-value*=_EXTRA_ATTRIBUTES_CLIENT_SECRET_VALUE_:: - The OAuth 2.0 client secret for retrieving extra attributes from the identity provider. - Required to get the Access Token using client credentials grant flow. + The OAuth 2.0 client secret for retrieving extra attributes from the identity provider. Required to get the access token using client credentials grant flow. *--extra-attributes-issuer-uri*=_EXTRA_ATTRIBUTES_ISSUER_URI_:: - OIDC identity provider's issuer URI. Must be a valid URI using the 'https' scheme. - Required to get the OIDC discovery document. + OIDC identity provider's issuer URI. Must be a valid URI using the `https` scheme. Required to get the OIDC discovery document. *--extra-attributes-type*=_EXTRA_ATTRIBUTES_TYPE_:: - Represents the identity provider and type of claims that should be fetched. _EXTRA_ATTRIBUTES_TYPE_ must be one of: *attributes-type-unspecified*, *azure-ad-groups-display-name*, *azure-ad-groups-id*, *azure-ad-groups-mail*. + Represents the identity provider and type of claims that should be fetched. _EXTRA_ATTRIBUTES_TYPE_ must be one of: *azure-ad-groups-mail*, *azure-ad-groups-id*. *--extra-attributes-filter*=_EXTRA_ATTRIBUTES_FILTER_:: - The filter used to request specific records from IdP. When used with the attributes type - azure-ad-groups-mail or azure-ad-groups-id, the filter requests specific groups associated - with a user from the IdP. By default all of the groups associated with the user are fetched. - When used with the attributes type azure-ad-groups-mail, the groups that are used should be - security and mail enabled. When used with the attributes type azure-ad-groups-id, the groups - that are used should be security enabled. See - https://learn.microsoft.com/en-us/graph/search-query-parameter for more details. + The filter used to request specific records from the IdP. By default, all of the groups that are associated with a user are fetched. For Microsoft Entra ID, you can add `$search` query parameters using [Keyword Query Language] (https://learn.microsoft.com/en-us/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference). To learn more about `$search` querying in Microsoft Entra ID, see [Use the `$search` query parameter] (https://learn.microsoft.com/en-us/graph/search-query-parameter). + + Additionally, Workforce Identity Federation automatically adds the following [`$filter` query parameters] (https://learn.microsoft.com/en-us/graph/filter-query-parameter), based on the value of `attributes_type`. Values passed to `filter` are converted to `$search` query parameters. Additional `$filter` query parameters cannot be added using this field. + + * `AZURE_AD_GROUPS_MAIL`: `mailEnabled` and `securityEnabled` filters are applied. + * `AZURE_AD_GROUPS_ID`: `securityEnabled` filter is 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. diff --git a/gcloud/alpha/iam/workforce-pools/providers/update-oidc b/gcloud/alpha/iam/workforce-pools/providers/update-oidc index 8d9f94b66..aca7216f4 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/update-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/update-oidc @@ -259,36 +259,32 @@ FLAGS *--clear-extra-attributes-config*::: - Clear the extra attributes configuration + Clear the extra attributes configuration. *--extra-attributes-client-id*=_EXTRA_ATTRIBUTES_CLIENT_ID_::: - The OAuth 2.0 client ID for retrieving extra attributes from the identity provider. Required - to get the Access Token using client credentials grant flow. + The OAuth 2.0 client ID for retrieving extra attributes from the identity provider. Required to get the access token using client credentials grant flow. *--extra-attributes-client-secret-value*=_EXTRA_ATTRIBUTES_CLIENT_SECRET_VALUE_::: - The OAuth 2.0 client secret for retrieving extra attributes from the identity provider. - Required to get the Access Token using client credentials grant flow. + The OAuth 2.0 client secret for retrieving extra attributes from the identity provider. Required to get the access token using client credentials grant flow. *--extra-attributes-filter*=_EXTRA_ATTRIBUTES_FILTER_::: - The filter used to request specific records from IdP. When used with the attributes type - azure-ad-groups-mail or azure-ad-groups-id, the filter requests specific groups associated - with a user from the IdP. By default all of the groups associated with the user are fetched. - When used with the attributes type azure-ad-groups-mail, the groups that are used should be - security and mail enabled. When used with the attributes type azure-ad-groups-id, the groups - that are used should be security enabled. See - https://learn.microsoft.com/en-us/graph/search-query-parameter for more details. + The filter used to request specific records from the IdP. By default, all of the groups that are associated with a user are fetched. For Microsoft Entra ID, you can add `$search` query parameters using [Keyword Query Language] (https://learn.microsoft.com/en-us/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference). To learn more about `$search` querying in Microsoft Entra ID, see [Use the `$search` query parameter] (https://learn.microsoft.com/en-us/graph/search-query-parameter). + + Additionally, Workforce Identity Federation automatically adds the following [`$filter` query parameters] (https://learn.microsoft.com/en-us/graph/filter-query-parameter), based on the value of `attributes_type`. Values passed to `filter` are converted to `$search` query parameters. Additional `$filter` query parameters cannot be added using this field. + + * `AZURE_AD_GROUPS_MAIL`: `mailEnabled` and `securityEnabled` filters are applied. + * `AZURE_AD_GROUPS_ID`: `securityEnabled` filter is applied. *--extra-attributes-issuer-uri*=_EXTRA_ATTRIBUTES_ISSUER_URI_::: - OIDC identity provider's issuer URI. Must be a valid URI using the 'https' scheme. - Required to get the OIDC discovery document. + OIDC identity provider's issuer URI. Must be a valid URI using the `https` scheme. Required to get the OIDC discovery document. *--extra-attributes-type*=_EXTRA_ATTRIBUTES_TYPE_::: - Represents the identity provider and type of claims that should be fetched. _EXTRA_ATTRIBUTES_TYPE_ must be one of: *attributes-type-unspecified*, *azure-ad-groups-display-name*, *azure-ad-groups-id*, *azure-ad-groups-mail*. + Represents the identity provider and type of claims that should be fetched. _EXTRA_ATTRIBUTES_TYPE_ must be one of: *azure-ad-groups-mail*, *azure-ad-groups-id*. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity. diff --git a/gcloud/alpha/managed-kafka/acls/add-acl-entry b/gcloud/alpha/managed-kafka/acls/add-acl-entry index d2a48aef0..b681592d3 100644 --- a/gcloud/alpha/managed-kafka/acls/add-acl-entry +++ b/gcloud/alpha/managed-kafka/acls/add-acl-entry @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha managed-kafka acls add-acl-entry (ACL : --cluster=CLUSTER --location=LOCATION) --operation=OPERATION - --principal=PRINCIPAL [--host=HOST; default=""] + --principal=PRINCIPAL [--host=HOST; default="*"] [--permission-type=PERMISSION_TYPE; default="ALLOW"] [GCLOUD_WIDE_FLAG ...] @@ -101,7 +101,7 @@ REQUIRED FLAGS "User:*" to refer to all users. OPTIONAL FLAGS - --host=HOST; default="" + --host=HOST; default="*" The host. Must be set to "*" for Managed Service for Apache Kafka. --permission-type=PERMISSION_TYPE; default="ALLOW" diff --git a/gcloud/alpha/managed-kafka/acls/remove-acl-entry b/gcloud/alpha/managed-kafka/acls/remove-acl-entry index f48765472..c9da9e96f 100644 --- a/gcloud/alpha/managed-kafka/acls/remove-acl-entry +++ b/gcloud/alpha/managed-kafka/acls/remove-acl-entry @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha managed-kafka acls remove-acl-entry (ACL : --cluster=CLUSTER --location=LOCATION) --operation=OPERATION - --principal=PRINCIPAL [--host=HOST; default=""] + --principal=PRINCIPAL [--host=HOST; default="*"] [--permission-type=PERMISSION_TYPE; default="ALLOW"] [GCLOUD_WIDE_FLAG ...] @@ -81,7 +81,7 @@ REQUIRED FLAGS "User:*" to refer to all users. OPTIONAL FLAGS - --host=HOST; default="" + --host=HOST; default="*" The host. Must be set to "*" for Managed Service for Apache Kafka. --permission-type=PERMISSION_TYPE; default="ALLOW" diff --git a/gcloud/alpha/managed-kafka/clusters/create b/gcloud/alpha/managed-kafka/clusters/create index b9984b409..2d5f3376b 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] [--encryption-key=ENCRYPTION_KEY] - [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--no-auto-rebalance] [--ca-pools=[CA_POOLS,...]] + [--encryption-key=ENCRYPTION_KEY] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a Managed Service for Apache Kafka cluster. @@ -62,13 +63,13 @@ REQUIRED FLAGS between 1 GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi. --subnets=[SUBNETS,...] - VPC subnets from which the cluster is accessible. Both broker and - bootstrap server IP addresses and DNS entries are automatically created - in each subnet. Only one subnet per network is allowed, and the subnet - must be located in the same region as the cluster. The project may - differ. A minimum of 1 subnet is required. A maximum of 10 subnets can - be specified. Use commas to separate multiple subnets. The name of the - subnet must be in the format + A comma-separated list of VPC subnets from which the cluster is + accessible. Both broker and bootstrap server IP addresses and DNS + entries are automatically created in each subnet. Only one subnet per + network is allowed, and the subnet must be located in the same region + as the cluster. The project may differ. A minimum of 1 subnet is + required. A maximum of 10 subnets can be specified. Use commas to + separate multiple subnets. The name of the subnet must be in the format projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. OPTIONAL FLAGS @@ -83,6 +84,14 @@ 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: diff --git a/gcloud/alpha/managed-kafka/clusters/update b/gcloud/alpha/managed-kafka/clusters/update index bb73fed65..2259a841f 100644 --- a/gcloud/alpha/managed-kafka/clusters/update +++ b/gcloud/alpha/managed-kafka/clusters/update @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha managed-kafka clusters update (CLUSTER : --location=LOCATION) - (--auto-rebalance --cpu=CPU + (--auto-rebalance --ca-pools=[CA_POOLS,...] --cpu=CPU --labels=[KEY=VALUE,...] --memory=MEMORY --subnets=[SUBNETS,...]) [--async] [GCLOUD_WIDE_FLAG ...] @@ -61,6 +61,15 @@ 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. @@ -75,14 +84,14 @@ REQUIRED FLAGS between 1 GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi. --subnets=[SUBNETS,...] - VPC subnets from which the cluster is accessible. Both broker and - bootstrap server IP addresses and DNS entries are automatically - created in each subnet. Only one subnet per network is allowed, and - the subnet must be located in the same region as the cluster. The - project may differ. A minimum of 1 subnet is required. A maximum of - 10 subnets can be specified. Use commas to separate multiple subnets. - The name of the subnet must be in the format - projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. + A comma-separated list of VPC subnets from which the cluster is + accessible. Both broker and bootstrap server IP addresses and DNS + entries are automatically created in each subnet. Only one subnet per + network is allowed, and the subnet must be located in the same region + as the cluster. The project may differ. A minimum of 1 subnet is + required. A maximum of 10 subnets can be specified. Use commas to + separate multiple subnets. The name of the subnet must be in the + format projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. OPTIONAL FLAGS --async diff --git a/gcloud/alpha/managed-kafka/consumer-groups/update b/gcloud/alpha/managed-kafka/consumer-groups/update index 0f37e2c40..2214edf5f 100644 --- a/gcloud/alpha/managed-kafka/consumer-groups/update +++ b/gcloud/alpha/managed-kafka/consumer-groups/update @@ -74,7 +74,7 @@ REQUIRED FLAGS --topics-file=JSON|YAML|FILE The path to the JSON or YAML file containing the configuration of the topics to be updated for the consumer group. This also supports inline - JSON or YAML. Required, Sets topics_file value. + JSON or YAML. Required, sets topics_file value. Input Example: diff --git a/gcloud/alpha/managed-kafka/help b/gcloud/alpha/managed-kafka/help index 0c3e4531c..cf992f659 100644 --- a/gcloud/alpha/managed-kafka/help +++ b/gcloud/alpha/managed-kafka/help @@ -35,6 +35,9 @@ GROUPS operations (ALPHA) View Managed Service for Apache Kafka operations. + schema-registries + (ALPHA) Administer Managed Service for Apache Kafka schema-registries. + topics (ALPHA) Administer Managed Service for Apache Kafka topics. diff --git a/gcloud/alpha/managed-kafka/schema-registries/create b/gcloud/alpha/managed-kafka/schema-registries/create new file mode 100644 index 000000000..2b47ca779 --- /dev/null +++ b/gcloud/alpha/managed-kafka/schema-registries/create @@ -0,0 +1,71 @@ +NAME + gcloud alpha managed-kafka schema-registries create - create a Managed + Service for Apache Kafka schema registry + +SYNOPSIS + gcloud alpha managed-kafka schema-registries create + (SCHEMA_REGISTRY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Managed Service for Apache Kafka schema registry. + +EXAMPLES + To create a schema registry, run the following: + + $ gcloud alpha 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 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/delete b/gcloud/alpha/managed-kafka/schema-registries/delete new file mode 100644 index 000000000..92017d4cc --- /dev/null +++ b/gcloud/alpha/managed-kafka/schema-registries/delete @@ -0,0 +1,72 @@ +NAME + gcloud alpha managed-kafka schema-registries delete - delete a Managed + Service for Apache Kafka schema registry + +SYNOPSIS + gcloud alpha managed-kafka schema-registries delete + (SCHEMA_REGISTRY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) 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 alpha 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 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/describe b/gcloud/alpha/managed-kafka/schema-registries/describe new file mode 100644 index 000000000..8f95eaa1f --- /dev/null +++ b/gcloud/alpha/managed-kafka/schema-registries/describe @@ -0,0 +1,72 @@ +NAME + gcloud alpha managed-kafka schema-registries describe - describe a Managed + Service for Apache Kafka schema registry + +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: + + $ gcloud alpha managed-kafka schema-registries describe \ + myschemaregistry --location=us-central1 + +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. + + 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 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/help b/gcloud/alpha/managed-kafka/schema-registries/help new file mode 100644 index 000000000..675564e91 --- /dev/null +++ b/gcloud/alpha/managed-kafka/schema-registries/help @@ -0,0 +1,37 @@ +NAME + gcloud alpha managed-kafka schema-registries - administer Managed Service + for Apache Kafka schema-registries + +SYNOPSIS + gcloud alpha managed-kafka schema-registries 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: + + create + (ALPHA) Create a Managed Service for Apache Kafka schema registry. + + delete + (ALPHA) Delete a Managed Service for Apache Kafka schema registry. + + describe + (ALPHA) Describe a Managed Service for Apache Kafka schema registry. + + list + (ALPHA) List all Managed Service for Apache Kafka schema registries in + a given location. + +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/list b/gcloud/alpha/managed-kafka/schema-registries/list new file mode 100644 index 000000000..cff539694 --- /dev/null +++ b/gcloud/alpha/managed-kafka/schema-registries/list @@ -0,0 +1,86 @@ +NAME + gcloud alpha managed-kafka schema-registries list - list all Managed + Service for Apache Kafka schema registries in a given location + +SYNOPSIS + gcloud alpha managed-kafka schema-registries list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) 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 list all schema registries in a given location, such as us-central1, run + the following: + + $ gcloud alpha managed-kafka schema-registries list \ + --location=us-central1 + +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 --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 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. + diff --git a/gcloud/alpha/monitoring/snoozes/create b/gcloud/alpha/monitoring/snoozes/create index c3f5cc314..5ba5fe293 100644 --- a/gcloud/alpha/monitoring/snoozes/create +++ b/gcloud/alpha/monitoring/snoozes/create @@ -50,15 +50,20 @@ FLAGS in the --snooze-from-file flags if specified. --criteria-filter=CRITERIA_FILTER - The filter that the Snooze applies to, which is a string to match on - Alert fields when silencing the alerts. It follows the standard - https://google.aip.dev/160 syntax. Filters can be defined for snoozes - that apply to one alerting policy. Filters must be a string formatted - as one or more resource labels with specific label values. If - multiple resource labels are used, then they must be connected with - an AND operator. For example: + Optional. When you define a Snooze, you can also define a filter for + that snooze. The filter is a string containing one or more key-value + pairs. The string uses the standard https://google.aip.dev/160 filter + syntax. If you define a filter for a snooze, then the snooze can only + apply to one alert policy. When the snooze is active, incidents won't + be created when the incident would have key-value pairs (labels) that + match those specified by the filter in the snooze. Snooze filters + support resource, metric, and metadata labels. If multiple labels are + used, then they must be connected with an AND operator. For example: resource.labels.instance_id="1234567890" AND - resource.labels.zone="us-central1-a" + resource.labels.zone="us-central1-a" AND + metric.labels.instance_name="test_group" AND + metadata.user_labels.foo="bar" AND + metadata.system_labels.region="us-central1" --criteria-policies=CRITERIA_POLICIES,[...] The policies that the Snooze applies to. Exactly 1 alert policy is diff --git a/gcloud/alpha/netapp/volumes/replications/create b/gcloud/alpha/netapp/volumes/replications/create index 841f01df5..386e94df2 100644 --- a/gcloud/alpha/netapp/volumes/replications/create +++ b/gcloud/alpha/netapp/volumes/replications/create @@ -65,7 +65,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --destination-volume-parameters=[description=DESCRIPTION],[share_name=SHARE_NAME],[storage_pool=STORAGE_POOL],[tiering_policy=TIERING_POLICY],[volume_id=VOLUME_ID] - Required, Sets destination_volume_parameters value. + Required, sets destination_volume_parameters value. description Sets description value. @@ -74,7 +74,7 @@ REQUIRED FLAGS Sets share_name value. storage_pool - Required, Sets storage_pool value. + Required, sets storage_pool value. tiering_policy Sets tiering_policy value. diff --git a/gcloud/alpha/network-security/intercept-deployment-groups/create b/gcloud/alpha/network-security/intercept-deployment-groups/create index 14e7b1a68..7a9668eef 100644 --- a/gcloud/alpha/network-security/intercept-deployment-groups/create +++ b/gcloud/alpha/network-security/intercept-deployment-groups/create @@ -130,7 +130,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 network-security intercept-deployment-groups create $ gcloud beta network-security intercept-deployment-groups create diff --git a/gcloud/alpha/network-security/intercept-deployment-groups/delete b/gcloud/alpha/network-security/intercept-deployment-groups/delete index 26dc9acde..cd0da25f2 100644 --- a/gcloud/alpha/network-security/intercept-deployment-groups/delete +++ b/gcloud/alpha/network-security/intercept-deployment-groups/delete @@ -84,7 +84,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 network-security intercept-deployment-groups delete $ gcloud beta network-security intercept-deployment-groups delete diff --git a/gcloud/alpha/network-security/intercept-deployment-groups/describe b/gcloud/alpha/network-security/intercept-deployment-groups/describe index 06392ef37..28542fa23 100644 --- a/gcloud/alpha/network-security/intercept-deployment-groups/describe +++ b/gcloud/alpha/network-security/intercept-deployment-groups/describe @@ -70,7 +70,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 network-security intercept-deployment-groups describe $ gcloud beta network-security intercept-deployment-groups describe diff --git a/gcloud/alpha/network-security/intercept-deployment-groups/help b/gcloud/alpha/network-security/intercept-deployment-groups/help index ebe2b1085..3529f8aef 100644 --- a/gcloud/alpha/network-security/intercept-deployment-groups/help +++ b/gcloud/alpha/network-security/intercept-deployment-groups/help @@ -40,7 +40,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 network-security intercept-deployment-groups $ gcloud beta network-security intercept-deployment-groups diff --git a/gcloud/alpha/network-security/intercept-deployment-groups/list b/gcloud/alpha/network-security/intercept-deployment-groups/list index 17bd42e8b..b70a2f0cc 100644 --- a/gcloud/alpha/network-security/intercept-deployment-groups/list +++ b/gcloud/alpha/network-security/intercept-deployment-groups/list @@ -88,7 +88,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 network-security intercept-deployment-groups list $ gcloud beta network-security intercept-deployment-groups list diff --git a/gcloud/alpha/network-security/intercept-deployment-groups/update b/gcloud/alpha/network-security/intercept-deployment-groups/update index 5a12b773a..9a0b1ee46 100644 --- a/gcloud/alpha/network-security/intercept-deployment-groups/update +++ b/gcloud/alpha/network-security/intercept-deployment-groups/update @@ -131,7 +131,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 network-security intercept-deployment-groups update $ gcloud beta network-security intercept-deployment-groups update diff --git a/gcloud/alpha/network-security/intercept-deployments/create b/gcloud/alpha/network-security/intercept-deployments/create index cbb152e89..31d0d1735 100644 --- a/gcloud/alpha/network-security/intercept-deployments/create +++ b/gcloud/alpha/network-security/intercept-deployments/create @@ -195,7 +195,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 network-security intercept-deployments create $ gcloud beta network-security intercept-deployments create diff --git a/gcloud/alpha/network-security/intercept-deployments/delete b/gcloud/alpha/network-security/intercept-deployments/delete index 0e42642bb..b330448f2 100644 --- a/gcloud/alpha/network-security/intercept-deployments/delete +++ b/gcloud/alpha/network-security/intercept-deployments/delete @@ -76,7 +76,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 network-security intercept-deployments delete $ gcloud beta network-security intercept-deployments delete diff --git a/gcloud/alpha/network-security/intercept-deployments/describe b/gcloud/alpha/network-security/intercept-deployments/describe index 212222baf..29ce44707 100644 --- a/gcloud/alpha/network-security/intercept-deployments/describe +++ b/gcloud/alpha/network-security/intercept-deployments/describe @@ -68,7 +68,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 network-security intercept-deployments describe $ gcloud beta network-security intercept-deployments describe diff --git a/gcloud/alpha/network-security/intercept-deployments/help b/gcloud/alpha/network-security/intercept-deployments/help index ac6ee28b9..db602f099 100644 --- a/gcloud/alpha/network-security/intercept-deployments/help +++ b/gcloud/alpha/network-security/intercept-deployments/help @@ -37,7 +37,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 network-security intercept-deployments $ gcloud beta network-security intercept-deployments diff --git a/gcloud/alpha/network-security/intercept-deployments/list b/gcloud/alpha/network-security/intercept-deployments/list index 6b3f3e153..ca6b3aace 100644 --- a/gcloud/alpha/network-security/intercept-deployments/list +++ b/gcloud/alpha/network-security/intercept-deployments/list @@ -89,7 +89,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 network-security intercept-deployments list $ gcloud beta network-security intercept-deployments list diff --git a/gcloud/alpha/network-security/intercept-deployments/update b/gcloud/alpha/network-security/intercept-deployments/update index 9b1402b95..45f96e7b1 100644 --- a/gcloud/alpha/network-security/intercept-deployments/update +++ b/gcloud/alpha/network-security/intercept-deployments/update @@ -129,7 +129,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 network-security intercept-deployments update $ gcloud beta network-security intercept-deployments update diff --git a/gcloud/alpha/network-security/intercept-endpoint-group-associations/create b/gcloud/alpha/network-security/intercept-endpoint-group-associations/create index a05c1aed0..af4eafccb 100644 --- a/gcloud/alpha/network-security/intercept-endpoint-group-associations/create +++ b/gcloud/alpha/network-security/intercept-endpoint-group-associations/create @@ -165,7 +165,10 @@ 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 network-security intercept-endpoint-group-associations \ + create $ gcloud beta network-security \ intercept-endpoint-group-associations create diff --git a/gcloud/alpha/network-security/intercept-endpoint-group-associations/delete b/gcloud/alpha/network-security/intercept-endpoint-group-associations/delete index 451738974..357d17cf4 100644 --- a/gcloud/alpha/network-security/intercept-endpoint-group-associations/delete +++ b/gcloud/alpha/network-security/intercept-endpoint-group-associations/delete @@ -84,7 +84,10 @@ 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 network-security intercept-endpoint-group-associations \ + delete $ gcloud beta network-security \ intercept-endpoint-group-associations delete diff --git a/gcloud/alpha/network-security/intercept-endpoint-group-associations/describe b/gcloud/alpha/network-security/intercept-endpoint-group-associations/describe index 02788d6cd..555f7747a 100644 --- a/gcloud/alpha/network-security/intercept-endpoint-group-associations/describe +++ b/gcloud/alpha/network-security/intercept-endpoint-group-associations/describe @@ -70,7 +70,10 @@ 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 network-security intercept-endpoint-group-associations \ + describe $ gcloud beta network-security \ intercept-endpoint-group-associations describe diff --git a/gcloud/alpha/network-security/intercept-endpoint-group-associations/help b/gcloud/alpha/network-security/intercept-endpoint-group-associations/help index daa35f2cd..99ea36937 100644 --- a/gcloud/alpha/network-security/intercept-endpoint-group-associations/help +++ b/gcloud/alpha/network-security/intercept-endpoint-group-associations/help @@ -37,7 +37,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 network-security intercept-endpoint-group-associations $ gcloud beta network-security intercept-endpoint-group-associations diff --git a/gcloud/alpha/network-security/intercept-endpoint-group-associations/list b/gcloud/alpha/network-security/intercept-endpoint-group-associations/list index 0584ec030..deae06be9 100644 --- a/gcloud/alpha/network-security/intercept-endpoint-group-associations/list +++ b/gcloud/alpha/network-security/intercept-endpoint-group-associations/list @@ -94,7 +94,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 network-security intercept-endpoint-group-associations list $ gcloud beta network-security \ intercept-endpoint-group-associations list diff --git a/gcloud/alpha/network-security/intercept-endpoint-group-associations/update b/gcloud/alpha/network-security/intercept-endpoint-group-associations/update index 1b129b2db..1c13532bf 100644 --- a/gcloud/alpha/network-security/intercept-endpoint-group-associations/update +++ b/gcloud/alpha/network-security/intercept-endpoint-group-associations/update @@ -120,7 +120,10 @@ 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 network-security intercept-endpoint-group-associations \ + update $ gcloud beta network-security \ intercept-endpoint-group-associations update diff --git a/gcloud/alpha/network-security/intercept-endpoint-groups/create b/gcloud/alpha/network-security/intercept-endpoint-groups/create index fc21c2c9c..42e174dc9 100644 --- a/gcloud/alpha/network-security/intercept-endpoint-groups/create +++ b/gcloud/alpha/network-security/intercept-endpoint-groups/create @@ -152,7 +152,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 network-security intercept-endpoint-groups create $ gcloud beta network-security intercept-endpoint-groups create diff --git a/gcloud/alpha/network-security/intercept-endpoint-groups/delete b/gcloud/alpha/network-security/intercept-endpoint-groups/delete index f1f4843de..7b0d4ea4c 100644 --- a/gcloud/alpha/network-security/intercept-endpoint-groups/delete +++ b/gcloud/alpha/network-security/intercept-endpoint-groups/delete @@ -82,7 +82,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud network-security intercept-endpoint-groups delete $ gcloud beta network-security intercept-endpoint-groups delete diff --git a/gcloud/alpha/network-security/intercept-endpoint-groups/describe b/gcloud/alpha/network-security/intercept-endpoint-groups/describe index 1540a6c81..1b8283826 100644 --- a/gcloud/alpha/network-security/intercept-endpoint-groups/describe +++ b/gcloud/alpha/network-security/intercept-endpoint-groups/describe @@ -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 network-security intercept-endpoint-groups describe $ gcloud beta network-security intercept-endpoint-groups describe diff --git a/gcloud/alpha/network-security/intercept-endpoint-groups/help b/gcloud/alpha/network-security/intercept-endpoint-groups/help index 0045d108f..791339928 100644 --- a/gcloud/alpha/network-security/intercept-endpoint-groups/help +++ b/gcloud/alpha/network-security/intercept-endpoint-groups/help @@ -37,7 +37,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 network-security intercept-endpoint-groups $ gcloud beta network-security intercept-endpoint-groups diff --git a/gcloud/alpha/network-security/intercept-endpoint-groups/list b/gcloud/alpha/network-security/intercept-endpoint-groups/list index 293e2f29c..ae64708e0 100644 --- a/gcloud/alpha/network-security/intercept-endpoint-groups/list +++ b/gcloud/alpha/network-security/intercept-endpoint-groups/list @@ -96,7 +96,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 network-security intercept-endpoint-groups list $ gcloud beta network-security intercept-endpoint-groups list diff --git a/gcloud/alpha/network-security/intercept-endpoint-groups/update b/gcloud/alpha/network-security/intercept-endpoint-groups/update index 217d1ed93..dfd647d54 100644 --- a/gcloud/alpha/network-security/intercept-endpoint-groups/update +++ b/gcloud/alpha/network-security/intercept-endpoint-groups/update @@ -131,7 +131,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 network-security intercept-endpoint-groups update $ gcloud beta network-security intercept-endpoint-groups update diff --git a/gcloud/alpha/network-security/security-profile-groups/create b/gcloud/alpha/network-security/security-profile-groups/create index 204a241e5..84a6a5ff7 100644 --- a/gcloud/alpha/network-security/security-profile-groups/create +++ b/gcloud/alpha/network-security/security-profile-groups/create @@ -70,7 +70,7 @@ REQUIRED FLAGS ID of the Security Profile or fully qualified identifier for the Security Profile. - To set the custom-intercept-profile-profile attribute: + To set the name attribute: ▫ provide the argument --custom-intercept-profile on the command line. @@ -81,7 +81,7 @@ REQUIRED FLAGS Location of the Security Profile. NOTE: Only global security profiles are supported. - To set the custom-intercept-profile-location attribute: + To set the location attribute: ▫ provide the argument --custom-intercept-profile on the command line with a fully specified name; ▫ provide the argument --custom-intercept-profile-location on the @@ -94,7 +94,7 @@ REQUIRED FLAGS --custom-intercept-profile-organization=CUSTOM_INTERCEPT_PROFILE_ORGANIZATION Organization ID of the Security Profile. - To set the custom-intercept-profile-organization attribute: + To set the organization attribute: ▫ provide the argument --custom-intercept-profile on the command line with a fully specified name; ▫ provide the argument --custom-intercept-profile-organization on @@ -112,7 +112,7 @@ REQUIRED FLAGS ID of the Security Profile or fully qualified identifier for the Security Profile. - To set the custom-mirroring-profile-profile attribute: + To set the name attribute: ▫ provide the argument --custom-mirroring-profile on the command line. @@ -123,7 +123,7 @@ REQUIRED FLAGS Location of the Security Profile. NOTE: Only global security profiles are supported. - To set the custom-mirroring-profile-location attribute: + To set the location attribute: ▫ provide the argument --custom-mirroring-profile on the command line with a fully specified name; ▫ provide the argument --custom-mirroring-profile-location on the @@ -136,7 +136,7 @@ REQUIRED FLAGS --custom-mirroring-profile-organization=CUSTOM_MIRRORING_PROFILE_ORGANIZATION Organization ID of the Security Profile. - To set the custom-mirroring-profile-organization attribute: + To set the organization attribute: ▫ provide the argument --custom-mirroring-profile on the command line with a fully specified name; ▫ provide the argument --custom-mirroring-profile-organization on @@ -154,7 +154,7 @@ REQUIRED FLAGS ID of the Security Profile or fully qualified identifier for the Security Profile. - To set the threat-prevention-profile-profile attribute: + To set the name attribute: ▫ provide the argument --threat-prevention-profile on the command line. @@ -165,7 +165,7 @@ REQUIRED FLAGS Location of the Security Profile. NOTE: Only global security profiles are supported. - To set the threat-prevention-profile-location attribute: + To set the location attribute: ▫ provide the argument --threat-prevention-profile on the command line with a fully specified name; ▫ provide the argument --threat-prevention-profile-location on @@ -180,7 +180,7 @@ REQUIRED FLAGS --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION Organization ID of the Security Profile. - To set the threat-prevention-profile-organization attribute: + To set the organization attribute: ▫ provide the argument --threat-prevention-profile on the command line with a fully specified name; ▫ provide the argument --threat-prevention-profile-organization @@ -200,7 +200,7 @@ REQUIRED FLAGS ID of the Security Profile or fully qualified identifier for the Security Profile. - To set the url-filtering-profile-profile attribute: + To set the name attribute: ▫ provide the argument --url-filtering-profile on the command line. @@ -211,7 +211,7 @@ REQUIRED FLAGS Location of the Security Profile. NOTE: Only global security profiles are supported. - To set the url-filtering-profile-location attribute: + To set the location attribute: ▫ provide the argument --url-filtering-profile on the command line with a fully specified name; ▫ provide the argument --url-filtering-profile-location on the @@ -224,7 +224,7 @@ REQUIRED FLAGS --url-filtering-profile-organization=URL_FILTERING_PROFILE_ORGANIZATION Organization ID of the Security Profile. - To set the url-filtering-profile-organization attribute: + To set the organization attribute: ▫ provide the argument --url-filtering-profile on the command line with a fully specified name; ▫ provide the argument --url-filtering-profile-organization on diff --git a/gcloud/alpha/network-security/security-profile-groups/update b/gcloud/alpha/network-security/security-profile-groups/update index 50c1a362c..243f6847c 100644 --- a/gcloud/alpha/network-security/security-profile-groups/update +++ b/gcloud/alpha/network-security/security-profile-groups/update @@ -115,7 +115,7 @@ FLAGS ID of the Security Profile or fully qualified identifier for the Security Profile. - To set the threat-prevention-profile-profile attribute: + To set the name attribute: ▫ provide the argument --threat-prevention-profile on the command line. @@ -126,7 +126,7 @@ FLAGS Location of the Security Profile. NOTE: Only global security profiles are supported. - To set the threat-prevention-profile-location attribute: + To set the location attribute: ▫ provide the argument --threat-prevention-profile on the command line with a fully specified name; ▫ provide the argument --threat-prevention-profile-location on @@ -141,7 +141,7 @@ FLAGS --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION Organization ID of the Security Profile. - To set the threat-prevention-profile-organization attribute: + To set the organization attribute: ▫ provide the argument --threat-prevention-profile on the command line with a fully specified name; ▫ provide the argument --threat-prevention-profile-organization @@ -166,7 +166,7 @@ FLAGS ID of the Security Profile or fully qualified identifier for the Security Profile. - To set the url-filtering-profile-profile attribute: + To set the name attribute: ▫ provide the argument --url-filtering-profile on the command line. @@ -177,7 +177,7 @@ FLAGS Location of the Security Profile. NOTE: Only global security profiles are supported. - To set the url-filtering-profile-location attribute: + To set the location attribute: ▫ provide the argument --url-filtering-profile on the command line with a fully specified name; ▫ provide the argument --url-filtering-profile-location on the @@ -190,7 +190,7 @@ FLAGS --url-filtering-profile-organization=URL_FILTERING_PROFILE_ORGANIZATION Organization ID of the Security Profile. - To set the url-filtering-profile-organization attribute: + To set the organization attribute: ▫ provide the argument --url-filtering-profile on the command line with a fully specified name; ▫ provide the argument --url-filtering-profile-organization on diff --git a/gcloud/alpha/network-security/security-profiles/custom-intercept/create b/gcloud/alpha/network-security/security-profiles/custom-intercept/create index 805511307..ff383a842 100644 --- a/gcloud/alpha/network-security/security-profiles/custom-intercept/create +++ b/gcloud/alpha/network-security/security-profiles/custom-intercept/create @@ -120,7 +120,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 network-security security-profiles custom-intercept create $ gcloud beta network-security security-profiles custom-intercept \ create diff --git a/gcloud/alpha/network-security/security-profiles/custom-intercept/delete b/gcloud/alpha/network-security/security-profiles/custom-intercept/delete index 52ec75c26..613319348 100644 --- a/gcloud/alpha/network-security/security-profiles/custom-intercept/delete +++ b/gcloud/alpha/network-security/security-profiles/custom-intercept/delete @@ -71,7 +71,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 network-security security-profiles custom-intercept delete $ gcloud beta network-security security-profiles custom-intercept \ delete diff --git a/gcloud/alpha/network-security/security-profiles/custom-intercept/describe b/gcloud/alpha/network-security/security-profiles/custom-intercept/describe index 10d64354b..116307b1c 100644 --- a/gcloud/alpha/network-security/security-profiles/custom-intercept/describe +++ b/gcloud/alpha/network-security/security-profiles/custom-intercept/describe @@ -66,7 +66,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 network-security security-profiles custom-intercept describe $ gcloud beta network-security security-profiles custom-intercept \ describe diff --git a/gcloud/alpha/network-security/security-profiles/custom-intercept/help b/gcloud/alpha/network-security/security-profiles/custom-intercept/help index 20c877c32..b7329b48c 100644 --- a/gcloud/alpha/network-security/security-profiles/custom-intercept/help +++ b/gcloud/alpha/network-security/security-profiles/custom-intercept/help @@ -37,7 +37,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 network-security security-profiles custom-intercept $ gcloud beta network-security security-profiles custom-intercept diff --git a/gcloud/alpha/network-security/security-profiles/custom-intercept/list b/gcloud/alpha/network-security/security-profiles/custom-intercept/list index 3194e6a18..10627d6cb 100644 --- a/gcloud/alpha/network-security/security-profiles/custom-intercept/list +++ b/gcloud/alpha/network-security/security-profiles/custom-intercept/list @@ -83,7 +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. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud network-security security-profiles custom-intercept list $ gcloud beta network-security security-profiles custom-intercept \ list diff --git a/gcloud/alpha/network-security/security-profiles/custom-intercept/update b/gcloud/alpha/network-security/security-profiles/custom-intercept/update index 1d833dbfe..911760006 100644 --- a/gcloud/alpha/network-security/security-profiles/custom-intercept/update +++ b/gcloud/alpha/network-security/security-profiles/custom-intercept/update @@ -112,7 +112,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 network-security security-profiles custom-intercept update $ gcloud beta network-security security-profiles custom-intercept \ update diff --git a/gcloud/alpha/run/worker-pools/describe b/gcloud/alpha/run/worker-pools/describe index 42dd0b416..f9c2a88bf 100644 --- a/gcloud/alpha/run/worker-pools/describe +++ b/gcloud/alpha/run/worker-pools/describe @@ -3,7 +3,7 @@ NAME worker-pool SYNOPSIS - gcloud alpha run worker-pools describe (WORKER_POOL : --region=REGION) + gcloud alpha run worker-pools describe WORKER_POOL [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -26,10 +26,9 @@ EXAMPLES --format=export POSITIONAL ARGUMENTS - WorkerPool resource - WorkerPool 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. + WorkerPool resource - WorkerPool to describe. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: ◆ provide the argument WORKER_POOL on the command line with a fully @@ -46,18 +45,10 @@ POSITIONAL ARGUMENTS To set the worker-pool attribute: ▸ provide the argument WORKER_POOL on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The Cloud region for the WorkerPool. Overrides the default run/region - property value for this command invocation. - - To set the region attribute: - ▸ provide the argument WORKER_POOL on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property run/region. +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/scc/findings/bulk-mute b/gcloud/alpha/scc/findings/bulk-mute index 8389c8c5b..2abfdef3c 100644 --- a/gcloud/alpha/scc/findings/bulk-mute +++ b/gcloud/alpha/scc/findings/bulk-mute @@ -62,11 +62,14 @@ OPTIONAL FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --mute-state=MUTE_STATE; default="muted" Desired mute state of the finding. MUTE_STATE must be one of: muted, diff --git a/gcloud/alpha/scc/findings/create b/gcloud/alpha/scc/findings/create index 1765232ef..4af2e5674 100644 --- a/gcloud/alpha/scc/findings/create +++ b/gcloud/alpha/scc/findings/create @@ -116,11 +116,14 @@ OPTIONAL FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --source-properties=[KEY=VALUE,...] Source specific properties. These properties are managed by the source diff --git a/gcloud/alpha/scc/findings/group b/gcloud/alpha/scc/findings/group index 6dac6fcd1..eb638bf61 100644 --- a/gcloud/alpha/scc/findings/group +++ b/gcloud/alpha/scc/findings/group @@ -131,11 +131,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --page-size=PAGE_SIZE Maximum number of results to return in a single response. Default is diff --git a/gcloud/alpha/scc/findings/list b/gcloud/alpha/scc/findings/list index f56be80fc..687950a8d 100644 --- a/gcloud/alpha/scc/findings/list +++ b/gcloud/alpha/scc/findings/list @@ -131,11 +131,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --order-by=ORDER_BY Expression that defines what fields and order to use for sorting. diff --git a/gcloud/alpha/scc/findings/list-marks b/gcloud/alpha/scc/findings/list-marks index 0878337f7..b6f6e7b20 100644 --- a/gcloud/alpha/scc/findings/list-marks +++ b/gcloud/alpha/scc/findings/list-marks @@ -46,11 +46,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --page-token=PAGE_TOKEN Response objects will return a non-null value for page-token to diff --git a/gcloud/alpha/scc/findings/set-mute b/gcloud/alpha/scc/findings/set-mute index d9832476b..cc697f65b 100644 --- a/gcloud/alpha/scc/findings/set-mute +++ b/gcloud/alpha/scc/findings/set-mute @@ -58,11 +58,14 @@ OPTIONAL FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --source=SOURCE ID of the source. diff --git a/gcloud/alpha/scc/findings/update b/gcloud/alpha/scc/findings/update index b87cb1e82..38f589cb9 100644 --- a/gcloud/alpha/scc/findings/update +++ b/gcloud/alpha/scc/findings/update @@ -72,11 +72,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --source=SOURCE; default="-" Source id. Defaults to all sources. diff --git a/gcloud/alpha/scc/findings/update-marks b/gcloud/alpha/scc/findings/update-marks index 80e1e0402..429879e41 100644 --- a/gcloud/alpha/scc/findings/update-marks +++ b/gcloud/alpha/scc/findings/update-marks @@ -63,11 +63,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --security-marks=[KEY=VALUE,...] SecurityMarks resource to be passed as the request body. It's a diff --git a/gcloud/alpha/scc/muteconfigs/create b/gcloud/alpha/scc/muteconfigs/create index 07eea672c..5ae17f3d8 100644 --- a/gcloud/alpha/scc/muteconfigs/create +++ b/gcloud/alpha/scc/muteconfigs/create @@ -64,11 +64,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --type=TYPE; default="static" The mute configuration type. Immutable after creation. TYPE must be one diff --git a/gcloud/alpha/scc/muteconfigs/delete b/gcloud/alpha/scc/muteconfigs/delete index ec45401c7..f454ae80b 100644 --- a/gcloud/alpha/scc/muteconfigs/delete +++ b/gcloud/alpha/scc/muteconfigs/delete @@ -42,11 +42,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. At most one of these can be specified: diff --git a/gcloud/alpha/scc/muteconfigs/get b/gcloud/alpha/scc/muteconfigs/get index 3a595131b..52e5a9875 100644 --- a/gcloud/alpha/scc/muteconfigs/get +++ b/gcloud/alpha/scc/muteconfigs/get @@ -41,11 +41,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. At most one of these can be specified: diff --git a/gcloud/alpha/scc/muteconfigs/list b/gcloud/alpha/scc/muteconfigs/list index dbdb0c2d5..bceb69690 100644 --- a/gcloud/alpha/scc/muteconfigs/list +++ b/gcloud/alpha/scc/muteconfigs/list @@ -50,11 +50,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/scc/muteconfigs/update b/gcloud/alpha/scc/muteconfigs/update index 49caf14c4..f47346251 100644 --- a/gcloud/alpha/scc/muteconfigs/update +++ b/gcloud/alpha/scc/muteconfigs/update @@ -64,11 +64,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --update-mask=UPDATE_MASK Optional: If left unspecified (default), an update-mask is diff --git a/gcloud/alpha/spanner/instance-partitions/delete b/gcloud/alpha/spanner/instance-partitions/delete index e9a96d4e1..d1e4fbbf8 100644 --- a/gcloud/alpha/spanner/instance-partitions/delete +++ b/gcloud/alpha/spanner/instance-partitions/delete @@ -1,13 +1,15 @@ NAME gcloud alpha spanner instance-partitions delete - delete a Spanner instance - partition + partition. You can't delete the default instance partition using this + command SYNOPSIS gcloud alpha spanner instance-partitions delete (INSTANCE_PARTITION : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete a Spanner instance partition. + (ALPHA) Delete a Spanner instance partition. You can't delete the default + instance partition using this command. EXAMPLES To delete a Spanner instance partition, run: diff --git a/gcloud/alpha/spanner/instance-partitions/describe b/gcloud/alpha/spanner/instance-partitions/describe index 8eb855627..d3d69f9e4 100644 --- a/gcloud/alpha/spanner/instance-partitions/describe +++ b/gcloud/alpha/spanner/instance-partitions/describe @@ -1,16 +1,16 @@ NAME - gcloud alpha spanner instance-partitions describe - describe a Cloud - Spanner instance partition + gcloud alpha spanner instance-partitions describe - describe a Spanner + instance partition SYNOPSIS gcloud alpha spanner instance-partitions describe (INSTANCE_PARTITION : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe a Cloud Spanner instance partition. + (ALPHA) Describe a Spanner instance partition. EXAMPLES - To describe a Cloud Spanner instance partition, run: + To describe a Spanner instance partition, run: $ gcloud alpha spanner instance-partitions describe \ my-instance-partition-id --instance=my-instance-id @@ -60,7 +60,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 spanner instance-partitions describe $ gcloud beta spanner instance-partitions describe diff --git a/gcloud/alpha/spanner/instance-partitions/help b/gcloud/alpha/spanner/instance-partitions/help index be7ad3414..06d0d8af7 100644 --- a/gcloud/alpha/spanner/instance-partitions/help +++ b/gcloud/alpha/spanner/instance-partitions/help @@ -20,17 +20,19 @@ COMMANDS (ALPHA) Create a Spanner instance partition. delete - (ALPHA) Delete a Spanner instance partition. + (ALPHA) Delete a Spanner instance partition. You can't delete the + default instance partition using this command. describe - (ALPHA) Describe a Cloud Spanner instance partition. + (ALPHA) Describe a Spanner instance partition. list - (ALPHA) List the Cloud Spanner instance partitions contained within the - given instance. + (ALPHA) List the Spanner instance partitions contained within the given + instance. update - (ALPHA) Update a Cloud Spanner instance partition. + (ALPHA) Update a Spanner instance partition. You can't update the + default instance partition using this command. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/spanner/instance-partitions/list b/gcloud/alpha/spanner/instance-partitions/list index 93db0533a..0fad4bc0d 100644 --- a/gcloud/alpha/spanner/instance-partitions/list +++ b/gcloud/alpha/spanner/instance-partitions/list @@ -1,6 +1,6 @@ NAME - gcloud alpha spanner instance-partitions list - list the Cloud Spanner - instance partitions contained within the given instance + gcloud alpha spanner instance-partitions list - list the Spanner instance + partitions contained within the given instance SYNOPSIS gcloud alpha spanner instance-partitions list [--instance=INSTANCE] @@ -8,11 +8,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List the Cloud Spanner instance partitions contained within the - given instance. + (ALPHA) List the Spanner instance partitions contained within the given + instance. EXAMPLES - To list all Cloud Spanner instances partitions in an instance, run: + To list all Spanner instances partitions in an instance, run: $ gcloud alpha spanner instance-partitions list \ --instance=my-instance-id @@ -73,7 +73,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud spanner instance-partitions list $ gcloud beta spanner instance-partitions list diff --git a/gcloud/alpha/spanner/instance-partitions/update b/gcloud/alpha/spanner/instance-partitions/update index a23ef52b2..a02aafac4 100644 --- a/gcloud/alpha/spanner/instance-partitions/update +++ b/gcloud/alpha/spanner/instance-partitions/update @@ -1,6 +1,7 @@ NAME - gcloud alpha spanner instance-partitions update - update a Cloud Spanner - instance partition + gcloud alpha spanner instance-partitions update - update a Spanner instance + partition. You can't update the default instance partition using this + command SYNOPSIS gcloud alpha spanner instance-partitions update @@ -10,16 +11,17 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Update a Cloud Spanner instance partition. + (ALPHA) Update a Spanner instance partition. You can't update the default + instance partition using this command. EXAMPLES - To update the display name of a Cloud Spanner instance partition, run: + To update the display name of a Spanner instance partition, run: $ gcloud alpha spanner instance-partitions update \ my-instance-partition-id --instance=my-instance-id \ --description=my-new-display-name - To update the node count of a Cloud Spanner instance partition, run: + To update the node count of a Spanner instance partition, run: $ gcloud alpha spanner instance-partitions update \ my-instance-partition-id --instance=my-instance-id --nodes=1 @@ -85,7 +87,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 spanner instance-partitions update $ gcloud beta spanner instance-partitions update diff --git a/gcloud/alpha/spanner/instances/move b/gcloud/alpha/spanner/instances/move index 3d22ff640..fe6d443fe 100644 --- a/gcloud/alpha/spanner/instances/move +++ b/gcloud/alpha/spanner/instances/move @@ -42,7 +42,7 @@ OPTIONAL FLAGS KMS keys. Sets target_database_move_configs value. database-id - Required, Sets database-id value. + Required, sets database-id value. kms-key-names Sets kms-key-names value. diff --git a/gcloud/alpha/spanner/operations/cancel b/gcloud/alpha/spanner/operations/cancel index 710cff988..ac7ecf1d4 100644 --- a/gcloud/alpha/spanner/operations/cancel +++ b/gcloud/alpha/spanner/operations/cancel @@ -26,8 +26,7 @@ EXAMPLES $ gcloud alpha spanner operations cancel _auto_12345 \ --instance=my-instance-id --backup=my-backup-id - To cancel a Cloud Spanner instance partition operation with ID auto_12345, - run: + To cancel an instance partition operation with ID auto_12345, run: $ gcloud alpha spanner operations cancel auto_12345 \ --instance=my-instance-id --instance-partition=my-partition-id @@ -55,7 +54,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/spanner/operations/list b/gcloud/alpha/spanner/operations/list index 757fe40f1..1dc0c1c25 100644 --- a/gcloud/alpha/spanner/operations/list +++ b/gcloud/alpha/spanner/operations/list @@ -43,13 +43,13 @@ EXAMPLES $ gcloud alpha spanner operations list --instance=my-instance-id \ --backup=my-backup-id --type=BACKUP - To list Cloud Spanner instance partition operations for an instance - partition, run: + To list instance partition operations for an instance partition, run: $ gcloud alpha spanner operations list --instance=my-instance-id \ --instance-partition=my-partition-id --type=INSTANCE_PARTITION - To list Cloud Spanner instance partition operations for an instance, run: + To list instance partition operations for all instance partitions belonging + to this instance, run: $ gcloud alpha spanner operations list --instance=my-instance-id \ --type=INSTANCE_PARTITION diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index 05742f0e6..f61af1767 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -439,7 +439,7 @@ FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project Sets project value. diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index e83c096ca..18a50682f 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -616,7 +616,7 @@ FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project Sets project value. diff --git a/gcloud/alpha/workstations/clusters/create b/gcloud/alpha/workstations/clusters/create index 04e9ee745..511313764 100644 --- a/gcloud/alpha/workstations/clusters/create +++ b/gcloud/alpha/workstations/clusters/create @@ -5,7 +5,8 @@ SYNOPSIS gcloud alpha workstations clusters create (CLUSTER : --region=REGION) [--async] [--domain=DOMAIN] [--enable-private-endpoint] [--labels=[KEY=VALUE,...]] [--network=NETWORK] - [--subnetwork=SUBNETWORK] [GCLOUD_WIDE_FLAG ...] + [--subnetwork=SUBNETWORK] [--tags=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a workstation cluster. @@ -79,6 +80,10 @@ FLAGS --subnetwork=SUBNETWORK Fully specified subnetwork path for instances created in this cluster. + --tags=[KEY=VALUE,...] + Resource manager tags to be bound to this cluster. For example: + "123/environment=production" "123/costCenter=marketing" + 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/workstations/configs/create b/gcloud/alpha/workstations/configs/create index 33235dec2..7bb336de7 100644 --- a/gcloud/alpha/workstations/configs/create +++ b/gcloud/alpha/workstations/configs/create @@ -131,10 +131,10 @@ FLAGS Sets allowed_ports value. first - Required, Sets first value. + Required, sets first value. last - Required, Sets last value. + Required, sets last value. Shorthand Example: @@ -179,7 +179,7 @@ FLAGS Sets enable-nested-virtualization value. id - Required, Sets id value. + Required, sets id value. machine-type Sets machine-type value. diff --git a/gcloud/alpha/workstations/configs/update b/gcloud/alpha/workstations/configs/update index 0d1714471..cef108d1f 100644 --- a/gcloud/alpha/workstations/configs/update +++ b/gcloud/alpha/workstations/configs/update @@ -112,10 +112,10 @@ FLAGS Sets allowed_ports value. first - Required, Sets first value. + Required, sets first value. last - Required, Sets last value. + Required, sets last value. Shorthand Example: @@ -160,7 +160,7 @@ FLAGS Sets enable-nested-virtualization value. id - Required, Sets id value. + Required, sets id value. machine-type Sets machine-type value. diff --git a/gcloud/artifacts/repositories/list b/gcloud/artifacts/repositories/list index 39530c857..da8c6371f 100644 --- a/gcloud/artifacts/repositories/list +++ b/gcloud/artifacts/repositories/list @@ -18,52 +18,56 @@ EXAMPLES $ gcloud artifacts repositories list --limit=5 - To list repositories with name as `my_repo`: + To list repositories with name as my_repo: $ gcloud artifacts repositories list \ - --filter='name="projects/my-project/locations/us/repositories/my\ + --filter='name="projects/my-project/locations/us/repositories/my\ _repo"' - To list repositories with a given partial name, use `*` to match any character in name: + To list repositories with a given partial name, use * to match any + character in name: $ gcloud artifacts repositories list \ - --filter='name="projects/my-project/locations/us/repositories/*r\ + --filter='name="projects/my-project/locations/us/repositories/*r\ epo"' $ gcloud artifacts repositories list \ - --filter='name="projects/my-project/locations/us/repositories/my\ + --filter='name="projects/my-project/locations/us/repositories/my\ _*"' - To list files that have annotations: + To list files that have annotations: $ gcloud artifacts repositories list --filter=annotations:* - To list repositories with annotations pair as [annotation_key: annotation_value] + To list repositories with annotations pair as [annotation_key: + annotation_value] $ gcloud artifacts repositories list \ - --filter='annotations.annotation_key:annotation_value' + --filter='annotations.annotation_key:annotation_value' - To list repositories with annotations containing key as `my_key`: + To list repositories with annotations containing key as my_key: $ gcloud artifacts repositories list --filter='annotations.my_key' - If the key or value contains special characters, such as `my.key` or `my.value`, backtick("`") is required: + If the key or value contains special characters, such as my.key or + my.value, backtick("") is required: $ gcloud artifacts repositories list --filter='annotations.`my.key`' $ gcloud artifacts repositories list \ - --filter='annotations.`my.key`:`my.value`' + --filter='annotations.`my.key`:`my.value`' - To list repositories with given partial annotation key or value, use `*` to match any character: + To list repositories with given partial annotation key or value, use * to + match any character: $ gcloud artifacts repositories list \ - --filter='annotations.*key:`*.value`' + --filter='annotations.*key:`*.value`' - To list repositories ordered by create_time: + To list repositories ordered by create_time: $ gcloud artifacts repositories list --sort-by=create_time - To list repositories ordered by update_time reversely: + To list repositories ordered by update_time reversely: $ gcloud artifacts repositories list--sort-by=~update_time diff --git a/gcloud/backup-dr/backups/update b/gcloud/backup-dr/backups/update index 6904a38a4..f84838c2e 100644 --- a/gcloud/backup-dr/backups/update +++ b/gcloud/backup-dr/backups/update @@ -21,15 +21,6 @@ EXAMPLES --project=sample-project --location=us-central1 \ --enforced-retention-end-time="2025-02-14T01:10:20Z" - To update the expire time of a backup sample-backup in backup vault - sample-vault, data source sample-ds, project sample-project and location - us-central1, run: - - $ gcloud backup-dr backups update sample-backup \ - --backup-vault=sample-vault --data-source=sample-ds \ - --project=sample-project --location=us-central1 \ - --expire-time="2025-02-14T01:10:20Z" - POSITIONAL ARGUMENTS Backup resource - Name of the backup to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some diff --git a/gcloud/beta/ai/endpoints/deploy-model b/gcloud/beta/ai/endpoints/deploy-model index 5d9095ef6..7afe3e2b3 100644 --- a/gcloud/beta/ai/endpoints/deploy-model +++ b/gcloud/beta/ai/endpoints/deploy-model @@ -77,10 +77,10 @@ OPTIONAL FLAGS type The type of the accelerator. Choices are 'nvidia-a100-80gb', - 'nvidia-h100-80gb', 'nvidia-h100-mega-80gb', 'nvidia-h200-141gb', - 'nvidia-l4', 'nvidia-tesla-a100', 'nvidia-tesla-k80', - 'nvidia-tesla-p100', 'nvidia-tesla-p4', 'nvidia-tesla-t4', - 'nvidia-tesla-v100'. + 'nvidia-b200', 'nvidia-h100-80gb', 'nvidia-h100-mega-80gb', + 'nvidia-h200-141gb', 'nvidia-l4', 'nvidia-tesla-a100', + 'nvidia-tesla-k80', 'nvidia-tesla-p100', 'nvidia-tesla-p4', + 'nvidia-tesla-t4', 'nvidia-tesla-v100'. count The number of accelerators to attach to each machine running the diff --git a/gcloud/beta/alloydb/instances/create b/gcloud/beta/alloydb/instances/create index 70abc1017..b67f95a62 100644 --- a/gcloud/beta/alloydb/instances/create +++ b/gcloud/beta/alloydb/instances/create @@ -4,11 +4,11 @@ NAME SYNOPSIS gcloud beta alloydb instances create INSTANCE --cluster=CLUSTER - --cpu-count=CPU_COUNT --instance-type=INSTANCE_TYPE --region=REGION + --instance-type=INSTANCE_TYPE --region=REGION [--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]] [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async] [--authorized-external-networks=[AUTHORIZED_NETWORK,...]] - [--availability-type=AVAILABILITY_TYPE] + [--availability-type=AVAILABILITY_TYPE] [--cpu-count=CPU_COUNT] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] @@ -51,18 +51,6 @@ REQUIRED FLAGS --cluster=CLUSTER AlloyDB cluster ID - --cpu-count=CPU_COUNT - Whole number value indicating how many vCPUs the machine should - contain. If the instance does not have a machine-type, the vCPU count - will be used to determine the machine type where each vCPU corresponds - to an N2 high-mem machine: - (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machine_types). - where CPU_COUNT can be one of: 2, 4, 8, 16, 32, 64, 96, 128. If the - instance has a machine-type, cpu-count must have the same value as the - vCPU count in the machine-type. Eg: if machine-type is - c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, - 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. - --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: @@ -118,6 +106,18 @@ OPTIONAL FLAGS production instances; instance does not automatically fail over to another zone. + --cpu-count=CPU_COUNT + Whole number value indicating how many vCPUs the machine should + contain. If the instance does not have a machine-type, the vCPU count + will be used to determine the machine type where each vCPU corresponds + to an N2 high-mem machine: + (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machine_types). + where CPU_COUNT can be one of: 2, 4, 8, 16, 32, 64, 96, 128. If the + instance has a machine-type, cpu-count must have the same value as the + vCPU count in the machine-type. Eg: if machine-type is + c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, + 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. + --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an equals sign to separate flag name and value. Flags without values, like @@ -204,10 +204,10 @@ OPTIONAL FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project - Required, Sets project value. + Required, sets project value. Shorthand Example: diff --git a/gcloud/beta/alloydb/instances/create-secondary b/gcloud/beta/alloydb/instances/create-secondary index f1b8b79b6..f075e0a47 100644 --- a/gcloud/beta/alloydb/instances/create-secondary +++ b/gcloud/beta/alloydb/instances/create-secondary @@ -97,10 +97,10 @@ OPTIONAL FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project - Required, Sets project value. + Required, sets project value. Shorthand Example: diff --git a/gcloud/beta/alloydb/instances/update b/gcloud/beta/alloydb/instances/update index 345e7082b..51e493534 100644 --- a/gcloud/beta/alloydb/instances/update +++ b/gcloud/beta/alloydb/instances/update @@ -232,10 +232,10 @@ OPTIONAL FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project - Required, Sets project value. + Required, sets project value. Shorthand Example: diff --git a/gcloud/beta/artifacts/repositories/list b/gcloud/beta/artifacts/repositories/list index b8544b01f..4f441f895 100644 --- a/gcloud/beta/artifacts/repositories/list +++ b/gcloud/beta/artifacts/repositories/list @@ -18,54 +18,58 @@ EXAMPLES $ gcloud beta artifacts repositories list --limit=5 - To list repositories with name as `my_repo`: + To list repositories with name as my_repo: $ gcloud beta artifacts repositories list \ - --filter='name="projects/my-project/locations/us/repositories/my\ + --filter='name="projects/my-project/locations/us/repositories/my\ _repo"' - To list repositories with a given partial name, use `*` to match any character in name: + To list repositories with a given partial name, use * to match any + character in name: $ gcloud beta artifacts repositories list \ - --filter='name="projects/my-project/locations/us/repositories/*r\ + --filter='name="projects/my-project/locations/us/repositories/*r\ epo"' $ gcloud beta artifacts repositories list \ - --filter='name="projects/my-project/locations/us/repositories/my\ + --filter='name="projects/my-project/locations/us/repositories/my\ _*"' - To list files that have annotations: + To list files that have annotations: $ gcloud beta artifacts repositories list --filter=annotations:* - To list repositories with annotations pair as [annotation_key: annotation_value] + To list repositories with annotations pair as [annotation_key: + annotation_value] $ gcloud beta artifacts repositories list \ - --filter='annotations.annotation_key:annotation_value' + --filter='annotations.annotation_key:annotation_value' - To list repositories with annotations containing key as `my_key`: + To list repositories with annotations containing key as my_key: $ gcloud beta artifacts repositories list \ - --filter='annotations.my_key' + --filter='annotations.my_key' - If the key or value contains special characters, such as `my.key` or `my.value`, backtick("`") is required: + If the key or value contains special characters, such as my.key or + my.value, backtick("") is required: $ gcloud beta artifacts repositories list \ - --filter='annotations.`my.key`' + --filter='annotations.`my.key`' $ gcloud beta artifacts repositories list \ - --filter='annotations.`my.key`:`my.value`' + --filter='annotations.`my.key`:`my.value`' - To list repositories with given partial annotation key or value, use `*` to match any character: + To list repositories with given partial annotation key or value, use * to + match any character: $ gcloud beta artifacts repositories list \ - --filter='annotations.*key:`*.value`' + --filter='annotations.*key:`*.value`' - To list repositories ordered by create_time: + To list repositories ordered by create_time: $ gcloud beta artifacts repositories list --sort-by=create_time - To list repositories ordered by update_time reversely: + To list repositories ordered by update_time reversely: $ gcloud beta artifacts repositories list--sort-by=~update_time diff --git a/gcloud/beta/bigtable/instances/tables/create b/gcloud/beta/bigtable/instances/tables/create index 2ac95de7c..5b00ebf02 100644 --- a/gcloud/beta/bigtable/instances/tables/create +++ b/gcloud/beta/bigtable/instances/tables/create @@ -9,6 +9,7 @@ SYNOPSIS [--deletion-protection] [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] + [--tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] @@ -159,6 +160,12 @@ OPTIONAL FLAGS Row keys where the table should initially be split. For example: car,key + --tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN + The age at which data should be moved to infrequent access storage. + + See $ gcloud topic datetimes for information on absolute duration + formats. + At most one of these can be specified: --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD diff --git a/gcloud/beta/bigtable/instances/tables/update b/gcloud/beta/bigtable/instances/tables/update index 7c409907c..4060788ac 100644 --- a/gcloud/beta/bigtable/instances/tables/update +++ b/gcloud/beta/bigtable/instances/tables/update @@ -11,6 +11,8 @@ SYNOPSIS | --clear-change-stream-retention-period] [--clear-row-key-schema | --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [--clear-tiered-storage-config + | --tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -162,6 +164,17 @@ FLAGS encoding: raw: {} + At most one of these can be specified: + + --clear-tiered-storage-config + Disables the tiered storage config. + + --tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN + The age at which data should be moved to infrequent access storage. + + See $ gcloud topic datetimes for information on absolute duration + formats. + 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/bigtable/tables/create b/gcloud/beta/bigtable/tables/create index 49dfd2d8e..d5f8917dc 100644 --- a/gcloud/beta/bigtable/tables/create +++ b/gcloud/beta/bigtable/tables/create @@ -8,6 +8,7 @@ SYNOPSIS [--deletion-protection] [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] + [--tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] @@ -158,6 +159,12 @@ OPTIONAL FLAGS Row keys where the table should initially be split. For example: car,key + --tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN + The age at which data should be moved to infrequent access storage. + + See $ gcloud topic datetimes for information on absolute duration + formats. + At most one of these can be specified: --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD diff --git a/gcloud/beta/bigtable/tables/update b/gcloud/beta/bigtable/tables/update index 607deabfe..14be37a6b 100644 --- a/gcloud/beta/bigtable/tables/update +++ b/gcloud/beta/bigtable/tables/update @@ -11,6 +11,8 @@ SYNOPSIS | --clear-change-stream-retention-period] [--clear-row-key-schema | --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [--clear-tiered-storage-config + | --tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -162,6 +164,17 @@ FLAGS encoding: raw: {} + At most one of these can be specified: + + --clear-tiered-storage-config + Disables the tiered storage config. + + --tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN + The age at which data should be moved to infrequent access storage. + + See $ gcloud topic datetimes for information on absolute duration + formats. + 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/composer/environments/storage/dags/delete b/gcloud/beta/composer/environments/storage/dags/delete index c84a225b7..f72dc4b6c 100644 --- a/gcloud/beta/composer/environments/storage/dags/delete +++ b/gcloud/beta/composer/environments/storage/dags/delete @@ -13,7 +13,7 @@ DESCRIPTION EXAMPLES To delete the dags in the path path/to/dags, for the environment named - environmnet-1 in the location us-east1, run: + environment-1 in the location us-east1, run: $ gcloud beta composer environments storage dags delete \ path/to/dags --environment=environment-1 --location=us-east1 diff --git a/gcloud/beta/composer/environments/storage/dags/list b/gcloud/beta/composer/environments/storage/dags/list index 6cd84f44d..ec8318bbf 100644 --- a/gcloud/beta/composer/environments/storage/dags/list +++ b/gcloud/beta/composer/environments/storage/dags/list @@ -11,7 +11,7 @@ DESCRIPTION (BETA) List the DAG files for a Cloud Composer environment. EXAMPLES - To list the dags for the Cloud Composer environment environmnet-1 and + To list the dags for the Cloud Composer environment environment-1 and location us-central1, run: $ gcloud beta composer environments storage dags list \ diff --git a/gcloud/beta/composer/environments/storage/data/delete b/gcloud/beta/composer/environments/storage/data/delete index ed61a937f..9610e2df6 100644 --- a/gcloud/beta/composer/environments/storage/data/delete +++ b/gcloud/beta/composer/environments/storage/data/delete @@ -13,7 +13,7 @@ DESCRIPTION EXAMPLES To delete the data from the path path/to/data, for the environment named - environmnet-1 in the location us-east1, run: + environment-1 in the location us-east1, run: $ gcloud beta composer environments storage data delete \ path/to/data --environment=environment-1 --location=us-east1 diff --git a/gcloud/beta/composer/environments/storage/data/list b/gcloud/beta/composer/environments/storage/data/list index 9f74fda6f..9096fca97 100644 --- a/gcloud/beta/composer/environments/storage/data/list +++ b/gcloud/beta/composer/environments/storage/data/list @@ -11,7 +11,7 @@ DESCRIPTION (BETA) List the data for a Cloud Composer environment. EXAMPLES - To list the data from the Cloud Composer environment environmnet-1 and + To list the data from the Cloud Composer environment environment-1 and location us-central1, run: $ gcloud beta composer environments storage data list \ diff --git a/gcloud/beta/composer/environments/storage/plugins/delete b/gcloud/beta/composer/environments/storage/plugins/delete index 868a2aa84..9bb813042 100644 --- a/gcloud/beta/composer/environments/storage/plugins/delete +++ b/gcloud/beta/composer/environments/storage/plugins/delete @@ -13,7 +13,7 @@ DESCRIPTION EXAMPLES To delete the plugins in the path path/to/plugins, for the environment - named environmnet-1 in the location us-east1, run: + named environment-1 in the location us-east1, run: $ gcloud beta composer environments storage plugins delete \ path/to/plugins --environment=environment-1 --location=us-east1 diff --git a/gcloud/beta/composer/environments/storage/plugins/list b/gcloud/beta/composer/environments/storage/plugins/list index 8ee4b0409..e637a4304 100644 --- a/gcloud/beta/composer/environments/storage/plugins/list +++ b/gcloud/beta/composer/environments/storage/plugins/list @@ -11,7 +11,7 @@ DESCRIPTION (BETA) List the plugins for a Cloud Composer environment. EXAMPLES - To list the plugins for the Cloud Composer environment environmnet-1 and + To list the plugins for the Cloud Composer environment environment-1 and location us-central1, run: $ gcloud beta composer environments storage plugins list \ diff --git a/gcloud/beta/compute/backend-services/add-backend b/gcloud/beta/compute/backend-services/add-backend index b33d64a25..b4a375788 100644 --- a/gcloud/beta/compute/backend-services/add-backend +++ b/gcloud/beta/compute/backend-services/add-backend @@ -283,7 +283,7 @@ OPTIONAL FLAGS Sets maxUtilization value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -316,7 +316,7 @@ OPTIONAL FLAGS Sets maxUtilization value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: diff --git a/gcloud/beta/compute/backend-services/create b/gcloud/beta/compute/backend-services/create index 840240433..aeecaa426 100644 --- a/gcloud/beta/compute/backend-services/create +++ b/gcloud/beta/compute/backend-services/create @@ -798,7 +798,7 @@ FLAGS Sets dryRun value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -827,7 +827,7 @@ FLAGS Sets dryRun value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: diff --git a/gcloud/beta/compute/backend-services/update b/gcloud/beta/compute/backend-services/update index 516421ea7..6091ddba1 100644 --- a/gcloud/beta/compute/backend-services/update +++ b/gcloud/beta/compute/backend-services/update @@ -313,7 +313,7 @@ FLAGS Enables Dynamic Forwarding in IpPort selection mode. --load-balancing-scheme=LOAD_BALANCING_SCHEME - Only for the Global external ALB migration. + Only for the Global external Application Load Balancer migration. The value of this field must be EXTERNAL or EXTERNAL_MANAGED. @@ -634,7 +634,7 @@ FLAGS Sets dryRun value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -663,7 +663,7 @@ FLAGS Sets dryRun value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -683,15 +683,15 @@ FLAGS Clears current state of external managed migration. --external-managed-migration-state=EXTERNAL_MANAGED_MIGRATION_STATE - Specifies the canary migration state. Possible values are PREPARE, + Specifies the migration state. Possible values are PREPARE, TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state must be changed to PREPARE. The state must be changed to TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be - used to migrate traffic by percentage using - externalManagedMigrationTestingPercentage. + used to migrate traffic by percentage using the + --external-managed-migration-testing-percentage flag. EXTERNAL_MANAGED_MIGRATION_STATE must be one of: PREPARE, TEST_BY_PERCENTAGE, TEST_ALL_TRAFFIC. diff --git a/gcloud/beta/compute/backend-services/update-backend b/gcloud/beta/compute/backend-services/update-backend index 0af4c9eb7..9ba21e668 100644 --- a/gcloud/beta/compute/backend-services/update-backend +++ b/gcloud/beta/compute/backend-services/update-backend @@ -255,7 +255,7 @@ OPTIONAL FLAGS Sets maxUtilization value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -288,7 +288,7 @@ OPTIONAL FLAGS Sets maxUtilization value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: diff --git a/gcloud/beta/compute/firewall-policies/mirroring-rules/create b/gcloud/beta/compute/firewall-policies/mirroring-rules/create index 6a30b35bd..5971fa625 100644 --- a/gcloud/beta/compute/firewall-policies/mirroring-rules/create +++ b/gcloud/beta/compute/firewall-policies/mirroring-rules/create @@ -68,7 +68,7 @@ OPTIONAL FLAGS http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ - c) . In case "c" gCloud CLI will create a reference matching + c) . In case "c" gcloud CLI will create a reference matching format "a", but to make it work CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSECURITY property must be set. In order to set this property, please run the command gcloud config set diff --git a/gcloud/beta/compute/firewall-policies/mirroring-rules/update b/gcloud/beta/compute/firewall-policies/mirroring-rules/update index 20bdedccf..df6c088ce 100644 --- a/gcloud/beta/compute/firewall-policies/mirroring-rules/update +++ b/gcloud/beta/compute/firewall-policies/mirroring-rules/update @@ -71,7 +71,7 @@ OPTIONAL FLAGS http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ - c) . In case "c" gCloud CLI will create a reference matching + c) . In case "c" gcloud CLI will create a reference matching format "a", but to make it work CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSECURITY property must be set. In order to set this property, please run the command gcloud config set diff --git a/gcloud/beta/compute/firewall-policies/rules/create b/gcloud/beta/compute/firewall-policies/rules/create index 8bea4fa08..c3189b61f 100644 --- a/gcloud/beta/compute/firewall-policies/rules/create +++ b/gcloud/beta/compute/firewall-policies/rules/create @@ -109,7 +109,7 @@ OPTIONAL FLAGS http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ - c) . In case "c" gCloud CLI will create a reference matching + c) . In case "c" gcloud CLI will create a reference matching format "a", but to make it work CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSECURITY property must be set. In order to set this property, please run the command gcloud config set diff --git a/gcloud/beta/compute/firewall-policies/rules/update b/gcloud/beta/compute/firewall-policies/rules/update index b937d489e..a2e7de33e 100644 --- a/gcloud/beta/compute/firewall-policies/rules/update +++ b/gcloud/beta/compute/firewall-policies/rules/update @@ -115,7 +115,7 @@ OPTIONAL FLAGS http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ - c) . In case "c" gCloud CLI will create a reference matching + c) . In case "c" gcloud CLI will create a reference matching format "a", but to make it work CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSECURITY property must be set. In order to set this property, please run the command gcloud config set diff --git a/gcloud/beta/compute/firewall-rules/create b/gcloud/beta/compute/firewall-rules/create index 7f8434bb8..2a4a49525 100644 --- a/gcloud/beta/compute/firewall-rules/create +++ b/gcloud/beta/compute/firewall-rules/create @@ -10,6 +10,7 @@ SYNOPSIS [--direction=DIRECTION] [--disabled] [--[no-]enable-logging] [--logging-metadata=LOGGING_METADATA] [--network=NETWORK; default="default"] [--priority=PRIORITY] + [--resource-manager-tags=[KEY=VALUE,...]] [--rules=PROTOCOL[:PORT[-PORT]],[...]] [--source-ranges=CIDR_RANGE,[CIDR_RANGE,...]] [--source-service-accounts=EMAIL,[EMAIL,...]] @@ -150,6 +151,10 @@ OPTIONAL FLAGS precedence. DENY rules take precedence over ALLOW rules having equal priority. + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the + firewall. + --rules=PROTOCOL[:PORT[-PORT]],[...] A list of protocols and ports to which the firewall rule will apply. diff --git a/gcloud/beta/compute/forwarding-rules/update b/gcloud/beta/compute/forwarding-rules/update index 83f0d14da..2179de090 100644 --- a/gcloud/beta/compute/forwarding-rules/update +++ b/gcloud/beta/compute/forwarding-rules/update @@ -64,7 +64,7 @@ FLAGS The value of this field must be in the range [0, 100]. --load-balancing-scheme=LOAD_BALANCING_SCHEME - Only for the Global external ALB migration. + Only for the Global external Application Load Balancer migration. The value of this field must be EXTERNAL or EXTERNAL_MANAGED. @@ -90,7 +90,7 @@ FLAGS Clears current state of external managed migration. --external-managed-backend-bucket-migration-state=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_STATE - Specifies the canary migration state. Possible values are PREPARE, + Specifies the migration state. Possible values are PREPARE, TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state @@ -98,8 +98,8 @@ FLAGS TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate traffic to backend buckets attached to this - forwarding rule by percentage using - externalManagedBackendBucketMigrationTestingPercentage. + forwarding rule by percentage using the + --external-managed-backend-bucket-migration-testing-percentage flag. EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_STATE must be one of: PREPARE, TEST_BY_PERCENTAGE, TEST_ALL_TRAFFIC. diff --git a/gcloud/beta/compute/future-reservations/update b/gcloud/beta/compute/future-reservations/update index 8a254dc37..98c16c809 100644 --- a/gcloud/beta/compute/future-reservations/update +++ b/gcloud/beta/compute/future-reservations/update @@ -6,6 +6,7 @@ SYNOPSIS gcloud beta compute future-reservations update FUTURE_RESERVATION [--[no-]auto-delete-auto-created-reservations] [--deployment-type=DEPLOYMENT_TYPE] [--description=DESCRIPTION] + [--[no-]enable-emergent-maintenance] [--planning-status=PLANNING_STATUS] [--[no-]require-specific-reservation] [--reservation-name=RESERVATION_NAME] @@ -59,6 +60,12 @@ FLAGS --description=DESCRIPTION An optional description of the future reservation to create. + --[no-]enable-emergent-maintenance + Emergent maintenance flag for the reservation, which enrolls all the + underlying vms, hosts and SB infrastructure to receive emergent + maintenance notifications in advance. Use --enable-emergent-maintenance + to enable and --no-enable-emergent-maintenance to disable. + --planning-status=PLANNING_STATUS The planning status of the future reservation. The default value is DRAFT. While in DRAFT, any changes to the future reservation's diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index 903e66624..be3eca16d 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -836,6 +836,9 @@ FLAGS 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 diff --git a/gcloud/beta/compute/networks/create b/gcloud/beta/compute/networks/create index 7c933a5b5..28eb91a2d 100644 --- a/gcloud/beta/compute/networks/create +++ b/gcloud/beta/compute/networks/create @@ -8,7 +8,7 @@ SYNOPSIS [--internal-ipv6-range=INTERNAL_IPV6_RANGE] [--mtu=MTU] [--network-firewall-policy-enforcement-order=NETWORK_FIREWALL_POLICY_ENFORCEMENT_ORDER] [--network-profile=NETWORK_PROFILE] [--range=RANGE] - [--subnet-mode=MODE] + [--resource-manager-tags=[KEY=VALUE,...]] [--subnet-mode=MODE] [--bgp-best-path-selection-mode=BGP_BEST_PATH_SELECTION_MODE --[no-]bgp-bps-always-compare-med --bgp-bps-inter-region-cost=BGP_BPS_INTER_REGION_COST] @@ -103,6 +103,10 @@ FLAGS Cloud Platform features are not supported on legacy networks. Please be advised that legacy networks may not be supported in the future. + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the + network. + --subnet-mode=MODE The subnet mode of the network. If not specified, defaults to AUTO. diff --git a/gcloud/beta/compute/networks/subnets/create b/gcloud/beta/compute/networks/subnets/create index 23a624177..d2aa903f8 100644 --- a/gcloud/beta/compute/networks/subnets/create +++ b/gcloud/beta/compute/networks/subnets/create @@ -15,7 +15,8 @@ SYNOPSIS [--logging-metadata-fields=[METADATA_FIELD,...]] [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] [--purpose=PURPOSE] [--range=RANGE] [--region=REGION] - [--reserved-internal-range=RESERVED_INTERNAL_RANGE] [--role=ROLE] + [--reserved-internal-range=RESERVED_INTERNAL_RANGE] + [--resource-manager-tags=[KEY=VALUE,...]] [--role=ROLE] [--secondary-range=PROPERTY=VALUE,[...]] [--secondary-range-with-reserved-internal-range=RANGE_NAME=INTERNAL_RANGE_URL, [...]] [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...] @@ -166,6 +167,10 @@ OPTIONAL FLAGS --reserved-internal-range //networkconnectivity.googleapis.com/projects/PROJECT/locations/global/internalRanges/RANGE + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the + subnetwork. + --role=ROLE The role of subnetwork. This field is required when the purpose is set to GLOBAL_MANAGED_PROXY, REGIONAL_MANAGED_PROXY or diff --git a/gcloud/beta/compute/reservations/update b/gcloud/beta/compute/reservations/update index a63a6d612..41ee0e9a6 100644 --- a/gcloud/beta/compute/reservations/update +++ b/gcloud/beta/compute/reservations/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta compute reservations update RESERVATION [--add-share-with=PROJECT,[PROJECT,...]] + [--[no-]enable-emergent-maintenance] [--remove-share-with=PROJECT,[PROJECT,...]] [--reservation-sharing-policy=RESERVATION_SHARING_POLICY] [--share-setting=SHARE_SETTING] @@ -56,6 +57,12 @@ FLAGS specify a comma-separated list of projects to share the reservation with. You must list the projects using project IDs or project numbers. + --[no-]enable-emergent-maintenance + The emergent maintenance flag for the reservation, which enrolls all + the underlying vms, hosts and SB infrastructure to receive emergent + maintenance notifications in advance. Use --enable-emergent-maintenance + to enable and --no-enable-emergent-maintenance to disable. + --remove-share-with=PROJECT,[PROJECT,...] A list of specific projects to remove from the list of projects that this reservation is shared with. List must contain project IDs or diff --git a/gcloud/beta/compute/routes/create b/gcloud/beta/compute/routes/create index bb6ca89b2..cefb3f064 100644 --- a/gcloud/beta/compute/routes/create +++ b/gcloud/beta/compute/routes/create @@ -12,7 +12,8 @@ SYNOPSIS [--next-hop-ilb-region=NEXT_HOP_ILB_REGION] [--next-hop-instance-zone=NEXT_HOP_INSTANCE_ZONE] [--next-hop-vpn-tunnel-region=NEXT_HOP_VPN_TUNNEL_REGION] - [--priority=PRIORITY; default=1000] [--tags=TAG,[TAG,...]] + [--priority=PRIORITY; default=1000] + [--resource-manager-tags=[KEY=VALUE,...]] [--tags=TAG,[TAG,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -159,6 +160,9 @@ OPTIONAL FLAGS Specifies the priority of this route relative to other routes with the same specificity. The lower the value, the higher the priority. + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the route. + --tags=TAG,[TAG,...] Identifies the set of instances that this route will apply to. If no tags are provided, the route will apply to all instances in the diff --git a/gcloud/beta/compute/security-policies/create b/gcloud/beta/compute/security-policies/create index ccb6c7826..a23cfbb89 100644 --- a/gcloud/beta/compute/security-policies/create +++ b/gcloud/beta/compute/security-policies/create @@ -49,7 +49,7 @@ FLAGS --type=SECURITY_POLICY_TYPE The type indicates the intended use of the security policy. SECURITY_POLICY_TYPE must be one of: CLOUD_ARMOR, CLOUD_ARMOR_EDGE, - CLOUD_ARMOR_NETWORK. + CLOUD_ARMOR_NETWORK, CLOUD_ARMOR_INTERNAL_SERVICE. At most one of these can be specified: diff --git a/gcloud/beta/compute/security-policies/rules/create b/gcloud/beta/compute/security-policies/rules/create index 7914cb58e..f3cdc7f75 100644 --- a/gcloud/beta/compute/security-policies/rules/create +++ b/gcloud/beta/compute/security-policies/rules/create @@ -70,6 +70,10 @@ REQUIRED FLAGS deny-502 Denies the request from HTTP(S) Load Balancing, with an HTTP response status code of 502. + fairshare + When traffic reaches the threshold limit, requests from the clients + matching this rule begin to be rate-limited using the Fair Share + algorithm. rate-based-ban Enforces rate-based ban action from HTTP(S) Load Balancing, based on rate limit options. diff --git a/gcloud/beta/compute/security-policies/rules/update b/gcloud/beta/compute/security-policies/rules/update index 0f8b04c75..e480e8687 100644 --- a/gcloud/beta/compute/security-policies/rules/update +++ b/gcloud/beta/compute/security-policies/rules/update @@ -70,6 +70,10 @@ FLAGS deny-502 Denies the request from HTTP(S) Load Balancing, with an HTTP response status code of 502. + fairshare + When traffic reaches the threshold limit, requests from the clients + matching this rule begin to be rate-limited using the Fair Share + algorithm. rate-based-ban Enforces rate-based ban action from HTTP(S) Load Balancing, based on rate limit options. diff --git a/gcloud/beta/container/backup-restore/backup-channels/create b/gcloud/beta/container/backup-restore/backup-channels/create index d2c737b2f..e775f5527 100644 --- a/gcloud/beta/container/backup-restore/backup-channels/create +++ b/gcloud/beta/container/backup-restore/backup-channels/create @@ -18,7 +18,7 @@ EXAMPLES $ gcloud beta container backup-restore backup-channels create \ my-backup-channel --project=my-project --location=us-central1 \ - --destination_project=projects/1234567890 + --destination-project=projects/1234567890 POSITIONAL ARGUMENTS Backup channel resource - Name of the backup channel to create. Once the diff --git a/gcloud/beta/container/backup-restore/restore-channels/create b/gcloud/beta/container/backup-restore/restore-channels/create index eade4e89b..0f4432cc5 100644 --- a/gcloud/beta/container/backup-restore/restore-channels/create +++ b/gcloud/beta/container/backup-restore/restore-channels/create @@ -18,7 +18,7 @@ EXAMPLES $ gcloud beta container backup-restore restore-channels create \ my-restore-channel --project=my-project --location=us-central1 \ - --destination_project=projects/1234567890 + --destination-project=projects/1234567890 POSITIONAL ARGUMENTS Restore channel resource - Name of the restore channel to create. Once the diff --git a/gcloud/beta/dataproc/batches/submit/help b/gcloud/beta/dataproc/batches/submit/help index 1a85c74a1..37e95a838 100644 --- a/gcloud/beta/dataproc/batches/submit/help +++ b/gcloud/beta/dataproc/batches/submit/help @@ -9,6 +9,7 @@ SYNOPSIS [--properties=[PROPERTY=VALUE,...]] [--region=REGION] [--request-id=REQUEST_ID] [--service-account=SERVICE_ACCOUNT] [--staging-bucket=STAGING_BUCKET] [--tags=[TAGS,...]] [--ttl=TTL] + [--user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE] [--version=VERSION] [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] @@ -132,6 +133,10 @@ FLAGS (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for information on duration formats. + --user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE + Whether to use END_USER_CREDENTIALS or SERVICE_ACCOUNT to run the + workload. + --version=VERSION Optional runtime version. If not specified, a default version will be used. diff --git a/gcloud/beta/dataproc/batches/submit/pyspark b/gcloud/beta/dataproc/batches/submit/pyspark index db63a01b5..957875ee3 100644 --- a/gcloud/beta/dataproc/batches/submit/pyspark +++ b/gcloud/beta/dataproc/batches/submit/pyspark @@ -11,9 +11,10 @@ SYNOPSIS [--properties=[PROPERTY=VALUE,...]] [--py-files=[PY,...]] [--region=REGION] [--request-id=REQUEST_ID] [--service-account=SERVICE_ACCOUNT] [--staging-bucket=STAGING_BUCKET] - [--tags=[TAGS,...]] [--ttl=TTL] [--version=VERSION] - [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] - [-- JOB_ARG ...] + [--tags=[TAGS,...]] [--ttl=TTL] + [--user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE] + [--version=VERSION] [--network=NETWORK | --subnet=SUBNET] + [GCLOUD_WIDE_FLAG ...] [-- JOB_ARG ...] DESCRIPTION (BETA) Submit a PySpark batch job. @@ -148,6 +149,10 @@ FLAGS (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for information on duration formats. + --user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE + Whether to use END_USER_CREDENTIALS or SERVICE_ACCOUNT to run the + workload. + --version=VERSION Optional runtime version. If not specified, a default version will be used. diff --git a/gcloud/beta/dataproc/batches/submit/spark b/gcloud/beta/dataproc/batches/submit/spark index 029b23b42..264d29150 100644 --- a/gcloud/beta/dataproc/batches/submit/spark +++ b/gcloud/beta/dataproc/batches/submit/spark @@ -12,6 +12,7 @@ SYNOPSIS [--properties=[PROPERTY=VALUE,...]] [--region=REGION] [--request-id=REQUEST_ID] [--service-account=SERVICE_ACCOUNT] [--staging-bucket=STAGING_BUCKET] [--tags=[TAGS,...]] [--ttl=TTL] + [--user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE] [--version=VERSION] [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARG ...] @@ -162,6 +163,10 @@ OPTIONAL FLAGS (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for information on duration formats. + --user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE + Whether to use END_USER_CREDENTIALS or SERVICE_ACCOUNT to run the + workload. + --version=VERSION Optional runtime version. If not specified, a default version will be used. diff --git a/gcloud/beta/dataproc/batches/submit/spark-r b/gcloud/beta/dataproc/batches/submit/spark-r index 92496edd3..5e8271b71 100644 --- a/gcloud/beta/dataproc/batches/submit/spark-r +++ b/gcloud/beta/dataproc/batches/submit/spark-r @@ -11,6 +11,7 @@ SYNOPSIS [--properties=[PROPERTY=VALUE,...]] [--region=REGION] [--request-id=REQUEST_ID] [--service-account=SERVICE_ACCOUNT] [--staging-bucket=STAGING_BUCKET] [--tags=[TAGS,...]] [--ttl=TTL] + [--user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE] [--version=VERSION] [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARG ...] @@ -139,6 +140,10 @@ FLAGS (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for information on duration formats. + --user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE + Whether to use END_USER_CREDENTIALS or SERVICE_ACCOUNT to run the + workload. + --version=VERSION Optional runtime version. If not specified, a default version will be used. diff --git a/gcloud/beta/dataproc/batches/submit/spark-sql b/gcloud/beta/dataproc/batches/submit/spark-sql index 86fa6a175..ceab4c0b8 100644 --- a/gcloud/beta/dataproc/batches/submit/spark-sql +++ b/gcloud/beta/dataproc/batches/submit/spark-sql @@ -12,6 +12,7 @@ SYNOPSIS [--properties=[PROPERTY=VALUE,...]] [--region=REGION] [--request-id=REQUEST_ID] [--service-account=SERVICE_ACCOUNT] [--staging-bucket=STAGING_BUCKET] [--tags=[TAGS,...]] [--ttl=TTL] + [--user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE] [--vars=[NAME=VALUE,...]] [--version=VERSION] [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] @@ -130,6 +131,10 @@ FLAGS (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for information on duration formats. + --user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE + Whether to use END_USER_CREDENTIALS or SERVICE_ACCOUNT to run the + workload. + --vars=[NAME=VALUE,...] Mapping of query variable names to values (equivalent to the Spark SQL command: SET name="value";). diff --git a/gcloud/beta/dataproc/clusters/create b/gcloud/beta/dataproc/clusters/create index db8423087..b161ecaad 100644 --- a/gcloud/beta/dataproc/clusters/create +++ b/gcloud/beta/dataproc/clusters/create @@ -43,7 +43,8 @@ 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] [--stop-max-idle=STOP_MAX_IDLE] + [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -77,6 +78,8 @@ 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 ...] @@ -418,6 +421,11 @@ 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. @@ -942,6 +950,18 @@ 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 5e032cc9e..e7d4b5048 100644 --- a/gcloud/beta/dataproc/clusters/update +++ b/gcloud/beta/dataproc/clusters/update @@ -15,7 +15,11 @@ 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] [GCLOUD_WIDE_FLAG ...] + | --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 ...] DESCRIPTION (BETA) Update the number of worker nodes and/or the labels in a cluster. @@ -216,6 +220,33 @@ 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/sessions/create/help b/gcloud/beta/dataproc/sessions/create/help index e3542867f..7c30d9724 100644 --- a/gcloud/beta/dataproc/sessions/create/help +++ b/gcloud/beta/dataproc/sessions/create/help @@ -10,8 +10,10 @@ SYNOPSIS [--property=[PROPERTY=VALUE,...]] [--request-id=REQUEST_ID] [--service-account=SERVICE_ACCOUNT] [--session_template=SESSION_TEMPLATE] [--staging-bucket=STAGING_BUCKET] - [--tags=[TAGS,...]] [--ttl=TTL] [--version=VERSION] - [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] + [--tags=[TAGS,...]] [--ttl=TTL] + [--user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE] + [--version=VERSION] [--network=NETWORK | --subnet=SUBNET] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create various sessions, such as Spark. @@ -102,6 +104,10 @@ FLAGS (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for information on duration formats. + --user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE + Whether to use END_USER_CREDENTIALS or SERVICE_ACCOUNT to run the + workload. + --version=VERSION Optional runtime version. If not specified, a default version will be used. diff --git a/gcloud/beta/dataproc/sessions/create/spark b/gcloud/beta/dataproc/sessions/create/spark index 88990428c..83593a61b 100644 --- a/gcloud/beta/dataproc/sessions/create/spark +++ b/gcloud/beta/dataproc/sessions/create/spark @@ -10,8 +10,10 @@ SYNOPSIS [--property=[PROPERTY=VALUE,...]] [--request-id=REQUEST_ID] [--service-account=SERVICE_ACCOUNT] [--session_template=SESSION_TEMPLATE] [--staging-bucket=STAGING_BUCKET] - [--tags=[TAGS,...]] [--ttl=TTL] [--version=VERSION] - [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] + [--tags=[TAGS,...]] [--ttl=TTL] + [--user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE] + [--version=VERSION] [--network=NETWORK | --subnet=SUBNET] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a Spark session. @@ -137,6 +139,10 @@ FLAGS (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for information on duration formats. + --user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE + Whether to use END_USER_CREDENTIALS or SERVICE_ACCOUNT to run the + workload. + --version=VERSION Optional runtime version. If not specified, a default version will be used. diff --git a/gcloud/beta/deploy/job-runs/terminate b/gcloud/beta/deploy/job-runs/terminate index c6ed2e6f4..4ab175ff1 100644 --- a/gcloud/beta/deploy/job-runs/terminate +++ b/gcloud/beta/deploy/job-runs/terminate @@ -5,7 +5,7 @@ SYNOPSIS gcloud beta deploy job-runs terminate (JOB_RUN : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION --release=RELEASE --rollout=ROLLOUT) - [GCLOUD_WIDE_FLAG ...] + [--override-deploy-policies=[POLICY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Terminates a Cloud Deploy job run. @@ -78,6 +78,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --rollout on the command line. +FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/releases/create b/gcloud/beta/deploy/releases/create index ff0556df9..6428f23b5 100644 --- a/gcloud/beta/deploy/releases/create +++ b/gcloud/beta/deploy/releases/create @@ -9,6 +9,7 @@ SYNOPSIS [--description=DESCRIPTION] [--gcs-source-staging-dir=GCS_SOURCE_STAGING_DIR] [--ignore-file=IGNORE_FILE] [--labels=[KEY=VALUE,...]] + [--override-deploy-policies=[POLICY,...]] [--skaffold-version=SKAFFOLD_VERSION] [--to-target=TO_TARGET] [--build-artifacts=BUILD_ARTIFACTS | --images=[NAME=TAG,...]] [--disable-initial-rollout | --enable-initial-rollout @@ -148,6 +149,9 @@ FLAGS $ gcloud beta deploy releases create \ --labels="commit=abc123,author=foo" + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --skaffold-version=SKAFFOLD_VERSION Version of the Skaffold binary. diff --git a/gcloud/beta/deploy/releases/promote b/gcloud/beta/deploy/releases/promote index ebdd57764..8092b05e2 100644 --- a/gcloud/beta/deploy/releases/promote +++ b/gcloud/beta/deploy/releases/promote @@ -7,8 +7,9 @@ SYNOPSIS (--release=RELEASE : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) [--annotations=[KEY=VALUE,...]] [--labels=[KEY=VALUE,...]] - [--rollout-id=ROLLOUT_ID] [--starting-phase-id=STARTING_PHASE_ID] - [--to-target=TO_TARGET] [GCLOUD_WIDE_FLAG ...] + [--override-deploy-policies=[POLICY,...]] [--rollout-id=ROLLOUT_ID] + [--starting-phase-id=STARTING_PHASE_ID] [--to-target=TO_TARGET] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) If to-target is not specified the command promotes the release from @@ -89,6 +90,9 @@ OPTIONAL FLAGS $ gcloud beta deploy releases promote \ --labels="commit=abc123,author=foo" + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --rollout-id=ROLLOUT_ID ID to assign to the generated rollout for promotion. diff --git a/gcloud/beta/deploy/rollouts/advance b/gcloud/beta/deploy/rollouts/advance index 2638283f5..b536c9009 100644 --- a/gcloud/beta/deploy/rollouts/advance +++ b/gcloud/beta/deploy/rollouts/advance @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta deploy rollouts advance (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE - --region=REGION --release=RELEASE) [--phase-id=PHASE_ID] + --region=REGION --release=RELEASE) + [--override-deploy-policies=[POLICY,...]] [--phase-id=PHASE_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -70,6 +71,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --release on the command line. FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --phase-id=PHASE_ID Phase ID on a rollout resource diff --git a/gcloud/beta/deploy/rollouts/approve b/gcloud/beta/deploy/rollouts/approve index da9c991d7..bd90cabba 100644 --- a/gcloud/beta/deploy/rollouts/approve +++ b/gcloud/beta/deploy/rollouts/approve @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta deploy rollouts approve (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE - --region=REGION --release=RELEASE) [GCLOUD_WIDE_FLAG ...] + --region=REGION --release=RELEASE) + [--override-deploy-policies=[POLICY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Approves a rollout having an Approval state of "Required". @@ -69,6 +70,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --release on the command line. +FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/rollouts/cancel b/gcloud/beta/deploy/rollouts/cancel index 8a061bb28..7fd0d8436 100644 --- a/gcloud/beta/deploy/rollouts/cancel +++ b/gcloud/beta/deploy/rollouts/cancel @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta deploy rollouts cancel (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE - --region=REGION --release=RELEASE) [GCLOUD_WIDE_FLAG ...] + --region=REGION --release=RELEASE) + [--override-deploy-policies=[POLICY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Cancel a Rollout. @@ -68,6 +69,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --release on the command line. +FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/rollouts/ignore-job b/gcloud/beta/deploy/rollouts/ignore-job index 26f3bad12..a8b7283cd 100644 --- a/gcloud/beta/deploy/rollouts/ignore-job +++ b/gcloud/beta/deploy/rollouts/ignore-job @@ -6,7 +6,8 @@ SYNOPSIS gcloud beta deploy rollouts ignore-job (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION --release=RELEASE) --job-id=JOB_ID - --phase-id=PHASE_ID [GCLOUD_WIDE_FLAG ...] + --phase-id=PHASE_ID [--override-deploy-policies=[POLICY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Ignores a specified job and phase combination on a rollout. @@ -79,6 +80,10 @@ REQUIRED FLAGS --phase-id=PHASE_ID Phase ID on a rollout resource +OPTIONAL FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/rollouts/reject b/gcloud/beta/deploy/rollouts/reject index 7f00f853e..e5bb55ef3 100644 --- a/gcloud/beta/deploy/rollouts/reject +++ b/gcloud/beta/deploy/rollouts/reject @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta deploy rollouts reject (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE - --region=REGION --release=RELEASE) [GCLOUD_WIDE_FLAG ...] + --region=REGION --release=RELEASE) + [--override-deploy-policies=[POLICY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Rejects a rollout having an Approval state of "Required". @@ -69,6 +70,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --release on the command line. +FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/rollouts/retry-job b/gcloud/beta/deploy/rollouts/retry-job index ae8a1ac46..2eb29b9cc 100644 --- a/gcloud/beta/deploy/rollouts/retry-job +++ b/gcloud/beta/deploy/rollouts/retry-job @@ -6,7 +6,8 @@ SYNOPSIS gcloud beta deploy rollouts retry-job (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION --release=RELEASE) --job-id=JOB_ID - --phase-id=PHASE_ID [GCLOUD_WIDE_FLAG ...] + --phase-id=PHASE_ID [--override-deploy-policies=[POLICY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Retries a specified job, phase combination on a rollout. @@ -79,6 +80,10 @@ REQUIRED FLAGS --phase-id=PHASE_ID Phase ID on a rollout resource +OPTIONAL FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/targets/redeploy b/gcloud/beta/deploy/targets/redeploy index c8c316383..3016783fe 100644 --- a/gcloud/beta/deploy/targets/redeploy +++ b/gcloud/beta/deploy/targets/redeploy @@ -5,8 +5,8 @@ SYNOPSIS gcloud beta deploy targets redeploy (TARGET : --region=REGION) --delivery-pipeline=DELIVERY_PIPELINE [--annotations=[KEY=VALUE,...]] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--rollout-id=ROLLOUT_ID] [--starting-phase-id=STARTING_PHASE_ID] - [GCLOUD_WIDE_FLAG ...] + [--override-deploy-policies=[POLICY,...]] [--rollout-id=ROLLOUT_ID] + [--starting-phase-id=STARTING_PHASE_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Redeploy the last rollout that has a state of SUCCESSFUL or FAILED @@ -82,6 +82,9 @@ OPTIONAL FLAGS $ gcloud beta deploy targets redeploy \ --labels="commit=abc123,author=foo" + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --rollout-id=ROLLOUT_ID ID to assign to the generated rollout for promotion. diff --git a/gcloud/beta/deploy/targets/rollback b/gcloud/beta/deploy/targets/rollback index e94e2ad86..5f6e33efb 100644 --- a/gcloud/beta/deploy/targets/rollback +++ b/gcloud/beta/deploy/targets/rollback @@ -5,8 +5,9 @@ SYNOPSIS gcloud beta deploy targets rollback (TARGET : --region=REGION) --delivery-pipeline=DELIVERY_PIPELINE [--annotations=[KEY=VALUE,...]] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--release=RELEASE] [--rollout-id=ROLLOUT_ID] - [--starting-phase-id=STARTING_PHASE_ID] [GCLOUD_WIDE_FLAG ...] + [--override-deploy-policies=[POLICY,...]] [--release=RELEASE] + [--rollout-id=ROLLOUT_ID] [--starting-phase-id=STARTING_PHASE_ID] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) If release is not specified, the command rollbacks the target with @@ -82,6 +83,9 @@ OPTIONAL FLAGS $ gcloud beta deploy targets rollback \ --labels="commit=abc123,author=foo" + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --release=RELEASE Name of the release to rollback to. diff --git a/gcloud/beta/iam/workforce-pools/providers/create-oidc b/gcloud/beta/iam/workforce-pools/providers/create-oidc index 4e578edb8..e01d8cc61 100644 --- a/gcloud/beta/iam/workforce-pools/providers/create-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/create-oidc @@ -273,32 +273,28 @@ OPTIONAL FLAGS *--extra-attributes-client-id*=_EXTRA_ATTRIBUTES_CLIENT_ID_:: - The OAuth 2.0 client ID for retrieving extra attributes from the identity provider. Required - to get the Access Token using client credentials grant flow. + The OAuth 2.0 client ID for retrieving extra attributes from the identity provider. Required to get the access token using client credentials grant flow. *--extra-attributes-client-secret-value*=_EXTRA_ATTRIBUTES_CLIENT_SECRET_VALUE_:: - The OAuth 2.0 client secret for retrieving extra attributes from the identity provider. - Required to get the Access Token using client credentials grant flow. + The OAuth 2.0 client secret for retrieving extra attributes from the identity provider. Required to get the access token using client credentials grant flow. *--extra-attributes-issuer-uri*=_EXTRA_ATTRIBUTES_ISSUER_URI_:: - OIDC identity provider's issuer URI. Must be a valid URI using the 'https' scheme. - Required to get the OIDC discovery document. + OIDC identity provider's issuer URI. Must be a valid URI using the `https` scheme. Required to get the OIDC discovery document. *--extra-attributes-type*=_EXTRA_ATTRIBUTES_TYPE_:: - Represents the identity provider and type of claims that should be fetched. _EXTRA_ATTRIBUTES_TYPE_ must be one of: *attributes-type-unspecified*, *azure-ad-groups-display-name*, *azure-ad-groups-id*, *azure-ad-groups-mail*. + Represents the identity provider and type of claims that should be fetched. _EXTRA_ATTRIBUTES_TYPE_ must be one of: *azure-ad-groups-mail*, *azure-ad-groups-id*. *--extra-attributes-filter*=_EXTRA_ATTRIBUTES_FILTER_:: - The filter used to request specific records from IdP. When used with the attributes type - azure-ad-groups-mail or azure-ad-groups-id, the filter requests specific groups associated - with a user from the IdP. By default all of the groups associated with the user are fetched. - When used with the attributes type azure-ad-groups-mail, the groups that are used should be - security and mail enabled. When used with the attributes type azure-ad-groups-id, the groups - that are used should be security enabled. See - https://learn.microsoft.com/en-us/graph/search-query-parameter for more details. + The filter used to request specific records from the IdP. By default, all of the groups that are associated with a user are fetched. For Microsoft Entra ID, you can add `$search` query parameters using [Keyword Query Language] (https://learn.microsoft.com/en-us/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference). To learn more about `$search` querying in Microsoft Entra ID, see [Use the `$search` query parameter] (https://learn.microsoft.com/en-us/graph/search-query-parameter). + + Additionally, Workforce Identity Federation automatically adds the following [`$filter` query parameters] (https://learn.microsoft.com/en-us/graph/filter-query-parameter), based on the value of `attributes_type`. Values passed to `filter` are converted to `$search` query parameters. Additional `$filter` query parameters cannot be added using this field. + + * `AZURE_AD_GROUPS_MAIL`: `mailEnabled` and `securityEnabled` filters are applied. + * `AZURE_AD_GROUPS_ID`: `securityEnabled` filter is 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. diff --git a/gcloud/beta/iam/workforce-pools/providers/update-oidc b/gcloud/beta/iam/workforce-pools/providers/update-oidc index e9c368702..a28e25ecc 100644 --- a/gcloud/beta/iam/workforce-pools/providers/update-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/update-oidc @@ -259,36 +259,32 @@ FLAGS *--clear-extra-attributes-config*::: - Clear the extra attributes configuration + Clear the extra attributes configuration. *--extra-attributes-client-id*=_EXTRA_ATTRIBUTES_CLIENT_ID_::: - The OAuth 2.0 client ID for retrieving extra attributes from the identity provider. Required - to get the Access Token using client credentials grant flow. + The OAuth 2.0 client ID for retrieving extra attributes from the identity provider. Required to get the access token using client credentials grant flow. *--extra-attributes-client-secret-value*=_EXTRA_ATTRIBUTES_CLIENT_SECRET_VALUE_::: - The OAuth 2.0 client secret for retrieving extra attributes from the identity provider. - Required to get the Access Token using client credentials grant flow. + The OAuth 2.0 client secret for retrieving extra attributes from the identity provider. Required to get the access token using client credentials grant flow. *--extra-attributes-filter*=_EXTRA_ATTRIBUTES_FILTER_::: - The filter used to request specific records from IdP. When used with the attributes type - azure-ad-groups-mail or azure-ad-groups-id, the filter requests specific groups associated - with a user from the IdP. By default all of the groups associated with the user are fetched. - When used with the attributes type azure-ad-groups-mail, the groups that are used should be - security and mail enabled. When used with the attributes type azure-ad-groups-id, the groups - that are used should be security enabled. See - https://learn.microsoft.com/en-us/graph/search-query-parameter for more details. + The filter used to request specific records from the IdP. By default, all of the groups that are associated with a user are fetched. For Microsoft Entra ID, you can add `$search` query parameters using [Keyword Query Language] (https://learn.microsoft.com/en-us/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference). To learn more about `$search` querying in Microsoft Entra ID, see [Use the `$search` query parameter] (https://learn.microsoft.com/en-us/graph/search-query-parameter). + + Additionally, Workforce Identity Federation automatically adds the following [`$filter` query parameters] (https://learn.microsoft.com/en-us/graph/filter-query-parameter), based on the value of `attributes_type`. Values passed to `filter` are converted to `$search` query parameters. Additional `$filter` query parameters cannot be added using this field. + + * `AZURE_AD_GROUPS_MAIL`: `mailEnabled` and `securityEnabled` filters are applied. + * `AZURE_AD_GROUPS_ID`: `securityEnabled` filter is applied. *--extra-attributes-issuer-uri*=_EXTRA_ATTRIBUTES_ISSUER_URI_::: - OIDC identity provider's issuer URI. Must be a valid URI using the 'https' scheme. - Required to get the OIDC discovery document. + OIDC identity provider's issuer URI. Must be a valid URI using the `https` scheme. Required to get the OIDC discovery document. *--extra-attributes-type*=_EXTRA_ATTRIBUTES_TYPE_::: - Represents the identity provider and type of claims that should be fetched. _EXTRA_ATTRIBUTES_TYPE_ must be one of: *attributes-type-unspecified*, *azure-ad-groups-display-name*, *azure-ad-groups-id*, *azure-ad-groups-mail*. + Represents the identity provider and type of claims that should be fetched. _EXTRA_ATTRIBUTES_TYPE_ must be one of: *azure-ad-groups-mail*, *azure-ad-groups-id*. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity. diff --git a/gcloud/beta/managed-kafka/acls/add-acl-entry b/gcloud/beta/managed-kafka/acls/add-acl-entry index 924fb13d8..30fa80989 100644 --- a/gcloud/beta/managed-kafka/acls/add-acl-entry +++ b/gcloud/beta/managed-kafka/acls/add-acl-entry @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud beta managed-kafka acls add-acl-entry (ACL : --cluster=CLUSTER --location=LOCATION) --operation=OPERATION - --principal=PRINCIPAL [--host=HOST; default=""] + --principal=PRINCIPAL [--host=HOST; default="*"] [--permission-type=PERMISSION_TYPE; default="ALLOW"] [GCLOUD_WIDE_FLAG ...] @@ -101,7 +101,7 @@ REQUIRED FLAGS "User:*" to refer to all users. OPTIONAL FLAGS - --host=HOST; default="" + --host=HOST; default="*" The host. Must be set to "*" for Managed Service for Apache Kafka. --permission-type=PERMISSION_TYPE; default="ALLOW" diff --git a/gcloud/beta/managed-kafka/acls/remove-acl-entry b/gcloud/beta/managed-kafka/acls/remove-acl-entry index 0470a4de9..6ea35ca22 100644 --- a/gcloud/beta/managed-kafka/acls/remove-acl-entry +++ b/gcloud/beta/managed-kafka/acls/remove-acl-entry @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud beta managed-kafka acls remove-acl-entry (ACL : --cluster=CLUSTER --location=LOCATION) --operation=OPERATION - --principal=PRINCIPAL [--host=HOST; default=""] + --principal=PRINCIPAL [--host=HOST; default="*"] [--permission-type=PERMISSION_TYPE; default="ALLOW"] [GCLOUD_WIDE_FLAG ...] @@ -81,7 +81,7 @@ REQUIRED FLAGS "User:*" to refer to all users. OPTIONAL FLAGS - --host=HOST; default="" + --host=HOST; default="*" The host. Must be set to "*" for Managed Service for Apache Kafka. --permission-type=PERMISSION_TYPE; default="ALLOW" diff --git a/gcloud/beta/managed-kafka/clusters/create b/gcloud/beta/managed-kafka/clusters/create index 6938aae21..47b6fc18b 100644 --- a/gcloud/beta/managed-kafka/clusters/create +++ b/gcloud/beta/managed-kafka/clusters/create @@ -62,13 +62,13 @@ REQUIRED FLAGS between 1 GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi. --subnets=[SUBNETS,...] - VPC subnets from which the cluster is accessible. Both broker and - bootstrap server IP addresses and DNS entries are automatically created - in each subnet. Only one subnet per network is allowed, and the subnet - must be located in the same region as the cluster. The project may - differ. A minimum of 1 subnet is required. A maximum of 10 subnets can - be specified. Use commas to separate multiple subnets. The name of the - subnet must be in the format + A comma-separated list of VPC subnets from which the cluster is + accessible. Both broker and bootstrap server IP addresses and DNS + entries are automatically created in each subnet. Only one subnet per + network is allowed, and the subnet must be located in the same region + as the cluster. The project may differ. A minimum of 1 subnet is + required. A maximum of 10 subnets can be specified. Use commas to + separate multiple subnets. The name of the subnet must be in the format projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. OPTIONAL FLAGS diff --git a/gcloud/beta/managed-kafka/clusters/update b/gcloud/beta/managed-kafka/clusters/update index 1ada40e15..fe61c14da 100644 --- a/gcloud/beta/managed-kafka/clusters/update +++ b/gcloud/beta/managed-kafka/clusters/update @@ -75,14 +75,14 @@ REQUIRED FLAGS between 1 GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi. --subnets=[SUBNETS,...] - VPC subnets from which the cluster is accessible. Both broker and - bootstrap server IP addresses and DNS entries are automatically - created in each subnet. Only one subnet per network is allowed, and - the subnet must be located in the same region as the cluster. The - project may differ. A minimum of 1 subnet is required. A maximum of - 10 subnets can be specified. Use commas to separate multiple subnets. - The name of the subnet must be in the format - projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. + A comma-separated list of VPC subnets from which the cluster is + accessible. Both broker and bootstrap server IP addresses and DNS + entries are automatically created in each subnet. Only one subnet per + network is allowed, and the subnet must be located in the same region + as the cluster. The project may differ. A minimum of 1 subnet is + required. A maximum of 10 subnets can be specified. Use commas to + separate multiple subnets. The name of the subnet must be in the + format projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. OPTIONAL FLAGS --async diff --git a/gcloud/beta/managed-kafka/consumer-groups/update b/gcloud/beta/managed-kafka/consumer-groups/update index fb7eaac29..db490cfe7 100644 --- a/gcloud/beta/managed-kafka/consumer-groups/update +++ b/gcloud/beta/managed-kafka/consumer-groups/update @@ -74,7 +74,7 @@ REQUIRED FLAGS --topics-file=JSON|YAML|FILE The path to the JSON or YAML file containing the configuration of the topics to be updated for the consumer group. This also supports inline - JSON or YAML. Required, Sets topics_file value. + JSON or YAML. Required, sets topics_file value. Input Example: diff --git a/gcloud/beta/monitoring/snoozes/create b/gcloud/beta/monitoring/snoozes/create index 407b1ec74..1b50145c7 100644 --- a/gcloud/beta/monitoring/snoozes/create +++ b/gcloud/beta/monitoring/snoozes/create @@ -50,15 +50,20 @@ FLAGS in the --snooze-from-file flags if specified. --criteria-filter=CRITERIA_FILTER - The filter that the Snooze applies to, which is a string to match on - Alert fields when silencing the alerts. It follows the standard - https://google.aip.dev/160 syntax. Filters can be defined for snoozes - that apply to one alerting policy. Filters must be a string formatted - as one or more resource labels with specific label values. If - multiple resource labels are used, then they must be connected with - an AND operator. For example: + Optional. When you define a Snooze, you can also define a filter for + that snooze. The filter is a string containing one or more key-value + pairs. The string uses the standard https://google.aip.dev/160 filter + syntax. If you define a filter for a snooze, then the snooze can only + apply to one alert policy. When the snooze is active, incidents won't + be created when the incident would have key-value pairs (labels) that + match those specified by the filter in the snooze. Snooze filters + support resource, metric, and metadata labels. If multiple labels are + used, then they must be connected with an AND operator. For example: resource.labels.instance_id="1234567890" AND - resource.labels.zone="us-central1-a" + resource.labels.zone="us-central1-a" AND + metric.labels.instance_name="test_group" AND + metadata.user_labels.foo="bar" AND + metadata.system_labels.region="us-central1" --criteria-policies=CRITERIA_POLICIES,[...] The policies that the Snooze applies to. Exactly 1 alert policy is diff --git a/gcloud/beta/netapp/volumes/replications/create b/gcloud/beta/netapp/volumes/replications/create index a0df60e5f..a714ef890 100644 --- a/gcloud/beta/netapp/volumes/replications/create +++ b/gcloud/beta/netapp/volumes/replications/create @@ -65,7 +65,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --destination-volume-parameters=[description=DESCRIPTION],[share_name=SHARE_NAME],[storage_pool=STORAGE_POOL],[tiering_policy=TIERING_POLICY],[volume_id=VOLUME_ID] - Required, Sets destination_volume_parameters value. + Required, sets destination_volume_parameters value. description Sets description value. @@ -74,7 +74,7 @@ REQUIRED FLAGS Sets share_name value. storage_pool - Required, Sets storage_pool value. + Required, sets storage_pool value. tiering_policy Sets tiering_policy value. diff --git a/gcloud/beta/network-connectivity/hubs/update b/gcloud/beta/network-connectivity/hubs/update index 2e094b3db..e9a1b7073 100644 --- a/gcloud/beta/network-connectivity/hubs/update +++ b/gcloud/beta/network-connectivity/hubs/update @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud beta network-connectivity hubs update HUB [--async] - [--description=DESCRIPTION] [--export-psc] + [--description=DESCRIPTION] [--[no-]export-psc] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -14,7 +14,7 @@ EXAMPLES To update the description of a hub named my-hub, run: $ gcloud beta network-connectivity hubs update my-hub \ - --description="The new description of my-hub". + --description="The new description of my-hub". POSITIONAL ARGUMENTS Hub resource - Name of the hub to be updated. This represents a Cloud @@ -43,8 +43,9 @@ FLAGS --description=DESCRIPTION New description of the hub. - --export-psc + --[no-]export-psc Whether Private Service Connect transitivity is enabled for the hub. + Use --export-psc to enable and --no-export-psc to disable. --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value diff --git a/gcloud/beta/network-security/intercept-deployment-groups/create b/gcloud/beta/network-security/intercept-deployment-groups/create index 0e169356f..a6f82da22 100644 --- a/gcloud/beta/network-security/intercept-deployment-groups/create +++ b/gcloud/beta/network-security/intercept-deployment-groups/create @@ -127,8 +127,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 network-security intercept-deployment-groups create $ gcloud alpha network-security intercept-deployment-groups create diff --git a/gcloud/beta/network-security/intercept-deployment-groups/delete b/gcloud/beta/network-security/intercept-deployment-groups/delete index 398c10382..c4c6215d0 100644 --- a/gcloud/beta/network-security/intercept-deployment-groups/delete +++ b/gcloud/beta/network-security/intercept-deployment-groups/delete @@ -81,8 +81,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 network-security intercept-deployment-groups delete $ gcloud alpha network-security intercept-deployment-groups delete diff --git a/gcloud/beta/network-security/intercept-deployment-groups/describe b/gcloud/beta/network-security/intercept-deployment-groups/describe index 293255aa0..e5dc69c5c 100644 --- a/gcloud/beta/network-security/intercept-deployment-groups/describe +++ b/gcloud/beta/network-security/intercept-deployment-groups/describe @@ -67,8 +67,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 network-security intercept-deployment-groups describe $ gcloud alpha network-security intercept-deployment-groups describe diff --git a/gcloud/beta/network-security/intercept-deployment-groups/help b/gcloud/beta/network-security/intercept-deployment-groups/help index a3cbbc439..c5e904d5c 100644 --- a/gcloud/beta/network-security/intercept-deployment-groups/help +++ b/gcloud/beta/network-security/intercept-deployment-groups/help @@ -37,8 +37,10 @@ COMMANDS (BETA) Update an Intercept Deployment Group. 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 network-security intercept-deployment-groups $ gcloud alpha network-security intercept-deployment-groups diff --git a/gcloud/beta/network-security/intercept-deployment-groups/list b/gcloud/beta/network-security/intercept-deployment-groups/list index b4fcf3799..5c74c6048 100644 --- a/gcloud/beta/network-security/intercept-deployment-groups/list +++ b/gcloud/beta/network-security/intercept-deployment-groups/list @@ -85,8 +85,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 network-security intercept-deployment-groups list $ gcloud alpha network-security intercept-deployment-groups list diff --git a/gcloud/beta/network-security/intercept-deployment-groups/update b/gcloud/beta/network-security/intercept-deployment-groups/update index 5bc06ada5..ea6dc65c5 100644 --- a/gcloud/beta/network-security/intercept-deployment-groups/update +++ b/gcloud/beta/network-security/intercept-deployment-groups/update @@ -128,8 +128,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 network-security intercept-deployment-groups update $ gcloud alpha network-security intercept-deployment-groups update diff --git a/gcloud/beta/network-security/intercept-deployments/create b/gcloud/beta/network-security/intercept-deployments/create index a96e688ab..109417a1c 100644 --- a/gcloud/beta/network-security/intercept-deployments/create +++ b/gcloud/beta/network-security/intercept-deployments/create @@ -192,8 +192,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 network-security intercept-deployments create $ gcloud alpha network-security intercept-deployments create diff --git a/gcloud/beta/network-security/intercept-deployments/delete b/gcloud/beta/network-security/intercept-deployments/delete index 8a33c6632..b45aeb6e0 100644 --- a/gcloud/beta/network-security/intercept-deployments/delete +++ b/gcloud/beta/network-security/intercept-deployments/delete @@ -73,8 +73,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 network-security intercept-deployments delete $ gcloud alpha network-security intercept-deployments delete diff --git a/gcloud/beta/network-security/intercept-deployments/describe b/gcloud/beta/network-security/intercept-deployments/describe index 4ee9673ac..8c6ac10ba 100644 --- a/gcloud/beta/network-security/intercept-deployments/describe +++ b/gcloud/beta/network-security/intercept-deployments/describe @@ -65,8 +65,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 network-security intercept-deployments describe $ gcloud alpha network-security intercept-deployments describe diff --git a/gcloud/beta/network-security/intercept-deployments/help b/gcloud/beta/network-security/intercept-deployments/help index 80c25bdb3..8ce7db004 100644 --- a/gcloud/beta/network-security/intercept-deployments/help +++ b/gcloud/beta/network-security/intercept-deployments/help @@ -34,8 +34,10 @@ COMMANDS (BETA) Update an Intercept Deployment. 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 network-security intercept-deployments $ gcloud alpha network-security intercept-deployments diff --git a/gcloud/beta/network-security/intercept-deployments/list b/gcloud/beta/network-security/intercept-deployments/list index ce67069e4..7e4a239fc 100644 --- a/gcloud/beta/network-security/intercept-deployments/list +++ b/gcloud/beta/network-security/intercept-deployments/list @@ -86,8 +86,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 network-security intercept-deployments list $ gcloud alpha network-security intercept-deployments list diff --git a/gcloud/beta/network-security/intercept-deployments/update b/gcloud/beta/network-security/intercept-deployments/update index 86c6a6ccd..354a85837 100644 --- a/gcloud/beta/network-security/intercept-deployments/update +++ b/gcloud/beta/network-security/intercept-deployments/update @@ -126,8 +126,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 network-security intercept-deployments update $ gcloud alpha network-security intercept-deployments update diff --git a/gcloud/beta/network-security/intercept-endpoint-group-associations/create b/gcloud/beta/network-security/intercept-endpoint-group-associations/create index 66ce6ef65..1a339664b 100644 --- a/gcloud/beta/network-security/intercept-endpoint-group-associations/create +++ b/gcloud/beta/network-security/intercept-endpoint-group-associations/create @@ -162,8 +162,11 @@ 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 network-security intercept-endpoint-group-associations \ + create $ gcloud alpha network-security \ intercept-endpoint-group-associations create diff --git a/gcloud/beta/network-security/intercept-endpoint-group-associations/delete b/gcloud/beta/network-security/intercept-endpoint-group-associations/delete index bdd7f3e6f..d861e8538 100644 --- a/gcloud/beta/network-security/intercept-endpoint-group-associations/delete +++ b/gcloud/beta/network-security/intercept-endpoint-group-associations/delete @@ -81,8 +81,11 @@ 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 network-security intercept-endpoint-group-associations \ + delete $ gcloud alpha network-security \ intercept-endpoint-group-associations delete diff --git a/gcloud/beta/network-security/intercept-endpoint-group-associations/describe b/gcloud/beta/network-security/intercept-endpoint-group-associations/describe index 5a17d8a5a..5aa89cf3c 100644 --- a/gcloud/beta/network-security/intercept-endpoint-group-associations/describe +++ b/gcloud/beta/network-security/intercept-endpoint-group-associations/describe @@ -67,8 +67,11 @@ 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 network-security intercept-endpoint-group-associations \ + describe $ gcloud alpha network-security \ intercept-endpoint-group-associations describe diff --git a/gcloud/beta/network-security/intercept-endpoint-group-associations/help b/gcloud/beta/network-security/intercept-endpoint-group-associations/help index 1078cf525..10c89bf32 100644 --- a/gcloud/beta/network-security/intercept-endpoint-group-associations/help +++ b/gcloud/beta/network-security/intercept-endpoint-group-associations/help @@ -34,8 +34,10 @@ COMMANDS (BETA) Update an Intercept Endpoint Group Association. 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 network-security intercept-endpoint-group-associations $ gcloud alpha network-security intercept-endpoint-group-associations diff --git a/gcloud/beta/network-security/intercept-endpoint-group-associations/list b/gcloud/beta/network-security/intercept-endpoint-group-associations/list index e7b9bdebc..f52f8952f 100644 --- a/gcloud/beta/network-security/intercept-endpoint-group-associations/list +++ b/gcloud/beta/network-security/intercept-endpoint-group-associations/list @@ -91,8 +91,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 network-security intercept-endpoint-group-associations list $ gcloud alpha network-security \ intercept-endpoint-group-associations list diff --git a/gcloud/beta/network-security/intercept-endpoint-group-associations/update b/gcloud/beta/network-security/intercept-endpoint-group-associations/update index 8e84497d8..831f944c3 100644 --- a/gcloud/beta/network-security/intercept-endpoint-group-associations/update +++ b/gcloud/beta/network-security/intercept-endpoint-group-associations/update @@ -117,8 +117,11 @@ 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 network-security intercept-endpoint-group-associations \ + update $ gcloud alpha network-security \ intercept-endpoint-group-associations update diff --git a/gcloud/beta/network-security/intercept-endpoint-groups/create b/gcloud/beta/network-security/intercept-endpoint-groups/create index fc0f16b6a..9c8e0c98d 100644 --- a/gcloud/beta/network-security/intercept-endpoint-groups/create +++ b/gcloud/beta/network-security/intercept-endpoint-groups/create @@ -149,8 +149,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 network-security intercept-endpoint-groups create $ gcloud alpha network-security intercept-endpoint-groups create diff --git a/gcloud/beta/network-security/intercept-endpoint-groups/delete b/gcloud/beta/network-security/intercept-endpoint-groups/delete index de763b72b..18b335f95 100644 --- a/gcloud/beta/network-security/intercept-endpoint-groups/delete +++ b/gcloud/beta/network-security/intercept-endpoint-groups/delete @@ -79,8 +79,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 network-security intercept-endpoint-groups delete $ gcloud alpha network-security intercept-endpoint-groups delete diff --git a/gcloud/beta/network-security/intercept-endpoint-groups/describe b/gcloud/beta/network-security/intercept-endpoint-groups/describe index 81b38b31b..14e2be4d3 100644 --- a/gcloud/beta/network-security/intercept-endpoint-groups/describe +++ b/gcloud/beta/network-security/intercept-endpoint-groups/describe @@ -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 network-security intercept-endpoint-groups describe $ gcloud alpha network-security intercept-endpoint-groups describe diff --git a/gcloud/beta/network-security/intercept-endpoint-groups/help b/gcloud/beta/network-security/intercept-endpoint-groups/help index b78f213ba..55f844587 100644 --- a/gcloud/beta/network-security/intercept-endpoint-groups/help +++ b/gcloud/beta/network-security/intercept-endpoint-groups/help @@ -34,8 +34,10 @@ COMMANDS (BETA) Update a Intercept Endpoint Group. 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 network-security intercept-endpoint-groups $ gcloud alpha network-security intercept-endpoint-groups diff --git a/gcloud/beta/network-security/intercept-endpoint-groups/list b/gcloud/beta/network-security/intercept-endpoint-groups/list index ba055deb3..5a14aec47 100644 --- a/gcloud/beta/network-security/intercept-endpoint-groups/list +++ b/gcloud/beta/network-security/intercept-endpoint-groups/list @@ -93,8 +93,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 network-security intercept-endpoint-groups list $ gcloud alpha network-security intercept-endpoint-groups list diff --git a/gcloud/beta/network-security/intercept-endpoint-groups/update b/gcloud/beta/network-security/intercept-endpoint-groups/update index f1c176361..82dc267d4 100644 --- a/gcloud/beta/network-security/intercept-endpoint-groups/update +++ b/gcloud/beta/network-security/intercept-endpoint-groups/update @@ -128,8 +128,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 network-security intercept-endpoint-groups update $ gcloud alpha network-security intercept-endpoint-groups update diff --git a/gcloud/beta/network-security/security-profile-groups/create b/gcloud/beta/network-security/security-profile-groups/create index e141606ed..7c27cb47e 100644 --- a/gcloud/beta/network-security/security-profile-groups/create +++ b/gcloud/beta/network-security/security-profile-groups/create @@ -5,14 +5,10 @@ NAME SYNOPSIS gcloud beta network-security security-profile-groups create (SECURITY_PROFILE_GROUP - : --location=LOCATION --organization=ORGANIZATION) [--async] - [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--custom-intercept-profile=CUSTOM_INTERCEPT_PROFILE - : --custom-intercept-profile-location=CUSTOM_INTERCEPT_PROFILE_LOCATION --custom-intercept-profile-organization=CUSTOM_INTERCEPT_PROFILE_ORGANIZATION] - [--custom-mirroring-profile=CUSTOM_MIRRORING_PROFILE - : --custom-mirroring-profile-location=CUSTOM_MIRRORING_PROFILE_LOCATION --custom-mirroring-profile-organization=CUSTOM_MIRRORING_PROFILE_ORGANIZATION] - [--threat-prevention-profile=THREAT_PREVENTION_PROFILE - : --threat-prevention-profile-location=THREAT_PREVENTION_PROFILE_LOCATION --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION] + : --location=LOCATION --organization=ORGANIZATION) + ([--custom-intercept-profile=CUSTOM_INTERCEPT_PROFILE + : --custom-intercept-profile-location=CUSTOM_INTERCEPT_PROFILE_LOCATION --custom-intercept-profile-organization=CUSTOM_INTERCEPT_PROFILE_ORGANIZATION] [--custom-mirroring-profile=CUSTOM_MIRRORING_PROFILE : --custom-mirroring-profile-location=CUSTOM_MIRRORING_PROFILE_LOCATION --custom-mirroring-profile-organization=CUSTOM_MIRRORING_PROFILE_ORGANIZATION] [--threat-prevention-profile=THREAT_PREVENTION_PROFILE : --threat-prevention-profile-location=THREAT_PREVENTION_PROFILE_LOCATION --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION]) + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -63,7 +59,140 @@ POSITIONAL ARGUMENTS with a fully specified name; ▸ provide the argument --organization on the command line. -FLAGS +REQUIRED FLAGS + At least one of these must be specified: + + Security Profile resource - Path to Security Profile resource. The + arguments in this group can be used to specify the attributes of this + resource. + + --custom-intercept-profile=CUSTOM_INTERCEPT_PROFILE + ID of the Security Profile or fully qualified identifier for the + Security Profile. + + To set the name attribute: + ▫ provide the argument --custom-intercept-profile on the command + line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --custom-intercept-profile-location=CUSTOM_INTERCEPT_PROFILE_LOCATION + Location of the Security Profile. NOTE: Only global security + profiles are supported. + + To set the location attribute: + ▫ provide the argument --custom-intercept-profile on the command + line with a fully specified name; + ▫ provide the argument --custom-intercept-profile-location on the + command line; + ▫ provide the argument --location on the command line; + ▫ provide the argument + networksecurity.organizations.locations.securityProfileGroups on + the command line with a fully specified name. + + --custom-intercept-profile-organization=CUSTOM_INTERCEPT_PROFILE_ORGANIZATION + Organization ID of the Security Profile. + + To set the organization attribute: + ▫ provide the argument --custom-intercept-profile on the command + line with a fully specified name; + ▫ provide the argument --custom-intercept-profile-organization on + the command line; + ▫ provide the argument --organization on the command line; + ▫ provide the argument + networksecurity.organizations.locations.securityProfileGroups on + the command line with a fully specified name. + + Security Profile resource - Path to Security Profile resource. The + arguments in this group can be used to specify the attributes of this + resource. + + --custom-mirroring-profile=CUSTOM_MIRRORING_PROFILE + ID of the Security Profile or fully qualified identifier for the + Security Profile. + + To set the name attribute: + ▫ provide the argument --custom-mirroring-profile on the command + line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --custom-mirroring-profile-location=CUSTOM_MIRRORING_PROFILE_LOCATION + Location of the Security Profile. NOTE: Only global security + profiles are supported. + + To set the location attribute: + ▫ provide the argument --custom-mirroring-profile on the command + line with a fully specified name; + ▫ provide the argument --custom-mirroring-profile-location on the + command line; + ▫ provide the argument --location on the command line; + ▫ provide the argument + networksecurity.organizations.locations.securityProfileGroups on + the command line with a fully specified name. + + --custom-mirroring-profile-organization=CUSTOM_MIRRORING_PROFILE_ORGANIZATION + Organization ID of the Security Profile. + + To set the organization attribute: + ▫ provide the argument --custom-mirroring-profile on the command + line with a fully specified name; + ▫ provide the argument --custom-mirroring-profile-organization on + the command line; + ▫ provide the argument --organization on the command line; + ▫ provide the argument + networksecurity.organizations.locations.securityProfileGroups on + the command line with a fully specified name. + + Security Profile resource - Path to Security Profile resource. The + arguments in this group can be used to specify the attributes of this + resource. + + --threat-prevention-profile=THREAT_PREVENTION_PROFILE + ID of the Security Profile or fully qualified identifier for the + Security Profile. + + To set the name attribute: + ▫ provide the argument --threat-prevention-profile on the command + line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --threat-prevention-profile-location=THREAT_PREVENTION_PROFILE_LOCATION + Location of the Security Profile. NOTE: Only global security + profiles are supported. + + To set the location attribute: + ▫ provide the argument --threat-prevention-profile on the command + line with a fully specified name; + ▫ provide the argument --threat-prevention-profile-location on + the command line; + ▫ provide the argument --security-profile-location on the command + line; + ▫ provide the argument --location on the command line; + ▫ provide the argument + networksecurity.organizations.locations.securityProfileGroups on + the command line with a fully specified name. + + --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION + Organization ID of the Security Profile. + + To set the organization attribute: + ▫ provide the argument --threat-prevention-profile on the command + line with a fully specified name; + ▫ provide the argument --threat-prevention-profile-organization + on the command line; + ▫ provide the argument --security-profile-organization on the + command line; + ▫ provide the argument --organization on the command line; + ▫ provide the argument + networksecurity.organizations.locations.securityProfileGroups on + the command line with a fully specified name. + +OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to complete. The default is False. @@ -79,136 +208,6 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - Security Profile resource - Path to Security Profile resource. The - arguments in this group can be used to specify the attributes of this - resource. - - --custom-intercept-profile=CUSTOM_INTERCEPT_PROFILE - ID of the Security Profile or fully qualified identifier for the - Security Profile. - - To set the custom-intercept-profile-profile attribute: - ▸ provide the argument --custom-intercept-profile on the command - line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --custom-intercept-profile-location=CUSTOM_INTERCEPT_PROFILE_LOCATION - Location of the Security Profile. NOTE: Only global security profiles - are supported. - - To set the custom-intercept-profile-location attribute: - ▸ provide the argument --custom-intercept-profile on the command - line with a fully specified name; - ▸ provide the argument --custom-intercept-profile-location on the - command line; - ▸ provide the argument --location on the command line; - ▸ provide the argument - networksecurity.organizations.locations.securityProfileGroups on - the command line with a fully specified name. - - --custom-intercept-profile-organization=CUSTOM_INTERCEPT_PROFILE_ORGANIZATION - Organization ID of the Security Profile. - - To set the custom-intercept-profile-organization attribute: - ▸ provide the argument --custom-intercept-profile on the command - line with a fully specified name; - ▸ provide the argument --custom-intercept-profile-organization on - the command line; - ▸ provide the argument --organization on the command line; - ▸ provide the argument - networksecurity.organizations.locations.securityProfileGroups on - the command line with a fully specified name. - - Security Profile resource - Path to Security Profile resource. The - arguments in this group can be used to specify the attributes of this - resource. - - --custom-mirroring-profile=CUSTOM_MIRRORING_PROFILE - ID of the Security Profile or fully qualified identifier for the - Security Profile. - - To set the custom-mirroring-profile-profile attribute: - ▸ provide the argument --custom-mirroring-profile on the command - line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --custom-mirroring-profile-location=CUSTOM_MIRRORING_PROFILE_LOCATION - Location of the Security Profile. NOTE: Only global security profiles - are supported. - - To set the custom-mirroring-profile-location attribute: - ▸ provide the argument --custom-mirroring-profile on the command - line with a fully specified name; - ▸ provide the argument --custom-mirroring-profile-location on the - command line; - ▸ provide the argument --location on the command line; - ▸ provide the argument - networksecurity.organizations.locations.securityProfileGroups on - the command line with a fully specified name. - - --custom-mirroring-profile-organization=CUSTOM_MIRRORING_PROFILE_ORGANIZATION - Organization ID of the Security Profile. - - To set the custom-mirroring-profile-organization attribute: - ▸ provide the argument --custom-mirroring-profile on the command - line with a fully specified name; - ▸ provide the argument --custom-mirroring-profile-organization on - the command line; - ▸ provide the argument --organization on the command line; - ▸ provide the argument - networksecurity.organizations.locations.securityProfileGroups on - the command line with a fully specified name. - - Security Profile resource - Path to Security Profile resource. The - arguments in this group can be used to specify the attributes of this - resource. - - --threat-prevention-profile=THREAT_PREVENTION_PROFILE - ID of the Security Profile or fully qualified identifier for the - Security Profile. - - To set the threat-prevention-profile-profile attribute: - ▸ provide the argument --threat-prevention-profile on the command - line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --threat-prevention-profile-location=THREAT_PREVENTION_PROFILE_LOCATION - Location of the Security Profile. NOTE: Only global security profiles - are supported. - - To set the threat-prevention-profile-location attribute: - ▸ provide the argument --threat-prevention-profile on the command - line with a fully specified name; - ▸ provide the argument --threat-prevention-profile-location on the - command line; - ▸ provide the argument --security-profile-location on the command - line; - ▸ provide the argument --location on the command line; - ▸ provide the argument - networksecurity.organizations.locations.securityProfileGroups on - the command line with a fully specified name. - - --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION - Organization ID of the Security Profile. - - To set the threat-prevention-profile-organization attribute: - ▸ provide the argument --threat-prevention-profile on the command - line with a fully specified name; - ▸ provide the argument --threat-prevention-profile-organization on - the command line; - ▸ provide the argument --security-profile-organization on the - command line; - ▸ provide the argument --organization on the command line; - ▸ provide the argument - networksecurity.organizations.locations.securityProfileGroups on - the command line with a fully specified name. - 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-security/security-profile-groups/update b/gcloud/beta/network-security/security-profile-groups/update index 6f7866a7b..6265a3b7d 100644 --- a/gcloud/beta/network-security/security-profile-groups/update +++ b/gcloud/beta/network-security/security-profile-groups/update @@ -105,7 +105,7 @@ FLAGS ID of the Security Profile or fully qualified identifier for the Security Profile. - To set the threat-prevention-profile-profile attribute: + To set the name attribute: ▸ provide the argument --threat-prevention-profile on the command line. @@ -116,7 +116,7 @@ FLAGS Location of the Security Profile. NOTE: Only global security profiles are supported. - To set the threat-prevention-profile-location attribute: + To set the location attribute: ▸ provide the argument --threat-prevention-profile on the command line with a fully specified name; ▸ provide the argument --threat-prevention-profile-location on the @@ -131,7 +131,7 @@ FLAGS --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION Organization ID of the Security Profile. - To set the threat-prevention-profile-organization attribute: + To set the organization attribute: ▸ provide the argument --threat-prevention-profile on the command line with a fully specified name; ▸ provide the argument --threat-prevention-profile-organization on diff --git a/gcloud/beta/network-security/security-profiles/custom-intercept/create b/gcloud/beta/network-security/security-profiles/custom-intercept/create index f2ac6b01d..cc0c317dd 100644 --- a/gcloud/beta/network-security/security-profiles/custom-intercept/create +++ b/gcloud/beta/network-security/security-profiles/custom-intercept/create @@ -117,8 +117,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 network-security security-profiles custom-intercept create $ gcloud alpha network-security security-profiles custom-intercept \ create diff --git a/gcloud/beta/network-security/security-profiles/custom-intercept/delete b/gcloud/beta/network-security/security-profiles/custom-intercept/delete index f2f407e6d..38ff6e869 100644 --- a/gcloud/beta/network-security/security-profiles/custom-intercept/delete +++ b/gcloud/beta/network-security/security-profiles/custom-intercept/delete @@ -68,8 +68,10 @@ API REFERENCE 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 network-security security-profiles custom-intercept delete $ gcloud alpha network-security security-profiles custom-intercept \ delete diff --git a/gcloud/beta/network-security/security-profiles/custom-intercept/describe b/gcloud/beta/network-security/security-profiles/custom-intercept/describe index 58289d950..ddad18b65 100644 --- a/gcloud/beta/network-security/security-profiles/custom-intercept/describe +++ b/gcloud/beta/network-security/security-profiles/custom-intercept/describe @@ -63,8 +63,10 @@ API REFERENCE 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 network-security security-profiles custom-intercept describe $ gcloud alpha network-security security-profiles custom-intercept \ describe diff --git a/gcloud/beta/network-security/security-profiles/custom-intercept/help b/gcloud/beta/network-security/security-profiles/custom-intercept/help index fb02619cc..62682e4ca 100644 --- a/gcloud/beta/network-security/security-profiles/custom-intercept/help +++ b/gcloud/beta/network-security/security-profiles/custom-intercept/help @@ -34,8 +34,10 @@ COMMANDS (BETA) Updates a Custom Intercept Profile. 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 network-security security-profiles custom-intercept $ gcloud alpha network-security security-profiles custom-intercept diff --git a/gcloud/beta/network-security/security-profiles/custom-intercept/list b/gcloud/beta/network-security/security-profiles/custom-intercept/list index c54cec19d..b68ab7803 100644 --- a/gcloud/beta/network-security/security-profiles/custom-intercept/list +++ b/gcloud/beta/network-security/security-profiles/custom-intercept/list @@ -80,8 +80,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 network-security security-profiles custom-intercept list $ gcloud alpha network-security security-profiles custom-intercept \ list diff --git a/gcloud/beta/network-security/security-profiles/custom-intercept/update b/gcloud/beta/network-security/security-profiles/custom-intercept/update index e571defde..373a2be53 100644 --- a/gcloud/beta/network-security/security-profiles/custom-intercept/update +++ b/gcloud/beta/network-security/security-profiles/custom-intercept/update @@ -109,8 +109,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 network-security security-profiles custom-intercept update $ gcloud alpha network-security security-profiles custom-intercept \ update diff --git a/gcloud/beta/network-services/service-lb-policies/create b/gcloud/beta/network-services/service-lb-policies/create index 6a7d8d093..7563ee3c7 100644 --- a/gcloud/beta/network-services/service-lb-policies/create +++ b/gcloud/beta/network-services/service-lb-policies/create @@ -7,6 +7,9 @@ SYNOPSIS (SERVICE_LB_POLICY : --location=LOCATION) [--async] [--auto-capacity-drain] [--description=DESCRIPTION] [--failover-health-threshold=FAILOVER_HEALTH_THRESHOLD] + [--isolation-config-granularity=ISOLATION_CONFIG_GRANULARITY; + default="unspecified"] + [--isolation-config-mode=ISOLATION_CONFIG_MODE; default="unspecified"] [--load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region"] [GCLOUD_WIDE_FLAG ...] @@ -77,6 +80,31 @@ FLAGS 99. The default value is 50 for Proxyless service mesh, and 70 for others. + --isolation-config-granularity=ISOLATION_CONFIG_GRANULARITY; default="unspecified" + The granularity of the isolation. ISOLATION_CONFIG_GRANULARITY must be + one of: + + region + Traffic for this service will be isolated at the nearest cloud + region. + + unspecified + No isolation is configured for the backend service. Traffic can + overflow based on the load balancing algorithm. + + --isolation-config-mode=ISOLATION_CONFIG_MODE; default="unspecified" + The granularity of the isolation. ISOLATION_CONFIG_MODE must be one of: + + nearest + Traffic will be sent to the nearest location. + + strict + Traffic will fail if no serving backends are available in the same + region as the load balancer. + + unspecified + No isolation mode is configured for the backend service. + --load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region" The global load balancing algorithm to be used. LOAD_BALANCING_ALGORITHM must be one of: diff --git a/gcloud/beta/network-services/service-lb-policies/update b/gcloud/beta/network-services/service-lb-policies/update index c39c9e396..5b709fca4 100644 --- a/gcloud/beta/network-services/service-lb-policies/update +++ b/gcloud/beta/network-services/service-lb-policies/update @@ -7,6 +7,9 @@ SYNOPSIS (SERVICE_LB_POLICY : --location=LOCATION) [--async] [--auto-capacity-drain] [--description=DESCRIPTION] [--failover-health-threshold=FAILOVER_HEALTH_THRESHOLD] + [--isolation-config-granularity=ISOLATION_CONFIG_GRANULARITY; + default="unspecified"] + [--isolation-config-mode=ISOLATION_CONFIG_MODE; default="unspecified"] [--load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region"] [GCLOUD_WIDE_FLAG ...] @@ -76,6 +79,31 @@ FLAGS 99. The default value is 50 for Proxyless service mesh, and 70 for others. + --isolation-config-granularity=ISOLATION_CONFIG_GRANULARITY; default="unspecified" + The granularity of the isolation. ISOLATION_CONFIG_GRANULARITY must be + one of: + + region + Traffic for this service will be isolated at the nearest cloud + region. + + unspecified + No isolation is configured for the backend service. Traffic can + overflow based on the load balancing algorithm. + + --isolation-config-mode=ISOLATION_CONFIG_MODE; default="unspecified" + The granularity of the isolation. ISOLATION_CONFIG_MODE must be one of: + + nearest + Traffic will be sent to the nearest location. + + strict + Traffic will fail if no serving backends are available in the same + region as the load balancer. + + unspecified + No isolation mode is configured for the backend service. + --load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region" The global load balancing algorithm to be used. LOAD_BALANCING_ALGORITHM must be one of: diff --git a/gcloud/beta/scc/findings/create b/gcloud/beta/scc/findings/create index e97753e88..cc814c133 100644 --- a/gcloud/beta/scc/findings/create +++ b/gcloud/beta/scc/findings/create @@ -116,11 +116,14 @@ OPTIONAL FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --source-properties=[KEY=VALUE,...] Source specific properties. These properties are managed by the source diff --git a/gcloud/beta/scc/findings/group b/gcloud/beta/scc/findings/group index 3672b7490..4ebec7848 100644 --- a/gcloud/beta/scc/findings/group +++ b/gcloud/beta/scc/findings/group @@ -131,11 +131,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --page-size=PAGE_SIZE Maximum number of results to return in a single response. Default is diff --git a/gcloud/beta/scc/findings/list b/gcloud/beta/scc/findings/list index 1ea87a987..db78fc97d 100644 --- a/gcloud/beta/scc/findings/list +++ b/gcloud/beta/scc/findings/list @@ -131,11 +131,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --order-by=ORDER_BY Expression that defines what fields and order to use for sorting. diff --git a/gcloud/beta/scc/findings/list-marks b/gcloud/beta/scc/findings/list-marks index 89916965b..13256eab1 100644 --- a/gcloud/beta/scc/findings/list-marks +++ b/gcloud/beta/scc/findings/list-marks @@ -46,11 +46,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --page-token=PAGE_TOKEN Response objects will return a non-null value for page-token to diff --git a/gcloud/beta/scc/findings/update b/gcloud/beta/scc/findings/update index a7c698a09..f7b498588 100644 --- a/gcloud/beta/scc/findings/update +++ b/gcloud/beta/scc/findings/update @@ -72,11 +72,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --source=SOURCE; default="-" Source id. Defaults to all sources. diff --git a/gcloud/beta/scc/findings/update-marks b/gcloud/beta/scc/findings/update-marks index cd8fb34ee..679a89f02 100644 --- a/gcloud/beta/scc/findings/update-marks +++ b/gcloud/beta/scc/findings/update-marks @@ -63,11 +63,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --security-marks=[KEY=VALUE,...] SecurityMarks resource to be passed as the request body. It's a diff --git a/gcloud/beta/spanner/instance-partitions/delete b/gcloud/beta/spanner/instance-partitions/delete index 74ac10175..a53264a62 100644 --- a/gcloud/beta/spanner/instance-partitions/delete +++ b/gcloud/beta/spanner/instance-partitions/delete @@ -1,13 +1,15 @@ NAME gcloud beta spanner instance-partitions delete - delete a Spanner instance - partition + partition. You can't delete the default instance partition using this + command SYNOPSIS gcloud beta spanner instance-partitions delete (INSTANCE_PARTITION : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete a Spanner instance partition. + (BETA) Delete a Spanner instance partition. You can't delete the default + instance partition using this command. EXAMPLES To delete a Spanner instance partition, run: diff --git a/gcloud/beta/spanner/instance-partitions/describe b/gcloud/beta/spanner/instance-partitions/describe index ac624a0c7..3f8d1aa87 100644 --- a/gcloud/beta/spanner/instance-partitions/describe +++ b/gcloud/beta/spanner/instance-partitions/describe @@ -1,5 +1,5 @@ NAME - gcloud beta spanner instance-partitions describe - describe a Cloud Spanner + gcloud beta spanner instance-partitions describe - describe a Spanner instance partition SYNOPSIS @@ -7,10 +7,10 @@ SYNOPSIS (INSTANCE_PARTITION : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe a Cloud Spanner instance partition. + (BETA) Describe a Spanner instance partition. EXAMPLES - To describe a Cloud Spanner instance partition, run: + To describe a Spanner instance partition, run: $ gcloud beta spanner instance-partitions describe \ my-instance-partition-id --instance=my-instance-id @@ -57,8 +57,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 spanner instance-partitions describe $ gcloud alpha spanner instance-partitions describe diff --git a/gcloud/beta/spanner/instance-partitions/help b/gcloud/beta/spanner/instance-partitions/help index 1b16966f4..973bf9c15 100644 --- a/gcloud/beta/spanner/instance-partitions/help +++ b/gcloud/beta/spanner/instance-partitions/help @@ -20,17 +20,19 @@ COMMANDS (BETA) Create a Spanner instance partition. delete - (BETA) Delete a Spanner instance partition. + (BETA) Delete a Spanner instance partition. You can't delete the + default instance partition using this command. describe - (BETA) Describe a Cloud Spanner instance partition. + (BETA) Describe a Spanner instance partition. list - (BETA) List the Cloud Spanner instance partitions contained within the - given instance. + (BETA) List the Spanner instance partitions contained within the given + instance. update - (BETA) Update a Cloud Spanner instance partition. + (BETA) Update a Spanner instance partition. You can't update the + default instance partition using this command. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/spanner/instance-partitions/list b/gcloud/beta/spanner/instance-partitions/list index 33cb90c9c..79bb7a589 100644 --- a/gcloud/beta/spanner/instance-partitions/list +++ b/gcloud/beta/spanner/instance-partitions/list @@ -1,6 +1,6 @@ NAME - gcloud beta spanner instance-partitions list - list the Cloud Spanner - instance partitions contained within the given instance + gcloud beta spanner instance-partitions list - list the Spanner instance + partitions contained within the given instance SYNOPSIS gcloud beta spanner instance-partitions list [--instance=INSTANCE] @@ -8,11 +8,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List the Cloud Spanner instance partitions contained within the - given instance. + (BETA) List the Spanner instance partitions contained within the given + instance. EXAMPLES - To list all Cloud Spanner instances partitions in an instance, run: + To list all Spanner instances partitions in an instance, run: $ gcloud beta spanner instance-partitions list \ --instance=my-instance-id @@ -70,8 +70,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 spanner instance-partitions list $ gcloud alpha spanner instance-partitions list diff --git a/gcloud/beta/spanner/instance-partitions/update b/gcloud/beta/spanner/instance-partitions/update index 22fbfae5a..b16eb0b6d 100644 --- a/gcloud/beta/spanner/instance-partitions/update +++ b/gcloud/beta/spanner/instance-partitions/update @@ -1,6 +1,7 @@ NAME - gcloud beta spanner instance-partitions update - update a Cloud Spanner - instance partition + gcloud beta spanner instance-partitions update - update a Spanner instance + partition. You can't update the default instance partition using this + command SYNOPSIS gcloud beta spanner instance-partitions update @@ -10,16 +11,17 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update a Cloud Spanner instance partition. + (BETA) Update a Spanner instance partition. You can't update the default + instance partition using this command. EXAMPLES - To update the display name of a Cloud Spanner instance partition, run: + To update the display name of a Spanner instance partition, run: $ gcloud beta spanner instance-partitions update \ my-instance-partition-id --instance=my-instance-id \ --description=my-new-display-name - To update the node count of a Cloud Spanner instance partition, run: + To update the node count of a Spanner instance partition, run: $ gcloud beta spanner instance-partitions update \ my-instance-partition-id --instance=my-instance-id --nodes=1 @@ -82,8 +84,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 spanner instance-partitions update $ gcloud alpha spanner instance-partitions update diff --git a/gcloud/beta/spanner/instances/move b/gcloud/beta/spanner/instances/move index 19933a20c..c275098aa 100644 --- a/gcloud/beta/spanner/instances/move +++ b/gcloud/beta/spanner/instances/move @@ -42,7 +42,7 @@ OPTIONAL FLAGS KMS keys. Sets target_database_move_configs value. database-id - Required, Sets database-id value. + Required, sets database-id value. kms-key-names Sets kms-key-names value. diff --git a/gcloud/beta/spanner/operations/cancel b/gcloud/beta/spanner/operations/cancel index 192b5afd2..5edd398d1 100644 --- a/gcloud/beta/spanner/operations/cancel +++ b/gcloud/beta/spanner/operations/cancel @@ -26,8 +26,7 @@ EXAMPLES $ gcloud beta spanner operations cancel _auto_12345 \ --instance=my-instance-id --backup=my-backup-id - To cancel a Cloud Spanner instance partition operation with ID auto_12345, - run: + To cancel an instance partition operation with ID auto_12345, run: $ gcloud beta spanner operations cancel auto_12345 \ --instance=my-instance-id --instance-partition=my-partition-id @@ -55,7 +54,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/spanner/operations/list b/gcloud/beta/spanner/operations/list index 902c69f82..8442fe8e9 100644 --- a/gcloud/beta/spanner/operations/list +++ b/gcloud/beta/spanner/operations/list @@ -43,13 +43,13 @@ EXAMPLES $ gcloud beta spanner operations list --instance=my-instance-id \ --backup=my-backup-id --type=BACKUP - To list Cloud Spanner instance partition operations for an instance - partition, run: + To list instance partition operations for an instance partition, run: $ gcloud beta spanner operations list --instance=my-instance-id \ --instance-partition=my-partition-id --type=INSTANCE_PARTITION - To list Cloud Spanner instance partition operations for an instance, run: + To list instance partition operations for all instance partitions belonging + to this instance, run: $ gcloud beta spanner operations list --instance=my-instance-id \ --type=INSTANCE_PARTITION diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index aa2b1ffde..a4d605041 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -439,7 +439,7 @@ FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project Sets project value. diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index 13b000749..82e6083ac 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -616,7 +616,7 @@ FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project Sets project value. diff --git a/gcloud/beta/workstations/clusters/create b/gcloud/beta/workstations/clusters/create index d8c3cb29a..2461967ba 100644 --- a/gcloud/beta/workstations/clusters/create +++ b/gcloud/beta/workstations/clusters/create @@ -5,7 +5,8 @@ SYNOPSIS gcloud beta workstations clusters create (CLUSTER : --region=REGION) [--async] [--domain=DOMAIN] [--enable-private-endpoint] [--labels=[KEY=VALUE,...]] [--network=NETWORK] - [--subnetwork=SUBNETWORK] [GCLOUD_WIDE_FLAG ...] + [--subnetwork=SUBNETWORK] [--tags=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a workstation cluster. @@ -79,6 +80,10 @@ FLAGS --subnetwork=SUBNETWORK Fully specified subnetwork path for instances created in this cluster. + --tags=[KEY=VALUE,...] + Resource manager tags to be bound to this cluster. For example: + "123/environment=production" "123/costCenter=marketing" + 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/workstations/configs/create b/gcloud/beta/workstations/configs/create index 10e851561..65207156a 100644 --- a/gcloud/beta/workstations/configs/create +++ b/gcloud/beta/workstations/configs/create @@ -131,10 +131,10 @@ FLAGS Sets allowed_ports value. first - Required, Sets first value. + Required, sets first value. last - Required, Sets last value. + Required, sets last value. Shorthand Example: @@ -179,7 +179,7 @@ FLAGS Sets enable-nested-virtualization value. id - Required, Sets id value. + Required, sets id value. machine-type Sets machine-type value. diff --git a/gcloud/beta/workstations/configs/update b/gcloud/beta/workstations/configs/update index 055b50496..fe20d80be 100644 --- a/gcloud/beta/workstations/configs/update +++ b/gcloud/beta/workstations/configs/update @@ -112,10 +112,10 @@ FLAGS Sets allowed_ports value. first - Required, Sets first value. + Required, sets first value. last - Required, Sets last value. + Required, sets last value. Shorthand Example: @@ -160,7 +160,7 @@ FLAGS Sets enable-nested-virtualization value. id - Required, Sets id value. + Required, sets id value. machine-type Sets machine-type value. diff --git a/gcloud/composer/environments/storage/dags/delete b/gcloud/composer/environments/storage/dags/delete index df3c6d88b..4e34638f6 100644 --- a/gcloud/composer/environments/storage/dags/delete +++ b/gcloud/composer/environments/storage/dags/delete @@ -12,7 +12,7 @@ DESCRIPTION EXAMPLES To delete the dags in the path path/to/dags, for the environment named - environmnet-1 in the location us-east1, run: + environment-1 in the location us-east1, run: $ gcloud composer environments storage dags delete path/to/dags \ --environment=environment-1 --location=us-east1 diff --git a/gcloud/composer/environments/storage/dags/list b/gcloud/composer/environments/storage/dags/list index 352311899..258dd3476 100644 --- a/gcloud/composer/environments/storage/dags/list +++ b/gcloud/composer/environments/storage/dags/list @@ -11,7 +11,7 @@ DESCRIPTION List the DAG files for a Cloud Composer environment. EXAMPLES - To list the dags for the Cloud Composer environment environmnet-1 and + To list the dags for the Cloud Composer environment environment-1 and location us-central1, run: $ gcloud composer environments storage dags list \ diff --git a/gcloud/composer/environments/storage/data/delete b/gcloud/composer/environments/storage/data/delete index 91b19c81c..e12eae2b5 100644 --- a/gcloud/composer/environments/storage/data/delete +++ b/gcloud/composer/environments/storage/data/delete @@ -12,7 +12,7 @@ DESCRIPTION EXAMPLES To delete the data from the path path/to/data, for the environment named - environmnet-1 in the location us-east1, run: + environment-1 in the location us-east1, run: $ gcloud composer environments storage data delete path/to/data \ --environment=environment-1 --location=us-east1 diff --git a/gcloud/composer/environments/storage/data/list b/gcloud/composer/environments/storage/data/list index fd4a3e64b..9b00e76f7 100644 --- a/gcloud/composer/environments/storage/data/list +++ b/gcloud/composer/environments/storage/data/list @@ -11,7 +11,7 @@ DESCRIPTION List the data for a Cloud Composer environment. EXAMPLES - To list the data from the Cloud Composer environment environmnet-1 and + To list the data from the Cloud Composer environment environment-1 and location us-central1, run: $ gcloud composer environments storage data list \ diff --git a/gcloud/composer/environments/storage/plugins/delete b/gcloud/composer/environments/storage/plugins/delete index 2be3db73b..b0c414c4d 100644 --- a/gcloud/composer/environments/storage/plugins/delete +++ b/gcloud/composer/environments/storage/plugins/delete @@ -12,7 +12,7 @@ DESCRIPTION EXAMPLES To delete the plugins in the path path/to/plugins, for the environment - named environmnet-1 in the location us-east1, run: + named environment-1 in the location us-east1, run: $ gcloud composer environments storage plugins delete \ path/to/plugins --environment=environment-1 --location=us-east1 diff --git a/gcloud/composer/environments/storage/plugins/list b/gcloud/composer/environments/storage/plugins/list index 124d78438..6aef63c87 100644 --- a/gcloud/composer/environments/storage/plugins/list +++ b/gcloud/composer/environments/storage/plugins/list @@ -11,7 +11,7 @@ DESCRIPTION List the plugins for a Cloud Composer environment. EXAMPLES - To list the plugins for the Cloud Composer environment environmnet-1 and + To list the plugins for the Cloud Composer environment environment-1 and location us-central1, run: $ gcloud composer environments storage plugins list \ diff --git a/gcloud/compute/backend-services/add-backend b/gcloud/compute/backend-services/add-backend index f5857a7a2..38a7c41c6 100644 --- a/gcloud/compute/backend-services/add-backend +++ b/gcloud/compute/backend-services/add-backend @@ -282,7 +282,7 @@ OPTIONAL FLAGS Sets maxUtilization value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -315,7 +315,7 @@ OPTIONAL FLAGS Sets maxUtilization value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: diff --git a/gcloud/compute/backend-services/create b/gcloud/compute/backend-services/create index 3dc7d8345..1eb430dc1 100644 --- a/gcloud/compute/backend-services/create +++ b/gcloud/compute/backend-services/create @@ -774,7 +774,7 @@ FLAGS Sets dryRun value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -803,7 +803,7 @@ FLAGS Sets dryRun value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: diff --git a/gcloud/compute/backend-services/update b/gcloud/compute/backend-services/update index fa1a35e3f..b2a6295b5 100644 --- a/gcloud/compute/backend-services/update +++ b/gcloud/compute/backend-services/update @@ -16,6 +16,7 @@ SYNOPSIS [--description=DESCRIPTION] [--drop-traffic-if-unhealthy] [--edge-security-policy=EDGE_SECURITY_POLICY] [--[no-]enable-cdn] [--[no-]enable-logging] [--[no-]enable-strong-affinity] + [--external-managed-migration-testing-percentage=EXTERNAL_MANAGED_MIGRATION_TESTING_PERCENTAGE] [--failover-ratio=FAILOVER_RATIO] [--health-checks=HEALTH_CHECK,[...]] [--no-health-checks] [--http-health-checks=HTTP_HEALTH_CHECK,[...]] [--https-health-checks=HTTPS_HEALTH_CHECK,[...]] @@ -23,6 +24,7 @@ SYNOPSIS oauth2-client-secret=OAUTH2-CLIENT-SECRET]] [--idle-timeout-sec=IDLE_TIMEOUT_SEC] [--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY] + [--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--locality-lb-policy=LOCALITY_LB_POLICY] [--logging-optional=LOGGING_OPTIONAL] [--logging-optional-fields=[LOGGING_OPTIONAL_FIELDS,...]] @@ -39,6 +41,8 @@ SYNOPSIS | --cache-key-query-string-whitelist=QUERY_STRING,[...]] [--clear-custom-metrics | --custom-metrics=[CUSTOM_METRICS,...] | --custom-metrics-file=[CUSTOM_METRICS,...]] + [--clear-external-managed-migration-state + | --external-managed-migration-state=EXTERNAL_MANAGED_MIGRATION_STATE] [--client-ttl=CLIENT_TTL | --no-client-ttl] [--custom-request-header=CUSTOM_REQUEST_HEADER | --no-custom-request-headers] @@ -209,6 +213,12 @@ FLAGS loadbalancingScheme EXTERNAL. Use --enable-strong-affinity to enable and --no-enable-strong-affinity to disable. + --external-managed-migration-testing-percentage=EXTERNAL_MANAGED_MIGRATION_TESTING_PERCENTAGE + Determines the fraction of requests that should be processed by the + Global external Application Load Balancer. + + The value of this field must be in the range [0, 100]. + --failover-ratio=FAILOVER_RATIO Applicable only to backend service-based external passthrough Network load balancers and internal passthrough Network load balancers as part @@ -294,6 +304,13 @@ FLAGS IP_ADDRESS_SELECTION_POLICY must be one of: IPV4_ONLY, PREFER_IPV6, IPV6_ONLY. + --load-balancing-scheme=LOAD_BALANCING_SCHEME + Only for the Global external Application Load Balancer migration. + + The value of this field must be EXTERNAL or EXTERNAL_MANAGED. + + LOAD_BALANCING_SCHEME must be one of: EXTERNAL, EXTERNAL_MANAGED. + --locality-lb-policy=LOCALITY_LB_POLICY The load balancing algorithm used within the scope of the locality. LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN, @@ -603,7 +620,7 @@ FLAGS Sets dryRun value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -632,7 +649,7 @@ FLAGS Sets dryRun value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -646,6 +663,25 @@ FLAGS --custom-metrics-file=path_to_file.(yaml|json) + At most one of these can be specified: + + --clear-external-managed-migration-state + Clears current state of external managed migration. + + --external-managed-migration-state=EXTERNAL_MANAGED_MIGRATION_STATE + Specifies the migration state. Possible values are PREPARE, + TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. + + To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state + must be changed to PREPARE. The state must be changed to + TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to + EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be + used to migrate traffic by percentage using the + --external-managed-migration-testing-percentage flag. + + EXTERNAL_MANAGED_MIGRATION_STATE must be one of: PREPARE, + TEST_BY_PERCENTAGE, TEST_ALL_TRAFFIC. + At most one of these can be specified: --client-ttl=CLIENT_TTL diff --git a/gcloud/compute/backend-services/update-backend b/gcloud/compute/backend-services/update-backend index 41ff26d99..c50a88270 100644 --- a/gcloud/compute/backend-services/update-backend +++ b/gcloud/compute/backend-services/update-backend @@ -248,7 +248,7 @@ OPTIONAL FLAGS Sets maxUtilization value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: @@ -281,7 +281,7 @@ OPTIONAL FLAGS Sets maxUtilization value. name - Required, Sets name value. + Required, sets name value. Shorthand Example: diff --git a/gcloud/compute/firewall-policies/rules/create b/gcloud/compute/firewall-policies/rules/create index 437e2aaf4..684d9acfe 100644 --- a/gcloud/compute/firewall-policies/rules/create +++ b/gcloud/compute/firewall-policies/rules/create @@ -99,7 +99,7 @@ OPTIONAL FLAGS http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ - c) . In case "c" gCloud CLI will create a reference matching + c) . In case "c" gcloud CLI will create a reference matching format "a", but to make it work CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSECURITY property must be set. In order to set this property, please run the command gcloud config set diff --git a/gcloud/compute/firewall-policies/rules/update b/gcloud/compute/firewall-policies/rules/update index 1dc1c0c0f..f383bd6d1 100644 --- a/gcloud/compute/firewall-policies/rules/update +++ b/gcloud/compute/firewall-policies/rules/update @@ -105,7 +105,7 @@ OPTIONAL FLAGS http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ - c) . In case "c" gCloud CLI will create a reference matching + c) . In case "c" gcloud CLI will create a reference matching format "a", but to make it work CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSECURITY property must be set. In order to set this property, please run the command gcloud config set diff --git a/gcloud/compute/forwarding-rules/update b/gcloud/compute/forwarding-rules/update index 3e0222f40..de7279321 100644 --- a/gcloud/compute/forwarding-rules/update +++ b/gcloud/compute/forwarding-rules/update @@ -4,8 +4,13 @@ NAME SYNOPSIS gcloud compute forwarding-rules update NAME [--allow-global-access] - [--allow-psc-global-access] [--source-ip-ranges=SOURCE_IP_RANGE,[...]] + [--allow-psc-global-access] + [--external-managed-backend-bucket-migration-testing-percentage=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_TESTING_PERCENTAGE] + [--load-balancing-scheme=LOAD_BALANCING_SCHEME] + [--source-ip-ranges=SOURCE_IP_RANGE,[...]] [--update-labels=[KEY=VALUE,...]] + [--clear-external-managed-backend-bucket-migration-state + | --external-managed-backend-bucket-migration-state=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_STATE] [--clear-labels | --remove-labels=[KEY,...]] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] @@ -51,6 +56,19 @@ FLAGS Connect forwarding rule. This can only be specified if the forwarding rule's target is a service attachment (--target-service-attachment). + --external-managed-backend-bucket-migration-testing-percentage=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_TESTING_PERCENTAGE + Determines the fraction of requests that should be processed by the + Global external Application Load Balancer. + + The value of this field must be in the range [0, 100]. + + --load-balancing-scheme=LOAD_BALANCING_SCHEME + Only for the Global external Application Load Balancer migration. + + The value of this field must be EXTERNAL or EXTERNAL_MANAGED. + + LOAD_BALANCING_SCHEME must be one of: EXTERNAL, EXTERNAL_MANAGED. + --source-ip-ranges=SOURCE_IP_RANGE,[...] List of comma-separated IP addresses or IP ranges. If set, this forwarding rule only forwards traffic when the packet's source IP @@ -65,6 +83,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + At most one of these can be specified: + + --clear-external-managed-backend-bucket-migration-state + Clears current state of external managed migration. + + --external-managed-backend-bucket-migration-state=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_STATE + Specifies the migration state. Possible values are PREPARE, + TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. + + To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state + must be changed to PREPARE. The state must be changed to + TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to + EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be + used to migrate traffic to backend buckets attached to this + forwarding rule by percentage using the + --external-managed-backend-bucket-migration-testing-percentage flag. + + EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_STATE must be one of: + PREPARE, TEST_BY_PERCENTAGE, TEST_ALL_TRAFFIC. + At most one of these can be specified: --clear-labels diff --git a/gcloud/dataplex/encryption-config/create b/gcloud/dataplex/encryption-config/create new file mode 100644 index 000000000..115df1fa1 --- /dev/null +++ b/gcloud/dataplex/encryption-config/create @@ -0,0 +1,69 @@ +NAME + gcloud dataplex encryption-config create - create a Dataplex encryption + config resource + +SYNOPSIS + gcloud dataplex encryption-config create + (ENCRYPTION_CONFIG : --location=LOCATION --organization=ORGANIZATION) + [--key=KEY] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + An EncryptionConfig is created only for CMEK opted in organizations. + +EXAMPLES + To create an EncryptionConfig default in organization test-org-id at + location us-central1 with key test-key, run: $ gcloud dataplex encryption-config create default \ + --location=us-central1 --organization=test-org-id \ + --key='test-key' + +POSITIONAL ARGUMENTS + Encryption config resource - Arguments and flags that define the Dataplex + EncryptionConfig you want to create. The arguments in this group can be + used to specify the attributes of this resource. + + This must be specified. + + ENCRYPTION_CONFIG + ID of the encryption config or fully qualified identifier for the + encryption config. + + To set the encryption_config attribute: + ▸ provide the argument encryption_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 of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument encryption_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + + --organization=ORGANIZATION + The name of encryption config to use. + + To set the organization attribute: + ▸ provide the argument encryption_config on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. + +FLAGS + --key=KEY + The KMS key to use for encryption. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha dataplex encryption-config create + diff --git a/gcloud/dataplex/encryption-config/describe b/gcloud/dataplex/encryption-config/describe new file mode 100644 index 000000000..d688c3e60 --- /dev/null +++ b/gcloud/dataplex/encryption-config/describe @@ -0,0 +1,67 @@ +NAME + gcloud dataplex encryption-config describe - describe an EncryptionConfig + +SYNOPSIS + gcloud dataplex encryption-config describe + (ENCRYPTION_CONFIG : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an EncryptionConfig. Displays all the details of an + EncryptionConfig used for CMEK with valid organization and location. + +EXAMPLES + To describe an EncryptionConfig: $ gcloud dataplex encryption-config describe default \ + --location=us-central1 --organization=test-org + +POSITIONAL ARGUMENTS + Encryption config resource - encryption_config you want to Describe The + arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + ENCRYPTION_CONFIG + ID of the encryption config or fully qualified identifier for the + encryption config. + + To set the encryption_config attribute: + ▸ provide the argument encryption_config 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 encryption_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + + --organization=ORGANIZATION + Name of the Cloud organization to use. + + To set the organization attribute: + ▸ provide the argument encryption_config on the command line with a + fully specified name; + ▸ provide the argument --organization 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 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 encryption-config describe + diff --git a/gcloud/dataplex/encryption-config/help b/gcloud/dataplex/encryption-config/help new file mode 100644 index 000000000..93de71e7e --- /dev/null +++ b/gcloud/dataplex/encryption-config/help @@ -0,0 +1,28 @@ +NAME + gcloud dataplex encryption-config - manage Dataplex encryption configs + +SYNOPSIS + gcloud dataplex encryption-config COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Dataplex encryption configs. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a Dataplex encryption config resource. + + describe + Describe an EncryptionConfig. + +NOTES + This variant is also available: + + $ gcloud alpha dataplex encryption-config + diff --git a/gcloud/dataplex/glossaries/add-iam-policy-binding b/gcloud/dataplex/glossaries/add-iam-policy-binding new file mode 100644 index 000000000..ba77ce69c --- /dev/null +++ b/gcloud/dataplex/glossaries/add-iam-policy-binding @@ -0,0 +1,87 @@ +NAME + gcloud dataplex glossaries add-iam-policy-binding - add IAM policy binding + to a Dataplex Glossary + +SYNOPSIS + gcloud dataplex glossaries add-iam-policy-binding + (GLOSSARY : --location=LOCATION) --member=PRINCIPAL --role=ROLE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Add IAM policy binding to a Dataplex Glossary. + +EXAMPLES + To add an IAM policy binding for the role of roles/dataplex.viewer for the + user test-user@gmail.com to Glossary test-glossary in location us-central, + run: $ gcloud dataplex glossaries add-iam-policy-binding test-glossary \ + --project=test-project --location=us-central1 \ + --role=roles/dataplex.viewer --member=user:test-user@gmail.com \ + See https://cloud.google.com/dataplex/docs/iam-roles for \ + details of policy role and member types. + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + you want to add 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 glossaries add-iam-policy-binding + diff --git a/gcloud/dataplex/glossaries/categories/create b/gcloud/dataplex/glossaries/categories/create new file mode 100644 index 000000000..eb1082845 --- /dev/null +++ b/gcloud/dataplex/glossaries/categories/create @@ -0,0 +1,100 @@ +NAME + gcloud dataplex glossaries categories create - creates a glossary category + +SYNOPSIS + gcloud dataplex glossaries categories create + (GLOSSARY_CATEGORY : --glossary=GLOSSARY --location=LOCATION) + --parent=PARENT [--description=DESCRIPTION] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + A glossary category represents a collection of glossary categories and + glossary terms within a glossary that are related to each other. + +EXAMPLES + To create a glossary category test-category in glossary test-glossary in + project test-project in location us-central1, with description test + description, displayName displayName and parent + projects/test-project/locations/us-central1/glossaries/test-glossary , run: + + $ gcloud dataplex glossaries categories create test-category \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project \ + --parent='projects/test-project/locations/us-central1/glossaries\ + /test-glossary' --description='test description' \ + --display-name='displayName' + +POSITIONAL ARGUMENTS + Glossary category resource - Arguments and flags that define the Dataplex + Glossary Category 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 glossary_category 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. + + GLOSSARY_CATEGORY + ID of the glossary category or fully qualified identifier for the + glossary category. + + To set the glossary_category attribute: + ▸ provide the argument glossary_category on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + The name of glossary category to use. + + To set the glossary attribute: + ▸ provide the argument glossary_category on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + The location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_category on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + --parent=PARENT + Immediate parent of the created glossary category. + +OPTIONAL FLAGS + --description=DESCRIPTION + Description of the glossary category. + + --display-name=DISPLAY_NAME + Display name of the glossary category. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha dataplex glossaries categories create + diff --git a/gcloud/dataplex/glossaries/categories/delete b/gcloud/dataplex/glossaries/categories/delete new file mode 100644 index 000000000..b6fd0d45e --- /dev/null +++ b/gcloud/dataplex/glossaries/categories/delete @@ -0,0 +1,75 @@ +NAME + gcloud dataplex glossaries categories delete - deletes a glossary category + +SYNOPSIS + gcloud dataplex glossaries categories delete + (GLOSSARY_CATEGORY : --glossary=GLOSSARY --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Deletes a glossary category. + +EXAMPLES + To delete glossary category test-category in glossary test-glossary in + project test-project in location us-central1, run: $ gcloud dataplex glossaries categories delete test-category \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Glossary category resource - Arguments and flags that define the glossary + category you want 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 glossary_category 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. + + GLOSSARY_CATEGORY + ID of the glossary category or fully qualified identifier for the + glossary category. + + To set the glossary_category attribute: + ▸ provide the argument glossary_category on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + Identifier of the Dataplex Glossary resource. + + To set the glossary attribute: + ▸ provide the argument glossary_category on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_category 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 glossaries categories delete + diff --git a/gcloud/dataplex/glossaries/categories/describe b/gcloud/dataplex/glossaries/categories/describe new file mode 100644 index 000000000..2a18ef38e --- /dev/null +++ b/gcloud/dataplex/glossaries/categories/describe @@ -0,0 +1,76 @@ +NAME + gcloud dataplex glossaries categories describe - describes a glossary + category + +SYNOPSIS + gcloud dataplex glossaries categories describe + (GLOSSARY_CATEGORY : --glossary=GLOSSARY --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describes a glossary category. + +EXAMPLES + To describe a glossary category test-category in glossary test-glossary in + project test-project in loaction us-central1, run: $ gcloud dataplex glossaries categories describe test-category \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Glossary category resource - Arguments and flags that define the glossary + category 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 glossary_category 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. + + GLOSSARY_CATEGORY + ID of the glossary category or fully qualified identifier for the + glossary category. + + To set the glossary_category attribute: + ▸ provide the argument glossary_category on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + Identifier of the Dataplex Glossary resource. + + To set the glossary attribute: + ▸ provide the argument glossary_category on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_category 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 glossaries categories describe + diff --git a/gcloud/dataplex/glossaries/categories/help b/gcloud/dataplex/glossaries/categories/help new file mode 100644 index 000000000..f9b6e4cff --- /dev/null +++ b/gcloud/dataplex/glossaries/categories/help @@ -0,0 +1,38 @@ +NAME + gcloud dataplex glossaries categories - manage Dataplex glossary categories + +SYNOPSIS + gcloud dataplex glossaries categories COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + A glossary category represents a collection of glossary categories and + glossary terms within a glossary that are related to each other. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Creates a glossary category. + + delete + Deletes a glossary category. + + describe + Describes a glossary category. + + list + List glossary categories. + + update + Updates a glossary category. + +NOTES + This variant is also available: + + $ gcloud alpha dataplex glossaries categories + diff --git a/gcloud/dataplex/glossaries/categories/list b/gcloud/dataplex/glossaries/categories/list new file mode 100644 index 000000000..7e5b83a75 --- /dev/null +++ b/gcloud/dataplex/glossaries/categories/list @@ -0,0 +1,101 @@ +NAME + gcloud dataplex glossaries categories list - list glossary categories + +SYNOPSIS + gcloud dataplex glossaries categories list + (--glossary=GLOSSARY : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List glossary categories. + +EXAMPLES + To list glossary categories in glossary test-glossary in location + us-central1 in project test-project, run : + + $ gcloud dataplex glossaries categories list \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project + +REQUIRED FLAGS + Glossary resource - Arguments and flags that define the glossary in which + to list glossary categories. 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 --glossary 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. + + --glossary=GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument --glossary on the command line. + + This flag 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 --glossary on the command line with a fully + specified name; + ▸ 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 glossaries categories list + diff --git a/gcloud/dataplex/glossaries/categories/update b/gcloud/dataplex/glossaries/categories/update new file mode 100644 index 000000000..a7d6523f7 --- /dev/null +++ b/gcloud/dataplex/glossaries/categories/update @@ -0,0 +1,104 @@ +NAME + gcloud dataplex glossaries categories update - updates a glossary category + +SYNOPSIS + gcloud dataplex glossaries categories update + (GLOSSARY_CATEGORY : --glossary=GLOSSARY --location=LOCATION) + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [--parent=PARENT] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates a glossary category. + +EXAMPLES + To update display name, desciption and labels of glossary category + test-category in glossary test-glossary in project test-project in location + us-central1, run: + + $ gcloud dataplex glossaries categories update test-category \ + --location=us-central1 --project=test-project \ + --glossary=test-glossary --description='updated description' \ + --display-name='updated displayName' \ + --labels=key1=value1,key2=value2 + + To update parent of glossary category test-category in glossary + test-glossary in project test-project in location us-central1, run: + + $ gcloud dataplex glossaries categories update test-category \ + --location=us-central1 --project=test-project \ + --glossary=test-glossary \ + --parent='projects/test-project/locations/us-central1/glossaries\ + /updated-glossary' + +POSITIONAL ARGUMENTS + Glossary category resource - Arguments and flags that define the Dataplex + Glossary Category you want to update. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument glossary_category 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. + + GLOSSARY_CATEGORY + ID of the glossary category or fully qualified identifier for the + glossary category. + + To set the glossary_category attribute: + ▸ provide the argument glossary_category on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + The name of glossary category to use. + + To set the glossary attribute: + ▸ provide the argument glossary_category on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + The location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_category 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 glossary category. + + --display-name=DISPLAY_NAME + Display Name of the glossary category. + + --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. + + --parent=PARENT + Immediate parent of the created glossary category. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 glossaries categories update + diff --git a/gcloud/dataplex/glossaries/create b/gcloud/dataplex/glossaries/create new file mode 100644 index 000000000..f747ab426 --- /dev/null +++ b/gcloud/dataplex/glossaries/create @@ -0,0 +1,90 @@ +NAME + gcloud dataplex glossaries create - create a Dataplex Glossary resource + +SYNOPSIS + gcloud dataplex glossaries create (GLOSSARY : --location=LOCATION) + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [--async | --validate-only] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + A Glossary represents a collection of Categories and Terms. + +EXAMPLES + To create a Glossary test-glossary in project test-dataplex at location + us-central1, with description test description and displayName displayName + , run: + + $ gcloud dataplex glossaries create test-glossary \ + --location=us-central1 --project=test-dataplex \ + --description='test description' --display-name='displayName' + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary 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 Glossary. + + --display-name=DISPLAY_NAME + Display Name of the Glossary. + + --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 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 glossaries create + diff --git a/gcloud/dataplex/glossaries/delete b/gcloud/dataplex/glossaries/delete new file mode 100644 index 000000000..3abc4818e --- /dev/null +++ b/gcloud/dataplex/glossaries/delete @@ -0,0 +1,72 @@ +NAME + gcloud dataplex glossaries delete - delete a Dataplex Glossary + +SYNOPSIS + gcloud dataplex glossaries delete (GLOSSARY : --location=LOCATION) + [--async] [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Dataplex Glossary. + +EXAMPLES + To Delete Glossary test-glossary in project test-dataplex at location + us-central1, run: $ gcloud dataplex glossaries delete test-glossary \ + --location=us-central1 --project=test-dataplex + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + you want 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --etag=ETAG + etag value for particular Glossary. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 glossaries delete + diff --git a/gcloud/dataplex/glossaries/describe b/gcloud/dataplex/glossaries/describe new file mode 100644 index 000000000..680a16f1d --- /dev/null +++ b/gcloud/dataplex/glossaries/describe @@ -0,0 +1,67 @@ +NAME + gcloud dataplex glossaries describe - describe a Glossary + +SYNOPSIS + gcloud dataplex glossaries describe (GLOSSARY : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Glossary. Displays all details of a Glossary given a valid + Glossary ID. + +EXAMPLES + To describe a Dataplex Glossary test-glossary within location us-central1 + and in project test-project + + $ gcloud dataplex glossaries describe test-glossary \ + --location=us-central1 --project=test-project + +POSITIONAL ARGUMENTS + Glossary resource - Glossary 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary 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 glossaries describe + diff --git a/gcloud/dataplex/glossaries/get-iam-policy b/gcloud/dataplex/glossaries/get-iam-policy new file mode 100644 index 000000000..f7911e303 --- /dev/null +++ b/gcloud/dataplex/glossaries/get-iam-policy @@ -0,0 +1,95 @@ +NAME + gcloud dataplex glossaries get-iam-policy - retrieve a Dataplex Glossary + IAM policy + +SYNOPSIS + gcloud dataplex glossaries get-iam-policy (GLOSSARY : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Displays the IAM policy associated with a Dataplex Glossary resource. If + formatted as JSON, the output can be edited and used as a policy file for + set-iam-policy. The output includes an "etag" field identifying the version + emitted and allowing detection of concurrent policy updates. + +EXAMPLES + To get the IAM policy of a Dataplex Glossary test-glossary in project + test-project under location us-central1 $ gcloud dataplex glossaries get-iam-policy test-glossary \ + --project=test-project --location=us-central1 + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + IAM policy 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary on the command line with a fully + specified name; + ▸ 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 glossaries get-iam-policy + diff --git a/gcloud/dataplex/glossaries/help b/gcloud/dataplex/glossaries/help new file mode 100644 index 000000000..0fd90c166 --- /dev/null +++ b/gcloud/dataplex/glossaries/help @@ -0,0 +1,59 @@ +NAME + gcloud dataplex glossaries - manage Dataplex glossaries + +SYNOPSIS + gcloud dataplex glossaries GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + A Glossary represents a collection of Categories and Terms. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + categories + Manage Dataplex glossary categories. + + terms + Manage Dataplex glossary terms. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + Add IAM policy binding to a Dataplex Glossary. + + create + Create a Dataplex Glossary resource. + + delete + Delete a Dataplex Glossary. + + describe + Describe a Glossary. + + get-iam-policy + Retrieve a Dataplex Glossary IAM policy. + + list + List Glossaries. + + remove-iam-policy-binding + Removes IAM policy binding from a Dataplex Glossary. + + set-iam-policy + Set an IAM policy binding for a Dataplex Glossary as defined in a JSON + or YAML file. + + update + Updates a Dataplex Glossary. + +NOTES + This variant is also available: + + $ gcloud alpha dataplex glossaries + diff --git a/gcloud/dataplex/glossaries/list b/gcloud/dataplex/glossaries/list new file mode 100644 index 000000000..87186173d --- /dev/null +++ b/gcloud/dataplex/glossaries/list @@ -0,0 +1,85 @@ +NAME + gcloud dataplex glossaries list - list Glossaries + +SYNOPSIS + gcloud dataplex glossaries list [--location=LOCATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Glossaries. + +EXAMPLES + To List Glossaries in project test-dataplex at location us-central1 + + $ gcloud dataplex glossaries list --location=us-central1 \ + --project=test-dataplex + +FLAGS + Location resource - Location in which to list Glossaries. 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 glossaries list + diff --git a/gcloud/dataplex/glossaries/remove-iam-policy-binding b/gcloud/dataplex/glossaries/remove-iam-policy-binding new file mode 100644 index 000000000..cf3ac8317 --- /dev/null +++ b/gcloud/dataplex/glossaries/remove-iam-policy-binding @@ -0,0 +1,88 @@ +NAME + gcloud dataplex glossaries remove-iam-policy-binding - removes IAM policy + binding from a Dataplex Glossary + +SYNOPSIS + gcloud dataplex glossaries remove-iam-policy-binding + (GLOSSARY : --location=LOCATION) --member=PRINCIPAL --role=ROLE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Removes IAM policy binding from a Dataplex Glossary. + +EXAMPLES + To remove an IAM policy binding for the role roles/dataplex.viewer for the + user test-user@gmail.com from a glossary test-glossary within projet + test-project in location us-central1, run: $ gcloud dataplex glossaries remove-iam-policy-binding \ + test-glossary --project=test-project --location=us-central1 \ + --role=roles/dataplex.viewer --member=user:test-user@gmail.com \ + See https://cloud.google.com/dataplex/docs/iam-roles for \ + details of policy role and member types. + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + you want to remove 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 glossaries remove-iam-policy-binding + diff --git a/gcloud/dataplex/glossaries/set-iam-policy b/gcloud/dataplex/glossaries/set-iam-policy new file mode 100644 index 000000000..49fe164a4 --- /dev/null +++ b/gcloud/dataplex/glossaries/set-iam-policy @@ -0,0 +1,71 @@ +NAME + gcloud dataplex glossaries set-iam-policy - set an IAM policy binding for a + Dataplex Glossary as defined in a JSON or YAML file + +SYNOPSIS + gcloud dataplex glossaries set-iam-policy (GLOSSARY : --location=LOCATION) + POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +EXAMPLES + The following command will read an IAM policy defined in a JSON file + policy.json and set it for the Dataplex Glossary test-glossary within + project test-project in location us-central1: $ gcloud dataplex glossaries set-iam-policy test-glossary \ + --project=test-project --location=us-central1 policy.json \ + where policy.json is the relative path to the json file. + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + you want to set IAM policy 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 glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/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. + +NOTES + This variant is also available: + + $ gcloud alpha dataplex glossaries set-iam-policy + diff --git a/gcloud/dataplex/glossaries/terms/create b/gcloud/dataplex/glossaries/terms/create new file mode 100644 index 000000000..337e12fab --- /dev/null +++ b/gcloud/dataplex/glossaries/terms/create @@ -0,0 +1,101 @@ +NAME + gcloud dataplex glossaries terms create - creates a glossary term + +SYNOPSIS + gcloud dataplex glossaries terms create + (GLOSSARY_TERM : --glossary=GLOSSARY --location=LOCATION) + --parent=PARENT [--description=DESCRIPTION] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + A glossary term holds a rich text description that can be attached to + entries or specific columns to enrich them. + +EXAMPLES + To create a glossary term test-term in glossary test-glossary in project + test-project in location us-central1, with description test description, + displayName displayName and parent + projects/test-project/locations/us-central1/glossaries/test-glossary/categories/test-category + , run: + + $ gcloud dataplex glossaries terms create test-term \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project \ + --parent='projects/test-project/locations/us-central1/glossaries\ + /test-glossary/categories/test-category' \ + --description='test description' --display-name='displayName' + +POSITIONAL ARGUMENTS + Glossary term resource - Arguments and flags that define the Dataplex + Glossary Term 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 glossary_term 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. + + GLOSSARY_TERM + ID of the glossary term or fully qualified identifier for the + glossary term. + + To set the glossary_term attribute: + ▸ provide the argument glossary_term on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + The name of glossary term to use. + + To set the glossary attribute: + ▸ provide the argument glossary_term on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + The location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_term on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + --parent=PARENT + Immediate parent of the created glossary term. + +OPTIONAL FLAGS + --description=DESCRIPTION + Description of the glossary term. + + --display-name=DISPLAY_NAME + Display name of the glossary term. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha dataplex glossaries terms create + diff --git a/gcloud/dataplex/glossaries/terms/delete b/gcloud/dataplex/glossaries/terms/delete new file mode 100644 index 000000000..2b73428d3 --- /dev/null +++ b/gcloud/dataplex/glossaries/terms/delete @@ -0,0 +1,77 @@ +NAME + gcloud dataplex glossaries terms delete - deletes a glossary term + +SYNOPSIS + gcloud dataplex glossaries terms delete + (GLOSSARY_TERM : --glossary=GLOSSARY --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Deletes a glossary term. + +EXAMPLES + To delete the glossary term test-term in glossary test-glossary in project + test-project in location us-central1, run: + + $ gcloud dataplex glossaries terms delete test-term \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Glossary term resource - Arguments and flags that define the glossary term + you want 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 glossary_term 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. + + GLOSSARY_TERM + ID of the glossary term or fully qualified identifier for the + glossary term. + + To set the glossary_term attribute: + ▸ provide the argument glossary_term on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + Identifier of the Dataplex Glossary resource. + + To set the glossary attribute: + ▸ provide the argument glossary_term on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_term 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 glossaries terms delete + diff --git a/gcloud/dataplex/glossaries/terms/describe b/gcloud/dataplex/glossaries/terms/describe new file mode 100644 index 000000000..b5ae21dd5 --- /dev/null +++ b/gcloud/dataplex/glossaries/terms/describe @@ -0,0 +1,77 @@ +NAME + gcloud dataplex glossaries terms describe - describes a glossary term + +SYNOPSIS + gcloud dataplex glossaries terms describe + (GLOSSARY_TERM : --glossary=GLOSSARY --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describes a glossary term. + +EXAMPLES + To describe the glossary term test-term in glossary test-glossary in + project test-project in loaction us-central1, run: + + $ gcloud dataplex glossaries terms describe test-term \ + --glossary=test-glossary --location=us-central1 \ + --project=test-project + +POSITIONAL ARGUMENTS + Glossary term resource - Arguments and flags that define the glossary term + 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 glossary_term 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. + + GLOSSARY_TERM + ID of the glossary term or fully qualified identifier for the + glossary term. + + To set the glossary_term attribute: + ▸ provide the argument glossary_term on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + Identifier of the Dataplex Glossary resource. + + To set the glossary attribute: + ▸ provide the argument glossary_term on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_term 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 glossaries terms describe + diff --git a/gcloud/dataplex/glossaries/terms/help b/gcloud/dataplex/glossaries/terms/help new file mode 100644 index 000000000..da8576a67 --- /dev/null +++ b/gcloud/dataplex/glossaries/terms/help @@ -0,0 +1,39 @@ +NAME + gcloud dataplex glossaries terms - manage Dataplex glossary terms + +SYNOPSIS + gcloud dataplex glossaries terms COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Glossary terms are the core of a Dataplex glossary. A glossary term holds a + rich text description that can be attached to entries or specific columns + to enrich them. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Creates a glossary term. + + delete + Deletes a glossary term. + + describe + Describes a glossary term. + + list + List glossary terms. + + update + Updates a glossary term. + +NOTES + This variant is also available: + + $ gcloud alpha dataplex glossaries terms + diff --git a/gcloud/dataplex/glossaries/terms/list b/gcloud/dataplex/glossaries/terms/list new file mode 100644 index 000000000..0567b9457 --- /dev/null +++ b/gcloud/dataplex/glossaries/terms/list @@ -0,0 +1,100 @@ +NAME + gcloud dataplex glossaries terms list - list glossary terms + +SYNOPSIS + gcloud dataplex glossaries terms list + (--glossary=GLOSSARY : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List glossary terms. + +EXAMPLES + To list glossary terms in glossary test-glossary in project test-project in + location us-central1, run : + + $ gcloud dataplex glossaries terms list --glossary=test-glossary \ + --location=us-central1 --project=test-project + +REQUIRED FLAGS + Glossary resource - Arguments and flags that define the glossary in which + to list glossary terms. 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 --glossary 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. + + --glossary=GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument --glossary on the command line. + + This flag 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 --glossary on the command line with a fully + specified name; + ▸ 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 glossaries terms list + diff --git a/gcloud/dataplex/glossaries/terms/update b/gcloud/dataplex/glossaries/terms/update new file mode 100644 index 000000000..24fe1eeb5 --- /dev/null +++ b/gcloud/dataplex/glossaries/terms/update @@ -0,0 +1,104 @@ +NAME + gcloud dataplex glossaries terms update - updates a glossary term + +SYNOPSIS + gcloud dataplex glossaries terms update + (GLOSSARY_TERM : --glossary=GLOSSARY --location=LOCATION) + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [--parent=PARENT] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates a glossary term. + +EXAMPLES + To update display name, desciption and labels of glossary term test-term in + glossary test-glossary in project test-project in location us-central1, + run: + + $ gcloud dataplex glossaries terms update test-term \ + --location=us-central1 --project=test-project \ + --glossary=test-glossary --description='updated description' \ + --display-name='updated displayName' \ + --labels=key1=value1,key2=value2 + + To update parent of glossary term test-term in glossary test-glossary in + project test-project in location us-central1, run: + + $ gcloud dataplex glossaries terms update test-term \ + --location=us-central1 --project=test-project \ + --glossary=test-glossary \ + --parent='projects/test-project/locations/us-central1/glossaries\ + /updated-glossary' + +POSITIONAL ARGUMENTS + Glossary term resource - Arguments and flags that define the Dataplex + Glossary Term you want to update. The arguments in this group can be used + to specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument glossary_term 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. + + GLOSSARY_TERM + ID of the glossary term or fully qualified identifier for the + glossary term. + + To set the glossary_term attribute: + ▸ provide the argument glossary_term on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --glossary=GLOSSARY + The name of glossary term to use. + + To set the glossary attribute: + ▸ provide the argument glossary_term on the command line with a + fully specified name; + ▸ provide the argument --glossary on the command line. + + --location=LOCATION + The location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument glossary_term 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 glossary term. + + --display-name=DISPLAY_NAME + Display name of the glossary term. + + --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. + + --parent=PARENT + Immediate parent of the created glossary term. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 glossaries terms update + diff --git a/gcloud/dataplex/glossaries/update b/gcloud/dataplex/glossaries/update new file mode 100644 index 000000000..86de645ba --- /dev/null +++ b/gcloud/dataplex/glossaries/update @@ -0,0 +1,91 @@ +NAME + gcloud dataplex glossaries update - updates a Dataplex Glossary + +SYNOPSIS + gcloud dataplex glossaries update (GLOSSARY : --location=LOCATION) + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--etag=ETAG] + [--labels=[KEY=VALUE,...]] [--async | --validate-only] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates a Dataplex Glossary. + +EXAMPLES + To update Glossary test-glossary in project test-dataplex at location + us-central1, with description updated description and displayName + displayName $ gcloud dataplex glossaries update test-glossary \ + --location=us-central1 --project test-dataplex \ + --description='updated description' + +POSITIONAL ARGUMENTS + Glossary resource - Arguments and flags that define the Dataplex Glossary + you want to update. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument glossary 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. + + GLOSSARY + ID of the glossary or fully qualified identifier for the glossary. + + To set the glossary attribute: + ▸ provide the argument glossary 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 glossary 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 Glossary. + + --display-name=DISPLAY_NAME + Display Name of the Glossary. + + --etag=ETAG + etag value for particular Glossary. + + --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 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 glossaries update + diff --git a/gcloud/dataplex/help b/gcloud/dataplex/help index 721d20ff0..002a9a641 100644 --- a/gcloud/dataplex/help +++ b/gcloud/dataplex/help @@ -27,6 +27,9 @@ GROUPS datascans Manage Dataplex Datascan. + encryption-config + Manage Dataplex encryption configs. + entries Manage Dataplex Catalog Entries resources. @@ -39,6 +42,9 @@ GROUPS environments Manage Dataplex Environments. + glossaries + Manage Dataplex glossaries. + lakes Manage Dataplex Lake resources. diff --git a/gcloud/dataproc/batches/submit/help b/gcloud/dataproc/batches/submit/help index e3fe35646..6da132d0a 100644 --- a/gcloud/dataproc/batches/submit/help +++ b/gcloud/dataproc/batches/submit/help @@ -9,6 +9,7 @@ SYNOPSIS [--properties=[PROPERTY=VALUE,...]] [--region=REGION] [--request-id=REQUEST_ID] [--service-account=SERVICE_ACCOUNT] [--staging-bucket=STAGING_BUCKET] [--tags=[TAGS,...]] [--ttl=TTL] + [--user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE] [--version=VERSION] [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] @@ -132,6 +133,10 @@ FLAGS (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for information on duration formats. + --user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE + Whether to use END_USER_CREDENTIALS or SERVICE_ACCOUNT to run the + workload. + --version=VERSION Optional runtime version. If not specified, a default version will be used. diff --git a/gcloud/dataproc/batches/submit/pyspark b/gcloud/dataproc/batches/submit/pyspark index d6c65a0b4..b1d67562e 100644 --- a/gcloud/dataproc/batches/submit/pyspark +++ b/gcloud/dataproc/batches/submit/pyspark @@ -11,9 +11,10 @@ SYNOPSIS [--properties=[PROPERTY=VALUE,...]] [--py-files=[PY,...]] [--region=REGION] [--request-id=REQUEST_ID] [--service-account=SERVICE_ACCOUNT] [--staging-bucket=STAGING_BUCKET] - [--tags=[TAGS,...]] [--ttl=TTL] [--version=VERSION] - [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] - [-- JOB_ARG ...] + [--tags=[TAGS,...]] [--ttl=TTL] + [--user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE] + [--version=VERSION] [--network=NETWORK | --subnet=SUBNET] + [GCLOUD_WIDE_FLAG ...] [-- JOB_ARG ...] DESCRIPTION Submit a PySpark batch job. @@ -148,6 +149,10 @@ FLAGS (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for information on duration formats. + --user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE + Whether to use END_USER_CREDENTIALS or SERVICE_ACCOUNT to run the + workload. + --version=VERSION Optional runtime version. If not specified, a default version will be used. diff --git a/gcloud/dataproc/batches/submit/spark b/gcloud/dataproc/batches/submit/spark index 58d54cabe..90f803f8e 100644 --- a/gcloud/dataproc/batches/submit/spark +++ b/gcloud/dataproc/batches/submit/spark @@ -11,6 +11,7 @@ SYNOPSIS [--properties=[PROPERTY=VALUE,...]] [--region=REGION] [--request-id=REQUEST_ID] [--service-account=SERVICE_ACCOUNT] [--staging-bucket=STAGING_BUCKET] [--tags=[TAGS,...]] [--ttl=TTL] + [--user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE] [--version=VERSION] [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARG ...] @@ -161,6 +162,10 @@ OPTIONAL FLAGS (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for information on duration formats. + --user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE + Whether to use END_USER_CREDENTIALS or SERVICE_ACCOUNT to run the + workload. + --version=VERSION Optional runtime version. If not specified, a default version will be used. diff --git a/gcloud/dataproc/batches/submit/spark-r b/gcloud/dataproc/batches/submit/spark-r index 2456b72c3..8fe4780ee 100644 --- a/gcloud/dataproc/batches/submit/spark-r +++ b/gcloud/dataproc/batches/submit/spark-r @@ -11,6 +11,7 @@ SYNOPSIS [--properties=[PROPERTY=VALUE,...]] [--region=REGION] [--request-id=REQUEST_ID] [--service-account=SERVICE_ACCOUNT] [--staging-bucket=STAGING_BUCKET] [--tags=[TAGS,...]] [--ttl=TTL] + [--user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE] [--version=VERSION] [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARG ...] @@ -139,6 +140,10 @@ FLAGS (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for information on duration formats. + --user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE + Whether to use END_USER_CREDENTIALS or SERVICE_ACCOUNT to run the + workload. + --version=VERSION Optional runtime version. If not specified, a default version will be used. diff --git a/gcloud/dataproc/batches/submit/spark-sql b/gcloud/dataproc/batches/submit/spark-sql index d08ce75d3..5c44aeb0a 100644 --- a/gcloud/dataproc/batches/submit/spark-sql +++ b/gcloud/dataproc/batches/submit/spark-sql @@ -11,6 +11,7 @@ SYNOPSIS [--properties=[PROPERTY=VALUE,...]] [--region=REGION] [--request-id=REQUEST_ID] [--service-account=SERVICE_ACCOUNT] [--staging-bucket=STAGING_BUCKET] [--tags=[TAGS,...]] [--ttl=TTL] + [--user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE] [--vars=[NAME=VALUE,...]] [--version=VERSION] [--network=NETWORK | --subnet=SUBNET] [GCLOUD_WIDE_FLAG ...] @@ -129,6 +130,10 @@ FLAGS (https://cloud.google.com/sdk/gcloud/reference/topic/datetimes) for information on duration formats. + --user-workload-authentication-type=USER_WORKLOAD_AUTHENTICATION_TYPE + Whether to use END_USER_CREDENTIALS or SERVICE_ACCOUNT to run the + workload. + --vars=[NAME=VALUE,...] Mapping of query variable names to values (equivalent to the Spark SQL command: SET name="value";). diff --git a/gcloud/dataproc/clusters/create b/gcloud/dataproc/clusters/create index dad1a68f0..81955493b 100644 --- a/gcloud/dataproc/clusters/create +++ b/gcloud/dataproc/clusters/create @@ -45,7 +45,8 @@ 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] [--stop-max-idle=STOP_MAX_IDLE] + [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -82,6 +83,8 @@ 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 ...] @@ -446,6 +449,11 @@ 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. @@ -1010,6 +1018,18 @@ 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 24c5880cf..f8443da4f 100644 --- a/gcloud/dataproc/clusters/update +++ b/gcloud/dataproc/clusters/update @@ -15,7 +15,11 @@ 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] [GCLOUD_WIDE_FLAG ...] + | --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 ...] DESCRIPTION Update the number of worker nodes and/or the labels in a cluster. @@ -216,6 +220,33 @@ 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/deploy/job-runs/terminate b/gcloud/deploy/job-runs/terminate index 7e6430929..aad54b887 100644 --- a/gcloud/deploy/job-runs/terminate +++ b/gcloud/deploy/job-runs/terminate @@ -5,7 +5,7 @@ SYNOPSIS gcloud deploy job-runs terminate (JOB_RUN : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION --release=RELEASE --rollout=ROLLOUT) - [GCLOUD_WIDE_FLAG ...] + [--override-deploy-policies=[POLICY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Terminates a Cloud Deploy job run. @@ -78,6 +78,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --rollout on the command line. +FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/releases/create b/gcloud/deploy/releases/create index 6ef3fdd84..f1e51f86b 100644 --- a/gcloud/deploy/releases/create +++ b/gcloud/deploy/releases/create @@ -9,6 +9,7 @@ SYNOPSIS [--description=DESCRIPTION] [--gcs-source-staging-dir=GCS_SOURCE_STAGING_DIR] [--ignore-file=IGNORE_FILE] [--labels=[KEY=VALUE,...]] + [--override-deploy-policies=[POLICY,...]] [--skaffold-version=SKAFFOLD_VERSION] [--to-target=TO_TARGET] [--build-artifacts=BUILD_ARTIFACTS | --images=[NAME=TAG,...]] [--disable-initial-rollout | --enable-initial-rollout @@ -147,6 +148,9 @@ FLAGS $ gcloud deploy releases create --labels="commit=abc123,author=foo" + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --skaffold-version=SKAFFOLD_VERSION Version of the Skaffold binary. diff --git a/gcloud/deploy/releases/promote b/gcloud/deploy/releases/promote index 53f8a4e85..b67a90359 100644 --- a/gcloud/deploy/releases/promote +++ b/gcloud/deploy/releases/promote @@ -7,8 +7,9 @@ SYNOPSIS (--release=RELEASE : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) [--annotations=[KEY=VALUE,...]] [--labels=[KEY=VALUE,...]] - [--rollout-id=ROLLOUT_ID] [--starting-phase-id=STARTING_PHASE_ID] - [--to-target=TO_TARGET] [GCLOUD_WIDE_FLAG ...] + [--override-deploy-policies=[POLICY,...]] [--rollout-id=ROLLOUT_ID] + [--starting-phase-id=STARTING_PHASE_ID] [--to-target=TO_TARGET] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION If to-target is not specified the command promotes the release from the @@ -88,6 +89,9 @@ OPTIONAL FLAGS $ gcloud deploy releases promote --labels="commit=abc123,author=foo" + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --rollout-id=ROLLOUT_ID ID to assign to the generated rollout for promotion. diff --git a/gcloud/deploy/rollouts/advance b/gcloud/deploy/rollouts/advance index bdbe1c207..25e59e366 100644 --- a/gcloud/deploy/rollouts/advance +++ b/gcloud/deploy/rollouts/advance @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud deploy rollouts advance (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE - --region=REGION --release=RELEASE) [--phase-id=PHASE_ID] + --region=REGION --release=RELEASE) + [--override-deploy-policies=[POLICY,...]] [--phase-id=PHASE_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -70,6 +71,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --release on the command line. FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --phase-id=PHASE_ID Phase ID on a rollout resource diff --git a/gcloud/deploy/rollouts/approve b/gcloud/deploy/rollouts/approve index a66b25266..bdbeee671 100644 --- a/gcloud/deploy/rollouts/approve +++ b/gcloud/deploy/rollouts/approve @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud deploy rollouts approve (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE - --region=REGION --release=RELEASE) [GCLOUD_WIDE_FLAG ...] + --region=REGION --release=RELEASE) + [--override-deploy-policies=[POLICY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Approves a rollout having an Approval state of "Required". @@ -69,6 +70,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --release on the command line. +FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/rollouts/cancel b/gcloud/deploy/rollouts/cancel index d972677bb..075d1e63d 100644 --- a/gcloud/deploy/rollouts/cancel +++ b/gcloud/deploy/rollouts/cancel @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud deploy rollouts cancel (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE - --region=REGION --release=RELEASE) [GCLOUD_WIDE_FLAG ...] + --region=REGION --release=RELEASE) + [--override-deploy-policies=[POLICY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Cancel a Rollout. @@ -68,6 +69,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --release on the command line. +FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/rollouts/ignore-job b/gcloud/deploy/rollouts/ignore-job index 8bf431c28..4dd455852 100644 --- a/gcloud/deploy/rollouts/ignore-job +++ b/gcloud/deploy/rollouts/ignore-job @@ -6,7 +6,8 @@ SYNOPSIS gcloud deploy rollouts ignore-job (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION --release=RELEASE) --job-id=JOB_ID - --phase-id=PHASE_ID [GCLOUD_WIDE_FLAG ...] + --phase-id=PHASE_ID [--override-deploy-policies=[POLICY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Ignores a specified job and phase combination on a rollout. @@ -78,6 +79,10 @@ REQUIRED FLAGS --phase-id=PHASE_ID Phase ID on a rollout resource +OPTIONAL FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/rollouts/reject b/gcloud/deploy/rollouts/reject index 6c90b0f2a..c32bbccec 100644 --- a/gcloud/deploy/rollouts/reject +++ b/gcloud/deploy/rollouts/reject @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud deploy rollouts reject (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE - --region=REGION --release=RELEASE) [GCLOUD_WIDE_FLAG ...] + --region=REGION --release=RELEASE) + [--override-deploy-policies=[POLICY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Rejects a rollout having an Approval state of "Required". @@ -69,6 +70,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --release on the command line. +FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/rollouts/retry-job b/gcloud/deploy/rollouts/retry-job index 5e9288886..0a7bda69d 100644 --- a/gcloud/deploy/rollouts/retry-job +++ b/gcloud/deploy/rollouts/retry-job @@ -6,7 +6,8 @@ SYNOPSIS gcloud deploy rollouts retry-job (ROLLOUT : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION --release=RELEASE) --job-id=JOB_ID - --phase-id=PHASE_ID [GCLOUD_WIDE_FLAG ...] + --phase-id=PHASE_ID [--override-deploy-policies=[POLICY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Retries a specified job, phase combination on a rollout. @@ -78,6 +79,10 @@ REQUIRED FLAGS --phase-id=PHASE_ID Phase ID on a rollout resource +OPTIONAL FLAGS + --override-deploy-policies=[POLICY,...] + Deploy policies to override + 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/deploy/targets/redeploy b/gcloud/deploy/targets/redeploy index 8fe39745e..4e2482d01 100644 --- a/gcloud/deploy/targets/redeploy +++ b/gcloud/deploy/targets/redeploy @@ -5,8 +5,8 @@ SYNOPSIS gcloud deploy targets redeploy (TARGET : --region=REGION) --delivery-pipeline=DELIVERY_PIPELINE [--annotations=[KEY=VALUE,...]] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--rollout-id=ROLLOUT_ID] [--starting-phase-id=STARTING_PHASE_ID] - [GCLOUD_WIDE_FLAG ...] + [--override-deploy-policies=[POLICY,...]] [--rollout-id=ROLLOUT_ID] + [--starting-phase-id=STARTING_PHASE_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Redeploy the last rollout that has a state of SUCCESSFUL or FAILED to a @@ -80,6 +80,9 @@ OPTIONAL FLAGS $ gcloud deploy targets redeploy --labels="commit=abc123,author=foo" + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --rollout-id=ROLLOUT_ID ID to assign to the generated rollout for promotion. diff --git a/gcloud/deploy/targets/rollback b/gcloud/deploy/targets/rollback index 64291d14a..86f40535e 100644 --- a/gcloud/deploy/targets/rollback +++ b/gcloud/deploy/targets/rollback @@ -5,8 +5,9 @@ SYNOPSIS gcloud deploy targets rollback (TARGET : --region=REGION) --delivery-pipeline=DELIVERY_PIPELINE [--annotations=[KEY=VALUE,...]] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--release=RELEASE] [--rollout-id=ROLLOUT_ID] - [--starting-phase-id=STARTING_PHASE_ID] [GCLOUD_WIDE_FLAG ...] + [--override-deploy-policies=[POLICY,...]] [--release=RELEASE] + [--rollout-id=ROLLOUT_ID] [--starting-phase-id=STARTING_PHASE_ID] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION If release is not specified, the command rollbacks the target with the last @@ -81,6 +82,9 @@ OPTIONAL FLAGS $ gcloud deploy targets rollback --labels="commit=abc123,author=foo" + --override-deploy-policies=[POLICY,...] + Deploy policies to override + --release=RELEASE Name of the release to rollback to. diff --git a/gcloud/iam/workforce-pools/providers/create-oidc b/gcloud/iam/workforce-pools/providers/create-oidc index 1af7d5d91..749c45cd1 100644 --- a/gcloud/iam/workforce-pools/providers/create-oidc +++ b/gcloud/iam/workforce-pools/providers/create-oidc @@ -273,32 +273,28 @@ OPTIONAL FLAGS *--extra-attributes-client-id*=_EXTRA_ATTRIBUTES_CLIENT_ID_:: - The OAuth 2.0 client ID for retrieving extra attributes from the identity provider. Required - to get the Access Token using client credentials grant flow. + The OAuth 2.0 client ID for retrieving extra attributes from the identity provider. Required to get the access token using client credentials grant flow. *--extra-attributes-client-secret-value*=_EXTRA_ATTRIBUTES_CLIENT_SECRET_VALUE_:: - The OAuth 2.0 client secret for retrieving extra attributes from the identity provider. - Required to get the Access Token using client credentials grant flow. + The OAuth 2.0 client secret for retrieving extra attributes from the identity provider. Required to get the access token using client credentials grant flow. *--extra-attributes-issuer-uri*=_EXTRA_ATTRIBUTES_ISSUER_URI_:: - OIDC identity provider's issuer URI. Must be a valid URI using the 'https' scheme. - Required to get the OIDC discovery document. + OIDC identity provider's issuer URI. Must be a valid URI using the `https` scheme. Required to get the OIDC discovery document. *--extra-attributes-type*=_EXTRA_ATTRIBUTES_TYPE_:: - Represents the identity provider and type of claims that should be fetched. _EXTRA_ATTRIBUTES_TYPE_ must be one of: *attributes-type-unspecified*, *azure-ad-groups-display-name*, *azure-ad-groups-id*, *azure-ad-groups-mail*. + Represents the identity provider and type of claims that should be fetched. _EXTRA_ATTRIBUTES_TYPE_ must be one of: *azure-ad-groups-mail*, *azure-ad-groups-id*. *--extra-attributes-filter*=_EXTRA_ATTRIBUTES_FILTER_:: - The filter used to request specific records from IdP. When used with the attributes type - azure-ad-groups-mail or azure-ad-groups-id, the filter requests specific groups associated - with a user from the IdP. By default all of the groups associated with the user are fetched. - When used with the attributes type azure-ad-groups-mail, the groups that are used should be - security and mail enabled. When used with the attributes type azure-ad-groups-id, the groups - that are used should be security enabled. See - https://learn.microsoft.com/en-us/graph/search-query-parameter for more details. + The filter used to request specific records from the IdP. By default, all of the groups that are associated with a user are fetched. For Microsoft Entra ID, you can add `$search` query parameters using [Keyword Query Language] (https://learn.microsoft.com/en-us/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference). To learn more about `$search` querying in Microsoft Entra ID, see [Use the `$search` query parameter] (https://learn.microsoft.com/en-us/graph/search-query-parameter). + + Additionally, Workforce Identity Federation automatically adds the following [`$filter` query parameters] (https://learn.microsoft.com/en-us/graph/filter-query-parameter), based on the value of `attributes_type`. Values passed to `filter` are converted to `$search` query parameters. Additional `$filter` query parameters cannot be added using this field. + + * `AZURE_AD_GROUPS_MAIL`: `mailEnabled` and `securityEnabled` filters are applied. + * `AZURE_AD_GROUPS_ID`: `securityEnabled` filter is 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. diff --git a/gcloud/iam/workforce-pools/providers/create-saml b/gcloud/iam/workforce-pools/providers/create-saml index 5e4e8f52d..0e612663e 100644 --- a/gcloud/iam/workforce-pools/providers/create-saml +++ b/gcloud/iam/workforce-pools/providers/create-saml @@ -192,35 +192,43 @@ OPTIONAL FLAGS --extra-attributes-client-id=EXTRA_ATTRIBUTES_CLIENT_ID The OAuth 2.0 client ID for retrieving extra attributes from the - identity provider. Required to get the Access Token using client + identity provider. Required to get the access token using client credentials grant flow. --extra-attributes-client-secret-value=EXTRA_ATTRIBUTES_CLIENT_SECRET_VALUE The OAuth 2.0 client secret for retrieving extra attributes from the - identity provider. Required to get the Access Token using client + identity provider. Required to get the access token using client credentials grant flow. --extra-attributes-issuer-uri=EXTRA_ATTRIBUTES_ISSUER_URI OIDC identity provider's issuer URI. Must be a valid URI using the - 'https' scheme. Required to get the OIDC discovery document. + https scheme. Required to get the OIDC discovery document. --extra-attributes-type=EXTRA_ATTRIBUTES_TYPE Represents the identity provider and type of claims that should be - fetched. EXTRA_ATTRIBUTES_TYPE must be one of: - attributes-type-unspecified, azure-ad-groups-display-name, - azure-ad-groups-id, azure-ad-groups-mail. + fetched. EXTRA_ATTRIBUTES_TYPE must be one of: azure-ad-groups-mail, + azure-ad-groups-id. --extra-attributes-filter=EXTRA_ATTRIBUTES_FILTER - The filter used to request specific records from IdP. When used with - the attributes type azure-ad-groups-mail or azure-ad-groups-id, the - filter requests specific groups associated with a user from the IdP. By - default all of the groups associated with the user are fetched. When - used with the attributes type azure-ad-groups-mail, the groups that are - used should be security and mail enabled. When used with the attributes - type azure-ad-groups-id, the groups that are used should be security - enabled. See - https://learn.microsoft.com/en-us/graph/search-query-parameter for more - details. + The filter used to request specific records from the IdP. By default, + all of the groups that are associated with a user are fetched. For + Microsoft Entra ID, you can add $search query parameters using [Keyword + Query Language] + (https://learn.microsoft.com/en-us/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference). + To learn more about $search querying in Microsoft Entra ID, see [Use + the $search query parameter] + (https://learn.microsoft.com/en-us/graph/search-query-parameter). + + Additionally, Workforce Identity Federation automatically adds the + following [$filter query parameters] + (https://learn.microsoft.com/en-us/graph/filter-query-parameter), based + on the value of attributes_type. Values passed to filter are converted + to $search query parameters. Additional $filter query parameters cannot + be added using this field. + + ◆ AZURE_AD_GROUPS_MAIL: mailEnabled and securityEnabled filters are + applied. + ◆ AZURE_AD_GROUPS_ID: securityEnabled filter is applied. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/iam/workforce-pools/providers/update-oidc b/gcloud/iam/workforce-pools/providers/update-oidc index a2fe17509..2b455b0f0 100644 --- a/gcloud/iam/workforce-pools/providers/update-oidc +++ b/gcloud/iam/workforce-pools/providers/update-oidc @@ -259,36 +259,32 @@ FLAGS *--clear-extra-attributes-config*::: - Clear the extra attributes configuration + Clear the extra attributes configuration. *--extra-attributes-client-id*=_EXTRA_ATTRIBUTES_CLIENT_ID_::: - The OAuth 2.0 client ID for retrieving extra attributes from the identity provider. Required - to get the Access Token using client credentials grant flow. + The OAuth 2.0 client ID for retrieving extra attributes from the identity provider. Required to get the access token using client credentials grant flow. *--extra-attributes-client-secret-value*=_EXTRA_ATTRIBUTES_CLIENT_SECRET_VALUE_::: - The OAuth 2.0 client secret for retrieving extra attributes from the identity provider. - Required to get the Access Token using client credentials grant flow. + The OAuth 2.0 client secret for retrieving extra attributes from the identity provider. Required to get the access token using client credentials grant flow. *--extra-attributes-filter*=_EXTRA_ATTRIBUTES_FILTER_::: - The filter used to request specific records from IdP. When used with the attributes type - azure-ad-groups-mail or azure-ad-groups-id, the filter requests specific groups associated - with a user from the IdP. By default all of the groups associated with the user are fetched. - When used with the attributes type azure-ad-groups-mail, the groups that are used should be - security and mail enabled. When used with the attributes type azure-ad-groups-id, the groups - that are used should be security enabled. See - https://learn.microsoft.com/en-us/graph/search-query-parameter for more details. + The filter used to request specific records from the IdP. By default, all of the groups that are associated with a user are fetched. For Microsoft Entra ID, you can add `$search` query parameters using [Keyword Query Language] (https://learn.microsoft.com/en-us/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference). To learn more about `$search` querying in Microsoft Entra ID, see [Use the `$search` query parameter] (https://learn.microsoft.com/en-us/graph/search-query-parameter). + + Additionally, Workforce Identity Federation automatically adds the following [`$filter` query parameters] (https://learn.microsoft.com/en-us/graph/filter-query-parameter), based on the value of `attributes_type`. Values passed to `filter` are converted to `$search` query parameters. Additional `$filter` query parameters cannot be added using this field. + + * `AZURE_AD_GROUPS_MAIL`: `mailEnabled` and `securityEnabled` filters are applied. + * `AZURE_AD_GROUPS_ID`: `securityEnabled` filter is applied. *--extra-attributes-issuer-uri*=_EXTRA_ATTRIBUTES_ISSUER_URI_::: - OIDC identity provider's issuer URI. Must be a valid URI using the 'https' scheme. - Required to get the OIDC discovery document. + OIDC identity provider's issuer URI. Must be a valid URI using the `https` scheme. Required to get the OIDC discovery document. *--extra-attributes-type*=_EXTRA_ATTRIBUTES_TYPE_::: - Represents the identity provider and type of claims that should be fetched. _EXTRA_ATTRIBUTES_TYPE_ must be one of: *attributes-type-unspecified*, *azure-ad-groups-display-name*, *azure-ad-groups-id*, *azure-ad-groups-mail*. + Represents the identity provider and type of claims that should be fetched. _EXTRA_ATTRIBUTES_TYPE_ must be one of: *azure-ad-groups-mail*, *azure-ad-groups-id*. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity. diff --git a/gcloud/iam/workforce-pools/providers/update-saml b/gcloud/iam/workforce-pools/providers/update-saml index 97ed7221c..5c426dd3f 100644 --- a/gcloud/iam/workforce-pools/providers/update-saml +++ b/gcloud/iam/workforce-pools/providers/update-saml @@ -194,39 +194,47 @@ FLAGS At most one of these can be specified: --clear-extra-attributes-config - Clear the extra attributes configuration + Clear the extra attributes configuration. --extra-attributes-client-id=EXTRA_ATTRIBUTES_CLIENT_ID The OAuth 2.0 client ID for retrieving extra attributes from the - identity provider. Required to get the Access Token using client + identity provider. Required to get the access token using client credentials grant flow. --extra-attributes-client-secret-value=EXTRA_ATTRIBUTES_CLIENT_SECRET_VALUE The OAuth 2.0 client secret for retrieving extra attributes from the - identity provider. Required to get the Access Token using client + identity provider. Required to get the access token using client credentials grant flow. --extra-attributes-filter=EXTRA_ATTRIBUTES_FILTER - The filter used to request specific records from IdP. When used with - the attributes type azure-ad-groups-mail or azure-ad-groups-id, the - filter requests specific groups associated with a user from the IdP. - By default all of the groups associated with the user are fetched. - When used with the attributes type azure-ad-groups-mail, the groups - that are used should be security and mail enabled. When used with the - attributes type azure-ad-groups-id, the groups that are used should - be security enabled. See - https://learn.microsoft.com/en-us/graph/search-query-parameter for - more details. + The filter used to request specific records from the IdP. By default, + all of the groups that are associated with a user are fetched. For + Microsoft Entra ID, you can add $search query parameters using + [Keyword Query Language] + (https://learn.microsoft.com/en-us/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference). + To learn more about $search querying in Microsoft Entra ID, see [Use + the $search query parameter] + (https://learn.microsoft.com/en-us/graph/search-query-parameter). + + Additionally, Workforce Identity Federation automatically adds the + following [$filter query parameters] + (https://learn.microsoft.com/en-us/graph/filter-query-parameter), + based on the value of attributes_type. Values passed to filter are + converted to $search query parameters. Additional $filter query + parameters cannot be added using this field. + + ▸ AZURE_AD_GROUPS_MAIL: mailEnabled and securityEnabled filters are + applied. + ▸ AZURE_AD_GROUPS_ID: securityEnabled filter is applied. --extra-attributes-issuer-uri=EXTRA_ATTRIBUTES_ISSUER_URI OIDC identity provider's issuer URI. Must be a valid URI using the - 'https' scheme. Required to get the OIDC discovery document. + https scheme. Required to get the OIDC discovery document. --extra-attributes-type=EXTRA_ATTRIBUTES_TYPE Represents the identity provider and type of claims that should be - fetched. EXTRA_ATTRIBUTES_TYPE must be one of: - attributes-type-unspecified, azure-ad-groups-display-name, - azure-ad-groups-id, azure-ad-groups-mail. + fetched. EXTRA_ATTRIBUTES_TYPE must be one of: azure-ad-groups-mail, + azure-ad-groups-id. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/iam/workload-identity-pools/providers/create-x509 b/gcloud/iam/workload-identity-pools/providers/create-x509 new file mode 100644 index 000000000..b03ec9789 --- /dev/null +++ b/gcloud/iam/workload-identity-pools/providers/create-x509 @@ -0,0 +1,213 @@ +NAME + gcloud iam workload-identity-pools providers create-x509 - create a new + X.509 workload identity pool provider + +SYNOPSIS + gcloud iam workload-identity-pools providers create-x509 + (PROVIDER : --location=LOCATION + --workload-identity-pool=WORKLOAD_IDENTITY_POOL) + --trust-store-config-path=TRUST_STORE_CONFIG_PATH + [--attribute-condition=ATTRIBUTE_CONDITION] + [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION] + [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new X.509 workload identity pool provider. + +EXAMPLES + The following command creates a disabled X.509 workload identity pool + provider in the default project with the ID + my-workload-identity-pool-provider. Explicit values for all required and + optional parameters are provided. + + $ gcloud iam workload-identity-pools providers create-x509 \ + my-workload-identity-pool-provider --location="global" \ + --workload-identity-pool="my-workload-identity-pool" \ + --display-name="My workload pool provider" \ + --description="My workload pool provider description" \ + --disabled --attribute-mapping="google.subject=assertion.sub" \ + --attribute-condition="true" \ + --trust-store-config-path="path/to/config/file.yaml" + +POSITIONAL ARGUMENTS + Workload identity pool provider resource - The workload identity pool + provider 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 provider 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. + + PROVIDER + ID of the workload identity pool provider or fully qualified + identifier for the workload identity pool provider. + + To set the provider attribute: + ▸ provide the argument provider 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 name. + + To set the location attribute: + ▸ provide the argument provider on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --workload-identity-pool=WORKLOAD_IDENTITY_POOL + The ID to use for the pool, which becomes the final component of the + resource name. This value should be 4-32 characters, and may contain + the characters [a-z0-9-]. The prefix gcp- is reserved for use by + Google, and may not be specified. + + To set the workload-identity-pool attribute: + ▸ provide the argument provider on the command line with a fully + specified name; + ▸ provide the argument --workload-identity-pool on the command + line. + +REQUIRED FLAGS + --trust-store-config-path=TRUST_STORE_CONFIG_PATH + YAML file with configuration metadata for the X.509 identity provider. + Example file format: trustStore: + trustAnchors: + - pemCertificate: "-----BEGIN CERTIFICATE----- + + -----END CERTIFICATE-----" + intermediateCas: + - pemCertificate: "-----BEGIN CERTIFICATE----- + + -----END CERTIFICATE-----" + +OPTIONAL FLAGS + --attribute-condition=ATTRIBUTE_CONDITION + A Common Expression Language (https://opensource.google/projects/cel) + expression, in plain text, to restrict what otherwise valid + authentication credentials issued by the provider should not be + accepted. + + The expression must output a boolean representing whether to allow the + federation. + + The following keywords may be referenced in the expressions: + + ◆ assertion: JSON representing the authentication credential issued + by the provider. + ◆ google: The Google attributes mapped from the assertion in the + attribute_mappings. + ◆ attribute: The custom attributes mapped from the assertion in the + attribute_mappings. + + The maximum length of the attribute condition expression is 4096 + characters. If unspecified, all valid authentication credential are + accepted. + + The following example shows how to only allow credentials with a mapped + google.groups value of admins: + + "'admins' in google.groups" + + --attribute-mapping=[KEY=VALUE,...] + Maps attributes from authentication credentials issued by an external + identity provider to Google Cloud attributes, such as subject and + segment. + + Each key must be a string specifying the Google Cloud IAM attribute to + map to. + + The following keys are supported: + + ◆ google.subject: The principal IAM is authenticating. You can + reference this value in IAM bindings. This is also the subject that + appears in Cloud Logging logs. Cannot exceed 127 bytes. + + ◆ google.groups: Groups the external identity belongs to. You can + grant groups access to resources using an IAM principalSet binding; + access applies to all members of the group. + + You can also provide custom attributes by specifying + attribute.{custom_attribute}, where {custom_attribute} is the name of + the custom attribute to be mapped. You can define a maximum of 50 + custom attributes. The maximum length of a mapped attribute key is 100 + characters, and the key may only contain the characters [a-z_0-9]. + + You can reference these attributes in IAM policies to define + fine-grained access for a workload to Google Cloud resources. For + example: + + ◆ google.subject: + principal://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/subject/{value} + + ◆ google.groups: + principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/group/{value} + + ◆ attribute.{custom_attribute}: + principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/attribute.{custom_attribute}/{value} + + Each value must be a [Common Expression Language] + (https://opensource.google/projects/cel) function that maps an identity + provider credential to the normalized attribute specified by the + corresponding map key. + + You can use the assertion keyword in the expression to access a JSON + representation of the authentication credential issued by the provider. + + The maximum length of an attribute mapping expression is 2048 + characters. When evaluated, the total size of all mapped attributes + must not exceed 8KB. + + For AWS providers, the following rules apply: + + ◆ If no attribute mapping is defined, the following default mapping + applies: + + { + "google.subject":"assertion.arn", + "attribute.aws_role": + "assertion.arn.contains('assumed-role')" + " ? assertion.arn.extract('{account_arn}assumed-role/')" + " + 'assumed-role/'" + " + assertion.arn.extract('assumed-role/{role_name}/')" + " : assertion.arn", + } + + ◆ If any custom attribute mappings are defined, they must include a + mapping to the google.subject attribute. + + For OIDC providers, the following rules apply: + + ◆ Custom attribute mappings must be defined, and must include a + mapping to the google.subject attribute. For example, the following + maps the sub claim of the incoming credential to the subject + attribute on a Google token. + + {"google.subject": "assertion.sub"} + + --description=DESCRIPTION + A description for the provider. Cannot exceed 256 characters. + + --disabled + Whether the provider is disabled. You cannot use a disabled provider to + exchange tokens. However, existing tokens still grant access. + + --display-name=DISPLAY_NAME + A display name for the provider. Cannot exceed 32 characters. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 iam/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/iam/ diff --git a/gcloud/iam/workload-identity-pools/providers/help b/gcloud/iam/workload-identity-pools/providers/help index 871fa53ed..128c87f16 100644 --- a/gcloud/iam/workload-identity-pools/providers/help +++ b/gcloud/iam/workload-identity-pools/providers/help @@ -35,6 +35,9 @@ COMMANDS create-saml Create a new SAML workload identity pool provider. + create-x509 + Create a new X.509 workload identity pool provider. + delete Delete a workload identity pool provider. @@ -56,6 +59,9 @@ COMMANDS update-saml Update a SAML workload identity pool provider. + update-x509 + Update an X.509 workload identity pool provider. + NOTES These variants are also available: diff --git a/gcloud/iam/workload-identity-pools/providers/update-x509 b/gcloud/iam/workload-identity-pools/providers/update-x509 new file mode 100644 index 000000000..fd278bb86 --- /dev/null +++ b/gcloud/iam/workload-identity-pools/providers/update-x509 @@ -0,0 +1,212 @@ +NAME + gcloud iam workload-identity-pools providers update-x509 - update an X.509 + workload identity pool provider + +SYNOPSIS + gcloud iam workload-identity-pools providers update-x509 + (PROVIDER : --location=LOCATION + --workload-identity-pool=WORKLOAD_IDENTITY_POOL) + [--attribute-condition=ATTRIBUTE_CONDITION] + [--attribute-mapping=[KEY=VALUE,...]] [--description=DESCRIPTION] + [--disabled] [--display-name=DISPLAY_NAME] + [--trust-store-config-path=TRUST_STORE_CONFIG_PATH] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an X.509 workload identity pool provider. + +EXAMPLES + The following command updates the X.509 workload identity pool provider + with the ID my-workload-identity-pool-provider. Explicit values for all + required and optional parameters are provided: + + $ gcloud iam workload-identity-pools providers update-x509 \ + my-workload-identity-pool-provider --location="global" \ + --workload-identity-pool="my-workload-identity-pool" \ + --display-name="My workload pool provider" \ + --description="My workload pool provider description" \ + --disabled --attribute-mapping="google.subject=assertion.sub" \ + --attribute-condition="true" \ + --trust-store-config-path="path/to/config/file.yaml" + +POSITIONAL ARGUMENTS + Workload identity pool provider resource - The workload identity pool + provider 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 provider 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. + + PROVIDER + ID of the workload identity pool provider or fully qualified + identifier for the workload identity pool provider. + + To set the provider attribute: + ▸ provide the argument provider 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 name. + + To set the location attribute: + ▸ provide the argument provider on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --workload-identity-pool=WORKLOAD_IDENTITY_POOL + The ID to use for the pool, which becomes the final component of the + resource name. This value should be 4-32 characters, and may contain + the characters [a-z0-9-]. The prefix gcp- is reserved for use by + Google, and may not be specified. + + To set the workload-identity-pool attribute: + ▸ provide the argument provider on the command line with a fully + specified name; + ▸ provide the argument --workload-identity-pool on the command + line. + +FLAGS + --attribute-condition=ATTRIBUTE_CONDITION + A Common Expression Language (https://opensource.google/projects/cel) + expression, in plain text, to restrict what otherwise valid + authentication credentials issued by the provider should not be + accepted. + + The expression must output a boolean representing whether to allow the + federation. + + The following keywords may be referenced in the expressions: + + ◆ assertion: JSON representing the authentication credential issued + by the provider. + ◆ google: The Google attributes mapped from the assertion in the + attribute_mappings. + ◆ attribute: The custom attributes mapped from the assertion in the + attribute_mappings. + + The maximum length of the attribute condition expression is 4096 + characters. If unspecified, all valid authentication credential are + accepted. + + The following example shows how to only allow credentials with a mapped + google.groups value of admins: + + "'admins' in google.groups" + + --attribute-mapping=[KEY=VALUE,...] + Maps attributes from authentication credentials issued by an external + identity provider to Google Cloud attributes, such as subject and + segment. + + Each key must be a string specifying the Google Cloud IAM attribute to + map to. + + The following keys are supported: + + ◆ google.subject: The principal IAM is authenticating. You can + reference this value in IAM bindings. This is also the subject that + appears in Cloud Logging logs. Cannot exceed 127 bytes. + + ◆ google.groups: Groups the external identity belongs to. You can + grant groups access to resources using an IAM principalSet binding; + access applies to all members of the group. + + You can also provide custom attributes by specifying + attribute.{custom_attribute}, where {custom_attribute} is the name of + the custom attribute to be mapped. You can define a maximum of 50 + custom attributes. The maximum length of a mapped attribute key is 100 + characters, and the key may only contain the characters [a-z_0-9]. + + You can reference these attributes in IAM policies to define + fine-grained access for a workload to Google Cloud resources. For + example: + + ◆ google.subject: + principal://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/subject/{value} + + ◆ google.groups: + principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/group/{value} + + ◆ attribute.{custom_attribute}: + principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/attribute.{custom_attribute}/{value} + + Each value must be a [Common Expression Language] + (https://opensource.google/projects/cel) function that maps an identity + provider credential to the normalized attribute specified by the + corresponding map key. + + You can use the assertion keyword in the expression to access a JSON + representation of the authentication credential issued by the provider. + + The maximum length of an attribute mapping expression is 2048 + characters. When evaluated, the total size of all mapped attributes + must not exceed 8KB. + + For AWS providers, the following rules apply: + + ◆ If no attribute mapping is defined, the following default mapping + applies: + + { + "google.subject":"assertion.arn", + "attribute.aws_role": + "assertion.arn.contains('assumed-role')" + " ? assertion.arn.extract('{account_arn}assumed-role/')" + " + 'assumed-role/'" + " + assertion.arn.extract('assumed-role/{role_name}/')" + " : assertion.arn", + } + + ◆ If any custom attribute mappings are defined, they must include a + mapping to the google.subject attribute. + + For OIDC providers, the following rules apply: + + ◆ Custom attribute mappings must be defined, and must include a + mapping to the google.subject attribute. For example, the following + maps the sub claim of the incoming credential to the subject + attribute on a Google token. + + {"google.subject": "assertion.sub"} + + --description=DESCRIPTION + A description for the provider. Cannot exceed 256 characters. + + --disabled + Whether the provider is disabled. You cannot use a disabled provider to + exchange tokens. However, existing tokens still grant access. + + --display-name=DISPLAY_NAME + A display name for the provider. Cannot exceed 32 characters. + + --trust-store-config-path=TRUST_STORE_CONFIG_PATH + YAML file with configuration metadata for the X.509 identity provider. + Example file format: trustStore: + trustAnchors: + - pemCertificate: "-----BEGIN CERTIFICATE----- + + -----END CERTIFICATE-----" + intermediateCas: + - pemCertificate: "-----BEGIN CERTIFICATE----- + + -----END CERTIFICATE-----" + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 iam/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/iam/ diff --git a/gcloud/managed-kafka/acls/add-acl-entry b/gcloud/managed-kafka/acls/add-acl-entry index e85b1d410..b42a7c34a 100644 --- a/gcloud/managed-kafka/acls/add-acl-entry +++ b/gcloud/managed-kafka/acls/add-acl-entry @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud managed-kafka acls add-acl-entry (ACL : --cluster=CLUSTER --location=LOCATION) --operation=OPERATION - --principal=PRINCIPAL [--host=HOST; default=""] + --principal=PRINCIPAL [--host=HOST; default="*"] [--permission-type=PERMISSION_TYPE; default="ALLOW"] [GCLOUD_WIDE_FLAG ...] @@ -101,7 +101,7 @@ REQUIRED FLAGS "User:*" to refer to all users. OPTIONAL FLAGS - --host=HOST; default="" + --host=HOST; default="*" The host. Must be set to "*" for Managed Service for Apache Kafka. --permission-type=PERMISSION_TYPE; default="ALLOW" diff --git a/gcloud/managed-kafka/acls/remove-acl-entry b/gcloud/managed-kafka/acls/remove-acl-entry index 3d6ae0d91..40fc9fefb 100644 --- a/gcloud/managed-kafka/acls/remove-acl-entry +++ b/gcloud/managed-kafka/acls/remove-acl-entry @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud managed-kafka acls remove-acl-entry (ACL : --cluster=CLUSTER --location=LOCATION) --operation=OPERATION - --principal=PRINCIPAL [--host=HOST; default=""] + --principal=PRINCIPAL [--host=HOST; default="*"] [--permission-type=PERMISSION_TYPE; default="ALLOW"] [GCLOUD_WIDE_FLAG ...] @@ -81,7 +81,7 @@ REQUIRED FLAGS "User:*" to refer to all users. OPTIONAL FLAGS - --host=HOST; default="" + --host=HOST; default="*" The host. Must be set to "*" for Managed Service for Apache Kafka. --permission-type=PERMISSION_TYPE; default="ALLOW" diff --git a/gcloud/managed-kafka/clusters/create b/gcloud/managed-kafka/clusters/create index e5b50adb9..18f52dba3 100644 --- a/gcloud/managed-kafka/clusters/create +++ b/gcloud/managed-kafka/clusters/create @@ -62,13 +62,13 @@ REQUIRED FLAGS between 1 GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi. --subnets=[SUBNETS,...] - VPC subnets from which the cluster is accessible. Both broker and - bootstrap server IP addresses and DNS entries are automatically created - in each subnet. Only one subnet per network is allowed, and the subnet - must be located in the same region as the cluster. The project may - differ. A minimum of 1 subnet is required. A maximum of 10 subnets can - be specified. Use commas to separate multiple subnets. The name of the - subnet must be in the format + A comma-separated list of VPC subnets from which the cluster is + accessible. Both broker and bootstrap server IP addresses and DNS + entries are automatically created in each subnet. Only one subnet per + network is allowed, and the subnet must be located in the same region + as the cluster. The project may differ. A minimum of 1 subnet is + required. A maximum of 10 subnets can be specified. Use commas to + separate multiple subnets. The name of the subnet must be in the format projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. OPTIONAL FLAGS diff --git a/gcloud/managed-kafka/clusters/update b/gcloud/managed-kafka/clusters/update index b7043ec6b..1acd9cea4 100644 --- a/gcloud/managed-kafka/clusters/update +++ b/gcloud/managed-kafka/clusters/update @@ -75,14 +75,14 @@ REQUIRED FLAGS between 1 GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi. --subnets=[SUBNETS,...] - VPC subnets from which the cluster is accessible. Both broker and - bootstrap server IP addresses and DNS entries are automatically - created in each subnet. Only one subnet per network is allowed, and - the subnet must be located in the same region as the cluster. The - project may differ. A minimum of 1 subnet is required. A maximum of - 10 subnets can be specified. Use commas to separate multiple subnets. - The name of the subnet must be in the format - projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. + A comma-separated list of VPC subnets from which the cluster is + accessible. Both broker and bootstrap server IP addresses and DNS + entries are automatically created in each subnet. Only one subnet per + network is allowed, and the subnet must be located in the same region + as the cluster. The project may differ. A minimum of 1 subnet is + required. A maximum of 10 subnets can be specified. Use commas to + separate multiple subnets. The name of the subnet must be in the + format projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. OPTIONAL FLAGS --async diff --git a/gcloud/managed-kafka/consumer-groups/update b/gcloud/managed-kafka/consumer-groups/update index da49f0823..6435ec2c1 100644 --- a/gcloud/managed-kafka/consumer-groups/update +++ b/gcloud/managed-kafka/consumer-groups/update @@ -74,7 +74,7 @@ REQUIRED FLAGS --topics-file=JSON|YAML|FILE The path to the JSON or YAML file containing the configuration of the topics to be updated for the consumer group. This also supports inline - JSON or YAML. Required, Sets topics_file value. + JSON or YAML. Required, sets topics_file value. Input Example: diff --git a/gcloud/monitoring/snoozes/create b/gcloud/monitoring/snoozes/create index 3cd99464a..dfb3189b6 100644 --- a/gcloud/monitoring/snoozes/create +++ b/gcloud/monitoring/snoozes/create @@ -50,15 +50,20 @@ FLAGS in the --snooze-from-file flags if specified. --criteria-filter=CRITERIA_FILTER - The filter that the Snooze applies to, which is a string to match on - Alert fields when silencing the alerts. It follows the standard - https://google.aip.dev/160 syntax. Filters can be defined for snoozes - that apply to one alerting policy. Filters must be a string formatted - as one or more resource labels with specific label values. If - multiple resource labels are used, then they must be connected with - an AND operator. For example: + Optional. When you define a Snooze, you can also define a filter for + that snooze. The filter is a string containing one or more key-value + pairs. The string uses the standard https://google.aip.dev/160 filter + syntax. If you define a filter for a snooze, then the snooze can only + apply to one alert policy. When the snooze is active, incidents won't + be created when the incident would have key-value pairs (labels) that + match those specified by the filter in the snooze. Snooze filters + support resource, metric, and metadata labels. If multiple labels are + used, then they must be connected with an AND operator. For example: resource.labels.instance_id="1234567890" AND - resource.labels.zone="us-central1-a" + resource.labels.zone="us-central1-a" AND + metric.labels.instance_name="test_group" AND + metadata.user_labels.foo="bar" AND + metadata.system_labels.region="us-central1" --criteria-policies=CRITERIA_POLICIES,[...] The policies that the Snooze applies to. Exactly 1 alert policy is diff --git a/gcloud/netapp/volumes/replications/create b/gcloud/netapp/volumes/replications/create index cd67f242f..356191d39 100644 --- a/gcloud/netapp/volumes/replications/create +++ b/gcloud/netapp/volumes/replications/create @@ -65,7 +65,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --destination-volume-parameters=[description=DESCRIPTION],[share_name=SHARE_NAME],[storage_pool=STORAGE_POOL],[tiering_policy=TIERING_POLICY],[volume_id=VOLUME_ID] - Required, Sets destination_volume_parameters value. + Required, sets destination_volume_parameters value. description Sets description value. @@ -74,7 +74,7 @@ REQUIRED FLAGS Sets share_name value. storage_pool - Required, Sets storage_pool value. + Required, sets storage_pool value. tiering_policy Sets tiering_policy value. diff --git a/gcloud/network-security/help b/gcloud/network-security/help index 888e5e5c9..b35bd4166 100644 --- a/gcloud/network-security/help +++ b/gcloud/network-security/help @@ -33,6 +33,18 @@ GROUPS gateway-security-policies Manage Network Security Gateway Security Policies. + intercept-deployment-groups + Manage Intercept Deployment Group resources. + + intercept-deployments + Manage Intercept Deployment resources. + + intercept-endpoint-group-associations + Manage Intercept Endpoint Group Association resources. + + intercept-endpoint-groups + Manage Intercept Endpoint Group resources. + mirroring-deployment-groups Manage Mirroring Deployment Group resources. diff --git a/gcloud/network-security/intercept-deployment-groups/create b/gcloud/network-security/intercept-deployment-groups/create new file mode 100644 index 000000000..c42498c77 --- /dev/null +++ b/gcloud/network-security/intercept-deployment-groups/create @@ -0,0 +1,135 @@ +NAME + gcloud network-security intercept-deployment-groups create - create an + Intercept Deployment Group + +SYNOPSIS + gcloud network-security intercept-deployment-groups create + (INTERCEPT_DEPLOYMENT_GROUP : --location=LOCATION) --network=NETWORK + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create an intercept deployment group. Successful creation of a deployment + group results in a deployment group in ACTIVE state. Check the progress of + deployment group creation by using gcloud network-security + intercept-deployment-groups list. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To create a intercept deployment group called my-deployment-group, in + project ID my-project, run: $ gcloud network-security intercept-deployment-groups create \ + my-deployment-group --project=my-project --location=global \ + --network=my-network + + OR + + $ gcloud network-security intercept-deployment-groups create \ + my-deployment-group --project=my-project --location=global \ + --network=projects/my-project/global/networks/my-network + + OR + + $ gcloud network-security intercept-deployment-groups create \ + projects/my-project/locations/global/interceptDeploymentGroups/\ + my-deployment-group \ + --network=projects/my-project/global/networks/my-network + + OR + + $ gcloud network-security intercept-deployment-groups create \ + projects/my-project/locations/global/interceptDeploymentGroups/\ + my-deployment-group \ + --network=projects/my-project/global/networks/my-network \ + --description='new description' + +POSITIONAL ARGUMENTS + Intercept deployment group resource - Intercept Deployment Group. 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 INTERCEPT_DEPLOYMENT_GROUP 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. + + INTERCEPT_DEPLOYMENT_GROUP + ID of the intercept deployment group or fully qualified identifier + for the intercept deployment group. + + To set the deployment-group-id attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT_GROUP 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 intercept deployment group. + + To set the location attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT_GROUP on the command + line with a fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Network resource - Intercept Deployment Group. 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 --network on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --network=NETWORK + ID of the network or fully qualified identifier for the network. + + To set the network-name attribute: + ▸ provide the argument --network on the command line. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + Description of the deployment group. + + --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. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 network-security intercept-deployment-groups create + + $ gcloud beta network-security intercept-deployment-groups create + diff --git a/gcloud/network-security/intercept-deployment-groups/delete b/gcloud/network-security/intercept-deployment-groups/delete new file mode 100644 index 000000000..4202b60e9 --- /dev/null +++ b/gcloud/network-security/intercept-deployment-groups/delete @@ -0,0 +1,89 @@ +NAME + gcloud network-security intercept-deployment-groups delete - delete an + Intercept Deployment Group + +SYNOPSIS + gcloud network-security intercept-deployment-groups delete + (INTERCEPT_DEPLOYMENT_GROUP : --location=LOCATION) [--async] + [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an intercept deployment group. Check the progress of deployment + group deletion by using gcloud network-security intercept-deployment-groups + list. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To delete an intercept deployment group called my-deployment-group, in + project ID my-project, run: + + $ gcloud network-security intercept-deployment-groups delete \ + my-deployment-group --project=my-project --location=global + + OR + + $ gcloud network-security intercept-deployment-groups delete \ + projects/my-project/locations/global/interceptDeploymentGroups/\ + my-deployment-group + +POSITIONAL ARGUMENTS + Intercept deployment group resource - Intercept Deployment Group. 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 INTERCEPT_DEPLOYMENT_GROUP 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. + + INTERCEPT_DEPLOYMENT_GROUP + ID of the intercept deployment group or fully qualified identifier + for the intercept deployment group. + + To set the deployment-group-id attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT_GROUP 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 intercept deployment group. + + To set the location attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT_GROUP 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. The default is True. Enabled by default, use --no-async to + disable. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 network-security intercept-deployment-groups delete + + $ gcloud beta network-security intercept-deployment-groups delete + diff --git a/gcloud/network-security/intercept-deployment-groups/describe b/gcloud/network-security/intercept-deployment-groups/describe new file mode 100644 index 000000000..bb481a671 --- /dev/null +++ b/gcloud/network-security/intercept-deployment-groups/describe @@ -0,0 +1,75 @@ +NAME + gcloud network-security intercept-deployment-groups describe - describe an + Intercept Deployment Group + +SYNOPSIS + gcloud network-security intercept-deployment-groups describe + (INTERCEPT_DEPLOYMENT_GROUP : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an intercept deployment group. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To get a description of an intercept deployment group called + my-deployment-group in project ID my-project, run: + + $ gcloud network-security intercept-deployment-groups describe \ + my-deployment-group --project=my-project --location=global + + OR + + $ gcloud network-security intercept-deployment-groups describe \ + projects/my-project/locations/global/interceptDeploymentGroups/\ + my-deployment-group + +POSITIONAL ARGUMENTS + Intercept deployment group resource - Intercept Deployment Group. 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 INTERCEPT_DEPLOYMENT_GROUP 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. + + INTERCEPT_DEPLOYMENT_GROUP + ID of the intercept deployment group or fully qualified identifier + for the intercept deployment group. + + To set the deployment-group-id attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT_GROUP 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 intercept deployment group. + + To set the location attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT_GROUP 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 + These variants are also available: + + $ gcloud alpha network-security intercept-deployment-groups describe + + $ gcloud beta network-security intercept-deployment-groups describe + diff --git a/gcloud/network-security/intercept-deployment-groups/help b/gcloud/network-security/intercept-deployment-groups/help new file mode 100644 index 000000000..9c008387f --- /dev/null +++ b/gcloud/network-security/intercept-deployment-groups/help @@ -0,0 +1,44 @@ +NAME + gcloud network-security intercept-deployment-groups - manage Intercept + Deployment Group resources + +SYNOPSIS + gcloud network-security intercept-deployment-groups COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This class provides commands for managing Intercept Deployment Groups. + + Attributes: category (str): The category under which this command group + falls. + +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 Intercept Deployment Group. + + delete + Delete an Intercept Deployment Group. + + describe + Describe an Intercept Deployment Group. + + list + List Intercept Deployment Groups. + + update + Update an Intercept Deployment Group. + +NOTES + These variants are also available: + + $ gcloud alpha network-security intercept-deployment-groups + + $ gcloud beta network-security intercept-deployment-groups + diff --git a/gcloud/network-security/intercept-deployment-groups/list b/gcloud/network-security/intercept-deployment-groups/list new file mode 100644 index 000000000..743394fc9 --- /dev/null +++ b/gcloud/network-security/intercept-deployment-groups/list @@ -0,0 +1,93 @@ +NAME + gcloud network-security intercept-deployment-groups list - list Intercept + Deployment Groups + +SYNOPSIS + gcloud network-security intercept-deployment-groups list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List intercept deployment groups. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To list intercept deployment groups in project ID my-project, run: + + $ gcloud network-security intercept-deployment-groups list \ + --location=global --project=my-project + + OR + + $ gcloud network-security intercept-deployment-groups list \ + --location=global + +FLAGS + Location resource - The location for a list operation 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 of the Intercept Deployment Group. Defaults to 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 of the Intercept Deployment Group. Defaults to 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. + + --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 network-security intercept-deployment-groups list + + $ gcloud beta network-security intercept-deployment-groups list + diff --git a/gcloud/network-security/intercept-deployment-groups/update b/gcloud/network-security/intercept-deployment-groups/update new file mode 100644 index 000000000..1e73d8800 --- /dev/null +++ b/gcloud/network-security/intercept-deployment-groups/update @@ -0,0 +1,136 @@ +NAME + gcloud network-security intercept-deployment-groups update - update an + Intercept Deployment Group + +SYNOPSIS + gcloud network-security intercept-deployment-groups update + (INTERCEPT_DEPLOYMENT_GROUP : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--max-wait=MAX_WAIT; default="20m"] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an intercept deployment group. Check the progress of deployment + group update by using gcloud network-security intercept-deployment-groups + list. + + For examples refer to the EXAMPLES section below. + +EXAMPLES + To update labels k1 and k2, run: + + $ gcloud network-security intercept-deployment-groups update \ + my-deployment-group --project=my-project --location=global \ + --update-labels=k1=v1,k2=v2 + + To remove labels k3 and k4, run: + + $ gcloud network-security intercept-deployment-groups update \ + my-deployment-group --project=my-project --location=global \ + --remove-labels=k3,k4 + + To clear all labels from the intercept deployment group, run: + + $ gcloud network-security intercept-deployment-groups update \ + my-deployment-group --project=my-project --location=global \ + --clear-labels + + To update description to 'new description', run: + + $ gcloud network-security intercept-deployment-groups update \ + my-deployment-group --project=my-project --location=global \ + --description='new description' + +POSITIONAL ARGUMENTS + Intercept deployment group resource - Intercept Deployment Group. 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 INTERCEPT_DEPLOYMENT_GROUP 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. + + INTERCEPT_DEPLOYMENT_GROUP + ID of the intercept deployment group or fully qualified identifier + for the intercept deployment group. + + To set the deployment-group-id attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT_GROUP 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 intercept deployment group. + + To set the location attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT_GROUP 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. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + Description of the deployment group. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + + --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 network-security intercept-deployment-groups update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud network-security intercept-deployment-groups 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 + These variants are also available: + + $ gcloud alpha network-security intercept-deployment-groups update + + $ gcloud beta network-security intercept-deployment-groups update + diff --git a/gcloud/network-security/intercept-deployments/create b/gcloud/network-security/intercept-deployments/create new file mode 100644 index 000000000..c6c5c94d8 --- /dev/null +++ b/gcloud/network-security/intercept-deployments/create @@ -0,0 +1,200 @@ +NAME + gcloud network-security intercept-deployments create - create an Intercept + Deployment + +SYNOPSIS + gcloud network-security intercept-deployments create + (INTERCEPT_DEPLOYMENT : --location=LOCATION) + (--forwarding-rule=FORWARDING_RULE + : --forwarding-rule-location=FORWARDING_RULE_LOCATION) + (--intercept-deployment-group=INTERCEPT_DEPLOYMENT_GROUP + : --intercept-deployment-group-location=INTERCEPT_DEPLOYMENT_GROUP_LOCATION) + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create an intercept deployment. Successful creation of a deployment results + in a deployment in ACTIVE state. Check the progress of deployment creation + by using gcloud network-security intercept-deployments list. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To create an intercept deployment called my-deployment, in project ID + my-project and zone us-central1-a, run: $ gcloud network-security intercept-deployments create \ + my-deployment --project=my-project --location=us-central1-a \ + --deployment-group-location=global \ + --forwarding-rule=my-forwarding-rule \ + --forwarding-rule-location=us-central1 \ + --intercept-deployment-group=my-deployment-group + + OR + + $ gcloud network-security intercept-deployments create \ + my-deployment --project=my-project --location=us-central1-a \ + --forwarding-rule=projects/my-project/regions/us-central1/\ + forwardingRules/my-forwarding-rule \ + --intercept-deployment-group=projects/my-project/locations/\ + global/interceptDeploymentGroups/my-deployment-group + + OR + + $ gcloud network-security intercept-deployments create \ + projects/my-project/locations/us-central1/interceptDeployments/\ + my-deployment \ + --forwarding-rule=projects/my-project/regions/us-central1/\ + forwardingRules/my-forwarding-rule \ + --intercept-deployment-group=projects/my-project/locations/\ + global/interceptDeploymentGroups/my-deployment-group + + OR + + $ gcloud network-security intercept-deployments create \ + projects/my-project/locations/us-central1/interceptDeployments/\ + my-deployment \ + --forwarding-rule=projects/my-project/regions/us-central1/\ + forwardingRules/my-forwarding-rule \ + --intercept-deployment-group=projects/my-project/locations/\ + global/interceptDeploymentGroups/my-deployment-group \ + --description="my-description" + +POSITIONAL ARGUMENTS + Intercept deployment resource - Intercept Deployment. 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 INTERCEPT_DEPLOYMENT 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. + + INTERCEPT_DEPLOYMENT + ID of the intercept deployment or fully qualified identifier for the + intercept deployment. + + To set the deployment-id attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT 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 intercept deployment. + + To set the location attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + ForwardingRule resource - Intercept Deployment Forwarding Rule. 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 --forwarding-rule 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. + + --forwarding-rule=FORWARDING_RULE + ID of the forwardingRule or fully qualified identifier for the + forwardingRule. + + To set the forwarding-rule-id attribute: + ▸ provide the argument --forwarding-rule on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --forwarding-rule-location=FORWARDING_RULE_LOCATION + The Cloud region for the forwardingRule. + + To set the forwarding-rule-location attribute: + ▸ provide the argument --forwarding-rule on the command line with a + fully specified name; + ▸ provide the argument --forwarding-rule-location on the command + line. + + Intercept deployment group resource - Intercept Deployment Group. 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 --intercept-deployment-group 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. + + --intercept-deployment-group=INTERCEPT_DEPLOYMENT_GROUP + ID of the intercept deployment group or fully qualified identifier + for the intercept deployment group. + + To set the id attribute: + ▸ provide the argument --intercept-deployment-group on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --intercept-deployment-group-location=INTERCEPT_DEPLOYMENT_GROUP_LOCATION + Location of the intercept deployment group. + + To set the location attribute: + ▸ provide the argument --intercept-deployment-group on the command + line with a fully specified name; + ▸ provide the argument --intercept-deployment-group-location on the + command line; + ▸ provide the argument --location on the command line; + ▸ provide the argument + networksecurity.projects.locations.interceptDeployments on the + command line with a fully specified name. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + Description of the deployment. + + --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. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 network-security intercept-deployments create + + $ gcloud beta network-security intercept-deployments create + diff --git a/gcloud/network-security/intercept-deployments/delete b/gcloud/network-security/intercept-deployments/delete new file mode 100644 index 000000000..718010a11 --- /dev/null +++ b/gcloud/network-security/intercept-deployments/delete @@ -0,0 +1,81 @@ +NAME + gcloud network-security intercept-deployments delete - delete an Intercept + Deployment + +SYNOPSIS + gcloud network-security intercept-deployments delete + (INTERCEPT_DEPLOYMENT : --location=LOCATION) [--async] + [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an intercept deployment. Check the progress of deployment deletion + by using gcloud network-security intercept-deployments list. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To delete an intercept deployment called my-deployment in location + us-central1, run: + + $ gcloud network-security intercept-deployments delete \ + my-deployment --location=us-central1-a --project=my-project + +POSITIONAL ARGUMENTS + Intercept deployment resource - Intercept Deployment. 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 INTERCEPT_DEPLOYMENT 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. + + INTERCEPT_DEPLOYMENT + ID of the intercept deployment or fully qualified identifier for the + intercept deployment. + + To set the deployment-id attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT 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 intercept deployment. + + To set the location attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT 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. The default is True. Enabled by default, use --no-async to + disable. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 network-security intercept-deployments delete + + $ gcloud beta network-security intercept-deployments delete + diff --git a/gcloud/network-security/intercept-deployments/describe b/gcloud/network-security/intercept-deployments/describe new file mode 100644 index 000000000..c071e6dc9 --- /dev/null +++ b/gcloud/network-security/intercept-deployments/describe @@ -0,0 +1,73 @@ +NAME + gcloud network-security intercept-deployments describe - describe an + Intercept Deployment + +SYNOPSIS + gcloud network-security intercept-deployments describe + (INTERCEPT_DEPLOYMENT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an intercept deployment. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To get a description of an intercept deployment called my-deployment in + zone us-central1-a, run: + + $ gcloud network-security intercept-deployments describe \ + my-deployment --location=us-central1-a --project=my-project + + OR + + $ gcloud network-security intercept-deployments describe \ + projects/my-project/locations/us-central1-a/\ + interceptDeployments/my-deployment + +POSITIONAL ARGUMENTS + Intercept deployment resource - Intercept Deployment. 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 INTERCEPT_DEPLOYMENT 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. + + INTERCEPT_DEPLOYMENT + ID of the intercept deployment or fully qualified identifier for the + intercept deployment. + + To set the deployment-id attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT 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 intercept deployment. + + To set the location attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT 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 + These variants are also available: + + $ gcloud alpha network-security intercept-deployments describe + + $ gcloud beta network-security intercept-deployments describe + diff --git a/gcloud/network-security/intercept-deployments/help b/gcloud/network-security/intercept-deployments/help new file mode 100644 index 000000000..e9562d0d2 --- /dev/null +++ b/gcloud/network-security/intercept-deployments/help @@ -0,0 +1,42 @@ +NAME + gcloud network-security intercept-deployments - manage Intercept Deployment + resources + +SYNOPSIS + gcloud network-security intercept-deployments COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The gcloud intercept-deployments command group lets you manage zonal + deployments for your Intercept Deployment Group. + +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 Intercept Deployment. + + delete + Delete an Intercept Deployment. + + describe + Describe an Intercept Deployment. + + list + List Intercept Deployments. + + update + Update an Intercept Deployment. + +NOTES + These variants are also available: + + $ gcloud alpha network-security intercept-deployments + + $ gcloud beta network-security intercept-deployments + diff --git a/gcloud/network-security/intercept-deployments/list b/gcloud/network-security/intercept-deployments/list new file mode 100644 index 000000000..453eb58b3 --- /dev/null +++ b/gcloud/network-security/intercept-deployments/list @@ -0,0 +1,93 @@ +NAME + gcloud network-security intercept-deployments list - list Intercept + Deployments + +SYNOPSIS + gcloud network-security intercept-deployments list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List intercept deployments. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To list intercept deployments in project my-project and zone us-central1-a, + run: + + $ gcloud network-security intercept-deployments list \ + --project=my-project --location=us-central1-a + + To list intercept deployments from all zones, run: + + $ gcloud network-security intercept-deployments list \ + --project=my-project --location=- + +FLAGS + Location resource - Zone of the deployment 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 of the Intercept Deployment. Defaults to a wildcard 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 of the Intercept Deployment. Defaults to a wildcard. + +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 network-security intercept-deployments list + + $ gcloud beta network-security intercept-deployments list + diff --git a/gcloud/network-security/intercept-deployments/update b/gcloud/network-security/intercept-deployments/update new file mode 100644 index 000000000..2a8d07040 --- /dev/null +++ b/gcloud/network-security/intercept-deployments/update @@ -0,0 +1,133 @@ +NAME + gcloud network-security intercept-deployments update - update an Intercept + Deployment + +SYNOPSIS + gcloud network-security intercept-deployments update + (INTERCEPT_DEPLOYMENT : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--max-wait=MAX_WAIT; default="20m"] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an intercept deployment. Check the progress of deployment update by + using gcloud network-security intercept-deployments list. + + For examples refer to the EXAMPLES section below. + +EXAMPLES + To update labels k1 and k2, run: + + $ gcloud network-security intercept-deployments update \ + my-deployment --project=my-project --location=us-central1-a \ + --update-labels=k1=v1,k2=v2 + + To remove labels k3 and k4, run: + + $ gcloud network-security intercept-deployments update \ + my-deployment --project=my-project --location=us-central1-a \ + --remove-labels=k3,k4 + + To clear all labels from the intercept deployment, run: + + $ gcloud network-security intercept-deployments update \ + my-deploymen --project=my-project --location=us-central1-a \ + --clear-labels + + To update description to 'new description', run: + + $ gcloud network-security intercept-deployments update \ + my-deploymen --project=my-project --location=us-central1-a \ + --description="new description" + +POSITIONAL ARGUMENTS + Intercept deployment resource - Intercept Deployment. 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 INTERCEPT_DEPLOYMENT 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. + + INTERCEPT_DEPLOYMENT + ID of the intercept deployment or fully qualified identifier for the + intercept deployment. + + To set the deployment-id attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT 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 intercept deployment. + + To set the location attribute: + ▸ provide the argument INTERCEPT_DEPLOYMENT 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. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + Description of the deployment. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + + --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 network-security intercept-deployments update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud network-security intercept-deployments 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 + These variants are also available: + + $ gcloud alpha network-security intercept-deployments update + + $ gcloud beta network-security intercept-deployments update + diff --git a/gcloud/network-security/intercept-endpoint-group-associations/create b/gcloud/network-security/intercept-endpoint-group-associations/create new file mode 100644 index 000000000..31671f856 --- /dev/null +++ b/gcloud/network-security/intercept-endpoint-group-associations/create @@ -0,0 +1,170 @@ +NAME + gcloud network-security intercept-endpoint-group-associations create - + create an Intercept Endpoint Group Association + +SYNOPSIS + gcloud network-security intercept-endpoint-group-associations create + (INTERCEPT_ENDPOINT_GROUP_ASSOCIATION : --location=LOCATION) + --network=NETWORK + (--intercept-endpoint-group=INTERCEPT_ENDPOINT_GROUP + : --intercept-endpoint-group-location=INTERCEPT_ENDPOINT_GROUP_LOCATION) + [--async] [--labels=[KEY=VALUE,...]] + [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create an intercept endpoint group association. Successful creation of an + association results in an association in ACTIVE state. Check the progress + of association creation by using gcloud network-security + intercept-endpoint-group-associations list. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To create an intercept endpoint group association called my-association, in + project ID my-project, run: + + $ gcloud network-security intercept-endpoint-group-associations \ create my-association --project=my-project --location=global \ + --intercept-endpoint-group=my-endpoint-group \ + --network=my-network + + OR + + $ gcloud network-security intercept-endpoint-group-associations \ create my-association --project=my-project --location=global \ + --intercept-endpoint-group=my-endpoint-group \ + --network=projects/my-project/global/networks/my-network + + OR + + $ gcloud network-security intercept-endpoint-group-associations \ create \ + projects/my-project/locations/global/\ + interceptEndpointGroupAssociations/my-association \ + --intercept-endpoint-group=projects/my-project/locations/\ + global/interceptEndpointGroups/my-endpoint-group \ + --network=projects/my-project/global/networks/my-network + +POSITIONAL ARGUMENTS + Intercept endpoint group association resource - Intercept Endpoint Group + Association. 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 INTERCEPT_ENDPOINT_GROUP_ASSOCIATION 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. + + INTERCEPT_ENDPOINT_GROUP_ASSOCIATION + ID of the intercept endpoint group association or fully qualified + identifier for the intercept endpoint group association. + + To set the endpoint-group-association-id attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP_ASSOCIATION 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 intercept endpoint group association. + + To set the location attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP_ASSOCIATION on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Network resource - Intercept Endpoint Group Association. 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 --network on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --network=NETWORK + ID of the network or fully qualified identifier for the network. + + To set the network-name attribute: + ▸ provide the argument --network on the command line. + + Intercept endpoint group resource - Intercept Endpoint Group. 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 --intercept-endpoint-group 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. + + --intercept-endpoint-group=INTERCEPT_ENDPOINT_GROUP + ID of the intercept endpoint group or fully qualified identifier for + the intercept endpoint group. + + To set the id attribute: + ▸ provide the argument --intercept-endpoint-group on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --intercept-endpoint-group-location=INTERCEPT_ENDPOINT_GROUP_LOCATION + Location of the intercept endpoint group. + + To set the location attribute: + ▸ provide the argument --intercept-endpoint-group on the command + line with a fully specified name; + ▸ provide the argument --intercept-endpoint-group-location on the + command line; + ▸ provide the argument --location on the command line; + ▸ provide the argument + networksecurity.projects.locations.interceptEndpointGroupAssociations + on the command line with a fully specified name. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --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. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 network-security \ + intercept-endpoint-group-associations create + + $ gcloud beta network-security \ + intercept-endpoint-group-associations create + diff --git a/gcloud/network-security/intercept-endpoint-group-associations/delete b/gcloud/network-security/intercept-endpoint-group-associations/delete new file mode 100644 index 000000000..b9124916f --- /dev/null +++ b/gcloud/network-security/intercept-endpoint-group-associations/delete @@ -0,0 +1,90 @@ +NAME + gcloud network-security intercept-endpoint-group-associations delete - + delete an Intercept Endpoint Group Association + +SYNOPSIS + gcloud network-security intercept-endpoint-group-associations delete + (INTERCEPT_ENDPOINT_GROUP_ASSOCIATION : --location=LOCATION) [--async] + [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an intercept endpoint group association. Check the progress of + deletion by using gcloud network-security + intercept-endpoint-group-associations list. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To delete an intercept endpoint group association called my-association, in + project ID my-project, run: + + $ gcloud network-security intercept-endpoint-group-associations \ delete my-association --project=my-project --location=global + + OR + + $ gcloud network-security intercept-endpoint-group-associations \ delete \ + projects/my-project/locations/global/\ + interceptEndpointGroupAssociations/my-association + +POSITIONAL ARGUMENTS + Intercept endpoint group association resource - Intercept Endpoint Group + Association. 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 INTERCEPT_ENDPOINT_GROUP_ASSOCIATION 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. + + INTERCEPT_ENDPOINT_GROUP_ASSOCIATION + ID of the intercept endpoint group association or fully qualified + identifier for the intercept endpoint group association. + + To set the endpoint-group-association-id attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP_ASSOCIATION 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 intercept endpoint group association. + + To set the location attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP_ASSOCIATION 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. The default is True. Enabled by default, use --no-async to + disable. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 network-security \ + intercept-endpoint-group-associations delete + + $ gcloud beta network-security \ + intercept-endpoint-group-associations delete + diff --git a/gcloud/network-security/intercept-endpoint-group-associations/describe b/gcloud/network-security/intercept-endpoint-group-associations/describe new file mode 100644 index 000000000..a89aede1f --- /dev/null +++ b/gcloud/network-security/intercept-endpoint-group-associations/describe @@ -0,0 +1,76 @@ +NAME + gcloud network-security intercept-endpoint-group-associations describe - + describe an Intercept Endpoint Group Association + +SYNOPSIS + gcloud network-security intercept-endpoint-group-associations describe + (INTERCEPT_ENDPOINT_GROUP_ASSOCIATION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an intercept endpoint group association. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To get a description of an intercept endpoint group association called + my-association in project my-project and location global, run: + + $ gcloud network-security intercept-endpoint-group-associations \ describe my-association --project=my-project --location=global + + OR + + $ gcloud network-security intercept-endpoint-group-associations \ describe \ + projects/my-project/locations/global/\ + interceptEndpointGroupAssociations/my-association + +POSITIONAL ARGUMENTS + Intercept endpoint group association resource - Intercept Endpoint Group + Association. 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 INTERCEPT_ENDPOINT_GROUP_ASSOCIATION 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. + + INTERCEPT_ENDPOINT_GROUP_ASSOCIATION + ID of the intercept endpoint group association or fully qualified + identifier for the intercept endpoint group association. + + To set the endpoint-group-association-id attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP_ASSOCIATION 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 intercept endpoint group association. + + To set the location attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP_ASSOCIATION 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 + These variants are also available: + + $ gcloud alpha network-security \ + intercept-endpoint-group-associations describe + + $ gcloud beta network-security \ + intercept-endpoint-group-associations describe + diff --git a/gcloud/network-security/intercept-endpoint-group-associations/help b/gcloud/network-security/intercept-endpoint-group-associations/help new file mode 100644 index 000000000..bd4b01bd6 --- /dev/null +++ b/gcloud/network-security/intercept-endpoint-group-associations/help @@ -0,0 +1,42 @@ +NAME + gcloud network-security intercept-endpoint-group-associations - manage + Intercept Endpoint Group Association resources + +SYNOPSIS + gcloud network-security intercept-endpoint-group-associations COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The gcloud intercept-endpoint-group-associations command group lets you + associate and deassociate networks to your Intercept Endpoint Group. + +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 Intercept Endpoint Group Association. + + delete + Delete an Intercept Endpoint Group Association. + + describe + Describe an Intercept Endpoint Group Association. + + list + List Intercept Endpoint Group Associations. + + update + Update an Intercept Endpoint Group Association. + +NOTES + These variants are also available: + + $ gcloud alpha network-security intercept-endpoint-group-associations + + $ gcloud beta network-security intercept-endpoint-group-associations + diff --git a/gcloud/network-security/intercept-endpoint-group-associations/list b/gcloud/network-security/intercept-endpoint-group-associations/list new file mode 100644 index 000000000..07144e051 --- /dev/null +++ b/gcloud/network-security/intercept-endpoint-group-associations/list @@ -0,0 +1,99 @@ +NAME + gcloud network-security intercept-endpoint-group-associations list - list + Intercept Endpoint Group Associations + +SYNOPSIS + gcloud network-security intercept-endpoint-group-associations list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List intercept endpoint group associations. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To list intercept endpoint group associations in project my-project and + location global, run: + + $ gcloud network-security intercept-endpoint-group-associations \ list --project=my-project --location=global + + OR + + $ gcloud network-security intercept-endpoint-group-associations \ list --location=global + + OR + + $ gcloud network-security intercept-endpoint-group-associations \ list --location=projects/my-project/locations/global + +FLAGS + Location resource - The location for a list operation 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 of the Intercept Endpoint Group Association. Defaults to + 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 of the Intercept Endpoint Group Association. Defaults to + 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. + + --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 network-security \ + intercept-endpoint-group-associations list + + $ gcloud beta network-security \ + intercept-endpoint-group-associations list + diff --git a/gcloud/network-security/intercept-endpoint-group-associations/update b/gcloud/network-security/intercept-endpoint-group-associations/update new file mode 100644 index 000000000..f663e3034 --- /dev/null +++ b/gcloud/network-security/intercept-endpoint-group-associations/update @@ -0,0 +1,125 @@ +NAME + gcloud network-security intercept-endpoint-group-associations update - + update an Intercept Endpoint Group Association + +SYNOPSIS + gcloud network-security intercept-endpoint-group-associations update + (INTERCEPT_ENDPOINT_GROUP_ASSOCIATION : --location=LOCATION) [--async] + [--max-wait=MAX_WAIT; default="20m"] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an intercept endpoint group association. Check the progress of + association update by using gcloud network-security + intercept-endpoint-group-associations list. + + For examples refer to the EXAMPLES section below. + +EXAMPLES + To update labels k1 and k2, run: + + $ gcloud network-security intercept-endpoint-group-associations \ update my-association --project=my-project --location=global \ + --update-labels=k1=v1,k2=v2 + + To remove labels k3 and k4, run: + + $ gcloud network-security intercept-endpoint-group-associations \ update my-association --project=my-project --location=global \ + --remove-labels=k3,k4 + + To clear all labels from the intercept endpoint group association, run: + + $ gcloud network-security intercept-endpoint-group-associations \ update my-association --project=my-project --location=global \ + --clear-labels + +POSITIONAL ARGUMENTS + Intercept endpoint group association resource - Intercept Endpoint Group + Association. 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 INTERCEPT_ENDPOINT_GROUP_ASSOCIATION 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. + + INTERCEPT_ENDPOINT_GROUP_ASSOCIATION + ID of the intercept endpoint group association or fully qualified + identifier for the intercept endpoint group association. + + To set the endpoint-group-association-id attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP_ASSOCIATION 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 intercept endpoint group association. + + To set the location attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP_ASSOCIATION 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. The default is True. Enabled by default, use --no-async to + disable. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + + --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 network-security intercept-endpoint-group-associations \ + update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud network-security intercept-endpoint-group-associations \ + 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 + These variants are also available: + + $ gcloud alpha network-security \ + intercept-endpoint-group-associations update + + $ gcloud beta network-security \ + intercept-endpoint-group-associations update + diff --git a/gcloud/network-security/intercept-endpoint-groups/create b/gcloud/network-security/intercept-endpoint-groups/create new file mode 100644 index 000000000..a96899252 --- /dev/null +++ b/gcloud/network-security/intercept-endpoint-groups/create @@ -0,0 +1,157 @@ +NAME + gcloud network-security intercept-endpoint-groups create - create a + Intercept Endpoint Group + +SYNOPSIS + gcloud network-security intercept-endpoint-groups create + (INTERCEPT_ENDPOINT_GROUP : --location=LOCATION) + (--intercept-deployment-group=INTERCEPT_DEPLOYMENT_GROUP + : --intercept-deployment-group-location=INTERCEPT_DEPLOYMENT_GROUP_LOCATION) + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a intercept endpoint group. Successful creation of an endpoint group + results in an endpoint group in ACTIVE state. Check the progress of + endpoint group creation by using gcloud network-security + intercept-endpoint-groups list. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To create a intercept endpoint group called my-endpoint-group, in project + ID my-project, run: $ gcloud network-security intercept-endpoint-groups create \ + my-endpoint-group --project=my-project --location=global \ + --intercept-deployment-group=my-deployment-group + + OR + + $ gcloud network-security intercept-endpoint-groups create \ + my-endpoint-group --project=my-project --location=global \ + --intercept-deployment-group=projects/my-project/locations/\ + global/interceptDeploymentGroups/my-deployment-group + + OR + + $ gcloud network-security intercept-endpoint-groups create \ + projects/my-project/locations/global/interceptEndpointGroups/\ + my-endpoint-group \ + --intercept-deployment-group=projects/my-project/locations/\ + global/interceptDeploymentGroups/my-deployment-group + + OR + + $ gcloud network-security intercept-endpoint-groups create \ + my-endpoint-group --project=my-project --location=global \ + --mirroring-deployment-group=projects/my-project/locations/\ + global/interceptDeploymentGroups/my-deployment-group \ + --description='new description' + +POSITIONAL ARGUMENTS + Intercept endpoint group resource - Intercept Endpoint Group. 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 INTERCEPT_ENDPOINT_GROUP 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. + + INTERCEPT_ENDPOINT_GROUP + ID of the intercept endpoint group or fully qualified identifier for + the intercept endpoint group. + + To set the endpoint-group-id attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP 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 intercept endpoint group. + + To set the location attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Intercept deployment group resource - Intercept Deployment Group. 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 --intercept-deployment-group 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. + + --intercept-deployment-group=INTERCEPT_DEPLOYMENT_GROUP + ID of the intercept deployment group or fully qualified identifier + for the intercept deployment group. + + To set the id attribute: + ▸ provide the argument --intercept-deployment-group on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --intercept-deployment-group-location=INTERCEPT_DEPLOYMENT_GROUP_LOCATION + Location of the intercept deployment group. + + To set the location attribute: + ▸ provide the argument --intercept-deployment-group on the command + line with a fully specified name; + ▸ provide the argument --intercept-deployment-group-location on the + command line; + ▸ provide the argument --location on the command line; + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP on the command line + with a fully specified name. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + Description of the endpoint + + --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. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 network-security intercept-endpoint-groups create + + $ gcloud beta network-security intercept-endpoint-groups create + diff --git a/gcloud/network-security/intercept-endpoint-groups/delete b/gcloud/network-security/intercept-endpoint-groups/delete new file mode 100644 index 000000000..b06417efd --- /dev/null +++ b/gcloud/network-security/intercept-endpoint-groups/delete @@ -0,0 +1,86 @@ +NAME + gcloud network-security intercept-endpoint-groups delete - delete a + Intercept Endpoint Group + +SYNOPSIS + gcloud network-security intercept-endpoint-groups delete + (INTERCEPT_ENDPOINT_GROUP : --location=LOCATION) [--async] + [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a intercept endpoint group. Check the progress of endpoint group + deletion by using gcloud network-security intercept-endpoint-groups list. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To delete a intercept endpoint group called my-endpoint-group, in project + ID my-project, run: $ gcloud network-security intercept-endpoint-groups delete \ + my-endpoint-group --project=my-project --location=global + + OR + + $ gcloud network-security intercept-endpoint-groups delete \ + projects/my-project/locations/global/interceptEndpointGroups/\ + my-endpoint-group + +POSITIONAL ARGUMENTS + Intercept endpoint group resource - Intercept Endpoint Group. 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 INTERCEPT_ENDPOINT_GROUP 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. + + INTERCEPT_ENDPOINT_GROUP + ID of the intercept endpoint group or fully qualified identifier for + the intercept endpoint group. + + To set the endpoint-group-id attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP 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 intercept endpoint group. + + To set the location attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP 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. The default is True. Enabled by default, use --no-async to + disable. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 network-security intercept-endpoint-groups delete + + $ gcloud beta network-security intercept-endpoint-groups delete + diff --git a/gcloud/network-security/intercept-endpoint-groups/describe b/gcloud/network-security/intercept-endpoint-groups/describe new file mode 100644 index 000000000..c15558c31 --- /dev/null +++ b/gcloud/network-security/intercept-endpoint-groups/describe @@ -0,0 +1,72 @@ +NAME + gcloud network-security intercept-endpoint-groups describe - describe a + Intercept Endpoint Group + +SYNOPSIS + gcloud network-security intercept-endpoint-groups describe + (INTERCEPT_ENDPOINT_GROUP : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a intercept endpoint group. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To get a description of a intercept endpoint group called my-endpoint-group + in project ID my-project, run: $ gcloud network-security intercept-endpoint-groups describe \ + my-endpoint-group --project=my-project --location=global + + OR + + $ gcloud network-security intercept-endpoint-groups describe \ + projects/my-project/locations/global/interceptEndpointGroups/\ + my-endpoint-group + +POSITIONAL ARGUMENTS + Intercept endpoint group resource - Intercept Endpoint Group. 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 INTERCEPT_ENDPOINT_GROUP 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. + + INTERCEPT_ENDPOINT_GROUP + ID of the intercept endpoint group or fully qualified identifier for + the intercept endpoint group. + + To set the endpoint-group-id attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP 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 intercept endpoint group. + + To set the location attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP 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 + These variants are also available: + + $ gcloud alpha network-security intercept-endpoint-groups describe + + $ gcloud beta network-security intercept-endpoint-groups describe + diff --git a/gcloud/network-security/intercept-endpoint-groups/help b/gcloud/network-security/intercept-endpoint-groups/help new file mode 100644 index 000000000..57ab2e12a --- /dev/null +++ b/gcloud/network-security/intercept-endpoint-groups/help @@ -0,0 +1,42 @@ +NAME + gcloud network-security intercept-endpoint-groups - manage Intercept + Endpoint Group resources + +SYNOPSIS + gcloud network-security intercept-endpoint-groups COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The gcloud intercept-endpoint-groups command group lets you create, delete + and manage endpoint 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 + Create a Intercept Endpoint Group. + + delete + Delete a Intercept Endpoint Group. + + describe + Describe a Intercept Endpoint Group. + + list + List Intercept Endpoint Groups. + + update + Update a Intercept Endpoint Group. + +NOTES + These variants are also available: + + $ gcloud alpha network-security intercept-endpoint-groups + + $ gcloud beta network-security intercept-endpoint-groups + diff --git a/gcloud/network-security/intercept-endpoint-groups/list b/gcloud/network-security/intercept-endpoint-groups/list new file mode 100644 index 000000000..147d7390b --- /dev/null +++ b/gcloud/network-security/intercept-endpoint-groups/list @@ -0,0 +1,101 @@ +NAME + gcloud network-security intercept-endpoint-groups list - list Intercept + Endpoint Groups + +SYNOPSIS + gcloud network-security intercept-endpoint-groups list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List intercept endpoint groups. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To list intercept endpoint groups in project ID my-project, run: $ gcloud network-security intercept-endpoint-groups list \ + --project=my-project --location=global + + OR + + $ gcloud network-security intercept-endpoint-groups list \ + --location=global + + OR + + $ gcloud network-security intercept-endpoint-groups list \ + --location=projects/my-project/locations/global + + OR + + $ gcloud network-security intercept-endpoint-groups list \ + projects/my-project/locations/global/interceptEndpointGroups + +FLAGS + Location resource - The location for a list operation 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 of the Intercept Endpoint Group. Defaults to 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 of the Intercept Endpoint Group. Defaults to 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. + + --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 network-security intercept-endpoint-groups list + + $ gcloud beta network-security intercept-endpoint-groups list + diff --git a/gcloud/network-security/intercept-endpoint-groups/update b/gcloud/network-security/intercept-endpoint-groups/update new file mode 100644 index 000000000..ddb94246c --- /dev/null +++ b/gcloud/network-security/intercept-endpoint-groups/update @@ -0,0 +1,135 @@ +NAME + gcloud network-security intercept-endpoint-groups update - update a + Intercept Endpoint Group + +SYNOPSIS + gcloud network-security intercept-endpoint-groups update + (INTERCEPT_ENDPOINT_GROUP : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--max-wait=MAX_WAIT; default="20m"] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a intercept endpoint groups. Check the progress of endpoint group + update by using gcloud network-security intercept-endpoint-groups list. + + For examples refer to the EXAMPLES section below. + +EXAMPLES + To update labels k1 and k2, run: + + $ gcloud network-security intercept-endpoint-groups update \ + my-endpoint-group --project=my-project \ + --location=us-central1-a --update-labels=k1=v1,k2=v2 + + To remove labels k3 and k4, run: + + $ gcloud network-security intercept-endpoint-groups update \ + my-endpoint-group --project=my-project \ + --location=us-central1-a --remove-labels=k3,k4 + + To clear all labels from the intercept endpoint group, run: + + $ gcloud network-security intercept-endpoint-groups update \ + my-endpoint-group --project=my-project \ + --location=us-central1-a --clear-labels + + To update description to 'new description', run: + + $ gcloud network-security intercept-endpoint-groups update \ + my-endpoint-group --project=my-project \ + --location=us-central1-a --description='new description' + +POSITIONAL ARGUMENTS + Intercept endpoint group resource - Intercept Endpoint Group. 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 INTERCEPT_ENDPOINT_GROUP 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. + + INTERCEPT_ENDPOINT_GROUP + ID of the intercept endpoint group or fully qualified identifier for + the intercept endpoint group. + + To set the endpoint-group-id attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP 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 intercept endpoint group. + + To set the location attribute: + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP 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. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + Description of the endpoint + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + + --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 network-security intercept-endpoint-groups update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud network-security intercept-endpoint-groups 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 + These variants are also available: + + $ gcloud alpha network-security intercept-endpoint-groups update + + $ gcloud beta network-security intercept-endpoint-groups update + diff --git a/gcloud/network-security/security-profile-groups/create b/gcloud/network-security/security-profile-groups/create index c6e0a70cb..449b4d020 100644 --- a/gcloud/network-security/security-profile-groups/create +++ b/gcloud/network-security/security-profile-groups/create @@ -5,12 +5,10 @@ NAME SYNOPSIS gcloud network-security security-profile-groups create (SECURITY_PROFILE_GROUP - : --location=LOCATION --organization=ORGANIZATION) [--async] - [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--custom-mirroring-profile=CUSTOM_MIRRORING_PROFILE - : --custom-mirroring-profile-location=CUSTOM_MIRRORING_PROFILE_LOCATION --custom-mirroring-profile-organization=CUSTOM_MIRRORING_PROFILE_ORGANIZATION] - [--threat-prevention-profile=THREAT_PREVENTION_PROFILE - : --threat-prevention-profile-location=THREAT_PREVENTION_PROFILE_LOCATION --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION] + : --location=LOCATION --organization=ORGANIZATION) + ([--custom-intercept-profile=CUSTOM_INTERCEPT_PROFILE + : --custom-intercept-profile-location=CUSTOM_INTERCEPT_PROFILE_LOCATION --custom-intercept-profile-organization=CUSTOM_INTERCEPT_PROFILE_ORGANIZATION] [--custom-mirroring-profile=CUSTOM_MIRRORING_PROFILE : --custom-mirroring-profile-location=CUSTOM_MIRRORING_PROFILE_LOCATION --custom-mirroring-profile-organization=CUSTOM_MIRRORING_PROFILE_ORGANIZATION] [--threat-prevention-profile=THREAT_PREVENTION_PROFILE : --threat-prevention-profile-location=THREAT_PREVENTION_PROFILE_LOCATION --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION]) + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -61,7 +59,140 @@ POSITIONAL ARGUMENTS with a fully specified name; ▸ provide the argument --organization on the command line. -FLAGS +REQUIRED FLAGS + At least one of these must be specified: + + Security Profile resource - Path to Security Profile resource. The + arguments in this group can be used to specify the attributes of this + resource. + + --custom-intercept-profile=CUSTOM_INTERCEPT_PROFILE + ID of the Security Profile or fully qualified identifier for the + Security Profile. + + To set the name attribute: + ▫ provide the argument --custom-intercept-profile on the command + line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --custom-intercept-profile-location=CUSTOM_INTERCEPT_PROFILE_LOCATION + Location of the Security Profile. NOTE: Only global security + profiles are supported. + + To set the location attribute: + ▫ provide the argument --custom-intercept-profile on the command + line with a fully specified name; + ▫ provide the argument --custom-intercept-profile-location on the + command line; + ▫ provide the argument --location on the command line; + ▫ provide the argument + networksecurity.organizations.locations.securityProfileGroups on + the command line with a fully specified name. + + --custom-intercept-profile-organization=CUSTOM_INTERCEPT_PROFILE_ORGANIZATION + Organization ID of the Security Profile. + + To set the organization attribute: + ▫ provide the argument --custom-intercept-profile on the command + line with a fully specified name; + ▫ provide the argument --custom-intercept-profile-organization on + the command line; + ▫ provide the argument --organization on the command line; + ▫ provide the argument + networksecurity.organizations.locations.securityProfileGroups on + the command line with a fully specified name. + + Security Profile resource - Path to Security Profile resource. The + arguments in this group can be used to specify the attributes of this + resource. + + --custom-mirroring-profile=CUSTOM_MIRRORING_PROFILE + ID of the Security Profile or fully qualified identifier for the + Security Profile. + + To set the name attribute: + ▫ provide the argument --custom-mirroring-profile on the command + line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --custom-mirroring-profile-location=CUSTOM_MIRRORING_PROFILE_LOCATION + Location of the Security Profile. NOTE: Only global security + profiles are supported. + + To set the location attribute: + ▫ provide the argument --custom-mirroring-profile on the command + line with a fully specified name; + ▫ provide the argument --custom-mirroring-profile-location on the + command line; + ▫ provide the argument --location on the command line; + ▫ provide the argument + networksecurity.organizations.locations.securityProfileGroups on + the command line with a fully specified name. + + --custom-mirroring-profile-organization=CUSTOM_MIRRORING_PROFILE_ORGANIZATION + Organization ID of the Security Profile. + + To set the organization attribute: + ▫ provide the argument --custom-mirroring-profile on the command + line with a fully specified name; + ▫ provide the argument --custom-mirroring-profile-organization on + the command line; + ▫ provide the argument --organization on the command line; + ▫ provide the argument + networksecurity.organizations.locations.securityProfileGroups on + the command line with a fully specified name. + + Security Profile resource - Path to Security Profile resource. The + arguments in this group can be used to specify the attributes of this + resource. + + --threat-prevention-profile=THREAT_PREVENTION_PROFILE + ID of the Security Profile or fully qualified identifier for the + Security Profile. + + To set the name attribute: + ▫ provide the argument --threat-prevention-profile on the command + line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --threat-prevention-profile-location=THREAT_PREVENTION_PROFILE_LOCATION + Location of the Security Profile. NOTE: Only global security + profiles are supported. + + To set the location attribute: + ▫ provide the argument --threat-prevention-profile on the command + line with a fully specified name; + ▫ provide the argument --threat-prevention-profile-location on + the command line; + ▫ provide the argument --security-profile-location on the command + line; + ▫ provide the argument --location on the command line; + ▫ provide the argument + networksecurity.organizations.locations.securityProfileGroups on + the command line with a fully specified name. + + --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION + Organization ID of the Security Profile. + + To set the organization attribute: + ▫ provide the argument --threat-prevention-profile on the command + line with a fully specified name; + ▫ provide the argument --threat-prevention-profile-organization + on the command line; + ▫ provide the argument --security-profile-organization on the + command line; + ▫ provide the argument --organization on the command line; + ▫ provide the argument + networksecurity.organizations.locations.securityProfileGroups on + the command line with a fully specified name. + +OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to complete. The default is False. @@ -77,94 +208,6 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - Security Profile resource - Path to Security Profile resource. The - arguments in this group can be used to specify the attributes of this - resource. - - --custom-mirroring-profile=CUSTOM_MIRRORING_PROFILE - ID of the Security Profile or fully qualified identifier for the - Security Profile. - - To set the custom-mirroring-profile-profile attribute: - ▸ provide the argument --custom-mirroring-profile on the command - line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --custom-mirroring-profile-location=CUSTOM_MIRRORING_PROFILE_LOCATION - Location of the Security Profile. NOTE: Only global security profiles - are supported. - - To set the custom-mirroring-profile-location attribute: - ▸ provide the argument --custom-mirroring-profile on the command - line with a fully specified name; - ▸ provide the argument --custom-mirroring-profile-location on the - command line; - ▸ provide the argument --location on the command line; - ▸ provide the argument - networksecurity.organizations.locations.securityProfileGroups on - the command line with a fully specified name. - - --custom-mirroring-profile-organization=CUSTOM_MIRRORING_PROFILE_ORGANIZATION - Organization ID of the Security Profile. - - To set the custom-mirroring-profile-organization attribute: - ▸ provide the argument --custom-mirroring-profile on the command - line with a fully specified name; - ▸ provide the argument --custom-mirroring-profile-organization on - the command line; - ▸ provide the argument --organization on the command line; - ▸ provide the argument - networksecurity.organizations.locations.securityProfileGroups on - the command line with a fully specified name. - - Security Profile resource - Path to Security Profile resource. The - arguments in this group can be used to specify the attributes of this - resource. - - --threat-prevention-profile=THREAT_PREVENTION_PROFILE - ID of the Security Profile or fully qualified identifier for the - Security Profile. - - To set the threat-prevention-profile-profile attribute: - ▸ provide the argument --threat-prevention-profile on the command - line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --threat-prevention-profile-location=THREAT_PREVENTION_PROFILE_LOCATION - Location of the Security Profile. NOTE: Only global security profiles - are supported. - - To set the threat-prevention-profile-location attribute: - ▸ provide the argument --threat-prevention-profile on the command - line with a fully specified name; - ▸ provide the argument --threat-prevention-profile-location on the - command line; - ▸ provide the argument --security-profile-location on the command - line; - ▸ provide the argument --location on the command line; - ▸ provide the argument - networksecurity.organizations.locations.securityProfileGroups on - the command line with a fully specified name. - - --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION - Organization ID of the Security Profile. - - To set the threat-prevention-profile-organization attribute: - ▸ provide the argument --threat-prevention-profile on the command - line with a fully specified name; - ▸ provide the argument --threat-prevention-profile-organization on - the command line; - ▸ provide the argument --security-profile-organization on the - command line; - ▸ provide the argument --organization on the command line; - ▸ provide the argument - networksecurity.organizations.locations.securityProfileGroups on - the command line with a fully specified name. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/network-security/security-profile-groups/update b/gcloud/network-security/security-profile-groups/update index 4aad4ae37..35548d83a 100644 --- a/gcloud/network-security/security-profile-groups/update +++ b/gcloud/network-security/security-profile-groups/update @@ -105,7 +105,7 @@ FLAGS ID of the Security Profile or fully qualified identifier for the Security Profile. - To set the threat-prevention-profile-profile attribute: + To set the name attribute: ▸ provide the argument --threat-prevention-profile on the command line. @@ -116,7 +116,7 @@ FLAGS Location of the Security Profile. NOTE: Only global security profiles are supported. - To set the threat-prevention-profile-location attribute: + To set the location attribute: ▸ provide the argument --threat-prevention-profile on the command line with a fully specified name; ▸ provide the argument --threat-prevention-profile-location on the @@ -131,7 +131,7 @@ FLAGS --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION Organization ID of the Security Profile. - To set the threat-prevention-profile-organization attribute: + To set the organization attribute: ▸ provide the argument --threat-prevention-profile on the command line with a fully specified name; ▸ provide the argument --threat-prevention-profile-organization on diff --git a/gcloud/network-security/security-profiles/custom-intercept/create b/gcloud/network-security/security-profiles/custom-intercept/create new file mode 100644 index 000000000..1c3073d3c --- /dev/null +++ b/gcloud/network-security/security-profiles/custom-intercept/create @@ -0,0 +1,127 @@ +NAME + gcloud network-security security-profiles custom-intercept create - create + a new Custom Intercept Profile + +SYNOPSIS + gcloud network-security security-profiles custom-intercept create + (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) + (--intercept-endpoint-group=INTERCEPT_ENDPOINT_GROUP + : --intercept-endpoint-group-location=INTERCEPT_ENDPOINT_GROUP_LOCATION) + [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new Custom Intercept Security Profile. + +EXAMPLES + To create a Custom Intercept Security Profile named intercept-profile + linked to a Intercept Endpoint Group (q.v.), run: + + $ gcloud network-security security-profiles custom-intercept \ + create intercept-profile --description="An Intercept Profile" \ + --intercept-endpoint-group=projects/my-project/locations/\ + global/interceptEndpointGroups/my-mep + +POSITIONAL ARGUMENTS + Security profile resource - Security Profile Name. The arguments in this + group can be used to specify the attributes of this resource. + + This must be specified. + + SECURITY_PROFILE + ID of the security_profile or fully qualified identifier for the + security_profile. + + To set the security_profile attribute: + ▸ provide the argument security_profile 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 security_profile - Global. + + To set the location attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + Organization ID to which the changes should apply. + + To set the organization attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. + +REQUIRED FLAGS + Intercept endpoint group resource - Intercept Endpoint Group. 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 --intercept-endpoint-group 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. + + --intercept-endpoint-group=INTERCEPT_ENDPOINT_GROUP + ID of the intercept endpoint group or fully qualified identifier for + the intercept endpoint group. + + To set the id attribute: + ▸ provide the argument --intercept-endpoint-group on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --intercept-endpoint-group-location=INTERCEPT_ENDPOINT_GROUP_LOCATION + Location of the intercept endpoint group. + + To set the location attribute: + ▸ provide the argument --intercept-endpoint-group on the command + line with a fully specified name; + ▸ provide the argument --intercept-endpoint-group-location on the + command line; + ▸ provide the argument --location on the command line; + ▸ provide the argument + networksecurity.projects.locations.interceptEndpointGroupAssociations + on the command line with a fully specified name. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is False. + + --description=DESCRIPTION + Brief description of the security profile + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha network-security security-profiles custom-intercept \ + create + + $ gcloud beta network-security security-profiles custom-intercept \ + create + diff --git a/gcloud/network-security/security-profiles/custom-intercept/delete b/gcloud/network-security/security-profiles/custom-intercept/delete new file mode 100644 index 000000000..8b4e79f8d --- /dev/null +++ b/gcloud/network-security/security-profiles/custom-intercept/delete @@ -0,0 +1,78 @@ +NAME + gcloud network-security security-profiles custom-intercept delete - delete + a Security Profile + +SYNOPSIS + gcloud network-security security-profiles custom-intercept delete + (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete the specified Security Profile. + +EXAMPLES + To delete a Security Profile called my-security-profile run: + + $ gcloud network-security security-profiles custom-intercept \ + delete my-security-profile + +POSITIONAL ARGUMENTS + Security profile resource - Name of the Security Profile you want to + delete. The arguments in this group can be used to specify the attributes + of this resource. + + This must be specified. + + SECURITY_PROFILE + ID of the security_profile or fully qualified identifier for the + security_profile. + + To set the security_profile attribute: + ▸ provide the argument security_profile on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ use default global location . + + --organization=ORGANIZATION + Organization number. + + To set the organization attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --organization 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/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-security security-profiles custom-intercept \ + delete + + $ gcloud beta network-security security-profiles custom-intercept \ + delete + diff --git a/gcloud/network-security/security-profiles/custom-intercept/describe b/gcloud/network-security/security-profiles/custom-intercept/describe new file mode 100644 index 000000000..09eda503f --- /dev/null +++ b/gcloud/network-security/security-profiles/custom-intercept/describe @@ -0,0 +1,73 @@ +NAME + gcloud network-security security-profiles custom-intercept describe - + describe a Custom InterceptSecurity Profile + +SYNOPSIS + gcloud network-security security-profiles custom-intercept describe + (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details of the Security Profile. + +EXAMPLES + To show details of a Security Profile named my-intercept-sp run: + + $ gcloud network-security security-profiles custom-intercept \ + describe my-intercept-sp --organization=1234 --location=global + +POSITIONAL ARGUMENTS + Security profile resource - Name of the Security Profile to be described. + The arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + SECURITY_PROFILE + ID of the security_profile or fully qualified identifier for the + security_profile. + + To set the security_profile attribute: + ▸ provide the argument security_profile on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ use default global location . + + --organization=ORGANIZATION + Organization number. + + To set the organization attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --organization 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/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-security security-profiles custom-intercept \ + describe + + $ gcloud beta network-security security-profiles custom-intercept \ + describe + diff --git a/gcloud/network-security/security-profiles/custom-intercept/help b/gcloud/network-security/security-profiles/custom-intercept/help new file mode 100644 index 000000000..1bad3dd49 --- /dev/null +++ b/gcloud/network-security/security-profiles/custom-intercept/help @@ -0,0 +1,42 @@ +NAME + gcloud network-security security-profiles custom-intercept - manage + Security Profiles - Custom Intercept Profile + +SYNOPSIS + gcloud network-security security-profiles custom-intercept COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This class provides commands for managing Custom Intercept Security + Profile. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a new Custom Intercept Profile. + + delete + Delete a Security Profile. + + describe + Describe a Custom InterceptSecurity Profile. + + list + List Custom Intercept Security Profiles. + + update + Updates a Custom Intercept Profile. + +NOTES + These variants are also available: + + $ gcloud alpha network-security security-profiles custom-intercept + + $ gcloud beta network-security security-profiles custom-intercept + diff --git a/gcloud/network-security/security-profiles/custom-intercept/list b/gcloud/network-security/security-profiles/custom-intercept/list new file mode 100644 index 000000000..2a260eda6 --- /dev/null +++ b/gcloud/network-security/security-profiles/custom-intercept/list @@ -0,0 +1,91 @@ +NAME + gcloud network-security security-profiles custom-intercept list - list + Custom Intercept Security Profiles + +SYNOPSIS + gcloud network-security security-profiles custom-intercept list + [--location=LOCATION : --organization=ORGANIZATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Custom Intercept Security Profiles. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To list Custom Intercept security profiles in an organization, run: + + $ gcloud network-security security-profiles custom-intercept list \ + --organization=12345 --location=global + +FLAGS + Location resource - Parent resource for the list operation. The arguments + in this group can be used to specify the attributes of this resource. + + --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. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --organization=ORGANIZATION + Organization ID of the location. + + 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. + +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 network-security security-profiles custom-intercept \ + list + + $ gcloud beta network-security security-profiles custom-intercept \ + list + diff --git a/gcloud/network-security/security-profiles/custom-intercept/update b/gcloud/network-security/security-profiles/custom-intercept/update new file mode 100644 index 000000000..21785d6b4 --- /dev/null +++ b/gcloud/network-security/security-profiles/custom-intercept/update @@ -0,0 +1,119 @@ +NAME + gcloud network-security security-profiles custom-intercept update - updates + a Custom Intercept Profile + +SYNOPSIS + gcloud network-security security-profiles custom-intercept update + (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) + [--async] [--description=DESCRIPTION] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Custom Intercept Security Profile. + + The supported fields for update are description and labels. + +EXAMPLES + To update the description of a Custom Intercept Security Profile named + intercept-profile, run: + + $ gcloud network-security security-profiles custom-intercept \ + update intercept-profile --description="A new description" \ + --organization=1234567890 --location=global + + To change the labels of a Custom Intercept Security Profile named + intercept-profile, run: + + $ gcloud network-security security-profiles custom-intercept \ + update intercept-profile \ + --update-labels=key1=value1,key2=value2 \ + --delete-labels=key3,key4 --organization=1234567890 \ + --location=glob + +POSITIONAL ARGUMENTS + Security profile resource - Security Profile Name. The arguments in this + group can be used to specify the attributes of this resource. + + This must be specified. + + SECURITY_PROFILE + ID of the security_profile or fully qualified identifier for the + security_profile. + + To set the security_profile attribute: + ▸ provide the argument security_profile 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 security_profile - Global. + + To set the location attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + Organization ID to which the changes should apply. + + To set the organization attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is False. + + --description=DESCRIPTION + Brief description of the security profile + + --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 network-security security-profiles custom-intercept \ + update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud network-security security-profiles custom-intercept \ + 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 + These variants are also available: + + $ gcloud alpha network-security security-profiles custom-intercept \ + update + + $ gcloud beta network-security security-profiles custom-intercept \ + update + diff --git a/gcloud/network-security/security-profiles/help b/gcloud/network-security/security-profiles/help index b1ec96170..07d12b8ff 100644 --- a/gcloud/network-security/security-profiles/help +++ b/gcloud/network-security/security-profiles/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + custom-intercept + Manage Security Profiles - Custom Intercept Profile. + custom-mirroring Manage Security Profiles - Custom Mirroring Profile. diff --git a/gcloud/scc/bqexports/create b/gcloud/scc/bqexports/create index f3f285590..5e4301770 100644 --- a/gcloud/scc/bqexports/create +++ b/gcloud/scc/bqexports/create @@ -78,11 +78,14 @@ OPTIONAL FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. At most one of these can be specified: diff --git a/gcloud/scc/bqexports/delete b/gcloud/scc/bqexports/delete index af6b3cdcf..3f32e99d2 100644 --- a/gcloud/scc/bqexports/delete +++ b/gcloud/scc/bqexports/delete @@ -49,11 +49,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. At most one of these can be specified: diff --git a/gcloud/scc/bqexports/get b/gcloud/scc/bqexports/get index 6136b33df..755cd0616 100644 --- a/gcloud/scc/bqexports/get +++ b/gcloud/scc/bqexports/get @@ -50,11 +50,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. At most one of these can be specified: diff --git a/gcloud/scc/bqexports/list b/gcloud/scc/bqexports/list index 2ac18b72e..f93a087f5 100644 --- a/gcloud/scc/bqexports/list +++ b/gcloud/scc/bqexports/list @@ -57,11 +57,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/scc/bqexports/update b/gcloud/scc/bqexports/update index 2d08abe62..8eba9e525 100644 --- a/gcloud/scc/bqexports/update +++ b/gcloud/scc/bqexports/update @@ -78,11 +78,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --update-mask=UPDATE_MASK Optional: If left unspecified (default), an update-mask is diff --git a/gcloud/scc/findings/bulk-mute b/gcloud/scc/findings/bulk-mute index 3f85f96e1..c64b527f9 100644 --- a/gcloud/scc/findings/bulk-mute +++ b/gcloud/scc/findings/bulk-mute @@ -60,11 +60,14 @@ OPTIONAL FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --mute-state=MUTE_STATE; default="muted" Desired mute state of the finding. MUTE_STATE must be one of: muted, diff --git a/gcloud/scc/findings/create b/gcloud/scc/findings/create index 0bc8c0fef..ae14c8a21 100644 --- a/gcloud/scc/findings/create +++ b/gcloud/scc/findings/create @@ -114,11 +114,14 @@ OPTIONAL FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --source-properties=[KEY=VALUE,...] Source specific properties. These properties are managed by the source diff --git a/gcloud/scc/findings/group b/gcloud/scc/findings/group index 64b12c3b7..bd7a55522 100644 --- a/gcloud/scc/findings/group +++ b/gcloud/scc/findings/group @@ -130,11 +130,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --page-size=PAGE_SIZE Maximum number of results to return in a single response. Default is diff --git a/gcloud/scc/findings/list b/gcloud/scc/findings/list index 9b48d3df8..729107b13 100644 --- a/gcloud/scc/findings/list +++ b/gcloud/scc/findings/list @@ -128,11 +128,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --order-by=ORDER_BY Expression that defines what fields and order to use for sorting. diff --git a/gcloud/scc/findings/list-marks b/gcloud/scc/findings/list-marks index d2ddaa6f1..915b7e70c 100644 --- a/gcloud/scc/findings/list-marks +++ b/gcloud/scc/findings/list-marks @@ -46,11 +46,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --page-token=PAGE_TOKEN Response objects will return a non-null value for page-token to diff --git a/gcloud/scc/findings/set-mute b/gcloud/scc/findings/set-mute index 1727dffd1..d7ee96289 100644 --- a/gcloud/scc/findings/set-mute +++ b/gcloud/scc/findings/set-mute @@ -58,11 +58,14 @@ OPTIONAL FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --source=SOURCE ID of the source. diff --git a/gcloud/scc/findings/update b/gcloud/scc/findings/update index 9ce63335e..ffee149a8 100644 --- a/gcloud/scc/findings/update +++ b/gcloud/scc/findings/update @@ -71,11 +71,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --source=SOURCE; default="-" Source id. Defaults to all sources. diff --git a/gcloud/scc/findings/update-marks b/gcloud/scc/findings/update-marks index b4b1004ba..173396258 100644 --- a/gcloud/scc/findings/update-marks +++ b/gcloud/scc/findings/update-marks @@ -63,11 +63,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --security-marks=[KEY=VALUE,...] SecurityMarks resource to be passed as the request body. It's a diff --git a/gcloud/scc/muteconfigs/create b/gcloud/scc/muteconfigs/create index e19a20c7b..eb00217f4 100644 --- a/gcloud/scc/muteconfigs/create +++ b/gcloud/scc/muteconfigs/create @@ -64,11 +64,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --type=TYPE; default="static" The mute configuration type. Immutable after creation. TYPE must be one diff --git a/gcloud/scc/muteconfigs/delete b/gcloud/scc/muteconfigs/delete index 40ddd2001..369f44fb8 100644 --- a/gcloud/scc/muteconfigs/delete +++ b/gcloud/scc/muteconfigs/delete @@ -41,11 +41,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. At most one of these can be specified: diff --git a/gcloud/scc/muteconfigs/get b/gcloud/scc/muteconfigs/get index af2c14bd7..bf5636a89 100644 --- a/gcloud/scc/muteconfigs/get +++ b/gcloud/scc/muteconfigs/get @@ -39,11 +39,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. At most one of these can be specified: diff --git a/gcloud/scc/muteconfigs/list b/gcloud/scc/muteconfigs/list index 6da6fffe3..83af26502 100644 --- a/gcloud/scc/muteconfigs/list +++ b/gcloud/scc/muteconfigs/list @@ -49,11 +49,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/scc/muteconfigs/update b/gcloud/scc/muteconfigs/update index e2252b174..8b827982f 100644 --- a/gcloud/scc/muteconfigs/update +++ b/gcloud/scc/muteconfigs/update @@ -64,11 +64,14 @@ FLAGS location in which the resource is located and applicable. The location attribute can be provided as part of the fully specified resource name or with the --location argument on the command line. The default - location is global. - - The default location on this command is unrelated to the default - location that is specified when data residency controls are enabled for - Security Command Center. + location is global. NOTE: If you override the endpoint to a regional + endpoint + (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint) + you must specify the correct data location + (https://cloud.google.com/security-command-center/docs/data-residency-support#locations) + using this flag. The default location on this command is unrelated to + the default location that is specified when data residency controls are + enabled for Security Command Center. --update-mask=UPDATE_MASK Optional: If left unspecified (default), an update-mask is diff --git a/gcloud/spanner/instance-partitions/delete b/gcloud/spanner/instance-partitions/delete index 537907ae2..d3995d232 100644 --- a/gcloud/spanner/instance-partitions/delete +++ b/gcloud/spanner/instance-partitions/delete @@ -1,13 +1,15 @@ NAME gcloud spanner instance-partitions delete - delete a Spanner instance - partition + partition. You can't delete the default instance partition using this + command SYNOPSIS gcloud spanner instance-partitions delete (INSTANCE_PARTITION : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Delete a Spanner instance partition. + Delete a Spanner instance partition. You can't delete the default instance + partition using this command. EXAMPLES To delete a Spanner instance partition, run: diff --git a/gcloud/spanner/instance-partitions/describe b/gcloud/spanner/instance-partitions/describe new file mode 100644 index 000000000..7b281d681 --- /dev/null +++ b/gcloud/spanner/instance-partitions/describe @@ -0,0 +1,65 @@ +NAME + gcloud spanner instance-partitions describe - describe a Spanner instance + partition + +SYNOPSIS + gcloud spanner instance-partitions describe + (INSTANCE_PARTITION : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Spanner instance partition. + +EXAMPLES + To describe a Spanner instance partition, run: + + $ gcloud spanner instance-partitions describe \ + my-instance-partition-id --instance=my-instance-id + +POSITIONAL ARGUMENTS + Instance partition resource - The Spanner instance partition 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 instance_partition on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE_PARTITION + ID of the instance partition or fully qualified identifier for the + instance partition. + + To set the instance partition attribute: + ▸ provide the argument instance_partition on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + The Cloud Spanner instance for the instance partition. + + To set the instance attribute: + ▸ provide the argument instance_partition on the command line with + a fully specified name; + ▸ provide the argument --instance on the command line; + ▸ set the property spanner/instance. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 spanner instance-partitions describe + + $ gcloud beta spanner instance-partitions describe + diff --git a/gcloud/spanner/instance-partitions/help b/gcloud/spanner/instance-partitions/help index 21261ca99..461aa636e 100644 --- a/gcloud/spanner/instance-partitions/help +++ b/gcloud/spanner/instance-partitions/help @@ -19,7 +19,19 @@ COMMANDS Create a Spanner instance partition. delete - Delete a Spanner instance partition. + Delete a Spanner instance partition. You can't delete the default + instance partition using this command. + + describe + Describe a Spanner instance partition. + + list + List the Spanner instance partitions contained within the given + instance. + + update + Update a Spanner instance partition. You can't update the default + instance partition using this command. NOTES These variants are also available: diff --git a/gcloud/spanner/instance-partitions/list b/gcloud/spanner/instance-partitions/list new file mode 100644 index 000000000..77f6fc06c --- /dev/null +++ b/gcloud/spanner/instance-partitions/list @@ -0,0 +1,76 @@ +NAME + gcloud spanner instance-partitions list - list the Spanner instance + partitions contained within the given instance + +SYNOPSIS + gcloud spanner instance-partitions list [--instance=INSTANCE] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List the Spanner instance partitions contained within the given instance. + +EXAMPLES + To list all Spanner instances partitions in an instance, run: + + $ gcloud spanner instance-partitions list --instance=my-instance-id + +FLAGS + Instance resource - The Cloud Spanner instance in which to list instance + partitions. 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 --instance on the command line with a fully + specified name; + ◆ set the property spanner/instance with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --instance=INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument --instance on the command line; + ▸ set the property spanner/instance. + +LIST COMMAND FLAGS + --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 spanner instance-partitions list + + $ gcloud beta spanner instance-partitions list + diff --git a/gcloud/spanner/instance-partitions/update b/gcloud/spanner/instance-partitions/update new file mode 100644 index 000000000..af0cc67bd --- /dev/null +++ b/gcloud/spanner/instance-partitions/update @@ -0,0 +1,92 @@ +NAME + gcloud spanner instance-partitions update - update a Spanner instance + partition. You can't update the default instance partition using this + command + +SYNOPSIS + gcloud spanner instance-partitions update + (INSTANCE_PARTITION : --instance=INSTANCE) [--async] + [--description=DESCRIPTION] + [--nodes=NODES | --processing-units=PROCESSING_UNITS] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Spanner instance partition. You can't update the default instance + partition using this command. + +EXAMPLES + To update the display name of a Spanner instance partition, run: + + $ gcloud spanner instance-partitions update \ + my-instance-partition-id --instance=my-instance-id \ + --description=my-new-display-name + + To update the node count of a Spanner instance partition, run: + + $ gcloud spanner instance-partitions update \ + my-instance-partition-id --instance=my-instance-id --nodes=1 + +POSITIONAL ARGUMENTS + Instance partition resource - The Spanner instance partition 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 instance_partition on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE_PARTITION + ID of the instance partition or fully qualified identifier for the + instance partition. + + To set the instance partition attribute: + ▸ provide the argument instance_partition on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + The Cloud Spanner instance for the instance partition. + + To set the instance attribute: + ▸ provide the argument instance_partition on the command line with + a fully specified name; + ▸ provide the argument --instance on the command line; + ▸ set the property spanner/instance. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description of the instance partition. + + At most one of these can be specified: + + --nodes=NODES + Number of nodes for the instance partition. + + --processing-units=PROCESSING_UNITS + Number of processing units for the instance partition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 spanner instance-partitions update + + $ gcloud beta spanner instance-partitions update + diff --git a/gcloud/spanner/instances/move b/gcloud/spanner/instances/move index d5d00631c..8bf847eb5 100644 --- a/gcloud/spanner/instances/move +++ b/gcloud/spanner/instances/move @@ -41,7 +41,7 @@ OPTIONAL FLAGS KMS keys. Sets target_database_move_configs value. database-id - Required, Sets database-id value. + Required, sets database-id value. kms-key-names Sets kms-key-names value. diff --git a/gcloud/spanner/operations/cancel b/gcloud/spanner/operations/cancel index 8fb36704d..daf31ff2e 100644 --- a/gcloud/spanner/operations/cancel +++ b/gcloud/spanner/operations/cancel @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud spanner operations cancel 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 Cancel a Cloud Spanner operation. @@ -25,6 +26,11 @@ EXAMPLES $ gcloud spanner operations cancel _auto_12345 \ --instance=my-instance-id --backup=my-backup-id + To cancel an instance partition operation with ID auto_12345, run: + + $ gcloud spanner operations cancel 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/spanner/operations/list b/gcloud/spanner/operations/list index 0e4ca2690..1d6c4e2af 100644 --- a/gcloud/spanner/operations/list +++ b/gcloud/spanner/operations/list @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud spanner operations list (--instance=INSTANCE | --instance-config=INSTANCE_CONFIG) - [--backup=BACKUP] [--database=DATABASE] [--type=TYPE] + [--backup=BACKUP] [--database=DATABASE] + [--instance-partition=INSTANCE_PARTITION] [--type=TYPE] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -42,6 +43,17 @@ EXAMPLES $ gcloud spanner operations list --instance=my-instance-id \ --backup=my-backup-id --type=BACKUP + To list instance partition operations for an instance partition, run: + + $ gcloud spanner operations list --instance=my-instance-id \ + --instance-partition=my-partition-id --type=INSTANCE_PARTITION + + To list instance partition operations for all instance partitions belonging + to this instance, run: + + $ gcloud spanner operations list --instance=my-instance-id \ + --type=INSTANCE_PARTITION + REQUIRED FLAGS Exactly one of these must be specified: @@ -60,6 +72,10 @@ FLAGS For database operations, the name of the database the operations are executing on. + --instance-partition=INSTANCE_PARTITION + For instance partition operations, the name of the instance partition + the operation is executing on. + --type=TYPE (optional) List only the operations of the given type. TYPE must be one of: @@ -99,6 +115,12 @@ FLAGS INSTANCE_CONFIG_UPDATE Instance configuration update operations are returned for the given instance configuration (--instance-config). + INSTANCE_PARTITION + If only the instance is specified (--instance), returns all + instance partition operations associated with instance partitions + in the instance. When an instance partition is specified + (--instance-partition), only the instance partition operations for + the given instance partition are returned. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index cf5da06ab..3027a9b99 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -394,7 +394,7 @@ FLAGS Sets psc_auto_connections value. network - Required, Sets network value. + Required, sets network value. project Sets project value. diff --git a/gcloud/workstations/clusters/create b/gcloud/workstations/clusters/create index 55028bfc7..de15e6d98 100644 --- a/gcloud/workstations/clusters/create +++ b/gcloud/workstations/clusters/create @@ -5,7 +5,8 @@ SYNOPSIS gcloud workstations clusters create (CLUSTER : --region=REGION) [--async] [--domain=DOMAIN] [--enable-private-endpoint] [--labels=[KEY=VALUE,...]] [--network=NETWORK] - [--subnetwork=SUBNETWORK] [GCLOUD_WIDE_FLAG ...] + [--subnetwork=SUBNETWORK] [--tags=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a workstation cluster. @@ -78,6 +79,10 @@ FLAGS --subnetwork=SUBNETWORK Fully specified subnetwork path for instances created in this cluster. + --tags=[KEY=VALUE,...] + Resource manager tags to be bound to this cluster. For example: + "123/environment=production" "123/costCenter=marketing" + 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/workstations/configs/create b/gcloud/workstations/configs/create index 2f016aa51..7cff4e4ff 100644 --- a/gcloud/workstations/configs/create +++ b/gcloud/workstations/configs/create @@ -117,10 +117,10 @@ FLAGS Sets allowed_ports value. first - Required, Sets first value. + Required, sets first value. last - Required, Sets last value. + Required, sets last value. Shorthand Example: diff --git a/gcloud/workstations/configs/update b/gcloud/workstations/configs/update index bd7e5bd9b..7bb6da46f 100644 --- a/gcloud/workstations/configs/update +++ b/gcloud/workstations/configs/update @@ -107,10 +107,10 @@ FLAGS Sets allowed_ports value. first - Required, Sets first value. + Required, sets first value. last - Required, Sets last value. + Required, sets last value. Shorthand Example: