NAME
    gcloud scc muteconfigs get - get a Security Command Center mute config

SYNOPSIS
    gcloud scc muteconfigs get MUTE_CONFIG
        [--location=LOCATION; default="global"]
        [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT]
        [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    Get a Security Command Center mute config.

EXAMPLES
    To get a mute config given organization 123 with id test-mute-config, run:

        $ gcloud scc muteconfigs get test-mute-config --organization=123

    To get a mute config given folder 456 with id test-mute-config, run:

        $ gcloud scc muteconfigs get test-mute-config --folder=456

    To get a mute config given project 789 with id test-mute-config, run:

        $ gcloud scc muteconfigs get test-mute-config --project=789

    To get a mute config given organization 123 with id test-mute-config and
    location=eu, run:

        $ gcloud scc muteconfigs get test-mute-config --organization=123 \
            --location=eu

POSITIONAL ARGUMENTS
     MUTE_CONFIG
        ID of the mute config or the full resource name of the mute config.

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
        (https://cloud.google.com/security-command-center/docs/reference/rest/index.html?rep_location=global#regional-service-endpoint)
        you must specify the correct data location
        (https://cloud.google.com/security-command-center/docs/data-residency-support#locations)
        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.

     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 get

