.TH "GCLOUD_ALPHA_SCC_NOTIFICATIONS_UPDATE" 1



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



.SH "SYNOPSIS"
.HP
\f5gcloud alpha scc notifications update\fR \fINOTIFICATION_CONFIG_ID\fR [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-filter\fR=\fIFILTER\fR] [\fB\-\-location\fR=\fILOCATION\fR;\ default="global"] [\fB\-\-pubsub\-topic\fR=\fIPUBSUB_TOPIC\fR] [\fB\-\-folder\fR=\fIFOLDER\fR\ |\ \fB\-\-organization\fR=\fIORGANIZATION\fR\ |\ \fB\-\-project\fR=\fIPROJECT\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Update 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"

Update all mutable fields under an organization parent \f5test\-config\fR
(description + pubsub topic + filter):

.RS 2m
$ gcloud alpha scc notifications update scc notifications update \e
    test\-config \-\-organization=123 \-\-description="New description" \e
    \-\-pubsub\-topic="projects/22222/topics/newtopic"
.RE

Update all mutable fields under a folder parent \f5test\-config\fR (description
+ pubsub topic + filter):

.RS 2m
$ gcloud alpha scc notifications update scc notifications update \e
    test\-config \-\-folder=456 \-\-description="New description" \e
    \-\-pubsub\-topic="projects/22222/topics/newtopic"
.RE

Update all mutable fields under a project parent \f5test\-config\fR (description
+ pubsub topic + filter):

.RS 2m
$ gcloud alpha scc notifications update scc notifications update \e
    test\-config \-\-project=789 \-\-description="New description" \e
    \-\-pubsub\-topic="projects/22222/topics/newtopic"
.RE

Update test\-config's description

.RS 2m
$ gcloud alpha scc notifications update test\-config \e
    \-\-organization=123 \-\-description="New description"
.RE

Update test\-config's pubsub\-topic

.RS 2m
$ gcloud alpha scc notifications update test\-config \e
    \-\-organization=123 \e
    \-\-pubsub\-topic="projects/22222/topics/newtopic"
.RE

Update test\-config's filter

.RS 2m
$ gcloud alpha scc notifications update test\-config \e
    \-\-organization=123 \-\-filter='state = \e"ACTIVE\e"'
.RE

Update all mutable fields for \f5test\-config\fR with \f5location=global\fR
under an organization parent (description + pubsub topic + filter):

.RS 2m
$ gcloud alpha scc notifications update scc notifications update \e
    test\-config \-\-organization=123 \-\-description="New description" \e
    \-\-pubsub\-topic="projects/22222/topics/newtopic" \e
    \-\-location=global
.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\-\-description\fR=\fIDESCRIPTION\fR

The text that will be used to describe a notification configuration.

.TP 2m
\fB\-\-filter\fR=\fIFILTER\fR

The filter string which will applied to events of findings of a notification
configuration.

.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\fR flag only if the
\f5notificationConfig\fR resource was created by using the Security Command
Center API v2, in which case, the only valid location is \f5global\fR.

.TP 2m
\fB\-\-pubsub\-topic\fR=\fIPUBSUB_TOPIC\fR

The Pub/Sub topic which will receive notifications. Its format is
"projects/[project_id]/topics/[topic]".

.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"

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:

.RS 2m
$ gcloud scc notifications update
.RE

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