dynamic-config-axum
A request-scoped dynamic-config snapshot
for axum: one tower layer, one extractor.
[]
= "0.1.0"
use ;
use sections;
async
let app = new
.route
.layer;
Both sections come from one reading taken when the request began, so a reload landing mid-request cannot show one response two generations.
The layer owns no lifecycle: loading, watching and the WatchHandle stay in
your main, unchanged.
See the workspace README for the problem this solves, and
cargo run -p dynamic-config-axum --example axum_two_sections for a
runnable demonstration.
MIT licensed.