uv tool integration

[MaKaNu]

Prerequisites

• This was not already reported in the past (duplicate check)
• It does reproduce it with code from main branch (latest unreleased version)
• I include a minimal example for reproducing the bug
• The bug is not trivial, as for those a direct pull-request is preferred
• Running pip check does not report any conflicts
• I was able to reproduce the issue on a different machine
• The issue is not specific to any driver other than 'default' one

Environment

$ uvx --from ansible-dev-tools adt --version
ansible-builder                          3.1.0
ansible-core                             2.19.0
ansible-creator                          25.7.0
ansible-dev-environment                  25.5.0
ansible-dev-tools                        25.5.2
ansible-lint                             25.6.1
ansible-navigator                        25.5.0
ansible-sign                             0.1.2
molecule                                 25.6.0
pytest-ansible                           25.6.3
tox-ansible                              25.5.5

What happened

Instead of using a venv or other method, I tried to utilize uv tool install ansible-dev-tools to work with adt.

The first thing I noticed was, that adt is installed via symlink into my ~/.local/bin/ directory. I do not understand uv tool enough, but I think this is the result of pyproject.toml#L34-L36

But this also results in not having the other binaries in path, instead only on ~/.local/share/uv/tools/ansible-dev-tools/bin which is not on path.

I think running the other binaries via additional tool like uvx --from ansible-core ansible --version, destroys some purpose of adt, I think.

I am not sure if it is possible to expose the other binaries the same way adt is exposed.

Reproducing example

$ uv tool install ansible-dev-tools

$ adt --version
ansible-builder                          3.1.0
ansible-core                             2.19.0
ansible-creator                          25.7.0
ansible-dev-environment                  25.5.0
ansible-dev-tools                        25.5.2
ansible-lint                             25.6.1
ansible-navigator                        25.5.0
ansible-sign                             0.1.2
molecule                                 25.6.0
pytest-ansible                           25.6.3
tox-ansible                              25.5.5

$ ansible --version
bash: ansible: command not found

$ which adt
/home/user/.local/bin/adt

$ ls -l $(which adt)
lrwxrwxrwx 1 user user 72 Jul 28 11:05 /home/user/.local/bin/adt -> /home/user/.local/share/uv/tools/ansible-dev-tools/bin/adt

ls /home/user/.local/share/uv/tools/ansible-dev-tools/bin/ | grep ansible
ansible
ansible-builder
ansible-config
ansible-console
ansible-creator
ansible-doc
ansible-galaxy
ansible-inventory
ansible-lint
ansible-navigator
ansible-playbook
ansible-pull
ansible-runner
ansible-sign
ansible-test
ansible-vault

[MaKaNu]

There is an issue with PR on uv github explaining what is happening: astral-sh/uv#6314

I leave it here to keep track of it.

[alisonlhart]

@MaKaNu Can you retry this with the latest uv release? It looks like there may have been a fix there.

[MaKaNu]

Yes, I tried already and the fix seem works like expected. There is now a different struggle:

while the fix works perfectly with ansible-core for example with ansible-dev-tools it is a bit annoying and ridiculous:

1. Using ansible-dev-tools to have one package to handle all the development tools for ansible with one toolbox
2. Needing to install with mentioning all the dependencies:

❯ uv tool install ansible-dev-tools --with-executables-from ansible-builder,ansible-core,ansible-creator,ansible-dev-environment,ansible-lint,ansible-navigator,ansible-sign,molecule
Resolved 74 packages in 13ms
Audited 74 packages in 0.02ms
Installed 1 executable from `ansible-builder`: ansible-builder
Installed 10 executables from `ansible-core`: ansible, ansible-config, ansible-console, ansible-doc, ansible-galaxy, ansible-inventory, ansible-playbook, ansible-pull, ansible-test, ansible-vault
Installed 1 executable from `ansible-creator`: ansible-creator
Installed 1 executable from `ansible-dev-environment`: ade
Installed 1 executable from `ansible-lint`: ansible-lint
Installed 1 executable from `ansible-navigator`: ansible-navigator
Installed 1 executable from `ansible-sign`: ansible-sign
Installed 1 executable from `molecule`: molecule
Installed 1 executable: adt

Well, it is just the first time and upgrading is easy as uv tool upgrade ansible-dev-tools so it is just a small inconvenience, but as a user I need to identify, as well, that pytest-ansible and tox-ansible don't ship with an executable.