gcloud alpha logging buckets delete

NAME
gcloud alpha logging buckets delete - delete a bucket
SYNOPSIS
gcloud alpha logging buckets delete BUCKET_ID --location=LOCATION [--billing-account=BILLING_ACCOUNT_ID     | --folder=FOLDER_ID     | --organization=ORGANIZATION_ID     | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG]
DESCRIPTION
(ALPHA) Delete a bucket.
POSITIONAL ARGUMENTS
BUCKET_ID
ID of the bucket to delete.
REQUIRED FLAGS
--location=LOCATION
Location of the bucket.
OPTIONAL FLAGS
At most one of these may be specified:
--billing-account=BILLING_ACCOUNT_ID
Delete a bucket associated with this billing account.
--folder=FOLDER_ID
Delete a bucket associated with this folder.
--organization=ORGANIZATION_ID
Delete a bucket associated with this organization.
--project=PROJECT_ID
Delete a bucket associated with this project.

The Google Cloud Platform project name 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: --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
This command is currently in ALPHA and may change without notice. If this command fails with API permission errors despite specifying the right project, you may be trying to access an API with an invitation-only early access whitelist.