Ansible Dev Tools v26.4.0: Complete Development Toolkit Guide

Introduction

ansible-dev-tools (ADT) is the official meta-package that bundles all the tools you need to create, test, and maintain Ansible content. Instead of installing each tool separately, one pip install gives you the complete development toolkit.

Version 26.4.0 brings the latest versions of all included tools with bug fixes and improvements.

See also: Top Tools for Writing and Testing Ansible Content Efficiently

Install

pip install ansible-dev-tools

This installs all of the following tools:

Included Tools

| Tool | Purpose | |------|---------| | ansible-core | Core Ansible engine | | ansible-builder | Build Execution Environments (container images) | | ansible-creator | Scaffold collections, roles, and projects | | ansible-lint | Identify anti-patterns and style issues | | ansible-navigator | TUI for running and debugging playbooks | | ansible-sign | Sign and verify Ansible content | | molecule | Test roles in containers/VMs | | pytest-ansible | Pytest plugin for Ansible testing | | tox-ansible | Tox plugin for Ansible testing |

See also: Ansible Builder & Execution Environments: Complete Guide (2026)

Quick Start

# Install everything
pip install ansible-dev-tools
# Verify all tools
ansible --version
ansible-lint --version
ansible-navigator --version
ansible-creator --version
molecule --version
ansible-builder --version

Workflow: Create → Develop → Test → Publish

1. Scaffold a Collection

ansible-creator init collection myorg.mytools
cd myorg/mytools

2. Develop Modules and Roles

# Add a role
ansible-creator add role webserver
# Add a module
ansible-creator add plugin module my_module
# Edit roles/webserver/tasks/main.yml

3. Lint Your Code

ansible-lint
# Checks for:
# - FQCN usage
# - YAML best practices
# - Deprecated syntax
# - Security issues (no_log missing)

4. Test with Molecule

cd roles/webserver
molecule init scenario
molecule test

5. Run with Navigator

# Interactive TUI mode
ansible-navigator run playbook.yml
# Stdout mode (CI-friendly)
ansible-navigator run playbook.yml -m stdout

6. Build Execution Environment

# execution-environment.yml
version: 3
dependencies:
  galaxy: requirements.yml
  python: requirements.txt
  system: bindep.txt

ansible-builder build -t myorg/my-ee:latest

7. Publish

ansible-galaxy collection build
ansible-galaxy collection publish myorg-mytools-1.0.0.tar.gz

See also: Ansible Development Workspaces: Enterprise-Ready Dev Environments on OpenShift Dev Spaces

Tool Deep Dives

ansible-lint

# Run on entire project
ansible-lint
# Fix auto-fixable issues
ansible-lint --fix
# Check specific file
ansible-lint playbook.yml
# Configuration: .ansible-lint

ansible-navigator

# Interactive mode (default)
ansible-navigator run site.yml
# Browse documentation
ansible-navigator doc ansible.builtin.copy
# Explore inventory
ansible-navigator inventory -i inventory.yml
# View execution environment contents
ansible-navigator images

molecule

# Test lifecycle
molecule test      # Full: create → converge → verify → destroy
molecule converge  # Just apply role
molecule verify    # Just run tests
molecule login     # Shell into test container

ansible-builder

# Build custom EE
ansible-builder build \
  --tag myorg/custom-ee:latest \
  --container-runtime docker
# Inspect EE
ansible-navigator images

ansible-creator

# Scaffold projects
ansible-creator init collection myorg.tools
ansible-creator init playbook my_project
ansible-creator add role webserver --path .

IDE Integration

VS Code

The Ansible VS Code Extension integrates with ansible-dev-tools: • Real-time ansible-lint feedback • Module documentation on hover • ansible-creator scaffolding from Command Palette • Execution Environment support

Configuration

# .ansible-lint
profile: production
skip_list:
  - yaml[line-length]
# .ansible-navigator.yml
ansible-navigator:
  mode: stdout
  execution-environment:
    enabled: true
    image: myorg/custom-ee:latest
# molecule/default/molecule.yml
driver:
  name: docker
platforms:
  - name: ubuntu
    image: ubuntu:24.04

Why Use ansible-dev-tools?

• One install — no dependency conflicts between tools • Consistent versions — tools tested together • Complete workflow — create, lint, test, build, publish • Official — maintained by the Ansible team • Always current — regular releases with latest tool versions

FAQ

Can I install tools individually instead?

Yes — each tool is available as a separate pip package. ADT just bundles them for convenience and ensures compatible versions.

Does ADT include ansible (community package)?

It includes ansible-core, not the full ansible package. Install community collections separately via ansible-galaxy.

What Python version is required?

Python 3.10 or newer. Check with python3 --version.

How do I update?

pip install --upgrade ansible-dev-tools

Related Articles