Skip to content

Commit

Permalink
docs: document usage of ENV overrides better (#97)
Browse files Browse the repository at this point in the history
* docs: document usage of ENV overrides better

* Update docs/configuration.md
  • Loading branch information
FUSAKLA authored Nov 3, 2022
1 parent 529e79b commit 2f64f54
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ Additional configuration files might be needed by some modules
depending on their needs and if they are used in the pipeline at all.

#### ENV variables
Every configuration option in the base YAML file can be overridden by using ENV variable.
Every configuration option in the base YAML file can be overridden (the configuration MUST be present in the yaml config for the ENV to be loaded, it can be even empty string) by using ENV variable.
The schema of ENV variable naming is `SLO_EXPORTER_` prefix and than in uppercase any key of the YAML
structure in uppercase without any underscores. Underscores are used for separating nested structures.
Example: `SLO_EXPORTER_WEBSERVERLISTENADDRESS=0.0.0.0:8080` or for module configuration `SLO_EXPORTER_TAILER_TAILEDFILE=access.log`
Expand Down

0 comments on commit 2f64f54

Please sign in to comment.