NETWAYS / NETWAYS/ansible-collection-elasticstack
[Feature]: Rename elasticstack_full_stack to reflect its residual meaning (inventory wiring)
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
After the other meanings are peeled off (see #531), elasticstack_full_stack has one remaining job: inventory-based host wiring — the roles resolving Elasticsearch and each other from inventory groups (vs a standalone single role pointing at user-provided targets). The name no longer reflects that, so rename it — without a backward-compat alias (clean break, 2.0.0).
Proposed name (TBD — pick one):
elasticstack_integrated— components are wired together, vs standalone. Short.elasticstack_collection_managed_stack— "the collection manages the whole stack". Intuitive but broad.elasticstack_wire_from_inventory— most literal (resolve peers from inventory groups). A bit technical.elasticstack_inventory_managed— topology managed via inventory groups.
Do this last, after (A)/(C)/(D) are removed. 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 reviewing issue #531 and the collection's roles and references for elasticstack_full_stack, focusing on inventory-based host wiring. Choose a final replacement name, update all affected references without adding a backward-compatible alias, and verify that the clean break is documented for the 2.0.0 release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, elasticsearch
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100