Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Make Ansible default verifier

See original GitHub issue

Proposal: Make Ansible default verifier

Author: Sviatoslav Sydorenko <@webknjaz> IRC: webknjaz

Date: 2019-04-26

Status: New
Proposal type: core design, consistent UX
Estimated time to implement: 1h

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?

Inconsistent UX across Ansible-related projects

Solution proposal

set Ansible to be a default verifier while keeping other options available.

Dependencies (optional)

Now that #1714 is merged, this is finally possible!

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.

Issue Analytics

State:
Created 4 years ago
Reactions:18
Comments:26 (20 by maintainers)

Top GitHub Comments

12reactions

MarkusTeufelbergercommented, Apr 26, 2019

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.

3reactions

decentral1secommented, Apr 30, 2019

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 https://github.com/ansible/molecule/issues/2013#issuecomment-487422948.

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”.

Top Results From Across the Web

Make Ansible default verifier · Issue #2013 - GitHub

At Ansible Core and Galaxy we try to ensure the consistent user experience so we all agreed that defaults should be "native" to...

Using Ansible to verify configurations | Enable Sysadmin

Ansible can do many things. This article demonstrates how to use Ansible to verify your configurations.

Ansible Configuration Settings

The ansible-config utility allows users to see all the configuration settings available, their defaults, how to set them and where their current value...

Ansible Testing Using Molecule with Ansible as Verifier

The default verifier is Ansible but there are also other verifiers, such as: testinfra, goss and inspec.

Configuration — Molecule Documentation

Name of the verifier tool (usually 'ansible') ... The developer's create playbook must provide the following instance-config data, and the developer's ...