gcloud beta logging buckets undelete

NAME

gcloud beta logging buckets undelete - undelete a bucket

SYNOPSIS

gcloud beta logging buckets undelete BUCKET_ID --location=LOCATION [--billing-account=BILLING_ACCOUNT_ID     | --folder=FOLDER_ID     | --organization=ORGANIZATION_ID     | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG …]

EXAMPLES

To undelete bucket 'my-bucket' in location 'global', run:

gcloud beta logging buckets undelete my-bucket --location=global

POSITIONAL ARGUMENTS

BUCKET_ID

ID of the bucket to undelete.

REQUIRED FLAGS

--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 bucket to undelete.

--folder=FOLDER_ID

Folder of the bucket to undelete.

--organization=ORGANIZATION_ID

Organization of the bucket to undelete.

--project=PROJECT_ID

Project of the bucket to undelete.

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.

NOTES

This command is currently in beta and might change without notice. These variants are also available:

gcloud logging buckets undelete

gcloud alpha logging buckets undelete