Solvedmolecule Make Ansible default verifier
✔️Accepted Answer
I see some value in having a tool that is NOT Ansible to verify something that was modified by Ansible.
Also writing good assertions in Ansible is surprisingly hard and brittle.
Lastly the Ansible verifier is very new, I'm not so sure if there are not still some kinks in there (e.g. imho it should fail the test if any job in the verification reports changed
).
None of these reasons are good enough to warrant a veto, I'd just be more comfortable with that change for e.g. Molecule around version 1.23, not directly the next release.
Other Answers:
This isn't about replacing or removing testinfra. It's a great tool. This is about changing the default to Ansible for verification as has been well explained in #2013 (comment).
Something that came to mind that should be extended in this proposal: the "documentation (optional)" part - we should provide some examples and usage examples. Ansible is not a "pure" verification tool but it can do it. We should show some best practices on what modules to use for typical use cases: "is the web server up".
Proposal: Make Ansible default verifier
Author: Sviatoslav Sydorenko <@webknjaz> IRC: webknjaz
Date: 2019-04-26
Motivation
The UX is inconsistent with the Ansible Engine and Galaxy which promise the ability to keep using YAML. "native" way of doing testing should come first which will improve the experience for new users.
Problems
What problems exist that this proposal will solve?
Solution proposal
Dependencies (optional)
Testing (optional)
N/A
Documentation (optional)
Just a
:versionchanged:
pointer.Anything else?
At Ansible Core and Galaxy we try to ensure the consistent user experience so we all agreed that defaults should be "native" to be "closer" to the user expectations and simplicity promises.
This will also facilitate the further introduction of Ansible Collections creation, testing and publishing workflows.