You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

History

Alex Willmer 85b1b4070a tests: Respect configured or detected Python more often Relying on the virtualenv default or hardcoding "python" results in a Python 2.x virtualenv on some targets (e.g. debian10-test). This caused a failure when testing with Ansible >= 10 (ansible-core >= 2.17), which have dropped Python 2.x support. refs #1074		4 months ago
..
README.md	issue #409 : add new stub_connections/ test type.	6 years ago
_end_play_if_not_sudo_linux.yml	ansible_mitogen: Handle AnsibleUnsafeText et al in Ansible >= 7	8 months ago
all.yml	Revert "Revert "fixed tests for ansible 2.12""	3 years ago
kubectl.yml	tests: Respect configured or detected Python more often	4 months ago
lxc.yml	tests: Respect configured or detected Python more often	4 months ago
lxd.yml	tests: Respect configured or detected Python more often	4 months ago
mitogen_doas.yml	tests: Respect configured or detected Python more often	4 months ago
mitogen_sudo.yml	tests: Respect configured or detected Python more often	4 months ago
setns_lxc.yml	tests: Use same verbosity when re-executing Ansible inside a playbook	6 months ago
setns_lxd.yml	tests: Use same verbosity when re-executing Ansible inside a playbook	6 months ago

README.md

`stub_connections/`

The playbooks in this directory use stub implementations of various third party tools (kubectl etc.) to verify arguments passed by Ansible to Mitogen and subsequently onward to the tool result in something that looks sane.

These are bare minimum tests just to ensure sporadically tested connection methods haven't broken in embarrasingly obvious ways.