-
-
Notifications
You must be signed in to change notification settings - Fork 479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
why was log4j2.properties.erb configuration commented ? #1200
Comments
Looks like #1185 tries to bring back managing this file but also not sure why that was removed. This was very unexpected when upgrading and does not appear to break anything when actually using the module. If it was just for tests maybe those should have been reviewed versus breaking/significantly altering how the application is configured.... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to reproduce (e.g Puppet code you use)
Set Elasticsearch logging options
What are you seeing
/etc/elasticsearch/log4j2.properties
is not modifiedWhat behaviour did you expect instead
/etc/elasticsearch/log4j2.properties
to be modifiedQuestion
Why was templating the
log4j2.properties
been disabled ? The block is completely commented inmanifests/config.pp
It seems to come from commit 67a0720Why ?
Currently the Puppet module seems to allow no way to configure Elasticsearch logging
The text was updated successfully, but these errors were encountered: