hyperi-rustlib 2.8.6

There's plenty of sage advice out there about how to run Rust services in production at scale — config cascades, structured logging, masking secrets, multi-backend secrets management, Prometheus, OpenTelemetry, Kafka transports, tiered disk-spillover sinks, adaptive worker pools, graceful shutdown — but almost none of it as code you can just install and use. This is that code. Opinionated, drop-in, working out of the box. The patterns from blog posts, watercooler chats and beers with your Google mates as actual library — not a framework you assemble from twenty crates and 8 weeks of munging.
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
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53

// Project:   hyperi-rustlib
// File:      src/cli/error.rs
// Purpose:   CLI error types
// Language:  Rust
//
// License:   BUSL-1.1
// Copyright: (c) 2026 HYPERI PTY LIMITED

//! Error types for the CLI module.

use thiserror::Error;

/// Errors from CLI operations.
#[derive(Debug, Error)]
pub enum CliError {
    /// Configuration loading failed.
    #[error("config error: {0}")]
    Config(String),

    /// Logger initialisation failed.
    #[error("logger error: {0}")]
    Logger(String),

    /// Metrics server failed.
    #[error("metrics error: {0}")]
    Metrics(String),

    /// Service runtime error.
    #[error("service error: {0}")]
    Service(String),

    /// Invalid CLI argument.
    #[error("invalid argument: {0}")]
    InvalidArgument(String),

    /// I/O error.
    #[error("I/O error: {0}")]
    Io(#[from] std::io::Error),
}

#[cfg(feature = "logger")]
impl From<crate::logger::LoggerError> for CliError {
    fn from(e: crate::logger::LoggerError) -> Self {
        Self::Logger(e.to_string())
    }
}

#[cfg(feature = "config")]
impl From<crate::config::ConfigError> for CliError {
    fn from(e: crate::config::ConfigError) -> Self {
        Self::Config(e.to_string())
    }
}