gcloud alpha scc notifications update

NAME: 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] [--location=LOCATION; default="global"] [--pubsub-topic=PUBSUB_TOPIC] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG …]
DESCRIPTION: (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 test-config (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"

Update all mutable fields under a folder parent test-config (description + pubsub topic + filter):
gcloud alpha scc notifications update scc notifications update test-config --folder=456 --description="New description" --pubsub-topic="projects/22222/topics/newtopic"

Update all mutable fields under a project parent test-config (description + pubsub topic + filter):
gcloud alpha scc notifications update scc notifications update test-config --project=789 --description="New description" --pubsub-topic="projects/22222/topics/newtopic"

Update test-config's description
gcloud alpha scc notifications update test-config --organization=123 --description="New description"

Update test-config's pubsub-topic
gcloud alpha scc notifications update test-config --organization=123 --pubsub-topic="projects/22222/topics/newtopic"

Update test-config's filter
gcloud alpha 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 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

The ID of the notification config. Formatted as "organizations/123/notificationConfigs/456" or just "456".
FLAGS: --description=DESCRIPTION

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

--filter=FILTER

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

--location=LOCATION; default="global"

Required if either data residency is enabled or the notificationConfig 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 /locations/``LOCATION´´ in the full name or specify the --location flag only if the notificationConfig resource was created by using the Security Command Center API v2, in which case, the only valid location is global.

--pubsub-topic=PUBSUB_TOPIC

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

At most one of these can be specified:

--folder=FOLDER

Folder where the notification config resides. Formatted as folders/456 or just 456.

--organization=ORGANIZATION

Organization where the notification config resides. Formatted as organizations/123 or just 123.

--project=PROJECT

Project (ID or number) where the notification config resides. Formatted as projects/789 or just 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 help for details.
API REFERENCE: This command uses the Security Command Center API. For more information, see Security Command Center API.
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 scc notifications update

gcloud beta scc notifications update