Of course! I keep forgetting that the "programmy" stuff should go in Python
:)
When you talk about a 'fact' module, though, what do you mean? Writing a
module that takes in a bunch of data formatted in some way and then
exit_json( [changed=False,] yourStuff=yourStuff ), where "yourStuff" is a
d
Might it be easier to write a simple fact module that returns what cores
you have, rather than doing the register?
This way you could return a hash table indexed by core name, as well as a
list of cores, which might make the playbooks more intuitive and less
relying on some rather "programmy" conc
I'm writing a playbook to create a number of solr cores, but I'm running
into some issues.
I started with a task file that would be included, but appearantly include
and with_items isn't supported.
The idea was, that for every core I would check that the base folder of the
core existed. This r
