NETWAYS / NETWAYS/ansible-collection-elasticstack
Rework `--check` mode
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
There are lots of tasks that won't work as expected when run in --check mode. There are some precautions taken in elasticsearch-security.yml but most other will just fail when run with --check.
We need to go through all task lists and build exceptions or take otherwise care that --check can run through and will show valid results.
Thanks @afeefghannam89 for pointing this out and showing me lots of background information!
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
Start by reviewing the precautions in elasticsearch-security.yml and then inspect the other task lists in the collection. Run the tasks with Ansible's --check mode to identify failures and determine which exceptions or safeguards are needed. Done means all task lists complete in --check mode and report valid results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, elasticsearch
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100