-
Notifications
You must be signed in to change notification settings - Fork 2
Added allow_ilm_indices #1
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
base: master
Are you sure you want to change the base?
Conversation
Can someone tell me why the Travis CI failed? |
Hi @GFM-tt, this repo is a fork from an archived module. I can accept your PR, but I'm not sure this will benefit anyone except you and us ;) |
If you'd like this included into our fork, I'd simply ask you to fix the typos (I'll happily link them for you if needed) |
Hi @faxm0dem I actually didn't expected an answer :D So sorry for the long waiting time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, just fix the 3 typos please
# Default: 'False' | ||
# | ||
# [*allow_ilm_indices*] | ||
# Boolean. If allow_ilm_indices is set to True, Curator will ingonre all ILM taged Indices and querry them regardless of ILM Polices. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typos:
- ignore
- tagged
- query
I added the "allow_ilm_indices" option as documented in https://www.elastic.co/guide/en/elasticsearch/client/curator/current/option_allow_ilm.html
It allows curator to handle Indices which are taged with the ILM flag.
In version 6.8 of ELK there is still a bug that tags Indices with the ILM flag, even if its disabled by default in the Elastic output plugin.
The setting was tested with puppet in our env.
And works like a charm.