From 37dd57701a71590d4929de9188f35fd2f626dd27 Mon Sep 17 00:00:00 2001 From: Automated Date: Thu, 29 Feb 2024 10:17:22 +0000 Subject: [PATCH] gcloud: Thu Feb 29 10:17:22 UTC 2024 --- gcloud/_version | 8 +- gcloud/alpha/apphub/applications/create | 35 ++- .../alpha/apphub/applications/services/create | 35 ++- .../alpha/apphub/applications/services/update | 37 ++- gcloud/alpha/apphub/applications/update | 43 ++- .../apphub/applications/workloads/create | 35 ++- .../apphub/applications/workloads/update | 37 ++- gcloud/alpha/apphub/discovered-services/list | 3 +- gcloud/alpha/apphub/discovered-workloads/list | 3 +- .../alpha/audit-manager/operations/describe | 6 +- .../builds/connections/create/bitbucket-cloud | 111 -------- .../connections/create/bitbucket-data-center | 142 ---------- gcloud/alpha/builds/connections/create/help | 6 - .../builds/connections/update/bitbucket-cloud | 106 -------- .../connections/update/bitbucket-data-center | 107 -------- gcloud/alpha/builds/connections/update/help | 6 - .../builds/triggers/create/bitbucket-cloud | 225 --------------- .../triggers/create/bitbucket-data-center | 226 --------------- gcloud/alpha/builds/triggers/create/help | 8 - .../builds/triggers/update/bitbucket-cloud | 255 ----------------- .../triggers/update/bitbucket-data-center | 257 ------------------ gcloud/alpha/builds/triggers/update/help | 6 - gcloud/alpha/compute/disks/create | 2 +- gcloud/alpha/compute/images/import | 5 + .../managed/all-instances-config/delete | 4 +- .../managed/all-instances-config/help | 4 +- .../managed/all-instances-config/update | 4 +- .../compute/instant-snapshots/add-labels | 4 +- gcloud/alpha/compute/instant-snapshots/create | 4 +- gcloud/alpha/compute/instant-snapshots/delete | 4 +- .../alpha/compute/instant-snapshots/describe | 4 +- gcloud/alpha/compute/instant-snapshots/help | 4 +- gcloud/alpha/compute/instant-snapshots/list | 4 +- .../attachments/dedicated/create | 12 +- .../attachments/dedicated/update | 8 +- gcloud/alpha/compute/snapshots/create | 9 +- gcloud/alpha/config/get | 3 + gcloud/alpha/config/help | 3 + gcloud/alpha/config/list | 3 + gcloud/alpha/config/set | 3 + gcloud/alpha/config/unset | 3 + gcloud/alpha/container/clusters/create | 17 +- gcloud/alpha/container/clusters/create-auto | 7 +- gcloud/alpha/container/clusters/update | 7 +- gcloud/alpha/container/node-pools/create | 8 + gcloud/alpha/container/node-pools/delete | 4 +- gcloud/alpha/firestore/operations/help | 3 + gcloud/alpha/firestore/operations/wait | 37 +++ gcloud/alpha/iap/settings/set | 35 +-- .../firewall-endpoint-associations/update | 127 +++++---- gcloud/alpha/scc/findings/bulk-mute | 32 ++- gcloud/alpha/scc/findings/create | 50 +++- gcloud/alpha/scc/findings/group | 25 +- gcloud/alpha/scc/findings/help | 8 +- gcloud/alpha/scc/findings/list | 24 +- gcloud/alpha/scc/findings/list-marks | 42 ++- gcloud/alpha/scc/findings/set-mute | 46 ++-- gcloud/alpha/scc/findings/update | 48 +++- gcloud/alpha/scc/findings/update-marks | 52 ++-- gcloud/alpha/scc/muteconfigs/create | 73 +++-- gcloud/alpha/scc/muteconfigs/delete | 55 ++-- gcloud/alpha/scc/muteconfigs/get | 52 ++-- gcloud/alpha/scc/muteconfigs/help | 10 +- gcloud/alpha/scc/muteconfigs/list | 33 ++- gcloud/alpha/scc/muteconfigs/update | 70 +++-- gcloud/alpha/scc/notifications/create | 48 ++-- gcloud/alpha/scc/notifications/delete | 61 +++-- gcloud/alpha/scc/notifications/describe | 56 ++-- gcloud/alpha/scc/notifications/help | 10 +- gcloud/alpha/scc/notifications/list | 34 ++- gcloud/alpha/scc/notifications/update | 88 +++--- gcloud/alpha/scc/postures/list | 13 +- gcloud/alpha/spanner/backups/copy | 58 ++-- gcloud/alpha/spanner/backups/create | 58 ++-- gcloud/alpha/spanner/databases/create | 58 ++-- gcloud/alpha/spanner/databases/restore | 58 ++-- gcloud/alpha/sql/backups/delete | 17 +- .../builds/connections/create/bitbucket-cloud | 109 -------- .../connections/create/bitbucket-data-center | 140 ---------- gcloud/beta/builds/connections/create/help | 6 - .../builds/connections/update/bitbucket-cloud | 104 ------- .../connections/update/bitbucket-data-center | 105 ------- gcloud/beta/builds/connections/update/help | 6 - .../builds/triggers/create/bitbucket-cloud | 223 --------------- .../triggers/create/bitbucket-data-center | 224 --------------- gcloud/beta/builds/triggers/create/help | 7 - .../builds/triggers/update/bitbucket-cloud | 253 ----------------- .../triggers/update/bitbucket-data-center | 255 ----------------- gcloud/beta/builds/triggers/update/help | 6 - gcloud/beta/compute/disks/create | 2 +- gcloud/beta/compute/images/import | 5 + .../managed/all-instances-config/delete | 6 +- .../managed/all-instances-config/help | 6 +- .../managed/all-instances-config/update | 6 +- .../beta/compute/instant-snapshots/add-labels | 6 +- gcloud/beta/compute/instant-snapshots/create | 6 +- gcloud/beta/compute/instant-snapshots/delete | 6 +- .../beta/compute/instant-snapshots/describe | 6 +- gcloud/beta/compute/instant-snapshots/help | 6 +- gcloud/beta/compute/instant-snapshots/list | 6 +- gcloud/beta/compute/snapshots/create | 9 +- gcloud/beta/config/get | 3 + gcloud/beta/config/help | 3 + gcloud/beta/config/list | 3 + gcloud/beta/config/set | 3 + gcloud/beta/config/unset | 3 + gcloud/beta/container/clusters/create | 17 +- gcloud/beta/container/clusters/create-auto | 7 +- gcloud/beta/container/clusters/update | 7 +- gcloud/beta/container/node-pools/create | 8 + gcloud/beta/container/node-pools/delete | 4 +- gcloud/beta/iap/settings/set | 34 +-- .../firewall-endpoint-associations/update | 6 +- gcloud/beta/scc/findings/create | 50 +++- gcloud/beta/scc/findings/group | 25 +- gcloud/beta/scc/findings/help | 6 +- gcloud/beta/scc/findings/list | 24 +- gcloud/beta/scc/findings/list-marks | 42 ++- gcloud/beta/scc/findings/update | 48 +++- gcloud/beta/scc/findings/update-marks | 52 ++-- gcloud/beta/scc/notifications/create | 48 ++-- gcloud/beta/scc/notifications/delete | 60 ++-- gcloud/beta/scc/notifications/describe | 58 ++-- gcloud/beta/scc/notifications/help | 10 +- gcloud/beta/scc/notifications/list | 34 ++- gcloud/beta/scc/notifications/update | 88 +++--- gcloud/beta/spanner/backups/copy | 58 ++-- gcloud/beta/spanner/backups/create | 58 ++-- gcloud/beta/spanner/databases/create | 58 ++-- gcloud/beta/spanner/databases/restore | 58 ++-- gcloud/beta/sql/backups/delete | 17 +- .../builds/connections/create/bitbucket-cloud | 108 -------- .../connections/create/bitbucket-data-center | 139 ---------- gcloud/builds/connections/create/help | 6 - .../builds/connections/update/bitbucket-cloud | 103 ------- .../connections/update/bitbucket-data-center | 104 ------- gcloud/builds/connections/update/help | 6 - gcloud/builds/triggers/create/bitbucket-cloud | 222 --------------- .../triggers/create/bitbucket-data-center | 222 --------------- gcloud/builds/triggers/create/help | 6 - gcloud/builds/triggers/update/bitbucket-cloud | 251 ----------------- .../triggers/update/bitbucket-data-center | 252 ----------------- gcloud/builds/triggers/update/help | 6 - gcloud/compute/disks/create | 7 +- gcloud/compute/help | 3 + gcloud/compute/images/import | 5 + .../managed/all-instances-config/delete | 86 ++++++ .../managed/all-instances-config/help | 35 +++ .../managed/all-instances-config/update | 88 ++++++ gcloud/compute/instance-groups/managed/create | 12 + gcloud/compute/instance-groups/managed/help | 4 + gcloud/compute/instance-groups/managed/update | 12 + gcloud/compute/instant-snapshots/add-labels | 96 +++++++ gcloud/compute/instant-snapshots/create | 100 +++++++ gcloud/compute/instant-snapshots/delete | 93 +++++++ gcloud/compute/instant-snapshots/describe | 82 ++++++ gcloud/compute/instant-snapshots/help | 43 +++ gcloud/compute/instant-snapshots/list | 113 ++++++++ gcloud/compute/snapshots/create | 33 ++- gcloud/config/get | 3 + gcloud/config/help | 3 + gcloud/config/list | 3 + gcloud/config/set | 3 + gcloud/config/unset | 3 + gcloud/container/clusters/create | 7 +- gcloud/container/clusters/create-auto | 7 +- gcloud/container/clusters/update | 7 +- gcloud/container/node-pools/delete | 4 +- gcloud/iap/settings/set | 19 +- gcloud/infra-manager/previews/export | 4 +- gcloud/scc/bqexports/create | 79 +++--- gcloud/scc/bqexports/delete | 62 +++-- gcloud/scc/bqexports/get | 61 +++-- gcloud/scc/bqexports/help | 10 +- gcloud/scc/bqexports/list | 42 ++- gcloud/scc/bqexports/update | 69 ++--- gcloud/scc/findings/bulk-mute | 31 ++- gcloud/scc/findings/create | 48 +++- gcloud/scc/findings/group | 25 +- gcloud/scc/findings/help | 8 +- gcloud/scc/findings/list | 25 +- gcloud/scc/findings/list-marks | 44 ++- gcloud/scc/findings/set-mute | 48 ++-- gcloud/scc/findings/update | 46 +++- gcloud/scc/findings/update-marks | 52 ++-- gcloud/scc/muteconfigs/create | 69 +++-- gcloud/scc/muteconfigs/delete | 52 ++-- gcloud/scc/muteconfigs/get | 52 ++-- gcloud/scc/muteconfigs/help | 10 +- gcloud/scc/muteconfigs/list | 34 ++- gcloud/scc/muteconfigs/update | 68 +++-- gcloud/scc/notifications/create | 46 ++-- gcloud/scc/notifications/delete | 58 ++-- gcloud/scc/notifications/describe | 57 ++-- gcloud/scc/notifications/help | 10 +- gcloud/scc/notifications/list | 36 ++- gcloud/scc/notifications/update | 102 +++---- gcloud/scc/postures/list | 12 +- gcloud/spanner/backups/copy | 58 ++-- gcloud/spanner/backups/create | 58 ++-- gcloud/spanner/databases/create | 58 ++-- gcloud/spanner/databases/restore | 58 ++-- gcloud/sql/backups/delete | 15 +- 203 files changed, 3473 insertions(+), 5938 deletions(-) delete mode 100644 gcloud/alpha/builds/connections/create/bitbucket-cloud delete mode 100644 gcloud/alpha/builds/connections/create/bitbucket-data-center delete mode 100644 gcloud/alpha/builds/connections/update/bitbucket-cloud delete mode 100644 gcloud/alpha/builds/connections/update/bitbucket-data-center delete mode 100644 gcloud/alpha/builds/triggers/create/bitbucket-cloud delete mode 100644 gcloud/alpha/builds/triggers/create/bitbucket-data-center delete mode 100644 gcloud/alpha/builds/triggers/update/bitbucket-cloud delete mode 100644 gcloud/alpha/builds/triggers/update/bitbucket-data-center create mode 100644 gcloud/alpha/firestore/operations/wait delete mode 100644 gcloud/beta/builds/connections/create/bitbucket-cloud delete mode 100644 gcloud/beta/builds/connections/create/bitbucket-data-center delete mode 100644 gcloud/beta/builds/connections/update/bitbucket-cloud delete mode 100644 gcloud/beta/builds/connections/update/bitbucket-data-center delete mode 100644 gcloud/beta/builds/triggers/create/bitbucket-cloud delete mode 100644 gcloud/beta/builds/triggers/create/bitbucket-data-center delete mode 100644 gcloud/beta/builds/triggers/update/bitbucket-cloud delete mode 100644 gcloud/beta/builds/triggers/update/bitbucket-data-center delete mode 100644 gcloud/builds/connections/create/bitbucket-cloud delete mode 100644 gcloud/builds/connections/create/bitbucket-data-center delete mode 100644 gcloud/builds/connections/update/bitbucket-cloud delete mode 100644 gcloud/builds/connections/update/bitbucket-data-center delete mode 100644 gcloud/builds/triggers/create/bitbucket-cloud delete mode 100644 gcloud/builds/triggers/create/bitbucket-data-center delete mode 100644 gcloud/builds/triggers/update/bitbucket-cloud delete mode 100644 gcloud/builds/triggers/update/bitbucket-data-center create mode 100644 gcloud/compute/instance-groups/managed/all-instances-config/delete create mode 100644 gcloud/compute/instance-groups/managed/all-instances-config/help create mode 100644 gcloud/compute/instance-groups/managed/all-instances-config/update create mode 100644 gcloud/compute/instant-snapshots/add-labels create mode 100644 gcloud/compute/instant-snapshots/create create mode 100644 gcloud/compute/instant-snapshots/delete create mode 100644 gcloud/compute/instant-snapshots/describe create mode 100644 gcloud/compute/instant-snapshots/help create mode 100644 gcloud/compute/instant-snapshots/list diff --git a/gcloud/_version b/gcloud/_version index 12721b15b..25dfb0fe4 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 465.0.0 -alpha 2024.02.16 -beta 2024.02.16 +Google Cloud SDK 466.0.0 +alpha 2024.02.26 +beta 2024.02.26 bq 2.0.101 bundled-python3-unix 3.11.7 -core 2024.02.16 +core 2024.02.26 gcloud-crc32c 1.0.0 gsutil 5.27 diff --git a/gcloud/alpha/apphub/applications/create b/gcloud/alpha/apphub/applications/create index 817b556f1..c33a32e1e 100644 --- a/gcloud/alpha/apphub/applications/create +++ b/gcloud/alpha/apphub/applications/create @@ -6,11 +6,10 @@ SYNOPSIS --scope-type=SCOPE_TYPE [--async] [--business-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] - [--criticality=[level=LEVEL],[mission-critical=MISSION-CRITICAL]] - [--description=DESCRIPTION] + [--criticality-type=CRITICALITY_TYPE] [--description=DESCRIPTION] [--developer-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] - [--display-name=DISPLAY_NAME] [--environment=ENVIRONMENT] + [--display-name=DISPLAY_NAME] [--environment-type=ENVIRONMENT_TYPE] [--operator-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] [GCLOUD_WIDE_FLAG ...] @@ -71,8 +70,19 @@ OPTIONAL FLAGS --business-owners=[channel-uri=CHANNEL-URI],[display-name=DISPLAY-NAME],[email=EMAIL] Business owners of the application - --criticality=[level=LEVEL],[mission-critical=MISSION-CRITICAL] - Criticality of the application + --criticality-type=CRITICALITY_TYPE + Criticality Type of the application. CRITICALITY_TYPE must be one of: + + HIGH + High impact + LOW + Low impact + MEDIUM + Medium impact + MISSION_CRITICAL + Mission critical service, application or workload + TYPE_UNSPECIFIED + Unspecified criticality type --description=DESCRIPTION Description of the Application @@ -83,8 +93,19 @@ OPTIONAL FLAGS --display-name=DISPLAY_NAME Human-friendly display name - --environment=ENVIRONMENT - Environment of the application + --environment-type=ENVIRONMENT_TYPE + Environment Type of the application. ENVIRONMENT_TYPE must be one of: + + DEVELOPMENT + Development environment + PRODUCTION + Production environment + STAGING + Staging environment + TEST + Test environment + TYPE_UNSPECIFIED + Unspecified environment type --operator-owners=[channel-uri=CHANNEL-URI],[display-name=DISPLAY-NAME],[email=EMAIL] Operator owners of the application diff --git a/gcloud/alpha/apphub/applications/services/create b/gcloud/alpha/apphub/applications/services/create index 6c0a87892..017f6ff31 100644 --- a/gcloud/alpha/apphub/applications/services/create +++ b/gcloud/alpha/apphub/applications/services/create @@ -8,11 +8,10 @@ SYNOPSIS --discovered-service=DISCOVERED_SERVICE [--async] [--business-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] - [--criticality=[level=LEVEL],[mission-critical=MISSION-CRITICAL]] - [--description=DESCRIPTION] + [--criticality-type=CRITICALITY_TYPE] [--description=DESCRIPTION] [--developer-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] - [--display-name=DISPLAY_NAME] [--environment=ENVIRONMENT] + [--display-name=DISPLAY_NAME] [--environment-type=ENVIRONMENT_TYPE] [--operator-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] [GCLOUD_WIDE_FLAG ...] @@ -98,8 +97,19 @@ OPTIONAL FLAGS --business-owners=[channel-uri=CHANNEL-URI],[display-name=DISPLAY-NAME],[email=EMAIL] Business owners of the service - --criticality=[level=LEVEL],[mission-critical=MISSION-CRITICAL] - Criticality of the service + --criticality-type=CRITICALITY_TYPE + Criticality Type of the service. CRITICALITY_TYPE must be one of: + + HIGH + High impact + LOW + Low impact + MEDIUM + Medium impact + MISSION_CRITICAL + Mission critical service, application or workload + TYPE_UNSPECIFIED + Unspecified criticality type --description=DESCRIPTION Description of the service @@ -110,8 +120,19 @@ OPTIONAL FLAGS --display-name=DISPLAY_NAME Human-friendly display name - --environment=ENVIRONMENT - Environment of the service + --environment-type=ENVIRONMENT_TYPE + Environment Type of the service. ENVIRONMENT_TYPE must be one of: + + DEVELOPMENT + Development environment + PRODUCTION + Production environment + STAGING + Staging environment + TEST + Test environment + TYPE_UNSPECIFIED + Unspecified environment type --operator-owners=[channel-uri=CHANNEL-URI],[display-name=DISPLAY-NAME],[email=EMAIL] Operator owners of the service diff --git a/gcloud/alpha/apphub/applications/services/update b/gcloud/alpha/apphub/applications/services/update index 4e231041a..f3ecfc4a0 100644 --- a/gcloud/alpha/apphub/applications/services/update +++ b/gcloud/alpha/apphub/applications/services/update @@ -7,11 +7,10 @@ SYNOPSIS (SERVICE : --application=APPLICATION --location=LOCATION) [--async] [--business-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] - [--criticality=[level=LEVEL],[mission-critical=MISSION-CRITICAL]] - [--description=DESCRIPTION] + [--criticality-type=CRITICALITY_TYPE] [--description=DESCRIPTION] [--developer-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] - [--display-name=DISPLAY_NAME] [--environment=ENVIRONMENT] + [--display-name=DISPLAY_NAME] [--environment-type=ENVIRONMENT_TYPE] [--operator-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] [GCLOUD_WIDE_FLAG ...] @@ -23,7 +22,7 @@ EXAMPLES Application my-app in location us-east1, run: $ gcloud alpha apphub applications services update my-service \ - --environment=prod --application=my-app --location=us-east1 + --environment-type=TEST --application=my-app --location=us-east1 POSITIONAL ARGUMENTS Service resource - The Service ID. The arguments in this group can be used @@ -71,8 +70,19 @@ FLAGS --business-owners=[channel-uri=CHANNEL-URI],[display-name=DISPLAY-NAME],[email=EMAIL] Business owners of the service - --criticality=[level=LEVEL],[mission-critical=MISSION-CRITICAL] - Criticality of the service + --criticality-type=CRITICALITY_TYPE + Criticality Type of the service. CRITICALITY_TYPE must be one of: + + HIGH + High impact + LOW + Low impact + MEDIUM + Medium impact + MISSION_CRITICAL + Mission critical service, application or workload + TYPE_UNSPECIFIED + Unspecified criticality type --description=DESCRIPTION Description of the service @@ -83,8 +93,19 @@ FLAGS --display-name=DISPLAY_NAME Human-friendly display name - --environment=ENVIRONMENT - Environment of the service + --environment-type=ENVIRONMENT_TYPE + Environment Type of the service. ENVIRONMENT_TYPE must be one of: + + DEVELOPMENT + Development environment + PRODUCTION + Production environment + STAGING + Staging environment + TEST + Test environment + TYPE_UNSPECIFIED + Unspecified environment type --operator-owners=[channel-uri=CHANNEL-URI],[display-name=DISPLAY-NAME],[email=EMAIL] Operator owners of the service diff --git a/gcloud/alpha/apphub/applications/update b/gcloud/alpha/apphub/applications/update index c98705d3f..088d7db42 100644 --- a/gcloud/alpha/apphub/applications/update +++ b/gcloud/alpha/apphub/applications/update @@ -6,11 +6,10 @@ SYNOPSIS [--async] [--business-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] - [--criticality=[level=LEVEL],[mission-critical=MISSION-CRITICAL]] - [--description=DESCRIPTION] + [--criticality-type=CRITICALITY_TYPE] [--description=DESCRIPTION] [--developer-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] - [--display-name=DISPLAY_NAME] [--environment=ENVIRONMENT] + [--display-name=DISPLAY_NAME] [--environment-type=ENVIRONMENT_TYPE] [--operator-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] [GCLOUD_WIDE_FLAG ...] @@ -22,7 +21,7 @@ EXAMPLES us-east1, run: $ gcloud alpha apphub applications update my-app \ - --location=us-east1 --environment=prod + --location=us-east1 --environment-type=TEST POSITIONAL ARGUMENTS Application resource - The Application ID. The arguments in this group can @@ -61,25 +60,47 @@ FLAGS complete. --business-owners=[channel-uri=CHANNEL-URI],[display-name=DISPLAY-NAME],[email=EMAIL] - Business owners of the Application + Business owners of the application - --criticality=[level=LEVEL],[mission-critical=MISSION-CRITICAL] - Criticality of the Application + --criticality-type=CRITICALITY_TYPE + Criticality Type of the application. CRITICALITY_TYPE must be one of: + + HIGH + High impact + LOW + Low impact + MEDIUM + Medium impact + MISSION_CRITICAL + Mission critical service, application or workload + TYPE_UNSPECIFIED + Unspecified criticality type --description=DESCRIPTION Description of the Application --developer-owners=[channel-uri=CHANNEL-URI],[display-name=DISPLAY-NAME],[email=EMAIL] - Developer owners of the Application + Developer owners of the application --display-name=DISPLAY_NAME Human-friendly display name - --environment=ENVIRONMENT - Environment of the Application + --environment-type=ENVIRONMENT_TYPE + Environment Type of the application. ENVIRONMENT_TYPE must be one of: + + DEVELOPMENT + Development environment + PRODUCTION + Production environment + STAGING + Staging environment + TEST + Test environment + TYPE_UNSPECIFIED + Unspecified environment type --operator-owners=[channel-uri=CHANNEL-URI],[display-name=DISPLAY-NAME],[email=EMAIL] - Operator owners of the Application + Operator owners of the application GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/apphub/applications/workloads/create b/gcloud/alpha/apphub/applications/workloads/create index e5a940eb1..cae81896e 100644 --- a/gcloud/alpha/apphub/applications/workloads/create +++ b/gcloud/alpha/apphub/applications/workloads/create @@ -8,11 +8,10 @@ SYNOPSIS --discovered-workload=DISCOVERED_WORKLOAD [--async] [--business-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] - [--criticality=[level=LEVEL],[mission-critical=MISSION-CRITICAL]] - [--description=DESCRIPTION] + [--criticality-type=CRITICALITY_TYPE] [--description=DESCRIPTION] [--developer-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] - [--display-name=DISPLAY_NAME] [--environment=ENVIRONMENT] + [--display-name=DISPLAY_NAME] [--environment-type=ENVIRONMENT_TYPE] [--operator-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] [GCLOUD_WIDE_FLAG ...] @@ -98,8 +97,19 @@ OPTIONAL FLAGS --business-owners=[channel-uri=CHANNEL-URI],[display-name=DISPLAY-NAME],[email=EMAIL] Business owners of the workload - --criticality=[level=LEVEL],[mission-critical=MISSION-CRITICAL] - Criticality of the workload + --criticality-type=CRITICALITY_TYPE + Criticality Type of the workload. CRITICALITY_TYPE must be one of: + + HIGH + High impact + LOW + Low impact + MEDIUM + Medium impact + MISSION_CRITICAL + Mission critical service, application or workload + TYPE_UNSPECIFIED + Unspecified criticality type --description=DESCRIPTION Description of the Workload @@ -110,8 +120,19 @@ OPTIONAL FLAGS --display-name=DISPLAY_NAME Human-friendly display name - --environment=ENVIRONMENT - Environment of the workload + --environment-type=ENVIRONMENT_TYPE + Environment Type of the workload. ENVIRONMENT_TYPE must be one of: + + DEVELOPMENT + Development environment + PRODUCTION + Production environment + STAGING + Staging environment + TEST + Test environment + TYPE_UNSPECIFIED + Unspecified environment type --operator-owners=[channel-uri=CHANNEL-URI],[display-name=DISPLAY-NAME],[email=EMAIL] Operator owners of the workload diff --git a/gcloud/alpha/apphub/applications/workloads/update b/gcloud/alpha/apphub/applications/workloads/update index 68f5bce23..7917b6c87 100644 --- a/gcloud/alpha/apphub/applications/workloads/update +++ b/gcloud/alpha/apphub/applications/workloads/update @@ -7,11 +7,10 @@ SYNOPSIS (WORKLOAD : --application=APPLICATION --location=LOCATION) [--async] [--business-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] - [--criticality=[level=LEVEL],[mission-critical=MISSION-CRITICAL]] - [--description=DESCRIPTION] + [--criticality-type=CRITICALITY_TYPE] [--description=DESCRIPTION] [--developer-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] - [--display-name=DISPLAY_NAME] [--environment=ENVIRONMENT] + [--display-name=DISPLAY_NAME] [--environment-type=ENVIRONMENT_TYPE] [--operator-owners=[channel-uri=CHANNEL-URI], [display-name=DISPLAY-NAME],[email=EMAIL]] [GCLOUD_WIDE_FLAG ...] @@ -23,7 +22,7 @@ EXAMPLES Application my-app in location us-east1, run: $ gcloud alpha apphub applications workloads update my-workload \ - --environment=prod --application=my-app --location=us-east1 + --environment-type=TEST --application=my-app --location=us-east1 POSITIONAL ARGUMENTS Workload resource - The Workload ID. The arguments in this group can be @@ -71,8 +70,19 @@ FLAGS --business-owners=[channel-uri=CHANNEL-URI],[display-name=DISPLAY-NAME],[email=EMAIL] Business owners of the workload - --criticality=[level=LEVEL],[mission-critical=MISSION-CRITICAL] - Criticality of the workload + --criticality-type=CRITICALITY_TYPE + Criticality Type of the workload. CRITICALITY_TYPE must be one of: + + HIGH + High impact + LOW + Low impact + MEDIUM + Medium impact + MISSION_CRITICAL + Mission critical service, application or workload + TYPE_UNSPECIFIED + Unspecified criticality type --description=DESCRIPTION Description of the Workload @@ -83,8 +93,19 @@ FLAGS --display-name=DISPLAY_NAME Human-friendly display name - --environment=ENVIRONMENT - Environment of the workload + --environment-type=ENVIRONMENT_TYPE + Environment Type of the workload. ENVIRONMENT_TYPE must be one of: + + DEVELOPMENT + Development environment + PRODUCTION + Production environment + STAGING + Staging environment + TEST + Test environment + TYPE_UNSPECIFIED + Unspecified environment type --operator-owners=[channel-uri=CHANNEL-URI],[display-name=DISPLAY-NAME],[email=EMAIL] Operator owners of the workload diff --git a/gcloud/alpha/apphub/discovered-services/list b/gcloud/alpha/apphub/discovered-services/list index b6265f3bb..07bd776c4 100644 --- a/gcloud/alpha/apphub/discovered-services/list +++ b/gcloud/alpha/apphub/discovered-services/list @@ -11,7 +11,8 @@ DESCRIPTION (ALPHA) List Apphub discovered services. EXAMPLES - To list all DiscoveredServices in location us-east1, run: + To list DiscoveredServices that could be added to an application in + location us-east1, run: $ gcloud alpha apphub discovered-services list --location=us-east1 diff --git a/gcloud/alpha/apphub/discovered-workloads/list b/gcloud/alpha/apphub/discovered-workloads/list index 18a4c985e..1f30163b6 100644 --- a/gcloud/alpha/apphub/discovered-workloads/list +++ b/gcloud/alpha/apphub/discovered-workloads/list @@ -11,7 +11,8 @@ DESCRIPTION (ALPHA) List Apphub discovered workloads. EXAMPLES - To list all DiscoveredWorkloads in location us-east1, run: + To list DiscoveredWorkloads that could be added to an application in + location us-east1, run: $ gcloud alpha apphub discovered-workloads list --location=us-east1 diff --git a/gcloud/alpha/audit-manager/operations/describe b/gcloud/alpha/audit-manager/operations/describe index 62336b95a..ab934adff 100644 --- a/gcloud/alpha/audit-manager/operations/describe +++ b/gcloud/alpha/audit-manager/operations/describe @@ -26,8 +26,8 @@ POSITIONAL ARGUMENTS specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. This resource can be one of the - following types: [auditmanager.folders.locations.operationIds, - auditmanager.projects.locations.operationIds]. + following types: [auditmanager.folders.locations.operationDetails, + auditmanager.projects.locations.operationDetails]. This must be specified. @@ -48,7 +48,7 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --folder on the command line. Must be specified for resource of type - [auditmanager.folders.locations.operationIds]. + [auditmanager.folders.locations.operationDetails]. --location=LOCATION The location for the operation. diff --git a/gcloud/alpha/builds/connections/create/bitbucket-cloud b/gcloud/alpha/builds/connections/create/bitbucket-cloud deleted file mode 100644 index 85f9d1a1c..000000000 --- a/gcloud/alpha/builds/connections/create/bitbucket-cloud +++ /dev/null @@ -1,111 +0,0 @@ -NAME - gcloud alpha builds connections create bitbucket-cloud - create a Cloud - Build Connection for Bitbucket Cloud - -SYNOPSIS - gcloud alpha builds connections create bitbucket-cloud - (CONNECTION : --region=REGION) - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION - --workspace=WORKSPACE [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a Cloud Build Connection for Bitbucket Cloud. - - A Bitbucket Cloud Connection can be created by using a - repository/project/workspace access token with - repository_read,repository_admin, pullrequest_read, webhook scope - permission and a repository/project/workspace access token with - repository_read scope permission. - -EXAMPLES - To create a Bitbucket Cloud connection, provide all the required - parameters: - - $ gcloud alpha builds connections create bitbucket-cloud \ - my-bitbucket-conn --project=myproj --region=us-central1 \ - --workspace=my-workspace \ - --read-authorizer-token-secret-version=projects/myproj/secrets/\ - read-pat/versions/1 \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 \ - --webhook-secret-secret-version=projects/myproj/secrets/\ - whsecret/versions/1 - -POSITIONAL ARGUMENTS - Connection resource - Connection 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 connection on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CONNECTION - ID of the connection or fully qualified identifier for the - connection. - - To set the connection attribute: - ▸ provide the argument connection on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The Google Cloud region. - - To set the region attribute: - ▸ provide the argument connection on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -REQUIRED FLAGS - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the repository_read,repository_admin, - pullrequest_read, webhook repository/project/workspace access token. - - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the repository_read repository/project/workspace - access token. - - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION - Secret containing the webhook secret string for validating webhook - events sent by Bitbucket Cloud. - - --workspace=WORKSPACE - Workspace of the Bitbucket Cloud instance. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the cloudbuild/v2 API. The full documentation for this - API can be found at: https://cloud.google.com/cloud-build/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. These variants are also available: - - $ gcloud builds connections create bitbucket-cloud - - $ gcloud beta builds connections create bitbucket-cloud - diff --git a/gcloud/alpha/builds/connections/create/bitbucket-data-center b/gcloud/alpha/builds/connections/create/bitbucket-data-center deleted file mode 100644 index 206917e69..000000000 --- a/gcloud/alpha/builds/connections/create/bitbucket-data-center +++ /dev/null @@ -1,142 +0,0 @@ -NAME - gcloud alpha builds connections create bitbucket-data-center - create a - Cloud Build Connection for Bitbucket Data Center - -SYNOPSIS - gcloud alpha builds connections create bitbucket-data-center - (CONNECTION : --region=REGION) - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION [--async] - [--host-uri=HOST_URI] - [--service-directory-service=SERVICE_DIRECTORY_SERVICE - : --ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a Cloud Build Connection for Bitbucket Data Center. - - A Bitbucket Data Center Connection can be created by using a personal - access token with REPO_ADMIN scope permission. A REPO_READ scoped personal - access token will also be required. - - If the Bitbucket Data Center can only be accessed within a VPC, a Service - Directory service resource can be provided for connecting to it. - -EXAMPLES - To create a Bitbucket Data Center connection, provide all the required - parameters: - - $ gcloud alpha builds connections create bitbucket-data-center \ - my-bitbucket-conn --project=myproj --region=us-central1 \ - --host-uri=https://bitbucket-server.net \ - --read-authorizer-token-secret-version=projects/myproj/secrets/\ - read-pat/versions/1 \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 \ - --webhook-secret-secret-version=projects/myproj/secrets/\ - whsecret/versions/1 - - To create a Bitbucket Data Center connection for a private Bitbucket Data - Center server. Provide the service-directory-service and ssl-ca-file as - well: - - $ gcloud alpha builds connections create bitbucket-data-center \ - my-private-bitbucket-conn \ - --host-uri=https://my.private-bitbucket-server.net \ - --project=myproj --region=us-central1 \ - --service-directory-service=projects/myproj/namespaces/x/\ - services/mysds --ssl-ca-file=mycertificate.crt \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 \ - --read-authorizer-token-secret-version=projects/myproj/secrets/\ - read-pat/versions/1 \ - --webhook-secret-secret-version=projects/myproj/secrets/\ - whsecret/versions/1 - -POSITIONAL ARGUMENTS - Connection resource - Connection 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 connection on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CONNECTION - ID of the connection or fully qualified identifier for the - connection. - - To set the connection attribute: - ▸ provide the argument connection on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The Google Cloud region. - - To set the region attribute: - ▸ provide the argument connection on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -REQUIRED FLAGS - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the REPO_ADMIN personal access token. - - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the REPO_READ personal access token. - - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION - Secret containing the webhook secret string for validating webhook - events sent by Bitbucket Data Center. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --host-uri=HOST_URI - URI of the Bitbucket Data Center instance. - - Group of arguments for configuring access through Service Directory. - - --service-directory-service=SERVICE_DIRECTORY_SERVICE - Service Directory service resource to use for accessing the Bitbucket - Data Center. Necessary only if the server has no public access from - the internet. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --ssl-ca-file=SSL_CA_FILE - File containing the SSL_CA to be used. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 cloudbuild/v2 API. The full documentation for this - API can be found at: https://cloud.google.com/cloud-build/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. These variants are also available: - - $ gcloud builds connections create bitbucket-data-center - - $ gcloud beta builds connections create bitbucket-data-center - diff --git a/gcloud/alpha/builds/connections/create/help b/gcloud/alpha/builds/connections/create/help index f7a765aa7..c5827bdbc 100644 --- a/gcloud/alpha/builds/connections/create/help +++ b/gcloud/alpha/builds/connections/create/help @@ -16,12 +16,6 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - bitbucket-cloud - (ALPHA) Create a Cloud Build Connection for Bitbucket Cloud. - - bitbucket-data-center - (ALPHA) Create a Cloud Build Connection for Bitbucket Data Center. - github (ALPHA) Create a Cloud Build Connection of type GitHub. diff --git a/gcloud/alpha/builds/connections/update/bitbucket-cloud b/gcloud/alpha/builds/connections/update/bitbucket-cloud deleted file mode 100644 index 53493e57a..000000000 --- a/gcloud/alpha/builds/connections/update/bitbucket-cloud +++ /dev/null @@ -1,106 +0,0 @@ -NAME - gcloud alpha builds connections update bitbucket-cloud - update a Cloud - Build Connection of type Bitbucket Cloud - -SYNOPSIS - gcloud alpha builds connections update bitbucket-cloud - (CONNECTION : --region=REGION) [--async] - [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] - [--read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION] - [--webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION] - [--workspace=WORKSPACE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Update a Cloud Build Connection of type Bitbucket Cloud. - -EXAMPLES - To update the workspace, provide the connection name and the workspace - name: - - $ gcloud alpha builds connections update bitbucket-cloud \ - my-bbc-conn --region=us-west1 --workspace=my-workspace - - To update the authorization token, provide the connection name and the new - authorization token secret version. - - $ gcloud alpha builds connections update bitbucket-cloud \ - my-bbc-conn --region=us-west1 \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 - -POSITIONAL ARGUMENTS - Connection resource - Connection 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 connection on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CONNECTION - ID of the connection or fully qualified identifier for the - connection. - - To set the connection attribute: - ▸ provide the argument connection on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The Google Cloud region. - - To set the region attribute: - ▸ provide the argument connection on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the repository_read,repository_admin, - pullrequest_read, webhook access token. It can be a repository, project - or workspace access token. - - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the repository_read access token. It can be a - repository, project or workspace access token. - - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION - Secret containing the webhook secret string for validating webhook - events sent by Bitbucket Cloud. - - --workspace=WORKSPACE - Workspace of the Bitbucket Cloud 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. - -API REFERENCE - This command uses the cloudbuild/v2 API. The full documentation for this - API can be found at: https://cloud.google.com/cloud-build/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. These variants are also available: - - $ gcloud builds connections update bitbucket-cloud - - $ gcloud beta builds connections update bitbucket-cloud - diff --git a/gcloud/alpha/builds/connections/update/bitbucket-data-center b/gcloud/alpha/builds/connections/update/bitbucket-data-center deleted file mode 100644 index e6290af47..000000000 --- a/gcloud/alpha/builds/connections/update/bitbucket-data-center +++ /dev/null @@ -1,107 +0,0 @@ -NAME - gcloud alpha builds connections update bitbucket-data-center - update a - Cloud Build Connection of type Bitbucket Data Center - -SYNOPSIS - gcloud alpha builds connections update bitbucket-data-center - (CONNECTION : --region=REGION) [--async] - [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] - [--host-uri=HOST_URI] - [--read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION] - [--service-directory-service=SERVICE_DIRECTORY_SERVICE] - [--ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Update a Cloud Build Connection of type Bitbucket Data Center. - -EXAMPLES - To update the ssl_ca, provide the connection name and the ssl_ca file: - - $ gcloud alpha builds connections update bitbucket-data-center \ - my-gle-conn --region=us-west1 --ssl-ca-file=mycertificate.crt - - To update the authorization token, provide the connection name and the new - authorization token secret version name. - - $ gcloud alpha builds connections update bitbucket-data-center \ - my-gle-conn --region=us-west1 \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 - -POSITIONAL ARGUMENTS - Connection resource - Connection 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 connection on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CONNECTION - ID of the connection or fully qualified identifier for the - connection. - - To set the connection attribute: - ▸ provide the argument connection on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The Google Cloud region. - - To set the region attribute: - ▸ provide the argument connection on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the REPO_ADMIN personal access token. - - --host-uri=HOST_URI - URI of the Bitbucket Data Center instance. - - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the REPO_READ personal access token. - - --service-directory-service=SERVICE_DIRECTORY_SERVICE - Service Directory service resource to use for accessing the Bitbucket - Data Center. Necessary only if the server has no public access from the - internet. - - --ssl-ca-file=SSL_CA_FILE - File containing the SSL_CA to be used. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 cloudbuild/v2 API. The full documentation for this - API can be found at: https://cloud.google.com/cloud-build/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. These variants are also available: - - $ gcloud builds connections update bitbucket-data-center - - $ gcloud beta builds connections update bitbucket-data-center - diff --git a/gcloud/alpha/builds/connections/update/help b/gcloud/alpha/builds/connections/update/help index 11dce4625..e9d72fc2f 100644 --- a/gcloud/alpha/builds/connections/update/help +++ b/gcloud/alpha/builds/connections/update/help @@ -16,12 +16,6 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - bitbucket-cloud - (ALPHA) Update a Cloud Build Connection of type Bitbucket Cloud. - - bitbucket-data-center - (ALPHA) Update a Cloud Build Connection of type Bitbucket Data Center. - github (ALPHA) Update a Cloud Build Connection of type GitHub. diff --git a/gcloud/alpha/builds/triggers/create/bitbucket-cloud b/gcloud/alpha/builds/triggers/create/bitbucket-cloud deleted file mode 100644 index 39e926bcf..000000000 --- a/gcloud/alpha/builds/triggers/create/bitbucket-cloud +++ /dev/null @@ -1,225 +0,0 @@ -NAME - gcloud alpha builds triggers create bitbucket-cloud - create a build - trigger for a 2nd-gen Bitbucket Cloud repository - -SYNOPSIS - gcloud alpha builds triggers create bitbucket-cloud - (--trigger-config=PATH | [(--branch-pattern=REGEX | --tag-pattern=REGEX - | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; - default="COMMENTS_ENABLED"]) (--build-config=PATH - | --inline-config=PATH - | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE - : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) - : --description=DESCRIPTION --ignored-files=[GLOB,...] - --included-files=[GLOB,...] --name=NAME --region=REGION - --repository=REPOSITORY --[no-]require-approval - --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a build trigger for a 2nd-gen Bitbucket Cloud repository. - -EXAMPLES - To create a push trigger with a 2nd-gen repository for all branches: - - $ gcloud alpha builds triggers create bitbucket-cloud \ - --name="my-trigger" \ - --service-account="projects/my-project/serviceAccounts/my-byosa@\ - my-project.iam.gserviceaccount.com" \ - --repository="projects/1234/locations/us-central1/connections/my\ - conn/repositories/myrepo" --branch-pattern=".*" \ - --build-config="cloudbuild.yaml" --region=us-central1 - - To create a pull request trigger with a 2nd-gen repository for main: - - $ gcloud alpha builds triggers create bitbucket-cloud \ - --name="my-trigger" \ - --service-account="projects/my-project/serviceAccounts/my-byosa@\ - my-project.iam.gserviceaccount.com" \ - --repository="projects/1234/locations/us-central1/connections/my\ - conn/repositories/myrepo" --build-config="cloudbuild.yaml" \ - --pull-request-pattern="^main$" --region=us-central1 - -REQUIRED FLAGS - Exactly one of these must be specified: - - --trigger-config=PATH - Path to Build Trigger config file (JSON or YAML format). For more - details, see - https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger - - Flag based trigger configuration - - --description=DESCRIPTION - Build trigger description. - - --ignored-files=[GLOB,...] - Glob filter. Changes only affecting ignored files won't trigger - builds. - - --included-files=[GLOB,...] - Glob filter. Changes affecting at least one included file will - trigger builds. - - --name=NAME - Build trigger name. - - --region=REGION - The region of the Cloud Build Service to use. Must be set to a - supported region name (e.g. us-central1). If unset, builds/region, - which is the default region to use when working with Cloud Build - resources, is used. If builds/region is unset, region is set to - global. Note: Region must be specified in 2nd gen repo; global is - not supported. - - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - - --[no-]require-approval - Require manual approval for triggered builds. Use - --require-approval to enable and --no-require-approval to disable. - - --service-account=SERVICE_ACCOUNT - The service account used for all user-controlled operations - including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and - CancelBuild. If no service account is set, then the standard Cloud - Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is - used instead. Format: - projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - - --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. For - example: - - $ gcloud alpha builds triggers create bitbucket-cloud ... \ - --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 - - This will result in a build where every occurrence of - ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and - similarly for ${_NUM_CANDIES} and "10". - - Substitutions can be applied to user-defined variables (starting - with an underscore) and to the following built-in variables: - REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, - SHORT_SHA. - - For more details, see: - https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values - - Exactly one of these must be specified: - - --branch-pattern=REGEX - A regular expression specifying which git branches to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --branch-pattern=foo will match - "foo", "foobar", and "barfoo". Events on a branch that does not - match will be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - --tag-pattern=REGEX - A regular expression specifying which git tags to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --tag-pattern=foo will match "foo", - "foobar", and "barfoo". Events on a tag that does not match will - be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - Pull Request settings - - --pull-request-pattern=REGEX - Regular expression specifying which base git branch to match - for pull request events. - - This pattern is used as a regex search for the base branch (the - branch you are trying to merge into) for pull request updates. - For example, --pull-request-pattern=foo will match "foo", - "foobar", and "barfoo". - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" - Require a repository collaborator or owner to comment '/gcbrun' - on a pull request before running the build. COMMENT_CONTROL - must be one of: - - COMMENTS_DISABLED - Do not require comments on Pull Requests before builds are - triggered. - COMMENTS_ENABLED - Enforce that repository owners or collaborators must - comment on Pull Requests before builds are triggered. - COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY - Enforce that repository owners or collaborators must - comment on external contributors' Pull Requests before - builds are triggered. - - Exactly one of these must be specified: - - --build-config=PATH - Path to a YAML or JSON file containing the build configuration in - the repository. - - For more details, see: - https://cloud.google.com/cloud-build/docs/build-config - - --inline-config=PATH - Local path to a YAML or JSON file containing a build - configuration. - - Dockerfile build configuration flags - - --dockerfile=DOCKERFILE - Path of Dockerfile to use for builds in the repository. - - If specified, a build config will be generated to run docker - build using the specified file. - - The filename is relative to the Dockerfile directory. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-image=DOCKERFILE_IMAGE - Docker image name to build. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-dir=DOCKERFILE_DIR; default="/" - Location of the directory containing the Dockerfile in the - repository. - - The directory will also be used as the Docker build context. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud builds triggers create bitbucket-cloud - - $ gcloud beta builds triggers create bitbucket-cloud - diff --git a/gcloud/alpha/builds/triggers/create/bitbucket-data-center b/gcloud/alpha/builds/triggers/create/bitbucket-data-center deleted file mode 100644 index c9893eebc..000000000 --- a/gcloud/alpha/builds/triggers/create/bitbucket-data-center +++ /dev/null @@ -1,226 +0,0 @@ -NAME - gcloud alpha builds triggers create bitbucket-data-center - create a build - trigger for a 2nd-gen Bitbucket Data Center repository - -SYNOPSIS - gcloud alpha builds triggers create bitbucket-data-center - (--trigger-config=PATH | [(--branch-pattern=REGEX | --tag-pattern=REGEX - | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; - default="COMMENTS_ENABLED"]) (--build-config=PATH - | --inline-config=PATH - | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE - : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) - : --description=DESCRIPTION --ignored-files=[GLOB,...] - --included-files=[GLOB,...] --name=NAME --region=REGION - --repository=REPOSITORY --[no-]require-approval - --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a build trigger for a 2nd-gen Bitbucket Data Center - repository. - -EXAMPLES - To create a push trigger with a 2nd-gen repository for all branches: - - $ gcloud alpha builds triggers create bitbucket-data-center \ - --name="my-trigger" \ - --service-account="projects/my-project/serviceAccounts/my-byosa@\ - my-project.iam.gserviceaccount.com" \ - --repository="projects/1234/locations/us-central1/connections/my\ - conn/repositories/myrepo" --branch-pattern=".*" \ - --build-config="cloudbuild.yaml" --region=us-central1 - - To create a pull request trigger with a 2nd-gen repository for main: - - $ gcloud alpha builds triggers create bitbucket-data-center \ - --name="my-trigger" \ - --service-account="projects/my-project/serviceAccounts/my-byosa@\ - my-project.iam.gserviceaccount.com" \ - --repository="projects/1234/locations/us-central1/connections/my\ - conn/repositories/myrepo" --build-config="cloudbuild.yaml" \ - --pull-request-pattern="^main$" --region=us-central1 - -REQUIRED FLAGS - Exactly one of these must be specified: - - --trigger-config=PATH - Path to Build Trigger config file (JSON or YAML format). For more - details, see - https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger - - Flag based trigger configuration - - --description=DESCRIPTION - Build trigger description. - - --ignored-files=[GLOB,...] - Glob filter. Changes only affecting ignored files won't trigger - builds. - - --included-files=[GLOB,...] - Glob filter. Changes affecting at least one included file will - trigger builds. - - --name=NAME - Build trigger name. - - --region=REGION - The region of the Cloud Build Service to use. Must be set to a - supported region name (e.g. us-central1). If unset, builds/region, - which is the default region to use when working with Cloud Build - resources, is used. If builds/region is unset, region is set to - global. Note: Region must be specified in 2nd gen repo; global is - not supported. - - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - - --[no-]require-approval - Require manual approval for triggered builds. Use - --require-approval to enable and --no-require-approval to disable. - - --service-account=SERVICE_ACCOUNT - The service account used for all user-controlled operations - including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and - CancelBuild. If no service account is set, then the standard Cloud - Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is - used instead. Format: - projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - - --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. For - example: - - $ gcloud alpha builds triggers create bitbucket-data-center ... \ - --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 - - This will result in a build where every occurrence of - ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and - similarly for ${_NUM_CANDIES} and "10". - - Substitutions can be applied to user-defined variables (starting - with an underscore) and to the following built-in variables: - REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, - SHORT_SHA. - - For more details, see: - https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values - - Exactly one of these must be specified: - - --branch-pattern=REGEX - A regular expression specifying which git branches to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --branch-pattern=foo will match - "foo", "foobar", and "barfoo". Events on a branch that does not - match will be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - --tag-pattern=REGEX - A regular expression specifying which git tags to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --tag-pattern=foo will match "foo", - "foobar", and "barfoo". Events on a tag that does not match will - be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - Pull Request settings - - --pull-request-pattern=REGEX - Regular expression specifying which base git branch to match - for pull request events. - - This pattern is used as a regex search for the base branch (the - branch you are trying to merge into) for pull request updates. - For example, --pull-request-pattern=foo will match "foo", - "foobar", and "barfoo". - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" - Require a repository collaborator or owner to comment '/gcbrun' - on a pull request before running the build. COMMENT_CONTROL - must be one of: - - COMMENTS_DISABLED - Do not require comments on Pull Requests before builds are - triggered. - COMMENTS_ENABLED - Enforce that repository owners or collaborators must - comment on Pull Requests before builds are triggered. - COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY - Enforce that repository owners or collaborators must - comment on external contributors' Pull Requests before - builds are triggered. - - Exactly one of these must be specified: - - --build-config=PATH - Path to a YAML or JSON file containing the build configuration in - the repository. - - For more details, see: - https://cloud.google.com/cloud-build/docs/build-config - - --inline-config=PATH - Local path to a YAML or JSON file containing a build - configuration. - - Dockerfile build configuration flags - - --dockerfile=DOCKERFILE - Path of Dockerfile to use for builds in the repository. - - If specified, a build config will be generated to run docker - build using the specified file. - - The filename is relative to the Dockerfile directory. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-image=DOCKERFILE_IMAGE - Docker image name to build. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-dir=DOCKERFILE_DIR; default="/" - Location of the directory containing the Dockerfile in the - repository. - - The directory will also be used as the Docker build context. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud builds triggers create bitbucket-data-center - - $ gcloud beta builds triggers create bitbucket-data-center - diff --git a/gcloud/alpha/builds/triggers/create/help b/gcloud/alpha/builds/triggers/create/help index c3b35f643..3de891bc8 100644 --- a/gcloud/alpha/builds/triggers/create/help +++ b/gcloud/alpha/builds/triggers/create/help @@ -16,14 +16,6 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - bitbucket-cloud - (ALPHA) Create a build trigger for a 2nd-gen Bitbucket Cloud - repository. - - bitbucket-data-center - (ALPHA) Create a build trigger for a 2nd-gen Bitbucket Data Center - repository. - bitbucketserver (ALPHA) Create a build trigger for a Bitbucket Server repository. diff --git a/gcloud/alpha/builds/triggers/update/bitbucket-cloud b/gcloud/alpha/builds/triggers/update/bitbucket-cloud deleted file mode 100644 index 7e16fbff1..000000000 --- a/gcloud/alpha/builds/triggers/update/bitbucket-cloud +++ /dev/null @@ -1,255 +0,0 @@ -NAME - gcloud alpha builds triggers update bitbucket-cloud - updates Bitbucket - Cloud trigger used by Cloud Build - -SYNOPSIS - gcloud alpha builds triggers update bitbucket-cloud - (TRIGGER : --region=REGION) - (--trigger-config=PATH | --description=DESCRIPTION - --ignored-files=[GLOB,...] --included-files=[GLOB,...] - --repository=REPOSITORY --[no-]require-approval - --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX - | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL - --pull-request-pattern=REGEX --build-config=PATH - | --inline-config=PATH - | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE - : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions - | --remove-substitutions=[KEY,...] - | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Updates Bitbucket Cloud trigger used by Cloud Build. - -EXAMPLES - To update the branch pattern of the trigger: - - $ gcloud alpha builds triggers update bitbucket-cloud my-trigger \ - --branch-pattern=".*" - - To update the build config of the trigger: - - $ gcloud alpha builds triggers update bitbucket-cloud my-trigger \ - --build-config="cloudbuild.yaml" - - To update the substitutions of the trigger: - - $ gcloud alpha builds triggers update bitbucket-cloud my-trigger \ - --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master - - To update the 2nd-gen repository resource of the trigger: - - $ gcloud alpha builds triggers update bitbucket-cloud my-trigger \ - --repository=projects/my-project/locations/us-west1/\ - connections/my-conn/repositories/my-repo - -POSITIONAL ARGUMENTS - Trigger resource - Build Trigger. 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 TRIGGER 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. - - TRIGGER - ID of the trigger or fully qualified identifier for the trigger. - - To set the trigger attribute: - ▸ provide the argument TRIGGER 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 location for the trigger. - - To set the region attribute: - ▸ provide the argument TRIGGER on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -REQUIRED FLAGS - Exactly one of these must be specified: - - --trigger-config=PATH - Path to Build Trigger config file (JSON or YAML format). For more - details, see - https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger - - Flag based trigger configuration - - --description=DESCRIPTION - Build trigger description. - - --ignored-files=[GLOB,...] - Glob filter. Changes only affecting ignored files won't trigger - builds. - - --included-files=[GLOB,...] - Glob filter. Changes affecting at least one included file will - trigger builds. - - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - - --[no-]require-approval - Require manual approval for triggered builds. Use - --require-approval to enable and --no-require-approval to disable. - - --service-account=SERVICE_ACCOUNT - The service account used for all user-controlled operations - including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and - CancelBuild. If no service account is set, then the standard Cloud - Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is - used instead. Format: - projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - - At most one of these can be specified: - - --branch-pattern=REGEX - A regular expression specifying which git branches to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --branch-pattern=foo will match - "foo", "foobar", and "barfoo". Events on a branch that does not - match will be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - --tag-pattern=REGEX - A regular expression specifying which git tags to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --tag-pattern=foo will match "foo", - "foobar", and "barfoo". Events on a tag that does not match will - be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - Pull Request settings - - --comment-control=COMMENT_CONTROL - Require a repository collaborator or owner to comment '/gcbrun' - on a pull request before running the build. COMMENT_CONTROL - must be one of: - - COMMENTS_DISABLED - Do not require comments on Pull Requests before builds are - triggered. - COMMENTS_ENABLED - Enforce that repository owners or collaborators must - comment on Pull Requests before builds are triggered. - COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY - Enforce that repository owners or collaborators must - comment on external contributors' Pull Requests before - builds are triggered. - - --pull-request-pattern=REGEX - A regular expression specifying which base git branch to match - for pull request events. - - This pattern is used as a regular expression search for the - base branch (the branch you are trying to merge into) for pull - request updates. For example, --pull-request-pattern=foo will - match "foo", "foobar", and "barfoo". - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - At most one of these can be specified: - - --build-config=PATH - Path to a YAML or JSON file containing the build configuration in - the repository. - - For more details, see: - https://cloud.google.com/cloud-build/docs/build-config - - --inline-config=PATH - Local path to a YAML or JSON file containing a build - configuration. - - Dockerfile build configuration flags - - --dockerfile=DOCKERFILE - Path of Dockerfile to use for builds in the repository. - - If specified, a build config will be generated to run docker - build using the specified file. - - The filename is relative to the Dockerfile directory. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-image=DOCKERFILE_IMAGE - Docker image name to build. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-dir=DOCKERFILE_DIR - Location of the directory containing the Dockerfile in the - repository. - - The directory will also be used as the Docker build context. - - At most one of these can be specified: - - --clear-substitutions - Clear existing substitutions. - - --remove-substitutions=[KEY,...] - Remove existing substitutions if present. - - --update-substitutions=[KEY=VALUE,...] - Update or add to existing substitutions. Substitutions are - parameters to be substituted or add in the build specification. - - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers update ... - --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 - - This will add the provided substitutions to the existing - substitutions and results in a build where every occurrence of - ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and - similarly for ${_NUM_CANDIES} and "10". - - Only the following built-in variables can be specified with the - --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, - REVISION_ID, COMMIT_SHA, SHORT_SHA. - - For more details, see: - https://cloud.google.com/build/docs/build-config-file-schema#substitutions - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud builds triggers update bitbucket-cloud - - $ gcloud beta builds triggers update bitbucket-cloud - diff --git a/gcloud/alpha/builds/triggers/update/bitbucket-data-center b/gcloud/alpha/builds/triggers/update/bitbucket-data-center deleted file mode 100644 index e4ceee977..000000000 --- a/gcloud/alpha/builds/triggers/update/bitbucket-data-center +++ /dev/null @@ -1,257 +0,0 @@ -NAME - gcloud alpha builds triggers update bitbucket-data-center - updates - Bitbucket Data Center trigger used by Cloud Build - -SYNOPSIS - gcloud alpha builds triggers update bitbucket-data-center - (TRIGGER : --region=REGION) - (--trigger-config=PATH | --description=DESCRIPTION - --ignored-files=[GLOB,...] --included-files=[GLOB,...] - --repository=REPOSITORY --[no-]require-approval - --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX - | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL - --pull-request-pattern=REGEX --build-config=PATH - | --inline-config=PATH - | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE - : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions - | --remove-substitutions=[KEY,...] - | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Updates Bitbucket Data Center trigger used by Cloud Build. - -EXAMPLES - To update the branch pattern of the trigger: - - $ gcloud alpha builds triggers update bitbucket-data-center \ - my-trigger --branch-pattern=".*" - - To update the build config of the trigger: - - $ gcloud alpha builds triggers update bitbucket-data-center \ - my-trigger --build-config="cloudbuild.yaml" - - To update the substitutions of the trigger: - - $ gcloud alpha builds triggers update bitbucket-data-center \ - my-trigger \ - --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master - - To update the 2nd-gen repository resource of the trigger: - - $ gcloud alpha builds triggers update bitbucket-data-center \ - my-trigger \ - --repository=projects/my-project/locations/us-west1/\ - connections/my-conn/repositories/my-repo - -POSITIONAL ARGUMENTS - Trigger resource - Build Trigger. 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 TRIGGER 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. - - TRIGGER - ID of the trigger or fully qualified identifier for the trigger. - - To set the trigger attribute: - ▸ provide the argument TRIGGER 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 location for the trigger. - - To set the region attribute: - ▸ provide the argument TRIGGER on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -REQUIRED FLAGS - Exactly one of these must be specified: - - --trigger-config=PATH - Path to Build Trigger config file (JSON or YAML format). For more - details, see - https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger - - Flag based trigger configuration - - --description=DESCRIPTION - Build trigger description. - - --ignored-files=[GLOB,...] - Glob filter. Changes only affecting ignored files won't trigger - builds. - - --included-files=[GLOB,...] - Glob filter. Changes affecting at least one included file will - trigger builds. - - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - - --[no-]require-approval - Require manual approval for triggered builds. Use - --require-approval to enable and --no-require-approval to disable. - - --service-account=SERVICE_ACCOUNT - The service account used for all user-controlled operations - including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and - CancelBuild. If no service account is set, then the standard Cloud - Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is - used instead. Format: - projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - - At most one of these can be specified: - - --branch-pattern=REGEX - A regular expression specifying which git branches to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --branch-pattern=foo will match - "foo", "foobar", and "barfoo". Events on a branch that does not - match will be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - --tag-pattern=REGEX - A regular expression specifying which git tags to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --tag-pattern=foo will match "foo", - "foobar", and "barfoo". Events on a tag that does not match will - be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - Pull Request settings - - --comment-control=COMMENT_CONTROL - Require a repository collaborator or owner to comment '/gcbrun' - on a pull request before running the build. COMMENT_CONTROL - must be one of: - - COMMENTS_DISABLED - Do not require comments on Pull Requests before builds are - triggered. - COMMENTS_ENABLED - Enforce that repository owners or collaborators must - comment on Pull Requests before builds are triggered. - COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY - Enforce that repository owners or collaborators must - comment on external contributors' Pull Requests before - builds are triggered. - - --pull-request-pattern=REGEX - A regular expression specifying which base git branch to match - for pull request events. - - This pattern is used as a regular expression search for the - base branch (the branch you are trying to merge into) for pull - request updates. For example, --pull-request-pattern=foo will - match "foo", "foobar", and "barfoo". - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - At most one of these can be specified: - - --build-config=PATH - Path to a YAML or JSON file containing the build configuration in - the repository. - - For more details, see: - https://cloud.google.com/cloud-build/docs/build-config - - --inline-config=PATH - Local path to a YAML or JSON file containing a build - configuration. - - Dockerfile build configuration flags - - --dockerfile=DOCKERFILE - Path of Dockerfile to use for builds in the repository. - - If specified, a build config will be generated to run docker - build using the specified file. - - The filename is relative to the Dockerfile directory. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-image=DOCKERFILE_IMAGE - Docker image name to build. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-dir=DOCKERFILE_DIR - Location of the directory containing the Dockerfile in the - repository. - - The directory will also be used as the Docker build context. - - At most one of these can be specified: - - --clear-substitutions - Clear existing substitutions. - - --remove-substitutions=[KEY,...] - Remove existing substitutions if present. - - --update-substitutions=[KEY=VALUE,...] - Update or add to existing substitutions. Substitutions are - parameters to be substituted or add in the build specification. - - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers update ... - --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 - - This will add the provided substitutions to the existing - substitutions and results in a build where every occurrence of - ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and - similarly for ${_NUM_CANDIES} and "10". - - Only the following built-in variables can be specified with the - --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, - REVISION_ID, COMMIT_SHA, SHORT_SHA. - - For more details, see: - https://cloud.google.com/build/docs/build-config-file-schema#substitutions - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud builds triggers update bitbucket-data-center - - $ gcloud beta builds triggers update bitbucket-data-center - diff --git a/gcloud/alpha/builds/triggers/update/help b/gcloud/alpha/builds/triggers/update/help index 02d1fb39f..d44c7b85b 100644 --- a/gcloud/alpha/builds/triggers/update/help +++ b/gcloud/alpha/builds/triggers/update/help @@ -15,12 +15,6 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - bitbucket-cloud - (ALPHA) Updates Bitbucket Cloud trigger used by Cloud Build. - - bitbucket-data-center - (ALPHA) Updates Bitbucket Data Center trigger used by Cloud Build. - bitbucketserver (ALPHA) Updates Bitbucket Server trigger used by Cloud Build. diff --git a/gcloud/alpha/compute/disks/create b/gcloud/alpha/compute/disks/create index 04f16122a..98d36b16e 100644 --- a/gcloud/alpha/compute/disks/create +++ b/gcloud/alpha/compute/disks/create @@ -242,7 +242,7 @@ FLAGS created. --source-instant-snapshot=SOURCE_INSTANT_SNAPSHOT - Source instant snapshot used to create the disks. + Name of the source instant snapshot used to create the disks. --source-snapshot=SOURCE_SNAPSHOT Source snapshot used to create the disks. It is safe to delete a diff --git a/gcloud/alpha/compute/images/import b/gcloud/alpha/compute/images/import index fe9fb71ad..765588e6d 100644 --- a/gcloud/alpha/compute/images/import +++ b/gcloud/alpha/compute/images/import @@ -31,6 +31,11 @@ DESCRIPTION all four of these steps as required, depending on the input arguments specified. + Before importing an image, set up access to Cloud Storage and grant + required roles to the user accounts and service accounts. For more + information, see + https://cloud.google.com/compute/docs/import/requirements-export-import-images. + To override the detected OS, specify the --os flag. You can omit the translation step using the --data-disk flag. diff --git a/gcloud/alpha/compute/instance-groups/managed/all-instances-config/delete b/gcloud/alpha/compute/instance-groups/managed/all-instances-config/delete index 5c6041424..8659bc970 100644 --- a/gcloud/alpha/compute/instance-groups/managed/all-instances-config/delete +++ b/gcloud/alpha/compute/instance-groups/managed/all-instances-config/delete @@ -80,7 +80,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instance-groups managed all-instances-config delete $ gcloud beta compute instance-groups managed all-instances-config \ delete diff --git a/gcloud/alpha/compute/instance-groups/managed/all-instances-config/help b/gcloud/alpha/compute/instance-groups/managed/all-instances-config/help index 361918e68..6c52d51b3 100644 --- a/gcloud/alpha/compute/instance-groups/managed/all-instances-config/help +++ b/gcloud/alpha/compute/instance-groups/managed/all-instances-config/help @@ -31,7 +31,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instance-groups managed all-instances-config $ gcloud beta compute instance-groups managed all-instances-config diff --git a/gcloud/alpha/compute/instance-groups/managed/all-instances-config/update b/gcloud/alpha/compute/instance-groups/managed/all-instances-config/update index b522caf9c..4100d43fc 100644 --- a/gcloud/alpha/compute/instance-groups/managed/all-instances-config/update +++ b/gcloud/alpha/compute/instance-groups/managed/all-instances-config/update @@ -81,7 +81,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instance-groups managed all-instances-config update $ gcloud beta compute instance-groups managed all-instances-config \ update diff --git a/gcloud/alpha/compute/instant-snapshots/add-labels b/gcloud/alpha/compute/instant-snapshots/add-labels index 858d9ed50..83eef7914 100644 --- a/gcloud/alpha/compute/instant-snapshots/add-labels +++ b/gcloud/alpha/compute/instant-snapshots/add-labels @@ -91,7 +91,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instant-snapshots add-labels $ gcloud beta compute instant-snapshots add-labels diff --git a/gcloud/alpha/compute/instant-snapshots/create b/gcloud/alpha/compute/instant-snapshots/create index f80331f84..7078d091e 100644 --- a/gcloud/alpha/compute/instant-snapshots/create +++ b/gcloud/alpha/compute/instant-snapshots/create @@ -95,7 +95,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instant-snapshots create $ gcloud beta compute instant-snapshots create diff --git a/gcloud/alpha/compute/instant-snapshots/delete b/gcloud/alpha/compute/instant-snapshots/delete index 92875dddc..b5261fbf2 100644 --- a/gcloud/alpha/compute/instant-snapshots/delete +++ b/gcloud/alpha/compute/instant-snapshots/delete @@ -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 compute instant-snapshots delete $ gcloud beta compute instant-snapshots delete diff --git a/gcloud/alpha/compute/instant-snapshots/describe b/gcloud/alpha/compute/instant-snapshots/describe index 7927be219..83c2abb5a 100644 --- a/gcloud/alpha/compute/instant-snapshots/describe +++ b/gcloud/alpha/compute/instant-snapshots/describe @@ -77,7 +77,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instant-snapshots describe $ gcloud beta compute instant-snapshots describe diff --git a/gcloud/alpha/compute/instant-snapshots/help b/gcloud/alpha/compute/instant-snapshots/help index f931b5152..295d11472 100644 --- a/gcloud/alpha/compute/instant-snapshots/help +++ b/gcloud/alpha/compute/instant-snapshots/help @@ -39,7 +39,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instant-snapshots $ gcloud beta compute instant-snapshots diff --git a/gcloud/alpha/compute/instant-snapshots/list b/gcloud/alpha/compute/instant-snapshots/list index b656fe23b..0c1a99a71 100644 --- a/gcloud/alpha/compute/instant-snapshots/list +++ b/gcloud/alpha/compute/instant-snapshots/list @@ -108,7 +108,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instant-snapshots list $ gcloud beta compute instant-snapshots list diff --git a/gcloud/alpha/compute/interconnects/attachments/dedicated/create b/gcloud/alpha/compute/interconnects/attachments/dedicated/create index 257003336..9c53dafee 100644 --- a/gcloud/alpha/compute/interconnects/attachments/dedicated/create +++ b/gcloud/alpha/compute/interconnects/attachments/dedicated/create @@ -10,9 +10,10 @@ SYNOPSIS [--cloud-router-ipv6-interface-id=INTERFACE_ID] [--customer-router-ipv6-interface-id=PEER_INTERFACE_ID] [--description=DESCRIPTION] [--dry-run] [--enable-admin] - [--encryption=ENCRYPTION] [--ipsec-internal-addresses=[ADDRESSES]] - [--mtu=MTU] [--region=REGION] [--stack-type=STACK_TYPE] - [--subnet-length=SUBNET_LENGTH] [--vlan=VLAN] [GCLOUD_WIDE_FLAG ...] + [--enable-multicast] [--encryption=ENCRYPTION] + [--ipsec-internal-addresses=[ADDRESSES]] [--mtu=MTU] [--region=REGION] + [--stack-type=STACK_TYPE] [--subnet-length=SUBNET_LENGTH] [--vlan=VLAN] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute interconnects attachments dedicated create is @@ -91,6 +92,11 @@ OPTIONAL FLAGS is operational and will carry traffic. Use --no-enable-admin to disable it. + --enable-multicast + If supplied, the attachment will be able to carry multicast traffic. If + not provided on creation, defaults to disabled. Use + --no-enable-multicast to disable it. + --encryption=ENCRYPTION Indicates the user-supplied encryption option for this interconnect attachment (VLAN attachment). diff --git a/gcloud/alpha/compute/interconnects/attachments/dedicated/update b/gcloud/alpha/compute/interconnects/attachments/dedicated/update index 39d7a8f38..af2c227e4 100644 --- a/gcloud/alpha/compute/interconnects/attachments/dedicated/update +++ b/gcloud/alpha/compute/interconnects/attachments/dedicated/update @@ -7,8 +7,8 @@ SYNOPSIS [--bandwidth=BANDWIDTH] [--candidate-ipv6-subnets=[IPV6_SUBNET,...]] [--cloud-router-ipv6-interface-id=INTERFACE_ID] [--customer-router-ipv6-interface-id=PEER_INTERFACE_ID] - [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU] - [--region=REGION] [--stack-type=STACK_TYPE] + [--description=DESCRIPTION] [--enable-admin] [--enable-multicast] + [--mtu=MTU] [--region=REGION] [--stack-type=STACK_TYPE] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -68,6 +68,10 @@ FLAGS enabled, the attachment is operational and will carry traffic. Use --no-enable-admin to disable it. + --enable-multicast + When enabled, the attachment will be able to carry multicast traffic. + Use --no-enable-multicast to disable it. + --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet passing through this interconnect attachment. Only 1440 and 1500 are diff --git a/gcloud/alpha/compute/snapshots/create b/gcloud/alpha/compute/snapshots/create index fc861b351..d064509ba 100644 --- a/gcloud/alpha/compute/snapshots/create +++ b/gcloud/alpha/compute/snapshots/create @@ -105,9 +105,12 @@ FLAGS encryption key. --source-instant-snapshot=SOURCE_INSTANT_SNAPSHOT - Source instant snapshot used to create the snapshot. To create a - snapshot from a source instant snapshot in a different project, specify - the full path to the source instant snapshot. For example: + The name or URL of the source instant snapshot. If the name is + provided, the instant snapshot's zone or region must be specified with + --source-instant-snapshot-zone or --source-instant-snapshot-region + accordingly. To create a snapshot from an instant snapshot in a + different project, specify the full path to the instant snapshot. If + the URL is provided, format should be: https://www.googleapis.com/compute/v1/projects/MY-PROJECT/zones/MY-ZONE/instantSnapshots/MY-INSTANT-SNAPSHOT --source-instant-snapshot-key-file=FILE diff --git a/gcloud/alpha/config/get b/gcloud/alpha/config/get index 265fe9215..55c3b90d1 100644 --- a/gcloud/alpha/config/get +++ b/gcloud/alpha/config/get @@ -486,6 +486,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index b707e33ef..d0f0e1a3f 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -518,6 +518,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index bfd71bf59..cf36b52f8 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -530,6 +530,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 4a41243a1..ff4996a07 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -533,6 +533,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 6e2a78a37..894c7ffd1 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -494,6 +494,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 646158801..2e96db5b0 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -68,7 +68,8 @@ SYNOPSIS [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--spot] - [--stack-type=STACK_TYPE] [--subnetwork=SUBNETWORK] + [--stack-type=STACK_TYPE] [--storage-pools=STORAGE_POOL,[...]] + [--subnetwork=SUBNETWORK] [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--workload-metadata=WORKLOAD_METADATA] [--workload-pool=WORKLOAD_POOL] @@ -1175,6 +1176,13 @@ FLAGS IP stack type of the node VMs. STACK_TYPE must be one of: ipv4, ipv4-ipv6. + --storage-pools=STORAGE_POOL,[...] + A list of storage pools where the cluster's boot disks will be + provisioned. + + STORAGE_POOL must be in the format + projects/project/zones/zone/storagePools/storagePool + --subnetwork=SUBNETWORK The Google Compute Engine subnetwork (https://cloud.google.com/compute/docs/subnetworks) to which the @@ -1421,7 +1429,7 @@ FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - (DEPRECATED) Select Advanced Datapath Observability mode for the + (REMOVED) Select Advanced Datapath Observability mode for the cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into @@ -1438,10 +1446,7 @@ FLAGS $ gcloud alpha container clusters create \ --dataplane-v2-observability-mode=EXTERNAL_LB - The --dataplane-v2-observability-mode flag is deprecated and will be - removed in an upcoming release. Please use - --enable-dataplane-v2-flow-observability or - --disable-dataplane-v2-flow-observability. + Flag --dataplane-v2-observability-mode has been removed. DATAPLANE_V2_OBSERVABILITY_MODE must be one of: diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index f960292da..e22fa74d0 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -404,7 +404,7 @@ FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - (DEPRECATED) Select Advanced Datapath Observability mode for the + (REMOVED) Select Advanced Datapath Observability mode for the cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into @@ -421,10 +421,7 @@ FLAGS $ gcloud alpha container clusters create-auto \ --dataplane-v2-observability-mode=EXTERNAL_LB - The --dataplane-v2-observability-mode flag is deprecated and will be - removed in an upcoming release. Please use - --enable-dataplane-v2-flow-observability or - --disable-dataplane-v2-flow-observability. + Flag --dataplane-v2-observability-mode has been removed. DATAPLANE_V2_OBSERVABILITY_MODE must be one of: diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index f4334db3c..d06401028 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -966,7 +966,7 @@ REQUIRED FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - (DEPRECATED) Select Advanced Datapath Observability mode for the + (REMOVED) Select Advanced Datapath Observability mode for the cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into @@ -983,10 +983,7 @@ REQUIRED FLAGS $ gcloud alpha container clusters update \ --dataplane-v2-observability-mode=EXTERNAL_LB - The --dataplane-v2-observability-mode flag is deprecated and will - be removed in an upcoming release. Please use - --enable-dataplane-v2-flow-observability or - --disable-dataplane-v2-flow-observability. + Flag --dataplane-v2-observability-mode has been removed. DATAPLANE_V2_OBSERVABILITY_MODE must be one of: diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index eeb2dde16..406fe9266 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -47,6 +47,7 @@ SYNOPSIS [--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, batch-soak-duration=BATCH_SOAK_DURATION,...]] + [--storage-pools=STORAGE_POOL,[...]] [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--tpu-topology=TPU_TOPOLOGY] [--windows-os-version=WINDOWS_OS_VERSION] @@ -634,6 +635,13 @@ FLAGS --standard-rollout-policy=batch-percent=0.3,\ batch-soak-duration=60s + --storage-pools=STORAGE_POOL,[...] + A list of storage pools where the node pool's boot disks will be + provisioned. + + STORAGE_POOL must be in the format + projects/project/zones/zone/storagePools/storagePool + --system-config-from-file=SYSTEM_CONFIG_FROM_FILE Path of the YAML/JSON file that contains the node configuration, including Linux kernel parameters (sysctls) and kubelet configs. diff --git a/gcloud/alpha/container/node-pools/delete b/gcloud/alpha/container/node-pools/delete index 6c79d731f..938222a7b 100644 --- a/gcloud/alpha/container/node-pools/delete +++ b/gcloud/alpha/container/node-pools/delete @@ -11,8 +11,8 @@ DESCRIPTION (ALPHA) gcloud alpha container node-pools delete deletes a node pool from a Google Kubernetes Engine (GKE) cluster. When you delete a node pool, GKE drains all the nodes in the node pool. The draining process involves GKE - evicting Pods on each node in the node pool. Each node in a node pool is - drained by evicting Pods with an allotted graceful termination period of + deleting Pods on each node in the node pool. Each node in a node pool is + drained by deleting Pods with an allotted graceful termination period of MAX_POD. MAX_POD is the maximum terminationGracePeriodSeconds set on the Pods scheduled to the node with a cap of one hour. diff --git a/gcloud/alpha/firestore/operations/help b/gcloud/alpha/firestore/operations/help index 16f475bcf..c45d63cf6 100644 --- a/gcloud/alpha/firestore/operations/help +++ b/gcloud/alpha/firestore/operations/help @@ -28,6 +28,9 @@ COMMANDS list (ALPHA) List pending Cloud Firestore admin operations and their status. + wait + (ALPHA) Waits a Cloud Firestore admin operation to complete. + 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/firestore/operations/wait b/gcloud/alpha/firestore/operations/wait new file mode 100644 index 000000000..23bc116d3 --- /dev/null +++ b/gcloud/alpha/firestore/operations/wait @@ -0,0 +1,37 @@ +NAME + gcloud alpha firestore operations wait - waits a Cloud Firestore admin + operation to complete + +SYNOPSIS + gcloud alpha firestore operations wait NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Waits a Cloud Firestore admin operation to complete. + +EXAMPLES + To wait a Cloud Firestore admin operation exampleOperationId to complete, + run: + + $ gcloud alpha firestore operations wait exampleOperationId + +POSITIONAL ARGUMENTS + NAME + The unique name of the Operation to retrieve, formatted as full + resource path: + + projects/my-app-id/databases/(default)/operations/foo + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/iap/settings/set b/gcloud/alpha/iap/settings/set index 3627f219d..2c4fac048 100644 --- a/gcloud/alpha/iap/settings/set +++ b/gcloud/alpha/iap/settings/set @@ -14,48 +14,51 @@ DESCRIPTION EXAMPLES To set the IAP setting for the resources within an organization, run: - $ gcloud alpha iap settings set SETTING_FILE \ + $ gcloud alpha iap settings set iap_settings.yaml \ --organization=ORGANIZATION_ID To set the IAP setting for the resources within a folder, run: - $ gcloud alpha iap settings set SETTING_FILE --folder=FOLDER_ID + $ gcloud alpha iap settings set iap_settings.yaml --folder=FOLDER_ID To set the IAP setting for the resources within a project, run: - $ gcloud alpha iap settings set SETTING_FILE --project=PROJECT_ID + $ gcloud alpha iap settings set iap_settings.yaml \ + --project=PROJECT_ID To set the IAP setting for web type resources within a project, run: - $ gcloud alpha iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=iap_web + $ gcloud alpha iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=iap_web To set the IAP setting for all app engine services within a project, run: - $ gcloud alpha iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=app-engine + $ gcloud alpha iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=app-engine To set the IAP setting for an app engine service within a project, run: - $ gcloud alpha iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=app-engine --service=SERVICE_ID + $ gcloud alpha iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=app-engine \ + --service=SERVICE_ID To set the IAP setting for an app engine service version within a project, run: - $ gcloud alpha iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=app-engine --service=SERVICE_ID \ - --version=VERSION_ID + $ gcloud alpha iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=app-engine \ + --service=SERVICE_ID --version=VERSION_ID To set the IAP setting for all backend services within a project, run: - $ gcloud alpha iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=compute + $ gcloud alpha iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=compute To set the IAP setting for a backend service within a project, run: - $ gcloud alpha iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=compute --service=SERVICE_ID + $ gcloud alpha iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=compute \ + --service=SERVICE_ID POSITIONAL ARGUMENTS SETTING_FILE diff --git a/gcloud/alpha/network-security/firewall-endpoint-associations/update b/gcloud/alpha/network-security/firewall-endpoint-associations/update index c70b7023c..263b951c3 100644 --- a/gcloud/alpha/network-security/firewall-endpoint-associations/update +++ b/gcloud/alpha/network-security/firewall-endpoint-associations/update @@ -5,9 +5,9 @@ NAME SYNOPSIS gcloud alpha network-security firewall-endpoint-associations update (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--async] - [--max-wait=MAX_WAIT; default="60m"] [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] - [--no-tls-inspection-policy + [--max-wait=MAX_WAIT; default="60m"] + [--disabled | --update-labels=[KEY=VALUE,...] --clear-labels + | --remove-labels=[KEY,...] --no-tls-inspection-policy | [--tls-inspection-policy=TLS_INSPECTION_POLICY : --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT --tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION]] @@ -84,78 +84,89 @@ FLAGS 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: + --disabled + Disable a firewall endpoint association. To enable a disabled + association, use: $ gcloud alpha network-security firewall-endpoint-associations \ - update --clear-labels + update MY-ASSOCIATION --no-disabled - To remove all existing labels and create two new labels, foo and baz: + --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. - $ gcloud alpha network-security firewall-endpoint-associations \ - update --clear-labels --update-labels foo=bar,baz=qux + 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. - --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. + At most one of these can be specified: - 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. - --no-tls-inspection-policy - Remove TLS inspection policy from this association. + For example, to remove all labels: - TLS Inspection Policy resource - Path to TLS Inspection Policy - configuration to use for intercepting TLS-encrypted traffic in this - network. The arguments in this group can be used to specify the - attributes of this resource. + $ gcloud alpha network-security firewall-endpoint-associations \ + update --clear-labels - --tls-inspection-policy=TLS_INSPECTION_POLICY - ID of the TLS Inspection Policy or fully qualified identifier for - the TLS Inspection Policy. + To remove all existing labels and create two new labels, foo and + baz: - To set the tls_inspection_policy attribute: - ▫ provide the argument --tls-inspection-policy on the command - line. + $ gcloud alpha network-security firewall-endpoint-associations \ + update --clear-labels --update-labels foo=bar,baz=qux - This flag argument must be specified if any of the other arguments - in this group are specified. + --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. - --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT - Project of the TLS Inspection Policy. + At most one of these can be specified: - To set the tls-inspection-policy-project attribute: - ▫ provide the argument --tls-inspection-policy on the command - line with a fully specified name; - ▫ provide the argument --tls-inspection-policy-project on the - command line; - ▫ provide the argument --project on the command line; - ▫ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the - command line with a fully specified name. + --no-tls-inspection-policy + Remove TLS inspection policy from this association. - --tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION - Region of the TLS Inspection Policy. NOTE: TLS Inspection Policy - needs to be in the same region as Firewall Plus endpoint resource. + TLS Inspection Policy resource - Path to TLS Inspection Policy + configuration to use for intercepting TLS-encrypted traffic in this + network. The arguments in this group can be used to specify the + attributes of this resource. - To set the tls-inspection-policy-region attribute: - ▫ provide the argument --tls-inspection-policy on the command - line with a fully specified name; - ▫ provide the argument --tls-inspection-policy-region on the - command line. + --tls-inspection-policy=TLS_INSPECTION_POLICY + ID of the TLS Inspection Policy or fully qualified identifier for + the TLS Inspection Policy. + + To set the tls_inspection_policy attribute: + ◇ provide the argument --tls-inspection-policy on the command + line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT + Project of the TLS Inspection Policy. + + To set the tls-inspection-policy-project attribute: + ◇ provide the argument --tls-inspection-policy on the command + line with a fully specified name; + ◇ provide the argument --tls-inspection-policy-project on the + command line; + ◇ provide the argument --project on the command line; + ◇ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the + command line with a fully specified name. + + --tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION + Region of the TLS Inspection Policy. NOTE: TLS Inspection Policy + needs to be in the same region as Firewall Plus endpoint + resource. + + To set the tls-inspection-policy-region attribute: + ◇ provide the argument --tls-inspection-policy on the command + line with a fully specified name; + ◇ provide the argument --tls-inspection-policy-region on the + command line. 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 f2e02ee71..5e4ff16fc 100644 --- a/gcloud/alpha/scc/findings/bulk-mute +++ b/gcloud/alpha/scc/findings/bulk-mute @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha scc findings bulk-mute (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) - [--filter=FILTER] [GCLOUD_WIDE_FLAG ...] + [--filter=FILTER] [--location=LOCATION; default="global"] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Bulk mute Security Command Center findings based on a filter. @@ -17,24 +18,25 @@ EXAMPLES $ gcloud alpha scc findings bulk-mute \ --organization=organizations/123 \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc findings bulk-mute --organization=123 \ - --filter="category=\"XSS_SCRIPTING\"" To bulk mute findings given folder 123 based on a filter on category that equals XSS_SCRIPTING, run: $ gcloud alpha scc findings bulk-mute --folder=folders/123 \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc findings bulk-mute --folder=123 \ - --filter="category=\"XSS_SCRIPTING\"" To bulk mute findings given project 123 based on a filter on category that equals XSS_SCRIPTING, run: $ gcloud alpha scc findings bulk-mute --project=projects/123 \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc findings bulk-mute --project=123 \ - --filter="category=\"XSS_SCRIPTING\"" + + To bulk mute findings given organization 123 based on a filter on category + that equals XSS_SCRIPTING and location=eu run: + + $ gcloud alpha scc findings bulk-mute \ + --organization=organizations/123 \ + --filter="category=\"XSS_SCRIPTING\"" --location=locations/eu REQUIRED FLAGS Exactly one of these must be specified: @@ -55,6 +57,17 @@ OPTIONAL FLAGS --filter=FILTER The filter string which will applied to findings being muted. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -64,8 +77,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/findings/create b/gcloud/alpha/scc/findings/create index 53e603152..ae668635a 100644 --- a/gcloud/alpha/scc/findings/create +++ b/gcloud/alpha/scc/findings/create @@ -1,49 +1,59 @@ NAME - gcloud alpha scc findings create - create a Cloud Security Command Center - finding + gcloud alpha scc findings create - create a Security Command Center finding SYNOPSIS gcloud alpha scc findings create (FINDING : --organization=ORGANIZATION --source=SOURCE) --category=CATEGORY --event-time=EVENT_TIME --resource-name=RESOURCE_NAME [--external-uri=EXTERNAL_URI] + [--location=LOCATION; default="global"] [--source-properties=[KEY=VALUE,...]] [--state=STATE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create a Cloud Security Command Center finding. + (ALPHA) Create a Security Command Center finding. EXAMPLES - Create an ACTIVE myFinding with category: XSS_SCRIPTING attached to - example-project under organization 123456 and source 5678: + Create an ACTIVE finding testFinding with category: XSS_SCRIPTING attached + to example-project under organization 123456 and source 5678: - $ gcloud alpha scc findings create `myFinding` \ + $ gcloud alpha scc findings create `testFinding` \ --organization=123456 --source=5678 --state=ACTIVE \ --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' - Create an ACTIVE myFinding attached to example-project under project - example-project and source 5678: + Create an ACTIVE finding testFinding attached to example-project under + project example-project and source 5678: $ gcloud alpha scc findings create \ - projects/example-project/sources/5678/findings/myFinding \ + projects/example-project/sources/5678/findings/testFinding \ --state=ACTIVE --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' - Create an ACTIVE myFinding attached to example-project under folder 456 and - source 5678: + Create an ACTIVE finding testFinding attached to example-project under + folder 456 and source 5678: $ gcloud alpha scc findings create \ - folders/456/sources/5678/findings/myFinding --state=ACTIVE \ + folders/456/sources/5678/findings/testFinding --state=ACTIVE \ --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' + Create an ACTIVE finding testFinding with category: XSS_SCRIPTING attached + to example-project under organization 123456, source 5678 and location=eu: + + $ gcloud alpha scc findings create `testFinding` \ + --organization=123456 --source=5678 --state=ACTIVE \ + --category='XSS_SCRIPTING' \ + --event-time=2023-01-11T07:00:06.861Z \ + --resource-name='//cloudresourcemanager.googleapis.com/projects/\ + example-project' --location=eu + POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command Center) command. The arguments in this group can be used to specify the @@ -108,6 +118,17 @@ OPTIONAL FLAGS finding can be found. This field is guaranteed to be either empty or a well formed URL. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --source-properties=[KEY=VALUE,...] Source specific properties. These properties are managed by the source that writes the finding. The key names in the source_properties map @@ -128,8 +149,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/findings/group b/gcloud/alpha/scc/findings/group index bc3dd5857..57233cb73 100644 --- a/gcloud/alpha/scc/findings/group +++ b/gcloud/alpha/scc/findings/group @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha scc findings group [PARENT] [--compare-duration=COMPARE_DURATION] [--filter=FILTER] - [--group-by=GROUP_BY] [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN] + [--group-by=GROUP_BY] [--location=LOCATION; default="global"] + [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN] [--read-time=READ_TIME] [--source=SOURCE; default="-"] [GCLOUD_WIDE_FLAG ...] @@ -54,6 +55,12 @@ EXAMPLES $ gcloud alpha scc findings group 123456 --source=5678 \ --group-by="state_change" --compare-duration=86400s + Group findings under organization 123456 and location=eu across all sources + by their category: + + $ gcloud alpha scc findings group 123456 --group-by="category" \ + --location=eu + POSITIONAL ARGUMENTS Parent resource - parent organization, folder, or project in the Google Cloud resource hierarchy to be used for the gcloud scc command. Specify @@ -127,6 +134,17 @@ FLAGS ◆ state ◆ parent + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --page-size=PAGE_SIZE Maximum number of results to return in a single response. Default is 10, minimum is 1, maximum is 1000. @@ -154,8 +172,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/findings/help b/gcloud/alpha/scc/findings/help index a8f240267..70cafaacb 100644 --- a/gcloud/alpha/scc/findings/help +++ b/gcloud/alpha/scc/findings/help @@ -20,7 +20,7 @@ COMMANDS (ALPHA) Bulk mute Security Command Center findings based on a filter. create - (ALPHA) Create a Cloud Security Command Center finding. + (ALPHA) Create a Security Command Center finding. group (ALPHA) Filter an organization or source's findings and groups them by @@ -33,13 +33,13 @@ COMMANDS (ALPHA) List a finding's security marks. set-mute - (ALPHA) Update a Cloud Security Command Center finding's mute state. + (ALPHA) Update a Security Command Center finding's mute state. update - (ALPHA) Update a Cloud Security Command Center finding. + (ALPHA) Update a Security Command Center finding. update-marks - (ALPHA) Update Cloud Security Command Center finding's security marks. + (ALPHA) Update Security Command Center finding's security marks. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/findings/list b/gcloud/alpha/scc/findings/list index 3c75ad7e0..5d0f9b94a 100644 --- a/gcloud/alpha/scc/findings/list +++ b/gcloud/alpha/scc/findings/list @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha scc findings list [PARENT] [--compare-duration=COMPARE_DURATION] [--field-mask=FIELD_MASK] - [--order-by=ORDER_BY] [--page-token=PAGE_TOKEN] [--read-time=READ_TIME] + [--location=LOCATION; default="global"] [--order-by=ORDER_BY] + [--page-token=PAGE_TOKEN] [--read-time=READ_TIME] [--source=SOURCE; default="-"] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -64,6 +65,11 @@ EXAMPLES $ gcloud alpha scc findings list 123456 \ --filter="state=\"ACTIVE\"" --read-time="2019-01-01T01:00:00Z" + List all findings under organization 123456 across all sources and + location=eu: + + $ gcloud alpha scc findings list 123456 --location=eu + POSITIONAL ARGUMENTS Parent resource - parent organization, folder, or project in the Google Cloud resource hierarchy to be used for the gcloud scc command. Specify @@ -118,6 +124,17 @@ FLAGS v/s camel case used in field masks. An empty or missing field mask will list all fields. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --order-by=ORDER_BY Expression that defines what fields and order to use for sorting. String value should follow SQL syntax: comma separated list of fields. @@ -177,8 +194,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/findings/list-marks b/gcloud/alpha/scc/findings/list-marks index 52467d2c6..6c17f001a 100644 --- a/gcloud/alpha/scc/findings/list-marks +++ b/gcloud/alpha/scc/findings/list-marks @@ -4,30 +4,36 @@ NAME SYNOPSIS gcloud alpha scc findings list-marks (FINDING : --organization=ORGANIZATION --source=SOURCE) - [--page-token=PAGE_TOKEN] [--read-time=READ_TIME] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION; default="global"] [--page-token=PAGE_TOKEN] + [--read-time=READ_TIME] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) List a finding's security marks. EXAMPLES - List all security marks for myFinding under organization 123456 and source - 5678: + List all security marks for testFinding under organization 123456 and + source 5678: - $ gcloud alpha scc findings list-marks `myFinding` \ + $ gcloud alpha scc findings list-marks `testFinding` \ --organization=123456 --source=5678 - List all security marks for myFinding under project example-project and + List all security marks for testFinding under project example-project and source 5678: $ gcloud alpha scc findings list-marks \ - projects/example-project/sources/5678/findings/myFinding + projects/example-project/sources/5678/findings/testFinding - List all security marks for myFinding under folder 456 and source 5678: + List all security marks for testFinding under folder 456 and source 5678: $ gcloud alpha scc findings list-marks \ - folders/456/sources/5678/findings/myFinding + folders/456/sources/5678/findings/testFinding + + List all security marks for testFinding under organization 123456, source + 5678 and location=eu: + + $ gcloud alpha scc findings list-marks `testFinding` \ + --organization=123456 --source=5678 --location=eu POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command @@ -71,6 +77,17 @@ POSITIONAL ARGUMENTS ▸ provide the argument --source on the command line. FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --page-token=PAGE_TOKEN Response objects will return a non-null value for page-token to indicate that there is at least one additional page of data. User can @@ -117,8 +134,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/findings/set-mute b/gcloud/alpha/scc/findings/set-mute index d756b3dc7..c590cc337 100644 --- a/gcloud/alpha/scc/findings/set-mute +++ b/gcloud/alpha/scc/findings/set-mute @@ -1,14 +1,15 @@ NAME - gcloud alpha scc findings set-mute - update a Cloud Security Command Center + gcloud alpha scc findings set-mute - update a Security Command Center finding's mute state SYNOPSIS - gcloud alpha scc findings set-mute FINDING --mute=MUTE [--source=SOURCE] + gcloud alpha scc findings set-mute FINDING --mute=MUTE + [--location=LOCATION; default="global"] [--source=SOURCE] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Update a Cloud Security Command Center finding's mute state. + (ALPHA) Update a Security Command Center finding's mute state. EXAMPLES To update finding's mute state to MUTED, given finding @@ -16,40 +17,31 @@ EXAMPLES $ gcloud alpha scc findings set-mute 789 \ --organization=organizations/123 --source=456 --mute=MUTED - $ gcloud alpha scc findings set-mute 789 --organization=123 \ - --source=456 --mute=MUTED - $ gcloud alpha scc findings set-mute \ - organizations/123/sources/456/findings/789 --mute=MUTED To update finding's mute state to UNMUTED, given finding organizations/123/sources/456/findings/789, run: $ gcloud alpha scc findings set-mute 789 \ --organization=organizations/123 --source=456 --mute=UNMUTED - $ gcloud alpha scc findings set-mute 789 --organization=123 \ - --source=456 --mute=UNMUTED - $ gcloud alpha scc findings set-mute \ - organizations/123/sources/456/findings/789 --mute=UNMUTED To update finding's mute state to MUTED, given finding folders/123/sources/456/findings/789, run: $ gcloud alpha scc findings set-mute 789 --folder=folders/123 \ --source=456 --mute=MUTED - $ gcloud alpha scc findings set-mute 789 --folder=123 --source=456 \ - --mute=MUTED - $ gcloud alpha scc findings set-mute \ - folders/123/sources/456/findings/789 --mute=MUTED To update finding's mute state to MUTED, given finding projects/123/sources/456/findings/789, run: $ gcloud alpha scc findings set-mute 789 --project=projects/123 \ --source=456 --mute=MUTED - $ gcloud alpha scc findings set-mute 789 --project=123 \ - --source=456 --mute=MUTED - $ gcloud alpha scc findings set-mute \ - projects/123/sources/456/findings/789 --mute=MUTED + + To update finding's mute state to MUTED, given finding + organizations/123/sources/456/findings/789 and location=eu, run: + + $ gcloud alpha scc findings set-mute 789 \ + --organization=organizations/123 --source=456 --mute=MUTED \ + --location=locations/eu POSITIONAL ARGUMENTS FINDING @@ -60,6 +52,17 @@ REQUIRED FLAGS Desired mute state of the finding. MUTE must be one of: muted, unmuted. OPTIONAL FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --source=SOURCE ID of the source. @@ -86,8 +89,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/findings/update b/gcloud/alpha/scc/findings/update index 7e9f49d5e..2a6146578 100644 --- a/gcloud/alpha/scc/findings/update +++ b/gcloud/alpha/scc/findings/update @@ -1,48 +1,54 @@ NAME - gcloud alpha scc findings update - update a Cloud Security Command Center - finding + gcloud alpha scc findings update - update a Security Command Center finding SYNOPSIS gcloud alpha scc findings update (FINDING : --organization=ORGANIZATION --source=SOURCE) [--event-time=EVENT_TIME] [--external-uri=EXTERNAL_URI] + [--location=LOCATION; default="global"] [--source-properties=[KEY=VALUE,...]] [--state=STATE] [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Update a Cloud Security Command Center finding. + (ALPHA) Update a Security Command Center finding. EXAMPLES - Update myFinding's state from ACTIVE to INACTIVE: + Update testFinding's state from ACTIVE to INACTIVE: - $ gcloud alpha scc findings update `myFinding` \ + $ gcloud alpha scc findings update `testFinding` \ --organization=123456 --source=5678 --state=INACTIVE - Update myFinding's state from ACTIVE to INACTIVE using project name for + Update testFinding's state from ACTIVE to INACTIVE using project name for example-project: $ gcloud alpha scc findings update \ - projects/example-project/sources/5678/findings/myFinding \ + projects/example-project/sources/5678/findings/testFinding \ --state=INACTIVE - Update myFinding's state from ACTIVE to INACTIVE using folder name 456: + Update testFinding's state from ACTIVE to INACTIVE using folder name 456: $ gcloud alpha scc findings update \ - folders/456/sources/5678/findings/myFinding --state=INACTIVE + folders/456/sources/5678/findings/testFinding --state=INACTIVE - Override all source properties on myFinding: + Override all source properties on testFinding: - $ gcloud alpha scc findings update `myFinding` \ + $ gcloud alpha scc findings update `testFinding` \ --organization=123456 --source=5678 \ --source-properties="propKey1=propVal1,propKey2=propVal2" - Selectively update a specific source property on myFinding: + Selectively update a specific source property on testFinding: - $ gcloud alpha scc findings update `myFinding` \ + $ gcloud alpha scc findings update `testFinding` \ --organization=123456 --source=5678 \ --source-properties="propKey1=propVal1,propKey2=propVal2" \ --update-mask="source_properties.propKey1" + Update finding testFinding with location=eu, state from ACTIVE to INACTIVE: + + $ gcloud alpha scc findings update `testFinding` \ + --organization=123456 --source=5678 --state=INACTIVE \ + --location=eu + POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command Center) command. The arguments in this group can be used to specify the @@ -98,6 +104,17 @@ FLAGS finding can be found. This field is guaranteed to be either empty or a well formed URL. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --source-properties=[KEY=VALUE,...] Source specific properties. These properties are managed by the source that writes the finding. The key names in the source_properties map @@ -133,8 +150,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/findings/update-marks b/gcloud/alpha/scc/findings/update-marks index 020d0d4d6..9d1100d7b 100644 --- a/gcloud/alpha/scc/findings/update-marks +++ b/gcloud/alpha/scc/findings/update-marks @@ -1,49 +1,57 @@ NAME - gcloud alpha scc findings update-marks - update Cloud Security Command - Center finding's security marks + gcloud alpha scc findings update-marks - update Security Command Center + finding's security marks SYNOPSIS gcloud alpha scc findings update-marks (FINDING : --organization=ORGANIZATION --source=SOURCE) + [--location=LOCATION; default="global"] [--security-marks=[KEY=VALUE,...]] [--start-time=START_TIME] [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Update Cloud Security Command Center finding's security marks. + (ALPHA) Update Security Command Center finding's security marks. EXAMPLES - Selectively update security mark (Key1) with value (v1) on myFinding. Note - that other security marks on myFinding are untouched: + Selectively update security mark Key1 with value v1 on testFinding. Note + that other security marks on testFinding are untouched: - $ gcloud alpha scc findings update-marks `myFinding` \ + $ gcloud alpha scc findings update-marks `testFinding` \ --organization=123456 --source=5678 --security-marks="key1=v1" \ --update-mask="marks.markKey1" - Update all security marks on myFinding, under project example-project and + Update all security marks on testFinding, under project example-project and source 5678: $ gcloud alpha scc findings update-marks \ - projects/example-project/sources/5678/findings/myFinding \ + projects/example-project/sources/5678/findings/testFinding \ --security-marks="key1=v1,key2=v2" - Update all security marks on myFinding, under folder 456 and source 5678: + Update all security marks on testFinding, under folder 456 and source 5678: $ gcloud alpha scc findings update-marks \ - folders/456/sources/5678/findings/myFinding \ + folders/456/sources/5678/findings/testFinding \ --security-marks="key1=v1,key2=v2" - Update all security marks on myFinding, under organization 123456 and + Update all security marks on testFinding, under organization 123456 and source 5678: - $ gcloud alpha scc findings update-marks `myFinding` \ + $ gcloud alpha scc findings update-marks `testFinding` \ --organization=123456 --source=5678 \ --security-marks="key1=v1,key2=v2" - Delete all security marks on myFinding: + Delete all security marks on testFinding: - $ gcloud alpha scc findings update-marks `myFinding` \ + $ gcloud alpha scc findings update-marks `testFinding` \ --organization=123456 --source=5678 --security-marks="" + Update all security marks on testFinding, under project example-project, + source 5678 and location=eu: + + $ gcloud alpha scc findings update-marks \ + projects/example-project/sources/5678/findings/testFinding \ + --security-marks="key1=v1,key2=v2" --location=eu + POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command Center) command. The arguments in this group can be used to specify the @@ -86,6 +94,17 @@ POSITIONAL ARGUMENTS ▸ provide the argument --source on the command line. FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --security-marks=[KEY=VALUE,...] SecurityMarks resource to be passed as the request body. It's a key=value pair separated by comma (,). For example: @@ -111,8 +130,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/muteconfigs/create b/gcloud/alpha/scc/muteconfigs/create index 641394f73..94e3b2627 100644 --- a/gcloud/alpha/scc/muteconfigs/create +++ b/gcloud/alpha/scc/muteconfigs/create @@ -1,62 +1,45 @@ NAME - gcloud alpha scc muteconfigs create - create a Cloud Security Command - Center mute config + gcloud alpha scc muteconfigs create - create a Security Command Center mute + config SYNOPSIS gcloud alpha scc muteconfigs create MUTE_CONFIG [--description=DESCRIPTION] - [--filter=FILTER] + [--filter=FILTER] [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create a Cloud Security Command Center mute config. + (ALPHA) Create a Security Command Center mute config. EXAMPLES - To create a mute config my-mute-config given organization 123 with a filter - on category that equals to XSS_SCRIPTING, run: + To create a mute config test-mute-config given organization 123 with a + filter on category that equals to XSS_SCRIPTING, run: - $ gcloud alpha scc muteconfigs create my-mute-config \ - --organization=organizations/123 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc muteconfigs create my-mute-config \ + $ gcloud alpha scc muteconfigs create test-mute-config \ --organization=123 --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc muteconfigs create \ - organizations/123/muteConfigs/my-mute-config \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - To create a mute config my-mute-config given folder 456 with a filter on + To create a mute config test-mute-config given folder 456 with a filter on category that equals to XSS_SCRIPTING, run: - $ gcloud alpha scc muteconfigs create my-mute-config \ - --folder=folders/456 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc muteconfigs create my-mute-config --folder=456 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc muteconfigs create \ - folders/456/muteConfigs/my-mute-config \ - --description="This is a test mute config" \ + $ gcloud alpha scc muteconfigs create test-mute-config \ + --folder=456 --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" - To create a mute config my-mute-config given project 789 with a filter on + To create a mute config test-mute-config given project 789 with a filter on category that equals to XSS_SCRIPTING, run: - $ gcloud alpha scc muteconfigs create my-mute-config \ - --project=projects/789 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc muteconfigs create my-mute-config --project=789 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc muteconfigs create \ - projects/789/muteConfigs/my-mute-config \ - --description="This is a test mute config" \ + $ gcloud alpha scc muteconfigs create test-mute-config \ + --project=789 --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" + To create a mute config test-mute-config given organization 123, + location=eu with a filter on category that equals to XSS_SCRIPTING, run: + + $ gcloud alpha scc muteconfigs create test-mute-config \ + --organization=123 --description="This is a test mute config" \ + --filter="category=\"XSS_SCRIPTING\"" --location=eu + POSITIONAL ARGUMENTS MUTE_CONFIG ID of the mute config or the full resource name of the mute config. @@ -69,6 +52,17 @@ FLAGS The filter string which will applied to findings muted by a mute configuration. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -92,8 +86,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/muteconfigs/delete b/gcloud/alpha/scc/muteconfigs/delete index c11c329e2..ec45401c7 100644 --- a/gcloud/alpha/scc/muteconfigs/delete +++ b/gcloud/alpha/scc/muteconfigs/delete @@ -1,49 +1,53 @@ NAME - gcloud alpha scc muteconfigs delete - delete a Cloud Security Command - Center mute config + gcloud alpha scc muteconfigs delete - delete a Security Command Center mute + config SYNOPSIS gcloud alpha scc muteconfigs delete MUTE_CONFIG + [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete a Cloud Security Command Center mute config. + (ALPHA) Delete a Security Command Center mute config. EXAMPLES - To delete a mute config given organization 123 with id my-test-mute-config, + To delete a mute config given organization 123 with id test-mute-config, run: - $ gcloud alpha scc muteconfigs delete my-test-mute-config \ - --organization=organizations/123 - $ gcloud alpha scc muteconfigs delete my-test-mute-config \ + $ gcloud alpha scc muteconfigs delete test-mute-config \ --organization=123 - $ gcloud alpha scc muteconfigs delete \ - organizations/123/muteConfigs/my-test-mute-config - To delete a mute config given folder 456 with id my-test-mute-config, run: + To delete a mute config given folder 456 with id test-mute-config, run: - $ gcloud alpha scc muteconfigs delete my-test-mute-config \ - --folder=folders/456 - $ gcloud alpha scc muteconfigs delete my-test-mute-config \ - --folder=456 - $ gcloud alpha scc muteconfigs delete \ - folders/456/muteConfigs/my-test-mute-config + $ gcloud alpha scc muteconfigs delete test-mute-config --folder=456 - To delete a mute config given project 789 with id my-test-mute-config, run: + To delete a mute config given project 789 with id test-mute-config, run: - $ gcloud alpha scc muteconfigs delete my-test-mute-config \ - --project=projects/789 - $ gcloud alpha scc muteconfigs delete my-test-mute-config \ - --project=789 - $ gcloud alpha scc muteconfigs delete \ - projects/789/muteConfigs/my-test-mute-config + $ gcloud alpha scc muteconfigs delete test-mute-config --project=789 + + To delete a mute config given organization 123 with id test-mute-config and + location=eu, run: + + $ gcloud alpha scc muteconfigs delete test-mute-config \ + --organization=123 --location=eu POSITIONAL ARGUMENTS MUTE_CONFIG ID of the mute config or the full resource name of the mute config. FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -67,8 +71,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/muteconfigs/get b/gcloud/alpha/scc/muteconfigs/get index ede683be4..3a595131b 100644 --- a/gcloud/alpha/scc/muteconfigs/get +++ b/gcloud/alpha/scc/muteconfigs/get @@ -1,47 +1,52 @@ NAME - gcloud alpha scc muteconfigs get - get a Cloud Security Command Center mute + gcloud alpha scc muteconfigs get - get a Security Command Center mute config SYNOPSIS gcloud alpha scc muteconfigs get MUTE_CONFIG + [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Get a Cloud Security Command Center mute config. + (ALPHA) Get a Security Command Center mute config. EXAMPLES - To get a mute config given organization 123 with id my-test-mute-config, - run: + To get a mute config given organization 123 with id test-mute-config, run: - $ gcloud alpha scc muteconfigs get my-test-mute-config \ - --organization=organizations/123 - $ gcloud alpha scc muteconfigs get my-test-mute-config \ + $ gcloud alpha scc muteconfigs get test-mute-config \ --organization=123 - $ gcloud alpha scc muteconfigs get \ - organizations/123/muteConfigs/my-test-mute-config - To get a mute config given folder 456 with id my-test-mute-config, run: + To get a mute config given folder 456 with id test-mute-config, run: - $ gcloud alpha scc muteconfigs get my-test-mute-config \ - --folder=folders/456 - $ gcloud alpha scc muteconfigs get my-test-mute-config --folder=456 - $ gcloud alpha scc muteconfigs get \ - folders/456/muteConfigs/my-test-mute-config + $ gcloud alpha scc muteconfigs get test-mute-config --folder=456 - To get a mute config given project 789 with id my-test-mute-config, run: + To get a mute config given project 789 with id test-mute-config, run: - $ gcloud alpha scc muteconfigs get my-test-mute-config \ - --project=projects/789 - $ gcloud alpha scc muteconfigs get my-test-mute-config --project=789 - $ gcloud alpha scc muteconfigs get \ - projects/789/muteConfigs/my-test-mute-config + $ gcloud alpha scc muteconfigs get test-mute-config --project=789 + + To get a mute config given organization 123 with id test-mute-config and + location=eu, run: + + $ gcloud alpha scc muteconfigs get test-mute-config \ + --organization=123 --location=eu POSITIONAL ARGUMENTS MUTE_CONFIG ID of the mute config or the full resource name of the mute config. FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -65,8 +70,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/muteconfigs/help b/gcloud/alpha/scc/muteconfigs/help index 95fee16c0..b26e12166 100644 --- a/gcloud/alpha/scc/muteconfigs/help +++ b/gcloud/alpha/scc/muteconfigs/help @@ -17,19 +17,19 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create a Cloud Security Command Center mute config. + (ALPHA) Create a Security Command Center mute config. delete - (ALPHA) Delete a Cloud Security Command Center mute config. + (ALPHA) Delete a Security Command Center mute config. get - (ALPHA) Get a Cloud Security Command Center mute config. + (ALPHA) Get a Security Command Center mute config. list - (ALPHA) List Cloud Security Command Center mute configs. + (ALPHA) ListSecurity Command Center mute configs. update - (ALPHA) Update a Cloud Security Command Center mute config. + (ALPHA) Update a Security Command Center mute config. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/muteconfigs/list b/gcloud/alpha/scc/muteconfigs/list index d8df174f7..dbdb0c2d5 100644 --- a/gcloud/alpha/scc/muteconfigs/list +++ b/gcloud/alpha/scc/muteconfigs/list @@ -1,32 +1,34 @@ NAME - gcloud alpha scc muteconfigs list - list Cloud Security Command Center mute + gcloud alpha scc muteconfigs list - listSecurity Command Center mute configs SYNOPSIS gcloud alpha scc muteconfigs list (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION; default="global"] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Cloud Security Command Center mute configs. + (ALPHA) List Security Command Center mute configs. EXAMPLES List mute configs under organization 123: - $ gcloud alpha scc muteconfigs list --organization=organizations/123 $ gcloud alpha scc muteconfigs list --organization=123 List mute configs under folder 456: - $ gcloud alpha scc muteconfigs list --folder=folders/456 $ gcloud alpha scc muteconfigs list --folder=456 List mute configs under project 789: - $ gcloud alpha scc muteconfigs list --project=projects/789 $ gcloud alpha scc muteconfigs list --project=789 + List mute configs under organization `_123_` and `location=eu`: + + $ gcloud alpha scc muteconfigs list --organization=123 --location=eu + REQUIRED FLAGS Exactly one of these must be specified: @@ -42,6 +44,18 @@ REQUIRED FLAGS Project (id or number) where the mute config resides. Formatted as projects/789 or just 789. +FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. @@ -77,8 +91,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/muteconfigs/update b/gcloud/alpha/scc/muteconfigs/update index 6e88487b9..6486fb46e 100644 --- a/gcloud/alpha/scc/muteconfigs/update +++ b/gcloud/alpha/scc/muteconfigs/update @@ -1,61 +1,45 @@ NAME - gcloud alpha scc muteconfigs update - update a Cloud Security Command - Center mute config + gcloud alpha scc muteconfigs update - update a Security Command Center mute + config SYNOPSIS gcloud alpha scc muteconfigs update MUTE_CONFIG [--description=DESCRIPTION] - [--filter=FILTER] [--update-mask=UPDATE_MASK] + [--filter=FILTER] [--location=LOCATION; default="global"] + [--update-mask=UPDATE_MASK] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Update a Cloud Security Command Center mute config. + (ALPHA) Update a Security Command Center mute config. EXAMPLES - Update a mute config with ID=my-test-mute-config under organization=123 - with a filter on category that equals to XSS_SCRIPTING: + Update a mute config with ID=test-mute-config under organization=123 with a + filter on category that equals to XSS_SCRIPTING: - $ gcloud alpha scc muteconfigs update my-test-mute-config \ - --organization=organizations/123 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc muteconfigs update my-test-mute-config \ + $ gcloud alpha scc muteconfigs update test-mute-config \ --organization=123 --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc muteconfigs update \ - organizations/123/muteConfigs/my-test-mute-config \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - Update a mute config with ID=my-test-mute-config under folder=456 with a + Update a mute config with ID=test-mute-config under folder=456 with a filter on category that equals to XSS_SCRIPTING: - $ gcloud alpha scc muteconfigs update my-test-mute-config \ - --folder=folders/456 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc muteconfigs update my-test-mute-config \ + $ gcloud alpha scc muteconfigs update test-mute-config \ --folder=456 --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc muteconfigs update \ - folders/456/muteConfigs/my-test-mute-config \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - Update a mute config with ID=my-test-mute-config under project=789 with a + Update a mute config with ID=test-mute-config under project=789 with a filter on category that equals to XSS_SCRIPTING: - $ gcloud alpha scc muteconfigs update my-test-mute-config \ - --project=projects/789 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc muteconfigs update my-test-mute-config \ + $ gcloud alpha scc muteconfigs update test-mute-config \ --project=789 --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud alpha scc muteconfigs update \ - projects/789/muteConfigs/my-test-mute-config \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" + + Update a mute config with ID=test-mute-config under organization=123 + location=eu with a filter on category that equals to XSS_SCRIPTING: + + $ gcloud alpha scc muteconfigs update test-mute-config \ + --organization=123 --description="This is a test mute config" \ + --filter="category=\"XSS_SCRIPTING\"" --location=eu POSITIONAL ARGUMENTS MUTE_CONFIG @@ -69,6 +53,17 @@ FLAGS The filter string which will applied to findings muted by a mute configuration. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --update-mask=UPDATE_MASK Optional: If left unspecified (default), an update-mask is automatically created using the flags specified in the command and only @@ -97,8 +92,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/notifications/create b/gcloud/alpha/scc/notifications/create index 0f749ff12..5204e8811 100644 --- a/gcloud/alpha/scc/notifications/create +++ b/gcloud/alpha/scc/notifications/create @@ -1,16 +1,22 @@ NAME - gcloud alpha scc notifications create - create a Cloud Security Command - Center notification config + gcloud alpha scc notifications create - create a Security Command Center + notification config SYNOPSIS gcloud alpha scc notifications create NOTIFICATION_CONFIG_ID --pubsub-topic=PUBSUB_TOPIC [--description=DESCRIPTION] - [--filter=FILTER] + [--filter=FILTER] [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create a Cloud Security Command Center notification config. + (ALPHA) Create a Security Command Center notification config. + + Notification configs that are created with Security Command Center API V2 + and later include a location attribute. If a location is not specified, the + default global location is used. For example, the following Notification + config name has location=global attribute: + organizations/123/locations/global/notificationConfigs/my-config. EXAMPLES Create a notification config test-config under organization 123 for @@ -21,10 +27,6 @@ EXAMPLES --organization=123 \ --pubsub-topic=projects/test-project/topics/notification-test \ --filter="resource_name: \"a\"" - $ gcloud alpha scc notifications create \ - organizations/123/notificationConfigs/test-config \ - --pubsub-topic=projects/test-project/topics/notification-test \ - --filter="resource_name: \"a\"" Create a notification config test-config under folder 456 for findings for pubsub-topic projects/test-project/topics/notification-test with a filter @@ -33,10 +35,6 @@ EXAMPLES $ gcloud alpha scc notifications create test-config --folder=456 \ --pubsub-topic=projects/test-project/topics/notification-test \ --filter="resource_name: \"a\"" - $ gcloud alpha scc notifications create \ - folders/456/notificationConfigs/test-config \ - --pubsub-topic=projects/test-project/topics/notification-test \ - --filter="resource_name: \"a\"" Create a notification config test-config under project 789 for findings for pubsub-topic projects/test-project/topics/notification-test with a filter @@ -45,10 +43,14 @@ EXAMPLES $ gcloud alpha scc notifications create test-config --project=789 \ --pubsub-topic=projects/test-project/topics/notification-test \ --filter="resource_name: \"a\"" - $ gcloud alpha scc notifications create \ - projects/789/notificationConfigs/test-config \ + + Create a notification config test-config under organization 123 for + findings for pubsub-topic projects/test-project/topics/notification-test + with a filter on resource name and location=eu + + $ gcloud alpha scc notifications create test-config --project=789 \ --pubsub-topic=projects/test-project/topics/notification-test \ - --filter="resource_name: \"a\"" + --filter="resource_name: \"a\"" --location=eu POSITIONAL ARGUMENTS NOTIFICATION_CONFIG_ID @@ -67,6 +69,17 @@ OPTIONAL FLAGS --filter=FILTER Filter to be used for notification config. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -90,8 +103,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/notifications/delete b/gcloud/alpha/scc/notifications/delete index 5a0df7569..482c81d98 100644 --- a/gcloud/alpha/scc/notifications/delete +++ b/gcloud/alpha/scc/notifications/delete @@ -1,33 +1,48 @@ NAME - gcloud alpha scc notifications delete - delete a Cloud Security Command - Center notification config + gcloud alpha scc notifications delete - delete a Security Command Center + notification config SYNOPSIS gcloud alpha scc notifications delete NOTIFICATION_CONFIG_ID + [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete a Cloud Security Command Center notification config. + (ALPHA) Delete a Security Command Center notification config. + + Notification configs that are created with Security Command Center API V2 + and later include a location attribute. If the location attribute is + included in the resource name of a Notification configs, you must specify + it when referencing the Notification config. For example, the following + Notification configs name has location=eu: + organizations/123/locations/eu/notificationConfigs/test-config. EXAMPLES - Delete notification config 'my-config' from organization 123 + Delete notification config 'test-config' from organization 123 - $ gcloud alpha scc notifications delete my-config --organization=123 - $ gcloud alpha scc notifications delete \ - organizations/123/notificationConfigs/my-config + $ gcloud alpha scc notifications delete test-config \ + --organization=123 - Delete notification config 'my-config' from folder 456 + Delete notification config 'test-config' from folder 456 - $ gcloud alpha scc notifications delete my-config --folder=456 - $ gcloud alpha scc notifications delete \ - folders/456/notificationConfigs/my-config + $ gcloud alpha scc notifications delete test-config --folder=456 - Delete notification config 'my-config' from project 789 + Delete notification config 'test-config' from project 789 - $ gcloud alpha scc notifications delete my-config --project=789 - $ gcloud alpha scc notifications delete \ - projects/789/notificationConfigs/my-config + $ gcloud alpha scc notifications delete test-config --project=789 + + Delete notification config 'test-config' with location global from + organization 123 + + $ gcloud alpha scc notifications delete test-config \ + --organization=123 --location=global + + Delete notification config 'test-config' with location=eu from organization + 123 + + $ gcloud alpha scc notifications delete test-config \ + --organization=123 --location=eu POSITIONAL ARGUMENTS NOTIFICATION_CONFIG_ID @@ -35,6 +50,17 @@ POSITIONAL ARGUMENTS "organizations/123/notificationConfigs/456" or just "456". FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -58,8 +84,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/notifications/describe b/gcloud/alpha/scc/notifications/describe index 54b64f9fe..7989aaa7c 100644 --- a/gcloud/alpha/scc/notifications/describe +++ b/gcloud/alpha/scc/notifications/describe @@ -1,36 +1,42 @@ NAME - gcloud alpha scc notifications describe - describe a Cloud Security Command + gcloud alpha scc notifications describe - describe a Security Command Center notification config SYNOPSIS gcloud alpha scc notifications describe NOTIFICATION_CONFIG_ID + [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe a Cloud Security Command Center notification config. + (ALPHA) Describe a Security Command Center notification config. + + Notification configs that are created with Security Command Center API V2 + and later include a location attribute. If the location attribute is + included in the resource name of a Notification configs, you must specify + it when referencing the Notification config. For example, the following + Notification configs name has location=eu: + organizations/123/locations/eu/notificationConfigs/test-config. EXAMPLES - Describe notification config 'my-config' from organization 123 + Describe notification config 'test-config' from organization 123 - $ gcloud alpha scc notifications describe notifications describe \ - my-config --organization=123 - $ gcloud alpha scc notifications describe notifications describe \ - organizations/123/notificationConfigs/my-config + $ gcloud alpha scc notifications describe test-config \ + --organization=123 - Describe notification config 'my-config' from folder 456 + Describe notification config 'test-config' from folder 456 - $ gcloud alpha scc notifications describe notifications describe \ - my-config --folder=456 - $ gcloud alpha scc notifications describe notifications describe \ - folders/456/notificationConfigs/my-config + $ gcloud alpha scc notifications describe test-config --folder=456 - Describe notification config 'my-config' from project 789 + Describe notification config 'test-config' from project 789 - $ gcloud alpha scc notifications describe notifications describe \ - my-config --project=789 - $ gcloud alpha scc notifications describe notifications describe \ - projects/789/notificationConfigs/my-config + $ gcloud alpha scc notifications describe test-config --project=789 + + Describe notification config 'test-config' from organization 123 and + location=global + + $ gcloud alpha scc notifications describe test-config \ + --organization=123 --location=global POSITIONAL ARGUMENTS NOTIFICATION_CONFIG_ID @@ -38,6 +44,17 @@ POSITIONAL ARGUMENTS "organizations/123/notificationConfigs/456" or just "456". FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -61,8 +78,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/notifications/help b/gcloud/alpha/scc/notifications/help index 7f6bda737..89eea0188 100644 --- a/gcloud/alpha/scc/notifications/help +++ b/gcloud/alpha/scc/notifications/help @@ -17,19 +17,19 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create a Cloud Security Command Center notification config. + (ALPHA) Create a Security Command Center notification config. delete - (ALPHA) Delete a Cloud Security Command Center notification config. + (ALPHA) Delete a Security Command Center notification config. describe - (ALPHA) Describe a Cloud Security Command Center notification config. + (ALPHA) Describe a Security Command Center notification config. list - (ALPHA) List Cloud Security Command Center notification configs. + (ALPHA) List Security Command Center notification configs. update - (ALPHA) Update a Cloud Security Command Center notification config. + (ALPHA) Update a Security Command Center notification config. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/notifications/list b/gcloud/alpha/scc/notifications/list index 62e9caa5e..5a329380d 100644 --- a/gcloud/alpha/scc/notifications/list +++ b/gcloud/alpha/scc/notifications/list @@ -1,14 +1,19 @@ NAME - gcloud alpha scc notifications list - list Cloud Security Command Center + gcloud alpha scc notifications list - list Security Command Center notification configs SYNOPSIS - gcloud alpha scc notifications list [PARENT] [--filter=EXPRESSION] + gcloud alpha scc notifications list [PARENT] + [--location=LOCATION; default="global"] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Cloud Security Command Center notification configs. + (ALPHA) List Security Command Center notification configs. + + Notification Configs that are created with Security Command Center API V2 + and later include a `location` attribute. Include the `--location` flag to + list Notification Configs with `location` attribute other than `global`. EXAMPLES List notification configs from organization 123 @@ -24,6 +29,12 @@ EXAMPLES $ gcloud alpha scc notifications list projects/789 + List notification configs from organization 123 and location=eu + + $ gcloud alpha scc notifications list 123 --location=eu + $ gcloud alpha scc notifications list organizations/123 \ + --location=locations/eu + POSITIONAL ARGUMENTS Parent resource - parent organization, folder, or project in the Google Cloud resource hierarchy to be used for the gcloud scc command. Specify @@ -38,6 +49,18 @@ POSITIONAL ARGUMENTS ▸ Set the parent property in configuration using gcloud config set scc/parent if it is not specified in command line. +FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. @@ -73,8 +96,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/notifications/update b/gcloud/alpha/scc/notifications/update index 29a162aa0..670cb0507 100644 --- a/gcloud/alpha/scc/notifications/update +++ b/gcloud/alpha/scc/notifications/update @@ -1,81 +1,69 @@ NAME - gcloud alpha scc notifications update - update a Cloud Security Command - Center notification config + gcloud alpha scc notifications update - update a Security Command Center + notification config SYNOPSIS gcloud alpha scc notifications update NOTIFICATION_CONFIG_ID [--description=DESCRIPTION] [--filter=FILTER] - [--pubsub-topic=PUBSUB_TOPIC] + [--location=LOCATION; default="global"] [--pubsub-topic=PUBSUB_TOPIC] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Update a Cloud Security Command Center notification config. + (ALPHA) Update a Security Command Center notification config. + + Notification configs that are created with Security Command Center API V2 + and later include a location attribute. If the location attribute is + included in the resource name of a Notification configs, you must specify + it when referencing the Notification config. For example, the following + Notification configs name has location=eu: + organizations/123/locations/eu/notificationConfigs/test-config. EXAMPLES - Update all mutable fields under an organization parent my-config + Update all mutable fields under an organization parent test-config (description + pubsub topic + filter): $ gcloud alpha scc notifications update scc notifications update \ - my-config --organization=123 --description="New description" \ + test-config --organization=123 --description="New description" \ --pubsub-topic="projects/22222/topics/newtopic" - $ gcloud alpha scc notifications update scc notifications update \ - organizations/123/notificationConfigs/my-config \ - --description="New description" \ - --pubsub-topic="projects/22222/topics/newtopic" - - Update all mutable fields under a folder parent my-config (description + + Update all mutable fields under a folder parent test-config (description + pubsub topic + filter): $ gcloud alpha scc notifications update scc notifications update \ - my-config --folder=456 --description="New description" \ + test-config --folder=456 --description="New description" \ --pubsub-topic="projects/22222/topics/newtopic" - $ gcloud alpha scc notifications update scc notifications update \ - folders/456/notificationConfigs/my-config \ - --description="New description" \ - --pubsub-topic="projects/22222/topics/newtopic" - - Update all mutable fields under a project parent my-config (description + + Update all mutable fields under a project parent test-config (description + pubsub topic + filter): $ gcloud alpha scc notifications update scc notifications update \ - my-config --project=789 --description="New description" \ + test-config --project=789 --description="New description" \ --pubsub-topic="projects/22222/topics/newtopic" - $ gcloud alpha scc notifications update scc notifications update \ - projects/789/notificationConfigs/my-config \ - --description="New description" \ - --pubsub-topic="projects/22222/topics/newtopic" + Update test-config's description - Update my-config's description - - $ gcloud alpha scc notifications update my-config \ + $ gcloud alpha scc notifications update test-config \ --organization=123 --description="New description" - $ gcloud alpha scc notifications update \ - organizations/123/notificationConfigs/my-config \ - --description="New description" + Update test-config's pubsub-topic - Update my-config's pubsub-topic - - $ gcloud alpha scc notifications update my-config \ + $ gcloud alpha scc notifications update test-config \ --organization=123 \ --pubsub-topic="projects/22222/topics/newtopic" - $ gcloud alpha scc notifications update \ - organizations/123/notificationConfigs/my-config \ - --pubsub-topic="projects/22222/topics/newtopic" + Update test-config's filter - Update my-config's filter - - $ gcloud alpha scc notifications update my-config \ + $ gcloud alpha scc notifications update test-config \ --organization=123 --filter='state = \"ACTIVE\"' - $ gcloud alpha scc notifications update \ - organizations/123/notificationConfigs/my-config \ - --filter='state = \"ACTIVE\"' + Update all mutable fields for test-config with location=global under an + organization parent (description + pubsub topic + filter): + + $ gcloud alpha scc notifications update scc notifications update \ + test-config --organization=123 --description="New description" \ + --pubsub-topic="projects/22222/topics/newtopic" \ + --location=global POSITIONAL ARGUMENTS NOTIFICATION_CONFIG_ID @@ -90,6 +78,17 @@ FLAGS The filter string which will applied to events of findings of a notification configuration. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --pubsub-topic=PUBSUB_TOPIC The Pub/Sub topic which will receive notifications. Its format is "projects/[project_id]/topics/[topic]". @@ -117,8 +116,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/scc/postures/list b/gcloud/alpha/scc/postures/list index 642d74b08..9733566d5 100644 --- a/gcloud/alpha/scc/postures/list +++ b/gcloud/alpha/scc/postures/list @@ -8,18 +8,11 @@ SYNOPSIS DESCRIPTION (ALPHA) Lists all Cloud Security Command Center (SCC) postures for an - organization. - - By default, postures created in global location are returned. + organization. For a posture with multiple revisions, only the latest + updated revision of the posture is returned in the output. EXAMPLES - List all postures in organization 123. If location is omitted, this returns - postures from location 'global'. For a posture with multiple revisions, - only the latest updated revision of the posture is returned in the output. - - $ gcloud alpha scc postures list organizations/123 - - List all postures in organization 123, location global + List all postures in organization 123, location global. $ gcloud alpha scc postures list organizations/123/locations/global diff --git a/gcloud/alpha/spanner/backups/copy b/gcloud/alpha/spanner/backups/copy index d7e1396b1..475987da1 100644 --- a/gcloud/alpha/spanner/backups/copy +++ b/gcloud/alpha/spanner/backups/copy @@ -129,42 +129,46 @@ OPTIONAL FLAGS Use the default encryption configuration if one exists. otherwise use the same encryption configuration as the source backup. - Key resource - Cloud KMS key to be used to copy the Cloud Spanner backup. - The arguments in this group can be used to specify the attributes of this - resource. + KMS key name group - --kms-key=KMS_KEY - ID of the key or fully qualified identifier for the key. + At most one of these can be specified: - To set the kms-key attribute: - ▸ provide the argument --kms-key on the command line. + Key resource - Cloud KMS key to be used to copy the Cloud Spanner + backup. The arguments in this group can be used to specify the + attributes of this resource. - This flag argument must be specified if any of the other arguments in - this group are specified. + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. - --kms-keyring=KMS_KEYRING - KMS keyring id of the key. + To set the kms-key attribute: + ▫ provide the argument --kms-key on the command line. - To set the kms-keyring attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-keyring on the command line. + This flag argument must be specified if any of the other arguments + in this group are specified. - --kms-location=KMS_LOCATION - Cloud location for the key. + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. - To set the kms-location attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-location on the command line. + To set the kms-keyring attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-keyring on the command line. - --kms-project=KMS_PROJECT - Cloud project id for the key. + --kms-location=KMS_LOCATION + Cloud location for the key. - To set the kms-project attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-project on the command line. + To set the kms-location attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. + + To set the kms-project attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-project on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/spanner/backups/create b/gcloud/alpha/spanner/backups/create index 4472adb26..7207c4437 100644 --- a/gcloud/alpha/spanner/backups/create +++ b/gcloud/alpha/spanner/backups/create @@ -98,42 +98,46 @@ OPTIONAL FLAGS use-database-encryption Use the same encryption configuration as the database. - Key resource - Cloud KMS key to be used to create the Cloud Spanner - backup. The arguments in this group can be used to specify the attributes - of this resource. + KMS key name group - --kms-key=KMS_KEY - ID of the key or fully qualified identifier for the key. + At most one of these can be specified: - To set the kms-key attribute: - ▸ provide the argument --kms-key on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner + backup. The arguments in this group can be used to specify the + attributes of this resource. - This flag argument must be specified if any of the other arguments in - this group are specified. + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. - --kms-keyring=KMS_KEYRING - KMS keyring id of the key. + To set the kms-key attribute: + ▫ provide the argument --kms-key on the command line. - To set the kms-keyring attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-keyring on the command line. + This flag argument must be specified if any of the other arguments + in this group are specified. - --kms-location=KMS_LOCATION - Cloud location for the key. + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. - To set the kms-location attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-location on the command line. + To set the kms-keyring attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-keyring on the command line. - --kms-project=KMS_PROJECT - Cloud project id for the key. + --kms-location=KMS_LOCATION + Cloud location for the key. - To set the kms-project attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-project on the command line. + To set the kms-location attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. + + To set the kms-project attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-project on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/spanner/databases/create b/gcloud/alpha/spanner/databases/create index c9375d52f..5f59fc2df 100644 --- a/gcloud/alpha/spanner/databases/create +++ b/gcloud/alpha/spanner/databases/create @@ -87,42 +87,46 @@ FLAGS --ddl_file is set, --ddl is ignored. One line comments starting with -- are ignored. - Key resource - Cloud KMS key to be used to create the Cloud Spanner - database. The arguments in this group can be used to specify the - attributes of this resource. + KMS key name group - --kms-key=KMS_KEY - ID of the key or fully qualified identifier for the key. + At most one of these can be specified: - To set the kms-key attribute: - ▸ provide the argument --kms-key on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner + database. The arguments in this group can be used to specify the + attributes of this resource. - This flag argument must be specified if any of the other arguments in - this group are specified. + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. - --kms-keyring=KMS_KEYRING - KMS keyring id of the key. + To set the kms-key attribute: + ▫ provide the argument --kms-key on the command line. - To set the kms-keyring attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-keyring on the command line. + This flag argument must be specified if any of the other arguments + in this group are specified. - --kms-location=KMS_LOCATION - Cloud location for the key. + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. - To set the kms-location attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-location on the command line. + To set the kms-keyring attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-keyring on the command line. - --kms-project=KMS_PROJECT - Cloud project id for the key. + --kms-location=KMS_LOCATION + Cloud location for the key. - To set the kms-project attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-project on the command line. + To set the kms-location attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. + + To set the kms-project attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-project on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/spanner/databases/restore b/gcloud/alpha/spanner/databases/restore index abdc8b2ca..a939a074d 100644 --- a/gcloud/alpha/spanner/databases/restore +++ b/gcloud/alpha/spanner/databases/restore @@ -110,42 +110,46 @@ OPTIONAL FLAGS Use the default encryption configuration if one exists, otherwise use the same encryption configuration as the backup. - Key resource - Cloud KMS key to be used to restore the Cloud Spanner - database. The arguments in this group can be used to specify the - attributes of this resource. + KMS key name group - --kms-key=KMS_KEY - ID of the key or fully qualified identifier for the key. + At most one of these can be specified: - To set the kms-key attribute: - ▸ provide the argument --kms-key on the command line. + Key resource - Cloud KMS key to be used to restore the Cloud Spanner + database. The arguments in this group can be used to specify the + attributes of this resource. - This flag argument must be specified if any of the other arguments in - this group are specified. + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. - --kms-keyring=KMS_KEYRING - KMS keyring id of the key. + To set the kms-key attribute: + ▫ provide the argument --kms-key on the command line. - To set the kms-keyring attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-keyring on the command line. + This flag argument must be specified if any of the other arguments + in this group are specified. - --kms-location=KMS_LOCATION - Cloud location for the key. + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. - To set the kms-location attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-location on the command line. + To set the kms-keyring attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-keyring on the command line. - --kms-project=KMS_PROJECT - Cloud project id for the key. + --kms-location=KMS_LOCATION + Cloud location for the key. - To set the kms-project attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-project on the command line. + To set the kms-location attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. + + To set the kms-project attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-project on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/sql/backups/delete b/gcloud/alpha/sql/backups/delete index 7059f1fdc..1d8e5fa57 100644 --- a/gcloud/alpha/sql/backups/delete +++ b/gcloud/alpha/sql/backups/delete @@ -2,26 +2,25 @@ NAME gcloud alpha sql backups delete - delete a backup of a Cloud SQL instance SYNOPSIS - gcloud alpha sql backups delete ID --instance=INSTANCE, -i INSTANCE - [--async] [GCLOUD_WIDE_FLAG ...] + gcloud alpha sql backups delete ID [--async] + [--instance=INSTANCE, -i INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Delete a backup of a Cloud SQL instance. POSITIONAL ARGUMENTS ID - The ID of the backup run. You can find the ID by running $ gcloud sql - backups list -i {instance}. + The ID of the backup run. To find the ID, run the following command: $ + gcloud sql backups list -i {instance}. -REQUIRED FLAGS - --instance=INSTANCE, -i INSTANCE - Cloud SQL instance ID. - -OPTIONAL FLAGS +FLAGS --async Return immediately, without waiting for the operation in progress to complete. + --instance=INSTANCE, -i INSTANCE + Cloud SQL instance ID. + 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/builds/connections/create/bitbucket-cloud b/gcloud/beta/builds/connections/create/bitbucket-cloud deleted file mode 100644 index a5c141590..000000000 --- a/gcloud/beta/builds/connections/create/bitbucket-cloud +++ /dev/null @@ -1,109 +0,0 @@ -NAME - gcloud beta builds connections create bitbucket-cloud - create a Cloud - Build Connection for Bitbucket Cloud - -SYNOPSIS - gcloud beta builds connections create bitbucket-cloud - (CONNECTION : --region=REGION) - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION - --workspace=WORKSPACE [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Create a Cloud Build Connection for Bitbucket Cloud. - - A Bitbucket Cloud Connection can be created by using a - repository/project/workspace access token with - repository_read,repository_admin, pullrequest_read, webhook scope - permission and a repository/project/workspace access token with - repository_read scope permission. - -EXAMPLES - To create a Bitbucket Cloud connection, provide all the required - parameters: - - $ gcloud beta builds connections create bitbucket-cloud \ - my-bitbucket-conn --project=myproj --region=us-central1 \ - --workspace=my-workspace \ - --read-authorizer-token-secret-version=projects/myproj/secrets/\ - read-pat/versions/1 \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 \ - --webhook-secret-secret-version=projects/myproj/secrets/\ - whsecret/versions/1 - -POSITIONAL ARGUMENTS - Connection resource - Connection 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 connection on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CONNECTION - ID of the connection or fully qualified identifier for the - connection. - - To set the connection attribute: - ▸ provide the argument connection on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The Google Cloud region. - - To set the region attribute: - ▸ provide the argument connection on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -REQUIRED FLAGS - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the repository_read,repository_admin, - pullrequest_read, webhook repository/project/workspace access token. - - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the repository_read repository/project/workspace - access token. - - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION - Secret containing the webhook secret string for validating webhook - events sent by Bitbucket Cloud. - - --workspace=WORKSPACE - Workspace of the Bitbucket Cloud instance. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the cloudbuild/v2 API. The full documentation for this - API can be found at: https://cloud.google.com/cloud-build/docs/ - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud builds connections create bitbucket-cloud - - $ gcloud alpha builds connections create bitbucket-cloud - diff --git a/gcloud/beta/builds/connections/create/bitbucket-data-center b/gcloud/beta/builds/connections/create/bitbucket-data-center deleted file mode 100644 index 9033c4083..000000000 --- a/gcloud/beta/builds/connections/create/bitbucket-data-center +++ /dev/null @@ -1,140 +0,0 @@ -NAME - gcloud beta builds connections create bitbucket-data-center - create a - Cloud Build Connection for Bitbucket Data Center - -SYNOPSIS - gcloud beta builds connections create bitbucket-data-center - (CONNECTION : --region=REGION) - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION [--async] - [--host-uri=HOST_URI] - [--service-directory-service=SERVICE_DIRECTORY_SERVICE - : --ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Create a Cloud Build Connection for Bitbucket Data Center. - - A Bitbucket Data Center Connection can be created by using a personal - access token with REPO_ADMIN scope permission. A REPO_READ scoped personal - access token will also be required. - - If the Bitbucket Data Center can only be accessed within a VPC, a Service - Directory service resource can be provided for connecting to it. - -EXAMPLES - To create a Bitbucket Data Center connection, provide all the required - parameters: - - $ gcloud beta builds connections create bitbucket-data-center \ - my-bitbucket-conn --project=myproj --region=us-central1 \ - --host-uri=https://bitbucket-server.net \ - --read-authorizer-token-secret-version=projects/myproj/secrets/\ - read-pat/versions/1 \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 \ - --webhook-secret-secret-version=projects/myproj/secrets/\ - whsecret/versions/1 - - To create a Bitbucket Data Center connection for a private Bitbucket Data - Center server. Provide the service-directory-service and ssl-ca-file as - well: - - $ gcloud beta builds connections create bitbucket-data-center \ - my-private-bitbucket-conn \ - --host-uri=https://my.private-bitbucket-server.net \ - --project=myproj --region=us-central1 \ - --service-directory-service=projects/myproj/namespaces/x/\ - services/mysds --ssl-ca-file=mycertificate.crt \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 \ - --read-authorizer-token-secret-version=projects/myproj/secrets/\ - read-pat/versions/1 \ - --webhook-secret-secret-version=projects/myproj/secrets/\ - whsecret/versions/1 - -POSITIONAL ARGUMENTS - Connection resource - Connection 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 connection on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CONNECTION - ID of the connection or fully qualified identifier for the - connection. - - To set the connection attribute: - ▸ provide the argument connection on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The Google Cloud region. - - To set the region attribute: - ▸ provide the argument connection on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -REQUIRED FLAGS - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the REPO_ADMIN personal access token. - - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the REPO_READ personal access token. - - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION - Secret containing the webhook secret string for validating webhook - events sent by Bitbucket Data Center. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --host-uri=HOST_URI - URI of the Bitbucket Data Center instance. - - Group of arguments for configuring access through Service Directory. - - --service-directory-service=SERVICE_DIRECTORY_SERVICE - Service Directory service resource to use for accessing the Bitbucket - Data Center. Necessary only if the server has no public access from - the internet. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --ssl-ca-file=SSL_CA_FILE - File containing the SSL_CA to be used. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 cloudbuild/v2 API. The full documentation for this - API can be found at: https://cloud.google.com/cloud-build/docs/ - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud builds connections create bitbucket-data-center - - $ gcloud alpha builds connections create bitbucket-data-center - diff --git a/gcloud/beta/builds/connections/create/help b/gcloud/beta/builds/connections/create/help index 6702b24dc..11317f047 100644 --- a/gcloud/beta/builds/connections/create/help +++ b/gcloud/beta/builds/connections/create/help @@ -16,12 +16,6 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - bitbucket-cloud - (BETA) Create a Cloud Build Connection for Bitbucket Cloud. - - bitbucket-data-center - (BETA) Create a Cloud Build Connection for Bitbucket Data Center. - github (BETA) Create a Cloud Build Connection of type GitHub. diff --git a/gcloud/beta/builds/connections/update/bitbucket-cloud b/gcloud/beta/builds/connections/update/bitbucket-cloud deleted file mode 100644 index 8950430b5..000000000 --- a/gcloud/beta/builds/connections/update/bitbucket-cloud +++ /dev/null @@ -1,104 +0,0 @@ -NAME - gcloud beta builds connections update bitbucket-cloud - update a Cloud - Build Connection of type Bitbucket Cloud - -SYNOPSIS - gcloud beta builds connections update bitbucket-cloud - (CONNECTION : --region=REGION) [--async] - [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] - [--read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION] - [--webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION] - [--workspace=WORKSPACE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Update a Cloud Build Connection of type Bitbucket Cloud. - -EXAMPLES - To update the workspace, provide the connection name and the workspace - name: - - $ gcloud beta builds connections update bitbucket-cloud \ - my-bbc-conn --region=us-west1 --workspace=my-workspace - - To update the authorization token, provide the connection name and the new - authorization token secret version. - - $ gcloud beta builds connections update bitbucket-cloud \ - my-bbc-conn --region=us-west1 \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 - -POSITIONAL ARGUMENTS - Connection resource - Connection 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 connection on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CONNECTION - ID of the connection or fully qualified identifier for the - connection. - - To set the connection attribute: - ▸ provide the argument connection on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The Google Cloud region. - - To set the region attribute: - ▸ provide the argument connection on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the repository_read,repository_admin, - pullrequest_read, webhook access token. It can be a repository, project - or workspace access token. - - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the repository_read access token. It can be a - repository, project or workspace access token. - - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION - Secret containing the webhook secret string for validating webhook - events sent by Bitbucket Cloud. - - --workspace=WORKSPACE - Workspace of the Bitbucket Cloud 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. - -API REFERENCE - This command uses the cloudbuild/v2 API. The full documentation for this - API can be found at: https://cloud.google.com/cloud-build/docs/ - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud builds connections update bitbucket-cloud - - $ gcloud alpha builds connections update bitbucket-cloud - diff --git a/gcloud/beta/builds/connections/update/bitbucket-data-center b/gcloud/beta/builds/connections/update/bitbucket-data-center deleted file mode 100644 index 0266920a0..000000000 --- a/gcloud/beta/builds/connections/update/bitbucket-data-center +++ /dev/null @@ -1,105 +0,0 @@ -NAME - gcloud beta builds connections update bitbucket-data-center - update a - Cloud Build Connection of type Bitbucket Data Center - -SYNOPSIS - gcloud beta builds connections update bitbucket-data-center - (CONNECTION : --region=REGION) [--async] - [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] - [--host-uri=HOST_URI] - [--read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION] - [--service-directory-service=SERVICE_DIRECTORY_SERVICE] - [--ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Update a Cloud Build Connection of type Bitbucket Data Center. - -EXAMPLES - To update the ssl_ca, provide the connection name and the ssl_ca file: - - $ gcloud beta builds connections update bitbucket-data-center \ - my-gle-conn --region=us-west1 --ssl-ca-file=mycertificate.crt - - To update the authorization token, provide the connection name and the new - authorization token secret version name. - - $ gcloud beta builds connections update bitbucket-data-center \ - my-gle-conn --region=us-west1 \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 - -POSITIONAL ARGUMENTS - Connection resource - Connection 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 connection on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CONNECTION - ID of the connection or fully qualified identifier for the - connection. - - To set the connection attribute: - ▸ provide the argument connection on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The Google Cloud region. - - To set the region attribute: - ▸ provide the argument connection on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the REPO_ADMIN personal access token. - - --host-uri=HOST_URI - URI of the Bitbucket Data Center instance. - - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the REPO_READ personal access token. - - --service-directory-service=SERVICE_DIRECTORY_SERVICE - Service Directory service resource to use for accessing the Bitbucket - Data Center. Necessary only if the server has no public access from the - internet. - - --ssl-ca-file=SSL_CA_FILE - File containing the SSL_CA to be used. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 cloudbuild/v2 API. The full documentation for this - API can be found at: https://cloud.google.com/cloud-build/docs/ - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud builds connections update bitbucket-data-center - - $ gcloud alpha builds connections update bitbucket-data-center - diff --git a/gcloud/beta/builds/connections/update/help b/gcloud/beta/builds/connections/update/help index 3fbf7f023..26a5da5ef 100644 --- a/gcloud/beta/builds/connections/update/help +++ b/gcloud/beta/builds/connections/update/help @@ -16,12 +16,6 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - bitbucket-cloud - (BETA) Update a Cloud Build Connection of type Bitbucket Cloud. - - bitbucket-data-center - (BETA) Update a Cloud Build Connection of type Bitbucket Data Center. - github (BETA) Update a Cloud Build Connection of type GitHub. diff --git a/gcloud/beta/builds/triggers/create/bitbucket-cloud b/gcloud/beta/builds/triggers/create/bitbucket-cloud deleted file mode 100644 index f73756478..000000000 --- a/gcloud/beta/builds/triggers/create/bitbucket-cloud +++ /dev/null @@ -1,223 +0,0 @@ -NAME - gcloud beta builds triggers create bitbucket-cloud - create a build trigger - for a 2nd-gen Bitbucket Cloud repository - -SYNOPSIS - gcloud beta builds triggers create bitbucket-cloud - (--trigger-config=PATH | [(--branch-pattern=REGEX | --tag-pattern=REGEX - | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; - default="COMMENTS_ENABLED"]) (--build-config=PATH - | --inline-config=PATH - | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE - : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) - : --description=DESCRIPTION --ignored-files=[GLOB,...] - --included-files=[GLOB,...] --name=NAME --region=REGION - --repository=REPOSITORY --[no-]require-approval - --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Create a build trigger for a 2nd-gen Bitbucket Cloud repository. - -EXAMPLES - To create a push trigger with a 2nd-gen repository for all branches: - - $ gcloud beta builds triggers create bitbucket-cloud \ - --name="my-trigger" \ - --service-account="projects/my-project/serviceAccounts/my-byosa@\ - my-project.iam.gserviceaccount.com" \ - --repository="projects/1234/locations/us-central1/connections/my\ - conn/repositories/myrepo" --branch-pattern=".*" \ - --build-config="cloudbuild.yaml" --region=us-central1 - - To create a pull request trigger with a 2nd-gen repository for main: - - $ gcloud beta builds triggers create bitbucket-cloud \ - --name="my-trigger" \ - --service-account="projects/my-project/serviceAccounts/my-byosa@\ - my-project.iam.gserviceaccount.com" \ - --repository="projects/1234/locations/us-central1/connections/my\ - conn/repositories/myrepo" --build-config="cloudbuild.yaml" \ - --pull-request-pattern="^main$" --region=us-central1 - -REQUIRED FLAGS - Exactly one of these must be specified: - - --trigger-config=PATH - Path to Build Trigger config file (JSON or YAML format). For more - details, see - https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger - - Flag based trigger configuration - - --description=DESCRIPTION - Build trigger description. - - --ignored-files=[GLOB,...] - Glob filter. Changes only affecting ignored files won't trigger - builds. - - --included-files=[GLOB,...] - Glob filter. Changes affecting at least one included file will - trigger builds. - - --name=NAME - Build trigger name. - - --region=REGION - The region of the Cloud Build Service to use. Must be set to a - supported region name (e.g. us-central1). If unset, builds/region, - which is the default region to use when working with Cloud Build - resources, is used. If builds/region is unset, region is set to - global. Note: Region must be specified in 2nd gen repo; global is - not supported. - - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - - --[no-]require-approval - Require manual approval for triggered builds. Use - --require-approval to enable and --no-require-approval to disable. - - --service-account=SERVICE_ACCOUNT - The service account used for all user-controlled operations - including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and - CancelBuild. If no service account is set, then the standard Cloud - Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is - used instead. Format: - projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - - --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. For - example: - - $ gcloud beta builds triggers create bitbucket-cloud ... \ - --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 - - This will result in a build where every occurrence of - ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and - similarly for ${_NUM_CANDIES} and "10". - - Substitutions can be applied to user-defined variables (starting - with an underscore) and to the following built-in variables: - REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, - SHORT_SHA. - - For more details, see: - https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values - - Exactly one of these must be specified: - - --branch-pattern=REGEX - A regular expression specifying which git branches to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --branch-pattern=foo will match - "foo", "foobar", and "barfoo". Events on a branch that does not - match will be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - --tag-pattern=REGEX - A regular expression specifying which git tags to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --tag-pattern=foo will match "foo", - "foobar", and "barfoo". Events on a tag that does not match will - be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - Pull Request settings - - --pull-request-pattern=REGEX - Regular expression specifying which base git branch to match - for pull request events. - - This pattern is used as a regex search for the base branch (the - branch you are trying to merge into) for pull request updates. - For example, --pull-request-pattern=foo will match "foo", - "foobar", and "barfoo". - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" - Require a repository collaborator or owner to comment '/gcbrun' - on a pull request before running the build. COMMENT_CONTROL - must be one of: - - COMMENTS_DISABLED - Do not require comments on Pull Requests before builds are - triggered. - COMMENTS_ENABLED - Enforce that repository owners or collaborators must - comment on Pull Requests before builds are triggered. - COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY - Enforce that repository owners or collaborators must - comment on external contributors' Pull Requests before - builds are triggered. - - Exactly one of these must be specified: - - --build-config=PATH - Path to a YAML or JSON file containing the build configuration in - the repository. - - For more details, see: - https://cloud.google.com/cloud-build/docs/build-config - - --inline-config=PATH - Local path to a YAML or JSON file containing a build - configuration. - - Dockerfile build configuration flags - - --dockerfile=DOCKERFILE - Path of Dockerfile to use for builds in the repository. - - If specified, a build config will be generated to run docker - build using the specified file. - - The filename is relative to the Dockerfile directory. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-image=DOCKERFILE_IMAGE - Docker image name to build. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-dir=DOCKERFILE_DIR; default="/" - Location of the directory containing the Dockerfile in the - repository. - - The directory will also be used as the Docker build context. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud builds triggers create bitbucket-cloud - - $ gcloud alpha builds triggers create bitbucket-cloud - diff --git a/gcloud/beta/builds/triggers/create/bitbucket-data-center b/gcloud/beta/builds/triggers/create/bitbucket-data-center deleted file mode 100644 index 98dfbc81c..000000000 --- a/gcloud/beta/builds/triggers/create/bitbucket-data-center +++ /dev/null @@ -1,224 +0,0 @@ -NAME - gcloud beta builds triggers create bitbucket-data-center - create a build - trigger for a 2nd-gen Bitbucket Data Center repository - -SYNOPSIS - gcloud beta builds triggers create bitbucket-data-center - (--trigger-config=PATH | [(--branch-pattern=REGEX | --tag-pattern=REGEX - | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; - default="COMMENTS_ENABLED"]) (--build-config=PATH - | --inline-config=PATH - | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE - : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) - : --description=DESCRIPTION --ignored-files=[GLOB,...] - --included-files=[GLOB,...] --name=NAME --region=REGION - --repository=REPOSITORY --[no-]require-approval - --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Create a build trigger for a 2nd-gen Bitbucket Data Center - repository. - -EXAMPLES - To create a push trigger with a 2nd-gen repository for all branches: - - $ gcloud beta builds triggers create bitbucket-data-center \ - --name="my-trigger" \ - --service-account="projects/my-project/serviceAccounts/my-byosa@\ - my-project.iam.gserviceaccount.com" \ - --repository="projects/1234/locations/us-central1/connections/my\ - conn/repositories/myrepo" --branch-pattern=".*" \ - --build-config="cloudbuild.yaml" --region=us-central1 - - To create a pull request trigger with a 2nd-gen repository for main: - - $ gcloud beta builds triggers create bitbucket-data-center \ - --name="my-trigger" \ - --service-account="projects/my-project/serviceAccounts/my-byosa@\ - my-project.iam.gserviceaccount.com" \ - --repository="projects/1234/locations/us-central1/connections/my\ - conn/repositories/myrepo" --build-config="cloudbuild.yaml" \ - --pull-request-pattern="^main$" --region=us-central1 - -REQUIRED FLAGS - Exactly one of these must be specified: - - --trigger-config=PATH - Path to Build Trigger config file (JSON or YAML format). For more - details, see - https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger - - Flag based trigger configuration - - --description=DESCRIPTION - Build trigger description. - - --ignored-files=[GLOB,...] - Glob filter. Changes only affecting ignored files won't trigger - builds. - - --included-files=[GLOB,...] - Glob filter. Changes affecting at least one included file will - trigger builds. - - --name=NAME - Build trigger name. - - --region=REGION - The region of the Cloud Build Service to use. Must be set to a - supported region name (e.g. us-central1). If unset, builds/region, - which is the default region to use when working with Cloud Build - resources, is used. If builds/region is unset, region is set to - global. Note: Region must be specified in 2nd gen repo; global is - not supported. - - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - - --[no-]require-approval - Require manual approval for triggered builds. Use - --require-approval to enable and --no-require-approval to disable. - - --service-account=SERVICE_ACCOUNT - The service account used for all user-controlled operations - including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and - CancelBuild. If no service account is set, then the standard Cloud - Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is - used instead. Format: - projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - - --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. For - example: - - $ gcloud beta builds triggers create bitbucket-data-center ... \ - --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 - - This will result in a build where every occurrence of - ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and - similarly for ${_NUM_CANDIES} and "10". - - Substitutions can be applied to user-defined variables (starting - with an underscore) and to the following built-in variables: - REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, - SHORT_SHA. - - For more details, see: - https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values - - Exactly one of these must be specified: - - --branch-pattern=REGEX - A regular expression specifying which git branches to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --branch-pattern=foo will match - "foo", "foobar", and "barfoo". Events on a branch that does not - match will be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - --tag-pattern=REGEX - A regular expression specifying which git tags to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --tag-pattern=foo will match "foo", - "foobar", and "barfoo". Events on a tag that does not match will - be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - Pull Request settings - - --pull-request-pattern=REGEX - Regular expression specifying which base git branch to match - for pull request events. - - This pattern is used as a regex search for the base branch (the - branch you are trying to merge into) for pull request updates. - For example, --pull-request-pattern=foo will match "foo", - "foobar", and "barfoo". - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" - Require a repository collaborator or owner to comment '/gcbrun' - on a pull request before running the build. COMMENT_CONTROL - must be one of: - - COMMENTS_DISABLED - Do not require comments on Pull Requests before builds are - triggered. - COMMENTS_ENABLED - Enforce that repository owners or collaborators must - comment on Pull Requests before builds are triggered. - COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY - Enforce that repository owners or collaborators must - comment on external contributors' Pull Requests before - builds are triggered. - - Exactly one of these must be specified: - - --build-config=PATH - Path to a YAML or JSON file containing the build configuration in - the repository. - - For more details, see: - https://cloud.google.com/cloud-build/docs/build-config - - --inline-config=PATH - Local path to a YAML or JSON file containing a build - configuration. - - Dockerfile build configuration flags - - --dockerfile=DOCKERFILE - Path of Dockerfile to use for builds in the repository. - - If specified, a build config will be generated to run docker - build using the specified file. - - The filename is relative to the Dockerfile directory. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-image=DOCKERFILE_IMAGE - Docker image name to build. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-dir=DOCKERFILE_DIR; default="/" - Location of the directory containing the Dockerfile in the - repository. - - The directory will also be used as the Docker build context. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud builds triggers create bitbucket-data-center - - $ gcloud alpha builds triggers create bitbucket-data-center - diff --git a/gcloud/beta/builds/triggers/create/help b/gcloud/beta/builds/triggers/create/help index 57db58fa3..cb1b5ebef 100644 --- a/gcloud/beta/builds/triggers/create/help +++ b/gcloud/beta/builds/triggers/create/help @@ -16,13 +16,6 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - bitbucket-cloud - (BETA) Create a build trigger for a 2nd-gen Bitbucket Cloud repository. - - bitbucket-data-center - (BETA) Create a build trigger for a 2nd-gen Bitbucket Data Center - repository. - bitbucketserver (BETA) Create a build trigger for a Bitbucket Server repository. diff --git a/gcloud/beta/builds/triggers/update/bitbucket-cloud b/gcloud/beta/builds/triggers/update/bitbucket-cloud deleted file mode 100644 index 17538e215..000000000 --- a/gcloud/beta/builds/triggers/update/bitbucket-cloud +++ /dev/null @@ -1,253 +0,0 @@ -NAME - gcloud beta builds triggers update bitbucket-cloud - updates Bitbucket - Cloud trigger used by Cloud Build - -SYNOPSIS - gcloud beta builds triggers update bitbucket-cloud - (TRIGGER : --region=REGION) - (--trigger-config=PATH | --description=DESCRIPTION - --ignored-files=[GLOB,...] --included-files=[GLOB,...] - --repository=REPOSITORY --[no-]require-approval - --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX - | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL - --pull-request-pattern=REGEX --build-config=PATH - | --inline-config=PATH - | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE - : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions - | --remove-substitutions=[KEY,...] - | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Updates Bitbucket Cloud trigger used by Cloud Build. - -EXAMPLES - To update the branch pattern of the trigger: - - $ gcloud beta builds triggers update bitbucket-cloud my-trigger \ - --branch-pattern=".*" - - To update the build config of the trigger: - - $ gcloud beta builds triggers update bitbucket-cloud my-trigger \ - --build-config="cloudbuild.yaml" - - To update the substitutions of the trigger: - - $ gcloud beta builds triggers update bitbucket-cloud my-trigger \ - --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master - - To update the 2nd-gen repository resource of the trigger: - - $ gcloud beta builds triggers update bitbucket-cloud my-trigger \ - --repository=projects/my-project/locations/us-west1/\ - connections/my-conn/repositories/my-repo - -POSITIONAL ARGUMENTS - Trigger resource - Build Trigger. 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 TRIGGER 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. - - TRIGGER - ID of the trigger or fully qualified identifier for the trigger. - - To set the trigger attribute: - ▸ provide the argument TRIGGER 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 location for the trigger. - - To set the region attribute: - ▸ provide the argument TRIGGER on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -REQUIRED FLAGS - Exactly one of these must be specified: - - --trigger-config=PATH - Path to Build Trigger config file (JSON or YAML format). For more - details, see - https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger - - Flag based trigger configuration - - --description=DESCRIPTION - Build trigger description. - - --ignored-files=[GLOB,...] - Glob filter. Changes only affecting ignored files won't trigger - builds. - - --included-files=[GLOB,...] - Glob filter. Changes affecting at least one included file will - trigger builds. - - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - - --[no-]require-approval - Require manual approval for triggered builds. Use - --require-approval to enable and --no-require-approval to disable. - - --service-account=SERVICE_ACCOUNT - The service account used for all user-controlled operations - including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and - CancelBuild. If no service account is set, then the standard Cloud - Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is - used instead. Format: - projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - - At most one of these can be specified: - - --branch-pattern=REGEX - A regular expression specifying which git branches to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --branch-pattern=foo will match - "foo", "foobar", and "barfoo". Events on a branch that does not - match will be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - --tag-pattern=REGEX - A regular expression specifying which git tags to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --tag-pattern=foo will match "foo", - "foobar", and "barfoo". Events on a tag that does not match will - be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - Pull Request settings - - --comment-control=COMMENT_CONTROL - Require a repository collaborator or owner to comment '/gcbrun' - on a pull request before running the build. COMMENT_CONTROL - must be one of: - - COMMENTS_DISABLED - Do not require comments on Pull Requests before builds are - triggered. - COMMENTS_ENABLED - Enforce that repository owners or collaborators must - comment on Pull Requests before builds are triggered. - COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY - Enforce that repository owners or collaborators must - comment on external contributors' Pull Requests before - builds are triggered. - - --pull-request-pattern=REGEX - A regular expression specifying which base git branch to match - for pull request events. - - This pattern is used as a regular expression search for the - base branch (the branch you are trying to merge into) for pull - request updates. For example, --pull-request-pattern=foo will - match "foo", "foobar", and "barfoo". - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - At most one of these can be specified: - - --build-config=PATH - Path to a YAML or JSON file containing the build configuration in - the repository. - - For more details, see: - https://cloud.google.com/cloud-build/docs/build-config - - --inline-config=PATH - Local path to a YAML or JSON file containing a build - configuration. - - Dockerfile build configuration flags - - --dockerfile=DOCKERFILE - Path of Dockerfile to use for builds in the repository. - - If specified, a build config will be generated to run docker - build using the specified file. - - The filename is relative to the Dockerfile directory. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-image=DOCKERFILE_IMAGE - Docker image name to build. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-dir=DOCKERFILE_DIR - Location of the directory containing the Dockerfile in the - repository. - - The directory will also be used as the Docker build context. - - At most one of these can be specified: - - --clear-substitutions - Clear existing substitutions. - - --remove-substitutions=[KEY,...] - Remove existing substitutions if present. - - --update-substitutions=[KEY=VALUE,...] - Update or add to existing substitutions. Substitutions are - parameters to be substituted or add in the build specification. - - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers update ... - --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 - - This will add the provided substitutions to the existing - substitutions and results in a build where every occurrence of - ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and - similarly for ${_NUM_CANDIES} and "10". - - Only the following built-in variables can be specified with the - --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, - REVISION_ID, COMMIT_SHA, SHORT_SHA. - - For more details, see: - https://cloud.google.com/build/docs/build-config-file-schema#substitutions - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud builds triggers update bitbucket-cloud - - $ gcloud alpha builds triggers update bitbucket-cloud - diff --git a/gcloud/beta/builds/triggers/update/bitbucket-data-center b/gcloud/beta/builds/triggers/update/bitbucket-data-center deleted file mode 100644 index feac36aaf..000000000 --- a/gcloud/beta/builds/triggers/update/bitbucket-data-center +++ /dev/null @@ -1,255 +0,0 @@ -NAME - gcloud beta builds triggers update bitbucket-data-center - updates - Bitbucket Data Center trigger used by Cloud Build - -SYNOPSIS - gcloud beta builds triggers update bitbucket-data-center - (TRIGGER : --region=REGION) - (--trigger-config=PATH | --description=DESCRIPTION - --ignored-files=[GLOB,...] --included-files=[GLOB,...] - --repository=REPOSITORY --[no-]require-approval - --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX - | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL - --pull-request-pattern=REGEX --build-config=PATH - | --inline-config=PATH - | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE - : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions - | --remove-substitutions=[KEY,...] - | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Updates Bitbucket Data Center trigger used by Cloud Build. - -EXAMPLES - To update the branch pattern of the trigger: - - $ gcloud beta builds triggers update bitbucket-data-center \ - my-trigger --branch-pattern=".*" - - To update the build config of the trigger: - - $ gcloud beta builds triggers update bitbucket-data-center \ - my-trigger --build-config="cloudbuild.yaml" - - To update the substitutions of the trigger: - - $ gcloud beta builds triggers update bitbucket-data-center \ - my-trigger \ - --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master - - To update the 2nd-gen repository resource of the trigger: - - $ gcloud beta builds triggers update bitbucket-data-center \ - my-trigger \ - --repository=projects/my-project/locations/us-west1/\ - connections/my-conn/repositories/my-repo - -POSITIONAL ARGUMENTS - Trigger resource - Build Trigger. 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 TRIGGER 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. - - TRIGGER - ID of the trigger or fully qualified identifier for the trigger. - - To set the trigger attribute: - ▸ provide the argument TRIGGER 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 location for the trigger. - - To set the region attribute: - ▸ provide the argument TRIGGER on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -REQUIRED FLAGS - Exactly one of these must be specified: - - --trigger-config=PATH - Path to Build Trigger config file (JSON or YAML format). For more - details, see - https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger - - Flag based trigger configuration - - --description=DESCRIPTION - Build trigger description. - - --ignored-files=[GLOB,...] - Glob filter. Changes only affecting ignored files won't trigger - builds. - - --included-files=[GLOB,...] - Glob filter. Changes affecting at least one included file will - trigger builds. - - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - - --[no-]require-approval - Require manual approval for triggered builds. Use - --require-approval to enable and --no-require-approval to disable. - - --service-account=SERVICE_ACCOUNT - The service account used for all user-controlled operations - including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and - CancelBuild. If no service account is set, then the standard Cloud - Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is - used instead. Format: - projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - - At most one of these can be specified: - - --branch-pattern=REGEX - A regular expression specifying which git branches to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --branch-pattern=foo will match - "foo", "foobar", and "barfoo". Events on a branch that does not - match will be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - --tag-pattern=REGEX - A regular expression specifying which git tags to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --tag-pattern=foo will match "foo", - "foobar", and "barfoo". Events on a tag that does not match will - be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - Pull Request settings - - --comment-control=COMMENT_CONTROL - Require a repository collaborator or owner to comment '/gcbrun' - on a pull request before running the build. COMMENT_CONTROL - must be one of: - - COMMENTS_DISABLED - Do not require comments on Pull Requests before builds are - triggered. - COMMENTS_ENABLED - Enforce that repository owners or collaborators must - comment on Pull Requests before builds are triggered. - COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY - Enforce that repository owners or collaborators must - comment on external contributors' Pull Requests before - builds are triggered. - - --pull-request-pattern=REGEX - A regular expression specifying which base git branch to match - for pull request events. - - This pattern is used as a regular expression search for the - base branch (the branch you are trying to merge into) for pull - request updates. For example, --pull-request-pattern=foo will - match "foo", "foobar", and "barfoo". - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - At most one of these can be specified: - - --build-config=PATH - Path to a YAML or JSON file containing the build configuration in - the repository. - - For more details, see: - https://cloud.google.com/cloud-build/docs/build-config - - --inline-config=PATH - Local path to a YAML or JSON file containing a build - configuration. - - Dockerfile build configuration flags - - --dockerfile=DOCKERFILE - Path of Dockerfile to use for builds in the repository. - - If specified, a build config will be generated to run docker - build using the specified file. - - The filename is relative to the Dockerfile directory. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-image=DOCKERFILE_IMAGE - Docker image name to build. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-dir=DOCKERFILE_DIR - Location of the directory containing the Dockerfile in the - repository. - - The directory will also be used as the Docker build context. - - At most one of these can be specified: - - --clear-substitutions - Clear existing substitutions. - - --remove-substitutions=[KEY,...] - Remove existing substitutions if present. - - --update-substitutions=[KEY=VALUE,...] - Update or add to existing substitutions. Substitutions are - parameters to be substituted or add in the build specification. - - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers update ... - --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 - - This will add the provided substitutions to the existing - substitutions and results in a build where every occurrence of - ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and - similarly for ${_NUM_CANDIES} and "10". - - Only the following built-in variables can be specified with the - --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, - REVISION_ID, COMMIT_SHA, SHORT_SHA. - - For more details, see: - https://cloud.google.com/build/docs/build-config-file-schema#substitutions - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud builds triggers update bitbucket-data-center - - $ gcloud alpha builds triggers update bitbucket-data-center - diff --git a/gcloud/beta/builds/triggers/update/help b/gcloud/beta/builds/triggers/update/help index ba0c8cba5..fbf2bf5db 100644 --- a/gcloud/beta/builds/triggers/update/help +++ b/gcloud/beta/builds/triggers/update/help @@ -15,12 +15,6 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - bitbucket-cloud - (BETA) Updates Bitbucket Cloud trigger used by Cloud Build. - - bitbucket-data-center - (BETA) Updates Bitbucket Data Center trigger used by Cloud Build. - bitbucketserver (BETA) Updates Bitbucket Server trigger used by Cloud Build. diff --git a/gcloud/beta/compute/disks/create b/gcloud/beta/compute/disks/create index 878b2b43b..55b3d7106 100644 --- a/gcloud/beta/compute/disks/create +++ b/gcloud/beta/compute/disks/create @@ -229,7 +229,7 @@ FLAGS created. --source-instant-snapshot=SOURCE_INSTANT_SNAPSHOT - Source instant snapshot used to create the disks. + Name of the source instant snapshot used to create the disks. --source-snapshot=SOURCE_SNAPSHOT Source snapshot used to create the disks. It is safe to delete a diff --git a/gcloud/beta/compute/images/import b/gcloud/beta/compute/images/import index 904571b29..20e43a2da 100644 --- a/gcloud/beta/compute/images/import +++ b/gcloud/beta/compute/images/import @@ -31,6 +31,11 @@ DESCRIPTION all four of these steps as required, depending on the input arguments specified. + Before importing an image, set up access to Cloud Storage and grant + required roles to the user accounts and service accounts. For more + information, see + https://cloud.google.com/compute/docs/import/requirements-export-import-images. + To override the detected OS, specify the --os flag. You can omit the translation step using the --data-disk flag. diff --git a/gcloud/beta/compute/instance-groups/managed/all-instances-config/delete b/gcloud/beta/compute/instance-groups/managed/all-instances-config/delete index c33566389..68d8a0b05 100644 --- a/gcloud/beta/compute/instance-groups/managed/all-instances-config/delete +++ b/gcloud/beta/compute/instance-groups/managed/all-instances-config/delete @@ -76,8 +76,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instance-groups managed all-instances-config delete $ gcloud alpha compute instance-groups managed \ all-instances-config delete diff --git a/gcloud/beta/compute/instance-groups/managed/all-instances-config/help b/gcloud/beta/compute/instance-groups/managed/all-instances-config/help index f0273b85c..582bb8d74 100644 --- a/gcloud/beta/compute/instance-groups/managed/all-instances-config/help +++ b/gcloud/beta/compute/instance-groups/managed/all-instances-config/help @@ -28,8 +28,10 @@ COMMANDS 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 compute instance-groups managed all-instances-config $ gcloud alpha compute instance-groups managed all-instances-config diff --git a/gcloud/beta/compute/instance-groups/managed/all-instances-config/update b/gcloud/beta/compute/instance-groups/managed/all-instances-config/update index e56bfeab6..75f00e8dc 100644 --- a/gcloud/beta/compute/instance-groups/managed/all-instances-config/update +++ b/gcloud/beta/compute/instance-groups/managed/all-instances-config/update @@ -78,8 +78,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instance-groups managed all-instances-config update $ gcloud alpha compute instance-groups managed \ all-instances-config update diff --git a/gcloud/beta/compute/instant-snapshots/add-labels b/gcloud/beta/compute/instant-snapshots/add-labels index 7319b582f..82dcc1fb3 100644 --- a/gcloud/beta/compute/instant-snapshots/add-labels +++ b/gcloud/beta/compute/instant-snapshots/add-labels @@ -88,8 +88,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instant-snapshots add-labels $ gcloud alpha compute instant-snapshots add-labels diff --git a/gcloud/beta/compute/instant-snapshots/create b/gcloud/beta/compute/instant-snapshots/create index 35b979831..487f63819 100644 --- a/gcloud/beta/compute/instant-snapshots/create +++ b/gcloud/beta/compute/instant-snapshots/create @@ -92,8 +92,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instant-snapshots create $ gcloud alpha compute instant-snapshots create diff --git a/gcloud/beta/compute/instant-snapshots/delete b/gcloud/beta/compute/instant-snapshots/delete index 132b8b3ee..988d45895 100644 --- a/gcloud/beta/compute/instant-snapshots/delete +++ b/gcloud/beta/compute/instant-snapshots/delete @@ -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 compute instant-snapshots delete $ gcloud alpha compute instant-snapshots delete diff --git a/gcloud/beta/compute/instant-snapshots/describe b/gcloud/beta/compute/instant-snapshots/describe index 811bff95f..e9c9b1e9b 100644 --- a/gcloud/beta/compute/instant-snapshots/describe +++ b/gcloud/beta/compute/instant-snapshots/describe @@ -74,8 +74,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instant-snapshots describe $ gcloud alpha compute instant-snapshots describe diff --git a/gcloud/beta/compute/instant-snapshots/help b/gcloud/beta/compute/instant-snapshots/help index ffce92e7b..3e54ea56b 100644 --- a/gcloud/beta/compute/instant-snapshots/help +++ b/gcloud/beta/compute/instant-snapshots/help @@ -35,8 +35,10 @@ COMMANDS (BETA) List Google Compute Engine instant snapshots. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instant-snapshots $ gcloud alpha compute instant-snapshots diff --git a/gcloud/beta/compute/instant-snapshots/list b/gcloud/beta/compute/instant-snapshots/list index fd87f77ff..5efb30d22 100644 --- a/gcloud/beta/compute/instant-snapshots/list +++ b/gcloud/beta/compute/instant-snapshots/list @@ -105,8 +105,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instant-snapshots list $ gcloud alpha compute instant-snapshots list diff --git a/gcloud/beta/compute/snapshots/create b/gcloud/beta/compute/snapshots/create index ccfcd511e..5c653ffd0 100644 --- a/gcloud/beta/compute/snapshots/create +++ b/gcloud/beta/compute/snapshots/create @@ -100,9 +100,12 @@ FLAGS encryption key. --source-instant-snapshot=SOURCE_INSTANT_SNAPSHOT - Source instant snapshot used to create the snapshot. To create a - snapshot from a source instant snapshot in a different project, specify - the full path to the source instant snapshot. For example: + The name or URL of the source instant snapshot. If the name is + provided, the instant snapshot's zone or region must be specified with + --source-instant-snapshot-zone or --source-instant-snapshot-region + accordingly. To create a snapshot from an instant snapshot in a + different project, specify the full path to the instant snapshot. If + the URL is provided, format should be: https://www.googleapis.com/compute/v1/projects/MY-PROJECT/zones/MY-ZONE/instantSnapshots/MY-INSTANT-SNAPSHOT --source-instant-snapshot-key-file=FILE diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index 4e4025097..7d286f8ea 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -486,6 +486,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index d7542d10b..793209a8c 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -518,6 +518,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index f8d6bfd5f..0909d4a6e 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -530,6 +530,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index f07bc0b99..4c458c70a 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -533,6 +533,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 3afd3b689..dfd28f98a 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -494,6 +494,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 6aea94961..7948a779e 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -67,7 +67,8 @@ SYNOPSIS [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--spot] - [--stack-type=STACK_TYPE] [--subnetwork=SUBNETWORK] + [--stack-type=STACK_TYPE] [--storage-pools=STORAGE_POOL,[...]] + [--subnetwork=SUBNETWORK] [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--workload-metadata=WORKLOAD_METADATA] [--workload-pool=WORKLOAD_POOL] @@ -1142,6 +1143,13 @@ FLAGS IP stack type of the node VMs. STACK_TYPE must be one of: ipv4, ipv4-ipv6. + --storage-pools=STORAGE_POOL,[...] + A list of storage pools where the cluster's boot disks will be + provisioned. + + STORAGE_POOL must be in the format + projects/project/zones/zone/storagePools/storagePool + --subnetwork=SUBNETWORK The Google Compute Engine subnetwork (https://cloud.google.com/compute/docs/subnetworks) to which the @@ -1388,7 +1396,7 @@ FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - (DEPRECATED) Select Advanced Datapath Observability mode for the + (REMOVED) Select Advanced Datapath Observability mode for the cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into @@ -1405,10 +1413,7 @@ FLAGS $ gcloud beta container clusters create \ --dataplane-v2-observability-mode=EXTERNAL_LB - The --dataplane-v2-observability-mode flag is deprecated and will be - removed in an upcoming release. Please use - --enable-dataplane-v2-flow-observability or - --disable-dataplane-v2-flow-observability. + Flag --dataplane-v2-observability-mode has been removed. DATAPLANE_V2_OBSERVABILITY_MODE must be one of: diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 528c06bcc..d56c6c92f 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -404,7 +404,7 @@ FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - (DEPRECATED) Select Advanced Datapath Observability mode for the + (REMOVED) Select Advanced Datapath Observability mode for the cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into @@ -421,10 +421,7 @@ FLAGS $ gcloud beta container clusters create-auto \ --dataplane-v2-observability-mode=EXTERNAL_LB - The --dataplane-v2-observability-mode flag is deprecated and will be - removed in an upcoming release. Please use - --enable-dataplane-v2-flow-observability or - --disable-dataplane-v2-flow-observability. + Flag --dataplane-v2-observability-mode has been removed. DATAPLANE_V2_OBSERVABILITY_MODE must be one of: diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index 71009ebc1..fdca07409 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -955,7 +955,7 @@ REQUIRED FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - (DEPRECATED) Select Advanced Datapath Observability mode for the + (REMOVED) Select Advanced Datapath Observability mode for the cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into @@ -972,10 +972,7 @@ REQUIRED FLAGS $ gcloud beta container clusters update \ --dataplane-v2-observability-mode=EXTERNAL_LB - The --dataplane-v2-observability-mode flag is deprecated and will - be removed in an upcoming release. Please use - --enable-dataplane-v2-flow-observability or - --disable-dataplane-v2-flow-observability. + Flag --dataplane-v2-observability-mode has been removed. DATAPLANE_V2_OBSERVABILITY_MODE must be one of: diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index a7cb90d7e..8da64b2e9 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -46,6 +46,7 @@ SYNOPSIS [--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, batch-soak-duration=BATCH_SOAK_DURATION,...]] + [--storage-pools=STORAGE_POOL,[...]] [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--tpu-topology=TPU_TOPOLOGY] [--windows-os-version=WINDOWS_OS_VERSION] @@ -616,6 +617,13 @@ FLAGS --standard-rollout-policy=batch-percent=0.3,\ batch-soak-duration=60s + --storage-pools=STORAGE_POOL,[...] + A list of storage pools where the node pool's boot disks will be + provisioned. + + STORAGE_POOL must be in the format + projects/project/zones/zone/storagePools/storagePool + --system-config-from-file=SYSTEM_CONFIG_FROM_FILE Path of the YAML/JSON file that contains the node configuration, including Linux kernel parameters (sysctls) and kubelet configs. diff --git a/gcloud/beta/container/node-pools/delete b/gcloud/beta/container/node-pools/delete index 7d5cd5a62..3bd8ec0c3 100644 --- a/gcloud/beta/container/node-pools/delete +++ b/gcloud/beta/container/node-pools/delete @@ -11,8 +11,8 @@ DESCRIPTION (BETA) gcloud beta container node-pools delete deletes a node pool from a Google Kubernetes Engine (GKE) cluster. When you delete a node pool, GKE drains all the nodes in the node pool. The draining process involves GKE - evicting Pods on each node in the node pool. Each node in a node pool is - drained by evicting Pods with an allotted graceful termination period of + deleting Pods on each node in the node pool. Each node in a node pool is + drained by deleting Pods with an allotted graceful termination period of MAX_POD. MAX_POD is the maximum terminationGracePeriodSeconds set on the Pods scheduled to the node with a cap of one hour. diff --git a/gcloud/beta/iap/settings/set b/gcloud/beta/iap/settings/set index 906aabec2..0ea3c5454 100644 --- a/gcloud/beta/iap/settings/set +++ b/gcloud/beta/iap/settings/set @@ -13,48 +13,50 @@ DESCRIPTION EXAMPLES To set the IAP setting for the resources within an organization, run: - $ gcloud beta iap settings set SETTING_FILE \ + $ gcloud beta iap settings set iap_settings.yaml \ --organization=ORGANIZATION_ID To set the IAP setting for the resources within a folder, run: - $ gcloud beta iap settings set SETTING_FILE --folder=FOLDER_ID + $ gcloud beta iap settings set iap_settings.yaml --folder=FOLDER_ID To set the IAP setting for the resources within a project, run: - $ gcloud beta iap settings set SETTING_FILE --project=PROJECT_ID + $ gcloud beta iap settings set iap_settings.yaml --project=PROJECT_ID To set the IAP setting for web type resources within a project, run: - $ gcloud beta iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=iap_web + $ gcloud beta iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=iap_web To set the IAP setting for all app engine services within a project, run: - $ gcloud beta iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=app-engine + $ gcloud beta iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=app-engine To set the IAP setting for an app engine service within a project, run: - $ gcloud beta iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=app-engine --service=SERVICE_ID + $ gcloud beta iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=app-engine \ + --service=SERVICE_ID To set the IAP setting for an app engine service version within a project, run: - $ gcloud beta iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=app-engine --service=SERVICE_ID \ - --version=VERSION_ID + $ gcloud beta iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=app-engine \ + --service=SERVICE_ID --version=VERSION_ID To set the IAP setting for all backend services within a project, run: - $ gcloud beta iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=compute + $ gcloud beta iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=compute To set the IAP setting for a backend service within a project, run: - $ gcloud beta iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=compute --service=SERVICE_ID + $ gcloud beta iap settings set iap_settings.yaml \ + --project=PROJECT_ID --resource-type=compute \ + --service=SERVICE_ID POSITIONAL ARGUMENTS SETTING_FILE diff --git a/gcloud/beta/network-security/firewall-endpoint-associations/update b/gcloud/beta/network-security/firewall-endpoint-associations/update index ada71d5c5..fc1926c35 100644 --- a/gcloud/beta/network-security/firewall-endpoint-associations/update +++ b/gcloud/beta/network-security/firewall-endpoint-associations/update @@ -5,9 +5,9 @@ NAME SYNOPSIS gcloud beta network-security firewall-endpoint-associations update (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--async] - [--max-wait=MAX_WAIT; default="60m"] [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] - [--no-tls-inspection-policy + [--max-wait=MAX_WAIT; default="60m"] + [--update-labels=[KEY=VALUE,...] --clear-labels + | --remove-labels=[KEY,...] --no-tls-inspection-policy | [--tls-inspection-policy=TLS_INSPECTION_POLICY : --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT --tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION]] diff --git a/gcloud/beta/scc/findings/create b/gcloud/beta/scc/findings/create index 22b077273..91f92e0a0 100644 --- a/gcloud/beta/scc/findings/create +++ b/gcloud/beta/scc/findings/create @@ -1,49 +1,59 @@ NAME - gcloud beta scc findings create - create a Cloud Security Command Center - finding + gcloud beta scc findings create - create a Security Command Center finding SYNOPSIS gcloud beta scc findings create (FINDING : --organization=ORGANIZATION --source=SOURCE) --category=CATEGORY --event-time=EVENT_TIME --resource-name=RESOURCE_NAME [--external-uri=EXTERNAL_URI] + [--location=LOCATION; default="global"] [--source-properties=[KEY=VALUE,...]] [--state=STATE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create a Cloud Security Command Center finding. + (BETA) Create a Security Command Center finding. EXAMPLES - Create an ACTIVE myFinding with category: XSS_SCRIPTING attached to - example-project under organization 123456 and source 5678: + Create an ACTIVE finding testFinding with category: XSS_SCRIPTING attached + to example-project under organization 123456 and source 5678: - $ gcloud beta scc findings create `myFinding` \ + $ gcloud beta scc findings create `testFinding` \ --organization=123456 --source=5678 --state=ACTIVE \ --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' - Create an ACTIVE myFinding attached to example-project under project - example-project and source 5678: + Create an ACTIVE finding testFinding attached to example-project under + project example-project and source 5678: $ gcloud beta scc findings create \ - projects/example-project/sources/5678/findings/myFinding \ + projects/example-project/sources/5678/findings/testFinding \ --state=ACTIVE --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' - Create an ACTIVE myFinding attached to example-project under folder 456 and - source 5678: + Create an ACTIVE finding testFinding attached to example-project under + folder 456 and source 5678: $ gcloud beta scc findings create \ - folders/456/sources/5678/findings/myFinding --state=ACTIVE \ + folders/456/sources/5678/findings/testFinding --state=ACTIVE \ --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' + Create an ACTIVE finding testFinding with category: XSS_SCRIPTING attached + to example-project under organization 123456, source 5678 and location=eu: + + $ gcloud beta scc findings create `testFinding` \ + --organization=123456 --source=5678 --state=ACTIVE \ + --category='XSS_SCRIPTING' \ + --event-time=2023-01-11T07:00:06.861Z \ + --resource-name='//cloudresourcemanager.googleapis.com/projects/\ + example-project' --location=eu + POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command Center) command. The arguments in this group can be used to specify the @@ -108,6 +118,17 @@ OPTIONAL FLAGS finding can be found. This field is guaranteed to be either empty or a well formed URL. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --source-properties=[KEY=VALUE,...] Source specific properties. These properties are managed by the source that writes the finding. The key names in the source_properties map @@ -128,8 +149,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/scc/findings/group b/gcloud/beta/scc/findings/group index 036ad00ea..9fb32f57b 100644 --- a/gcloud/beta/scc/findings/group +++ b/gcloud/beta/scc/findings/group @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta scc findings group [PARENT] [--compare-duration=COMPARE_DURATION] [--filter=FILTER] - [--group-by=GROUP_BY] [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN] + [--group-by=GROUP_BY] [--location=LOCATION; default="global"] + [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN] [--read-time=READ_TIME] [--source=SOURCE; default="-"] [GCLOUD_WIDE_FLAG ...] @@ -54,6 +55,12 @@ EXAMPLES $ gcloud beta scc findings group 123456 --source=5678 \ --group-by="state_change" --compare-duration=86400s + Group findings under organization 123456 and location=eu across all sources + by their category: + + $ gcloud beta scc findings group 123456 --group-by="category" \ + --location=eu + POSITIONAL ARGUMENTS Parent resource - parent organization, folder, or project in the Google Cloud resource hierarchy to be used for the gcloud scc command. Specify @@ -127,6 +134,17 @@ FLAGS ◆ state ◆ parent + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --page-size=PAGE_SIZE Maximum number of results to return in a single response. Default is 10, minimum is 1, maximum is 1000. @@ -154,8 +172,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/scc/findings/help b/gcloud/beta/scc/findings/help index c9bbc055f..a36a7cd2a 100644 --- a/gcloud/beta/scc/findings/help +++ b/gcloud/beta/scc/findings/help @@ -17,7 +17,7 @@ COMMANDS COMMAND is one of the following: create - (BETA) Create a Cloud Security Command Center finding. + (BETA) Create a Security Command Center finding. group (BETA) Filter an organization or source's findings and groups them by @@ -30,10 +30,10 @@ COMMANDS (BETA) List a finding's security marks. update - (BETA) Update a Cloud Security Command Center finding. + (BETA) Update a Security Command Center finding. update-marks - (BETA) Update Cloud Security Command Center finding's security marks. + (BETA) Update Security Command Center finding's security marks. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/scc/findings/list b/gcloud/beta/scc/findings/list index 8717b96de..9f43594f7 100644 --- a/gcloud/beta/scc/findings/list +++ b/gcloud/beta/scc/findings/list @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta scc findings list [PARENT] [--compare-duration=COMPARE_DURATION] [--field-mask=FIELD_MASK] - [--order-by=ORDER_BY] [--page-token=PAGE_TOKEN] [--read-time=READ_TIME] + [--location=LOCATION; default="global"] [--order-by=ORDER_BY] + [--page-token=PAGE_TOKEN] [--read-time=READ_TIME] [--source=SOURCE; default="-"] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -64,6 +65,11 @@ EXAMPLES $ gcloud beta scc findings list 123456 \ --filter="state=\"ACTIVE\"" --read-time="2019-01-01T01:00:00Z" + List all findings under organization 123456 across all sources and + location=eu: + + $ gcloud beta scc findings list 123456 --location=eu + POSITIONAL ARGUMENTS Parent resource - parent organization, folder, or project in the Google Cloud resource hierarchy to be used for the gcloud scc command. Specify @@ -118,6 +124,17 @@ FLAGS v/s camel case used in field masks. An empty or missing field mask will list all fields. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --order-by=ORDER_BY Expression that defines what fields and order to use for sorting. String value should follow SQL syntax: comma separated list of fields. @@ -177,8 +194,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/scc/findings/list-marks b/gcloud/beta/scc/findings/list-marks index 6590a089f..0d310a4e5 100644 --- a/gcloud/beta/scc/findings/list-marks +++ b/gcloud/beta/scc/findings/list-marks @@ -4,30 +4,36 @@ NAME SYNOPSIS gcloud beta scc findings list-marks (FINDING : --organization=ORGANIZATION --source=SOURCE) - [--page-token=PAGE_TOKEN] [--read-time=READ_TIME] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION; default="global"] [--page-token=PAGE_TOKEN] + [--read-time=READ_TIME] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) List a finding's security marks. EXAMPLES - List all security marks for myFinding under organization 123456 and source - 5678: + List all security marks for testFinding under organization 123456 and + source 5678: - $ gcloud beta scc findings list-marks `myFinding` \ + $ gcloud beta scc findings list-marks `testFinding` \ --organization=123456 --source=5678 - List all security marks for myFinding under project example-project and + List all security marks for testFinding under project example-project and source 5678: $ gcloud beta scc findings list-marks \ - projects/example-project/sources/5678/findings/myFinding + projects/example-project/sources/5678/findings/testFinding - List all security marks for myFinding under folder 456 and source 5678: + List all security marks for testFinding under folder 456 and source 5678: $ gcloud beta scc findings list-marks \ - folders/456/sources/5678/findings/myFinding + folders/456/sources/5678/findings/testFinding + + List all security marks for testFinding under organization 123456, source + 5678 and location=eu: + + $ gcloud beta scc findings list-marks `testFinding` \ + --organization=123456 --source=5678 --location=eu POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command @@ -71,6 +77,17 @@ POSITIONAL ARGUMENTS ▸ provide the argument --source on the command line. FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --page-token=PAGE_TOKEN Response objects will return a non-null value for page-token to indicate that there is at least one additional page of data. User can @@ -117,8 +134,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/scc/findings/update b/gcloud/beta/scc/findings/update index dec2053b1..5fca5a286 100644 --- a/gcloud/beta/scc/findings/update +++ b/gcloud/beta/scc/findings/update @@ -1,48 +1,54 @@ NAME - gcloud beta scc findings update - update a Cloud Security Command Center - finding + gcloud beta scc findings update - update a Security Command Center finding SYNOPSIS gcloud beta scc findings update (FINDING : --organization=ORGANIZATION --source=SOURCE) [--event-time=EVENT_TIME] [--external-uri=EXTERNAL_URI] + [--location=LOCATION; default="global"] [--source-properties=[KEY=VALUE,...]] [--state=STATE] [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update a Cloud Security Command Center finding. + (BETA) Update a Security Command Center finding. EXAMPLES - Update myFinding's state from ACTIVE to INACTIVE: + Update testFinding's state from ACTIVE to INACTIVE: - $ gcloud beta scc findings update `myFinding` \ + $ gcloud beta scc findings update `testFinding` \ --organization=123456 --source=5678 --state=INACTIVE - Update myFinding's state from ACTIVE to INACTIVE using project name for + Update testFinding's state from ACTIVE to INACTIVE using project name for example-project: $ gcloud beta scc findings update \ - projects/example-project/sources/5678/findings/myFinding \ + projects/example-project/sources/5678/findings/testFinding \ --state=INACTIVE - Update myFinding's state from ACTIVE to INACTIVE using folder name 456: + Update testFinding's state from ACTIVE to INACTIVE using folder name 456: $ gcloud beta scc findings update \ - folders/456/sources/5678/findings/myFinding --state=INACTIVE + folders/456/sources/5678/findings/testFinding --state=INACTIVE - Override all source properties on myFinding: + Override all source properties on testFinding: - $ gcloud beta scc findings update `myFinding` \ + $ gcloud beta scc findings update `testFinding` \ --organization=123456 --source=5678 \ --source-properties="propKey1=propVal1,propKey2=propVal2" - Selectively update a specific source property on myFinding: + Selectively update a specific source property on testFinding: - $ gcloud beta scc findings update `myFinding` \ + $ gcloud beta scc findings update `testFinding` \ --organization=123456 --source=5678 \ --source-properties="propKey1=propVal1,propKey2=propVal2" \ --update-mask="source_properties.propKey1" + Update finding testFinding with location=eu, state from ACTIVE to INACTIVE: + + $ gcloud beta scc findings update `testFinding` \ + --organization=123456 --source=5678 --state=INACTIVE \ + --location=eu + POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command Center) command. The arguments in this group can be used to specify the @@ -98,6 +104,17 @@ FLAGS finding can be found. This field is guaranteed to be either empty or a well formed URL. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --source-properties=[KEY=VALUE,...] Source specific properties. These properties are managed by the source that writes the finding. The key names in the source_properties map @@ -133,8 +150,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/scc/findings/update-marks b/gcloud/beta/scc/findings/update-marks index 3040fc7fd..6764709f2 100644 --- a/gcloud/beta/scc/findings/update-marks +++ b/gcloud/beta/scc/findings/update-marks @@ -1,49 +1,57 @@ NAME - gcloud beta scc findings update-marks - update Cloud Security Command - Center finding's security marks + gcloud beta scc findings update-marks - update Security Command Center + finding's security marks SYNOPSIS gcloud beta scc findings update-marks (FINDING : --organization=ORGANIZATION --source=SOURCE) + [--location=LOCATION; default="global"] [--security-marks=[KEY=VALUE,...]] [--start-time=START_TIME] [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update Cloud Security Command Center finding's security marks. + (BETA) Update Security Command Center finding's security marks. EXAMPLES - Selectively update security mark (Key1) with value (v1) on myFinding. Note - that other security marks on myFinding are untouched: + Selectively update security mark Key1 with value v1 on testFinding. Note + that other security marks on testFinding are untouched: - $ gcloud beta scc findings update-marks `myFinding` \ + $ gcloud beta scc findings update-marks `testFinding` \ --organization=123456 --source=5678 --security-marks="key1=v1" \ --update-mask="marks.markKey1" - Update all security marks on myFinding, under project example-project and + Update all security marks on testFinding, under project example-project and source 5678: $ gcloud beta scc findings update-marks \ - projects/example-project/sources/5678/findings/myFinding \ + projects/example-project/sources/5678/findings/testFinding \ --security-marks="key1=v1,key2=v2" - Update all security marks on myFinding, under folder 456 and source 5678: + Update all security marks on testFinding, under folder 456 and source 5678: $ gcloud beta scc findings update-marks \ - folders/456/sources/5678/findings/myFinding \ + folders/456/sources/5678/findings/testFinding \ --security-marks="key1=v1,key2=v2" - Update all security marks on myFinding, under organization 123456 and + Update all security marks on testFinding, under organization 123456 and source 5678: - $ gcloud beta scc findings update-marks `myFinding` \ + $ gcloud beta scc findings update-marks `testFinding` \ --organization=123456 --source=5678 \ --security-marks="key1=v1,key2=v2" - Delete all security marks on myFinding: + Delete all security marks on testFinding: - $ gcloud beta scc findings update-marks `myFinding` \ + $ gcloud beta scc findings update-marks `testFinding` \ --organization=123456 --source=5678 --security-marks="" + Update all security marks on testFinding, under project example-project, + source 5678 and location=eu: + + $ gcloud beta scc findings update-marks \ + projects/example-project/sources/5678/findings/testFinding \ + --security-marks="key1=v1,key2=v2" --location=eu + POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command Center) command. The arguments in this group can be used to specify the @@ -86,6 +94,17 @@ POSITIONAL ARGUMENTS ▸ provide the argument --source on the command line. FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --security-marks=[KEY=VALUE,...] SecurityMarks resource to be passed as the request body. It's a key=value pair separated by comma (,). For example: @@ -111,8 +130,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/scc/notifications/create b/gcloud/beta/scc/notifications/create index f1c9d0d68..22aa67ea7 100644 --- a/gcloud/beta/scc/notifications/create +++ b/gcloud/beta/scc/notifications/create @@ -1,16 +1,22 @@ NAME - gcloud beta scc notifications create - create a Cloud Security Command - Center notification config + gcloud beta scc notifications create - create a Security Command Center + notification config SYNOPSIS gcloud beta scc notifications create NOTIFICATION_CONFIG_ID --pubsub-topic=PUBSUB_TOPIC [--description=DESCRIPTION] - [--filter=FILTER] + [--filter=FILTER] [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create a Cloud Security Command Center notification config. + (BETA) Create a Security Command Center notification config. + + Notification configs that are created with Security Command Center API V2 + and later include a location attribute. If a location is not specified, the + default global location is used. For example, the following Notification + config name has location=global attribute: + organizations/123/locations/global/notificationConfigs/my-config. EXAMPLES Create a notification config test-config under organization 123 for @@ -21,10 +27,6 @@ EXAMPLES --organization=123 \ --pubsub-topic=projects/test-project/topics/notification-test \ --filter="resource_name: \"a\"" - $ gcloud beta scc notifications create \ - organizations/123/notificationConfigs/test-config \ - --pubsub-topic=projects/test-project/topics/notification-test \ - --filter="resource_name: \"a\"" Create a notification config test-config under folder 456 for findings for pubsub-topic projects/test-project/topics/notification-test with a filter @@ -33,10 +35,6 @@ EXAMPLES $ gcloud beta scc notifications create test-config --folder=456 \ --pubsub-topic=projects/test-project/topics/notification-test \ --filter="resource_name: \"a\"" - $ gcloud beta scc notifications create \ - folders/456/notificationConfigs/test-config \ - --pubsub-topic=projects/test-project/topics/notification-test \ - --filter="resource_name: \"a\"" Create a notification config test-config under project 789 for findings for pubsub-topic projects/test-project/topics/notification-test with a filter @@ -45,10 +43,14 @@ EXAMPLES $ gcloud beta scc notifications create test-config --project=789 \ --pubsub-topic=projects/test-project/topics/notification-test \ --filter="resource_name: \"a\"" - $ gcloud beta scc notifications create \ - projects/789/notificationConfigs/test-config \ + + Create a notification config test-config under organization 123 for + findings for pubsub-topic projects/test-project/topics/notification-test + with a filter on resource name and location=eu + + $ gcloud beta scc notifications create test-config --project=789 \ --pubsub-topic=projects/test-project/topics/notification-test \ - --filter="resource_name: \"a\"" + --filter="resource_name: \"a\"" --location=eu POSITIONAL ARGUMENTS NOTIFICATION_CONFIG_ID @@ -67,6 +69,17 @@ OPTIONAL FLAGS --filter=FILTER Filter to be used for notification config. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -90,8 +103,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/scc/notifications/delete b/gcloud/beta/scc/notifications/delete index 768243a74..ead691cb5 100644 --- a/gcloud/beta/scc/notifications/delete +++ b/gcloud/beta/scc/notifications/delete @@ -1,33 +1,47 @@ NAME - gcloud beta scc notifications delete - delete a Cloud Security Command - Center notification config + gcloud beta scc notifications delete - delete a Security Command Center + notification config SYNOPSIS gcloud beta scc notifications delete NOTIFICATION_CONFIG_ID + [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete a Cloud Security Command Center notification config. + (BETA) Delete a Security Command Center notification config. + + Notification configs that are created with Security Command Center API V2 + and later include a location attribute. If the location attribute is + included in the resource name of a Notification configs, you must specify + it when referencing the Notification config. For example, the following + Notification configs name has location=eu: + organizations/123/locations/eu/notificationConfigs/test-config. EXAMPLES - Delete notification config 'my-config' from organization 123 + Delete notification config 'test-config' from organization 123 - $ gcloud beta scc notifications delete my-config --organization=123 - $ gcloud beta scc notifications delete \ - organizations/123/notificationConfigs/my-config + $ gcloud beta scc notifications delete test-config --organization=123 - Delete notification config 'my-config' from folder 456 + Delete notification config 'test-config' from folder 456 - $ gcloud beta scc notifications delete my-config --folder=456 - $ gcloud beta scc notifications delete \ - folders/456/notificationConfigs/my-config + $ gcloud beta scc notifications delete test-config --folder=456 - Delete notification config 'my-config' from project 789 + Delete notification config 'test-config' from project 789 - $ gcloud beta scc notifications delete my-config --project=789 - $ gcloud beta scc notifications delete \ - projects/789/notificationConfigs/my-config + $ gcloud beta scc notifications delete test-config --project=789 + + Delete notification config 'test-config' with location global from + organization 123 + + $ gcloud beta scc notifications delete test-config \ + --organization=123 --location=global + + Delete notification config 'test-config' with location=eu from organization + 123 + + $ gcloud beta scc notifications delete test-config \ + --organization=123 --location=eu POSITIONAL ARGUMENTS NOTIFICATION_CONFIG_ID @@ -35,6 +49,17 @@ POSITIONAL ARGUMENTS "organizations/123/notificationConfigs/456" or just "456". FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -58,8 +83,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/scc/notifications/describe b/gcloud/beta/scc/notifications/describe index 0fc3a1a0e..679fdbd3c 100644 --- a/gcloud/beta/scc/notifications/describe +++ b/gcloud/beta/scc/notifications/describe @@ -1,36 +1,42 @@ NAME - gcloud beta scc notifications describe - describe a Cloud Security Command - Center notification config + gcloud beta scc notifications describe - describe a Security Command Center + notification config SYNOPSIS gcloud beta scc notifications describe NOTIFICATION_CONFIG_ID + [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe a Cloud Security Command Center notification config. + (BETA) Describe a Security Command Center notification config. + + Notification configs that are created with Security Command Center API V2 + and later include a location attribute. If the location attribute is + included in the resource name of a Notification configs, you must specify + it when referencing the Notification config. For example, the following + Notification configs name has location=eu: + organizations/123/locations/eu/notificationConfigs/test-config. EXAMPLES - Describe notification config 'my-config' from organization 123 + Describe notification config 'test-config' from organization 123 - $ gcloud beta scc notifications describe notifications describe \ - my-config --organization=123 - $ gcloud beta scc notifications describe notifications describe \ - organizations/123/notificationConfigs/my-config + $ gcloud beta scc notifications describe test-config \ + --organization=123 - Describe notification config 'my-config' from folder 456 + Describe notification config 'test-config' from folder 456 - $ gcloud beta scc notifications describe notifications describe \ - my-config --folder=456 - $ gcloud beta scc notifications describe notifications describe \ - folders/456/notificationConfigs/my-config + $ gcloud beta scc notifications describe test-config --folder=456 - Describe notification config 'my-config' from project 789 + Describe notification config 'test-config' from project 789 - $ gcloud beta scc notifications describe notifications describe \ - my-config --project=789 - $ gcloud beta scc notifications describe notifications describe \ - projects/789/notificationConfigs/my-config + $ gcloud beta scc notifications describe test-config --project=789 + + Describe notification config 'test-config' from organization 123 and + location=global + + $ gcloud beta scc notifications describe test-config \ + --organization=123 --location=global POSITIONAL ARGUMENTS NOTIFICATION_CONFIG_ID @@ -38,6 +44,17 @@ POSITIONAL ARGUMENTS "organizations/123/notificationConfigs/456" or just "456". FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -61,8 +78,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/scc/notifications/help b/gcloud/beta/scc/notifications/help index 408d2036b..5a398318d 100644 --- a/gcloud/beta/scc/notifications/help +++ b/gcloud/beta/scc/notifications/help @@ -17,19 +17,19 @@ COMMANDS COMMAND is one of the following: create - (BETA) Create a Cloud Security Command Center notification config. + (BETA) Create a Security Command Center notification config. delete - (BETA) Delete a Cloud Security Command Center notification config. + (BETA) Delete a Security Command Center notification config. describe - (BETA) Describe a Cloud Security Command Center notification config. + (BETA) Describe a Security Command Center notification config. list - (BETA) List Cloud Security Command Center notification configs. + (BETA) List Security Command Center notification configs. update - (BETA) Update a Cloud Security Command Center notification config. + (BETA) Update a Security Command Center notification config. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/scc/notifications/list b/gcloud/beta/scc/notifications/list index bc9390c61..d4473edc9 100644 --- a/gcloud/beta/scc/notifications/list +++ b/gcloud/beta/scc/notifications/list @@ -1,14 +1,19 @@ NAME - gcloud beta scc notifications list - list Cloud Security Command Center + gcloud beta scc notifications list - list Security Command Center notification configs SYNOPSIS - gcloud beta scc notifications list [PARENT] [--filter=EXPRESSION] + gcloud beta scc notifications list [PARENT] + [--location=LOCATION; default="global"] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Cloud Security Command Center notification configs. + (BETA) List Security Command Center notification configs. + + Notification Configs that are created with Security Command Center API V2 + and later include a `location` attribute. Include the `--location` flag to + list Notification Configs with `location` attribute other than `global`. EXAMPLES List notification configs from organization 123 @@ -24,6 +29,12 @@ EXAMPLES $ gcloud beta scc notifications list projects/789 + List notification configs from organization 123 and location=eu + + $ gcloud beta scc notifications list 123 --location=eu + $ gcloud beta scc notifications list organizations/123 \ + --location=locations/eu + POSITIONAL ARGUMENTS Parent resource - parent organization, folder, or project in the Google Cloud resource hierarchy to be used for the gcloud scc command. Specify @@ -38,6 +49,18 @@ POSITIONAL ARGUMENTS ▸ Set the parent property in configuration using gcloud config set scc/parent if it is not specified in command line. +FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. @@ -73,8 +96,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/scc/notifications/update b/gcloud/beta/scc/notifications/update index 712a87b30..9c0abd028 100644 --- a/gcloud/beta/scc/notifications/update +++ b/gcloud/beta/scc/notifications/update @@ -1,81 +1,69 @@ NAME - gcloud beta scc notifications update - update a Cloud Security Command - Center notification config + gcloud beta scc notifications update - update a Security Command Center + notification config SYNOPSIS gcloud beta scc notifications update NOTIFICATION_CONFIG_ID [--description=DESCRIPTION] [--filter=FILTER] - [--pubsub-topic=PUBSUB_TOPIC] + [--location=LOCATION; default="global"] [--pubsub-topic=PUBSUB_TOPIC] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update a Cloud Security Command Center notification config. + (BETA) Update a Security Command Center notification config. + + Notification configs that are created with Security Command Center API V2 + and later include a location attribute. If the location attribute is + included in the resource name of a Notification configs, you must specify + it when referencing the Notification config. For example, the following + Notification configs name has location=eu: + organizations/123/locations/eu/notificationConfigs/test-config. EXAMPLES - Update all mutable fields under an organization parent my-config + Update all mutable fields under an organization parent test-config (description + pubsub topic + filter): $ gcloud beta scc notifications update scc notifications update \ - my-config --organization=123 --description="New description" \ + test-config --organization=123 --description="New description" \ --pubsub-topic="projects/22222/topics/newtopic" - $ gcloud beta scc notifications update scc notifications update \ - organizations/123/notificationConfigs/my-config \ - --description="New description" \ - --pubsub-topic="projects/22222/topics/newtopic" - - Update all mutable fields under a folder parent my-config (description + + Update all mutable fields under a folder parent test-config (description + pubsub topic + filter): $ gcloud beta scc notifications update scc notifications update \ - my-config --folder=456 --description="New description" \ + test-config --folder=456 --description="New description" \ --pubsub-topic="projects/22222/topics/newtopic" - $ gcloud beta scc notifications update scc notifications update \ - folders/456/notificationConfigs/my-config \ - --description="New description" \ - --pubsub-topic="projects/22222/topics/newtopic" - - Update all mutable fields under a project parent my-config (description + + Update all mutable fields under a project parent test-config (description + pubsub topic + filter): $ gcloud beta scc notifications update scc notifications update \ - my-config --project=789 --description="New description" \ + test-config --project=789 --description="New description" \ --pubsub-topic="projects/22222/topics/newtopic" - $ gcloud beta scc notifications update scc notifications update \ - projects/789/notificationConfigs/my-config \ - --description="New description" \ - --pubsub-topic="projects/22222/topics/newtopic" + Update test-config's description - Update my-config's description - - $ gcloud beta scc notifications update my-config \ + $ gcloud beta scc notifications update test-config \ --organization=123 --description="New description" - $ gcloud beta scc notifications update \ - organizations/123/notificationConfigs/my-config \ - --description="New description" + Update test-config's pubsub-topic - Update my-config's pubsub-topic - - $ gcloud beta scc notifications update my-config \ + $ gcloud beta scc notifications update test-config \ --organization=123 \ --pubsub-topic="projects/22222/topics/newtopic" - $ gcloud beta scc notifications update \ - organizations/123/notificationConfigs/my-config \ - --pubsub-topic="projects/22222/topics/newtopic" + Update test-config's filter - Update my-config's filter - - $ gcloud beta scc notifications update my-config \ + $ gcloud beta scc notifications update test-config \ --organization=123 --filter='state = \"ACTIVE\"' - $ gcloud beta scc notifications update \ - organizations/123/notificationConfigs/my-config \ - --filter='state = \"ACTIVE\"' + Update all mutable fields for test-config with location=global under an + organization parent (description + pubsub topic + filter): + + $ gcloud beta scc notifications update scc notifications update \ + test-config --organization=123 --description="New description" \ + --pubsub-topic="projects/22222/topics/newtopic" \ + --location=global POSITIONAL ARGUMENTS NOTIFICATION_CONFIG_ID @@ -90,6 +78,17 @@ FLAGS The filter string which will applied to events of findings of a notification configuration. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --pubsub-topic=PUBSUB_TOPIC The Pub/Sub topic which will receive notifications. Its format is "projects/[project_id]/topics/[topic]". @@ -117,8 +116,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/spanner/backups/copy b/gcloud/beta/spanner/backups/copy index 365f59afe..8b6ef32f5 100644 --- a/gcloud/beta/spanner/backups/copy +++ b/gcloud/beta/spanner/backups/copy @@ -129,42 +129,46 @@ OPTIONAL FLAGS Use the default encryption configuration if one exists. otherwise use the same encryption configuration as the source backup. - Key resource - Cloud KMS key to be used to copy the Cloud Spanner backup. - The arguments in this group can be used to specify the attributes of this - resource. + KMS key name group - --kms-key=KMS_KEY - ID of the key or fully qualified identifier for the key. + At most one of these can be specified: - To set the kms-key attribute: - ▸ provide the argument --kms-key on the command line. + Key resource - Cloud KMS key to be used to copy the Cloud Spanner + backup. The arguments in this group can be used to specify the + attributes of this resource. - This flag argument must be specified if any of the other arguments in - this group are specified. + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. - --kms-keyring=KMS_KEYRING - KMS keyring id of the key. + To set the kms-key attribute: + ▫ provide the argument --kms-key on the command line. - To set the kms-keyring attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-keyring on the command line. + This flag argument must be specified if any of the other arguments + in this group are specified. - --kms-location=KMS_LOCATION - Cloud location for the key. + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. - To set the kms-location attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-location on the command line. + To set the kms-keyring attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-keyring on the command line. - --kms-project=KMS_PROJECT - Cloud project id for the key. + --kms-location=KMS_LOCATION + Cloud location for the key. - To set the kms-project attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-project on the command line. + To set the kms-location attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. + + To set the kms-project attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-project on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/spanner/backups/create b/gcloud/beta/spanner/backups/create index 6707045d1..b4f808c4f 100644 --- a/gcloud/beta/spanner/backups/create +++ b/gcloud/beta/spanner/backups/create @@ -98,42 +98,46 @@ OPTIONAL FLAGS use-database-encryption Use the same encryption configuration as the database. - Key resource - Cloud KMS key to be used to create the Cloud Spanner - backup. The arguments in this group can be used to specify the attributes - of this resource. + KMS key name group - --kms-key=KMS_KEY - ID of the key or fully qualified identifier for the key. + At most one of these can be specified: - To set the kms-key attribute: - ▸ provide the argument --kms-key on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner + backup. The arguments in this group can be used to specify the + attributes of this resource. - This flag argument must be specified if any of the other arguments in - this group are specified. + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. - --kms-keyring=KMS_KEYRING - KMS keyring id of the key. + To set the kms-key attribute: + ▫ provide the argument --kms-key on the command line. - To set the kms-keyring attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-keyring on the command line. + This flag argument must be specified if any of the other arguments + in this group are specified. - --kms-location=KMS_LOCATION - Cloud location for the key. + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. - To set the kms-location attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-location on the command line. + To set the kms-keyring attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-keyring on the command line. - --kms-project=KMS_PROJECT - Cloud project id for the key. + --kms-location=KMS_LOCATION + Cloud location for the key. - To set the kms-project attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-project on the command line. + To set the kms-location attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. + + To set the kms-project attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-project on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/spanner/databases/create b/gcloud/beta/spanner/databases/create index 4bc032fba..252d83e8e 100644 --- a/gcloud/beta/spanner/databases/create +++ b/gcloud/beta/spanner/databases/create @@ -87,42 +87,46 @@ FLAGS --ddl_file is set, --ddl is ignored. One line comments starting with -- are ignored. - Key resource - Cloud KMS key to be used to create the Cloud Spanner - database. The arguments in this group can be used to specify the - attributes of this resource. + KMS key name group - --kms-key=KMS_KEY - ID of the key or fully qualified identifier for the key. + At most one of these can be specified: - To set the kms-key attribute: - ▸ provide the argument --kms-key on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner + database. The arguments in this group can be used to specify the + attributes of this resource. - This flag argument must be specified if any of the other arguments in - this group are specified. + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. - --kms-keyring=KMS_KEYRING - KMS keyring id of the key. + To set the kms-key attribute: + ▫ provide the argument --kms-key on the command line. - To set the kms-keyring attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-keyring on the command line. + This flag argument must be specified if any of the other arguments + in this group are specified. - --kms-location=KMS_LOCATION - Cloud location for the key. + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. - To set the kms-location attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-location on the command line. + To set the kms-keyring attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-keyring on the command line. - --kms-project=KMS_PROJECT - Cloud project id for the key. + --kms-location=KMS_LOCATION + Cloud location for the key. - To set the kms-project attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-project on the command line. + To set the kms-location attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. + + To set the kms-project attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-project on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/spanner/databases/restore b/gcloud/beta/spanner/databases/restore index fada0f896..c6663c2cc 100644 --- a/gcloud/beta/spanner/databases/restore +++ b/gcloud/beta/spanner/databases/restore @@ -110,42 +110,46 @@ OPTIONAL FLAGS Use the default encryption configuration if one exists, otherwise use the same encryption configuration as the backup. - Key resource - Cloud KMS key to be used to restore the Cloud Spanner - database. The arguments in this group can be used to specify the - attributes of this resource. + KMS key name group - --kms-key=KMS_KEY - ID of the key or fully qualified identifier for the key. + At most one of these can be specified: - To set the kms-key attribute: - ▸ provide the argument --kms-key on the command line. + Key resource - Cloud KMS key to be used to restore the Cloud Spanner + database. The arguments in this group can be used to specify the + attributes of this resource. - This flag argument must be specified if any of the other arguments in - this group are specified. + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. - --kms-keyring=KMS_KEYRING - KMS keyring id of the key. + To set the kms-key attribute: + ▫ provide the argument --kms-key on the command line. - To set the kms-keyring attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-keyring on the command line. + This flag argument must be specified if any of the other arguments + in this group are specified. - --kms-location=KMS_LOCATION - Cloud location for the key. + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. - To set the kms-location attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-location on the command line. + To set the kms-keyring attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-keyring on the command line. - --kms-project=KMS_PROJECT - Cloud project id for the key. + --kms-location=KMS_LOCATION + Cloud location for the key. - To set the kms-project attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-project on the command line. + To set the kms-location attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. + + To set the kms-project attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-project on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/sql/backups/delete b/gcloud/beta/sql/backups/delete index 022eb4680..59cac6764 100644 --- a/gcloud/beta/sql/backups/delete +++ b/gcloud/beta/sql/backups/delete @@ -2,26 +2,25 @@ NAME gcloud beta sql backups delete - delete a backup of a Cloud SQL instance SYNOPSIS - gcloud beta sql backups delete ID --instance=INSTANCE, -i INSTANCE - [--async] [GCLOUD_WIDE_FLAG ...] + gcloud beta sql backups delete ID [--async] + [--instance=INSTANCE, -i INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Delete a backup of a Cloud SQL instance. POSITIONAL ARGUMENTS ID - The ID of the backup run. You can find the ID by running $ gcloud sql - backups list -i {instance}. + The ID of the backup run. To find the ID, run the following command: $ + gcloud sql backups list -i {instance}. -REQUIRED FLAGS - --instance=INSTANCE, -i INSTANCE - Cloud SQL instance ID. - -OPTIONAL FLAGS +FLAGS --async Return immediately, without waiting for the operation in progress to complete. + --instance=INSTANCE, -i INSTANCE + Cloud SQL instance ID. + 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/builds/connections/create/bitbucket-cloud b/gcloud/builds/connections/create/bitbucket-cloud deleted file mode 100644 index 37eb9246a..000000000 --- a/gcloud/builds/connections/create/bitbucket-cloud +++ /dev/null @@ -1,108 +0,0 @@ -NAME - gcloud builds connections create bitbucket-cloud - create a Cloud Build - Connection for Bitbucket Cloud - -SYNOPSIS - gcloud builds connections create bitbucket-cloud - (CONNECTION : --region=REGION) - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION - --workspace=WORKSPACE [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - Create a Cloud Build Connection for Bitbucket Cloud. - - A Bitbucket Cloud Connection can be created by using a - repository/project/workspace access token with - repository_read,repository_admin, pullrequest_read, webhook scope - permission and a repository/project/workspace access token with - repository_read scope permission. - -EXAMPLES - To create a Bitbucket Cloud connection, provide all the required - parameters: - - $ gcloud builds connections create bitbucket-cloud \ - my-bitbucket-conn --project=myproj --region=us-central1 \ - --workspace=my-workspace \ - --read-authorizer-token-secret-version=projects/myproj/secrets/\ - read-pat/versions/1 \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 \ - --webhook-secret-secret-version=projects/myproj/secrets/\ - whsecret/versions/1 - -POSITIONAL ARGUMENTS - Connection resource - Connection 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 connection on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CONNECTION - ID of the connection or fully qualified identifier for the - connection. - - To set the connection attribute: - ▸ provide the argument connection on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The Google Cloud region. - - To set the region attribute: - ▸ provide the argument connection on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -REQUIRED FLAGS - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the repository_read,repository_admin, - pullrequest_read, webhook repository/project/workspace access token. - - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the repository_read repository/project/workspace - access token. - - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION - Secret containing the webhook secret string for validating webhook - events sent by Bitbucket Cloud. - - --workspace=WORKSPACE - Workspace of the Bitbucket Cloud instance. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the cloudbuild/v2 API. The full documentation for this - API can be found at: https://cloud.google.com/cloud-build/docs/ - -NOTES - These variants are also available: - - $ gcloud alpha builds connections create bitbucket-cloud - - $ gcloud beta builds connections create bitbucket-cloud - diff --git a/gcloud/builds/connections/create/bitbucket-data-center b/gcloud/builds/connections/create/bitbucket-data-center deleted file mode 100644 index 5d104aeab..000000000 --- a/gcloud/builds/connections/create/bitbucket-data-center +++ /dev/null @@ -1,139 +0,0 @@ -NAME - gcloud builds connections create bitbucket-data-center - create a Cloud - Build Connection for Bitbucket Data Center - -SYNOPSIS - gcloud builds connections create bitbucket-data-center - (CONNECTION : --region=REGION) - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION [--async] - [--host-uri=HOST_URI] - [--service-directory-service=SERVICE_DIRECTORY_SERVICE - : --ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - Create a Cloud Build Connection for Bitbucket Data Center. - - A Bitbucket Data Center Connection can be created by using a personal - access token with REPO_ADMIN scope permission. A REPO_READ scoped personal - access token will also be required. - - If the Bitbucket Data Center can only be accessed within a VPC, a Service - Directory service resource can be provided for connecting to it. - -EXAMPLES - To create a Bitbucket Data Center connection, provide all the required - parameters: - - $ gcloud builds connections create bitbucket-data-center \ - my-bitbucket-conn --project=myproj --region=us-central1 \ - --host-uri=https://bitbucket-server.net \ - --read-authorizer-token-secret-version=projects/myproj/secrets/\ - read-pat/versions/1 \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 \ - --webhook-secret-secret-version=projects/myproj/secrets/\ - whsecret/versions/1 - - To create a Bitbucket Data Center connection for a private Bitbucket Data - Center server. Provide the service-directory-service and ssl-ca-file as - well: - - $ gcloud builds connections create bitbucket-data-center \ - my-private-bitbucket-conn \ - --host-uri=https://my.private-bitbucket-server.net \ - --project=myproj --region=us-central1 \ - --service-directory-service=projects/myproj/namespaces/x/\ - services/mysds --ssl-ca-file=mycertificate.crt \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 \ - --read-authorizer-token-secret-version=projects/myproj/secrets/\ - read-pat/versions/1 \ - --webhook-secret-secret-version=projects/myproj/secrets/\ - whsecret/versions/1 - -POSITIONAL ARGUMENTS - Connection resource - Connection 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 connection on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CONNECTION - ID of the connection or fully qualified identifier for the - connection. - - To set the connection attribute: - ▸ provide the argument connection on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The Google Cloud region. - - To set the region attribute: - ▸ provide the argument connection on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -REQUIRED FLAGS - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the REPO_ADMIN personal access token. - - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the REPO_READ personal access token. - - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION - Secret containing the webhook secret string for validating webhook - events sent by Bitbucket Data Center. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --host-uri=HOST_URI - URI of the Bitbucket Data Center instance. - - Group of arguments for configuring access through Service Directory. - - --service-directory-service=SERVICE_DIRECTORY_SERVICE - Service Directory service resource to use for accessing the Bitbucket - Data Center. Necessary only if the server has no public access from - the internet. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --ssl-ca-file=SSL_CA_FILE - File containing the SSL_CA to be used. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 cloudbuild/v2 API. The full documentation for this - API can be found at: https://cloud.google.com/cloud-build/docs/ - -NOTES - These variants are also available: - - $ gcloud alpha builds connections create bitbucket-data-center - - $ gcloud beta builds connections create bitbucket-data-center - diff --git a/gcloud/builds/connections/create/help b/gcloud/builds/connections/create/help index a4fc637eb..d9ef19a9e 100644 --- a/gcloud/builds/connections/create/help +++ b/gcloud/builds/connections/create/help @@ -15,12 +15,6 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - bitbucket-cloud - Create a Cloud Build Connection for Bitbucket Cloud. - - bitbucket-data-center - Create a Cloud Build Connection for Bitbucket Data Center. - github Create a Cloud Build Connection of type GitHub. diff --git a/gcloud/builds/connections/update/bitbucket-cloud b/gcloud/builds/connections/update/bitbucket-cloud deleted file mode 100644 index 9c888a26e..000000000 --- a/gcloud/builds/connections/update/bitbucket-cloud +++ /dev/null @@ -1,103 +0,0 @@ -NAME - gcloud builds connections update bitbucket-cloud - update a Cloud Build - Connection of type Bitbucket Cloud - -SYNOPSIS - gcloud builds connections update bitbucket-cloud - (CONNECTION : --region=REGION) [--async] - [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] - [--read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION] - [--webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION] - [--workspace=WORKSPACE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - Update a Cloud Build Connection of type Bitbucket Cloud. - -EXAMPLES - To update the workspace, provide the connection name and the workspace - name: - - $ gcloud builds connections update bitbucket-cloud my-bbc-conn \ - --region=us-west1 --workspace=my-workspace - - To update the authorization token, provide the connection name and the new - authorization token secret version. - - $ gcloud builds connections update bitbucket-cloud my-bbc-conn \ - --region=us-west1 \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 - -POSITIONAL ARGUMENTS - Connection resource - Connection 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 connection on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CONNECTION - ID of the connection or fully qualified identifier for the - connection. - - To set the connection attribute: - ▸ provide the argument connection on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The Google Cloud region. - - To set the region attribute: - ▸ provide the argument connection on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the repository_read,repository_admin, - pullrequest_read, webhook access token. It can be a repository, project - or workspace access token. - - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the repository_read access token. It can be a - repository, project or workspace access token. - - --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION - Secret containing the webhook secret string for validating webhook - events sent by Bitbucket Cloud. - - --workspace=WORKSPACE - Workspace of the Bitbucket Cloud 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. - -API REFERENCE - This command uses the cloudbuild/v2 API. The full documentation for this - API can be found at: https://cloud.google.com/cloud-build/docs/ - -NOTES - These variants are also available: - - $ gcloud alpha builds connections update bitbucket-cloud - - $ gcloud beta builds connections update bitbucket-cloud - diff --git a/gcloud/builds/connections/update/bitbucket-data-center b/gcloud/builds/connections/update/bitbucket-data-center deleted file mode 100644 index 4ec0b3c69..000000000 --- a/gcloud/builds/connections/update/bitbucket-data-center +++ /dev/null @@ -1,104 +0,0 @@ -NAME - gcloud builds connections update bitbucket-data-center - update a Cloud - Build Connection of type Bitbucket Data Center - -SYNOPSIS - gcloud builds connections update bitbucket-data-center - (CONNECTION : --region=REGION) [--async] - [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] - [--host-uri=HOST_URI] - [--read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION] - [--service-directory-service=SERVICE_DIRECTORY_SERVICE] - [--ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - Update a Cloud Build Connection of type Bitbucket Data Center. - -EXAMPLES - To update the ssl_ca, provide the connection name and the ssl_ca file: - - $ gcloud builds connections update bitbucket-data-center \ - my-gle-conn --region=us-west1 --ssl-ca-file=mycertificate.crt - - To update the authorization token, provide the connection name and the new - authorization token secret version name. - - $ gcloud builds connections update bitbucket-data-center \ - my-gle-conn --region=us-west1 \ - --authorizer-token-secret-version=projects/myproj/secrets/\ - admin-pat/versions/1 - -POSITIONAL ARGUMENTS - Connection resource - Connection 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 connection on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CONNECTION - ID of the connection or fully qualified identifier for the - connection. - - To set the connection attribute: - ▸ provide the argument connection on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The Google Cloud region. - - To set the region attribute: - ▸ provide the argument connection on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the REPO_ADMIN personal access token. - - --host-uri=HOST_URI - URI of the Bitbucket Data Center instance. - - --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION - Secret containing the REPO_READ personal access token. - - --service-directory-service=SERVICE_DIRECTORY_SERVICE - Service Directory service resource to use for accessing the Bitbucket - Data Center. Necessary only if the server has no public access from the - internet. - - --ssl-ca-file=SSL_CA_FILE - File containing the SSL_CA to be used. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 cloudbuild/v2 API. The full documentation for this - API can be found at: https://cloud.google.com/cloud-build/docs/ - -NOTES - These variants are also available: - - $ gcloud alpha builds connections update bitbucket-data-center - - $ gcloud beta builds connections update bitbucket-data-center - diff --git a/gcloud/builds/connections/update/help b/gcloud/builds/connections/update/help index cb4141591..07871e5ba 100644 --- a/gcloud/builds/connections/update/help +++ b/gcloud/builds/connections/update/help @@ -15,12 +15,6 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - bitbucket-cloud - Update a Cloud Build Connection of type Bitbucket Cloud. - - bitbucket-data-center - Update a Cloud Build Connection of type Bitbucket Data Center. - github Update a Cloud Build Connection of type GitHub. diff --git a/gcloud/builds/triggers/create/bitbucket-cloud b/gcloud/builds/triggers/create/bitbucket-cloud deleted file mode 100644 index 8fb276812..000000000 --- a/gcloud/builds/triggers/create/bitbucket-cloud +++ /dev/null @@ -1,222 +0,0 @@ -NAME - gcloud builds triggers create bitbucket-cloud - create a build trigger for - a 2nd-gen Bitbucket Cloud repository - -SYNOPSIS - gcloud builds triggers create bitbucket-cloud - (--trigger-config=PATH | [(--branch-pattern=REGEX | --tag-pattern=REGEX - | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; - default="COMMENTS_ENABLED"]) (--build-config=PATH - | --inline-config=PATH - | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE - : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) - : --description=DESCRIPTION --ignored-files=[GLOB,...] - --included-files=[GLOB,...] --name=NAME --region=REGION - --repository=REPOSITORY --[no-]require-approval - --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - Create a build trigger for a 2nd-gen Bitbucket Cloud repository. - -EXAMPLES - To create a push trigger with a 2nd-gen repository for all branches: - - $ gcloud builds triggers create bitbucket-cloud \ - --name="my-trigger" \ - --service-account="projects/my-project/serviceAccounts/my-byosa@\ - my-project.iam.gserviceaccount.com" \ - --repository="projects/1234/locations/us-central1/connections/my\ - conn/repositories/myrepo" --branch-pattern=".*" \ - --build-config="cloudbuild.yaml" --region=us-central1 - - To create a pull request trigger with a 2nd-gen repository for main: - - $ gcloud builds triggers create bitbucket-cloud \ - --name="my-trigger" \ - --service-account="projects/my-project/serviceAccounts/my-byosa@\ - my-project.iam.gserviceaccount.com" \ - --repository="projects/1234/locations/us-central1/connections/my\ - conn/repositories/myrepo" --build-config="cloudbuild.yaml" \ - --pull-request-pattern="^main$" --region=us-central1 - -REQUIRED FLAGS - Exactly one of these must be specified: - - --trigger-config=PATH - Path to Build Trigger config file (JSON or YAML format). For more - details, see - https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger - - Flag based trigger configuration - - --description=DESCRIPTION - Build trigger description. - - --ignored-files=[GLOB,...] - Glob filter. Changes only affecting ignored files won't trigger - builds. - - --included-files=[GLOB,...] - Glob filter. Changes affecting at least one included file will - trigger builds. - - --name=NAME - Build trigger name. - - --region=REGION - The region of the Cloud Build Service to use. Must be set to a - supported region name (e.g. us-central1). If unset, builds/region, - which is the default region to use when working with Cloud Build - resources, is used. If builds/region is unset, region is set to - global. Note: Region must be specified in 2nd gen repo; global is - not supported. - - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - - --[no-]require-approval - Require manual approval for triggered builds. Use - --require-approval to enable and --no-require-approval to disable. - - --service-account=SERVICE_ACCOUNT - The service account used for all user-controlled operations - including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and - CancelBuild. If no service account is set, then the standard Cloud - Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is - used instead. Format: - projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - - --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. For - example: - - $ gcloud builds triggers create bitbucket-cloud ... \ - --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 - - This will result in a build where every occurrence of - ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and - similarly for ${_NUM_CANDIES} and "10". - - Substitutions can be applied to user-defined variables (starting - with an underscore) and to the following built-in variables: - REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, - SHORT_SHA. - - For more details, see: - https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values - - Exactly one of these must be specified: - - --branch-pattern=REGEX - A regular expression specifying which git branches to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --branch-pattern=foo will match - "foo", "foobar", and "barfoo". Events on a branch that does not - match will be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - --tag-pattern=REGEX - A regular expression specifying which git tags to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --tag-pattern=foo will match "foo", - "foobar", and "barfoo". Events on a tag that does not match will - be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - Pull Request settings - - --pull-request-pattern=REGEX - Regular expression specifying which base git branch to match - for pull request events. - - This pattern is used as a regex search for the base branch (the - branch you are trying to merge into) for pull request updates. - For example, --pull-request-pattern=foo will match "foo", - "foobar", and "barfoo". - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" - Require a repository collaborator or owner to comment '/gcbrun' - on a pull request before running the build. COMMENT_CONTROL - must be one of: - - COMMENTS_DISABLED - Do not require comments on Pull Requests before builds are - triggered. - COMMENTS_ENABLED - Enforce that repository owners or collaborators must - comment on Pull Requests before builds are triggered. - COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY - Enforce that repository owners or collaborators must - comment on external contributors' Pull Requests before - builds are triggered. - - Exactly one of these must be specified: - - --build-config=PATH - Path to a YAML or JSON file containing the build configuration in - the repository. - - For more details, see: - https://cloud.google.com/cloud-build/docs/build-config - - --inline-config=PATH - Local path to a YAML or JSON file containing a build - configuration. - - Dockerfile build configuration flags - - --dockerfile=DOCKERFILE - Path of Dockerfile to use for builds in the repository. - - If specified, a build config will be generated to run docker - build using the specified file. - - The filename is relative to the Dockerfile directory. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-image=DOCKERFILE_IMAGE - Docker image name to build. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-dir=DOCKERFILE_DIR; default="/" - Location of the directory containing the Dockerfile in the - repository. - - The directory will also be used as the Docker build context. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 builds triggers create bitbucket-cloud - - $ gcloud beta builds triggers create bitbucket-cloud - diff --git a/gcloud/builds/triggers/create/bitbucket-data-center b/gcloud/builds/triggers/create/bitbucket-data-center deleted file mode 100644 index db76e3dea..000000000 --- a/gcloud/builds/triggers/create/bitbucket-data-center +++ /dev/null @@ -1,222 +0,0 @@ -NAME - gcloud builds triggers create bitbucket-data-center - create a build - trigger for a 2nd-gen Bitbucket Data Center repository - -SYNOPSIS - gcloud builds triggers create bitbucket-data-center - (--trigger-config=PATH | [(--branch-pattern=REGEX | --tag-pattern=REGEX - | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; - default="COMMENTS_ENABLED"]) (--build-config=PATH - | --inline-config=PATH - | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE - : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) - : --description=DESCRIPTION --ignored-files=[GLOB,...] - --included-files=[GLOB,...] --name=NAME --region=REGION - --repository=REPOSITORY --[no-]require-approval - --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - Create a build trigger for a 2nd-gen Bitbucket Data Center repository. - -EXAMPLES - To create a push trigger with a 2nd-gen repository for all branches: - - $ gcloud builds triggers create bitbucket-data-center \ - --name="my-trigger" \ - --service-account="projects/my-project/serviceAccounts/my-byosa@\ - my-project.iam.gserviceaccount.com" \ - --repository="projects/1234/locations/us-central1/connections/my\ - conn/repositories/myrepo" --branch-pattern=".*" \ - --build-config="cloudbuild.yaml" --region=us-central1 - - To create a pull request trigger with a 2nd-gen repository for main: - - $ gcloud builds triggers create bitbucket-data-center \ - --name="my-trigger" \ - --service-account="projects/my-project/serviceAccounts/my-byosa@\ - my-project.iam.gserviceaccount.com" \ - --repository="projects/1234/locations/us-central1/connections/my\ - conn/repositories/myrepo" --build-config="cloudbuild.yaml" \ - --pull-request-pattern="^main$" --region=us-central1 - -REQUIRED FLAGS - Exactly one of these must be specified: - - --trigger-config=PATH - Path to Build Trigger config file (JSON or YAML format). For more - details, see - https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger - - Flag based trigger configuration - - --description=DESCRIPTION - Build trigger description. - - --ignored-files=[GLOB,...] - Glob filter. Changes only affecting ignored files won't trigger - builds. - - --included-files=[GLOB,...] - Glob filter. Changes affecting at least one included file will - trigger builds. - - --name=NAME - Build trigger name. - - --region=REGION - The region of the Cloud Build Service to use. Must be set to a - supported region name (e.g. us-central1). If unset, builds/region, - which is the default region to use when working with Cloud Build - resources, is used. If builds/region is unset, region is set to - global. Note: Region must be specified in 2nd gen repo; global is - not supported. - - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - - --[no-]require-approval - Require manual approval for triggered builds. Use - --require-approval to enable and --no-require-approval to disable. - - --service-account=SERVICE_ACCOUNT - The service account used for all user-controlled operations - including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and - CancelBuild. If no service account is set, then the standard Cloud - Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is - used instead. Format: - projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - - --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. For - example: - - $ gcloud builds triggers create bitbucket-data-center ... \ - --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 - - This will result in a build where every occurrence of - ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and - similarly for ${_NUM_CANDIES} and "10". - - Substitutions can be applied to user-defined variables (starting - with an underscore) and to the following built-in variables: - REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, - SHORT_SHA. - - For more details, see: - https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values - - Exactly one of these must be specified: - - --branch-pattern=REGEX - A regular expression specifying which git branches to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --branch-pattern=foo will match - "foo", "foobar", and "barfoo". Events on a branch that does not - match will be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - --tag-pattern=REGEX - A regular expression specifying which git tags to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --tag-pattern=foo will match "foo", - "foobar", and "barfoo". Events on a tag that does not match will - be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - Pull Request settings - - --pull-request-pattern=REGEX - Regular expression specifying which base git branch to match - for pull request events. - - This pattern is used as a regex search for the base branch (the - branch you are trying to merge into) for pull request updates. - For example, --pull-request-pattern=foo will match "foo", - "foobar", and "barfoo". - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" - Require a repository collaborator or owner to comment '/gcbrun' - on a pull request before running the build. COMMENT_CONTROL - must be one of: - - COMMENTS_DISABLED - Do not require comments on Pull Requests before builds are - triggered. - COMMENTS_ENABLED - Enforce that repository owners or collaborators must - comment on Pull Requests before builds are triggered. - COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY - Enforce that repository owners or collaborators must - comment on external contributors' Pull Requests before - builds are triggered. - - Exactly one of these must be specified: - - --build-config=PATH - Path to a YAML or JSON file containing the build configuration in - the repository. - - For more details, see: - https://cloud.google.com/cloud-build/docs/build-config - - --inline-config=PATH - Local path to a YAML or JSON file containing a build - configuration. - - Dockerfile build configuration flags - - --dockerfile=DOCKERFILE - Path of Dockerfile to use for builds in the repository. - - If specified, a build config will be generated to run docker - build using the specified file. - - The filename is relative to the Dockerfile directory. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-image=DOCKERFILE_IMAGE - Docker image name to build. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-dir=DOCKERFILE_DIR; default="/" - Location of the directory containing the Dockerfile in the - repository. - - The directory will also be used as the Docker build context. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 builds triggers create bitbucket-data-center - - $ gcloud beta builds triggers create bitbucket-data-center - diff --git a/gcloud/builds/triggers/create/help b/gcloud/builds/triggers/create/help index 889bfb238..892daf30b 100644 --- a/gcloud/builds/triggers/create/help +++ b/gcloud/builds/triggers/create/help @@ -16,12 +16,6 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - bitbucket-cloud - Create a build trigger for a 2nd-gen Bitbucket Cloud repository. - - bitbucket-data-center - Create a build trigger for a 2nd-gen Bitbucket Data Center repository. - bitbucketserver Create a build trigger for a Bitbucket Server repository. diff --git a/gcloud/builds/triggers/update/bitbucket-cloud b/gcloud/builds/triggers/update/bitbucket-cloud deleted file mode 100644 index 558a3609d..000000000 --- a/gcloud/builds/triggers/update/bitbucket-cloud +++ /dev/null @@ -1,251 +0,0 @@ -NAME - gcloud builds triggers update bitbucket-cloud - updates Bitbucket Cloud - trigger used by Cloud Build - -SYNOPSIS - gcloud builds triggers update bitbucket-cloud (TRIGGER : --region=REGION) - (--trigger-config=PATH | --description=DESCRIPTION - --ignored-files=[GLOB,...] --included-files=[GLOB,...] - --repository=REPOSITORY --[no-]require-approval - --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX - | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL - --pull-request-pattern=REGEX --build-config=PATH - | --inline-config=PATH - | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE - : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions - | --remove-substitutions=[KEY,...] - | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - Updates Bitbucket Cloud trigger used by Cloud Build. - -EXAMPLES - To update the branch pattern of the trigger: - - $ gcloud builds triggers update bitbucket-cloud my-trigger \ - --branch-pattern=".*" - - To update the build config of the trigger: - - $ gcloud builds triggers update bitbucket-cloud my-trigger \ - --build-config="cloudbuild.yaml" - - To update the substitutions of the trigger: - - $ gcloud builds triggers update bitbucket-cloud my-trigger \ - --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master - - To update the 2nd-gen repository resource of the trigger: - - $ gcloud builds triggers update bitbucket-cloud my-trigger \ - --repository=projects/my-project/locations/us-west1/\ - connections/my-conn/repositories/my-repo - -POSITIONAL ARGUMENTS - Trigger resource - Build Trigger. 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 TRIGGER 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. - - TRIGGER - ID of the trigger or fully qualified identifier for the trigger. - - To set the trigger attribute: - ▸ provide the argument TRIGGER 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 location for the trigger. - - To set the region attribute: - ▸ provide the argument TRIGGER on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -REQUIRED FLAGS - Exactly one of these must be specified: - - --trigger-config=PATH - Path to Build Trigger config file (JSON or YAML format). For more - details, see - https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger - - Flag based trigger configuration - - --description=DESCRIPTION - Build trigger description. - - --ignored-files=[GLOB,...] - Glob filter. Changes only affecting ignored files won't trigger - builds. - - --included-files=[GLOB,...] - Glob filter. Changes affecting at least one included file will - trigger builds. - - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - - --[no-]require-approval - Require manual approval for triggered builds. Use - --require-approval to enable and --no-require-approval to disable. - - --service-account=SERVICE_ACCOUNT - The service account used for all user-controlled operations - including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and - CancelBuild. If no service account is set, then the standard Cloud - Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is - used instead. Format: - projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - - At most one of these can be specified: - - --branch-pattern=REGEX - A regular expression specifying which git branches to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --branch-pattern=foo will match - "foo", "foobar", and "barfoo". Events on a branch that does not - match will be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - --tag-pattern=REGEX - A regular expression specifying which git tags to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --tag-pattern=foo will match "foo", - "foobar", and "barfoo". Events on a tag that does not match will - be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - Pull Request settings - - --comment-control=COMMENT_CONTROL - Require a repository collaborator or owner to comment '/gcbrun' - on a pull request before running the build. COMMENT_CONTROL - must be one of: - - COMMENTS_DISABLED - Do not require comments on Pull Requests before builds are - triggered. - COMMENTS_ENABLED - Enforce that repository owners or collaborators must - comment on Pull Requests before builds are triggered. - COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY - Enforce that repository owners or collaborators must - comment on external contributors' Pull Requests before - builds are triggered. - - --pull-request-pattern=REGEX - A regular expression specifying which base git branch to match - for pull request events. - - This pattern is used as a regular expression search for the - base branch (the branch you are trying to merge into) for pull - request updates. For example, --pull-request-pattern=foo will - match "foo", "foobar", and "barfoo". - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - At most one of these can be specified: - - --build-config=PATH - Path to a YAML or JSON file containing the build configuration in - the repository. - - For more details, see: - https://cloud.google.com/cloud-build/docs/build-config - - --inline-config=PATH - Local path to a YAML or JSON file containing a build - configuration. - - Dockerfile build configuration flags - - --dockerfile=DOCKERFILE - Path of Dockerfile to use for builds in the repository. - - If specified, a build config will be generated to run docker - build using the specified file. - - The filename is relative to the Dockerfile directory. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-image=DOCKERFILE_IMAGE - Docker image name to build. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-dir=DOCKERFILE_DIR - Location of the directory containing the Dockerfile in the - repository. - - The directory will also be used as the Docker build context. - - At most one of these can be specified: - - --clear-substitutions - Clear existing substitutions. - - --remove-substitutions=[KEY,...] - Remove existing substitutions if present. - - --update-substitutions=[KEY=VALUE,...] - Update or add to existing substitutions. Substitutions are - parameters to be substituted or add in the build specification. - - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers update ... - --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 - - This will add the provided substitutions to the existing - substitutions and results in a build where every occurrence of - ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and - similarly for ${_NUM_CANDIES} and "10". - - Only the following built-in variables can be specified with the - --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, - REVISION_ID, COMMIT_SHA, SHORT_SHA. - - For more details, see: - https://cloud.google.com/build/docs/build-config-file-schema#substitutions - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 builds triggers update bitbucket-cloud - - $ gcloud beta builds triggers update bitbucket-cloud - diff --git a/gcloud/builds/triggers/update/bitbucket-data-center b/gcloud/builds/triggers/update/bitbucket-data-center deleted file mode 100644 index 401c53961..000000000 --- a/gcloud/builds/triggers/update/bitbucket-data-center +++ /dev/null @@ -1,252 +0,0 @@ -NAME - gcloud builds triggers update bitbucket-data-center - updates Bitbucket - Data Center trigger used by Cloud Build - -SYNOPSIS - gcloud builds triggers update bitbucket-data-center - (TRIGGER : --region=REGION) - (--trigger-config=PATH | --description=DESCRIPTION - --ignored-files=[GLOB,...] --included-files=[GLOB,...] - --repository=REPOSITORY --[no-]require-approval - --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX - | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL - --pull-request-pattern=REGEX --build-config=PATH - | --inline-config=PATH - | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE - : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions - | --remove-substitutions=[KEY,...] - | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - Updates Bitbucket Data Center trigger used by Cloud Build. - -EXAMPLES - To update the branch pattern of the trigger: - - $ gcloud builds triggers update bitbucket-data-center my-trigger \ - --branch-pattern=".*" - - To update the build config of the trigger: - - $ gcloud builds triggers update bitbucket-data-center my-trigger \ - --build-config="cloudbuild.yaml" - - To update the substitutions of the trigger: - - $ gcloud builds triggers update bitbucket-data-center my-trigger \ - --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master - - To update the 2nd-gen repository resource of the trigger: - - $ gcloud builds triggers update bitbucket-data-center my-trigger \ - --repository=projects/my-project/locations/us-west1/\ - connections/my-conn/repositories/my-repo - -POSITIONAL ARGUMENTS - Trigger resource - Build Trigger. 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 TRIGGER 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. - - TRIGGER - ID of the trigger or fully qualified identifier for the trigger. - - To set the trigger attribute: - ▸ provide the argument TRIGGER 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 location for the trigger. - - To set the region attribute: - ▸ provide the argument TRIGGER on the command line with a fully - specified name; - ▸ provide the argument --region on the command line; - ▸ set the property builds/region. - -REQUIRED FLAGS - Exactly one of these must be specified: - - --trigger-config=PATH - Path to Build Trigger config file (JSON or YAML format). For more - details, see - https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger - - Flag based trigger configuration - - --description=DESCRIPTION - Build trigger description. - - --ignored-files=[GLOB,...] - Glob filter. Changes only affecting ignored files won't trigger - builds. - - --included-files=[GLOB,...] - Glob filter. Changes affecting at least one included file will - trigger builds. - - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - - --[no-]require-approval - Require manual approval for triggered builds. Use - --require-approval to enable and --no-require-approval to disable. - - --service-account=SERVICE_ACCOUNT - The service account used for all user-controlled operations - including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and - CancelBuild. If no service account is set, then the standard Cloud - Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is - used instead. Format: - projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - - At most one of these can be specified: - - --branch-pattern=REGEX - A regular expression specifying which git branches to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --branch-pattern=foo will match - "foo", "foobar", and "barfoo". Events on a branch that does not - match will be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - --tag-pattern=REGEX - A regular expression specifying which git tags to match. - - This pattern is used as a regular expression search for any - incoming pushes. For example, --tag-pattern=foo will match "foo", - "foobar", and "barfoo". Events on a tag that does not match will - be ignored. - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - Pull Request settings - - --comment-control=COMMENT_CONTROL - Require a repository collaborator or owner to comment '/gcbrun' - on a pull request before running the build. COMMENT_CONTROL - must be one of: - - COMMENTS_DISABLED - Do not require comments on Pull Requests before builds are - triggered. - COMMENTS_ENABLED - Enforce that repository owners or collaborators must - comment on Pull Requests before builds are triggered. - COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY - Enforce that repository owners or collaborators must - comment on external contributors' Pull Requests before - builds are triggered. - - --pull-request-pattern=REGEX - A regular expression specifying which base git branch to match - for pull request events. - - This pattern is used as a regular expression search for the - base branch (the branch you are trying to merge into) for pull - request updates. For example, --pull-request-pattern=foo will - match "foo", "foobar", and "barfoo". - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - At most one of these can be specified: - - --build-config=PATH - Path to a YAML or JSON file containing the build configuration in - the repository. - - For more details, see: - https://cloud.google.com/cloud-build/docs/build-config - - --inline-config=PATH - Local path to a YAML or JSON file containing a build - configuration. - - Dockerfile build configuration flags - - --dockerfile=DOCKERFILE - Path of Dockerfile to use for builds in the repository. - - If specified, a build config will be generated to run docker - build using the specified file. - - The filename is relative to the Dockerfile directory. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-image=DOCKERFILE_IMAGE - Docker image name to build. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --dockerfile-dir=DOCKERFILE_DIR - Location of the directory containing the Dockerfile in the - repository. - - The directory will also be used as the Docker build context. - - At most one of these can be specified: - - --clear-substitutions - Clear existing substitutions. - - --remove-substitutions=[KEY,...] - Remove existing substitutions if present. - - --update-substitutions=[KEY=VALUE,...] - Update or add to existing substitutions. Substitutions are - parameters to be substituted or add in the build specification. - - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers update ... - --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 - - This will add the provided substitutions to the existing - substitutions and results in a build where every occurrence of - ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and - similarly for ${_NUM_CANDIES} and "10". - - Only the following built-in variables can be specified with the - --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, - REVISION_ID, COMMIT_SHA, SHORT_SHA. - - For more details, see: - https://cloud.google.com/build/docs/build-config-file-schema#substitutions - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 builds triggers update bitbucket-data-center - - $ gcloud beta builds triggers update bitbucket-data-center - diff --git a/gcloud/builds/triggers/update/help b/gcloud/builds/triggers/update/help index 30a4b34d7..a5529e459 100644 --- a/gcloud/builds/triggers/update/help +++ b/gcloud/builds/triggers/update/help @@ -15,12 +15,6 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - bitbucket-cloud - Updates Bitbucket Cloud trigger used by Cloud Build. - - bitbucket-data-center - Updates Bitbucket Data Center trigger used by Cloud Build. - bitbucketserver Updates Bitbucket Server trigger used by Cloud Build. diff --git a/gcloud/compute/disks/create b/gcloud/compute/disks/create index a3e85acf1..e86f396cd 100644 --- a/gcloud/compute/disks/create +++ b/gcloud/compute/disks/create @@ -15,7 +15,9 @@ SYNOPSIS [--image-family-scope=IMAGE_FAMILY_SCOPE --image-project=IMAGE_PROJECT --image=IMAGE | --image-family=IMAGE_FAMILY | --primary-disk=PRIMARY_DISK - | --source-disk=SOURCE_DISK | --source-snapshot=SOURCE_SNAPSHOT] + | --source-disk=SOURCE_DISK + | --source-instant-snapshot=SOURCE_INSTANT_SNAPSHOT + | --source-snapshot=SOURCE_SNAPSHOT] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [--primary-disk-region=PRIMARY_DISK_REGION @@ -201,6 +203,9 @@ FLAGS The source disk must be in the same zone/region as the disk to be created. + --source-instant-snapshot=SOURCE_INSTANT_SNAPSHOT + Name of the source instant snapshot used to create the disks. + --source-snapshot=SOURCE_SNAPSHOT Source snapshot used to create the disks. It is safe to delete a snapshot after a disk has been created from the snapshot. In such diff --git a/gcloud/compute/help b/gcloud/compute/help index 1c5b2327d..2b11f3e2b 100644 --- a/gcloud/compute/help +++ b/gcloud/compute/help @@ -81,6 +81,9 @@ GROUPS instances Read and manipulate Compute Engine virtual machine instances. + instant-snapshots + Create, list and delete Compute Engine instant snapshots. + interconnects Read and manipulate Compute Engine interconnects. diff --git a/gcloud/compute/images/import b/gcloud/compute/images/import index 986b8bde6..1cd8f8430 100644 --- a/gcloud/compute/images/import +++ b/gcloud/compute/images/import @@ -31,6 +31,11 @@ DESCRIPTION all four of these steps as required, depending on the input arguments specified. + Before importing an image, set up access to Cloud Storage and grant + required roles to the user accounts and service accounts. For more + information, see + https://cloud.google.com/compute/docs/import/requirements-export-import-images. + To override the detected OS, specify the --os flag. You can omit the translation step using the --data-disk flag. diff --git a/gcloud/compute/instance-groups/managed/all-instances-config/delete b/gcloud/compute/instance-groups/managed/all-instances-config/delete new file mode 100644 index 000000000..c64a32ec8 --- /dev/null +++ b/gcloud/compute/instance-groups/managed/all-instances-config/delete @@ -0,0 +1,86 @@ +NAME + gcloud compute instance-groups managed all-instances-config delete - delete + values defined in the all-instances configuration of a managed instance + group + +SYNOPSIS + gcloud compute instance-groups managed all-instances-config delete NAME + [--labels=KEY,[KEY,...]] [--metadata=KEY,[KEY,...]] + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instance-groups managed all-instances-config delete deletes + one or more values defined in the all-instances configuration of a managed + instance group. + + To apply a revised all-instances configuration to existing instances in the + group, use one of the following methods: + + ▪ Update instances using the update-instances command. + ▪ Recreate instances using the recreate-instances command. + ▪ Use the rolling-action start-update command. + ▪ Use the API to set the group's updatePolicy.type to PROACTIVE. + +EXAMPLES + To delete the group's all-instances configuration in order to stop + overriding the group's instance template for a label with the key label-key + and metadata with the key metadata-key in group my-group, run: + + $ gcloud compute instance-groups managed all-instances-config \ + delete my-group --metadata=metadata-key --labels=label-key + +POSITIONAL ARGUMENTS + NAME + Name of the managed instance group to delete the all instances + configuration for. + +FLAGS + --labels=KEY,[KEY,...] + Remove labels keys from the group's all instances configuration. + + --metadata=KEY,[KEY,...] + Remove metadata keys from the group's all instances configuration. + + At most one of these can be specified: + + --region=REGION + Region of the managed instance group to delete the all instances + configuration for. If not specified, you might be prompted to select + a region (interactive mode only). + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + Overrides the default compute/region property value for this command + invocation. + + --zone=ZONE + Zone of the managed instance group to delete the all instances + configuration for. If not specified, you might be prompted to select + a zone (interactive mode only). + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instance-groups managed \ + all-instances-config delete + + $ gcloud beta compute instance-groups managed all-instances-config \ + delete + diff --git a/gcloud/compute/instance-groups/managed/all-instances-config/help b/gcloud/compute/instance-groups/managed/all-instances-config/help new file mode 100644 index 000000000..a7cf0cb91 --- /dev/null +++ b/gcloud/compute/instance-groups/managed/all-instances-config/help @@ -0,0 +1,35 @@ +NAME + gcloud compute instance-groups managed all-instances-config - override + instance template settings for all instances in a managed instance + group + +SYNOPSIS + gcloud compute instance-groups managed all-instances-config COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Override instance template settings for all instances in a managed instance + group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + Delete values defined in the all-instances configuration of a managed + instance group. + + update + Update the all-instances configuration of a managed instance group. + +NOTES + These variants are also available: + + $ gcloud alpha compute instance-groups managed all-instances-config + + $ gcloud beta compute instance-groups managed all-instances-config + diff --git a/gcloud/compute/instance-groups/managed/all-instances-config/update b/gcloud/compute/instance-groups/managed/all-instances-config/update new file mode 100644 index 000000000..4ce63f6c3 --- /dev/null +++ b/gcloud/compute/instance-groups/managed/all-instances-config/update @@ -0,0 +1,88 @@ +NAME + gcloud compute instance-groups managed all-instances-config update - update + the all-instances configuration of a managed instance group + +SYNOPSIS + gcloud compute instance-groups managed all-instances-config update NAME + [--labels=KEY=VALUE,[KEY=VALUE,...]] + [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--region=REGION | --zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instance-groups managed all-instances-config update updates + the group's all-instances configuration and applies it only to new + instances that are added to the group. + + To apply a revised all-instances configuration to existing instances in the + group, use one of the following methods: + + ▪ Update instances using the update-instances command. + ▪ Recreate instances using the recreate-instances command. + ▪ Use the rolling-action start-update command. + ▪ Use the API to set the group's updatePolicy.type to PROACTIVE. + +EXAMPLES + To update an all-instances configuration in order to override the group's + instance template for a label with the key label-key and metadata with the + key metadata-key in group my-group, run: + + $ gcloud compute instance-groups managed all-instances-config \ + update my-group \ + --metadata=metadata-key=metadata-override-value \ + --labels=qlabel-key=label-override-value + +POSITIONAL ARGUMENTS + NAME + Name of the managed instance group to update the all instances + configuration for. + +FLAGS + --labels=KEY=VALUE,[KEY=VALUE,...] + Add labels to the group's all instances configuration. + + --metadata=KEY=VALUE,[KEY=VALUE,...] + Add metadata to the group's all instances configuration. + + At most one of these can be specified: + + --region=REGION + Region of the managed instance group to update the all instances + configuration for. If not specified, you might be prompted to select + a region (interactive mode only). + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + Overrides the default compute/region property value for this command + invocation. + + --zone=ZONE + Zone of the managed instance group to update the all instances + configuration for. If not specified, you might be prompted to select + a zone (interactive mode only). + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instance-groups managed \ + all-instances-config update + + $ gcloud beta compute instance-groups managed all-instances-config \ + update + diff --git a/gcloud/compute/instance-groups/managed/create b/gcloud/compute/instance-groups/managed/create index f3817df14..224366f1f 100644 --- a/gcloud/compute/instance-groups/managed/create +++ b/gcloud/compute/instance-groups/managed/create @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud compute instance-groups managed create NAME --size=SIZE --template=TEMPLATE [--base-instance-name=BASE_INSTANCE_NAME] + [--default-action-on-vm-failure=ACTION_ON_VM_FAILURE] [--description=DESCRIPTION] [--[no-]force-update-on-repair] [--initial-delay=INITIAL_DELAY] [--instance-redistribution-type=TYPE] [--list-managed-instances-results=MODE] @@ -71,6 +72,17 @@ OPTIONAL FLAGS with the managed instance group. If not provided base instance name will be the prefix of instance group name. + --default-action-on-vm-failure=ACTION_ON_VM_FAILURE + Specifies the action that a MIG performs on a failed or an unhealthy + VM. A VM is marked as unhealthy when the application running on that VM + fails a health check. By default, the value of the flag is set to + repair. ACTION_ON_VM_FAILURE must be one of: + + do-nothing + MIG does not repair a failed or an unhealthy VM. + repair + MIG automatically repairs a failed or an unhealthy VM. + --description=DESCRIPTION An optional description for this group. diff --git a/gcloud/compute/instance-groups/managed/help b/gcloud/compute/instance-groups/managed/help index db75f30c6..0a3799384 100644 --- a/gcloud/compute/instance-groups/managed/help +++ b/gcloud/compute/instance-groups/managed/help @@ -17,6 +17,10 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + all-instances-config + Override instance template settings for all instances in a managed + instance group. + instance-configs Manage instance-specific settings in a managed instance group. diff --git a/gcloud/compute/instance-groups/managed/update b/gcloud/compute/instance-groups/managed/update index 9984aa7ed..3d14c40ea 100644 --- a/gcloud/compute/instance-groups/managed/update +++ b/gcloud/compute/instance-groups/managed/update @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud compute instance-groups managed update NAME + [--default-action-on-vm-failure=ACTION_ON_VM_FAILURE] [--description=DESCRIPTION] [--[no-]force-update-on-repair] [--instance-redistribution-type=TYPE] [--list-managed-instances-results=MODE] @@ -60,6 +61,17 @@ POSITIONAL ARGUMENTS Name of the managed instance group to update. FLAGS + --default-action-on-vm-failure=ACTION_ON_VM_FAILURE + Specifies the action that a MIG performs on a failed or an unhealthy + VM. A VM is marked as unhealthy when the application running on that VM + fails a health check. By default, the value of the flag is set to + repair. ACTION_ON_VM_FAILURE must be one of: + + do-nothing + MIG does not repair a failed or an unhealthy VM. + repair + MIG automatically repairs a failed or an unhealthy VM. + --description=DESCRIPTION An optional description for this group. To clear the description, set the value to an empty string. diff --git a/gcloud/compute/instant-snapshots/add-labels b/gcloud/compute/instant-snapshots/add-labels new file mode 100644 index 000000000..a366bc8c1 --- /dev/null +++ b/gcloud/compute/instant-snapshots/add-labels @@ -0,0 +1,96 @@ +NAME + gcloud compute instant-snapshots add-labels - add labels to Google Compute + Engine instant-snapshotss + +SYNOPSIS + gcloud compute instant-snapshots add-labels INSTANT_SNAPSHOT_NAME + --labels=[KEY=VALUE,...] [--region=REGION | --zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instant-snapshots add-labels adds labels to a Google Compute + Engine instant-snapshots. + +EXAMPLES + To add key-value pairs k0=v0 and k1=v1 to 'example-instant-snapshots' + + $ gcloud compute instant-snapshots add-labels \ + example-instant-snapshots --labels=k0=v0,k1=v1 + + Labels can be used to identify the instant-snapshots and to filter them. To + find a instant-snapshots labeled with key-value pair k1, v2 + + $ gcloud compute instant-snapshots list --filter='labels.k1:v2' + + To list only the labels when describing a resource, use --format + + $ gcloud compute instant-snapshots describe \ + example-instant-snapshots --format='default(labels)' + +POSITIONAL ARGUMENTS + INSTANT_SNAPSHOT_NAME + Name of the instant snapshot to operate on. + +REQUIRED FLAGS + --labels=[KEY=VALUE,...] + A list of labels to add. + +OPTIONAL FLAGS + At most one of these can be specified: + + --region=REGION + Region of the instant snapshot to operate on. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --zone=ZONE + Zone of the instant snapshot to operate on. If not specified and the + compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instant-snapshots add-labels + + $ gcloud beta compute instant-snapshots add-labels + diff --git a/gcloud/compute/instant-snapshots/create b/gcloud/compute/instant-snapshots/create new file mode 100644 index 000000000..82b847511 --- /dev/null +++ b/gcloud/compute/instant-snapshots/create @@ -0,0 +1,100 @@ +NAME + gcloud compute instant-snapshots create - create a Compute Engine instant + snapshot + +SYNOPSIS + gcloud compute instant-snapshots create INSTANT_SNAPSHOT_NAME + --source-disk=SOURCE_DISK [--labels=[KEY=VALUE,...]] + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instant-snapshots create creates an instant snapshot of + persistent disk. Instant snapshots are useful for backing up persistent + disk data. + +EXAMPLES + To create an instant snapshot 'my-instant-snap' from a disk 'my-disk' in + zone 'us-east1-a', run: + + $ gcloud compute instant-snapshots create my-instant-snap \ + --source-disk=my-disk --zone=us-east1-a + +POSITIONAL ARGUMENTS + INSTANT_SNAPSHOT_NAME + Name of the instant snapshot to create. + +REQUIRED FLAGS + Source disk options + + This must be specified. + + --source-disk=SOURCE_DISK + Source disk used to create the instant snapshot. + +OPTIONAL FLAGS + --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: + + --region=REGION + Region of the instant snapshot 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 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 + These variants are also available: + + $ gcloud alpha compute instant-snapshots create + + $ gcloud beta compute instant-snapshots create + diff --git a/gcloud/compute/instant-snapshots/delete b/gcloud/compute/instant-snapshots/delete new file mode 100644 index 000000000..2bc8b0829 --- /dev/null +++ b/gcloud/compute/instant-snapshots/delete @@ -0,0 +1,93 @@ +NAME + gcloud compute instant-snapshots delete - delete a Compute Engine instant + snapshot + +SYNOPSIS + gcloud compute instant-snapshots delete INSTANT_SNAPSHOT_NAME + [INSTANT_SNAPSHOT_NAME ...] [--region=REGION | --zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instant-snapshots delete deletes a Compute Engine instant + snapshot. A disk can be deleted only if it is not attached to any virtual + machine instances. + +EXAMPLES + To delete Compute Engine instant snapshots with the names + 'instant-snapshot-1' and 'instant-snapshot-2', run: + + $ gcloud compute instant-snapshots delete instant-snapshot-1 \ + instant-snapshot-2 + + To list all instant snapshots that were created before a specific date, use + the --filter flag with the gcloud compute instant-snapshots list command. + + $ gcloud compute instant-snapshots list \ + --filter="creationTimestamp<'2017-01-01'" + + For more information on how to use --filter with the list command, run $ + gcloud topic filters. + +POSITIONAL ARGUMENTS + INSTANT_SNAPSHOT_NAME [INSTANT_SNAPSHOT_NAME ...] + Names of the instant snapshots to delete. + +FLAGS + At most one of these can be specified: + + --region=REGION + Region of the instant snapshots to delete. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --zone=ZONE + Zone of the instant snapshots to delete. If not specified and the + compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instant-snapshots delete + + $ gcloud beta compute instant-snapshots delete + diff --git a/gcloud/compute/instant-snapshots/describe b/gcloud/compute/instant-snapshots/describe new file mode 100644 index 000000000..cac44814c --- /dev/null +++ b/gcloud/compute/instant-snapshots/describe @@ -0,0 +1,82 @@ +NAME + gcloud compute instant-snapshots describe - describe a Compute Engine + instant snapshot + +SYNOPSIS + gcloud compute instant-snapshots describe INSTANT_SNAPSHOT_NAME + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instant-snapshots describe displays all data associated with + a Compute Engine instant snapshot in a project. + +EXAMPLES + To describe the instant snapshot 'instant-snapshot-1' in zone 'us-east1-a', + run: + + $ gcloud compute instant-snapshots describe instant-snapshot-1 \ + --zone=us-east1-a + +POSITIONAL ARGUMENTS + INSTANT_SNAPSHOT_NAME + Name of the instant snapshot to describe. + +FLAGS + At most one of these can be specified: + + --region=REGION + Region of the instant snapshot 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 to describe. If not specified and the + compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instant-snapshots describe + + $ gcloud beta compute instant-snapshots describe + diff --git a/gcloud/compute/instant-snapshots/help b/gcloud/compute/instant-snapshots/help new file mode 100644 index 000000000..72f96109e --- /dev/null +++ b/gcloud/compute/instant-snapshots/help @@ -0,0 +1,43 @@ +NAME + gcloud compute instant-snapshots - create, list and delete Compute Engine + instant snapshots + +SYNOPSIS + gcloud compute instant-snapshots COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List, create, describe, and delete Compute Engine instant snapshots. + + See also: Snapshots API + (https://cloud.google.com/compute/docs/reference/rest/beta/instantSnapshots). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-labels + Add labels to Google Compute Engine instant-snapshotss. + + create + Create a Compute Engine instant snapshot. + + delete + Delete a Compute Engine instant snapshot. + + describe + Describe a Compute Engine instant snapshot. + + list + List Google Compute Engine instant snapshots. + +NOTES + These variants are also available: + + $ gcloud alpha compute instant-snapshots + + $ gcloud beta compute instant-snapshots + diff --git a/gcloud/compute/instant-snapshots/list b/gcloud/compute/instant-snapshots/list new file mode 100644 index 000000000..e40fe834e --- /dev/null +++ b/gcloud/compute/instant-snapshots/list @@ -0,0 +1,113 @@ +NAME + gcloud compute instant-snapshots list - list Google Compute Engine instant + snapshots + +SYNOPSIS + gcloud compute instant-snapshots list [NAME ...] + [--regexp=REGEXP, -r REGEXP] + [--regions=[REGION,...] | --zones=[ZONE,...]] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instant-snapshots list displays all Google Compute Engine + instant snapshots in a project. + + By default, instant snapshots from all regions and instant snapshots from + all zones are listed. The results can be narrowed down by providing the + --regions or --zones flag. + +EXAMPLES + To list all instant snapshots in a project in table form, run: + + $ gcloud compute instant-snapshots list + + To list the URIs of all instant snapshots in a project, run: + + $ gcloud compute instant-snapshots list --uri + + To list all instant snapshots in the us-central1 and europe-west1 regions, + given they are regional resources, run: + + $ gcloud compute instant-snapshots list \ + --filter="region:( europe-west1 us-central1 )" + + To list all instant snapshots in zones us-central1-b and europe-west1-d, + given they are zonal resources, run: + + $ gcloud compute instant-snapshots list \ + --filter="zone:( europe-west1-d us-central1-b )" + +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. + + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. + +FLAGS + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. + + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + + At most one of these can be specified: + + --regions=[REGION,...] + If provided, only regional resources are shown. If arguments are + provided, only resources from the given regions are shown. + + --zones=[ZONE,...] + If provided, only zonal resources are shown. If arguments are + provided, only resources from the given zones are shown. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instant-snapshots list + + $ gcloud beta compute instant-snapshots list + diff --git a/gcloud/compute/snapshots/create b/gcloud/compute/snapshots/create index 69ad31d0f..caddc7da4 100644 --- a/gcloud/compute/snapshots/create +++ b/gcloud/compute/snapshots/create @@ -8,9 +8,14 @@ SYNOPSIS [--source-disk=SOURCE_DISK] [--source-disk-for-recovery-checkpoint=SOURCE_DISK_FOR_RECOVERY_CHECKPOINT] [--source-disk-for-recovery-checkpoint-region=SOURCE_DISK_FOR_RECOVERY_CHECKPOINT_REGION] - [--source-disk-key-file=FILE] [--storage-location=LOCATION] + [--source-disk-key-file=FILE] + [--source-instant-snapshot=SOURCE_INSTANT_SNAPSHOT] + [--source-instant-snapshot-key-file=FILE] [--storage-location=LOCATION] [--source-disk-region=SOURCE_DISK_REGION - | --source-disk-zone=SOURCE_DISK_ZONE] [GCLOUD_WIDE_FLAG ...] + | --source-disk-zone=SOURCE_DISK_ZONE] + [--source-instant-snapshot-region=SOURCE_INSTANT_SNAPSHOT_REGION + | --source-instant-snapshot-zone=SOURCE_INSTANT_SNAPSHOT_ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute snapshots create creates snapshot of persistent disk. @@ -94,6 +99,20 @@ FLAGS Required if the source disk is protected by a customer-supplied encryption key. + --source-instant-snapshot=SOURCE_INSTANT_SNAPSHOT + The name or URL of the source instant snapshot. If the name is + provided, the instant snapshot's zone or region must be specified with + --source-instant-snapshot-zone or --source-instant-snapshot-region + accordingly. To create a snapshot from an instant snapshot in a + different project, specify the full path to the instant snapshot. If + the URL is provided, format should be: + https://www.googleapis.com/compute/v1/projects/MY-PROJECT/zones/MY-ZONE/instantSnapshots/MY-INSTANT-SNAPSHOT + + --source-instant-snapshot-key-file=FILE + Path to the customer-supplied encryption key of the source instant + snapshot. Required if the source instant snapshot is protected by a + customer-supplied encryption key. + --storage-location=LOCATION Google Cloud Storage location, either regional or multi-regional, where snapshot content is to be stored. If absent, a nearby regional or @@ -109,6 +128,16 @@ FLAGS Zone of the source disk to operate on. Overrides the default compute/zone property value for this command invocation. + At most one of these can be specified: + + --source-instant-snapshot-region=SOURCE_INSTANT_SNAPSHOT_REGION + Region of the source instant snapshot to operate on. Overrides the + default compute/region property value for this command invocation. + + --source-instant-snapshot-zone=SOURCE_INSTANT_SNAPSHOT_ZONE + Zone of the source instant snapshot to operate on. Overrides the + default compute/zone property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/config/get b/gcloud/config/get index 6e400b755..287c06bd0 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -486,6 +486,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/config/help b/gcloud/config/help index e1b4ebc52..9c7a5c803 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -518,6 +518,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/config/list b/gcloud/config/list index 53fee5071..85df477e4 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -530,6 +530,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/config/set b/gcloud/config/set index 1fd2bfd99..104cc229f 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -533,6 +533,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/config/unset b/gcloud/config/unset index 2ef8aa216..86e86a323 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -494,6 +494,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud org-policies command group. Defaults to https://orgpolicy.googleapis.com/ + pam + Overrides API endpoint for gcloud pam command group. + policyanalyzer Overrides API endpoint for policy-intelligence command group. Defaults to https://policyanalyzer.googleapis.com/ diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 41d581029..1721a71bd 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -1269,7 +1269,7 @@ FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - (DEPRECATED) Select Advanced Datapath Observability mode for the + (REMOVED) Select Advanced Datapath Observability mode for the cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into @@ -1286,10 +1286,7 @@ FLAGS $ gcloud container clusters create \ --dataplane-v2-observability-mode=EXTERNAL_LB - The --dataplane-v2-observability-mode flag is deprecated and will be - removed in an upcoming release. Please use - --enable-dataplane-v2-flow-observability or - --disable-dataplane-v2-flow-observability. + Flag --dataplane-v2-observability-mode has been removed. DATAPLANE_V2_OBSERVABILITY_MODE must be one of: diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 9959143e9..0dd92a6bd 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -387,7 +387,7 @@ FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - (DEPRECATED) Select Advanced Datapath Observability mode for the + (REMOVED) Select Advanced Datapath Observability mode for the cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into @@ -404,10 +404,7 @@ FLAGS $ gcloud container clusters create-auto \ --dataplane-v2-observability-mode=EXTERNAL_LB - The --dataplane-v2-observability-mode flag is deprecated and will be - removed in an upcoming release. Please use - --enable-dataplane-v2-flow-observability or - --disable-dataplane-v2-flow-observability. + Flag --dataplane-v2-observability-mode has been removed. DATAPLANE_V2_OBSERVABILITY_MODE must be one of: diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index bff9148dc..a5f04d3f4 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -870,7 +870,7 @@ REQUIRED FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - (DEPRECATED) Select Advanced Datapath Observability mode for the + (REMOVED) Select Advanced Datapath Observability mode for the cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into @@ -887,10 +887,7 @@ REQUIRED FLAGS $ gcloud container clusters update \ --dataplane-v2-observability-mode=EXTERNAL_LB - The --dataplane-v2-observability-mode flag is deprecated and will - be removed in an upcoming release. Please use - --enable-dataplane-v2-flow-observability or - --disable-dataplane-v2-flow-observability. + Flag --dataplane-v2-observability-mode has been removed. DATAPLANE_V2_OBSERVABILITY_MODE must be one of: diff --git a/gcloud/container/node-pools/delete b/gcloud/container/node-pools/delete index 182b93fce..3d0bc427d 100644 --- a/gcloud/container/node-pools/delete +++ b/gcloud/container/node-pools/delete @@ -10,9 +10,9 @@ SYNOPSIS DESCRIPTION gcloud container node-pools delete deletes a node pool from a Google Kubernetes Engine (GKE) cluster. When you delete a node pool, GKE drains - all the nodes in the node pool. The draining process involves GKE evicting + all the nodes in the node pool. The draining process involves GKE deleting Pods on each node in the node pool. Each node in a node pool is drained by - evicting Pods with an allotted graceful termination period of MAX_POD. + deleting Pods with an allotted graceful termination period of MAX_POD. MAX_POD is the maximum terminationGracePeriodSeconds set on the Pods scheduled to the node with a cap of one hour. diff --git a/gcloud/iap/settings/set b/gcloud/iap/settings/set index e214bbd97..17da87ca4 100644 --- a/gcloud/iap/settings/set +++ b/gcloud/iap/settings/set @@ -13,46 +13,47 @@ DESCRIPTION EXAMPLES To set the IAP setting for the resources within an organization, run: - $ gcloud iap settings set SETTING_FILE --organization=ORGANIZATION_ID + $ gcloud iap settings set iap_settings.yaml \ + --organization=ORGANIZATION_ID To set the IAP setting for the resources within a folder, run: - $ gcloud iap settings set SETTING_FILE --folder=FOLDER_ID + $ gcloud iap settings set iap_settings.yaml --folder=FOLDER_ID To set the IAP setting for the resources within a project, run: - $ gcloud iap settings set SETTING_FILE --project=PROJECT_ID + $ gcloud iap settings set iap_settings.yaml --project=PROJECT_ID To set the IAP setting for web type resources within a project, run: - $ gcloud iap settings set SETTING_FILE --project=PROJECT_ID \ + $ gcloud iap settings set iap_settings.yaml --project=PROJECT_ID \ --resource-type=iap_web To set the IAP setting for all app engine services within a project, run: - $ gcloud iap settings set SETTING_FILE --project=PROJECT_ID \ + $ gcloud iap settings set iap_settings.yaml --project=PROJECT_ID \ --resource-type=app-engine To set the IAP setting for an app engine service within a project, run: - $ gcloud iap settings set SETTING_FILE --project=PROJECT_ID \ + $ gcloud iap settings set iap_settings.yaml --project=PROJECT_ID \ --resource-type=app-engine --service=SERVICE_ID To set the IAP setting for an app engine service version within a project, run: - $ gcloud iap settings set SETTING_FILE --project=PROJECT_ID \ + $ gcloud iap settings set iap_settings.yaml --project=PROJECT_ID \ --resource-type=app-engine --service=SERVICE_ID \ --version=VERSION_ID To set the IAP setting for all backend services within a project, run: - $ gcloud iap settings set SETTING_FILE --project=PROJECT_ID \ + $ gcloud iap settings set iap_settings.yaml --project=PROJECT_ID \ --resource-type=compute To set the IAP setting for a backend service within a project, run: - $ gcloud iap settings set SETTING_FILE --project=PROJECT_ID \ + $ gcloud iap settings set iap_settings.yaml --project=PROJECT_ID \ --resource-type=compute --service=SERVICE_ID POSITIONAL ARGUMENTS diff --git a/gcloud/infra-manager/previews/export b/gcloud/infra-manager/previews/export index 6b69433d2..22beb0ec6 100644 --- a/gcloud/infra-manager/previews/export +++ b/gcloud/infra-manager/previews/export @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud infra-manager previews export (PREVIEW : --location=LOCATION) - [--file=FILE; default="preview"] [GCLOUD_WIDE_FLAG ...] + [--file=FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command generates a signed url to download a preview results. @@ -47,7 +47,7 @@ POSITIONAL ARGUMENTS ▸ set the property infra-manager/location. FLAGS - --file=FILE; default="preview" + --file=FILE File name for preview export artifacts. It is optional and if --file is specified with a name or complete path, the artifacts will be downloaded to either the current directory with files named as the name diff --git a/gcloud/scc/bqexports/create b/gcloud/scc/bqexports/create index add52e220..f3f285590 100644 --- a/gcloud/scc/bqexports/create +++ b/gcloud/scc/bqexports/create @@ -1,76 +1,65 @@ NAME - gcloud scc bqexports create - create a Cloud Security Command Center - BigQuery export + gcloud scc bqexports create - create a Security Command Center BigQuery + export SYNOPSIS gcloud scc bqexports create BIG_QUERY_EXPORT --dataset=DATASET [--description=DESCRIPTION] [--filter=FILTER] + [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Create a Cloud Security Command Center BigQuery export. + Create a Security Command Center BigQuery export. + + BigQuery exports that are created with Security Command Center API V2 and + later include a location attribute. If a location is not specified, the + default global location is used. For example, the following BigQuery export + name has location=global attribute: + organizations/123/locations/global/bigQueryExports/test-bq-export. EXAMPLES - To create a BigQuery export my-bq-export given organization 123 with a + To create a BigQuery export test-bq-export given organization 123 with a dataset abc in project 234 and filter on category that equals to XSS_SCRIPTING, run: - $ gcloud scc bqexports create my-bq-export \ - --organization=organizations/123 \ - --dataset=projects/234/datasets/abc \ - --description="This is a test BigQuery export" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc bqexports create my-bq-export --organization=123 \ - --dataset=projects/234/datasets/abc \ - --description="This is a test BigQuery export" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc bqexports create \ - organizations/123/bigQueryExports/my-bq-export \ + $ gcloud scc bqexports create test-bq-export --organization=123 \ --dataset=projects/234/datasets/abc \ --description="This is a test BigQuery export" \ --filter="category=\"XSS_SCRIPTING\"" - To create a BigQuery export my-bq-export given folder 456 with a dataset + To create a BigQuery export test-bq-export given folder 456 with a dataset abc in project 234 and filter on category that equals to XSS_SCRIPTING, run: - $ gcloud scc bqexports create my-bq-export --folder=folders/456 \ - --dataset=projects/234/datasets/abc \ - --description="This is a test BigQuery export" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc bqexports create my-bq-export --folder=456 \ - --dataset=projects/234/datasets/abc \ - --description="This is a test BigQuery export" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc bqexports create \ - folders/456/bigQueryExports/my-bq-export \ + $ gcloud scc bqexports create test-bq-export --folder=456 \ --dataset=projects/234/datasets/abc \ --description="This is a test BigQuery export" \ --filter="category=\"XSS_SCRIPTING\"" - To create a BigQuery export my-bq-export given project 789 with a dataset + To create a BigQuery export test-bq-export given project 789 with a dataset abc in project 234 and filter on category that equals to XSS_SCRIPTING, run: - $ gcloud scc bqexports create my-bq-export --project=projects/789 \ + $ gcloud scc bqexports create test-bq-export --project=789 \ --dataset=projects/234/datasets/abc \ --description="This is a test BigQuery export" \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc bqexports create my-bq-export --project=789 \ + + To create a BigQuery export test-bq-export given organization 123 and + location=global to send findings with category=XSS_SCRIPTING to the + BigQuery dataset abc in project 234, run: + + $ gcloud scc bqexports create test-bq-export --organization=123 \ --dataset=projects/234/datasets/abc \ --description="This is a test BigQuery export" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc bqexports create \ - projects/789/bigQueryExports/my-bq-export \ - --dataset=projects/234/datasets/abc \ - --description="This is a test BigQuery export" \ - --filter="category=\"XSS_SCRIPTING\"" + --filter="category=\"XSS_SCRIPTING\"" --location=global POSITIONAL ARGUMENTS BIG_QUERY_EXPORT - ID of the BigQuery export or the full resource name of the BigQuery - export. + ID of the BigQuery export e.g. my-bq-export or the full resource name + of the BigQuery export e.g. + organizations/123/bigQueryExports/my-bq-export. REQUIRED FLAGS --dataset=DATASET @@ -84,6 +73,17 @@ OPTIONAL FLAGS The filter string which will applied to findings muted by a BigQuery export. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -107,5 +107,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) diff --git a/gcloud/scc/bqexports/delete b/gcloud/scc/bqexports/delete index ea91fee7d..af6b3cdcf 100644 --- a/gcloud/scc/bqexports/delete +++ b/gcloud/scc/bqexports/delete @@ -1,45 +1,60 @@ NAME - gcloud scc bqexports delete - delete a Cloud Security Command Center - BigQuery export + gcloud scc bqexports delete - delete a Security Command Center BigQuery + export SYNOPSIS gcloud scc bqexports delete BIG_QUERY_EXPORT + [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Delete a Cloud Security Command Center BigQuery export. + Delete a Security Command Center BigQuery export. + + BigQuery exports that are created with Security Command Center API V2 and + later include a location attribute. If the location attribute is included + in the resource name of a BigQuery export, you must specify it when + referencing the export. For example, the following BigQuery export name has + location=eu: organizations/123/locations/eu/bigQueryExports/test-bq-export. EXAMPLES - To delete a BigQuery export given organization 123 with id my-bq-export, + To delete a BigQuery export given organization 123 with id test-bq-export, run: - $ gcloud scc bqexports delete my-bq-export \ - --organization=organizations/123 - $ gcloud scc bqexports delete my-bq-export --organization=123 - $ gcloud scc bqexports delete \ - organizations/123/bigQueryExports/my-bq-export + $ gcloud scc bqexports delete test-bq-export --organization=123 - To delete a BigQuery export given folder 456 with id my-bq-export, run: + To delete a BigQuery export given folder 456 with id test-bq-export, run: - $ gcloud scc bqexports delete my-bq-export --folder=folders/456 - $ gcloud scc bqexports delete my-bq-export --folder=456 - $ gcloud scc bqexports delete \ - folders/456/bigQueryExports/my-bq-export + $ gcloud scc bqexports delete test-bq-export --folder=456 - To delete a BigQuery export given project 789 with id my-bq-export, run: + To delete a BigQuery export given project 789 with id test-bq-export, run: - $ gcloud scc bqexports delete my-bq-export --project=projects/789 - $ gcloud scc bqexports delete my-bq-export --project=789 - $ gcloud scc bqexports delete \ - projects/789/bigQueryExports/my-bq-export + $ gcloud scc bqexports delete test-bq-export --project=789 + + To delete the BigQuery export test-bq-export, with location=global, from + organization 123, run: + + $ gcloud scc bqexports delete test-bq-export --organization=123 \ + --location=global POSITIONAL ARGUMENTS BIG_QUERY_EXPORT - ID of the BigQuery export or the full resource name of the BigQuery - export. + ID of the BigQuery export e.g. my-bq-export or the full resource name + of the BigQuery export e.g. + organizations/123/bigQueryExports/my-bq-export. FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -63,5 +78,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) diff --git a/gcloud/scc/bqexports/get b/gcloud/scc/bqexports/get index cb09ffbe6..6136b33df 100644 --- a/gcloud/scc/bqexports/get +++ b/gcloud/scc/bqexports/get @@ -1,43 +1,61 @@ NAME - gcloud scc bqexports get - get a Cloud Security Command Center BigQuery - export + gcloud scc bqexports get - get a Security Command Center BigQuery export SYNOPSIS gcloud scc bqexports get BIG_QUERY_EXPORT + [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Get a Cloud Security Command Center BigQuery export. + Get a Security Command Center BigQuery export. + + BigQuery exports that are created with Security Command Center API V2 and + later include a location attribute. If the location attribute is included + in the resource name of a BigQuery export, you must specify it when + referencing the export. For example, the following BigQuery export name has + location=eu: organizations/123/locations/eu/bigQueryExports/test-bq-export. EXAMPLES - To get a BigQuery export under given organization 123 with id my-bq-export, + To get a BigQuery export under given organization 123 with id + test-bq-export, run: + + $ gcloud scc bqexports get test-bq-export --organization=123 + + To get a BigQuery export under given folder 456 with id test-bq-export, run: - $ gcloud scc bqexports get my-bq-export \ - --organization=organizations/123 - $ gcloud scc bqexports get my-bq-export --organization=123 - $ gcloud scc bqexports get \ - organizations/123/bigQueryExports/bq-export + $ gcloud scc bqexports get test-bq-export --folder=456 - To get a BigQuery export under given folder 456 with id my-bq-export, run: + To get a BigQuery export under given project 789 with id test-bq-export, + run: - $ gcloud scc bqexports get my-bq-export --folder=folders/456 - $ gcloud scc bqexports get my-bq-export --folder=456 - $ gcloud scc bqexports get folders/456/bigQueryExports/my-bq-export + $ gcloud scc bqexports get test-bq-export --project=789 - To get a BigQuery export under given project 789 with id my-bq-export, run: + To get a BigQuery export under given organization 123 with id + test-bq-export, and location=global run: - $ gcloud scc bqexports get my-bq-export --project=projects/789 - $ gcloud scc bqexports get my-bq-export --project=789 - $ gcloud scc bqexports get projects/789/bigQueryExports/my-bq-export + $ gcloud scc bqexports get test-bq-export --organization=123 \ + --location=global POSITIONAL ARGUMENTS BIG_QUERY_EXPORT - ID of the BigQuery export or the full resource name of the BigQuery - export. + ID of the BigQuery export e.g. my-bq-export or the full resource name + of the BigQuery export e.g. + organizations/123/bigQueryExports/my-bq-export. FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -61,5 +79,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) diff --git a/gcloud/scc/bqexports/help b/gcloud/scc/bqexports/help index 810d2b640..c2ddb0a18 100644 --- a/gcloud/scc/bqexports/help +++ b/gcloud/scc/bqexports/help @@ -17,16 +17,16 @@ COMMANDS COMMAND is one of the following: create - Create a Cloud Security Command Center BigQuery export. + Create a Security Command Center BigQuery export. delete - Delete a Cloud Security Command Center BigQuery export. + Delete a Security Command Center BigQuery export. get - Get a Cloud Security Command Center BigQuery export. + Get a Security Command Center BigQuery export. list - List Cloud Security Command Center BigQuery exports. + List Security Command Center BigQuery exports. update - Update a Cloud Security Command Center BigQuery export. + Update a Security Command Center BigQuery export. diff --git a/gcloud/scc/bqexports/list b/gcloud/scc/bqexports/list index 2603308ad..2ac18b72e 100644 --- a/gcloud/scc/bqexports/list +++ b/gcloud/scc/bqexports/list @@ -1,32 +1,41 @@ NAME - gcloud scc bqexports list - list Cloud Security Command Center BigQuery - exports + gcloud scc bqexports list - list Security Command Center BigQuery exports SYNOPSIS gcloud scc bqexports list (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION; default="global"] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - List Cloud Security Command Center BigQuery exports. + List Security Command Center BigQuery exports. + + BigQuery exports that are created with Security Command Center API V2 and + later include a `location` attribute. Include the `--location` flag to + list BigQuery exports with `location` attribute other than `global`. EXAMPLES List BigQuery exports under organization 123: - $ gcloud scc bqexports list --organization=organizations/123 $ gcloud scc bqexports list --organization=123 List BigQuery exports under folder 456: - $ gcloud scc bqexports list --folder=folders/456 $ gcloud scc bqexports list --folder=456 List BigQuery exports under project 789: - $ gcloud scc bqexports list --project=projects/789 $ gcloud scc bqexports list --project=789 + List BigQuery exports under organization 123 and location global: + + $ gcloud scc bqexports list --organization=123 --location=global + + List BigQuery exports under organization 123 and location=eu: + + $ gcloud scc bqexports list --organization=123 --location=eu + REQUIRED FLAGS Exactly one of these must be specified: @@ -42,6 +51,18 @@ REQUIRED FLAGS Project (id or number) where the BigQuery export resides. Formatted as projects/789 or just 789. +FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. @@ -77,5 +98,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) diff --git a/gcloud/scc/bqexports/update b/gcloud/scc/bqexports/update index ae946f1e8..2d08abe62 100644 --- a/gcloud/scc/bqexports/update +++ b/gcloud/scc/bqexports/update @@ -1,77 +1,66 @@ NAME - gcloud scc bqexports update - update a Cloud Security Command Center - BigQuery export + gcloud scc bqexports update - update a Security Command Center BigQuery + export SYNOPSIS gcloud scc bqexports update BIG_QUERY_EXPORT [--dataset=DATASET] [--description=DESCRIPTION] [--filter=FILTER] - [--update-mask=UPDATE_MASK] + [--location=LOCATION; default="global"] [--update-mask=UPDATE_MASK] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Update a Cloud Security Command Center BigQuery export. + Update a Security Command Center BigQuery export. + + BigQuery exports that are created with Security Command Center API V2 and + later include a location attribute. If the location attribute is included + in the resource name of a BigQuery export, you must specify it when + referencing the export. For example, the following BigQuery export name has + location=eu: organizations/123/locations/eu/bigQueryExports/test-bq-export. EXAMPLES Update a BigQuery export with id test-bq-export under organization 123 with a dataset abc in project 234 and a filter on category that equals to XSS_SCRIPTING: - $ gcloud scc bqexports update test-bq-export \ - --organization=organizations/123 \ - --dataset=projects/234/datasets/abc \ - --description="This is a test BigQuery export" \ - --filter="category=\"XSS_SCRIPTING\"" $ gcloud scc bqexports update test-bq-export --organization=123 \ --dataset=projects/234/datasets/abc \ --description="This is a test BigQuery export" \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc bqexports update \ - organizations/123/bigQueryExports/test-bq-export \ - --dataset=projects/234/datasets/abc \ - --description="This is a test BigQuery export" \ - --filter="category=\"XSS_SCRIPTING\"" Update a BigQuery export with id test-bq-export under folder 456 with a dataset abc in project 234 and a filter on category that equals to XSS_SCRIPTING: - $ gcloud scc bqexports update test-bq-export --folder=folders/456 \ - --dataset=projects/234/datasets/abc \ - --description="This is a test BigQuery export" \ - --filter="category=\"XSS_SCRIPTING\"" $ gcloud scc bqexports update test-bq-export --folder=456 \ --dataset=projects/234/datasets/abc \ --description="This is a test BigQuery export" \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc bqexports update \ - folders/456/bigQueryExports/test-bq-export \ - --dataset=projects/234/datasets/abc \ - --description="This is a test BigQuery export" \ - --filter="category=\"XSS_SCRIPTING\"" Update a BigQuery export with id test-bq-export under project 789 with a dataset abc in project 234 and a filter on category that equals to XSS_SCRIPTING: - $ gcloud scc bqexports update test-bq-export \ - --project=projects/789 --dataset=projects/234/datasets/abc \ - --description="This is a test BigQuery export" \ - --filter="category=\"XSS_SCRIPTING\"" $ gcloud scc bqexports update test-bq-export --project=789 \ --dataset=projects/234/datasets/abc \ --description="This is a test BigQuery export" \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc bqexports update \ - projects/789/bigQueryExports/test-bq-export \ + + Update a BigQuery export test-bq-export in organization 123 and + location=global. This command updates the target dataset to + projects/234/datasets/abc, the export description to This is a test + BigQuery export and the export filter to XSS_SCRIPTING: + + $ gcloud scc bqexports update test-bq-export --organization=123 \ --dataset=projects/234/datasets/abc \ --description="This is a test BigQuery export" \ - --filter="category=\"XSS_SCRIPTING\"" + --filter="category=\"XSS_SCRIPTING\"" --location=global POSITIONAL ARGUMENTS BIG_QUERY_EXPORT - ID of the BigQuery export or the full resource name of the BigQuery - export. + ID of the BigQuery export e.g. my-bq-export or the full resource name + of the BigQuery export e.g. + organizations/123/bigQueryExports/my-bq-export. FLAGS --dataset=DATASET @@ -84,6 +73,17 @@ FLAGS The filter string which will applied to findings muted by a BigQuery export. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --update-mask=UPDATE_MASK Optional: If left unspecified (default), an update-mask is automatically created using the flags specified in the command and only @@ -112,5 +112,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) diff --git a/gcloud/scc/findings/bulk-mute b/gcloud/scc/findings/bulk-mute index 5a13af805..afb286544 100644 --- a/gcloud/scc/findings/bulk-mute +++ b/gcloud/scc/findings/bulk-mute @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud scc findings bulk-mute (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) - [--filter=FILTER] [GCLOUD_WIDE_FLAG ...] + [--filter=FILTER] [--location=LOCATION; default="global"] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Bulk mute Security Command Center findings based on a filter. @@ -16,24 +17,24 @@ EXAMPLES $ gcloud scc findings bulk-mute --organization=organizations/123 \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc findings bulk-mute --organization=123 \ - --filter="category=\"XSS_SCRIPTING\"" To bulk mute findings given folder 123 based on a filter on category that equals XSS_SCRIPTING, run: $ gcloud scc findings bulk-mute --folder=folders/123 \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc findings bulk-mute --folder=123 \ - --filter="category=\"XSS_SCRIPTING\"" To bulk mute findings given project 123 based on a filter on category that equals XSS_SCRIPTING, run: $ gcloud scc findings bulk-mute --project=projects/123 \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc findings bulk-mute --project=123 \ - --filter="category=\"XSS_SCRIPTING\"" + + To bulk mute findings given organization 123 based on a filter on category + that equals XSS_SCRIPTING and location=eu run: + + $ gcloud scc findings bulk-mute --organization=organizations/123 \ + --filter="category=\"XSS_SCRIPTING\"" --location=locations/eu REQUIRED FLAGS Exactly one of these must be specified: @@ -54,6 +55,17 @@ OPTIONAL FLAGS --filter=FILTER The filter string which will applied to findings being muted. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -63,8 +75,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This variant is also available: diff --git a/gcloud/scc/findings/create b/gcloud/scc/findings/create index cbd32070f..203ad417c 100644 --- a/gcloud/scc/findings/create +++ b/gcloud/scc/findings/create @@ -1,47 +1,57 @@ NAME - gcloud scc findings create - create a Cloud Security Command Center finding + gcloud scc findings create - create a Security Command Center finding SYNOPSIS gcloud scc findings create (FINDING : --organization=ORGANIZATION --source=SOURCE) --category=CATEGORY --event-time=EVENT_TIME --resource-name=RESOURCE_NAME [--external-uri=EXTERNAL_URI] + [--location=LOCATION; default="global"] [--source-properties=[KEY=VALUE,...]] [--state=STATE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Create a Cloud Security Command Center finding. + Create a Security Command Center finding. EXAMPLES - Create an ACTIVE myFinding with category: XSS_SCRIPTING attached to - example-project under organization 123456 and source 5678: + Create an ACTIVE finding testFinding with category: XSS_SCRIPTING attached + to example-project under organization 123456 and source 5678: - $ gcloud scc findings create `myFinding` --organization=123456 \ + $ gcloud scc findings create `testFinding` --organization=123456 \ --source=5678 --state=ACTIVE --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' - Create an ACTIVE myFinding attached to example-project under project - example-project and source 5678: + Create an ACTIVE finding testFinding attached to example-project under + project example-project and source 5678: $ gcloud scc findings create \ - projects/example-project/sources/5678/findings/myFinding \ + projects/example-project/sources/5678/findings/testFinding \ --state=ACTIVE --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' - Create an ACTIVE myFinding attached to example-project under folder 456 and - source 5678: + Create an ACTIVE finding testFinding attached to example-project under + folder 456 and source 5678: $ gcloud scc findings create \ - folders/456/sources/5678/findings/myFinding --state=ACTIVE \ + folders/456/sources/5678/findings/testFinding --state=ACTIVE \ --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' + Create an ACTIVE finding testFinding with category: XSS_SCRIPTING attached + to example-project under organization 123456, source 5678 and location=eu: + + $ gcloud scc findings create `testFinding` --organization=123456 \ + --source=5678 --state=ACTIVE --category='XSS_SCRIPTING' \ + --event-time=2023-01-11T07:00:06.861Z \ + --resource-name='//cloudresourcemanager.googleapis.com/projects/\ + example-project' --location=eu + POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command Center) command. The arguments in this group can be used to specify the @@ -106,6 +116,17 @@ OPTIONAL FLAGS finding can be found. This field is guaranteed to be either empty or a well formed URL. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --source-properties=[KEY=VALUE,...] Source specific properties. These properties are managed by the source that writes the finding. The key names in the source_properties map @@ -126,8 +147,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES These variants are also available: diff --git a/gcloud/scc/findings/group b/gcloud/scc/findings/group index 2b1efe234..58b04a66f 100644 --- a/gcloud/scc/findings/group +++ b/gcloud/scc/findings/group @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud scc findings group [PARENT] [--compare-duration=COMPARE_DURATION] - [--filter=FILTER] [--group-by=GROUP_BY] [--page-size=PAGE_SIZE] + [--filter=FILTER] [--group-by=GROUP_BY] + [--location=LOCATION; default="global"] [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN] [--read-time=READ_TIME] [--source=SOURCE; default="-"] [GCLOUD_WIDE_FLAG ...] @@ -53,6 +54,12 @@ EXAMPLES $ gcloud scc findings group 123456 --source=5678 \ --group-by="state_change" --compare-duration=86400s + Group findings under organization 123456 and location=eu across all sources + by their category: + + $ gcloud scc findings group 123456 --group-by="category" \ + --location=eu + POSITIONAL ARGUMENTS Parent resource - parent organization, folder, or project in the Google Cloud resource hierarchy to be used for the gcloud scc command. Specify @@ -126,6 +133,17 @@ FLAGS ◆ state ◆ parent + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --page-size=PAGE_SIZE Maximum number of results to return in a single response. Default is 10, minimum is 1, maximum is 1000. @@ -153,8 +171,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES These variants are also available: diff --git a/gcloud/scc/findings/help b/gcloud/scc/findings/help index ae3a3f0b8..f89752243 100644 --- a/gcloud/scc/findings/help +++ b/gcloud/scc/findings/help @@ -19,7 +19,7 @@ COMMANDS Bulk mute Security Command Center findings based on a filter. create - Create a Cloud Security Command Center finding. + Create a Security Command Center finding. group Filter an organization or source's findings and groups them by their @@ -32,13 +32,13 @@ COMMANDS List a finding's security marks. set-mute - Update a Cloud Security Command Center finding's mute state. + Update a Security Command Center finding's mute state. update - Update a Cloud Security Command Center finding. + Update a Security Command Center finding. update-marks - Update Cloud Security Command Center finding's security marks. + Update Security Command Center finding's security marks. NOTES These variants are also available: diff --git a/gcloud/scc/findings/list b/gcloud/scc/findings/list index 241f3b4cf..7d53dfe3a 100644 --- a/gcloud/scc/findings/list +++ b/gcloud/scc/findings/list @@ -3,8 +3,8 @@ NAME SYNOPSIS gcloud scc findings list [PARENT] [--compare-duration=COMPARE_DURATION] - [--field-mask=FIELD_MASK] [--order-by=ORDER_BY] - [--page-token=PAGE_TOKEN] [--read-time=READ_TIME] + [--field-mask=FIELD_MASK] [--location=LOCATION; default="global"] + [--order-by=ORDER_BY] [--page-token=PAGE_TOKEN] [--read-time=READ_TIME] [--source=SOURCE; default="-"] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -62,6 +62,11 @@ EXAMPLES $ gcloud scc findings list 123456 \ --filter="state=\"ACTIVE\"" --read-time="2019-01-01T01:00:00Z" + List all findings under organization 123456 across all sources and + location=eu: + + $ gcloud scc findings list 123456 --location=eu + POSITIONAL ARGUMENTS Parent resource - parent organization, folder, or project in the Google Cloud resource hierarchy to be used for the gcloud scc command. Specify @@ -116,6 +121,17 @@ FLAGS v/s camel case used in field masks. An empty or missing field mask will list all fields. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --order-by=ORDER_BY Expression that defines what fields and order to use for sorting. String value should follow SQL syntax: comma separated list of fields. @@ -175,8 +191,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES These variants are also available: diff --git a/gcloud/scc/findings/list-marks b/gcloud/scc/findings/list-marks index c6f0233c8..f2925ea13 100644 --- a/gcloud/scc/findings/list-marks +++ b/gcloud/scc/findings/list-marks @@ -4,30 +4,36 @@ NAME SYNOPSIS gcloud scc findings list-marks (FINDING : --organization=ORGANIZATION --source=SOURCE) - [--page-token=PAGE_TOKEN] [--read-time=READ_TIME] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION; default="global"] [--page-token=PAGE_TOKEN] + [--read-time=READ_TIME] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION List a finding's security marks. EXAMPLES - List all security marks for myFinding under organization 123456 and source - 5678: + List all security marks for testFinding under organization 123456 and + source 5678: - $ gcloud scc findings list-marks `myFinding` --organization=123456 \ - --source=5678 + $ gcloud scc findings list-marks `testFinding` \ + --organization=123456 --source=5678 - List all security marks for myFinding under project example-project and + List all security marks for testFinding under project example-project and source 5678: $ gcloud scc findings list-marks \ - projects/example-project/sources/5678/findings/myFinding + projects/example-project/sources/5678/findings/testFinding - List all security marks for myFinding under folder 456 and source 5678: + List all security marks for testFinding under folder 456 and source 5678: $ gcloud scc findings list-marks \ - folders/456/sources/5678/findings/myFinding + folders/456/sources/5678/findings/testFinding + + List all security marks for testFinding under organization 123456, source + 5678 and location=eu: + + $ gcloud scc findings list-marks `testFinding` \ + --organization=123456 --source=5678 --location=eu POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command @@ -71,6 +77,17 @@ POSITIONAL ARGUMENTS ▸ provide the argument --source on the command line. FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --page-token=PAGE_TOKEN Response objects will return a non-null value for page-token to indicate that there is at least one additional page of data. User can @@ -117,8 +134,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES These variants are also available: diff --git a/gcloud/scc/findings/set-mute b/gcloud/scc/findings/set-mute index 1dfc5bb8c..d6cd015d7 100644 --- a/gcloud/scc/findings/set-mute +++ b/gcloud/scc/findings/set-mute @@ -1,14 +1,15 @@ NAME - gcloud scc findings set-mute - update a Cloud Security Command Center - finding's mute state + gcloud scc findings set-mute - update a Security Command Center finding's + mute state SYNOPSIS - gcloud scc findings set-mute FINDING --mute=MUTE [--source=SOURCE] + gcloud scc findings set-mute FINDING --mute=MUTE + [--location=LOCATION; default="global"] [--source=SOURCE] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Update a Cloud Security Command Center finding's mute state. + Update a Security Command Center finding's mute state. EXAMPLES To update finding's mute state to MUTED, given finding @@ -16,40 +17,31 @@ EXAMPLES $ gcloud scc findings set-mute 789 \ --organization=organizations/123 --source=456 --mute=MUTED - $ gcloud scc findings set-mute 789 --organization=123 --source=456 \ - --mute=MUTED - $ gcloud scc findings set-mute \ - organizations/123/sources/456/findings/789 --mute=MUTED To update finding's mute state to UNMUTED, given finding organizations/123/sources/456/findings/789, run: $ gcloud scc findings set-mute 789 \ --organization=organizations/123 --source=456 --mute=UNMUTED - $ gcloud scc findings set-mute 789 --organization=123 --source=456 \ - --mute=UNMUTED - $ gcloud scc findings set-mute \ - organizations/123/sources/456/findings/789 --mute=UNMUTED To update finding's mute state to MUTED, given finding folders/123/sources/456/findings/789, run: $ gcloud scc findings set-mute 789 --folder=folders/123 \ --source=456 --mute=MUTED - $ gcloud scc findings set-mute 789 --folder=123 --source=456 \ - --mute=MUTED - $ gcloud scc findings set-mute \ - folders/123/sources/456/findings/789 --mute=MUTED To update finding's mute state to MUTED, given finding projects/123/sources/456/findings/789, run: $ gcloud scc findings set-mute 789 --project=projects/123 \ --source=456 --mute=MUTED - $ gcloud scc findings set-mute 789 --project=123 --source=456 \ - --mute=MUTED - $ gcloud scc findings set-mute \ - projects/123/sources/456/findings/789 --mute=MUTED + + To update finding's mute state to MUTED, given finding + organizations/123/sources/456/findings/789 and location=eu, run: + + $ gcloud scc findings set-mute 789 \ + --organization=organizations/123 --source=456 --mute=MUTED \ + --location=locations/eu POSITIONAL ARGUMENTS FINDING @@ -60,6 +52,17 @@ REQUIRED FLAGS Desired mute state of the finding. MUTE must be one of: muted, unmuted. OPTIONAL FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --source=SOURCE ID of the source. @@ -86,8 +89,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This variant is also available: diff --git a/gcloud/scc/findings/update b/gcloud/scc/findings/update index f30ab5706..c02f25d2e 100644 --- a/gcloud/scc/findings/update +++ b/gcloud/scc/findings/update @@ -1,47 +1,53 @@ NAME - gcloud scc findings update - update a Cloud Security Command Center finding + gcloud scc findings update - update a Security Command Center finding SYNOPSIS gcloud scc findings update (FINDING : --organization=ORGANIZATION --source=SOURCE) [--event-time=EVENT_TIME] [--external-uri=EXTERNAL_URI] + [--location=LOCATION; default="global"] [--source-properties=[KEY=VALUE,...]] [--state=STATE] [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Update a Cloud Security Command Center finding. + Update a Security Command Center finding. EXAMPLES - Update myFinding's state from ACTIVE to INACTIVE: + Update testFinding's state from ACTIVE to INACTIVE: - $ gcloud scc findings update `myFinding` --organization=123456 \ + $ gcloud scc findings update `testFinding` --organization=123456 \ --source=5678 --state=INACTIVE - Update myFinding's state from ACTIVE to INACTIVE using project name for + Update testFinding's state from ACTIVE to INACTIVE using project name for example-project: $ gcloud scc findings update \ - projects/example-project/sources/5678/findings/myFinding \ + projects/example-project/sources/5678/findings/testFinding \ --state=INACTIVE - Update myFinding's state from ACTIVE to INACTIVE using folder name 456: + Update testFinding's state from ACTIVE to INACTIVE using folder name 456: $ gcloud scc findings update \ - folders/456/sources/5678/findings/myFinding --state=INACTIVE + folders/456/sources/5678/findings/testFinding --state=INACTIVE - Override all source properties on myFinding: + Override all source properties on testFinding: - $ gcloud scc findings update `myFinding` --organization=123456 \ + $ gcloud scc findings update `testFinding` --organization=123456 \ --source=5678 \ --source-properties="propKey1=propVal1,propKey2=propVal2" - Selectively update a specific source property on myFinding: + Selectively update a specific source property on testFinding: - $ gcloud scc findings update `myFinding` --organization=123456 \ + $ gcloud scc findings update `testFinding` --organization=123456 \ --source=5678 \ --source-properties="propKey1=propVal1,propKey2=propVal2" \ --update-mask="source_properties.propKey1" + Update finding testFinding with location=eu, state from ACTIVE to INACTIVE: + + $ gcloud scc findings update `testFinding` --organization=123456 \ + --source=5678 --state=INACTIVE --location=eu + POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command Center) command. The arguments in this group can be used to specify the @@ -97,6 +103,17 @@ FLAGS finding can be found. This field is guaranteed to be either empty or a well formed URL. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --source-properties=[KEY=VALUE,...] Source specific properties. These properties are managed by the source that writes the finding. The key names in the source_properties map @@ -132,8 +149,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES These variants are also available: diff --git a/gcloud/scc/findings/update-marks b/gcloud/scc/findings/update-marks index a4626d90a..a6299b686 100644 --- a/gcloud/scc/findings/update-marks +++ b/gcloud/scc/findings/update-marks @@ -1,49 +1,57 @@ NAME - gcloud scc findings update-marks - update Cloud Security Command Center - finding's security marks + gcloud scc findings update-marks - update Security Command Center finding's + security marks SYNOPSIS gcloud scc findings update-marks (FINDING : --organization=ORGANIZATION --source=SOURCE) + [--location=LOCATION; default="global"] [--security-marks=[KEY=VALUE,...]] [--start-time=START_TIME] [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Update Cloud Security Command Center finding's security marks. + Update Security Command Center finding's security marks. EXAMPLES - Selectively update security mark (Key1) with value (v1) on myFinding. Note - that other security marks on myFinding are untouched: + Selectively update security mark Key1 with value v1 on testFinding. Note + that other security marks on testFinding are untouched: - $ gcloud scc findings update-marks `myFinding` \ + $ gcloud scc findings update-marks `testFinding` \ --organization=123456 --source=5678 --security-marks="key1=v1" \ --update-mask="marks.markKey1" - Update all security marks on myFinding, under project example-project and + Update all security marks on testFinding, under project example-project and source 5678: $ gcloud scc findings update-marks \ - projects/example-project/sources/5678/findings/myFinding \ + projects/example-project/sources/5678/findings/testFinding \ --security-marks="key1=v1,key2=v2" - Update all security marks on myFinding, under folder 456 and source 5678: + Update all security marks on testFinding, under folder 456 and source 5678: $ gcloud scc findings update-marks \ - folders/456/sources/5678/findings/myFinding \ + folders/456/sources/5678/findings/testFinding \ --security-marks="key1=v1,key2=v2" - Update all security marks on myFinding, under organization 123456 and + Update all security marks on testFinding, under organization 123456 and source 5678: - $ gcloud scc findings update-marks `myFinding` \ + $ gcloud scc findings update-marks `testFinding` \ --organization=123456 --source=5678 \ --security-marks="key1=v1,key2=v2" - Delete all security marks on myFinding: + Delete all security marks on testFinding: - $ gcloud scc findings update-marks `myFinding` \ + $ gcloud scc findings update-marks `testFinding` \ --organization=123456 --source=5678 --security-marks="" + Update all security marks on testFinding, under project example-project, + source 5678 and location=eu: + + $ gcloud scc findings update-marks \ + projects/example-project/sources/5678/findings/testFinding \ + --security-marks="key1=v1,key2=v2" --location=eu + POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command Center) command. The arguments in this group can be used to specify the @@ -86,6 +94,17 @@ POSITIONAL ARGUMENTS ▸ provide the argument --source on the command line. FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --security-marks=[KEY=VALUE,...] SecurityMarks resource to be passed as the request body. It's a key=value pair separated by comma (,). For example: @@ -111,8 +130,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES These variants are also available: diff --git a/gcloud/scc/muteconfigs/create b/gcloud/scc/muteconfigs/create index 12965e778..eb43d4909 100644 --- a/gcloud/scc/muteconfigs/create +++ b/gcloud/scc/muteconfigs/create @@ -1,62 +1,45 @@ NAME - gcloud scc muteconfigs create - create a Cloud Security Command Center mute + gcloud scc muteconfigs create - create a Security Command Center mute config SYNOPSIS gcloud scc muteconfigs create MUTE_CONFIG [--description=DESCRIPTION] - [--filter=FILTER] + [--filter=FILTER] [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Create a Cloud Security Command Center mute config. + Create a Security Command Center mute config. EXAMPLES - To create a mute config my-mute-config given organization 123 with a filter - on category that equals to XSS_SCRIPTING, run: + To create a mute config test-mute-config given organization 123 with a + filter on category that equals to XSS_SCRIPTING, run: - $ gcloud scc muteconfigs create my-mute-config \ - --organization=organizations/123 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc muteconfigs create my-mute-config --organization=123 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc muteconfigs create \ - organizations/123/muteConfigs/my-mute-config \ - --description="This is a test mute config" \ + $ gcloud scc muteconfigs create test-mute-config \ + --organization=123 --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" - To create a mute config my-mute-config given folder 456 with a filter on + To create a mute config test-mute-config given folder 456 with a filter on category that equals to XSS_SCRIPTING, run: - $ gcloud scc muteconfigs create my-mute-config \ - --folder=folders/456 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc muteconfigs create my-mute-config --folder=456 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc muteconfigs create \ - folders/456/muteConfigs/my-mute-config \ + $ gcloud scc muteconfigs create test-mute-config --folder=456 \ --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" - To create a mute config my-mute-config given project 789 with a filter on + To create a mute config test-mute-config given project 789 with a filter on category that equals to XSS_SCRIPTING, run: - $ gcloud scc muteconfigs create my-mute-config \ - --project=projects/789 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc muteconfigs create my-mute-config --project=789 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc muteconfigs create \ - projects/789/muteConfigs/my-mute-config \ + $ gcloud scc muteconfigs create test-mute-config --project=789 \ --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" + To create a mute config test-mute-config given organization 123, + location=eu with a filter on category that equals to XSS_SCRIPTING, run: + + $ gcloud scc muteconfigs create test-mute-config \ + --organization=123 --description="This is a test mute config" \ + --filter="category=\"XSS_SCRIPTING\"" --location=eu + POSITIONAL ARGUMENTS MUTE_CONFIG ID of the mute config or the full resource name of the mute config. @@ -69,6 +52,17 @@ FLAGS The filter string which will applied to findings muted by a mute configuration. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -92,8 +86,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This variant is also available: diff --git a/gcloud/scc/muteconfigs/delete b/gcloud/scc/muteconfigs/delete index 44549bff4..40ddd2001 100644 --- a/gcloud/scc/muteconfigs/delete +++ b/gcloud/scc/muteconfigs/delete @@ -1,47 +1,52 @@ NAME - gcloud scc muteconfigs delete - delete a Cloud Security Command Center mute + gcloud scc muteconfigs delete - delete a Security Command Center mute config SYNOPSIS gcloud scc muteconfigs delete MUTE_CONFIG + [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Delete a Cloud Security Command Center mute config. + Delete a Security Command Center mute config. EXAMPLES - To delete a mute config given organization 123 with id my-test-mute-config, + To delete a mute config given organization 123 with id test-mute-config, run: - $ gcloud scc muteconfigs delete my-test-mute-config \ - --organization=organizations/123 - $ gcloud scc muteconfigs delete my-test-mute-config \ - --organization=123 - $ gcloud scc muteconfigs delete \ - organizations/123/muteConfigs/my-test-mute-config + $ gcloud scc muteconfigs delete test-mute-config --organization=123 - To delete a mute config given folder 456 with id my-test-mute-config, run: + To delete a mute config given folder 456 with id test-mute-config, run: - $ gcloud scc muteconfigs delete my-test-mute-config \ - --folder=folders/456 - $ gcloud scc muteconfigs delete my-test-mute-config --folder=456 - $ gcloud scc muteconfigs delete \ - folders/456/muteConfigs/my-test-mute-config + $ gcloud scc muteconfigs delete test-mute-config --folder=456 - To delete a mute config given project 789 with id my-test-mute-config, run: + To delete a mute config given project 789 with id test-mute-config, run: - $ gcloud scc muteconfigs delete my-test-mute-config \ - --project=projects/789 - $ gcloud scc muteconfigs delete my-test-mute-config --project=789 - $ gcloud scc muteconfigs delete \ - projects/789/muteConfigs/my-test-mute-config + $ gcloud scc muteconfigs delete test-mute-config --project=789 + + To delete a mute config given organization 123 with id test-mute-config and + location=eu, run: + + $ gcloud scc muteconfigs delete test-mute-config \ + --organization=123 --location=eu POSITIONAL ARGUMENTS MUTE_CONFIG ID of the mute config or the full resource name of the mute config. FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -65,8 +70,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This variant is also available: diff --git a/gcloud/scc/muteconfigs/get b/gcloud/scc/muteconfigs/get index 72661154e..af2c14bd7 100644 --- a/gcloud/scc/muteconfigs/get +++ b/gcloud/scc/muteconfigs/get @@ -1,45 +1,50 @@ NAME - gcloud scc muteconfigs get - get a Cloud Security Command Center mute - config + gcloud scc muteconfigs get - get a Security Command Center mute config SYNOPSIS gcloud scc muteconfigs get MUTE_CONFIG + [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Get a Cloud Security Command Center mute config. + Get a Security Command Center mute config. EXAMPLES - To get a mute config given organization 123 with id my-test-mute-config, - run: + To get a mute config given organization 123 with id test-mute-config, run: - $ gcloud scc muteconfigs get my-test-mute-config \ - --organization=organizations/123 - $ gcloud scc muteconfigs get my-test-mute-config --organization=123 - $ gcloud scc muteconfigs get \ - organizations/123/muteConfigs/my-test-mute-config + $ gcloud scc muteconfigs get test-mute-config --organization=123 - To get a mute config given folder 456 with id my-test-mute-config, run: + To get a mute config given folder 456 with id test-mute-config, run: - $ gcloud scc muteconfigs get my-test-mute-config --folder=folders/456 - $ gcloud scc muteconfigs get my-test-mute-config --folder=456 - $ gcloud scc muteconfigs get \ - folders/456/muteConfigs/my-test-mute-config + $ gcloud scc muteconfigs get test-mute-config --folder=456 - To get a mute config given project 789 with id my-test-mute-config, run: + To get a mute config given project 789 with id test-mute-config, run: - $ gcloud scc muteconfigs get my-test-mute-config \ - --project=projects/789 - $ gcloud scc muteconfigs get my-test-mute-config --project=789 - $ gcloud scc muteconfigs get \ - projects/789/muteConfigs/my-test-mute-config + $ gcloud scc muteconfigs get test-mute-config --project=789 + + To get a mute config given organization 123 with id test-mute-config and + location=eu, run: + + $ gcloud scc muteconfigs get test-mute-config --organization=123 \ + --location=eu POSITIONAL ARGUMENTS MUTE_CONFIG ID of the mute config or the full resource name of the mute config. FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -63,8 +68,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This variant is also available: diff --git a/gcloud/scc/muteconfigs/help b/gcloud/scc/muteconfigs/help index 788229478..fc01cb22b 100644 --- a/gcloud/scc/muteconfigs/help +++ b/gcloud/scc/muteconfigs/help @@ -17,19 +17,19 @@ COMMANDS COMMAND is one of the following: create - Create a Cloud Security Command Center mute config. + Create a Security Command Center mute config. delete - Delete a Cloud Security Command Center mute config. + Delete a Security Command Center mute config. get - Get a Cloud Security Command Center mute config. + Get a Security Command Center mute config. list - List Cloud Security Command Center mute configs. + ListSecurity Command Center mute configs. update - Update a Cloud Security Command Center mute config. + Update a Security Command Center mute config. NOTES This variant is also available: diff --git a/gcloud/scc/muteconfigs/list b/gcloud/scc/muteconfigs/list index 94d377682..6da6fffe3 100644 --- a/gcloud/scc/muteconfigs/list +++ b/gcloud/scc/muteconfigs/list @@ -1,32 +1,33 @@ NAME - gcloud scc muteconfigs list - list Cloud Security Command Center mute - configs + gcloud scc muteconfigs list - listSecurity Command Center mute configs SYNOPSIS gcloud scc muteconfigs list (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION; default="global"] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - List Cloud Security Command Center mute configs. + List Security Command Center mute configs. EXAMPLES List mute configs under organization 123: - $ gcloud scc muteconfigs list --organization=organizations/123 $ gcloud scc muteconfigs list --organization=123 List mute configs under folder 456: - $ gcloud scc muteconfigs list --folder=folders/456 $ gcloud scc muteconfigs list --folder=456 List mute configs under project 789: - $ gcloud scc muteconfigs list --project=projects/789 $ gcloud scc muteconfigs list --project=789 + List mute configs under organization `_123_` and `location=eu`: + + $ gcloud scc muteconfigs list --organization=123 --location=eu + REQUIRED FLAGS Exactly one of these must be specified: @@ -42,6 +43,18 @@ REQUIRED FLAGS Project (id or number) where the mute config resides. Formatted as projects/789 or just 789. +FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. @@ -77,8 +90,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This variant is also available: diff --git a/gcloud/scc/muteconfigs/update b/gcloud/scc/muteconfigs/update index 590310a3f..3af1ec001 100644 --- a/gcloud/scc/muteconfigs/update +++ b/gcloud/scc/muteconfigs/update @@ -1,62 +1,46 @@ NAME - gcloud scc muteconfigs update - update a Cloud Security Command Center mute + gcloud scc muteconfigs update - update a Security Command Center mute config SYNOPSIS gcloud scc muteconfigs update MUTE_CONFIG [--description=DESCRIPTION] - [--filter=FILTER] [--update-mask=UPDATE_MASK] + [--filter=FILTER] [--location=LOCATION; default="global"] + [--update-mask=UPDATE_MASK] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Update a Cloud Security Command Center mute config. + Update a Security Command Center mute config. EXAMPLES - Update a mute config with ID=my-test-mute-config under organization=123 - with a filter on category that equals to XSS_SCRIPTING: + Update a mute config with ID=test-mute-config under organization=123 with a + filter on category that equals to XSS_SCRIPTING: - $ gcloud scc muteconfigs update my-test-mute-config \ - --organization=organizations/123 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc muteconfigs update my-test-mute-config \ + $ gcloud scc muteconfigs update test-mute-config \ --organization=123 --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc muteconfigs update \ - organizations/123/muteConfigs/my-test-mute-config \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - Update a mute config with ID=my-test-mute-config under folder=456 with a + Update a mute config with ID=test-mute-config under folder=456 with a filter on category that equals to XSS_SCRIPTING: - $ gcloud scc muteconfigs update my-test-mute-config \ - --folder=folders/456 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc muteconfigs update my-test-mute-config --folder=456 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc muteconfigs update \ - folders/456/muteConfigs/my-test-mute-config \ + $ gcloud scc muteconfigs update test-mute-config --folder=456 \ --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" - Update a mute config with ID=my-test-mute-config under project=789 with a + Update a mute config with ID=test-mute-config under project=789 with a filter on category that equals to XSS_SCRIPTING: - $ gcloud scc muteconfigs update my-test-mute-config \ - --project=projects/789 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc muteconfigs update my-test-mute-config --project=789 \ - --description="This is a test mute config" \ - --filter="category=\"XSS_SCRIPTING\"" - $ gcloud scc muteconfigs update \ - projects/789/muteConfigs/my-test-mute-config \ + $ gcloud scc muteconfigs update test-mute-config --project=789 \ --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" + Update a mute config with ID=test-mute-config under organization=123 + location=eu with a filter on category that equals to XSS_SCRIPTING: + + $ gcloud scc muteconfigs update test-mute-config \ + --organization=123 --description="This is a test mute config" \ + --filter="category=\"XSS_SCRIPTING\"" --location=eu + POSITIONAL ARGUMENTS MUTE_CONFIG ID of the mute config or the full resource name of the mute config. @@ -69,6 +53,17 @@ FLAGS The filter string which will applied to findings muted by a mute configuration. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --update-mask=UPDATE_MASK Optional: If left unspecified (default), an update-mask is automatically created using the flags specified in the command and only @@ -97,8 +92,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES This variant is also available: diff --git a/gcloud/scc/notifications/create b/gcloud/scc/notifications/create index 7481f9258..3e009edc0 100644 --- a/gcloud/scc/notifications/create +++ b/gcloud/scc/notifications/create @@ -1,16 +1,22 @@ NAME - gcloud scc notifications create - create a Cloud Security Command Center + gcloud scc notifications create - create a Security Command Center notification config SYNOPSIS gcloud scc notifications create NOTIFICATION_CONFIG_ID --pubsub-topic=PUBSUB_TOPIC [--description=DESCRIPTION] - [--filter=FILTER] + [--filter=FILTER] [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Create a Cloud Security Command Center notification config. + Create a Security Command Center notification config. + + Notification configs that are created with Security Command Center API V2 + and later include a location attribute. If a location is not specified, the + default global location is used. For example, the following Notification + config name has location=global attribute: + organizations/123/locations/global/notificationConfigs/my-config. EXAMPLES Create a notification config test-config under organization 123 for @@ -20,10 +26,6 @@ EXAMPLES $ gcloud scc notifications create test-config --organization=123 \ --pubsub-topic=projects/test-project/topics/notification-test \ --filter="resource_name: \"a\"" - $ gcloud scc notifications create \ - organizations/123/notificationConfigs/test-config \ - --pubsub-topic=projects/test-project/topics/notification-test \ - --filter="resource_name: \"a\"" Create a notification config test-config under folder 456 for findings for pubsub-topic projects/test-project/topics/notification-test with a filter @@ -32,10 +34,6 @@ EXAMPLES $ gcloud scc notifications create test-config --folder=456 \ --pubsub-topic=projects/test-project/topics/notification-test \ --filter="resource_name: \"a\"" - $ gcloud scc notifications create \ - folders/456/notificationConfigs/test-config \ - --pubsub-topic=projects/test-project/topics/notification-test \ - --filter="resource_name: \"a\"" Create a notification config test-config under project 789 for findings for pubsub-topic projects/test-project/topics/notification-test with a filter @@ -44,10 +42,14 @@ EXAMPLES $ gcloud scc notifications create test-config --project=789 \ --pubsub-topic=projects/test-project/topics/notification-test \ --filter="resource_name: \"a\"" - $ gcloud scc notifications create \ - projects/789/notificationConfigs/test-config \ + + Create a notification config test-config under organization 123 for + findings for pubsub-topic projects/test-project/topics/notification-test + with a filter on resource name and location=eu + + $ gcloud scc notifications create test-config --project=789 \ --pubsub-topic=projects/test-project/topics/notification-test \ - --filter="resource_name: \"a\"" + --filter="resource_name: \"a\"" --location=eu POSITIONAL ARGUMENTS NOTIFICATION_CONFIG_ID @@ -66,6 +68,17 @@ OPTIONAL FLAGS --filter=FILTER Filter to be used for notification config. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -89,8 +102,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES These variants are also available: diff --git a/gcloud/scc/notifications/delete b/gcloud/scc/notifications/delete index 8191e2077..4fa7bfcd8 100644 --- a/gcloud/scc/notifications/delete +++ b/gcloud/scc/notifications/delete @@ -1,33 +1,47 @@ NAME - gcloud scc notifications delete - delete a Cloud Security Command Center + gcloud scc notifications delete - delete a Security Command Center notification config SYNOPSIS gcloud scc notifications delete NOTIFICATION_CONFIG_ID + [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Delete a Cloud Security Command Center notification config. + Delete a Security Command Center notification config. + + Notification configs that are created with Security Command Center API V2 + and later include a location attribute. If the location attribute is + included in the resource name of a Notification configs, you must specify + it when referencing the Notification config. For example, the following + Notification configs name has location=eu: + organizations/123/locations/eu/notificationConfigs/test-config. EXAMPLES - Delete notification config 'my-config' from organization 123 + Delete notification config 'test-config' from organization 123 - $ gcloud scc notifications delete my-config --organization=123 - $ gcloud scc notifications delete \ - organizations/123/notificationConfigs/my-config + $ gcloud scc notifications delete test-config --organization=123 - Delete notification config 'my-config' from folder 456 + Delete notification config 'test-config' from folder 456 - $ gcloud scc notifications delete my-config --folder=456 - $ gcloud scc notifications delete \ - folders/456/notificationConfigs/my-config + $ gcloud scc notifications delete test-config --folder=456 - Delete notification config 'my-config' from project 789 + Delete notification config 'test-config' from project 789 - $ gcloud scc notifications delete my-config --project=789 - $ gcloud scc notifications delete \ - projects/789/notificationConfigs/my-config + $ gcloud scc notifications delete test-config --project=789 + + Delete notification config 'test-config' with location global from + organization 123 + + $ gcloud scc notifications delete test-config --organization=123 \ + --location=global + + Delete notification config 'test-config' with location=eu from organization + 123 + + $ gcloud scc notifications delete test-config --organization=123 \ + --location=eu POSITIONAL ARGUMENTS NOTIFICATION_CONFIG_ID @@ -35,6 +49,17 @@ POSITIONAL ARGUMENTS "organizations/123/notificationConfigs/456" or just "456". FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -58,8 +83,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES These variants are also available: diff --git a/gcloud/scc/notifications/describe b/gcloud/scc/notifications/describe index fa6f52831..10c6d203b 100644 --- a/gcloud/scc/notifications/describe +++ b/gcloud/scc/notifications/describe @@ -1,36 +1,41 @@ NAME - gcloud scc notifications describe - describe a Cloud Security Command - Center notification config + gcloud scc notifications describe - describe a Security Command Center + notification config SYNOPSIS gcloud scc notifications describe NOTIFICATION_CONFIG_ID + [--location=LOCATION; default="global"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Describe a Cloud Security Command Center notification config. + Describe a Security Command Center notification config. + + Notification configs that are created with Security Command Center API V2 + and later include a location attribute. If the location attribute is + included in the resource name of a Notification configs, you must specify + it when referencing the Notification config. For example, the following + Notification configs name has location=eu: + organizations/123/locations/eu/notificationConfigs/test-config. EXAMPLES - Describe notification config 'my-config' from organization 123 + Describe notification config 'test-config' from organization 123 - $ gcloud scc notifications describe notifications describe \ - my-config --organization=123 - $ gcloud scc notifications describe notifications describe \ - organizations/123/notificationConfigs/my-config + $ gcloud scc notifications describe test-config --organization=123 - Describe notification config 'my-config' from folder 456 + Describe notification config 'test-config' from folder 456 - $ gcloud scc notifications describe notifications describe \ - my-config --folder=456 - $ gcloud scc notifications describe notifications describe \ - folders/456/notificationConfigs/my-config + $ gcloud scc notifications describe test-config --folder=456 - Describe notification config 'my-config' from project 789 + Describe notification config 'test-config' from project 789 - $ gcloud scc notifications describe notifications describe \ - my-config --project=789 - $ gcloud scc notifications describe notifications describe \ - projects/789/notificationConfigs/my-config + $ gcloud scc notifications describe test-config --project=789 + + Describe notification config 'test-config' from organization 123 and + location=global + + $ gcloud scc notifications describe test-config --organization=123 \ + --location=global POSITIONAL ARGUMENTS NOTIFICATION_CONFIG_ID @@ -38,6 +43,17 @@ POSITIONAL ARGUMENTS "organizations/123/notificationConfigs/456" or just "456". FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + At most one of these can be specified: --folder=FOLDER @@ -61,8 +77,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES These variants are also available: diff --git a/gcloud/scc/notifications/help b/gcloud/scc/notifications/help index bf9f0b1fb..125515ea2 100644 --- a/gcloud/scc/notifications/help +++ b/gcloud/scc/notifications/help @@ -17,19 +17,19 @@ COMMANDS COMMAND is one of the following: create - Create a Cloud Security Command Center notification config. + Create a Security Command Center notification config. delete - Delete a Cloud Security Command Center notification config. + Delete a Security Command Center notification config. describe - Describe a Cloud Security Command Center notification config. + Describe a Security Command Center notification config. list - List Cloud Security Command Center notification configs. + List Security Command Center notification configs. update - Update a Cloud Security Command Center notification config. + Update a Security Command Center notification config. NOTES These variants are also available: diff --git a/gcloud/scc/notifications/list b/gcloud/scc/notifications/list index 62b534157..271054ff2 100644 --- a/gcloud/scc/notifications/list +++ b/gcloud/scc/notifications/list @@ -1,14 +1,19 @@ NAME - gcloud scc notifications list - list Cloud Security Command Center - notification configs + gcloud scc notifications list - list Security Command Center notification + configs SYNOPSIS - gcloud scc notifications list [PARENT] [--filter=EXPRESSION] + gcloud scc notifications list [PARENT] + [--location=LOCATION; default="global"] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - List Cloud Security Command Center notification configs. + List Security Command Center notification configs. + + Notification Configs that are created with Security Command Center API V2 + and later include a `location` attribute. Include the `--location` flag to + list Notification Configs with `location` attribute other than `global`. EXAMPLES List notification configs from organization 123 @@ -24,6 +29,12 @@ EXAMPLES $ gcloud scc notifications list projects/789 + List notification configs from organization 123 and location=eu + + $ gcloud scc notifications list 123 --location=eu + $ gcloud scc notifications list organizations/123 \ + --location=locations/eu + POSITIONAL ARGUMENTS Parent resource - parent organization, folder, or project in the Google Cloud resource hierarchy to be used for the gcloud scc command. Specify @@ -38,6 +49,18 @@ POSITIONAL ARGUMENTS ▸ Set the parent property in configuration using gcloud config set scc/parent if it is not specified in command line. +FLAGS + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. @@ -73,8 +96,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES These variants are also available: diff --git a/gcloud/scc/notifications/update b/gcloud/scc/notifications/update index 47eb12136..77fbb50eb 100644 --- a/gcloud/scc/notifications/update +++ b/gcloud/scc/notifications/update @@ -1,80 +1,68 @@ NAME - gcloud scc notifications update - update a Cloud Security Command Center + gcloud scc notifications update - update a Security Command Center notification config SYNOPSIS gcloud scc notifications update NOTIFICATION_CONFIG_ID [--description=DESCRIPTION] [--filter=FILTER] - [--pubsub-topic=PUBSUB_TOPIC] + [--location=LOCATION; default="global"] [--pubsub-topic=PUBSUB_TOPIC] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Update a Cloud Security Command Center notification config. + Update a Security Command Center notification config. + + Notification configs that are created with Security Command Center API V2 + and later include a location attribute. If the location attribute is + included in the resource name of a Notification configs, you must specify + it when referencing the Notification config. For example, the following + Notification configs name has location=eu: + organizations/123/locations/eu/notificationConfigs/test-config. EXAMPLES - Update all mutable fields under an organization parent my-config + Update all mutable fields under an organization parent test-config (description + pubsub topic + filter): $ gcloud scc notifications update scc notifications update \ - my-config --organization=123 --description="New description" \ + test-config --organization=123 --description="New description" \ --pubsub-topic="projects/22222/topics/newtopic" - $ gcloud scc notifications update scc notifications update \ - organizations/123/notificationConfigs/my-config \ - --description="New description" \ - --pubsub-topic="projects/22222/topics/newtopic" - - Update all mutable fields under a folder parent my-config (description + + Update all mutable fields under a folder parent test-config (description + pubsub topic + filter): $ gcloud scc notifications update scc notifications update \ - my-config --folder=456 --description="New description" \ + test-config --folder=456 --description="New description" \ --pubsub-topic="projects/22222/topics/newtopic" - $ gcloud scc notifications update scc notifications update \ - folders/456/notificationConfigs/my-config \ - --description="New description" \ - --pubsub-topic="projects/22222/topics/newtopic" - - Update all mutable fields under a project parent my-config (description + + Update all mutable fields under a project parent test-config (description + pubsub topic + filter): $ gcloud scc notifications update scc notifications update \ - my-config --project=789 --description="New description" \ + test-config --project=789 --description="New description" \ --pubsub-topic="projects/22222/topics/newtopic" + Update test-config's description + + $ gcloud scc notifications update test-config --organization=123 \ + --description="New description" + + Update test-config's pubsub-topic + + $ gcloud scc notifications update test-config --organization=123 \ + --pubsub-topic="projects/22222/topics/newtopic" + + Update test-config's filter + + $ gcloud scc notifications update test-config --organization=123 \ + --filter='state = \"ACTIVE\"' + + Update all mutable fields for test-config with location=global under an + organization parent (description + pubsub topic + filter): + $ gcloud scc notifications update scc notifications update \ - projects/789/notificationConfigs/my-config \ - --description="New description" \ - --pubsub-topic="projects/22222/topics/newtopic" - - Update my-config's description - - $ gcloud scc notifications update my-config --organization=123 \ - --description="New description" - - $ gcloud scc notifications update \ - organizations/123/notificationConfigs/my-config \ - --description="New description" - - Update my-config's pubsub-topic - - $ gcloud scc notifications update my-config --organization=123 \ - --pubsub-topic="projects/22222/topics/newtopic" - - $ gcloud scc notifications update \ - organizations/123/notificationConfigs/my-config \ - --pubsub-topic="projects/22222/topics/newtopic" - - Update my-config's filter - - $ gcloud scc notifications update my-config --organization=123 \ - --filter='state = \"ACTIVE\"' - - $ gcloud scc notifications update \ - organizations/123/notificationConfigs/my-config \ - --filter='state = \"ACTIVE\"' + test-config --organization=123 --description="New description" \ + --pubsub-topic="projects/22222/topics/newtopic" \ + --location=global POSITIONAL ARGUMENTS NOTIFICATION_CONFIG_ID @@ -89,6 +77,17 @@ FLAGS The filter string which will applied to events of findings of a notification configuration. + --location=LOCATION; default="global" + When data residency controls are enabled, this attribute specifies the + 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. + --pubsub-topic=PUBSUB_TOPIC The Pub/Sub topic which will receive notifications. Its format is "projects/[project_id]/topics/[topic]". @@ -116,8 +115,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the securitycenter/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/security-command-center + This command uses the Security Command Center API. For more information, + see Security Command Center API. + (https://cloud.google.com/security-command-center/docs/reference/rest) NOTES These variants are also available: diff --git a/gcloud/scc/postures/list b/gcloud/scc/postures/list index 0edb1066c..4ad72ff24 100644 --- a/gcloud/scc/postures/list +++ b/gcloud/scc/postures/list @@ -8,17 +8,11 @@ SYNOPSIS DESCRIPTION Lists all Cloud Security Command Center (SCC) postures for an organization. - - By default, postures created in global location are returned. + For a posture with multiple revisions, only the latest updated revision of + the posture is returned in the output. EXAMPLES - List all postures in organization 123. If location is omitted, this returns - postures from location 'global'. For a posture with multiple revisions, - only the latest updated revision of the posture is returned in the output. - - $ gcloud scc postures list organizations/123 - - List all postures in organization 123, location global + List all postures in organization 123, location global. $ gcloud scc postures list organizations/123/locations/global diff --git a/gcloud/spanner/backups/copy b/gcloud/spanner/backups/copy index 6d6bfe8d0..c14062f06 100644 --- a/gcloud/spanner/backups/copy +++ b/gcloud/spanner/backups/copy @@ -127,42 +127,46 @@ OPTIONAL FLAGS Use the default encryption configuration if one exists. otherwise use the same encryption configuration as the source backup. - Key resource - Cloud KMS key to be used to copy the Cloud Spanner backup. - The arguments in this group can be used to specify the attributes of this - resource. + KMS key name group - --kms-key=KMS_KEY - ID of the key or fully qualified identifier for the key. + At most one of these can be specified: - To set the kms-key attribute: - ▸ provide the argument --kms-key on the command line. + Key resource - Cloud KMS key to be used to copy the Cloud Spanner + backup. The arguments in this group can be used to specify the + attributes of this resource. - This flag argument must be specified if any of the other arguments in - this group are specified. + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. - --kms-keyring=KMS_KEYRING - KMS keyring id of the key. + To set the kms-key attribute: + ▫ provide the argument --kms-key on the command line. - To set the kms-keyring attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-keyring on the command line. + This flag argument must be specified if any of the other arguments + in this group are specified. - --kms-location=KMS_LOCATION - Cloud location for the key. + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. - To set the kms-location attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-location on the command line. + To set the kms-keyring attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-keyring on the command line. - --kms-project=KMS_PROJECT - Cloud project id for the key. + --kms-location=KMS_LOCATION + Cloud location for the key. - To set the kms-project attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-project on the command line. + To set the kms-location attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. + + To set the kms-project attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-project on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/spanner/backups/create b/gcloud/spanner/backups/create index 2fd17e068..5657a7aef 100644 --- a/gcloud/spanner/backups/create +++ b/gcloud/spanner/backups/create @@ -97,42 +97,46 @@ OPTIONAL FLAGS use-database-encryption Use the same encryption configuration as the database. - Key resource - Cloud KMS key to be used to create the Cloud Spanner - backup. The arguments in this group can be used to specify the attributes - of this resource. + KMS key name group - --kms-key=KMS_KEY - ID of the key or fully qualified identifier for the key. + At most one of these can be specified: - To set the kms-key attribute: - ▸ provide the argument --kms-key on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner + backup. The arguments in this group can be used to specify the + attributes of this resource. - This flag argument must be specified if any of the other arguments in - this group are specified. + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. - --kms-keyring=KMS_KEYRING - KMS keyring id of the key. + To set the kms-key attribute: + ▫ provide the argument --kms-key on the command line. - To set the kms-keyring attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-keyring on the command line. + This flag argument must be specified if any of the other arguments + in this group are specified. - --kms-location=KMS_LOCATION - Cloud location for the key. + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. - To set the kms-location attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-location on the command line. + To set the kms-keyring attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-keyring on the command line. - --kms-project=KMS_PROJECT - Cloud project id for the key. + --kms-location=KMS_LOCATION + Cloud location for the key. - To set the kms-project attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-project on the command line. + To set the kms-location attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. + + To set the kms-project attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-project on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/spanner/databases/create b/gcloud/spanner/databases/create index c44597303..12892ecca 100644 --- a/gcloud/spanner/databases/create +++ b/gcloud/spanner/databases/create @@ -84,42 +84,46 @@ FLAGS --ddl_file is set, --ddl is ignored. One line comments starting with -- are ignored. - Key resource - Cloud KMS key to be used to create the Cloud Spanner - database. The arguments in this group can be used to specify the - attributes of this resource. + KMS key name group - --kms-key=KMS_KEY - ID of the key or fully qualified identifier for the key. + At most one of these can be specified: - To set the kms-key attribute: - ▸ provide the argument --kms-key on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner + database. The arguments in this group can be used to specify the + attributes of this resource. - This flag argument must be specified if any of the other arguments in - this group are specified. + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. - --kms-keyring=KMS_KEYRING - KMS keyring id of the key. + To set the kms-key attribute: + ▫ provide the argument --kms-key on the command line. - To set the kms-keyring attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-keyring on the command line. + This flag argument must be specified if any of the other arguments + in this group are specified. - --kms-location=KMS_LOCATION - Cloud location for the key. + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. - To set the kms-location attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-location on the command line. + To set the kms-keyring attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-keyring on the command line. - --kms-project=KMS_PROJECT - Cloud project id for the key. + --kms-location=KMS_LOCATION + Cloud location for the key. - To set the kms-project attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-project on the command line. + To set the kms-location attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. + + To set the kms-project attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-project on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/spanner/databases/restore b/gcloud/spanner/databases/restore index a532e0b09..b49e7b089 100644 --- a/gcloud/spanner/databases/restore +++ b/gcloud/spanner/databases/restore @@ -110,42 +110,46 @@ OPTIONAL FLAGS Use the default encryption configuration if one exists, otherwise use the same encryption configuration as the backup. - Key resource - Cloud KMS key to be used to restore the Cloud Spanner - database. The arguments in this group can be used to specify the - attributes of this resource. + KMS key name group - --kms-key=KMS_KEY - ID of the key or fully qualified identifier for the key. + At most one of these can be specified: - To set the kms-key attribute: - ▸ provide the argument --kms-key on the command line. + Key resource - Cloud KMS key to be used to restore the Cloud Spanner + database. The arguments in this group can be used to specify the + attributes of this resource. - This flag argument must be specified if any of the other arguments in - this group are specified. + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. - --kms-keyring=KMS_KEYRING - KMS keyring id of the key. + To set the kms-key attribute: + ▫ provide the argument --kms-key on the command line. - To set the kms-keyring attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-keyring on the command line. + This flag argument must be specified if any of the other arguments + in this group are specified. - --kms-location=KMS_LOCATION - Cloud location for the key. + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. - To set the kms-location attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-location on the command line. + To set the kms-keyring attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-keyring on the command line. - --kms-project=KMS_PROJECT - Cloud project id for the key. + --kms-location=KMS_LOCATION + Cloud location for the key. - To set the kms-project attribute: - ▸ provide the argument --kms-key on the command line with a fully - specified name; - ▸ provide the argument --kms-project on the command line. + To set the kms-location attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. + + To set the kms-project attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-project on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/sql/backups/delete b/gcloud/sql/backups/delete index 0112d7b97..5d8358606 100644 --- a/gcloud/sql/backups/delete +++ b/gcloud/sql/backups/delete @@ -2,7 +2,7 @@ NAME gcloud sql backups delete - delete a backup of a Cloud SQL instance SYNOPSIS - gcloud sql backups delete ID --instance=INSTANCE, -i INSTANCE [--async] + gcloud sql backups delete ID [--async] [--instance=INSTANCE, -i INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -10,18 +10,17 @@ DESCRIPTION POSITIONAL ARGUMENTS ID - The ID of the backup run. You can find the ID by running $ gcloud sql - backups list -i {instance}. + The ID of the backup run. To find the ID, run the following command: $ + gcloud sql backups list -i {instance}. -REQUIRED FLAGS - --instance=INSTANCE, -i INSTANCE - Cloud SQL instance ID. - -OPTIONAL FLAGS +FLAGS --async Return immediately, without waiting for the operation in progress to complete. + --instance=INSTANCE, -i INSTANCE + Cloud SQL instance ID. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format,