fastly logging sumologic update

Update a Sumologic 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 Sumologic 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 Sumologic logging object
--url <url>The URL to POST to
--format <format>Apache style log formatting
--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
--response-condition <response-condition>The name of an existing condition in the configured endpoint, or leave blank to always execute
--message-type <message-type>How the message should be formatted. One of: classic (default), loggly, logplex or blank
--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