NETWAYS / NETWAYS/ansible-collection-elasticstack
Determine minimum Ansible version
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
We need to keep track in meta of the minimum Ansible version needed.
I'm also tempted to run tests for different versions. We had a lot of issues in the past that were traced back to incompatible versions. Ansible is moving fast and we need to keep track. How about introducing checks per version? Not for every change but when merging into main?
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 locating the collection metadata under meta and reviewing the repository's existing test or CI entry points. Done means the minimum supported Ansible version is recorded and the approach for checking compatibility across versions is defined, including whether checks run when merging into main.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100