gcloud alpha scc findings set-mute

NAME
gcloud alpha scc findings set-mute - update a Security Command Center finding's mute state
SYNOPSIS
gcloud alpha scc findings set-mute FINDING --mute=MUTE [--location=LOCATION; default="global"] [--source=SOURCE] [--folder=FOLDER     | --organization=ORGANIZATION     | --project=PROJECT] [GCLOUD_WIDE_FLAG …]
DESCRIPTION
(ALPHA) Update a Security Command Center finding's mute state.
EXAMPLES
To update finding's mute state to MUTED, given finding organizations/123/sources/456/findings/789, run: 
gcloud alpha scc findings set-mute 789 --organization=organizations/123 --source=456 --mute=MUTED

To update finding's mute state to UNMUTED, given finding organizations/123/sources/456/findings/789, run: 

gcloud alpha scc findings set-mute 789 --organization=organizations/123 --source=456 --mute=UNMUTED

To update finding's mute state to MUTED, given finding folders/123/sources/456/findings/789, run: 

gcloud alpha scc findings set-mute 789 --folder=folders/123 --source=456 --mute=MUTED

To update finding's mute state to MUTED, given finding projects/123/sources/456/findings/789, run: 

gcloud alpha scc findings set-mute 789 --project=projects/123 --source=456 --mute=MUTED

To update finding's mute state to MUTED, given finding organizations/123/sources/456/findings/789 and location=eu, run: 

gcloud alpha scc findings set-mute 789 --organization=organizations/123 --source=456 --mute=MUTED --location=locations/eu
POSITIONAL ARGUMENTS
FINDING
ID of the finding or the full resource name of the finding.
REQUIRED FLAGS
--mute=MUTE
Desired mute state of the finding. MUTE must be one of: muted, unmuted, undefined.
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 you must specify the correct data location 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.

--source=SOURCE
ID of the source.
At most one of these can be specified:
--folder=FOLDER
Folder where the finding resides. Formatted as folders/456 or just 456.
--organization=ORGANIZATION
Organization where the finding resides. Formatted as organizations/123 or just 123.
--project=PROJECT
Project (id or number) where the finding 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. This variant is also available: 
gcloud scc findings set-mute