Playbooks & Execution•4 min read•Productivity

Saved Runs & 1-Click Execution Templates

Turn recurring playbook runs with locked inventories, tags, runtime engines, and variables into reusable 1-click execution templates in CIEL.

Routine operations such as nightly database dumps, edge cache purges, container stack rollouts, or compliance audits should not require manually re-selecting inventories, toggling tags, and re-entering extra variables every time you run them.

CIEL provides Saved Runs (/saved-runs): pre-configured launch templates that freeze your playbook, target scope, execution engine, tags, and variable sets into one reusable profile. Anyone on your team can launch them with a single click, or bind them to cron schedules and external webhook triggers.

Configured Saved Runs Management Table with One-Click Launch Controls and Execution Metadata

1. Saved Runs Management (/saved-runs)

The Saved Runs dashboard organizes all execution templates across your workspace in a searchable table:

  • Template Identity: Operational name and ID (e.g. Saved Run #1: Deploy Production Web & API).
  • Playbook Mapping: The underlying Ansible playbook tied to the template (e.g. Nginx Reverse Proxy & SSL).
  • Target Scope: Locked inventory group or direct host selection (e.g. Production Infrastructure).
  • Configuration Badges:
    • Execution Engine: Indicates runtime isolation mode, such as PODMAN container runner or NATIVE host execution.
    • Variables Badge: Shows the count of attached runtime variables (e.g. 2 vars, 1 vars, 0 vars).
  • Actions:
    • Run: Dispatches the execution immediately using the locked parameters and redirects straight to the live log console.
    • Menu (...): Edit template options, duplicate configuration, or delete the template.

2. Two Ways to Create a Saved Run

You can create a Saved Run template from scratch or capture a successful run directly from history:

Method A: From the Saved Runs Page (+ Create Saved Run)

  1. Navigate to RUNS & JOBS > Saved Runs in the sidebar.
  2. Click + Create Saved Run in the top header.
  3. Configure the launch parameters in the drawer:
    • Template Name: A descriptive operational label (e.g. Nightly Database Backup).
    • Target Playbook: Select the playbook recipe.
    • Target Scope: Select an Inventory (with optional host inclusion/exclusion filters) or choose Direct Hosts.
    • Execution Engine: Choose between Podman Container and Native Mode.
    • Ansible Tags (Optional): Specify comma-separated --tags or --skip-tags.
    • Variable Sets & Extra Variables (Optional): Attach variable sets in precedence order and define runtime extra variables.
  4. Click Save.

Method B: From Completed Jobs (Save as Run)

  1. Open any completed job in RUNS & JOBS > Jobs (/jobs/[id]).
  2. In the header actions, click Save as Run.
  3. CIEL automatically pre-populates the drawer with the exact playbook, target scope, tags, and variable inputs used during that execution.
  4. Name the template and save it for future one-click launches.

3. Real-World Saved Run Presets

The screenshot above highlights three standard operational templates:

Saved RunPlaybookTarget ScopeEngineUse Case
Deploy Production Web & APINginx Reverse Proxy & SSLProduction InfrastructurePODMANPushing reverse proxy updates, upstream backend balancing, and SSL renewals with locked extra variables.
Nightly Database BackupPostgreSQL Backup & S3 ArchiveProduction InfrastructurePODMANCreating compressed database dumps, streaming snapshots to object storage, and purging local temporary files.
Weekly Security Compliance AuditLinux Baseline HardeningProduction InfrastructurePODMANRunning automated CIS security checks, verifying SSH settings, and inspecting firewall rules across fleet nodes.

4. Single Source of Truth for Automation

Saved Runs act as the foundation for automated triggers across CIEL:

  • Automated Schedules (/schedules): Cron jobs link directly to a Saved Run. If you update the template parameters (such as switching an execution engine or adjusting extra variables), all linked schedules automatically adopt the new configuration without recreating cron rules.
  • Inbound Webhooks (/webhooks): CI/CD pipelines (such as GitHub Actions or GitLab CI) invoke a webhook token tied to a Saved Run. The external pipeline triggers deployments safely without needing access to dashboard credentials or root server keys.

5. External References

For upstream Ansible operational best practices and playbook execution tips: