gcloud logging links describe

NAME
gcloud logging links describe - display information about a linked dataset
SYNOPSIS
gcloud logging links describe LINK_ID --bucket=BUCKET --location=LOCATION [--billing-account=BILLING_ACCOUNT_ID     | --folder=FOLDER_ID     | --organization=ORGANIZATION_ID     | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG]
DESCRIPTION
Display information about a linked dataset.
EXAMPLES
To describe a linked dataset in a project, run:
gcloud logging links describe my-link --bucket=my-bucket --location=global
POSITIONAL ARGUMENTS
Id of the linked dataset to describe.
REQUIRED FLAGS
--bucket=BUCKET
ID of bucket
--location=LOCATION
Location of the bucket.
OPTIONAL FLAGS
At most one of these can be specified:
--billing-account=BILLING_ACCOUNT_ID
Billing account of the linked dataset to describe.
--folder=FOLDER_ID
Folder of the linked dataset to describe.
--organization=ORGANIZATION_ID
Organization of the linked dataset to describe.
--project=PROJECT_ID
Project of the linked dataset 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. It specifies the project of the resource to operate on. It also specifies the project for API enablement check, quota, and billing. To specify a different project for quota and billing, use --billing-project or 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.

NOTES
These variants are also available:
gcloud alpha logging links describe
gcloud beta logging links describe