Compatible with ansible-core 2.19, name by name.

Volant loads the whole ansible-core 2.19 grammar and reproduces its behaviour, so any difference is a bug. The test suite lists every keyword, option and plugin ansible-core ships and checks what this release does with each.

99.1%of ansible-core runs: 551 of 556 names, 0 more in part
97.9%of the collections’ modules and plugins: 11,663 of 11,906. Most of the 243 others come with Windows and network device support.

Checking one project? Will my playbook run? shows the three commands, and the known gaps list what fails without a message.

runspartial: an argument or a value is missinglater: Windows, other connections, other output callbacksThe numbers are read from the support matrix the test suite generates.

The playbook language

keyword (play)41/41
keyword (block)31/31
keyword (task)66/66
keyword (loop_control)7/7
meta action10/10
YAML tag2/2

Modules and templating

module71/71
action plugin28/28
filter122/122
test82/82
lookup25/25

Hosts, runs and the command line

ansible-playbook option38/38
inventory9/9
connection4/62 later
become2/31 later
strategy4/4
shell1/32 later
vars1/1
cache2/2
callback5/5

Collections in the ansible package

module9,266/9,443177 later
action plugin2,073/2,08411 later
inventory50/50
lookup95/95
connection11/3019 later
callback3/3936 later
filter136/136
test29/29

Check your own project.

Three commands, and the first two never touch a host.

  1. Read it without running it

    volant playbook -i inventory.ini site.yml --syntax-check

    Listings and --syntax-check never stop on something unsupported, so they work on any playbook.

  2. Compare the task list

    volant playbook -i inventory.ini site.yml --list-tasks

    If it matches what ansible-playbook --list-tasks prints, Volant compiled your roles, imports and tags the same way.

  3. Run it on one host

    volant playbook -i inventory.ini site.yml --limit test1

    Most of what this release cannot run stops the run before it connects, names what it refused, and exits with code 4.

A few gaps are silent: a run can ignore a setting there without an error. Read the known gaps before a run that matters.