Skip to content
Source on GitHubVisitors

Ansible project structure

See how the playbooks, roles and inventories of an Ansible project include and depend on each other.

Diagram · origin tag ansible/structure · Infrastructure, network & cloud diagrams

Availability

Availability per host
HostStateHow to get it
StandalonePrototypeNot yet released
DesktopPrototypeNot yet released
IntelliJ PlatformNot plannedNot planned
Visual Studio CodeNot plannedNot planned
EclipseNot plannedNot planned
ThinkRailNot plannedNot planned
NotionNot plannedNot planned
ClaudeNot plannedNot planned

What it is for

Ansible project structure (playbooks, roles, inventories and their include/import/dependency relationships; Ansible's own files are never written, and node positions a user arranges are authored into the `.adp`)

Why a specialized view helps

An Ansible project spreads its structure over many folders and includes; a graph shows the dependencies without touching Ansible's own files.

File formats

Not described yet.

Screenshots

The playbooks, roles and inventories of the folder, with import, role and dependency edges labelled; the Toolbox saying the type offers no elements, since it is read from the folder. Nothing selected.

Standalone, at 3e2df46

What is visible: The playbooks, roles and inventories of the folder, with import, role and dependency edges labelled; the Toolbox saying the type offers no elements, since it is read from the folder. Nothing selected.

Why it matters: The folder's playbooks, roles and inventories appear as one graph with every import and dependency labelled, so how the project hangs together is visible without opening its YAML files, and Ansible's own files are left untouched.

Licence: Apache-2.0

Background

Focus areas

Sources