fastly logging bigquery update
Update a BigQuery logging endpoint on a Fastly service version
Options
| Name | Description |
|---|---|
--version <version> | 'latest', 'active', or the number of a specific version |
--autoclone | If the selected service version is not editable, clone it and use the clone |
--name <name> | The name of the BigQuery logging object |
--service-id <service-id> | Service ID (falls back to FASTLY_SERVICE_ID, then fastly.toml) |
--service-name <service-name> | The name of the service |
--new-name <new-name> | New name of the BigQuery logging object |
--project-id <project-id> | Your Google Cloud Platform project ID |
--dataset <dataset> | Your BigQuery dataset |
--table <table> | Your BigQuery table |
--user <user> | Your Google Cloud Platform service account email address. The client_email field in your service account authentication JSON |
--secret-key <secret-key> | Your Google Cloud Platform account secret key. The private_key field in your service account authentication JSON |
--template-suffix <template-suffix> | BigQuery table name suffix template |
--format <format> | Apache style log formatting. Must produce JSON that matches the schema of your BigQuery table |
--format-version <format-version> | The version of the custom logging format used for the configured endpoint. Can be either 2 (the default, version 2 log format) or 1 (the version 1 log format). The logging call gets placed by default in vcl_log if format_version is set to 2 and in vcl_deliver if format_version is set to 1 |
--placement <placement> | Where in the generated VCL the logging call should be placed, overriding any format_version default. Can be none or waf_debug. This field is not required and has no default value |
--response-condition <response-condition> | The name of an existing condition in the configured endpoint, or leave blank to always execute |