Playbook Library

Manage Ansible playbooks available for MOP execution. View, edit, create, and assign playbooks to categories.

Back to Admin

9

Total Playbooks

9

Assigned to Categories

0

Unassigned
Auto-Classify
 MOP Detection Tool
Available Playbooks
How playbooks work: Each playbook is an Ansible YAML file that defines a set of tasks to execute on target hosts. Categories map MOPs to one or more playbooks that run in sequence. You can edit existing playbooks, create new ones, or assign them to categories on the Admin page Categories tab.
Playbook Description Used by Categories Lines Last Modified Actions
cert_rotation.yml Certificate Rotation cert-rotation 87 2026-03-08 01:47 View/Edit
Delete cert_rotation.yml?
commit_to_git.yml Commit Configuration Changes to Git agent-upgrade git-ops infrastructure multi-region-deploy 150 2026-03-08 01:37 View/Edit
Delete commit_to_git.yml?
db_maintenance.yml Database Maintenance Operations db-maintenance 77 2026-03-08 01:47 View/Edit
Delete db_maintenance.yml?
edit_yaml.yml Edit YAML Configuration Files agent-upgrade git-ops infrastructure multi-region-deploy 138 2026-03-08 01:37 View/Edit
Delete edit_yaml.yml?
patch_linux.yml Patch Linux Systems patch-linux multi-region-patch 112 2026-03-08 01:37 View/Edit
Delete patch_linux.yml?
run_manual_pipeline.yml Trigger Azure DevOps Pipeline agent-upgrade pipeline-only infrastructure multi-region-deploy 216 2026-03-08 01:47 View/Edit
Delete run_manual_pipeline.yml?
run_terraform.yml Execute Terraform Plan and Apply terraform 126 2026-03-08 01:47 View/Edit
Delete run_terraform.yml?
security_scan.yml Security Compliance Scan security-scan 79 2026-03-08 01:47 View/Edit
Delete security_scan.yml?
service_restart.yml Service Restart Operations service-restart 70 2026-03-08 01:47 View/Edit
Delete service_restart.yml?
How Category-to-Playbook Mapping Works
The Mapping Process
  1. Vendor delivers an archive (.tgz/.tar.gz/.gz) containing MOP templates (J2 files)
  2. Each MOP has a category defined in its frontmatter metadata (e.g., category: patch-linux)
  3. Auto-detection analyzes the MOP filename, content keywords, and frontmatter to suggest the best category
  4. Category maps to playbooks — each category has one or more playbooks that execute in order
  5. Playbooks execute the actual work: SSH to VMs, API calls to ADO, Git operations, or Terraform runs
Auto-Detection Signals

The classifier examines three signals to determine the correct category:

  • Filename patterns (weight: 3x) — e.g., "patch_linux_security_update.j2" matches patch-linux
  • Content keywords (weight: 1x) — e.g., "terraform plan" or "yum update" in the MOP body
  • Frontmatter fields (weight: 5x) — e.g., type: terraform or category: git-ops

The highest-scoring category is suggested, with a confidence percentage showing how strong the match is.

Try Auto-Classification Tool