Documentation about management of paths for Elasticsearch is confusing

[widhalmt]

Getting the collection to manage directories for Elastic Search is implemented in a failsafe but cumbersome way but lacks configuration. Sorry, @xtruthx that you had to find out the hard way that it's not as well documented and easy as one would wish.

Historically we just started with a few variables for paths. If they were set, the role made sure the according directory is created and has the correct permissions. Now we have a loop that iterates over several variables and does this job. The catch is that for every path we have a second variable that controls whether the task is run on the specific directory or not. This variable usually defaults to false so not to interfere with system configuration.

It's counterintuitive to have means for managing paths but skipping them alltogether. And it's a bit cumbersome to have two variables per path.

So what we need is at least some documentation on how to have paths managed. Maybe we should use the chance and overhaul the process alltogether. Maybe we should switch to a single variable of type dictionary to handle all paths?

[xtruthx]

Thank you. I will inheriit the revise of the documentation and additional improvements.