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

SYNOPSIS
    gcloud alpha scc notifications delete NOTIFICATION_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
    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
    Delete notification config 'test-config' from organization 123

        $ gcloud alpha scc notifications delete test-config \
            --organization=123

    Delete notification config 'test-config' from folder 456

        $ gcloud alpha scc notifications delete test-config --folder=456

    Delete notification config 'test-config' from project 789

        $ gcloud alpha scc notifications delete test-config --project=789

    Delete notification config 'test-config' with location global from
    organization 123

        $ gcloud alpha scc notifications delete test-config \
            --organization=123 --location=global

    Delete notification config 'test-config' with location=eu from organization
    123

        $ gcloud alpha scc notifications delete test-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 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 was created by using the Security Command Center API
        v2, in which case, the only valid location is global.

     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.
    (https://cloud.google.com/security-command-center/docs/reference/rest)

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