Skip to content

Commit

Permalink
Doc: Environment variables cannot be in config.string comments due to…
Browse files Browse the repository at this point in the history
… substitution logic.
  • Loading branch information
mashhurs committed Nov 18, 2024
1 parent a94659c commit 6820d47
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 1 deletion.
1 change: 1 addition & 0 deletions docs/static/env-vars.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ environment variable is undefined.
* You can add environment variable references in any plugin option type: string, number, boolean, array, or hash.
* Environment variables for list-type URI parameters can support lists of space-delimited values. Currently, other non-URI based options do not support lists of values. See <<plugin-concepts>>
* Environment variables are immutable. If you update the environment variable, you'll have to restart Logstash to pick up the updated value.
* Environment variables in `config.string` comments are not allowed. Remove the `$` sign to avoid pipeline config failures.

==== Examples

Expand Down
2 changes: 1 addition & 1 deletion docs/static/pipeline-configuration.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -310,7 +310,7 @@ input { # comments can appear at the end of a line, too
# ...
}
----------------------------------

NOTE: Due to a substitution logic, commenting environment `${var}` in `config.string` is not allowed. Remove the `$` sign to avoid pipeline config failures.

include::event-data.asciidoc[]
include::env-vars.asciidoc[]
Expand Down

0 comments on commit 6820d47

Please sign in to comment.