gcloud logging views update - update a view
gcloud logging views update VIEW_ID --bucket=BUCKET --location=LOCATION [--description=DESCRIPTION] [--log-filter=LOG_FILTER] [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...]
Updates the properties of a view.
To update a view in your project, run:
$ gcloud logging views update my-view --bucket=my-bucket \ --location=global --description=my-new-description
- VIEW_ID
Id of the view to update.
- --bucket=BUCKET
ID of the bucket that holds the view
- --location=LOCATION
Location of the bucket that contains the view.
- --description=DESCRIPTION
New description for the view.
- --log-filter=LOG_FILTER
New filter for the view.
- At most one of these can be specified:
- --billing-account=BILLING_ACCOUNT_ID
Billing account of the view to update.
- --folder=FOLDER_ID
Folder of the view to update.
- --organization=ORGANIZATION_ID
Organization of the view to update.
- --project=PROJECT_ID
Project of the view to update.
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.
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.
These variants are also available:
$ gcloud alpha logging views update
$ gcloud beta logging views update