1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-08 10:35:03 +00:00
gcloud-help/gcloud/scc/muteconfigs/update
2024-02-29 10:17:22 +00:00

103 lines
3.9 KiB
Text

NAME
gcloud scc muteconfigs update - update a Security Command Center mute
config
SYNOPSIS
gcloud scc muteconfigs update MUTE_CONFIG [--description=DESCRIPTION]
[--filter=FILTER] [--location=LOCATION; default="global"]
[--update-mask=UPDATE_MASK]
[--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Update a Security Command Center mute config.
EXAMPLES
Update a mute config with ID=test-mute-config under organization=123 with a
filter on category that equals to XSS_SCRIPTING:
$ gcloud scc muteconfigs update test-mute-config \
--organization=123 --description="This is a test mute config" \
--filter="category=\"XSS_SCRIPTING\""
Update a mute config with ID=test-mute-config under folder=456 with a
filter on category that equals to XSS_SCRIPTING:
$ gcloud scc muteconfigs update test-mute-config --folder=456 \
--description="This is a test mute config" \
--filter="category=\"XSS_SCRIPTING\""
Update a mute config with ID=test-mute-config under project=789 with a
filter on category that equals to XSS_SCRIPTING:
$ gcloud scc muteconfigs update test-mute-config --project=789 \
--description="This is a test mute config" \
--filter="category=\"XSS_SCRIPTING\""
Update a mute config with ID=test-mute-config under organization=123
location=eu with a filter on category that equals to XSS_SCRIPTING:
$ gcloud scc muteconfigs update 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.
--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.
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.
--update-mask=UPDATE_MASK
Optional: If left unspecified (default), an update-mask is
automatically created using the flags specified in the command and only
those values are updated.
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 variant is also available:
$ gcloud alpha scc muteconfigs update