Tags: eaze/preroll
Tags
0.9.0
This release changes test database naming inference and `/monitor/ping` output.
### Changes
- Change: `/monitor/ping` now randomly generates a human-readable name at start-up, and will reply with that for the process duration.
- Change: the default postgres test database name is now `{crate_name}-test`.
### Additions
- Support for overriding `host`, `name` and `port` for the postgres test database.
0.8.0
### Additions
- New `"lambda-http"` feature, which changes the HTTP listener to connect to an AWS Lambda execution environment.
- Is no longer reachable as a regular http server, but accepts http lambda requests as if it were one.
- Some environment variables, such as `PORT`, are disregarded.
- If the `"honeycomb"` feature is enabled, trace events are written to stdout, and must be collected via
a layer provided by Honeycomb. See: https://docs.honeycomb.io/getting-data-in/integrations/aws/aws-lambda/
0.7.0
### Changes
- The default backend for the included Surf http client has changed from libcurl (via Isahc) to http-client's async-h1 client.
- `honeycomb`: Environemtn variables now start with `HONEYCOMB_` rather than `HONEYCOMBIO_`.
- Consistency with other honeycomb SDK's.
- `honeycomb`: `HONEYCOMBIO_WRITE_KEY` is now `HONEYCOMB_WRITEKEY` (required).
- Consistency with other honeycomb SDK's.
### Additions
- `honeycomb`: Added `HONEYCOMB_SAMPLE_RATE` environment var usage.
0.6.0 ### Additions - `postgres`: Added a `PGMAXLIFETIME` environemnt variable, set in minutes. ### Dependencies - `honeycomb`: Switched back to `tracing-honeycomb` and upgraded to `0.3`. - This allows patch upgrades to be picked up via `cargo update`, and is otherwise identical to `0.2.1-eaze.7`.
PreviousNext