NAME
    gcloud scc findings bulk-mute - bulk mute Security Command Center findings
        based on a filter

SYNOPSIS
    gcloud scc findings bulk-mute --filter=FILTER
        (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT)
        [--location=LOCATION; default="global"]
        [--mute-state=MUTE_STATE; default="muted"] [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    Bulk mute Security Command Center findings based on a filter.

EXAMPLES
    To bulk mute findings given organization 123 based on a filter on category
    that equals XSS_SCRIPTING, run:

        $ gcloud scc findings bulk-mute --organization=organizations/123 \
            --filter="category=\"XSS_SCRIPTING\""

    To bulk mute findings given folder 123 based on a filter on category that
    equals XSS_SCRIPTING, run:

        $ gcloud scc findings bulk-mute --folder=folders/123 \
            --filter="category=\"XSS_SCRIPTING\""

    To bulk mute findings given project 123 based on a filter on category that
    equals XSS_SCRIPTING, run:

        $ gcloud scc findings bulk-mute --project=projects/123 \
            --filter="category=\"XSS_SCRIPTING\""

    To bulk mute findings given organization 123 based on a filter on category
    that equals XSS_SCRIPTING and location=eu run:

        $ gcloud scc findings bulk-mute --organization=organizations/123 \
            --filter="category=\"XSS_SCRIPTING\"" --location=locations/eu

REQUIRED FLAGS
     --filter=FILTER
        Expression that identifies findings that should be muted.

     Exactly one of these must be specified:

       --folder=FOLDER
          Folder where the findings reside. Formatted as folders/456 or just
          456.

       --organization=ORGANIZATION
          Organization where the findings reside. Formatted as
          organizations/123 or just 123.

       --project=PROJECT
          Project (id or number) where the findings reside. Formatted as
          projects/789 or just 789.

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

        NOTE: If you override the endpoint to a regional endpoint
        (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint)
        you must specify the correct data location
        (https://cloud.google.com/security-command-center/docs/data-residency-support#locations)
        using this flag. 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.

        NOTE: If no location is specified, the default location is global AND
        the request will be routed to the SCC V1 API. To use the SCC V2 API -
        please explicitly specify the flag.

     --mute-state=MUTE_STATE; default="muted"
        Desired mute state of the finding. MUTE_STATE must be one of: muted,
        undefined.

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 variant is also available:

        $ gcloud alpha scc findings bulk-mute

