-
-
Notifications
You must be signed in to change notification settings - Fork 28
warn log level cannot be configured #2995
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Preflight checklist
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines."
- I could not find a solution in the existing issues, docs, nor discussions.
Describe the bug
Despite the documentation states there is a warn log level, it cannot be configured as the config validation results in an error shown below. If you now follow the hints from the log output and configure the log level to be warning, heimdall will start, but the log level will be error, as warning does not exist internally as log level and the implementation will fallback to the default one - which is error.
How can the bug be reproduced
Use e.g., the docker compose base example, configure the log level to be warn, and try to start e.g., the proxy based demo.
Relevant log output
heimdall-1 | Error: configuration error: jsonschema validation failed with 'file:///opt/heimdall/config.schema.json#'
heimdall-1 | - at '/log/level': value must be one of 'trace', 'debug', 'info', 'warning', 'error', 'fatal', 'panic'
heimdall-1 | configuration error: jsonschema validation failed with 'file:///opt/heimdall/config.schema.json#'
heimdall-1 | - at '/log/level': value must be one of 'trace', 'debug', 'info', 'warning', 'error', 'fatal', 'panic'
heimdall-1 exited with code 255Relevant configuration
log:
level: warnVersion
0.17.7
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Docker Compose
Additional Context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working