NETWAYS / NETWAYS/ansible-collection-elasticstack
[Feature]: Per-beat extra_config passthrough for unmanaged settings
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
The Beats templates are opinionated, so any setting without a dedicated role variable (e.g. queue.*, max_procs, http, custom processors) can't be set.
Add a beats_filebeat_extra_config / beats_metricbeat_extra_config / beats_auditbeat_extra_config dict (default {}), appended to the generated config via to_nice_yaml. Only for top-level keys the role does not already manage (setting a managed key like output.* would duplicate it). Not argument_specs-validated — the escape hatch for the long tail. Non-breaking (empty default).
Complements #505/#510 (which only cover the inputs/modules sections), this targets the top-level keys the role doesn't manage.
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 with the Beats templates that generate the Filebeat, Metricbeat, and Auditbeat configurations, and identify how top-level managed settings are assembled. Add the three optional extra-config variables without duplicating managed keys, preserve the empty default behavior, and verify the rendered output uses to_nice_yaml.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100