NETWAYS / NETWAYS/ansible-collection-elasticstack
[Feature]: Introduce elasticstack_generate_passwords (collection-generated vs user-supplied credentials)
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
Another job hidden inside elasticstack_full_stack: whether the collection generates the built-in user passwords (elasticsearch-setup-passwords auto on the CA host) and fetches them for the other roles.
Add elasticstack_generate_passwords (default true). When false, the collection creates/fetches nothing and the user supplies each role's credentials via per-role variables (a standalone role against an external/cloud Elasticsearch the collection didn't bootstrap).
Note: password generation currently hangs on elasticsearch_security + the CA host, not on full_stack — this gives it its own explicit switch.
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 by tracing password generation in the elasticsearch_security role on the CA host, then compare how elasticstack_full_stack invokes that work. Done means elasticstack_generate_passwords defaults to true, while false skips credential creation and fetching and allows each role's credentials to be supplied externally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, elasticsearch
- Domain
- devops, infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100