gcloud logging scopes describe

NAME

gcloud logging scopes describe - display information about a log scope

SYNOPSIS

gcloud logging scopes describe LOG_SCOPE_ID [--folder=FOLDER_ID     | --organization=ORGANIZATION_ID     | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG …]

DESCRIPTION

Display information about a log scope.

EXAMPLES

To describe a log scope in a project, run:

gcloud logging scopes describe my-scope --project=my-project

POSITIONAL ARGUMENTS

LOG_SCOPE_ID

The ID of the log scope to describe.

FLAGS

At most one of these can be specified:

--folder=FOLDER_ID

Folder of the log scope to describe.

--organization=ORGANIZATION_ID

Organization of the log scope to describe.

--project=PROJECT_ID

Project of the log scope to describe.

The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be listed using gcloud config list --format='text(core.project)' and can be set using gcloud config set project PROJECTID.

--project and its fallback core/project property play two roles in the invocation: they specify both the project of the resource to operate on, and the project for API enablement checks, quota, and billing. To specify a different project for quota and billing, use the --billing-project flag or the billing/quota_project property.

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.