mirror of
https://github.com/aljazceru/kata-containers.git
synced 2025-12-28 19:44:21 +01:00
bcf3e82cf0
Raise the `slog` maximum log level feature for release code from `info` to `debug` by changing the `slog` maximum level features in the shared `logging` crate. This allows the consumers of the `logging` crate (the agent, the `trace-forwarder` and the `agent-ctl` tool) to produce debug output when their debug options are enabled. Currently, those options will essentially be a NOP (unless using a debug version of the code). Testing showed that setting the `slog` maximum level features in the rust manifest files for the consumers of the `logging` crate has no impact: those values are ignored, so they have been removed and replaced with a comment stating the levels are set in the `logging` crate. Fixes: #2966. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
22 lines
683 B
TOML
22 lines
683 B
TOML
[package]
|
|
name = "logging"
|
|
version = "0.1.0"
|
|
authors = ["The Kata Containers community <kata-dev@lists.katacontainers.io>"]
|
|
edition = "2018"
|
|
|
|
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
|
|
|
|
[dependencies]
|
|
serde_json = "1.0.39"
|
|
# slog:
|
|
# - Dynamic keys required to allow HashMap keys to be slog::Serialized.
|
|
# - The 'max_*' features allow changing the log level at runtime
|
|
# (by stopping the compiler from removing log calls).
|
|
slog = { version = "2.5.2", features = ["dynamic-keys", "max_level_trace", "release_max_level_debug"] }
|
|
slog-json = "2.3.0"
|
|
slog-async = "2.3.0"
|
|
slog-scope = "4.1.2"
|
|
|
|
[dev-dependencies]
|
|
tempfile = "3.1.0"
|