NETWAYS / NETWAYS/ansible-collection-elasticstack
Solve version dependent configuration changes
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
In this collection, elastic_release is an integer, not a version. We have a version variable, that's not always used and can be filled with latest.
So checks like https://github.com/NETWAYS/ansible-collection-elasticstack/pull/243/commits/a5c88d449ffb17a59d0c5afea2d85890805d8b3c are very helpful bon't won't work with the current implementation.
There could be a combined solution for this issue and #236 . So set a variable that contains the actual or desired version and then use it for checks like the one in jvm.options. For now I have to deactivate the checks because they create illegal code for version 7.
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 how elastic_release and the optional version variable are defined and consumed, especially the checks around jvm.options. Review the referenced pull request commit and issue #236 before deciding how the actual or desired version should be selected. Done means version-dependent checks generate valid configuration for version 7 while still supporting explicit versions and latest.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, elasticsearch
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100