[Question]: Scope of the project

[Oddly]

Ask a question

Hi guys,

Thanks for this collection, it really helps to have a Elasticsearch Ansible collection that does the heavy lifting for those of us still living on VM's.

I was looking into contributing to this collection, but before I put any more time into it, it'd seem prudent to ask some clarification first.

• Are you open to AI-assisted PR's? I'm not talking about mindless slop, but actual verified and tested changes that were vetted by a human.
• What's in scope of this collection and what isn't? I'm aware this is an open question, but you maintain this collection so it's good to know what's out of scope and what isn't before I add features for my own (and others) use.

Things I'd like to add:

• Pre-commit checks (linting)
• Upgrade to Elasticsearch 9
• API key module and user management implementations
• Broader testing (Ansible and Python versions)

Hope to hear from you soon,

Sam

[ivareri]

I have a few changes I'd like to implement myself, from the top of my head

• Split CA code into a separate role
• make elasticsearch python install optional
• mTLS support for interactions with a cluster
• ability to run all API calls to cluster from Ansible controller
• rolling upgrade + config change leads to 2 cluster restarts
• Rip out ES7 logic to make the code cleaner

If I ever get the time allocated to see to these is anyone's guess. Though with AI assist most of these would be trivial to fix...

For my part I would like some form of commitment for timely PR review. As it is now, the drift between the code I use and the project is large enough that it takes to much effort to create a well tested PR. (No hard feelings or grudges for not prioritizing reviews of PRs from 3rd parties)

[ivareri]

Ohh, and, I don't think I made any changes for using ES9. Just updated config with correct major version and did an rolling upgrade.

[Oddly]

Actually, that was my concern as well, NETWAYS are kind enough to share the role they use internally, but they have no obligation or reason to support more features than they themselves use. I've forked the role and am working on adding and generalizing. No promises though.