NETWAYS / NETWAYS/ansible-collection-elasticstack

[Feature]: Introduce elasticstack_authentication + elasticstack_tls masters with an insecure-auth guard

Open
#527 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component:elasticstack
Dominant language
Jinja
Stars
14
Forks
11
Avg merge
1d 47m
Merged PRs (30d)
6

Description

Foundation for splitting the per-role *_security flags (umbrella #526).

  • Add two shared masters: elasticstack_authentication (default true) and elasticstack_tls (default true). Each role's future *_authentication / *_tls takes its default from the matching master via a plain variable default (not set_fact), so a user can override it per role without the master stomping the value.
  • Add elasticstack_allow_insecure_auth (default false).
  • Add a preflight assert (in the shared elasticstack role): fail when authentication is on and TLS is off, unless elasticstack_allow_insecure_auth is true — otherwise credentials would be sent over the wire in cleartext.

This is only the groundwork (masters + guard); the actual removal of the beats_security / logstash_security / kibana_security flags happens in the child PRs.

Breaking → 2.0.0. Part of #526.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the shared elasticstack role and the existing per-role *_security defaults. Trace how shared variables and role defaults are currently defined, then identify the role's preflight entry point for the authentication/TLS assertion. Done means the two masters, the insecure-auth override, and the guard work without overriding per-role values; the issue names no tests to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible
Domain
devops, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.