fastly logging honeycomb update

Update a Honeycomb logging endpoint on a Fastly service version

Options

NameDescription
--version <version>'latest', 'active', or the number of a specific version
--autocloneIf the selected service version is not editable, clone it and use the clone
--name <name>The name of the Honeycomb 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 Honeycomb logging object
--format <format>Apache style log formatting. Your log must produce valid JSON that Honeycomb can ingest
--format-version <format-version>The version of the custom logging format used for the configured endpoint. Can be either 2 (default) or 1
--dataset <dataset>The Honeycomb Dataset you want to log to
--auth-token <auth-token>The Write Key from the Account page of your Honeycomb account
--response-condition <response-condition>The name of an existing condition in the configured endpoint, or leave blank to always execute
--placement <placement>Where in the generated VCL the logging call should be placed, overriding any format_version default. Can be none or waf_debug