NETWAYS / NETWAYS/ansible-collection-elasticstack
Refactoring and review
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
As agreed with @widhalmt in person, we want to review the current state of the collection and refactor some parts of it.
There is no fixed list of issues, bugs, etc. that we want to refactor, but we will find those while reviewing.
We "accept" to implement breaking changes to improve the collection.
Already merged PRs: #394. All following PRs will be reference this issue.
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
Review the current collection and the already merged PR #394 first, then identify concrete refactoring candidates and bugs during that review. Done means the proposed breaking changes are agreed and implemented in follow-up PRs that reference issue #396.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100