🔎

Module Overview

This page is a placeholder

Modules are the 'behavior' in Playbook Task statements that cause meaningful action to happen on managed systems- they do things or make some property of a system match a particular state.
Tasks appear like so in a Playbook:
​
tasks:
​
   - !shell
     name: optional comment about running /usr/bin/foo
     cmd: /usr/bin/foo --flag1 --flag2
     
This diagram was used earlier in the documentation, but we'll repeat it here:
​
​
​
Core modules are code that is part of our Rust binary and do not require any software to be installed or transferred to remote systems. We will follow a many-batteries-included philosophy with some minor curation caveats that are detailed on each module page.
​
​
​
​External module support (pending) involves executing modules written in any language that can read or emit JSON, which can also be used to call modules from other management tooling, regardless of programming language implementation choices.
​

Last modified 4d ago