fastly logging splunk update
Update a Splunk 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 Splunk 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 Splunk logging object |
--url <url> | The URL to POST to |
--tls-ca-cert <tls-ca-cert> | A secure certificate to authenticate the server with. Must be in PEM format |
--tls-hostname <tls-hostname> | The hostname used to verify the server's certificate. It can either be the Common Name or a Subject Alternative Name (SAN) |
--tls-client-cert <tls-client-cert> | The client certificate used to make authenticated requests. Must be in PEM format |
--tls-client-key <tls-client-key> | The client private key used to make authenticated requests. Must be in PEM format |
--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 (default) or 1 |
--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. This field is not required and has no default value |
--auth-token <auth-token> |