NETWAYS / NETWAYS/ansible-collection-elasticstack
Metricbeat configuration task is missing the configuration tags
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
The "Configure Metricbeat" task in roles/beats/tasks/metricbeat.yml has no tags, unlike the Filebeat and Auditbeat configuration tasks which carry configuration, beats_configuration and their per-beat tag.
As a result, running the role with --tags configuration (or beats_configuration) re-writes the Filebeat and Auditbeat configuration but silently skips Metricbeat.
Fix: add the tags (configuration, beats_configuration, beats_metricbeat_configuration) to the Metricbeat configuration task for consistency with the other two Beats.
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
Open roles/beats/tasks/metricbeat.yml and compare the "Configure Metricbeat" task with the Filebeat and Auditbeat configuration tasks. Add the three tags named in the issue, then verify that running the role with configuration or beats_configuration selects the Metricbeat task as well.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 94/100