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

gcloud alpha scc muteconfigs deleteMUTE_CONFIG[--location=LOCATION; default="global"][--folder=FOLDER    |--organization=ORGANIZATION    |--project=PROJECT][GCLOUD_WIDE_FLAG …]

gcloudalphasccmuteconfigsdeletetest-mute-config--organization=123

To delete a mute config given folder456with idtest-mute-config, run:

gcloudalphasccmuteconfigsdeletetest-mute-config--folder=456

To delete a mute config given project789with idtest-mute-config, run:

gcloudalphasccmuteconfigsdeletetest-mute-config--project=789

To delete a mute config given organization123 with idtest-mute-config andlocation=eu, run:

gcloudalphasccmuteconfigsdeletetest-mute-config--organization=123--location=eu

MUTE_CONFIG

ID of the mute config or the full resource name of the mute config.

--location=LOCATION; default="global"

When data residency controls are enabled, this attribute specifies the locationin which the resource is located and applicable. Thelocationattribute can be provided as part of the fully specified resource name or withthe--location argument on the command line. The default locationisglobal.

NOTE: If you override the endpoint to aregionalendpoint you must specify the correctdatalocation using this flag. The default location on this command is unrelatedto the default location that is specified when data residency controls areenabled for Security Command Center.

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

At most one of these can be specified:

--folder=FOLDER

Folder where the mute config resides. Formatted asfolders/456 or just456.

--organization=ORGANIZATION

Organization where the mute config resides. Formatted asorganizations/123 or just123.

--project=PROJECT

Project (id or number) where the mute config resides. Formatted asprojects/789 or just789.

Run$gcloud help for details.