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
{{ message }}
This repository has been archived by the owner on Nov 18, 2020. It is now read-only.
When a configured environment variable is not set, the library is printing out a warning stating the same, which is good, but in the log message it is also printing out all the environment variables which could be dangerous as some environment variables might have sensitive data like passwords. These logs could get shipped out to a log collector (like splunk) which can be viewed by the entire organization (at least in our case).
WARNING [org.jeasy.props.processors.EnvironmentVariableAnnotationProcessor processAnnotation] - Environment variable 'ENVIRONMENT' on field 'environment' of type 'com.test..Config' not found in environment variables: [all the env vars]
The text was updated successfully, but these errors were encountered:
When a configured environment variable is not set, the library is printing out a warning stating the same, which is good, but in the log message it is also printing out all the environment variables which could be dangerous as some environment variables might have sensitive data like passwords. These logs could get shipped out to a log collector (like splunk) which can be viewed by the entire organization (at least in our case).
And logs are like,
The text was updated successfully, but these errors were encountered: