Confusing ansible-test cli help

[rndmh3ro]

Summary

The ansible-test help option is very confusing.

I had a simpke use case: run my integration tests in a docker container with python 3.9.
Trying to find out how to do this (with no prior knowledge) from ansible-test integration --help is very hard.

There are controller options, controller origin options, target options, target controller options...
Then there are global env options, environment env options and composite env options.

I think some examples or a how-to (a la "I want to do X") would help.

Issue Type

Documentation Report

Component Name

ansible-test

Ansible Version

> ansible --version

ansible [core 2.12.1]
  config file = None
  configured module search path = ['/root/dev/openshift-ansible/roles/lib_openshift/library', '/root/dev/openshift-ansible/roles/openshift_facts/library', '/root/dev/openshift-ansible/roles/lib_utils/library']
  ansible python module location = /home/basti/.local/lib/python3.8/site-packages/ansible
  ansible collection location = /home/basti/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/basti/.local/bin/ansible
  python version = 3.8.10 (default, Nov 26 2021, 20:14:08) [GCC 9.3.0]
  jinja version = 3.0.3
  libyaml = True

Configuration

$ ansible-config dump --only-changed

OS / Environment

Ubuntu

Additional Information

Code of Conduct

• I agree to follow the Ansible Code of Conduct

[ansibot]

Files identified in the description:

• bin/ansible-test

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

[acozine]

Related to #76655.

[acozine]

@rndmh3ro would you be willing to share the command you ended up using? We could add that to #76655, or open a similar PR that covers ansible-test.

[rndmh3ro]

It was something like ansible-test integration --docker <image or defined name> --python 3.9 - but I'm not sure anymore.

[ansibot]

Thank you very much for your submission to Ansible. It means a lot to us that you've taken time to contribute.

Unfortunately, this issue has been open for some time while waiting for a contributor to take it up but there does not seem to have been anyone that did so. So we are going to close this issue to clear up the queues and make it easier for contributors to browse possible implementation targets.

However, we're absolutely always up for discussion. Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time. If you or anyone else has any further questions, please let us know by using any of the communication methods listed in the page below:

• https://docs.ansible.com/ansible/latest/community/communication.html

In the future, sometimes starting a discussion on the development list prior to proposing or implementing a feature can make getting things included a little easier, but it's not always necessary.

Thank you once again for this and your interest in Ansible!

click here for bot help