NETWAYS / NETWAYS/ansible-collection-elasticstack
[Feature]: Make the Logstash monitoring API (host/port + TLS) configurable
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
Describe the feature request
The role only exposes logstash_http_host/logstash_http_port (both unset by
default) and cannot secure the Logstash HTTP API. Add variables to configure the
API's bind host/port and TLS (api.ssl.enabled + api.ssl.keystore.path/
password). This allows a secured and/or remotely reachable API — a prerequisite
for remote monitoring and health checks.
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
Search the role for logstash_http_host and logstash_http_port, then trace where those variables configure the Logstash HTTP API. Add configurable bind host and port plus the specified api.ssl settings, and verify that secured and remotely reachable API configurations render correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100