diff options
author | Erik Skultety <eskultet@redhat.com> | 2023-03-13 13:54:19 +0100 |
---|---|---|
committer | Erik Skultety <eskultet@redhat.com> | 2023-03-13 14:38:14 +0000 |
commit | c0a30d7b1b7d9fd2d1d13680032ca94f9dc35222 (patch) | |
tree | b2a58d467f96c77527dcd70044d0cab85d8c760b /setup.py | |
parent | c3f2bc9d8a1374367f60ac6d7cf4c3db72d66663 (diff) | |
download | libvirt-ci-c0a30d7b1b7d9fd2d1d13680032ca94f9dc35222.zip libvirt-ci-c0a30d7b1b7d9fd2d1d13680032ca94f9dc35222.tar.gz libvirt-ci-c0a30d7b1b7d9fd2d1d13680032ca94f9dc35222.tar.bz2 |
ansible_wrapper: Move onto ansible-runner 2.1.1 or newer
Ansible introduced some API changes in ansible-runner 2.0, luckily none
of them backwards incompatible. However, Ansible is planning on
deprecating Python 3.7 starting with version 2.12. Here's the weird
problem for us - the deprecation warning Ansible produces here is a
multiline string which is delivered in multiple Ansible events, so our
ugly WARNING filter can't work properly. By moving onto ansible-runner
2.1.1 and newer, we're able to get rid of that ugly piece of code
because ansible-runner now provides attributes for both stdout and
stderr streams.
As for API changes, the biggest change is the introduction of the
interface module providing a new 'run' method. The old Runner.run
method is essentially just a wrapper over the new API. Yet we need to
keep using the Runner object (which is fine) directly, otherwise we'd
lose some logging details about the actual command Ansible ran, because
the new APIs simply don't provide that information.
Signed-off-by: Erik Skultety <eskultet@redhat.com>
Diffstat (limited to 'setup.py')
0 files changed, 0 insertions, 0 deletions