How It Works
How LaraDep runs playbooks, what it checks before execution and how saved presets work.
- The run is blocked and the system displays a concrete description of the problem — what is missing and where. You fix the problem and try again. If it is a warning rather than a blocking error (for example a missing optional integration), you have the option to confirm the run anyway and continue.
- On the playbook page click "Export runtime" — the system walks you through the same wizard as for execution, but the output is a downloadable ZIP file. It contains everything the system would use when running: server list, configuration, settings and credentials in encrypted form. The ZIP is automatically deleted after download.
- A preset is a saved configuration for a recurring task — you select a playbook, target server or server group and run parameters. Next time you just click the preset and run, without having to configure everything again. You create a preset directly while going through the run wizard — you check "Save as preset" and name it. The default preset can be run with one click directly from the playbook overview.