gcloud alpha scc notifications delete

NAME
gcloud alpha scc notifications delete - delete a Security Command Center notification config
SYNOPSIS
gcloud alpha scc notifications deleteNOTIFICATION_CONFIG_ID[--location=LOCATION; default="global"][--folder=FOLDER    |--organization=ORGANIZATION    |--project=PROJECT][GCLOUD_WIDE_FLAG …]
DESCRIPTION
(ALPHA) Delete a Security Command Center notification config.

Notification configs that are created with Security Command Center API V2 andlater include alocation attribute. If thelocationattribute is included in the resource name of a Notification configs, you mustspecify it when referencing the Notification config. For example, the followingNotification configs name haslocation=eu:organizations/123/locations/eu/notificationConfigs/test-config.

EXAMPLES
Delete notification config 'test-config' from organization123
gcloudalphasccnotificationsdeletetest-config--organization=123

Delete notification config 'test-config' from folder456

gcloudalphasccnotificationsdeletetest-config--folder=456

Delete notification config 'test-config' from project789

gcloudalphasccnotificationsdeletetest-config--project=789

Delete notification config 'test-config' with locationglobal fromorganization123

gcloudalphasccnotificationsdeletetest-config--organization=123--location=global

Delete notification config 'test-config' withlocation=eu fromorganization123

gcloudalphasccnotificationsdeletetest-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 thenotificationConfig was created by using the API v2.

If data residency is enabled, specify the Security Command Center location inwhich the notification is stored.

If data residency is not enabled, include/locations/``LOCATION´´ in the full name or specify the--location flag only if thenotificationConfig wascreated by using the Security Command Center API v2, in which case, the onlyvalid location isglobal.

At most one of these can be specified:
--folder=FOLDER
Folder where the notification config resides. Formatted asfolders/456 or just456.
--organization=ORGANIZATION
Organization where the notification config resides. Formatted asorganizations/123 or just123.
--project=PROJECT
Project (ID or number) where the notification config resides. Formatted asprojects/789 or just789.
GCLOUD WIDE FLAGS
These flags are available to all commands:--access-token-file,--account,--billing-project,--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 Security Command Center API. For more information, seeSecurityCommand Center API.
NOTES
This command is currently in alpha and might change without notice. If thiscommand fails with API permission errors despite specifying the correct project,you might be trying to access an API with an invitation-only early accessallowlist. These variants are also available:
gcloudsccnotificationsdelete
gcloudbetasccnotificationsdelete

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-05-07 UTC.