Version history

0.3 (TBD)

In service.proto a change was made to allow both Output and error_detail to co-exist at the same time.
Both nighthawk_client and nighthawk_service will indicate execution failure (respectively through exit code or grpc reply) when connection errors and/or status code errors are observed by default.
The simple warmup we performed earlier has been removed, to eliminate counter pollution. This will be restored when configuration of phases lands in a next release. For those who need the old behavior, --simple-warmup can be configured to opt-in to the old-style behavior again.

--request-body-file sends a file's bytes verbatim as the request body (binary safe; no Content-Type is set). The RequestOptions.request_body (bytes) field carries it over the gRPC service API. Mutually exclusive with --request-body-size.
OptionsImpl::toCommandLineOptions() now always emits request_options.request_body_size; it was only set when at least one --request-header was configured, so the size was lost on the gRPC service path otherwise.
The Envoy exception on the tunneling startup path is logged instead of printed to stdout, keeping stdout reserved for the formatted output.
Introducing termination predicates (envoyproxy#167) and envoyproxy#176

Nighthawk as a service: (envoyproxy#22)
Add option to control how request pacing is maintained (envoyproxy#80)
Add python orchestration for integration testing: envoyproxy#50
Benchmark client configuration options:
- Connection-pool configuration envoyproxy#45
- Allow control of TLS ciphers and settings envoyproxy#32
- Measure time spend waiting on a full connection queue: envoyproxy#97

Initial release.