You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it is expected that a variable is passed in when the container is run that would set this value i.e. KMS_LOGGING_LOGSTASH: "true" to turn logging on. By only checking whether the variable is defined, something like KMS_LOGGING_LOGSTASH: "false" would also enable logging which is quite counterintuitive/wrong.
I think the condition should be adjusted to something where the configuration makes more sense e.g:
Currently the logstash config looks for whether the
KMS_LOGGING_LOGSTASH
variable is defined to determine whether to enable logging or not.I think it is expected that a variable is passed in when the container is run that would set this value i.e.
KMS_LOGGING_LOGSTASH: "true"
to turn logging on. By only checking whether the variable is defined, something likeKMS_LOGGING_LOGSTASH: "false"
would also enable logging which is quite counterintuitive/wrong.I think the condition should be adjusted to something where the configuration makes more sense e.g:
I'm not sure if there are better ways of doing this e.g. parsing the env variable to a real boolean rather than true/false wrapped in a string.
Also, this config should probably be documented in the how-to-run-it section of the README.
The text was updated successfully, but these errors were encountered: