stratify 1.1.0

Layered configuration and structured logging for Rust services: pluggable sources, priority merging, typed access, and a tracing facade
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

//! Why lower numbers win, shown rather than described.
//!
//! ```bash
//! cargo run --example precedence
//! ```

use stratify::config::Builder;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    // Three sources all defining database.host. The TOML file has the lowest
    // priority number, so it is the one that wins.
    let store = Builder::default()
        .json("examples/config/base.json", 100) // host = localhost
        .yaml("examples/config/production.yaml", 50) // host = db.prod.internal
        .toml("examples/config/app.toml", 10) // host = db.toml.internal
        .build()
        .await?;

    println!(
        "winner: database.host = {:?}",
        store.get_str("database.host")
    );
    assert_eq!(
        store.get_str("database.host").as_deref(),
        Some("db.toml.internal")
    );

    // The point of the inverted ordering: adding a more specific source later
    // means giving it a smaller number, not renumbering everything already
    // there. Think ranking, not weight.
    println!(
        "app.workers survives from the base file: {:?}",
        store.get_str("app.workers")
    );
    Ok(())
}