Skip to content

Commit 537f66f

Browse files
Update administration/configuring-fluent-bit/yaml/environment-variables-section.md
Co-authored-by: Alexa Kreizinger <[email protected]> Signed-off-by: Lynette Miles <[email protected]>
1 parent 3da9e70 commit 537f66f

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

administration/configuring-fluent-bit/yaml/environment-variables-section.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,7 @@
22

33
The `env` section lets you define environment variables directly within the configuration file. These variables can then be used to dynamically replace values throughout your configuration using the `${VARIABLE_NAME}` syntax.
44

5-
Values set in the `env` section are case-sensitive. However, as a best practice,
6-
Fluent Bit recommends using uppercase names for environment variables. The following
7-
example defines two variables, `FLUSH_INTERVAL` and `STDOUT_FMT`, which can be
8-
accessed in the configuration using `${FLUSH_INTERVAL}` and `${STDOUT_FMT}`:
5+
Values set in the `env` section are case-sensitive. However, as a best practice, Fluent Bit recommends using uppercase names for environment variables. The following example defines two variables, `FLUSH_INTERVAL` and `STDOUT_FMT`, which can be accessed in the configuration using `${FLUSH_INTERVAL}` and `${STDOUT_FMT}`:
96

107
```yaml
118
env:

0 commit comments

Comments
 (0)