NAME

gcloud alpha scc notifications delete - delete a Cloud Security Command Center notification config

SYNOPSIS

gcloud alpha scc notifications delete NOTIFICATION_CONFIG_ID [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...]

DESCRIPTION

(ALPHA) Delete a Cloud Security Command Center notification config.

EXAMPLES

Delete notification config 'my-config' from organization 123

$ gcloud alpha scc notifications delete my-config --organization=123 $ gcloud alpha scc notifications delete \ organizations/123/notificationConfigs/my-config

Delete notification config 'my-config' from folder 456

$ gcloud alpha scc notifications delete my-config --folder=456 $ gcloud alpha scc notifications delete \ folders/456/notificationConfigs/my-config

Delete notification config 'my-config' from project 789

$ gcloud alpha scc notifications delete my-config --project=789 $ gcloud alpha scc notifications delete \ projects/789/notificationConfigs/my-config

POSITIONAL ARGUMENTS

NOTIFICATION_CONFIG_ID

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

FLAGS

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 securitycenter/v1 API. The full documentation for this API can be found at: https://cloud.google.com/security-command-center

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 delete

$ gcloud beta scc notifications delete