NETWAYS / NETWAYS/ansible-collection-elasticstack
Optionally use data streams
Open
Nobody has claimed this yet.
component:elasticsearch
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
Newer versions of Elasticsearch will use data streams for Index handling.
We should make sure we are prepared to use them.
see
Configuration is data stream compliant but due backwards compatibility Logstash 7.x will not assume writing to a data-stream, default behavior will change on Logstash 8.0 (set `data_stream => true/false` to disable this warning)
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
The issue does not name files, tests, or an entry point. Start by locating the collection's Logstash and Elasticsearch configuration, then review the cited Logstash 7.x data-stream compatibility warning. Done means the collection is prepared for optional Elasticsearch data streams while preserving the stated backwards-compatibility behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, elasticsearch
- Domain
- devops, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100