.TH "GCLOUD_SCC_NOTIFICATIONS_DELETE" 1



.SH "NAME"
.HP
gcloud scc notifications delete \- delete a Security Command Center notification config



.SH "SYNOPSIS"
.HP
\f5gcloud scc notifications delete\fR \fINOTIFICATION_CONFIG_ID\fR [\fB\-\-location\fR=\fILOCATION\fR;\ default="global"] [\fB\-\-folder\fR=\fIFOLDER\fR\ |\ \fB\-\-organization\fR=\fIORGANIZATION\fR\ |\ \fB\-\-project\fR=\fIPROJECT\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Delete a Security Command Center notification config.

Notification configs that are created with Security Command Center API V2 and
later include a \f5location\fR attribute. If the \f5location\fR 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 \f5location=eu\fR:
\f5organizations/123/locations/eu/notificationConfigs/test\-config\fR.



.SH "EXAMPLES"

Delete notification config 'test\-config' from organization \f5123\fR

.RS 2m
$ gcloud scc notifications delete test\-config \-\-organization=123
.RE

Delete notification config 'test\-config' from folder \f5456\fR

.RS 2m
$ gcloud scc notifications delete test\-config \-\-folder=456
.RE

Delete notification config 'test\-config' from project \f5789\fR

.RS 2m
$ gcloud scc notifications delete test\-config \-\-project=789
.RE

Delete notification config 'test\-config' with location \f5global\fR from
organization \f5123\fR

.RS 2m
$ gcloud scc notifications delete test\-config \-\-organization=123 \e
    \-\-location=global
.RE

Delete notification config 'test\-config' with \f5location=eu\fR from
organization \f5123\fR

.RS 2m
$ gcloud scc notifications delete test\-config \-\-organization=123 \e
    \-\-location=eu
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fINOTIFICATION_CONFIG_ID\fR

The ID of the notification config. Formatted as
"organizations/123/notificationConfigs/456" or just "456".


.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-location\fR=\fILOCATION\fR; default="global"

Required if either data residency is enabled or the \f5notificationConfig\fR was
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 \f5/locations/``\fRLOCATION'' in the
full name or specify the \f5\-\-location flag\fR only if the
\f5notificationConfig\fR was created by using the Security Command Center API
v2, in which case, the only valid location is \f5global\fR.

.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-folder\fR=\fIFOLDER\fR

Folder where the notification config resides. Formatted as
\f5\fIfolders/456\fR\fR or just \f5\fI456\fR\fR.

.TP 2m
\fB\-\-organization\fR=\fIORGANIZATION\fR

Organization where the notification config resides. Formatted as
\f5\fIorganizations/123\fR\fR or just \f5\fI123\fR\fR.

.TP 2m
\fB\-\-project\fR=\fIPROJECT\fR

Project (ID or number) where the notification config resides. Formatted as
\f5\fIprojects/789\fR\fR or just \f5\fI789\fR\fR.


.RE
.RE
.sp

.SH "GCLOUD WIDE FLAGS"

These flags are available to all commands: \-\-access\-token\-file, \-\-account,
\-\-billing\-project, \-\-configuration, \-\-flags\-file, \-\-flatten,
\-\-format, \-\-help, \-\-impersonate\-service\-account, \-\-log\-http,
\-\-project, \-\-quiet, \-\-trace\-token, \-\-user\-output\-enabled,
\-\-verbosity.

Run \fB$ gcloud help\fR for details.



.SH "API REFERENCE"

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)



.SH "NOTES"

These variants are also available:

.RS 2m
$ gcloud alpha scc notifications delete
.RE

.RS 2m
$ gcloud beta scc notifications delete
.RE