NETWAYS / NETWAYS/ansible-collection-elasticstack
Better password handling
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
While we might need the file with the initial passwords during setup, we need to provide a way of using your own password with variables. This leads to options like Ansible vault, Hashicorp vault and more.
I guess we will need #132 to be fixed before we can start with this.
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 reading issue #132, then trace how the initial password file and setup variables are handled in this Ansible collection. Compare the requested variable-based password flow with the mentioned Ansible Vault and HashiCorp Vault options. Done means users can supply their own password securely without depending on the initial password file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, elasticsearch
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100