Skip to content
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

Open
alexfouche opened this issue Jul 13, 2023 · 1 comment · May be fixed by #1234
Open

why was log4j2.properties.erb configuration commented ? #1200

alexfouche opened this issue Jul 13, 2023 · 1 comment · May be fixed by #1234

Comments

@alexfouche
Copy link

How to reproduce (e.g Puppet code you use)

Set Elasticsearch logging options

    class { 'elasticsearch':
        file_rolling_type             => 'rollingFile',
        rolling_file_max_backup_index => 14,
        rolling_file_max_file_size    => '256MB',

What are you seeing

/etc/elasticsearch/log4j2.properties is not modified

What behaviour did you expect instead

/etc/elasticsearch/log4j2.properties to be modified

Question

Why was templating the log4j2.properties been disabled ? The block is completely commented in manifests/config.pp It seems to come from commit 67a0720

Why ?

Currently the Puppet module seems to allow no way to configure Elasticsearch logging

@bmagistro
Copy link

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....

@phaedriel phaedriel linked a pull request Jul 31, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants