NETWAYS / NETWAYS/ansible-collection-elasticstack
Check flush handlers task
Open
Nobody has claimed this yet.
component:elasticsearch
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
We should check the need of flush handlers task in the elasticsearch-security.yml. If we can get rid of it, we can also delete the wait for task after it
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect elasticsearch-security.yml and locate the flush handlers task and the wait-for-task step that follows it. Trace how these tasks are used in the Elastic Stack setup, then verify whether removing both is safe; done means the need for the flush task is established and the file reflects the resulting decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, elasticsearch
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100