NAME
    gcloud alpha scc muteconfigs delete - delete a Security Command Center mute
        config

SYNOPSIS
    gcloud alpha scc muteconfigs delete MUTE_CONFIG
        [--location=LOCATION; default="global"]
        [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT]
        [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    (ALPHA) Delete a Security Command Center mute config.

EXAMPLES
    To delete a mute config given organization 123 with id test-mute-config,
    run:

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

    To delete a mute config given folder 456 with id test-mute-config, run:

        $ gcloud alpha scc muteconfigs delete test-mute-config --folder=456

    To delete a mute config given project 789 with id test-mute-config, run:

        $ gcloud alpha scc muteconfigs delete test-mute-config --project=789

    To delete a mute config given organization 123 with id test-mute-config and
    location=eu, run:

        $ gcloud alpha scc muteconfigs delete test-mute-config \
            --organization=123 --location=eu

POSITIONAL ARGUMENTS
     MUTE_CONFIG
        ID of the mute config or the full resource name of the mute config.

FLAGS
     --location=LOCATION; default="global"
        When data residency controls are enabled, this attribute specifies the
        location in which the resource is located and applicable. The location
        attribute can be provided as part of the fully specified resource name
        or with the --location argument on the command line. The default
        location is global.

        The default location on this command is unrelated to the default
        location that is specified when data residency controls are enabled for
        Security Command Center.

     At most one of these can be specified:

       --folder=FOLDER
          Folder where the mute config resides. Formatted as folders/456 or
          just 456.

       --organization=ORGANIZATION
          Organization where the mute config resides. Formatted as
          organizations/123 or just 123.

       --project=PROJECT
          Project (id or number) where the mute 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. This variant is also available:

        $ gcloud scc muteconfigs delete