Struct MultiConfig 

pub struct MultiConfig { /* private fields */ }

Implementations

impl MultiConfig

Create a configuration that uses the given list of configs to try and get values. If a value isn’t found, the next config on the list is consulted. This allows your to create a set of configs that can override values as needed. For example, creating a MultiConfig with !vec[environment, instance-config-file, global-config-file, default-values] would provide something like you’d expect in a 12-factor app.

pub fn new(configs: Vec<Box<dyn Config>>) -> Self

Trait Implementations

impl Config for MultiConfig

fn get(&self, key: &str) -> Option<String>

Returns the value associated with the given key.

fn must_get(&self, key: &str) -> String

Similar to get but panics if there is no value.

fn string(&self, key: &str) -> String

Get the value as a string or panics if one isn’t found.

fn int(&self, key: &str) -> i64

Get the value as an integer or panics if one isn’t found or cannot be parsed.

fn float(&self, key: &str) -> f64

Get the value as a float or panics if one isn’t found or cannot be parsed.

fn bool(&self, key: &str) -> bool

Get the value as a bool or panics if one isn’t found or cannot be parsed. The following case-insensitive values are considered true: t, true, 1, y, yes. All other values are considered false.

fn duration(&self, key: &str) -> Duration

Get the value as a duration or panics if one isn’t found or can’t be parsed. Thre doesn’t appear to be a parsing function for a duration, so it attempts to convert to an integer and use that as the number of seconds.

fn datetime(&self, key: &str) -> DateTime<Utc>

Get the value as a duration or panics if one isn’t found or it can’t be parsed. It uses RFC339 to parse it.

fn list(&self, key: &str) -> Vec<String>

Get a list or panics if one isn’t found. The list should be a comma-delimited list surrouned by brackets (e.g. [1, 2, 3] => vec![“1”, “2”, “3”].

fn map(&self, key: &str) -> HashMap<String, String>

Get a map or panics if one isn’t found. The list should be a comma-delimited list surrouned by braces with key/value pairs associated with => (e.g. {a=>1, b=>2, c=>3} => ((a,1), (b,2), (c,3))).