Use podman modules instead of the podman cli?

[gardar]

Wondering if PR's that replace the shell/command tasks with podman modules would be welcome, or is there any specific reason why this driver is using the podman cli via command/shell?

[gardar]

Quoting to reply to the question from ansible-community/molecule-podman#142
@ssbarnea ansible-community/molecule-podman#142 (comment)

I can answer this one. Podman collection was not really actively maintained and that gave more flexibility. Things change, I am not against using it, but be sure it is maintained.

Leaving this issue open since I feel like this improvement should be on the todo list.

[ssbarnea]

I am also considering the possibility of making molecule provisioning plugins be just ansible collections but I am not yet sure that would work. If it works, it would mean that you would not have to install python modules but instead just add some collections. Collections such podman or vagrant could include the "glue" code or metadata to expose themselves as also being molecule plugins.

[gardar]

Having the plugins/drivers as ansible collections sounds like an excellent idea, as it would make it feel more closely integrated in ansible.
With that it would also perhaps make sense to get molecule to install the ansible collection for the required driver automatically.