Skip to content

ansible-dev-environment: Reference

This page provides exhaustive reference material for ansible-dev-environment. For an introduction and typical usage, see the ansible-dev-environment guide.

These options apply to all ade subcommands:

Flag Short Description Default
--ansi Enable colored output true
--no-ansi Disable colored output —
--lf <path> Log file path —
--ll <level> Log level: notset, debug, info, warning, error, critical notset
--la <true|false> Append to log file true
--uv Use uv package manager if available true
--no-uv Disable uv usage —
--verbose -v Verbose output —
--version -V Show version and exit —
--help -h Show help and exit —

Install a collection and its dependencies into a virtual environment.

ade install [options] [collection_specifier]
Flag Short Description Default
--venv <path> Target virtual environment directory .venv
--editable -e Install in editable mode (symlink) —
--requirement <file> -r Install from requirements file —
--python <version> -p Python interpreter (version number, name, or full path) System default
--seed Install ansible-dev-tools into venv true
--no-seed Skip ansible-dev-tools installation —
--isolation-mode <mode> --im Isolation mode: cfg, restrictive, none cfg
--acv <constraint> Ansible core version constraint (pip format) —
--uv Use uv for package operations true
--no-uv Disable uv —
--cpi Collection path isolation —
--ssp Enable system site packages —
Terminal window
# Current directory
ade install -e .
# Current directory with test extras
ade install -e .[test]
# Specific collection by FQCN
ade install namespace.name
# From requirements file
ade install -r requirements.yml
Mode Behavior
cfg Creates/updates ansible.cfg with collections_path = . in the current directory
restrictive Exits with error if collections exist in ~/.ansible/collections or /usr/share/ansible/collections
none No collection path isolation

When installing a collection, ade install processes these files if present:

File Purpose When processed
requirements.txt Python runtime dependencies Always
test-requirements.txt Python test/dev dependencies With [test] extra
requirements.yml Collection dependencies Always (via ansible-galaxy)
galaxy.yml Collection metadata and version Always

Remove a collection from the virtual environment.

ade uninstall <namespace.name> [options]
Flag Description Default
--venv <path> Target virtual environment .venv

List installed collections.

ade list [options]
Flag Description Default
--venv <path> Target virtual environment .venv

Inspect installed collections with detailed metadata.

ade inspect [options]
Flag Description Default
--venv <path> Target virtual environment .venv

Check installed collections for issues (missing dependencies, version conflicts).

ade check [options]
Flag Description Default
--venv <path> Target virtual environment .venv

Display the dependency tree for installed collections.

ade tree [options]
Flag Description Default
--venv <path> Target virtual environment .venv
Variable Description
SKIP_UV Set to 1 to disable uv acceleration

When ade install -e . is used:

  1. ADE reads galaxy.yml to determine the collection namespace and name
  2. Creates the virtual environment (with uv if available)
  3. Installs ansible-dev-tools (unless --no-seed)
  4. Runs ansible-galaxy collection build to generate the collection tarball
  5. Runs ansible-galaxy collection install for collection dependencies from requirements.yml
  6. Creates a symlink from <venv>/lib/python<ver>/site-packages/ansible_collections/<namespace>/<name> to the source directory
  7. Installs Python dependencies from requirements.txt
  8. Installs test dependencies from test-requirements.txt (if [test] extra specified)

The symlink means your source edits are immediately visible to:

  • ansible-playbook and ansible commands
  • pytest test runners
  • ansible-lint
  • molecule
  • Any tool using the venv’s Python