gcloud scc muteconfigs create

NAME
gcloud scc muteconfigs create - create a Security Command Center mute config
SYNOPSIS
gcloud scc muteconfigs create MUTE_CONFIG [--description=DESCRIPTION] [--expiry-time=EXPIRY_TIME] [--filter=FILTER] [--___location=LOCATION; default="global"] [--type=TYPE; default="static"] [--folder=FOLDER     | --organization=ORGANIZATION     | --project=PROJECT] [GCLOUD_WIDE_FLAG]
DESCRIPTION
Create a Security Command Center mute config.
EXAMPLES
To create a mute config test-mute-config given organization 123 with a filter on category that equals to XSS_SCRIPTING, run:
gcloud scc muteconfigs create test-mute-config --organization=123 --description="This is a test mute config" --filter="category=\"XSS_SCRIPTING\""

To create a mute config test-mute-config given folder 456 with a filter on category that equals to XSS_SCRIPTING, run:

gcloud scc muteconfigs create test-mute-config --folder=456 --description="This is a test mute config" --filter="category=\"XSS_SCRIPTING\""

To create a mute config test-mute-config given project 789 with a filter on category that equals to XSS_SCRIPTING, run:

gcloud scc muteconfigs create test-mute-config --project=789 --description="This is a test mute config" --filter="category=\"XSS_SCRIPTING\""

To create a mute config test-mute-config given organization 123, ___location=eu with a filter on category that equals to XSS_SCRIPTING, run:

gcloud scc muteconfigs create test-mute-config --organization=123 --description="This is a test mute config" --filter="category=\"XSS_SCRIPTING\"" --___location=eu
POSITIONAL ARGUMENTS
MUTE_CONFIG
ID of the mute config or the full resource name of the mute config.
FLAGS
--description=DESCRIPTION
The text that will be used to describe a mute configuration.
--expiry-time=EXPIRY_TIME
The expiry of the mute config. Only applicable for dynamic configs. If the expiry is set, when the config expires, it is removed from all findings. See $ gcloud topic datetimes for information on supported time formats.
--filter=FILTER
The filter string which will applied to findings muted by a mute configuration.
--___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.
--type=TYPE; default="static"
The mute configuration type. Immutable after creation. TYPE must be one of: static, dynamic.
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.
NOTES
This variant is also available:
gcloud alpha scc muteconfigs create