gcloud scc notifications delete
Stay organized with collections
Save and categorize content based on your preferences.
- NAME
-
- gcloud scc notifications delete - delete a Security Command Center notification config
- SYNOPSIS
-
-
gcloud scc notifications deleteNOTIFICATION_CONFIG_ID[--location=LOCATION; default="global"] [--folder=FOLDER|--organization=ORGANIZATION|--project=PROJECT] [GCLOUD_WIDE_FLAG …]
-
- DESCRIPTION
-
Delete a Security Command Center notification config.
Notification configs that are created with Security Command Center API V2 and later include a
locationattribute. If thelocationattribute 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 haslocation=eu:organizations/123/locations/eu/notificationConfigs/test-config. - EXAMPLES
-
Delete notification config 'test-config' from organization
123gcloudsccnotificationsdeletetest-config--organization=123Delete notification config 'test-config' from folder
456gcloudsccnotificationsdeletetest-config--folder=456Delete notification config 'test-config' from project
789gcloudsccnotificationsdeletetest-config--project=789Delete notification config 'test-config' with location
globalfrom organization123gcloudsccnotificationsdeletetest-config--organization=123--location=globalDelete notification config 'test-config' with
location=eufrom organization123gcloudsccnotificationsdeletetest-config--organization=123--location=eu - POSITIONAL ARGUMENTS
-
NOTIFICATION_CONFIG_ID- The ID of the notification config. Formatted as "organizations/123/notificationConfigs/456" or just "456".
- FLAGS
-
--location=LOCATION; default="global"-
Required if either data residency is enabled or the
notificationConfigwas created by using the API v2.If data residency is enabled, specify the Security Command Center location in which the notification is stored.
If data residency is not enabled, include
/locations/``LOCATION´´ in the full name or specify the--location flagonly if thenotificationConfigwas created by using the Security Command Center API v2, in which case, the only valid location isglobal. -
At most one of these can be specified:
--folder=FOLDER-
Folder where the notification config resides. Formatted as
or justfolders/456.456 --organization=ORGANIZATION-
Organization where the notification config resides. Formatted as
or justorganizations/123.123 --project=PROJECT-
Project (ID or number) where the notification config resides. Formatted as
or justprojects/789.789
- GCLOUD WIDE FLAGS
-
These flags are available to all commands:
--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.Run
$ gcloud helpfor details. - API REFERENCE
- This command uses the Security Command Center API. For more information, see Security Command Center API.
- NOTES
-
These variants are also available:
gcloudalphasccnotificationsdeletegcloudbetasccnotificationsdelete