Timothy Appnel

Is this guidance specifically for writing modules and other plugins in python? If so, it is not clear to me in this. If it is about writing Ansible playbooks and...

**The Zen of Ansible** Ansible is not Python. YAML sucks for coding. Playbooks are not for programming. Ansible users are (most probably) not a programmers. Clear is better than cluttered....

Thanks for your input @anon-software. I get the desire for batch (all) operations, but this, as proposed, is too dangerous. If someone forgets to set the name they'd inadvertently wiping...

I really dislike this one because it's controversial and a matter of taste and style. It didn't make it into the Ansible CoP good practices for a reason. I dislike...

This is another controversial rule that got cut from the CoP good practices for good reason. I'm really opposed to forcing it on users by putting it in the production...

@ssbarnea I believe this has been completed now with the downstream release of Molecule 6.

That naming is OK with me. I'm not sold on the multi-stage Dockerfile approach though. That seems inconsistent with the direction the Ansible community is heading with its efforts like...

@imreACTmd Are you referring to the new line protocol api in v0.9?

@ssbarnea Is this still an issue after after the release of Molecule 6?

I like the idea of collections for Molecule here. I'd recommend we leave the naming open to many provisions. So `molecule.core` for main/default/supported provisioners and using the `molecule.*` convention for...