NAME gcloud alpha scc muteconfigs get - get a Cloud Security Command Center mute config SYNOPSIS gcloud alpha scc muteconfigs get MUTE_CONFIG [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Get a Cloud Security Command Center mute config. EXAMPLES To get a mute config given organization 123 with id my-test-mute-config, run: $ gcloud alpha scc muteconfigs get my-test-mute-config \ --organization=organizations/123 $ gcloud alpha scc muteconfigs get my-test-mute-config \ --organization=123 $ gcloud alpha scc muteconfigs get \ organizations/123/muteConfigs/my-test-mute-config To get a mute config given folder 456 with id my-test-mute-config, run: $ gcloud alpha scc muteconfigs get my-test-mute-config \ --folder=folders/456 $ gcloud alpha scc muteconfigs get my-test-mute-config --folder=456 $ gcloud alpha scc muteconfigs get \ folders/456/muteConfigs/my-test-mute-config To get a mute config given project 789 with id my-test-mute-config, run: $ gcloud alpha scc muteconfigs get my-test-mute-config \ --project=projects/789 $ gcloud alpha scc muteconfigs get my-test-mute-config --project=789 $ gcloud alpha scc muteconfigs get \ projects/789/muteConfigs/my-test-mute-config POSITIONAL ARGUMENTS MUTE_CONFIG ID of the mute config or the full resource name of the mute config. FLAGS 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 securitycenter/v1 API. The full documentation for this API can be found at: https://cloud.google.com/security-command-center 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 muteconfigs get