NETWAYS / NETWAYS/ansible-collection-elasticstack
[Feature]: Introduce elasticstack_manage_ca (collection-managed CA vs bring-your-own)
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
One job hidden inside elasticstack_full_stack: whether the collection acts as its own Certificate Authority — generating the CA with elasticsearch-certutil and distributing ca.crt + node/component certificates across the roles.
Add elasticstack_manage_ca (default true) to control exactly this. When false, the collection generates/distributes nothing and the user brings their own CA/certificates via the existing *_tls_* variables (externally-managed or cloud stack). Decouples "collection owns the PKI" from "collection deploys the components".
Breaking → 2.0.0. Part of #531.
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 at the elasticstack_full_stack job and trace the existing tls variables and elasticsearch-certutil handling across the collection's roles. Implement the new default-true control so false skips CA and certificate generation or distribution while retaining user-provided certificates; done means both managed and bring-your-own paths behave as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100