nifr / ansible-collections Goto Github PK

In order to test ansible collections against multiple combinations of python and ansible versions the use of pipx's --suffix parameter is very tempting.

The resulting binary shims can be named similar to homebrew's co-installable versioned packages (i.e. helm and helm@2).

Similar to tox in a CI environment their usage opens up the possibility to test different version combinations quickly in a local environment.

Altering the behaviour of binaries depending on their name is definitely an anti-pattern. I've personally experienced this with old versions of hashicorp's packer in a Debian environment before.

... to be investigated.

Example

pipx install
  --suffix '@2.10-python3.7' \
  --python python3.7 \
  --include-deps \
  --force \
  'ansible >= 2.10.0, == 2.10.*, < 2.11'

[email protected] --version

Output:

ERROR! Unknown Ansible alias: [email protected]

Example

git clone [email protected]:nifr/ansible-collections.git ansible_collections
cd ansible_collections/nifr/inventory_scripts/
ansible-test --sanity -v

Output:

ERROR: The current working directory must be at or below:

  an Ansible collection: {...}/ansible_collections/{namespace}/{collection}/

Current working directory: /[..]/ansible-collections/nifr/inventory_scripts

Example

git clone [email protected]:nifr/ansible-collections.git 
cd ansible-collections/nifr/inventory_scripts/
ansible-test --sanity --docker default -v

Output:

WARNING: Skipping sanity test 'yamllint' due to missing libyaml support in PyYAML.