toolbox/playbooks
Debarshi Ray b57dfd8b58 playbooks: Use Ansible's 'command' module, instead of 'shell'
Ansible's 'shell' module is almost exactly like the 'command' module,
except that it runs the command through a command line shell so that
environment variables like HOSTNAME and operations like '*', '<' and '>'
work.  None of those things are necessary are here.  Hence, it's better
to use the 'command' module as elsewhere.

Note that, unlike Ansible's 'shell' module, the 'command' module doesn't
support inline scripts.  So, each command needs to be in its own
separate task.

https://github.com/containers/toolbox/pull/1318
2023-06-22 18:20:49 +02:00
..
build.yaml .zuul, playbooks: Add copyright and license notices 2022-11-28 22:47:15 +01:00
dependencies-centos-9-stream.yaml playbooks: Use Ansible's 'command' module, instead of 'shell' 2023-06-22 18:20:49 +02:00
dependencies-fedora-restricted.yaml playbooks: Use Ansible's 'command' module, instead of 'shell' 2023-06-22 18:20:49 +02:00
dependencies-fedora.yaml playbooks: Use Ansible's 'command' module, instead of 'shell' 2023-06-22 18:20:49 +02:00
setup-env-migration-path-for-coreos-toolbox.yaml Test -Dmigration_path_for_coreos_toolbox on CentOS Stream 9 2022-12-14 23:09:55 +01:00
setup-env-restricted.yaml Test that toolbox(1) can be built without podman(1) and subordinate IDs 2023-03-02 10:25:54 +01:00
setup-env.yaml playbooks: Rename the file with the dependencies 2022-12-14 23:09:55 +01:00
system-test.yaml .zuul, playbooks: Add copyright and license notices 2022-11-28 22:47:15 +01:00
unit-test.yaml playbooks: Reveal the standard error & output streams from 'meson test' 2022-12-14 23:09:55 +01:00