mirrors/arti.git/crates/arti-config/src/lib.rs, branch arti-v0.1.0

Add warnings about configuration stability.

2022-02-28T19:25:24Z

Upgrade to newer version of config crate.

2022-02-25T14:20:48Z

Change deny(clippy::all) to warn(clippy::all).

2022-02-14T14:24:06Z

Closes #338.

Fix a doc link.

2022-02-04T21:03:39Z

arti-config: add blank lines between functions.

2022-02-02T18:08:03Z

arti-config: Small type and comment refactoring from review.

2022-02-02T18:05:57Z

Make configuration-watching configurable and off-by-default.

2022-02-01T21:04:59Z

I'm slightly concerned about whether this is behavior people would expect to have on-by-default, so let's make this off-by-default for now. Maybe the `application` and `system` sections should merge?

Reload configuration when our configuration files change.

2022-02-01T21:04:53Z

Closes #270

arti_config: Refactor configuration sources into a struct

2022-02-01T19:26:39Z

This is by no means our final API, but should represent an improvement. Here instead of having to specify a list of files and their is-this-optional status, along with a list of command-line options, we have a single structure that encapsulates all of that information. Two advantages here: - Callers no longer have to remember what the boolean means. - We can "reload" more easily, by keeping the source object around. This change also implements the correct behavior for our default configuration file in `arti::main`: if the file is absent and the user doesn't list a config file, that's no problem. But if the user lists _that very same config file, we should insist that it be present.

Tracing configuration for logfiles, per-target filters

2022-01-10T18:23:11Z

Previously we could only configure one global tracing filter that applied to stdout and journald. There was no support for log files, either. This patch fixes both issues, by substantially revising the configuration format: There are now separate filters for each log file, for journald, and for the console log. Because we want to allow multiple logfiles, they have to go into an array in the configuration. The configuration logic has grown a bit complicated in its types, since the tracing_subscriber crate would prefer to have the complete structure of tracing Layers known statically. That's fine when you know how many you have, and which kinds there will be, but for the runtime-configuration case we need to mess around with `Box`. I also had to switch from tracing_subscriber's EnvFilter to its Targets filter. It seems "EnvFilter" can only be applied as a Layer in itself, and won't work as a Filter on an individual Layer. Closes #166. Closes #170.